Actions when Including Additional Import Data that Does Not Affect the Database Level


We assume that the customer wants to use additional import data that is only required at runtime.

Process Flow

This type of enhancement requires the following steps at most:

  1. Creating help structures
    In the first step, create data structures that contain the additional, related fields that are to be passed on to the BAPI. 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 the help structures, see
    Enhancing the BAPI with Import Data that Does Not Affect the Database Level.
  1. Programming the 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.

Read the documentation about Business Add-Ins.

  1. Filling ExtensionIn before a BAPI call
    The customer can generally use any structure for the data to transfer in the ExtensionIn container. If help structures are used, the structuring described in
    Actions for an Enhancement Based on Existing SAP Database Tables is available.