System Settings for Resource-related Billing

When you work with resource-related billing, you will need to change some of the system settings in the online Implementation Guide. The most important system settings are as follows:

For further information, see the online Information Guide.

1. Settings for document types in SD

We recommend that you make the following changes in the document types for sales orders and billing requests:

You make the settings for the document type in SD Customizing via  Sales Sales documents Sales document header .

2. Settings for pricing

During resource-related billing the customer is charged for costs such as bills from vendors, hotel costs etc. In these cases, no general sales price can be specified for the materials that these items represent in the billing request. More often, the price can only be determined from costs in question.

For this reason, conditions for these kinds of prices (e.g. PR00) cannot be marked as mandatory in pricing procedure used for pricing in the billing request.

You can find the settings for pricing in SD Customizing via  Basic functions Pricing .

3. Determining activities for billing request items

In resource-related billing, information on the resources required is used when the system creates items in the billing request. The resource items are represented in the billing request as activities. For this reason, you need to assign the following to the activities in the appropriate application (internal orders, maintenance, project system).

This is carried out in Customizing.

Internal company services and costs are represented as activities in the standard system. You need to create service materials for these activities so that resource-related billing can take them into account.

4. Defining reasons for rejection

Reasons for rejection are used during resource-related billing to:

You can enter a description in the online Implementation Guide for individual reasons for rejection. For each reason for rejection the system also specifies how an item marked with that particular reason for rejection is treated when subsequent new billing requests are created.

For example, the following reasons for rejection could be specified:

You can mark an item as not relevant for billing using this reason for rejection also. It is also no longer proposed in subsequently created billing requests.

The following indicators are set for this reason for rejection:

- Ndr = ‘X’, the item will not be forwarded for printing

- EPO = ‘_’, the item is treated as completed for subsequent billing requests

- FKE = ‘X’, the item cannot be transferred to the billing document

- STAT = ‘-’, the item value is not considered when determining the overall value of the document

You can mark an item as not relevant for billing using this reason for rejection also. It is still proposed for subsequently created new billing requests, however.

The following indicators are set for this reason for rejection:

- Ndr = ‘X’, the item will not be forwarded for printing

- EPO = ‘X’, the item is still open

- FKE = ‘X’, the item cannot be transferred to the billing document

- STAT = ‘-’, the item value is not considered when determining the overall value of the document

You use this reason for rejection to mark an item in a billing request when a billing document had already been created for the billing request but was then canceled.

You can no longer simply delete the billing request item. You can also use this reason for rejection to mark an item that is to be transferred to another billing request.

The following indicators are set for this reason for rejection:

- Ndr = ‘X’, the item will not be forwarded for printing

- EPO = ‘X’, the item is still open

- FKE = ‘X’, the item cannot be transferred to the billing document- STAT = ‘-’, the item value is not considered when determining the overall value of the document