SAP ABAP IMG Activity RMS_RCP_TRANSF (BAdI: Checks Whether General Recipe Can Be Transformed to Master Recipe)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ PLM-RM-REC (Application Component) Recipe
     ⤷ RMSRCPCST (Package) RMS-RCP: Customizing Recipe
IMG Activity
ID RMS_RCP_TRANSF BAdI: Checks Whether General Recipe Can Be Transformed to Master Recipe  
Transaction Code S_XBK_47000016   (empty) 
Created on 20030718    
Customizing Attributes RMS_RCP_TRANSF   BAdI: Checks Whether General Recipe Can Be Transformed to Master Recipe 
Customizing Activity RMS_RCP_TRANSF   BAdI: Checks Whether General Recipe Can Be Transformed to Master Recipe 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RCP_GR_TO_MR_ALLOWED    

Use

This Business Add-In (BAdI) is used in the Recipe Management (PLM-RM) component.

The system uses this BAdI to check whether a transfer of general recipe data to master recipes is allowed.

Checking criteria are the plant, the logical system of the master recipe, and the GUID of the general recipe. Using this information, the system checks the application area for the general recipe and decides whether the general recipe can be used to create the master recipe.

Requirements

Standard settings

The BAdI is active in the system.

Standard implementation: CL_DEF_IM_RCP_GR_TO_MR_ALLOWED

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:

  1. 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.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. 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.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. 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:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

See also

Method: Check Whether GR -> MR Transfer Is Allowed

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  20030718 
SAP Release Created in 220