Ansicht
Dokumentation

BAPI_PPR_MAINTAIN_40 - CRM 4.0 Method "Maintain Partner/Product Ranges (PPRs)"

Functionality

This method allows the independentmaintenance (create/change/delete) of the following objects of Partner/Product Ranges (PPRs):

• Headers (input table HeaderData),

• Header descriptions (input table HeaderDescription),

• Header organisational data (input table HeaderOrganisationalData),

• Header organisational data extension fields (input table HeaderExtensionFields),

• Items (input table ItemData)

• Item descriptions (input table ItemDescription),

• Item business partner data (input table ItemBusinessPartnerData),

• Item product data (input table ItemProductData),

• Item validity period data (input table ItemValidityPeriodData),

• Item rule parameter data (input table ItemRuleParameterData) and

• Item business partner / product / validity period data extension fields (input table ItemExtensionFields).

All input parameters and input tables are optional, except the success/error message log Return.

An authority check is performed using the authorization object CRM_PRP_BP. Depending on the PPR types defined in the Customizing of the CRM Online System, it is checked, which activities (Create, Change and/or Delete) are allowed.

General Remarks

• Each line of the below mentioned input data tables must contain a valid PPR type defined in the CRM Customizing. If, at least, one wrong PPR type is contained, all input data is rejected and nothing will be posted to the database.

• For each PPR type used within this method, an authorization profile using the authorization object CRM_PRP_BP must be maintained in the CRM system. Possible activities are 'Create', 'Change' and 'Delete'.

• For each line of the below mentioned input data tables, the field Processing_Mode mustbe filled with one of the following values:

• 'A' (for creating data),

• 'B' (for changing data) and

• 'D' (for deleting data).

• For each object (header, item, descriptions, organisational data, business partner / product / validity period references, extension fields, rule parameter data) of a PPR that is to be created or changed, a corresponding line in the input data table InputFieldData must exist.

• If PPR data is to be created in the database,

• each input table line must either contain a value for the field Handle to identify it or contain a value for the field GUIDtogether withthe value 'X' for the field Foreign_Source_System, if an already existing GUID of an external system is to be used

• for each input table line - except header data, org. data extensions and business partner / product / validity period extensions -, the field Reference_Handle or Reference_Guidmust be filled with the value of the respective field Handleor GUID(Globally Unique ID) of the related PPR header or item.

• If existing PPR data is to be changed/deleted in the database,

• each input table line must contain the value of the respective field Guidof the related entry in the database in the input table field Guid.

• each input table line - except header data, org. data extensions and business partner / product / validity period extensions - must contain the value of the respective field Guidof the related PPR header or item in the input table field Reference_Guid.

• If existing PPR Data is to be changed, only those fields of the respective input data line are to be filled, whose values are to be changed in the database.

• In case of updating an existing PPR, the tables HeaderData and ItemData, respectively, have only to be filled, if header administrative data or item administrative data is to be modified. If any other PPR object is to be modified, for example a product entry is updated or newly created, it is sufficient to make an entry in the respective input table, in this example ItemProductData.

• Note that false input data is reported in the error message log Return, but the data is nevertheless posted to the database. Therefore, the error message log must be carefully considered and checked to recognize wrong data. The erroneous lines have to be corrected and posted again, so that the data in the database is correct and consistent.

• For defined and allowed input values, have a look at the data elements contained in the Data Dictionary structures BAPI40_<OBJECT>_COMwith