Show TOC

 Replicate Supplier as Bulk V1

 

To replicate the supplier data.

Technical Data

Entity Type

Service Operation

Software Component Version

RTLDDF 200

Release State

Released

Technical Name

SupplierReplicateBulkRequest_In

Namespace

http://sap.com/xi/RTLDMF/Global2

Category

SAP A2A

Direction

inbound

Mode

Asynchronous

Idempotency

Not applicable

Change/Update Behavior

Type 1

P2P Communication Enabled

True

Business Context and Use

The Replicate Supplier as Bulk V1 service operation is used to receive the supplier (also known as vendor) master data.

Features

The inbound operation creates, updates, and deletes the vendor data.

The operation includes the following main nodes:

  • External Location Identifier

  • Sending System Identifier

  • Time Zone

  • Address Data

Message Types

  • SupplierReplicateBulkRequest_V1

Error Handling

The Replicate Supplier as Bulk V1 operation supports Forward Error Handling (FEH).

Notes on SAP Implementation

  • The vendor is defined in the location master data using the Location Type Code field with entry 1011.

  • The Interface Workbench receives all data coming through an Extensible Markup Language (XML) message. The relevant tables for this process component are as follows: /dmf/mdif_loc, /dmf/mdif_loctxt, /dmf/mdif_locadr, and /dmf/mdif_locass.

  • The generated proxy in Demand Data Foundation (DDF) is the /DMF/CL_FND_SPLRRPLCTBLK ABAP class. The proxy data type is used in DDF for the /DMF/FND_SPLR_RPLCT_BLK_RQ incoming bulk replication message.

  • The Service Implementation Workbench (SIW) is used to implement the service back-end system. The SIW uses the /DMF/II_FND_SPLRRPLCTBLK project ID configuration name and the /DMF/CL_FND_SPLRRPLCTBLK_SI generated service implementation class.

  • DDF uses the Service Mapping Tool (SMT) for the inbound message mapping (/DMF/CL_SUPPLIER_SMT Mapping field).

Enhancements

The /DMF/SE_FND_SPLRRPLCTBLK Business Add-In (BAdI) is available for this operation. The BAdI is used to enhance the inbound message, and it is defined as an external customer BAdI. A default implementation is not delivered.