3792567 - S/4 To Ariba Invoicing: Schedule Replication For Supplier, GL Account, And Project (WBS) Data Instead Of Manual “Replicate By Replication Model”

• When new supplier records are created or when supplier, general-ledger account, or project/WBS data changes, the user runs the “replicate by replication model” app in s/4 and then runs the scheduled import in ariba invoicing.
• The user asks whether a batch job can be scheduled in s/4 to perform this replication automatically.
• No error messages are mentioned.

• Product: SAP S/4HANA Cloud Public Edition
• Logistics Invoice Verification (Public Cloud)

1. Create or change a supplier, general-ledger account, or project/WBS element in s/4.
2. Observe that replication is performed manually via the “replicate by replication model” app in s/4.
3. Run a separate scheduled import on the ariba invoicing side to receive the data.

• The “replicate by replication model” app is intended for one-off or exceptional runs (for example, initial load or recovery after a failed run), not for daily operational synchronization.
• For these data types, s/4 can send changes automatically upon save; the manual habit suggests automatic sending may be disabled or not configured for all involved data types.
• No ready-made scheduled job template specific to supplier/general-ledger/project data to ariba was found in standard documentation; availability must be verified in the Application Jobs app.
• Other apps identified by the user are not applicable (one relates to United States tax reporting; another runs only on the ariba side).

1. Validate automatic outbound replication:
   1. Change one test supplier record in s/4; do not run the manual app; verify it reaches Ariba invoicing automatically.
   2. Repeat for a general-ledger account and a project/WBS element.
2. If automatic replication works for all three data types:
   1. Discontinue routine use of the manual “replicate by replication model” app.
   2. Enable and use replication monitoring to detect any failures promptly.
3. If automatic replication does not work:
   1. Open the Application Jobs app in s/4.
   2. Check whether a suitable replication job template exists for these data types.
   3. If available, perform one initial full load, then schedule a recurring job in delta (“changes”) mode.
4. If no suitable job template exists and automatic replication is unavailable:
   1. Continue with disciplined manual runs using the “replicate by replication model” app.
   2. Monitor each run using replication monitoring.
   3. Submit an enhancement request via the SAP Customer Influence process to ask for a schedulable option.
5. Do not use the United States tax scheduling app or the Ariba-side import job to schedule s/4 outbound replication; they are unrelated to this use case.

Important: Keep manual runs in place until automatic replication is confirmed for supplier, general-ledger, and project/WBS data to avoid data mismatches in ariba invoicing.

• refer to: SAP S/4HANA Cloud Public Edition – Replicate Master Data Using SAP Master Data Integration
• refer to: KBA 2963059 — SAP Customer Influence process (requesting product enhancements)

ariba invoicing, schedule replication, replicate by replication model, supplier replication, gl account replication, wbs replication, application jobs, automatic replication, delta replication, initial load, monitor replication, s/4 to ariba integration, background job, data synchronization , KBA , MM-IV-LIV-2CL , Logistics Invoice Verification (Public Cloud) , Problem