Data Caching Implementation Example: Master Data from S/4HANA

Scenario

A Supplier Portal requires master data such as suppliers, materials, and company details from S/4HANA to function efficiently. Since master data changes infrequently, a batch synchronization approach with a local cache is ideal. The cached data will be refreshed weekly to minimize API calls and backend load.

---

Objective

• Cache supplier, material, and organizational master data locally in the portal’s database.
• Ensure the cache remains consistent with the S/4HANA backend through periodic updates.
• Optimize access speed for the portal while minimizing dependency on real-time API calls.

---

Steps for Implementation

Step 1: Identify Master Data Entities

Master data entities required for the portal:

• Supplier Master Data
• Material Master Data
• Organizational Units

---

Step 2: Design the Cache Database

Create database tables in the portal’s local database to store master data.

Supplier Master Data Table:

CREATE TABLE SupplierMaster (
    SupplierID VARCHAR(20) PRIMARY KEY,
    SupplierName VARCHAR(255),
    City VARCHAR(100),
    Country VARCHAR(100),
    ContactPerson VARCHAR(255),
    Email VARCHAR(255),
    Phone VARCHAR(20),
    LastUpdated TIMESTAMP
);

Material Master Data Table:

CREATE TABLE MaterialMaster (
    MaterialID VARCHAR(20) PRIMARY KEY,
    MaterialName VARCHAR(255),
    MaterialType VARCHAR(50),
    UnitOfMeasure VARCHAR(10),
    Price DECIMAL(10, 2),
    LastUpdated TIMESTAMP
);

Organizational Units Table:

CREATE TABLE OrgUnits (
    OrgUnitID VARCHAR(20) PRIMARY KEY,
    OrgUnitName VARCHAR(255),
    ParentUnitID VARCHAR(20),
    Location VARCHAR(255),
    LastUpdated TIMESTAMP
);

---

Step 3: Fetch Master Data from S/4HANA

Use SAP OData APIs to fetch master data from S/4HANA.

Supplier API Call:

GET /sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner?$filter=BusinessPartnerRole eq 'FLVN00'

Material API Call:

GET /sap/opu/odata/sap/API_MATERIAL_MASTER_SRV/A_Material?$filter=MaterialType eq 'RAW'

Organizational Units API Call:

GET /sap/opu/odata/sap/API_ORGANIZATION_SRV/A_Organization

---

Step 4: Transform and Load Data

Once the data is fetched, transform it to match the portal’s schema and load it into the cache database.

Example Transformation Logic in Node.js:

const axios = require('axios');
const { Pool } = require('pg');

// Database connection pool
const pool = new Pool({
  user: 'username',
  host: 'localhost',
  database: 'supplier_portal',
  password: 'password',
  port: 5432,
});

// API endpoint and headers
const apiUrl = 'https://s4hana.example.com/sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner';
const headers = { Authorization: 'Bearer YOUR_ACCESS_TOKEN' };

// Fetch and update supplier master data
async function syncSupplierMasterData() {
  try {
    const response = await axios.get(apiUrl, { headers });
    const suppliers = response.data.value;

    const client = await pool.connect();

    for (const supplier of suppliers) {
      await client.query(`
        INSERT INTO SupplierMaster (SupplierID, SupplierName, City, Country, ContactPerson, Email, Phone, LastUpdated)
        VALUES ($1, $2, $3, $4, $5, $6, $7, NOW())
        ON CONFLICT (SupplierID) DO UPDATE
        SET SupplierName = EXCLUDED.SupplierName,
            City = EXCLUDED.City,
            Country = EXCLUDED.Country,
            ContactPerson = EXCLUDED.ContactPerson,
            Email = EXCLUDED.Email,
            Phone = EXCLUDED.Phone,
            LastUpdated = NOW();
      `, [
        supplier.BusinessPartner,
        supplier.BusinessPartnerName,
        supplier.CityName,
        supplier.Country,
        supplier.ContactPersonName,
        supplier.EmailAddress,
        supplier.PhoneNumber,
      ]);
    }

    client.release();
  } catch (error) {
    console.error('Error syncing supplier master data:', error.message);
  }
}

// Call the sync function
syncSupplierMasterData();

---

Step 5: Schedule Data Sync Jobs

Set up a periodic job to refresh the cache using tools like Cron Jobs or ETL Pipelines.

Example Cron Job for Weekly Sync:

0 2 * * SUN node sync_master_data.js

---

Step 6: Monitor and Validate Cache

Monitoring:

• Track the success of sync jobs and log errors.
• Use monitoring tools to ensure API availability.

Validation:

• Periodically compare cached data with the backend to verify consistency.
• Example: Run reconciliation scripts every month.

---

Best Practices

1. Optimize API Usage:
   • Use pagination and filters to fetch only necessary data.
   • Example: Fetch suppliers by region or activity status.
2. Handle Delta Updates:
   • Use timestamps or delta tokens to fetch only updated or new records.
   • Example: Filter suppliers by LastChangeDate.
3. Secure Data Transfer:
   • Use HTTPS and OAuth2 for API calls.
   • Encrypt sensitive data in the cache.
4. Manage Cache Expiry:
   • Set a TTL for cached data to ensure it remains relevant.
   • Example: Weekly expiry for supplier master data.
5. Implement Fallback Mechanisms:
   • Provide a fallback mechanism to fetch data directly from S/4HANA in case of cache misses.

---

Example Use Case: Supplier Portal

Scenario: A Supplier Portal needs supplier and material master data to:

• Display supplier details on dashboards.
• Validate materials during quotation submissions.

Workflow:

1. Supplier logs in to the portal.
2. Portal retrieves supplier and material details from the cache.
3. If the requested data is not in the cache:
   • Trigger an API call to fetch the missing data.
   • Update the cache with the new data.

Benefits:

• Faster response times for suppliers.
• Reduced load on S/4HANA backend.
• Consistent and up-to-date data for portal operations.

---

Conclusion

Caching master data from S/4HANA enables efficient access and reduces backend dependency in integration scenarios. By implementing a structured approach involving batch jobs, delta updates, and secure data transfer, businesses can achieve optimal performance and data consistency. Proper monitoring and validation ensure the cache remains reliable for business-critical operations.