SAP ABAP IMG Activity CMX_XSRSRVXSV (BAdI: Enhancements for Standard XStep Repository)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PP-PI-PMA (Application Component) Process Management
     ⤷ CMX_XSR (Package) XSteps: Standard Repositories
IMG Activity
ID CMX_XSRSRVXSV BAdI: Enhancements for Standard XStep Repository  
Transaction Code S_PLN_06000251   (empty) 
Created on 20030604    
Customizing Attributes CMX_XSRSRVXSV   BAdI: Enhancements for Standard XSteps 
Customizing Activity CMX_XSRSRVXSV   BAdI: Enhancements for Standard XStep Repository 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CMX_XSR_SRV_XSV    

Use

You can use this Business Add-In (BAdI) CMX_XSR_SRV_XSV to influence actions in the standard XStep repository (SXS repository). You can remove actions from the context menu, or add specific actions to the context menu for specific actions.

Requirements

Standard settings

The BAdI can be used more than once, which means that you can create several active implementations that can be called for the relevant actions in the SXS repository.

Method ON_NODE_CREATE:

The implementation of this method is called when a new node is created in the SXS repository (folder, standard XStep, version). In the implementation of this method, you can influence the attributes of the newly created node (for example, set an additional status for a version).

Method ON_ACTION_SELECT:

The implementation of this method is called when actions for a node in the SXS repository are selected in the context menu. In the implementation for this method, you can remove actions from the context menu and add specific actions. For example, for the implementation of an approval procedure you can define a new action "Approve".

Method ON_ACTION_PREPARE:

The implementation of this method is called before an action for a node in the SXS repository is performed. In the implementation for this method, you can check whether the execution of the action should be prevented by specific conditions. For example, to implement an approval procedure, you can check whether the user has the required specific authorizations or knowledge.

Method ON_ACTION_EXECUTE:

The implementation of this method is called when a specific action is called in the SXS repository for a node, where the action cannot be performed by the SXS repository. This specific action must be included in the context menu using the method ON_ACTION_SELECT. For example, to implement an approval procedure, you can request a digital signature, then set an additional status for a version once the signature has been successfully made.

Method ON_ACTION_CANCEL:

The implementation of this method is called when an action could not be performed in a node in the SXS repository and the execution was canceled. In the implementation for this method, you can, for example, influence the attributes of this node (for example, add or delete an additional status for a version) or note the canceled action in a log.

Method ON_ACTION_COMPLETE:

The implementation of this method is called after an action was successfully performed in a node in the SXS repository. In the implementation for this method you can, for example, further influence the attributes of the node to process, or note the performed action in a log.

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 code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. 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 code you stored in the method will be run when the application program is executed.

Example

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
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  20030604 
SAP Release Created in 200