Delivery-Related Billing

You use this process if you have integrated SAP ERP and want to bill for delivered quantities. As well as enabling you to bill for partial deliveries, this process enables you to bill for delivery costs, such as shipping costs.

Note Note

This following describes the process of delivery-related billing for deliveries with goods issue. Delivery-related billing is also possible if no goods issue is involved (if a delivery document has no goods movement type). In this case, a billing due list item is automatically created when a delivery document is saved.

End of the note.

Prerequisites

You have made the following settings in Customizing for Customer Relationship Management:

You have set the billing relevance Delivery-Related Billing or Delivery-Related Billing – No Zero Quantities for the relevant item category.
You do this by choosing Billing Define Billing Relevance of Item Categories .
The billing-relevance Q is set for the corresponding item category in SAP ERP. This ensures the following:
- Billing takes place in SAP CRM and not SAP ERP.
- After billing, the status of the delivery item in SAP ERP is set to Billed and the billing document item is included in the document flow for the delivery item.
You have specified that the billing item category assigned to the sales order is a dependent item. This ensures that the billing due list item created for the sales order cannot be billed independent of the delivery.
You make this setting by choosing Billing Define Billing Item Categories and setting the Dependent Item indicator for the relevant billing item category.

Example
In the standard system, the billing item category TAND is predefined for delivery-related billing. It can be assigned to transaction type TA (Sales Order) and the item category TAN (Sales Item) under Billing Item Category Determination Assign Item Categories .

End of the example.
You have assigned a separate billing item category to the transaction type and item category that are used for the delivery. This enables the system to assign the correct billing type and billing item category to the billing due list item for the delivery.

Example
The billing item category TAN is predefined in the standard system. It can be assigned to transaction type LF (Outbound Delivery) and the item category TAN (Sales Item) under Billing Item Category Determination Assign Item Categories .

End of the example.

For information on the required CRM Middleware settings for data transfer, see Data Exchange with SAP ERP for Delivery-Related Billing.

Process

The flow of data in delivery-related billing is shown in the following figure:

This graphic is explained in the accompanying text.

A user creates a sales order in SAP CRM.
The system replicates the sales order in SAP ERP.
The system creates a dependent item in the billing due list, containing billing information from the sales order.
A user creates a delivery in SAP ERP.
The system updates the delivery status in the SAP CRM sales order, and updates the transaction history.
A user posts a goods issue in SAP ERP.
The system updates the delivered quantity in the SAP CRM sales order, and updates the transaction history.
In SAP CRM, the system creates billing due list items for delivery items.
A user creates a billing document in SAP CRM.
The billing document is based on billing due list data from steps 3 and 8.
The system updates the billed quantity, billing amount, status, and transaction history, and deletes the corresponding billing due list item.

Note

The above process is different if you implement the service parts management functions for orders (for more information, see SPM Functions in Customer Order Management). In this case, the SAP CRM sales order is not replicated in SAP ERP. Instead an unchecked delivery is automatically created in SAP ERP.

End of the note.

Result

You can see the delivery documents created in SAP ERP in the CRM WebClient UI (on the Billing Documents page, in the Referenced Transactions assignment block).