Kontakt

Ansicht
Dokumentation

CRM_SRV_ACCT_TOOL - BAdI: Determine Tool Costs and Account Assignment

CRM_SRV_ACCT_TOOL - BAdI: Determine Tool Costs and Account Assignment

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

You use this Business Add-In (BAdI) in the Product Costs Controlling (CO-PC) component.

You can use this Business Add-In to reorganize the account assignment and determination of tool costs in CRM service processes. The system calculates tool costs by using an hourly rate.

The BAdI is called either to determine planned costs for a service process or to determine actual costs for a service confirmation. You can recognize which case applies from the value type that is transferred to the BAdI.

When calculating tool costs for service processes, an account assignment object is credited. To do this, you can specify different types of account assignment objects:

Cost center / activity type (default)

Cost center

Internal order

If a cost center/ activity type is credited by the allocation, the system executes an internal activity allocation for service confirmations. If a cost center or an internal order is credited, the system executes reposting to the service confirmations.

For account assignment to the cost center / activity type, tool costs are calculated by using the activity price. In this case, do not determine the rate and currency key in the BAdI.

For account assignment to the cost center or internal order, on the other hand, you must determine the rate and currency key in the BAdI.

In default implementation, the BAdI is active and is used to determine a cost center / activity type. To do this, a Customizing table is used that contains as assignment criteria characteristics from the material master for production resources.

The Business Add-In 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.

To display example coding, choose Goto → Default Coding → Display.






ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4126 Date: 20240523 Time: 180139     sap01-206 ( 65 ms )