SAP ABAP IMG Activity DPR_BAPI_BUS2167_APP (BAdI: Approval for BOR Object Phase in a Template)
Hierarchy
☛ CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0
   ⤷ PPM-PRO (Application Component) Project Management
     ⤷ DEVELOPMENT_PROJECTS_CUSTOMIZE (Package) General Customizing for Project Management
IMG Activity
ID DPR_BAPI_BUS2167_APP BAdI: Approval for BOR Object Phase in a Template  
Transaction Code S_CP4_60000014   (empty) 
Created on 20040205    
Customizing Attributes DPR_BAPI_BUS2167_APP   BAdI: Approval for BOR Object Phase in a Template 
Customizing Activity DPR_BAPI_BUS2167_APP   BAdI: Approval for BOR Object Phase in a Template 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BAPIEXT_BUS2167_APP    

Use

This Business Add-In (BAdI) is used in the Project Managment (PPM-PRO) component. This BAdI enables you to use the customer-defined fields in the BAPIs when approving a phase in a template.

The ApprovalCreate and ApprovalChange methods of the BAPI for creating an approval each contain the importing parameter IS_EXTENSION_IN and the exporting parameter ES_EXTENSION_OUT for you to use, the ApprovalGetDetail method only contains the exporting parameter ES_EXTENSION_OUT.

If you fill the IS_EXTENSION_IN extension structure correctly and have implemented the following methods of the BAdI, you can carry out customer-defined checks before the approval is created or changed:

Method        Action

CREATE_EXIT_IN        Create approval

CHANGE_EXIT_IN        Change approval (name and comment)

If this method returns at least one message of the type 'E', 'A', or 'X' in the return table, the system stops processing the BAPI.

  • If you fill the extension structure IS_EXTENSION_IN correctly in the ApprovalChange method, and the Extensions indicator has been set in the update structure, you can use the CHANGE_EXIT_MAP method of the BAdI to fill the customer-defined fields of the CI structure CI_DPR_APPROVAL with the values from this extension structure.
  • After the current approval has been created or changed, you can fill the exporting structure ES_EXTENSION_OUT provided that the importing structure IS_EXTENSION_IN has been filled correctly and you have implemented the following methods of the BAdI.
    This method cannot undo the action. All messages from the return table are transferred to the log.

Method    Action

CREATE_EXIT_OUT    Create approval

CHANGE_EXIT_OUT     Change approval (name and comment)

  • You can use theGET_DETAIL_EXIT_MAP method of the BAdI to transfer the customer- defined fields (that is, the content of the CI include CI_DPR_APPROVAL for the current approval) to the ES_EXTENSION_OUT parameter.

Requirements

Standard settings

  • The BAdI is not active in the standard system and there is no default code.
  • The BAdI is not dependent on a filter and cannot be used more than once.

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.

Example

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  20040205 
SAP Release Created in 310