Kontakt

Ansicht
Dokumentation

CPRO_BAPIBUS2173IAPP - BAdI: Individual Approval for BOR Object Phase

CPRO_BAPIBUS2173IAPP - BAdI: Individual Approval for BOR Object Phase

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Project Management (PPM-PRO) component. This BAdI enables you to use the customer-defined fields for the individual approval of a phase in the BAPIs too. Each decision maker for an approval then represents an individual approval.

The IndividualApprovalAdd, IndividualApprovalChange, and IndividualApprovalRemove methods each contain the importing parameter IS_EXTENSION_IN and the exporting parameter ES_EXTENSION_OUT. The ApprovalGetDetail method delivers the individual approvals to the ET_IND_APPROVAL exporting table. The customer-defined fields that belong to the individual approvals are available in the ET_IND_APPROVAL_EXTENSION_OUT exporting table.

  • If you fill the IS_EXTENSION_IN extension structure correctly and have implemented the methods named below of the BAdI you can carry out customer-defined checks before the action that belongs to the method is performed for the current individual approval.
    If the method in the return table returns at least one message of the type 'E', 'A', or 'X', the system cancels the processing of the BAPI.
Method   Action
ADD_EXIT_IN   Create individual approval
CHANGE_EXIT_IN   Change individual approval
REMOVE_EXIT_IN   Delete individual approval

  • If you fill the IS_EXTENSION_IN extension structure correctly in the IndividualApprovalAdd or IndividualApprovalChange method and have set the Extensions indicator in the update structure, you can use the ADD_EXIT_MAP or CHANGE_EXIT_MAP method of the BAdI to fill the customer-defined fields of the CI_DPR_IND_APPROVAL CI structure with the values of this extension structure.

  • After the action for the current individual approval has been performed, you can fill the ES_EXTENSION_OUT exporting structure, provided that the IS_EXTENSION_IN importing structure has been filled correctly and you have implemented the methods named below of the BAdI.
    This method cannot undo the action. All messages in the return table are transferred to the log.
Method   Action
ADD_EXIT_OUT   Create individual approval
CHANGE_EXIT_OUT   Change individual approval
REMOVE_EXIT_OUT   Delete individual approval

  • If you request the ET_IND_APPROVAL_EXTENSION_OUT table in the BAPI interface in the ApprovalGetDetail method, the system generates a table entry for each individual approval. You can use the GET_DETAIL_EXIT_MAP method of the existing BAdI to transfer the customer-defined fields (that is, the content of the CI_DPR_IND_APPROVAL CI include for the current individual approval) to the appropriate row in the ET_IND_APPROVAL_EXTENSION_OUT table. Mapping ET_IND_APPROVAL and ET_IND_APPROVAL_EXTENSION_OUT then takes place in that sequence so that an individual approval has the same sequence number in both tables.
 
  • You can publish the customer-defined fields of an approval externally using the GET_DETAIL_EXIT_MAP method of the BAPIEXT_BUS2173_APP BAdI (parameter ES_EXTENSION_OUT of BAPI_BUS2173_APPR_GET_DETAIL or ApprovalGetDetail).
  • You can publish the customer-defined fields of an individual approval externally using the <DS:IO.IF_EX_BAPIEXT_BUS2173_APP GET_DETAIL_EXIT_MAP>GET_DETAIL_EXIT_MAP method of the almost identical BAdI BAPIEXT_BUS2173_IAPP (rows in table ET_IND_APPROVAL_EXTENSION_OUT of BAPI_BUS2173_APPR_GET_DETAIL or ApprovalGetDetail).

 

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

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.
 






ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 8418 Date: 20240523 Time: 165504     sap01-206 ( 114 ms )