Kontakt

Ansicht
Dokumentation

CRM_SRV_BILL_BADI - BAdI: Influence on Data During External Billing of CRM Service Documents

CRM_SRV_BILL_BADI - BAdI: Influence on Data During External Billing of CRM Service Documents

RFUMSV00 - Advance Return for Tax on Sales/Purchases   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Billing (SD-BIL)component. It enables you to modify data from business transactions in SAP CRM Service (service contracts, service orders, and service confirmations) before this data is imported into SAP ECC.

The following customer-specific enhancements are available in the BAdI:

  • The method SERVICE_BILLING_DATA_CHANGE is called when service contracts and service orders are transferred.
  • The method SRVCONF_BILLING_DATA_CHANGE is called when service confirmations are transferred.

When service business transactions are transferred from SAP CRM, sales orders are created in SAP ECC, with the billing-relevant transaction items created as sales order items.

You can use the above-mentioned methods to influence sales order data, such as the order reason, billing block, partner, and conditions.

Note:

  • Service business transaction data is only transferred to SAP ECC if you have defined the item categories as relevant for external billing in SAP CRM Customizing under Customer Relationship Management → Billing → Billing Relevance of Item Categories.
  • You can use the BAdI CRM_EXT_BILLING in SAP CRM to modify data before it is transferred to SAP ECC.

You have ensured that the sales document type and the item categories for the sales order in SAP ECC are set up correctly (they should be billing-relevant but, for example, not delivery-relevant).

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.






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

Length: 3866 Date: 20240523 Time: 155849     sap01-206 ( 66 ms )