Hierarchy
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE (Package) Agency Business
IMG Activity
ID | W_WLFA_BADI_0009 | BAdI: Enhancement Process Lock |
Transaction Code | S_PL0_86000086 | (empty) |
Created on | 20040228 | |
Customizing Attributes | W_WLFA_BADI_0009 | BAdI: Enhancement Process Lock |
Customizing Activity | W_WLFA_BADI_0009 | BAdI: Enhancement Process Lock |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WLF_PROCESS_ENQUEUE |
Use
You can use this Business Add-In to define your own logic for the process lock in agency business. This is a good idea if you want to lock the process on a more detailed level than is possible in the standard system. For example, at the level of a company code or a logical day.
To do this, you define your own lock object analog to the standard lock object WLF_PROCESS_ENQUEUE, with the additional lock parameters between the document category and the process. In the BAdI methods you then replace the standard coding with your own, based on your lock object.
Requirements
Standard settings
The Business Add-In is active in the standard system. The system calls the default implementation for lock object WLF_PROCESS_ENQUEUE.
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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Documentation for BAdI method ENQUEUE_PROCESS
Documentation for BAdI method PROCESS_ENQUEUE_CHECK
Documentation for BAdI method ENQUEUE_PROCESS_ALL
Documentation for BAdI method DEQUEUE_PROCESS_ALL
Documentation for BAdI method PROCESS_ENQUEUE_CHECK_MULTIPLE
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 | 20040228 |
SAP Release Created in | 500 |