Actions when Including Additional Customer Database Tables

We assume that the customer wants to process his own tables within the BAPI.

In this case, the following steps are required at most:

1. Creating the customer tables

   If you have not already done so, create the customer tables in the customer namespace.

2. Creating Help Structures

   Create a help structure for each customer table. As mentioned above, this step is optional and is only used to ensure that the extension container has a clear, uniform structure. For more information on help structures, see Enhancing the BAPI by Including Additional Customer Database Tables .

3. Programming BAdIs

   In this case, as well, the first BAdI gives customers the option of performing data checks, while the second BAdI allows the further processing of the data passed on to the BAPI (also see Actions by the BAPI Developer ). The standard BAdI rules apply here.

   Note

   Read the documentation about Business Add-Ins .

4. Filling ExtensionIn before a BAPI call

   The customer can generally structure the data to be transferred in the ExtensionIn container in any way. If help structures are used, the structuring described in Actions for an Enhancement Based on Existing SAP Database Tables is available.

5. Evaluating ExtensionOut after a BAPI call

   The conversion of the ExtensionOut container to a structure may have to be implemented, depending on your specific situation.