CL_BUPA_CURRENT_DATA - API for Comparing Current Business Partner Data with DB

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Functionality

Introduction

The public methods of the class CVI_BP_CURRENT_DATA complete the inbound business partner data from the database and return an extensive version of the input data.

• GET_ALL - Completion of the entire Business Partner object, including the Business Partner relationships

• GET_CENTRAL - Completion of the central data sets for the Business Partner

• GET_ADDRESS - Completion of the address data sets for the Business Partner

• GET_TAXNUMBER - Completion of the tax number data sets for the Business Partner

• GET_BANKDETAIL - Completion of the bank data sets for the Business Partner

If errors occur during the processing of a business partner, the indicator ES_ERROR-IS_ERROR containsthe value 'X'. ES_ERROR-MESSAGES refers to the relevant error message. ES_ERROR-MESSAGES-ROW contains the index of the entry of the incorrect business partner in the return table ET_BUSINESS_PARTERNER, ET_CENTRAL.

The Completion Algorithm

If the importing data contains filled data sets, these are merged with with the data base version. The merging process is defined as follows:

• If an inbound data record has the value 'I' or 'C' in the field HEADER-OBJECT_TASK, no further processing takes place. The unchanged data record is then returned.

• If the indicator CURRENT_STATE in an inbound data set, e.g. in the address data set, has the value 'X', then the data set is returned without any changes.

• Filled structure-like data sets are returned without any changes. This means that no merging takes place at field level. Empty structure-like data sets are filled with the relevant data from the data base.

• Table-like data sets are processed as follows: If the indicator CURRENT_STATE is empty, all the transferred entries are copied. In addition, entries existing on the data base are also completed.

Conditions for the Input Data

The data transferred to the API methods must fulfill the following conditions:

• GET_ALL: IT_BUSINESS_PARTERS-RELATIONS may contain only Business Partner relationships, for which IT_BUSINESS_PARTERS-PARTNERS contains at least one business partner.

• All methods: The input data may not contain more than one entry per business partner.

• All methods: The business partners to be defined must be defined explicitly (IT_...-HEADER).

Relationships

A prerequisite for the method GET_ALL is that function modules for the event MERGE and the objects BUPAand BUPR are defined and activated in the transaction BUPA_CALL_FU for all business partner-relevantapplications (see function group CVI_BP_CURRENT_DATA and classes CVI_BUPA_MERGE_CENTRAL, CVI_BUPA_MERGE_FINSERV and CVI_BUPR_MERGE_CENTRAL).

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.


Length: 3025 Date: 20120526 Time: 093946     triton ( 154 ms )