Hierarchy
⤷ IS-AD-MEB (Application Component) Line Maintenance Planning (MEB Enhancements)
⤷ DIWPS_AD (Package) DI: Work Packaging and Sequencing (A&D)
IMG Activity
ID | DIWPS_REV_CHECK | BAdI: Change Customer Checks to Revision Status |
Transaction Code | S_KA5_12001406 | SAPLS_CUS_IMG_ACTIVITY |
Created on | 20030109 | |
Customizing Attributes | DIWPS_REV_CHECK | BAdI: Change Customer Checks to Revision Status |
Customizing Activity | DIWPS_REV_CHECK | BAdI: Change Customer Checks to Revision Status |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | DIWPS_REV_CHECK |
Use
You use this Business Add-In (BAdI) to add customer-specific checks with regard to releasing and completing revisions.
Requirements
Standard settings
This BAdI is used in the context of the maintenance event builder (MEB), transaction WPS1. The methods of this BAdI enable you to run additional checks when a revision is released, a revision is closed, the work center for a revision has been changed, and the status "Closed" of a revision is revoked.
Method REV_CLOSE_REVOKE_CHECK is executed when the status "Closed" of a revision is revoked. Status "Closed" of a revision can be revoked by choosing a menu option in the work area of the revision in the MEB.
Note that the implementation of BAdI method REV_CLOSE_REVOKE_CHECK is responsible for the message that the customer must be contacted. If you do not use this BAdI method to send this message, the customer will not receive a message. CAUTION: The message type must be I, S, X, or A. It must not be E or W. Use the two statements "MESSAGE i XXX(XXXX)" and "RAISE customer_exception" to display the message. Do NOT use the statement "MESSAGE i XXX(XXXXX) RAISING customer_exception", because this does not display the message.
This exception is read by the function for revoking the revision status "Closed". If the exception is raised, the status "Closed" is not revoked, and the message defined in the BAdI method is displayed.
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
See also:
Methods
Non-standard checks when closing a revision
Interface
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
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 | DIWPS_REV_CHECK | 0 | PLN0000022 | Revision Planning |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030703 |
SAP Release Created in | 471 |