After the scenario and the business object types used in it have been identified in the analysis of the scenario, the BAPI signature is defined conceptionally within the design phase. The content should be described and the parameter names and the parameter structure must be defined.
Since BAPIs represent business interfaces and not technical ones, the following central requirement for developing BAPIs arises:
In an external application, users must be able to correctly implement a BAPI call using their knowledge of the application and the BAPI documentation alone. Users are not expected to have any knowledge of SAP, so that they can view the SAP System as a "black box".
In this phase you also have to decide from the BAPI's functions, whether the BAPI is an instance method or a class method and whether it can be implemented as a
standardized BAPI.The specific instances of a business object type are identified by their key fields which is why they play a special role in this context. In the design phase, the keys of instance-dependent BAPIs should be identified as special parameters. For more details see
Defining the Interface.When designing the BAPI signature you should keep in mind: