MAINTAIN_BAPI method for Customer Upload

[melchior_periyanayagam]

For DATA Conversion activity, the customer data upload is the base for the rest of the upload. The MAINTAIN_BAPI is very powerful method from class CMD_EI_API to create as well as for change the customer data.

Customer creation and maintenance can be performed by using the below method of class CMD_EI_API

• MAINTAIN_BAPI()

This method has three import parameters as shown below,

IV_TEST_RUN parameter needs to be filed with ‘X’ to run in the Test mode.  IV_COLLECT_MESSAGE parameter needs to be filled with ‘X’ to collect the messages.

IS_MASTER_DATA parameter is the main structure for creating the customer as well as for changing the customer data.

Below tree structure shows the available components in the IS_MASTER_DATA parameter,

We will see the MANDATORY field in the aforementioned components for creation as well as for change.

a) HEADER:

In HEADER component, we have two fields.

• OBJECT_INSTANCE and
• OBJECT_TASK

Only for external customer number range, KUNNR needs to be filled under OBJECT_INSTANCE

OBJECT_TASK has two indicators,

• INSERT – I

• UPDATE – U

If it’s for customer creation, then choose the indicator as ‘I’ and for customer change, it should be ‘U’

b) CENTRAL_DATA

This component is exclusively for updating the Customer General Data. If the requirement is to create only general data, then the  CENTRAL_DATA component should be filled all MANDATORY fields.

It has following subcomponents for Customer General data,

To update the Customer Control Tab data, the CENTRAL component needs to be filled. For Address Tab, the ADDRESS component needs to be filled.

Based on the operation, the TASK field should be filled.  For example, If it’s for creating the customer, then the TASK field should  be filled with ‘I’.

To update the Comments field  in the Address tab, the REMARK component  should be filled. Since this field is text field, then Language Key needs to be filled based on the requirement.

For Payment Transactions tab, the BANKDETAILS component should be filled.

To update the communication details which is available in the Address tab, the COMMUNICATION component should be filled.

c) COMPANY_DATA

The COMPANY_DATA component is presented for updating the company code data. It has below two components,

The CURRENT_STATE is Optional field for creation as well as for change.

COMPANY

Under COMPANY, the below sub components are available,

The TASK field has two indicators as ‘I’ and ‘U’.

If it’s for company code data creation, then choose the indicator as ‘I’ and for company code data change, it should be ‘U’

The company code should be filled in the BURKS field. The DATA_KEY-BURKS and TAKS fields are MANDATORY for Company code data.

The DATA and DATAX components should be filled for Account Management tab, Payment Transactions tab, Insurance tab and correspondence tab except the Dunning data.

For Dunning data from  correspondence tab, the DUNNING component needs to be filled. For Withholding Tax, the WTAX_TYPE component should be filled.

d) SALES_DATA:

The SALES_DATA component is presented for updating the sales area data. It has below two components,

The CURRENT_STATE is Optional field for creation as well as for change.

SALES

The TASK field has two indicators as ‘I’ and ‘U’.

If it’s for sales data creation, then choose the indicator as ‘I’ and for sales data change, it should be ‘U’

Under DATA_KEY, three key fields are available for Sales area data. The TASK and DATA_KEY are mandatory for Sales area data.

The DATA and DATAX components should be filled for Sales tab, Shipping tab, billing document tab except for Taxes details.

For Taxes, the TAX_IND component which is available in the CENTRAL_DATA component should be filled.

For Partner function, the FUNCTIONS component should be filled with Mandatory partner function.

 

The partner functions should be filled for successful creation of customer. With the help of account group, the partner determination procedure can be identified.

By using the tpaer table w.r.t to partner determination procedure, the mandatory partner functions can be identified to update the customer successfully,

Output Parameters

It has four output parameters to show the status of the customer upload.

·         ES_MASTER_DATA_CORRECT         -      Total Customer Data Without Errors

·         ES_MESSAGE_CORRECT                    -      Error Indicator and System Messages for Data Without Errors

·         ES_MASTER_DATA_DEFECTIVE       -      Incorrect Total Customer Data

·         ES_MESSAGE_DEFECTIVE                  -      Error Indicator and System Messages for Incorrect Data