SAP ABAP IMG Activity BSD_ESA_GENERAL_SE19 (Implement Enhancements for Inbound and Outbound Processing)
Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation
   CA-SOA (Application Component) Enterprise SOA
     BS_SOA_REUSE_CUST_DOCU (Package) Business Suite SOA: General Documentation and Customizing
IMG Activity
ID BSD_ESA_GENERAL_SE19 Implement Enhancements for Inbound and Outbound Processing  
Transaction Code S_BSD_38000027   (empty) 
Created on 20080422    
Customizing Attributes BSD_ESA_GENERAL_SE19   Implement Enhancements for Inbound and Outbound Processing 
Customizing Activity BSD_ESA_GENERAL_SE19   Implement Enhancements for Inbound and Outbound Processing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BSD_ESA_GENERAL_SE19    

Use

You can use this IMG activity to enhance the interfaces.

Technical Background Information

The data contained in a Web service is available in an XML data format. Before the SAP backend system can process the data in the applications, the XML data types have to be assigned to corresponding ABAP data types.

The ABAP data structures that map the data structures of the Web services are implemented in the SAP backend system in the form of proxies. The proxy framework contains the information about how the XML data types are mapped to the ABAP data types and vice versa.

The proxies generally have a different data format at their interfaces (output and input parameters) than the data structures that are available for the applications and that are processed in a certain way (application log). This means it can be necessary to map the generated data of the proxy to the data that processes a BAPI, for example.

Business Add-Ins (BAdIs)

For most ABAP proxies, the corresponding BAdIs provide you with two methods with with you can enhance the services without modification. This is necessary, for example, if you wish to include additional fields in an input or output parameter or run a special application logic depending on the data supplied.

Not all the BAdIs that are available to you for enhancing the proxies are listed in the Implementation Guides for the applications of the SAP Business Suite. In the Implementation Guides you will only find those BAdIs listed that are generally used by lots of customers or that provide particular functions.

For the names of all the other BAdIs, see the respective documentation for the operations in question.

Process Flow for Mapping the Data in the ABAP Proxies

  1. In the standard set-up, the system maps the input parameters of the ABAP proxy to the data structure of the applications.
  2. It runs method INBOUND_PROCESSING
  3. It runs the application logic
  4. In the standard set-up, it maps the application logic to the output parameters of the ABAP proxy
  5. It runs method OUTBOUND-PROCESSING.

    Note

    Methods INBOUND_PROCESSING and OUTBOUND_PROCESSING have a slightly different name in some BAdIs but they function in exactly the same way.

Method INBOUND_PROCESSING

Using this method you can access all the input parameters of the ABAP proxies.The data of the application logic that is already mapped is also available to you. You can use the method to map customer fields of a proxy to the data of the application logic or adapt the data already mapped to the application logic to suit your particular requirements.

Examples

You have enhanced input parameter INPUT_PROXY_xy with customer field Z_XYAA. In the proxy, the system calls a BAPI that contains the structure EXTENSIONIN. Using structure EXTENSIONIN you can enahnce the standard system with customer-specific requirements. Using method INBOUND_PROCESSING you map the Z_XYAA field to structure EXTENSIONIN.

You have enhanced input parameter INPUT_PROXY_xy with customer field Z_XYAA. Depending on the content of field Z_XYAA, you want order type AB determined in the standard system changed to XY in the data of the application logic.

Method OUTBOUND_PROCESSING

You can use this method to access the data already mapped in the ABAP proxies. The data of the application logic is also available to you. You can map your enhancements of the standard system to the output parameters of the proxy, or realize special requirements.

Examples

You have enhanced output parameter OUTPUT_PROXY_xy with the customer field Z_XYBB. In the proxy, the system calls a BAPI in whose EXTENSIONOUT structure you can make enhancements to the standard. Using method OUTBOUND_PROCESSING you can map struture EXTENSIONOUT to the Z_XYBB field.

You wish to filter the results of a query service for one special requirement. Depending on your settings in Customizing, you do not want the service to supply the results for order type AB. You filter the results using method OUTBOUND_PROCESSING.

Requirements

Standard settings

Activities

For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BSD_ESA_GENERAL_SE19 0 ABA0000561 Enterprise SOA 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VARIDUMMY D - Dummy object SE19  
History
Last changed by/on SAP  20080422 
SAP Release Created in 701