Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-GTF-DOB (Application Component) Document Builder⤷
/IPRO/BASIS (Package) Tables, Structures, general Infrastruktur
IMG Activity
| ID | /IPRO/MGT_BADI_ORDER | Define Element Ordering Sequence |
| Transaction Code | /IPRO/67000018 | (empty) |
| Created on | 20040602 | |
| Customizing Attributes | /IPRO/MGT_BADI_ORDER | Define Element Ordering Sequence |
| Customizing Activity | /IPRO/ORDER_DEF | Define element order |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IPRO/ORDER_DEF |
Use
Implement this Business Add-In to determine if a clause should precede another during clause ordering.
The Business Add-In consists of the method described below, which can be used instead of the standard algorithm.
PRECEDE
The following import parameters are provided:
- IV_CLAUSE1
First clause ID structure. - IV_CLAUSE2
Second clause ID structure
The following returning parameters must be provided by your coding:
RV_CODE
Indicates whether the first clause should precede the second one during ordering ('X') or not ('').
Requirements
Standard settings
By default, the system compares the values of all structure members of both clauses to determine the result.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
2. Enter a short text for the implementation in the Short text for implementation field.
3. From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
4. Save your entries, and assign the implementation to a development class.
5. Place the cursor on the method, and double-click to enter method processing.
6. Enter the coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your coding. Return to the Edit Implementation screen.
8. Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
9. Choose Activate.
The coding you stored in the methods will be run when the application program is executed.
Example
For more information on using Business Add-Ins, see the SAP Library under Basis Components -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins.
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 | 20040727 |
| SAP Release Created in | 100 |
