Hierarchy

⤷

⤷

IMG Activity
ID | /SPE/BAPI_DLVEXEC_EX | BAdI: Check and Transport of Additional Data Fields/Structures |
Transaction Code | /SPE/79000051 | (empty) |
Created on | 20040722 | |
Customizing Attributes | /SPE/BAPI_DLVEXEC_EX | BAdI: Check and Transport Additional Data Fields/Structures |
Customizing Activity | /SPE/BAPI_DLVEXEC_EX | BAdI: Check and Transport Additional Data Fields/Structures |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SPE/BAPI_DLVEXEC_EX |
Use
This Business Add-In (BAdI) is used in the Delivery Processing (LE-SHP-DL) component and enables you to check and transport additional data fields and structures of the customer from the external system (for example, SAP CRM to the internal structures and/or appends).
Data is handed over to the function module using the parameter table.
Requirements
Standard settings
- In the ERP system, this BAdI is not activated, and the default code is not executed.
There are checks to determine whether a customer implementation exists.
- The Business Add-In is not filter-dependent but is reusable.
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
Further information
Documentation for interface /SPE/IF_EX_BAPI_DLVEXEC_EX.
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 | /SPE/BAPI_DLVEXEC_EX | 0 | AC00000092 | Goods Issue Process |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050114 |
SAP Release Created in | 100 |