Complex Interface for the Business Partner 

Use

You can use the complex interface for the business partner to load and change business partners automatically into/in the target system.

You can load business partners into the target system either using an initial load when you implement the components, or at regular intervals after you have gone live so that you can change the data. This second option is called the delta load.

You can use the complex interface to load in one batch the data collected in various systems and data segments. This considerably reduces the number of objects, which improves system performance.

Features

The complex interface for the business partner can be used for the mass processing of data. It contains interfaces that can be called by the distribution function in Application Link Enabling (ALE) (IDoc), the Data Transfer Workbench, or directly by means of a function module.

Data Transfer Workbench

If you use the data transfer workbench to load business partners, you can convert the IDoc format file that you optimized or aggregated in the source system to an internal transfer structure, and then the system can process it as such. The input processing module (of the complex interface) that processes the imported IDoc has to be registered in the Data Transfer Workbench. The Data Transfer Workbench then maps the input file in IDoc format to the nested transfer structure of the input processing module.

For more information about using the Data Transfer Workbench, see Data Transfer Workbench.

Custom Report

If you want to use a program you created to aggregate business partner data in the SAP System during data transfer, you can directly implement the complex interface using the relevant function modules.

The complex interface contains the following function modules:

●     BUPA_INBOUND_MAIN_SAVE (IDoc Inbound Interface for Business Partner)

●     BUPA_INBOUND_REL_SAVE (IDoc Inbound Interface for Business Partner Relationships)

The function modules process the following table types in the complex interface:

●     BUS_EI_EXTERN_T (Complex External Interface for Business Partner (Tab.))

●     BURS_EI_EXTERN_T (Copy of the Complex External Interface for Relationships (Tab.))

The table types are based on the following transfer structures of the complex interface:

●     BUS_EI_EXTERN (Complex External Interface for the Business Partner)

●     BURS_EI_EXTERN (Complex External Interface for a Relationship)

The complex interface structure is in the form of a hierarchy, and is based on the Business Application Programming Interfaces (BAPIs) of the business partner, which are table-based.

The BAPIs make it easier for you to create and change business partners because you need to supply data to these interfaces only. The interfaces call the BAPIs for processing the business partner. The complex interface automatically processes the objects in the correct order when it calls the BAPIs.

The complex interface also makes it possible to process the business partner in Current State mode. This processing mode enables the system to determine the delta for the daily change service. If all business partner data is imported using the Current State processing mode, only the changed data is updated in the respective tables.