Hierarchy

⤷

⤷

IMG Activity
ID | EHS_DG_INT_002 | BAdI: Convert and Change Data in ALE Distribution |
Transaction Code | S_ALN_01002161 | (empty) |
Created on | 20030404 | |
Customizing Attributes | EHS_DG_INT_002 | BAdI: Convert and Change Data in ALE Distribution |
Customizing Activity | EHS_DG_INT_002 | BAdI: Convert and Change Data in ALE Distribution |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | EHS_DG_INT_002 |
Use
This BAdI allows you to:
- Change dangerous goods data and packaging data before sending the data in the sending system and before posting the data in the receiving system
- Distribute customer-specific enhancements to the dangerous goods master
The BAdI has two methods for changing data. Both methods are supplied empty. In the standard system, no data is changed.
- MODIFY_DGDATA_BEFORE_SENDING
This method is called before the dangerous goods data is transferred to the ALE interface. You can change dangerous goods data and delete dangerous goods master records depending on the receiving system.
- MODIFY_DGDATA_AFTER_RECEIVING
This method is called after the IDoc was unpacked in the receiving system and is available in BAPI structures. You can change the data in the same way as for the above method.
The BAdI has two methods to distribute customer-specific enhancements in the dangerous goods master. Both methods contain standard implementations to distribute the data without any further actions.
- TRANSFER_IOTAB_2_EXTENSIONTAB
This method copies the data from the internal dangerous goods table RDGMDIOT to the extension table that serves as the data container for distribution.
- TRANSFER_EXTENSIONTAB_2_IOTAB
This method copies the data from the extension table to the dangerous goods table RDGMDIOT.
Requirements
Standard settings
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
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 | EHS_DG_INT_002 | 0 | ALR0000067 | Tools |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030404 |
SAP Release Created in | 200 |