Hierarchy

⤷

⤷

IMG Activity
ID | CRM_SRV_BILL_BADI | BAdI: Influence on Data During External Billing of CRM Service Documents |
Transaction Code | S_P7D_67000008 | (empty) |
Created on | 20050929 | |
Customizing Attributes | CRM_SRV_BILL_BADI | BAdI: Influence on Data During External Billing of CRM Service Documents |
Customizing Activity | CRM_SRV_BILL_BADI | BAdI: Influence on Data During External Billing of CRM Service Documents |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SRV_BILLING_CHANGE |
Use
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.
Requirements
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).
Standard settings
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - 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: - 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 | 20050929 |
SAP Release Created in |