Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

/AIF/INTERFACES - Define Interfaces

/AIF/INTERFACES - Define Interfaces

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define interfaces in the SAP Application Interface Framework. You have to set up the interface according to the communication technology you are using (for example, the SAP NetWeaver PI). Once an interface is defined, you can maintain its mapping and assign actions.

You have defined a Namespace using the Customizing activity Define Namespace. Each interface has to be assigned to a namespace.

You have created / generated the Raw Data Structure and SAP Data Structure for this interface.

You require the authorization to maintain interfaces for a given namespace.

There are no interfaces in the delivery of the SAP Application Interface Framework. The interface list is empty by default.

  1. Choose an existing namespace.
  2. In order to define a new interface, choose New Entries. The overview screen appears.
    To edit an existing interface, double-click into any field in the corresponding line.
  3. Assign a name to the interface and provide a short description. Assigning a name is only possible for new interfaces.
  4. Define at least the SAP Data Structure, the Raw Data Structure, and the Record Type in Raw Structure. Where you are using an SAP NetWeaver PI inbound interface, the raw data structure and the record type in raw structure are automatically filled when you enter the Proxy Class Inbound class name.
  5. [Optional] Enter a check and / or init function module name.
  6. If the interface uses the proxy framework for receiving / sending messages, you have to fill the Proxy Class Inbound for an inbound interface, or the Proxy Class Outbound for an outbound interface.
    If your service interface has multiple operations, you have to maintain the corresponding Proxy Method that the interface should use.
  7. [Optional] Define a Field for the Sending System. This value can be used, for example, as a key field for interface determination or for creating system-specific value mappings.
  8. [Optional] Define an interface status, for example, Obsolete, with the corresponding status handling. Furthermore, you can set a formal end date until which the interface will be valid.

You have an inbound interface for receiving business partner data using the SAP NetWeaver PI. You generated the proxy class ZCL_BP_INBOUND in transaction SPROXY. The generated main structure is ZBP_PI_DATA. Within the proxy class main method implementation, you call the SAP Application Interface Framework.

Within the SAP Application Interface Framework, you define an interface named BP_INBOUND. You enter the name of the SAP data structure you previously created. You also enter ZCL_BP_INBOUND as the proxy class inbound and press ENTER. The raw data structure and the record type in raw structure will be derived automatically.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3933 Date: 20211130 Time: 125453     sap01-206 ( 69 ms )