Hierarchy

⤷

⤷

IMG Activity
ID | CFX_STATUS_TRANS | BAdI: User-Defined Actions for Status Transitions |
Transaction Code | S_PPD_96000004 | (empty) |
Created on | 20040902 | |
Customizing Attributes | CFX_STATUS_TRANS | User-Defined Actions for Status Transitions |
Customizing Activity | CFX_STATUS_TRANS | User-Defined Actions for Status Transitions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CFX_STATUS_TRANS |
Use
This Business Add-In (BAdI) is used in the cFolders (PLM-CFO) component. It is called when you change the status in cFolders if a user-defined action has been assigned to the status transition. This BAdI enables you to define and implement actions such as these that are to be performed when a status is changed.
For more information, see the User-Defined Actions for Status Transitions (UI) BAdI that is also called when statuses are changed and which you can use to navigate to your own pages.
Requirements
You have defined user-defined actions for the status transition.
Standard settings
The BAdI is filter-dependent. You can create one implementation for each status action you have defined.
We deliver the following BAdI implementations for use in the engineering change collaboration process:
- CFX_ECN_LOCK
This implementation locks an engineering change number (ECN) and prevents it from being edited.
- CFX_ECN_STATUS_TRANS
This implementation releases and creates a new version of objects attached to an ECN.
- CFX_ECN_UNLOCK
This implementation unlocks an engineering change number (ECN) and allows it to be edited.
- CFX_LOCK_ATT_OBJS
This implementation locks objects attached to an ECN. However, the ECN itself can still be edited.
- CFX_UNLOCK_ATT_OBJS
This implementation unlocks objects attached to an ECN and allows them to be edited.
Note: The data entered for an action is client-dependent. Define the statuses in the client in which they will be used in cFolders. The BAdI implementation is not client-dependent. Therefore, when you define actions for the status with the same ID in more than one client, the system executes the same BAdI implementation for all these actions.
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.
See also:
Methods
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 | CFX_STATUS_TRANS | 0 | JSI0000002 | Collaboration Folders |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20041028 |
SAP Release Created in | 400 |