Hierarchy
⤷ IS-OIL-DS-TSW (Application Component) Trader's and Scheduler's Workbench
⤷ OIJ (Package) TSW Traders and Schedulers Workbench
IMG Activity
ID | SIMG_OIJ_TSW_0032 | BAdI: Ticket Validation with Complete Data |
Transaction Code | S_SO7_28000027 | (empty) |
Created on | 20030923 | |
Customizing Attributes | SIMG_OIJ_TSW_0032 | BAdI: Ticket Validation with Complete Data |
Customizing Activity | SIMG_OIJ_TSW_0032 | BAdI: Ticket Validation with Complete Data |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OIJ_TSW_0032 |
Use
This Business Add-In (BAdI) is used in the Trader's and Scheduler's Workbench (IS-OIL-DS-TSW) component.
This BAdI enables you to create new check routines used for ticket validation. During ticketing validation, the system checks the ticket header, item, and event fields. By implementing this BAdI, you can set up the system to check across all items and events for one ticket (header).
The system can check across all items or compare all items to validate dependent items (for example, if the ticket contains a schedule item and pending consumption item of a nomination).
The checks need to be included into a validation group to be activated.
Requirements
Standard settings
In the standard system, the Business Add-In (BAdI) is activated.
The BAdI affects only tickets against nominations with included bunker consumption line items.
The BAdI is filter-dependent.
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 | SIMG_OIJ_TSW_0032 | 0 | I400022114 | Trader's and Scheduler's Workbench |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20031029 |
SAP Release Created in | 472 |