Processing Method 

Use

You enter the processing methods for the complex interface in the control segments of the transfer structures.

Control segments of transfer structures are used in the different hierarchical levels of the complex interface:

Hierarchy	Level	Component
1	Object	OBJECT_TASK
2	Table	CURRENT_STATE
3	Data record	TASK
4	Single field	DATAX

The processing methods of the complex interface define for each hierarchy level how the system treats the data that is in the complex interface and is to be transferred.

The processing method at higher levels in the hierarchy governs which processing method is used for the segments further down in the hierarchy.

For an explanation of the processing methods used in the different levels of the interface, see the example “Control Segments for Ratings“. This example takes a cross-section of the Ratings in the transfer structure for master data.

Integration

Processing methods are entered in the complex interface for the business partner in the Transfer Structure for Master Data and the Transfer Structure for Business Partner Relationships.

For information about how the processing method selected interacts at various hierarchy levels of the complex interface, see Effects of Processing Method Selected at Object Level.

Features

Control at Object Level (Hierarchy Level 1)

At the highest level, which is object level (component HEADER-OBJECT_TASK), the control segment makes the processing methods Insert and Current State effective for the entire object.

In the inbound processing of the complex interface, the following processing methods can be used at object level:

Insert (I)

The business partner/business partner relationship is created in the Financial Database. This processing method is, therefore, used at object level only. It creates new business partners/business partner relationships. If the business partner already exists in the system, then the system issues an error message.

The control at data record level and single field level is ignored in mode I.

Current State (C)

The business partner is completely contained in the data structure and is to be created if it does not yet exist in the system, or changed if it already exists. All the business partner/business partner relationship components that are not contained in the data structure are deleted in the system.

Control at data record level and single field level is generally not provided if you use processing mode C.

Update (U)

This processing method is used to update business partners that are already contained in the target system. If the business partner does not yet exist in the target system, the system issues an error message. You can also use this processing method to select the business partner for archiving in the target system.

When processing method U is used, the control at table level or data record level is required.

Modify (M)

When this processing method is used, a distinction has to be made between the following two cases:

●     If the business partner already exists in the target system, the business partner is updated.

In this case, the control at table level or data record level is additionally required (see Update scenario).

●     If the business partner does not yet exist in the target system, then it is created. The control at data record level or single field level is ignored (see Insert scenario).

Delete (D)

This processing method is not supported at object level.

Control at Table Level (Hierarchy Level 2)

You can set the Current State control segment at table level. In this case, the system’s behavior for the relevant table is exactly the same as it would be if the Current State processing had been set globally at object level.

The Current State mode is then effective for all data records in the relevant table (for example, for all addresses of the business partner).

Control at data record level and single field level is not provided if the CURRENT_STATE control segment is set.

Control at Data Record Level (Hierarchy Level 3)

If you use the TASK control segment at data record level, then this processing mode is effective only for one single row in the affected database table.

The system determines which data record is to be changed by means of the DATA_KEY or DATA structure. This structure contains the data record key.

In the inbound processing of the complex interface, the following processing methods can be used at data record level:

●     Insert (I)

●     Update (U)

●     Modify (M)

In mode M, the system tests whether the data record already exists. If it does, then the data record is changed as in method U. If it does not yet exist, then the data record is created as in method I.

●     Delete (D)

This mode deletes a single data record.

Processing mode I creates data records in the same way as the Add BAPI. Processing mode U changes data records in the same way as the Change BAPI. Processing mode D deletes data records in the same way as the Remove BAPI.

Control at Data Record Level for Addresses

In addition to the general processing methods, the following values for the control segments are possible for the business partner addresses:

●     Standard (S) only permitted for standard addresses

●     Logical key insert

●     Logical key update

●     Logical key delete

●     Logical key modify

You can use processing mode S when you transfer a BP address. This standard mode processes an address data record in such a way that the standard address is processed. This means that an address GUID does not have to be specified in this processing method.

Logical processing methods behave in the same way as the other processing methods for control at data record level. Addresses are identified by specifying an activity in the operation field in the DATA_KEY structure rather than by specifying an address GUID.

For more information about address activities, see Address Data.

Control at Single Field Level (Hierarchy Level 4)

If you specify the processing method at single field level (DATAX component), then the processing mode is effective only for the selected field in the database table in question.

The system determines which field is to be changed by means of the DATA and DATAX components. The DATAX component contains the same number of fields as the DATA component, but it has an indicator for change information for the relevant user data field for the DATA component. This means that you need to set the appropriate change indicator in the DATAX component for the fields of the DATA component whose data you want to change in the data transfer. The processing of control at single field level uses the same processing logic as the corresponding field in the underlying BAPIs.

The system treats control at single field level as not relevant, if you have set the processing method at table level (CURRENT_STATE component).

Example

Data Supply with the Processing Method OBJECT_TASK U

Data Supply with the Processing Method OBJECT_TASK C