Ansicht
Dokumentation

CRM_BADI_040 - Business Add-In: Change of Relevant Accounting Data for Tools

CRM_BADI_040 - Business Add-In: Change of Relevant Accounting Data for Tools

General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Service Confirmation component (CRM-BTX-SCO).

You can use this BAdI to enhance the tool item data of a service confirmation.

The item category of the service confirmation refers to the leading business object type BUS2000187 Device Returns Item CRM.

The BAdI is active.

The default coding is executed automatically.

General Data for Current Processing

  • From a logistics perspective, the reservation (issue and return) is controlled by the Tool Manager.
  • From a commercial perspective, the quantity to be billed can be confirmed by a logistics confirmation for the tool item.

If alternative base units of measure are available in the tool product master, a tool or measuring device can be reserved as a "piece" from a logistics perspective and the time used can then be calculated.

If the system is to calculate the costs for the use of the tool, you have to flag the item category in the service and confirmation attributes as relevant for the expense account and confirmation. In Customizing for item categories, you assign the statistical cost condition type 0CT0 to the sales item attributes area.

You can maintain this condition type for the tool with a budgeted cost when you maintain the product condition types. You define the cost center to be credited for the use of the tool in the product master by assigning the set type CRM_AC_ASSIGN. This means that when a confirmation is created, the planned and actual costs and revenues for the use of the tool can be determined on the basis of the confirmed quantity and the planned condition types.

When a transfer posting is then carried out in SAP R/3 Controlling, the tool cost center (from the tool product master) is credited and the cost object for the CRM document (internal order, cost center, profitability segment, WBS element, and so on) debited.

Example:

Using 1 piece of a specific tool for 5 hours costs EUR 10/hour and generates EUR 50/hour in revenues. The condition types 0CT0 (costs) and 0PR0 (revenues) are maintained in the product master.

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 default coding, choose Goto -> Default Coding -> Display.

Method

Adjust Tool Data for Accounting






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

Length: 4864 Date: 20240523 Time: 155747     sap01-206 ( 81 ms )