Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
LO-S95 (Application Component) ANSI/ISA S95 Interface⤷
ANSI_ISA_S95_INTERFACE (Package) ANSI/ISA S95 Interface
IMG Activity
| ID | LO_S95_BADI_ENHANCE | BAdI: S95 Enhancements |
| Transaction Code | S_AEN_10000338 | (empty) |
| Created on | 20050125 | |
| Customizing Attributes | LO_S95_BADI_ENHANCE | ANSI / ISA S95 Message Processing - Enhancements |
| Customizing Activity | LO_S95_BADI_ENHANCE | ANSI / ISA S95 Message Processing - Enhancements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | S95_ENHANCEMENTS |
Use
This Business Add-In (BadI) is used in the ANSI/ISA S95 Interface (LO-S95) component. It enables you to add customer-specific processing to the S95 messages used for S95-based shop-floor integration.
This BAdI is called after the SAP ECC system has processed the S95 messages. It updates the tables in the SAP ECC system with the message data.
Requirements
You have activated S95-based shop-floor integration in Customizing for Logistics General under Shop-Floor Integration and ANSI/ISA S95 Compliance -> Activate S95-Based Shop-Floor Integration.
You have maintained the SAP XI destination for S95 messages sent from the SAP ECC system to SAP XI in Customizing for Logistics General under Shop-Floor Integration and ANSI/ISA S95 Compliance -> Maintain the XI Destination for the ANSI/ISA S95 Interface.
Standard settings
The BAdI is activated in the standard system. If you activate the BAdI without modifying it first, the default code is implemented. If there is no active customer implementation, the system executes the default code.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.andendmethod.statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
To display the default code, choose Goto -> Default Code -> Display .
The default code includes S95 message transformations, updates in the SAP ECC system from inbound messages, and calls to the SAP XI system for outbound messages.
See also:
Methods
Interface
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050128 |
| SAP Release Created in | 600 |
