Sie sind auf Seite 1von 43

5/2/2019

Project System (PS)


Generated on: 2019-05-02

SAP S/4HANA | 1809.001

PUBLIC

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the SAP Help Portal.

This is custom documentation. For more information, please visit the SAP Help Portal 1
5/2/2019

Resource-Related Billing
Use
The prices for customer-speci c services are not always de ned in a contract as xed prices, nor can they always be determined
using standard pricing. This is the case if, for example, no empirical values exist for speci c services, and therefore the services
cannot be calculated adequately before the conclusion of a contract. Typical examples of this are the following:

Make-to-order production

External plant maintenance in the service company

Speci c services such as consulting

For these kinds of orders, you carry out resource-related billing. The customer receives a billing document verifying individual
materials, internal activities, and costs. The basis for creating a billing document is the billing request (see Create Billing
Request).

Implementation Considerations
Since static billing is no longer available, you may need to perform a conversion. For more information, see Customizing for the
Project System under Revenues and Earnings Integration with SD Documents Creating Quotations and Project Billing Static
Processing (Process Before Release 4.5) .

Features
Pricing

The system determines prices for later billing requests based on the quantity and the material by using the pricing procedure. In
collective processing, the billing request is created automatically and cannot be edited. In individual processing, you can process
the billing request in the following two views:

Expenditure View

Sales Price View

For more information, see Pricing.

Use

You can carry out the new resource-related billing for the following objects:

Items of an SD document (such as standard order) with controlling object (this means that costs and revenues are
updated in the SD document

Items of an SD document with relation to a work breakdown structure element from a customer project

Items of an SD document with relation to a production order or internal order

Non-revenue bearing service orders with reference to an SD document item

Revenue-bearing service orders

You use resource-related billing in the Customer Service (CS), Sales and Distribution (SD), and Project System (PS)
components for processing sales orders and service orders.

This is custom documentation. For more information, please visit the SAP Help Portal 2
5/2/2019
For more information about resource-related billing in these components, see:

Billing Process (CS)

Billing Process (PS)

Dynamic Items
De nition
Dynamic items are the data summarized according to de ned criteria, from a project, sales order, or service order. They occur
during quotation creation or sales pricing, and during billing.

Data is summarized - from de ned sources, such as planned cost totals records or actual cost line items - using the dynamic
item processor (DI processor) and is regulated by the settings you enter in the dynamic item processor pro le (DIP pro le).

You maintain the DIP pro le in customizing for Sales and Distribution (SD), Customer Service (CS), or the Project System (PS).

For more information, refer to customizing for SD, CS, or PS.

Component Menu Path in the IMG

SD Sales and Distribution Sales Sales Documents Customer


Service Service Quotation/Resource-Related Billing Pro les
for Resource-Related Billing/Quotation Creation

CS Plant Maintenance and Customer Service Maintenance and


Service Processing Basic Settings Quotation Creation and
Billing for Service Orders Pro les for Quotation Creation,
Billing, Results Analysis.

PS Project System Revenues and Earnings Integration with SD


Documents Creating Quotations and Project Billing Maintain
Pro les for Quotations and Billing

Use
The data is summarized in the following processes using the DI processor, into dynamic items.

Quotation Creation or Sales Pricing

Quotation generation for CS service quotations

PS sales pricing and quotation generation

Billing

Resource-related billing

Flat rate billing with list of expenditures

For information on these processes, see:

Quotation Creation and Sales Pricing

Billing

This is custom documentation. For more information, please visit the SAP Help Portal 3
5/2/2019

Structure
Summarization takes place at two levels:

Level 1

The system summarizes the data records from the stipulated sources. The DIP pro le you maintained in customizing regulates
the type of summarization.

Level 2

The system summarizes the data from the dynamic items on the basis of the materials assigned to the items in a sales and
distribution document (such as a quotation or billing request). The second level of summarization is also dependent on the
settings in the DIP pro le.

The Summarization Process

Activities
Further Settings in Customizing

Function Object Menu Path in the IMG

This is custom documentation. For more information, please visit the SAP Help Portal 4
5/2/2019
De ne default values for DIP pro le Service order Plant Maintenance and Customer Service
Maintenance and Service Processing
Maintenance and Service Orders
Functions and Settings for Order Types
Credit Limit Checks, Sales Document
Types for Service Orders

De ne default values for DIP pro le Sales order by item category Sales and Distribution Sales Sales
Documents Sales Document Item
De ne Item Categories

When you create a sales order, the system


uses the order type and the item category
of the material to nd the item category
that you have stored in a DIP pro le.

Maintain cost element sets for DIP pro le Set General Controlling Pro t Center
Accounting Tools Sets and Variables
Maintain Sets

Further Settings for Resource-Related Billing


Settings for Pricing for Resource-Related Billing

In resource-related billing customers see billing documents from vendors, hotel costs, and so on in the billing. In this case you
cannot de ne a general sales price for service materials which represent these items in the billing request. Even more so, the
price is a result of the incurred costs alone.

Therefore, you cannot ag conditions for these types of prices (for example, PR00) as obligatory in the pricing procedure you
use in pricing for the billing request.

You de ne cost conditions in Customizing for the Project System under Revenues and Earnings Integration with SD
Documents Creating Quotations and Project Billing Assign Cost Conditions to Sales and Distribution Document Types .

Make settings for pricing in the IMG for Sales and Distribution under Basic Functions Pricing Pricing .

De nition of Rejection Reasons for Resource-Related Billing

Rejection reasons are used in resource-related billing to:

Flag items in the billing request as not billable

Defer items in the billing request for later billing request

Cancel items in a billing request if the billing request should be agged as cancelled

You can specify a description for each rejection reason in Customizing. In addition, for each rejection reason you de ne how the
item with this reason should be handled when you create new billing requests in the future.

You can de ne the following rejection reasons, for example:

VN Items not billable

You ag an item with this rejection reason as not billable. The system will no longer suggest it for billing requests you create
later.

You specify the following indicators for the rejection reason:

This is custom documentation. For more information, please visit the SAP Help Portal 5
5/2/2019
Ndr = ʻX’

This means the item is not listed when printed

EPO = ʻ_’

This means the item is considered complete for later billing requests.

FKE = ʻX’

This means the item should not be transferred to the billing document.

STAT = ʻ-’

This means the item value should not be taken into account when you determine the total value of the document.

VB Defer item

You ag an item with this rejection reason as not billable. The system will suggest it for billing requests you create later.

You specify the following indicators for the rejection reason:

Ndr = ʻX’

This means the item is not listed when printed

EPO = ʻX’

This means that the item is still considered open.

FKE = ʻX’

This means the item should not be transferred to the billing document.

STAT = ʻ ’

This means the item value should not be taken into account when you determine the total value of the document.

VS Cancel items

With this rejection reason you can ag an item in a billing request, even if you already created a billing document for the billing
request and cancelled it later.

In this case, however, you can no longer delete the billing request item. If you want to include this item in a different billing
request, you can ag it with this special rejection reason.

You specify the following indicators for the rejection reason:

Ndr = ʻ_’

This means the item is not listed when printed

EPO = ʻX’

This means that the item is still considered open.

FKE = ʻ_’

This means that the item should not be transferred to the billing document

STAT = ʻ ʻ

This means that the item value should not be taken into account when you determine the total value of the document.

This is custom documentation. For more information, please visit the SAP Help Portal 6
5/2/2019

Note

The SAP Standard System does not deliver its own rejection reasons for resource-related billing.

Billing Process (CS)


Purpose
This process describes how you bill a customer for resources (for example, personnel or material) with resource-related billing.
You can implement resource-related billing in Customer Service for various scenarios. For more information see Billing
Scenarios and Quotation Creation Scenarios.

Prerequisites
Customizing

You have maintained a Dynamic Item Processor pro le (DIP pro le).

Service Order

You created one of the following objects:

A revenue-bearing service order

A non-revenue bearing service order in relation to a customer order (for example, a repair order or contract)

You have maintained the following sales data in the service order under Extras Sales Data :

Sales organization

Distribution channel

Division

You have entered a DIP pro le on the Administration tab

You have speci ed a customer

If you want to bill by using service product, you have speci ed a service product and selected the Product characteristic
in the DIP pro le

You have released the service order and entered costs

Sales Document Item

You have created a sales document item (for example, standard order or repair order) that either has a Controlling
object or is assigned to a WBS element from a customer project.

You have assigned a DIP pro le to the item from the sales document for which you want to perform resource-related
billing under Goto Item Sales B.

You have costs to be billed:

Costs were con rmed for the sales document item

This is custom documentation. For more information, please visit the SAP Help Portal 7
5/2/2019
The sales document items is assigned to a production order, internal order, or work breakdown structure element
(WBS element), each of which contains costs

Material

If you want the system to display the planned costs (totals records) in the expenditure view according to material and
quantities, select one of the following indicators when you create a material:

On the Costing 1 tab: Origin of Material indicator

On the Costing 1 tab: With Quantity Structure indicator

Process Flow
1. Go to Customizing and use the DIP pro le to set which data you want the system to bill and how you want the data to be
summarized for the billing request.

2. Create a service order and enter, among others, the DIP pro le.

3. Con rm expenditures (such as work done or materials used) in the service order.

4. Create a billing request.

5. When you opt to create a billing request, the system works as follows:

The system determines the items in the expenditure view using the DIP pro le. These items are identi ed as
dynamic items.

The prices are determined using SD Pricing. The required pricing procedure is determined using the document
category speci ed in the DIP pro le.

There are two views that you can use for processing:

Expenditure view

Sales price view

1. Save the view.

2. Create a billing request in the expenditure view.

3. A billing document is generated in SD.

Related Information
Resource-Related Billing (CS)
Billing Options
Settings: Billing

Resource-Related Billing (CS)


Use
The price for customer-speci c services are not always de ned in a contract as xed prices, nor can they always be determined
using standard pricing. It can happen that empirical values do not exist for speci c service, for example, and therefore the
services cannot be calculated adequately before conclusion of the contract. Typical examples of this are:

This is custom documentation. For more information, please visit the SAP Help Portal 8
5/2/2019
Make-to-order production

External plant maintenance in the service business

Speci c services, such as consulting

In Customer Service (CS) you can bill (resource-related) a customer for resources used (for example, personnel and material)
to carry out services. During resource-related billing, the system creates dynamic items from the expenditure information (for
example, costs for material, utilities, personnel, trips).

There are two views you can use to process the billing request you create before the actual billing document:

Expenditure View

Sales Price View

In collective processing, the billing request is created automatically and cannot be edited.

You can implement resource-related billing in Customer Service for various scenarios. For more information see Billing
Scenarios and Quotation Creation Scenarios.

Fore more information about resource-related billing, see Resource-Related Billing.

Note
Since static billing is no longer available, you must make a conversion if necessary. For more information, see the
Implementation Guide for the Project System under Revenues and Earnings Integration with SD Documents Creating
Quotations and Project Billing Static Processing (Process Before Release 4.5) .

Prerequisites
For information about prerequisites, see Resource-Related Billing Process (CS).

Features
General

You can carry out the new resource-related billing in Customer Service for the following objects:

Non-revenue bearing service orders with reference to an SD document item

Revenue-bearing service orders

Using Service Products

You can use service products and con gurable service products in billing.

If you choose a process with service product, you have the following advantages:

The cumulative nal amount is displayed under the title of the service product in the billing request (for example, bicycle
assembly).

You can display the services agreed upon and described in the service product as subitems in the billing request.

Only the main item is relevant for billing in the at-rate form of billing. The subitems are relevant for billing in the
resource-related form of billing. The scenario from assembly processing is an exception. Here, expenditures are saved

This is custom documentation. For more information, please visit the SAP Help Portal 9
5/2/2019
again as subitems to the sales order item. For more information, see Scenario 4.

You stipulate whether a service product is transferred to the billing request in the Dynamic Item Processor pro le.

If you choose a process without service product, only the incurred costs are displayed in the billing request. The customer no
longer obtains any more information about which service (for example, standard service, service package, or service product)
he or she speci ed in the order.

Special Characteristics

The system does not create any new sales documents from the dynamic items during repairs processing. Instead subitems are
created in repairs processing from the dynamic items. These subitems serve as the basis for creating billing documents.

This is true in the following cases:

For a sales order processing with service items, if you chose at-rate as the form of billing

For a quotation with service product, if you chose at-rate as the form of billing

Accounting Indicator

The accounting indicator is a criterion you can use to differentiate between costs and revenues in service processing. You can
report accrued costs and targeted revenues according to guarantee or grace period, for example.

If you do not want to bill or only partially bill a dynamic item, you can determine a discount based on the accounting indicator. To
do this, a condition type, in whose access must be contained in the sequence the accounting indicator is present, must be
contained in the pricing procedure for pricing (in Customizing for Sales and Distribution under Basic Functions Pricing ). The
dynamic item is displayed with the accounting indicator in the billing request.

You can change the accounting indicator

in the expenditure view.

The changes are valid only for the expenditure view and the billing request. They do not affect the individual document in
Controlling (CO individual document).

Repost

You post a different accounting indicator for the CO individual document created by the system for a con rmation, for
example.

For more information on the accounting indicator, see Accounting Indicator in the Completion Con rmation.

Apportionment Reason

If you do not want to bill a customer for a dynamic item, you can specify the reason (for example, return warranty) in the
overview screen for dynamic items as an apportionment reason. The dynamic item is not displayed on the billing request. The
reason is used internally only, and therefore can be used during results analysis, for example.

Activities

Function Object Menu Path

This is custom documentation. For more information, please visit the SAP Help Portal 10
5/2/2019

Function Object Menu Path

De ne default values for the DIP pro le Service order Plant Maintenance and Customer
Service Maintenance and Service
Processing Maintenance and Service
Orders Functions and Settings for Order
Types Credit Limit Checks, Sales
Document Types for Service Orders

De ne default values for the DIP pro le Sales order using item category Sales and Distribution Sales Sales
Documents Sales Document Item De ne
Item Categories

When you create a sales order, the system


nds the item category you stored in the
DIP pro le by using the order type and
the item group of the material.

Maintain sets for the DIP pro le Set Enterprise Controlling Pro t Center
Accounting Tools Sets and
Variables Maintain Sets

See also
Billing access options

Settings: Sales Pricing and Billing

Billing Scenarios
Use

This scenario describes different scenarios that you can represent in the SAP system for billing. The table provides an overview
of at rate and resource-related billing with dynamic items . You can call up more detailed information for the individual
scenarios:

Object to be Billed Use Features

Service order

Service order The work that was performed, the materials See Scenario 1
that were used, and the additional costs
that arose within the framework of providing
a service are to be billed to the customer.

Resource-related billing can be performed


once the service has been completed, or
periodically in the case of extensive
services that are performed over a long
period of time. No contractual agreements
exist.

Service order A prede ned service product (for example, See Scenario 2
standard service, service package) is sold
to the customer.

This is custom documentation. For more information, please visit the SAP Help Portal 11
5/2/2019

Object to be Billed Use Features

Service order with reference to a sales A contract is drawn up with the customer or See Scenario 3
document item (contract or sales order item a standard service is sold to the customer
from assembly processing) (service package already created in the
system). The service is to be billed to the
customer based on the expenses that have
arisen.

Service order with reference to a sales order A prede ned service product is sold to the See Scenario 4
item from assembly processing customer. A at rate price is de ned for the
service product, or is agreed upon. If
required, you can list the work that has been
performed in the bill.

Sales document

For example, sales order item with internal The customer should be billed within the See Scenario 5
order, production order, etc . framework of production for services that
have been performed, materials that have
been used and so on.

For example, sales order item with cost The customer is to be billed for services See Scenario 6
collector (for example, consultation service at the
service provider’s) that have been
con rmed for a sales document item.

For example, sales order item with WBS The customer should be billed within the See Scenario 7
element (customer project) framework of a customer project for
services that have been performed,
materials that have been used and so on.

Billing - Scenario 1 (CS)


Use
The work that was performed, the materials that were used, and the additional costs that arose within the framework of
providing a service are to be billed to the customer.

Resource-related billing can be performed once the service has been completed, or periodically in the case of extensive services
that are performed over a long period of time. No contractual agreements exist.

Representation in the System


Service order

No billing form, or billing form Resource-related

With or without service product

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Material Service product (if available)

This is custom documentation. For more information, please visit the SAP Help Portal 12
5/2/2019

Hours worked

Graphical Representation

Features
The service order carries revenues and these are posted to the order during billing.

You can copy a service product into the billing request for structuring purposes. You de ne whether it is copied using the
dynamic item processing pro le .

Billing - Scenario 2 (CS)


Use
A prede ned service product (for example, standard service, service package) is sold to the customer.

Representation in the System


Service order

Billing form Flat rate

With service product

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Service product Material

Hours worked

Graphical Representation

This is custom documentation. For more information, please visit the SAP Help Portal 13
5/2/2019

Features
The service order carries revenues and these are posted to the order during billing.

The service product must be copied into the billing request because the at rate is linked to it.

Billing - Scenario 3 (CS)


Use
A contract is drawn up with the customer or a standard service is sold to the customer (whereby the service package has
already been created in the system as a service product). The service is to be billed to the customer based on the expenses that
have arisen.

Representation in the System


Service order with reference to a sales document item (contract or sales order item from assembly processing)

Billing form Resource-related

With service product

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Material Service product

Hours worked

Graphical Representation

This is custom documentation. For more information, please visit the SAP Help Portal 14
5/2/2019

Features
If the service order makes reference to a contract item , it does not carry revenues. The revenues are posted to the
contract item during billing.

If the service order makes reference to a sales order item , it does not carry revenues. The revenues are posted to the
sales order item during billing.

The system copies the service product into the service order and possibly into the billing request (setting in the dynamic
item processor pro le ).

You can bill several items of a sales document together if the service product is not copied into the billing requests.

Billing - Scenario 4 (CS)


Use
A prede ned service product is sold to the customer. A at rate price is de ned for the service product, or is agreed upon. If
required, you can list the work that has been performed in the bill.

Representation in the System


Service order with reference to a sales document item from assembly processing

Billing form Flat rate

With service product

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Service product Material

This is custom documentation. For more information, please visit the SAP Help Portal 15
5/2/2019
Hours worked

Graphical Representation

Features
The service order carries revenues. The revenues are posted to the sales order during billing.

During at rate billing, you can only bill one item. The dynamic items are copied as sub-items into the original sales order.

Billing - Scenario 5 (CS)


Use
The customer should be billed within the framework of production for services that have been performed, materials that have
been used and so on.

Representation in the System


Sales document item (here, a sales order item) with reference to an internal order or production order.

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Material

Hours worked

Graphical Representation

This is custom documentation. For more information, please visit the SAP Help Portal 16
5/2/2019

Features
The revenues are posted to the sales document item during billing.

You can bill several items of a sales document at the same time.

Billing - Scenario 6 (CS)


Use
The customer is to be billed for services (for example, consultation service at the service provider’s) that have been con rmed
for a sales document item.

Representation in the System


Sales document item (here, a sales order item) with cost collector

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Material

Hours worked

Graphical Representation

This is custom documentation. For more information, please visit the SAP Help Portal 17
5/2/2019

Features
The revenues are posted to the sales document item during billing.

You can bill several items of a sales document at the same time.

Reposting the Accounting Indicator


Use
You can use this function to change the accounting indicator that is speci ed, for example, in a completion con rmation.

Instead of canceling the completion con rmation, you can change the accounting indicator for the CO individual document that
the system has created for the completion con rmation. The system posts the CO individual document with the new accounting
indicator.

Note

You can also change the accounting indicator in resource-related billing in the expenditure view . This function is not identical
to reposting the accounting indicator. If you change the accounting indicator in the overview screen, the change only applies
to the overview screen and not to the billing request. It does not affect the CO individual document.

Procedure
You can use this function for a different scenarios. The process ow is described using an example scenario and is also valid for
the other objects for which you can perform resource-related billing.

Scenario:

Quotation for Service Management, without service product, billing form Resource-related

1. Choose Logistics Customer service Service processing Completion Create billing request Repost accounting
indicator.

2. The initial screen for reposting the accounting indicator is displayed.

3. Enter the necessary data and choose Program Execute .

This is custom documentation. For more information, please visit the SAP Help Portal 18
5/2/2019
4. A list of dynamic items is displayed.

5. Change the accounting indicator of the appropriate dynamic item.

6. Save the changes.

Billing Process (PS)


Purpose
You use this process to bill customers for work done, materials used, and other costs incurred in customer projects.

In the SAP system you process customer projects by means of sales order items account assigned to projects. You create a
billing request in a sales order in the Sales and Distribution (SD) component. This means that the resource-related billing
process for customer orders is the same as the process in Sales and Distribution (SD).

Integration
You can only use this component if you also use SD because you need a sales order account assigned to the project before you
can run resource-related billing.

By account assigning one or more order items to a WBS element speci ed as a billing element, you connect the sales order in
SD with the Project System (PS).

The billing element that refers to the sales order item is the highest element in the billing structure. All of the objects that are
subordinate to the billing element in the hierarchy (WBS elements, orders, networks, network elements) belong to this billing
structure.

Prerequisites
Customizing in Sales and Distribution (SD)

This is custom documentation. For more information, please visit the SAP Help Portal 19
5/2/2019
You have created an order item (for example, standard order or repair order) that is account assigned to a WBS element in a
customer project. To do this, de ne the WBS element to be assigned to the order item on the Account Assignment tab page.

You have de ned a Dynamic Item Processor pro le in the order. To do this, enter a Dynamic Item Processor pro le (DIP pro le)
for the order item on the Sales B tab.

In the order item, de ne a material that permits assignment to a project.

For more information, see Customizing for the Project System under Revenues and Earnings Integration with SD
Documents Assign Sales Orders to Project Account .

Customizing in Project System (PS):

You have de ned a Dynamic Item Processor pro le.

Note
If you have maintained the Dynamic Item Processor pro le in a way so that the system takes the actual cost totals records
as the source for the dynamic items, the system does not display the costs according to material.

Other Prerequisites:

The WBS element account assigned to the sales order item carries costs.

Process Flow
Go to Customizing and use the DIP pro le to set which data is to be billed and how the system is to summarize this data for the
billing request.

Con rm expenditures (such as work done or materials used) in the sales order.

Note
You also have the option of differentiating the con rmed costs according to cost element or accounting indicator. For more
information, see Accounting Indicator in the Completion Con rmation and Reposting the Accounting Indicator .

1. Create a billing request.

When you create a billing request, the system works as follows:

a. Starting with the costs, it determines the expenditure basis items using the DIP pro le (see Prerequisites above).
These items are identi ed as dynamic items.

b. The system sorts the dynamic items according to the SD order items and determines the price of the billing
request using SD Pricing.

To this end, it uses the document category (from the DIP pro le) to determine the pricing procedure.

There are two views you can use for processing:

a. Expenditure view

b. Sales price view

2. Save the billing request in a document.

3. The system records the revenues to the project.

This is custom documentation. For more information, please visit the SAP Help Portal 20
5/2/2019

Billing - Scenario 7 (PS)


Use
The customer should be billed within the framework of a customer project for services that have been performed, materials
that have been used and so on.

For more information on resource-related billing in PS, see Resource-Related Billing Process (PS)

Representation in the System


Sales document item (here, a sales order item) with reference to a WBS element.

Relevance for Billing


The table describes which objects are relevant for billing in this scenario.

Relevant for Billing Not Relevant for Billing

Material

Hours worked

Graphical Representation

Features
The revenues are posted to the WBS element during billing.

You can bill several items of a sales document at the same time.

Processing the Expenditure View


Use

This is custom documentation. For more information, please visit the SAP Help Portal 21
5/2/2019
You can edit the items in resource-related billing in the following views:

Expenditure view

Sales Price View

You can switch between the views at any time.

The expenditure view shows the costs from the sales/service order or project, summarized using the DI processor. The
summarized costs - called dynamic items - form the items in the expenditure view.

You use the expenditure view to determine whether the system bills the costs summarized for dynamic items in full, later, or
does not include them in the billing request at all.

The screen for the expenditure view is comprised of an overview tree and a table.

The overview tree shows the hierarchy of SD items per the selected characteristics from the DIP pro le.

The table displays the hierarchy node selected in the overview tree, and the objects subordinate to it (the SD document
items).

Features
The tables below contain information on the processing options:

In the overview tree

In the table

Using the menu bar

Processing Options in the Overview Tree

Function Procedure Result

Hierarchy change in the structure Edit Hierarchy change You can change the hierarchy at any time,
and display the new hierarchy immediately.

These settings override the structuring


setting entered in the DIP pro le for a
characteristic.

Open and close hierarchy nodes Click once. Opening and closing hierarchy nodes gives
you on overview of the dynamic items and
their assignments within the project
structure, or of the sales/service order.

Display detailed information for the objects Double click the symbol in front of the The system displays the detailed
object information.

Choose to return to the expenditure


view.

Display objects in table Double click the object description The hierarchy node and its direct
successors are displayed in the table.

Lock values Set the Locked indicator. You stipulate, for a hierarchy node and/or
the objects subordinate to it, that the
values in the hierarchy node should be sent
to the billing request unchanged.

This is custom documentation. For more information, please visit the SAP Help Portal 22
5/2/2019

Display processing status – To be billed The status symbols show whether and in
what amount the system copies the original
– To be postponed
amount of an item into the billing request.
– Rejected

Processing Options in the Table

Function Procedure Result

Edit values Process the values in the Amount , You stipulate whether the system should
Quantity , or Percent tab page, as take over some, all, or none of the original
appropriate. amount for an item into the billing request.

The symbols in the Status column changes


as appropriate (see table above).

Apportionment Reason

If you do not want to bill a customer for a


dynamic item, you can specify the reason
for this (for example, warranty return) as an
apportionment reason.

The dynamic item is not displayed in the


billing request. The reason is only used
internally and can therefore be used during
results analysis .

Lock values Set the Locked indicator. You stipulate, for a hierarchy node and/or
the objects subordinate to it, that the
values in the hierarchy node should be sent
to the calculation unchanged.

Display detailed information Double click line in table The system displays the detailed
information.

Choose to return to the expenditure


view.

Processing Options Using the Menu Bar

Function Procedure Result

Hide structure tree and display it again Choose . The structure tree is hidden; the table
display is expanded to ll the screen.

Choose again to restore the structure


tree display.

Switch to the sales price view Choose Sales Price . The system displays the sales price view

Save billing request in a document Choose . The system saves the billing request in a
document. You can edit the document later.

Generate billing request Choose Billing Request . You generate a billing request in the Sales
and Distribution (SD) application
component.

See also:

Settings: Sales Pricing and Billing

This is custom documentation. For more information, please visit the SAP Help Portal 23
5/2/2019

Editing the Sales Price View


Use
You can edit the items in resource-related billing in the following views:

Expenditure view

Sales price view

You can switch between the views at any time.

This sales price view shows the items from the expenditure view, sorted and combined per SD items. The prices for the items
are calculated using SD pricing .

In the sales price view, you can edit individual or header items from resource-related billing, with the help of SD conditions . If
you make changes in the header item, the system automatically copies them to the line items.

The screen for the sales price view is comprised of an overview tree and a table.

The overview tree shows the hierarchy of SD items per the selected characteristics from the DIP pro le .

The table displays the hierarchy node selected in the overview tree, and the objects subordinate to it (the SD document
items).

Procedure
The tables below contain information on the processing options:

In the overview tree

In the table

Using the menu bar

Processing Options in the Overview Tree

Function Procedure Result

Open and close hierarchy nodes Click once. Opening and closing hierarchy nodes gives
you on overview of the dynamic items and
their assignments within the project
structure, or of the sales/service order.

Display objects in table Double click the object description The hierarchy node and its direct
successors are displayed in the table.

Processing Options in the Table

Function Procedure Result

Display detailed information Select a line in the table and choose . The system displays detailed information
in a dialog box.

Enter conditions for pricing Use the Condition typ e table column to You choose a condition type and enter the
choose conditions appropriate value. The system updates the

This is custom documentation. For more information, please visit the SAP Help Portal 24
5/2/2019
price automatically.

See also:

Maintaining Conditions

Display condition records Select a condition record and choose The system displays the detailed
Condition Record . information for the selected condition type.

Choose to return to the sales price view.

Update prices Choose Update. You can stipulate that the system updates
all of pricing or only part of it by, for
example, recalculating the rebate
conditions.

See also:

Repeating Pricing

Display pricing log Choose Analysis. The system displays a detailed log of
pricing.

Choose to return to the sales price view.

See also:

Analyzing Pricing and Conditions

Processing Options Using the Menu Bar

Function Procedure Result

Switch to the expenditure view Choose Expenditure. The system displays the expenditure view

Save billing request in a document Choose . The system saves the billing request in a
document. You can edit the document later.

Generate billing request Choose Billing Request . You generate a billing document in the Sales
and Distribution (SD) component.

See also:

Settings: Sales Pricing and Billing

Settings: Sales Pricing and Billing


Features
Choose Extras Settings to access four tab pages where you can enter the settings described below.

You can do the following with your settings:

Store them for the duration of your current processing: choose .

Save them in the database: choose .

If you update the settings to the database, the system automatically accesses them each time you access the sales pricing
again.

This is custom documentation. For more information, please visit the SAP Help Portal 25
5/2/2019
The settings apply to quotation generation or sales pricing and resource-related billing .

General Tab Page

Sales Pricing or Quotation Creation

You can choose between the sales price view or the sales price basis as the initial view for the sales pricing.

To access the view you want, select one of the following in the Create Quotation: Initial Screen or Sales Price Billing: Initial
Screen :

Create new sales pricing

Access sales pricing

If you want the system to display the quotation document for further processing once it has been created (by means of
Create quotation ), select the indicator Show quotation doc. after saving .

If you do not select this indicator, the system simply displays a message, con rming that the quotation has been created.

Resource-Related Billing

You can choose between the sales price view or the expenditure view as the initial view for the sales pricing.

To access the view you want, select in the Create Billing Request: Initial Screen .

If you want the system to display the billing request for further processing once it has been created (by means of
Billing Request ), select the indicator Show billing request after saving .

If you do not select this indicator, the system simply displays a message, con rming that the billing request has been created.

Structure Tree Tab Page

Here, you determine how the two screen areas (table and structure tree) are arranged in the two views.

Sales price basis view/expenditure view

You can show or hide the structure tree at the top of the screen or at the bottom, on the left or on the right. The tree
reproduces the dynamic item hierarchy.

Sales price view

You can show the structure tree at the top of the screen or at the bottom. The tree reproduces the individual SD documents
with main items and subitems.

Sales Price Basis/Expenditure Tab Page

You can choose the currency in which the system displays the sales price basis/expenditure items. You can choose
between controlling area currency, object currency, and transaction currency. This setting does not affect the currency
transferred to the quotation/billing request.

The system usually transfers the transaction currency, unless the Transaction currency eld is not lled. In this event, the
controlling area currency is transferred. This happens if the All currencies eld is not selected (in cost accounting customizing,
under Controlling General Controlling Maintain Controlling Area ) .

This is custom documentation. For more information, please visit the SAP Help Portal 26
5/2/2019
If you select the indicator Only dynamic items will accept input , it will only be possible to enter values for the dynamic
items.

Selecting the Block in manual input indicator ensures that values changed manually can be overwritten.

The following indicator can only be found in Resource-Related Billing:

With the indicator Only display open items, you de ne that the system only displays the dynamic items whose total
amount has not yet been fully transferred to a billing request. (The value in the column Open amount is not 0).

If the indicator has not been set, then all dynamic items are displayed.

Description Tab Page

The system only draws on this tab page in the sales price basis view/expenditure view.

You use this tab page to stipulate how the dynamic items , objects, and the selected characteristics are labeled in the structure
tree and table.

You can use any combination of posting period, material number, and material description as the description in a
dynamic item.

You can use the short or long description of an object as its description in the DIP.

You can use an abbreviation and/or the short/long description of a characteristic as the label for that characteristic.

Note

This tab page is the header for a variable number of subordinate tab pages. The number of tab pages depends on whether
you have maintained the activity type, cost element, cost center type, and statistical key gures as structuring
characteristics in the DIP pro le.

The system displays one tab page for each of these structuring characteristics. In addition to the optional tab pages, the
system always displays the Dynamic Items and Object tab pages.

Activities
Depending on which component and process you are using, choose one of the following menu paths:

Sales Pricing or Quotation Creation

Components Menu Path

CS Logistics Customer Service Service Processing Order


Service Order Create Quotation

Project System (PS) Logistics or Accounting Project


System Financials Planning Sales Pricing.

Resource-Related Billing

Components Menu Path

SD Logistics Sales and Distribution Sales Order Subsequent


Functions Resource-Related Billing Document

This is custom documentation. For more information, please visit the SAP Help Portal 27
5/2/2019
CS Logistics Customer Service Service Processing Completion
Create Billing Request Individual Processing.

Project System (PS) Logistics Sales and Distribution Sales Order Subsequent
Functions Resource-Related Billing Document

Choose Extras Settings …

The Settings dialog box appears.

Select the tab page indicators described above as required.

Choose to save the settings for the duration of your processing work.

Choose to save the data in the database.

Billing Options
Use
You use resource-related billing to calculate the price for a sales/service order or customer project on a resource-related basis,
and save the result in a billing request.

Prerequisites
For information on the prerequisites, see:

Billing Process (CS)

Billing Process (PS)

Billing in SD follows the same procedure as billing in PS.

Procedure
1. Choose the appropriate menu path:

2. Component Menu Path Resulting Screen

CS Logistics Customer Service Service Resource-Related Billing Request:


Processing Completion Create Billing Initial Screen
Request Individual Processing.

PS Logistics Sales and Resource-Related Billing Request:


Distribution Sales Order Subsequent Initial Screen
Functions Resource-Related Billing
Document.

SD Logistics Sales and Resource-Related Billing Request:


Distribution Sales Order Subsequent Initial Screen
Functions Resource-Related Billing
Document.

3. Enter data as required.

This is custom documentation. For more information, please visit the SAP Help Portal 28
5/2/2019
4. If necessary, overwrite the pricing date defaulted by the system (today's date). The date you enter applies to all items in
the billing request.

5. If you want to use your own settings for sales pricing, choose Extras Settings…

6. Here, for example, you can determine how the screen areas are divided or stipulate to which of the two processing views
you want to jump when you access a resource-related billing again.

For more information on the settings, see Settings: Sales Pricing and Billing .

7. Once you have chosen your selection criteria and decided on settings, the following additional options for further
processing are available:

Pushbutton Function

Expenditure This view shows the costs from the sales/service order or project
billing structure, summarized using the DI processor . The
summarized costs form the items in the expenditure view.

You can use this view to edit the items in resource-related billing
and transfer some, all, or none of them to the billing request.

For more information, see Editing the Expenditure View .

Sales price This view shows the items from the expenditure view, sorted and
combined per SD items. The prices for the items are calculated
using SD pricing.

In the sales price view, you can edit individual or header items from
resource-related billing, with the help of SD conditions.

For more information, see Editing the Sales Price View .

Create billing request The system carries out resource-related billing and creates a billing
request.

If you chose Extras Settings … and selected Show billing request


after saving on the General tab page, the system creates the
billing request and jumps to the change mode for it.

If you did not select the indicator, a message appears in the status
line, telling you that the billing request was created successfully.

For more information, see Creating Billing Requests .

Access billing request The system accesses an existing billing request.

If more than one billing request exists, the system asks you to
choose one.

Depending on the settings you entered under Extras Settings , you


then branch to the expenditure view or the sales price view.

Billing Request Editor


Use
In many professional service rms time and expenses as well as other transactions are captured during the duration of an
engagement. At the time of billing these detailed transactions are reviewed to ensure completeness and to adjust mis-postings.

Professional Service Firms have quite a diverse way to bill their customers, from situation where everything is agreed at time of
contract closure to mixed scenarios, where parts of the delivery are subject to a xed price and other add-on work might be

This is custom documentation. For more information, please visit the SAP Help Portal 29
5/2/2019
charged separately to time and material based billing. Also, the detail of the bill differs a lot from very high level summarized
bills to bills where each single posting is revealed to the customer.

In resource related billing (RRB), postings can be aggregated to so called dynamic line items (DLI) and then further being
aggregated to individual positions on a debit memo request (DMR line). Therefore a exible solution was developed that allows
balancing the level of details required and the exibility in bill generation.

The basic idea of the Billing Request Editor is to create a resource related debit memo request rst using the already existing
functionality. The user would not need to do any decision in this initial step. The DMR is then used as basis for all further
processing.

Implementation Considerations
Billing Request Editor can be used if you are using RRB and have business requirements as mentioned above. The Billing
Request Editor changes the DMR created in resource related billing process and therefore is strongly integrated with the DMR,
especially in regards to reasons for rejection, pricing procedure and pricing conditions, texts on line item.

Integration
Billing Request Editor is an additional optional step during processing of RRB. It is executed after creation of the resource
related DMR and prior to billing the resource related DMR.

Using the Billing Request Editor


Use
This process is used to create a resource related debit memo request (DMR) .The DMR is then used as a basis for all further
processing.

Process
Following are the process steps:

1. In the Initial screen the user enters a DMR number to review and adjust so that it can be billed.

The usual checks for authorization are executed, as well as checks if this DMR is already billed, fully rejected or if it is not
a resource related DMR at all.

System then retrieves from the DMR and DLI the details and presents the data on maximum DLI level for WIP review
and selection

2. In the WIP Selection screen the WIP is reviewed or either aggregated on a very detailed level.

The user can decide not to bill certain percentage or value of the WIP and move these portions back into the WIP, where
it is available for subsequent bills.

The grouping section allows the user to aggregate the DLI based on DLI characteristics and can be defaulted. For
example aggregate the values by period and employee.

The user can then maintain the WIP Selection screen if parts of them have to be postponed. This can be done
based on a value basis or a percentage basis. Traffic light then changes to yellow (partially billed) or red
(completely returned to WIP). Postponed bill items will be moved back to WIP.

Metric section shows the impact of previous and current decision.

This is custom documentation. For more information, please visit the SAP Help Portal 30
5/2/2019
The user can then re-group and do additional postponements or can move on to the accrual screen.

Note
Data can be exported to excel at this stage. In case items are missing (late time sheets, missing invoices) the user
has the option to add these into the DMR in the next step.

3. In the Accrual screen, the user can to add accruals for example for missing time sheets or missing invoices. The available
categories for accruals are de ned in customizing and the user can only select from these categories.

Enter the following mandatory elds for each accrual:

Category, description and value

For some accrual types, quantity can be made mandatory.

Further elds are available to capture additional characteristics. The usage of these depends on the value screen.

If the user wants to group the accruals together with original entries, then the characteristics have to be
captured as well, otherwise the system does not know what belongs together.

Note
Accruals are not mandatory. If nished or no accruals are needed the user can proceed to the value screen

4. In the Value screen, the user can group the items and review the valuation as defaulted through pricing, on the basis of
the DMR lines after the postponement and the accruals are added. These are the initial values, for which the user can
then adjust the pricing.

The user can group the DMR lines in this screen to make the pricing decision easier. The grouping works with the same
handling as described above for the WIP selection. But here there are fewer characteristics available as the work here is
on the DMR level and not on the DLI level. Default values are controlled per customizing.

The grouped DMR items are presented to user with original value and quantity and the user can then change the rate or
the value for this grouping.

There are some exceptions to be considered:

Quantity and rate is shown only if all items grouped have a quantity and a rate

If quantity and rate is not shown it cannot be changed

There are certain categories of DMR lines, which are marked in customizing as not changeable.

From here there are three basic ways to proceed:

The grouping last used is how the bill items should appear on the invoice.

The invoice is freely de ned use the free form option

There is a customer de ned option, which lls defaults to next screen based on customer logic (see BAdI
BADI_PRS_BUSINESS).

5. In the Billing screen, the nal bill presentation is de ned. There are several different options supported as the
differences here are quite big between different billing scenarios. There are options provided to default everything and
only allow the user to change the texts. To options where the user can change the grouping (that is, in one case the bill is
presented by period in next case the bill is presented by period and employee) to the option where the bill is prepared
completely using the free form.

The Metrics section shows the usable components and the metrics.

In the Bill Items section the items are shown (where the text can be either opened or collapsed).

This is custom documentation. For more information, please visit the SAP Help Portal 31
5/2/2019
In case copy over lines are defaulted with each group available in the value screen. These items need to be kept in
synchronization between the two screens, so in Value screen the user can change the value on such items and in the
Billing screen the user can only change the texts.

If the user changes the grouping in the Value screen after going to the Billing screen then a warning is displayed and if
the user proceeds, then the copied items will be deleted from the Billing screen.

6. On saving the DMR is updated. The changes executed are:

Reject DMR if they were completely postponed in WIP selection screen

Change quantity/value in EK01 on DMR line, if they were partially postponed in WIP selection screen, update
AD01DLI tables as well

Postponement is always done in a way that the system tries to bill the old items fully and only bills the newest
items partially.

Note
This is different to DP90, where all items would be partially postponed

Accrual lines are added to DMR and accrual lines are priced

Value on original DMR lines is changed (details below)

Additional lines for all items shown in the billing screen are added with text and value.

Result
A DMR is updated with regards to quantity, price being billed. Additional items are created on DMR, Texts are maintained and
DLIs are moved back to WIP.

Start Delete Job for Additional Data


Use
This report is used to select data to be deleted by the sales organization of a DMR, by DMR number (number range) and by
DMR status (complete or alternatively subsequent DM being paid).

Features
This is a stand-alone report. The idea is that the report is run after archiving of the VBAK / VBAP tables belonging to the SD.
The report deletes the data from the new tables. All the entries will be deleted from the table which do not have the
corresponding entries in VBAK / VBAP any more (because of the archiving). The purpose of this is to speed up the operation by
deleting data that are not required after an archiving.

Note
The user must have appropriate authorization to run the report.

Activities
The start screen triggers a batch program, which deletes the history data stored with reference to the DMR. Depending
on the start parameter the system checks if: The DMR status is complete (VBAK status) or alternatively the subsequent

This is custom documentation. For more information, please visit the SAP Help Portal 32
5/2/2019
DM is fully paid.

The user can select one of the options on the screen and a DMR number range and a sales organization. At execution
program, will seek through the DMR and determine, if the above conditions are met. If the conditions are met, history
data is removed/deleted.

Billing Request
Use

The billing request is a document containing the expenditures to be billed. These expenditures appear as items in the billing
request.

You can create a billing request for:

Sales orders

Customer projects

Service orders without reference to a sales order

The hierarchical structure of the objects evaluated for a sales order item (internal orders and service orders) in a sales order;
WBS elements, activities, internal orders and service orders for customer projects) create the billing structure.

Creating Billing Requests


Use
You can use this function to create the billing request for a sales/service order or a customer project.

The following is the procedure for the individual processing. If you want to transfer the data directly from the system into the
billing request, you can also use the collective processing transactions in the following table:

Component Menu Path

Customer Service (CS) Logistics Customer Service Service


Processing Completion Billing Request Collective Processing
(DP95) or Collective Processing – Service (DP97)

Sales and Distribution (SD) Logistics Sales and Distribution Sales Order Subsequent
Functions Resource-Related Billing Document (Collective
Processing) (DP96)

Project System (PS) Logistics Sales and Distribution Sales Order Subsequent
Functions Resource-Related Billing Document (Collective
Processing) (DP96)

Transactions DP96 and DP97 use the logical database of Sales and Distribution or of Maintenance for the selection of the data.
The output corresponds to collective processing DP95. The system issues an event log. All collective processings can also be
executed in the background.

For more information, see Resource-Related Billing.

Prerequisites
This is custom documentation. For more information, please visit the SAP Help Portal 33
5/2/2019
For more information about the prerequisites, refer to

Billing Process (CS)

Billing Process (PS)

Procedure
Choose one of the following menu paths:

Component Menu Path

Customer Service (CS) Logistics Customer Service Service


Processing Completion Billing Request Individual Processing

Sales and Distribution (SD) Logistics Sales and Distribution Sales Order Subsequent
Functions Resource-Related Billing Document

Project System (PS) Logistics Sales and Distribution Sales Order Subsequent
Functions Resource-Related Billing Document

The system displays the Resource-Related Billing Request: Initial Screen.

Specify the sales order or service order for which you want to create a billing request. If you want the billing request only to
cover particular items from the order, specify the items.

To display the billing request for further processing, choose Extras Settings and select Show billing request after save on the
General tab page.

For more information about the prerequisites, refer to Settings: Sales Pricing and Billing.

You can create the billing request in one of the following ways:

To copy data to the billing request directly from the system, choose Billing Request.

The system generates a billing request for the sales/service order.

If you want to edit the data from the system copied to the billing request, choose one of the processing views.

For more information about this, see

Processing the Expenditure View

Editing the Sales Price View

If you did not select the Show billing request after save indicator, a message appears in the status line, telling you that the
billing request was created successfully.

If you did select the Show billing request after save indicator, the system displays the Change Billing Request:Overview screen.

Result
The system uses the DI processor to summarize the costs from the sales/service order into dynamic items. When valuating the
dynamic items, the system takes account of the conditions and prices de ned in the component Sales and Distribution (SD).

This is custom documentation. For more information, please visit the SAP Help Portal 34
5/2/2019
The currency for the individual items in the dynamic item processor is taken over from the CO document (object currency) or
customer master record (transaction currency).

Choose Extras Settings to stipulate which currency (controlling area currency, object currency, or transaction currency) is
relevant for the individual items.

Changing Billing Requests


1. Choose Logistics Sales and Distribution Sales Order Change .

2. The Change Sales Order: Initial Screen appears.

3. Enter the billing request number in the Order eld, then choose an overview.

4. The Change Sales Order: Overview screen appears.

5. Process the items as you wish.

6. Choose to save the changes.

Canceling a Billing Request


Use
You must cancel a billing request if the items in it are not to be billed or if they should be made available for a new billing request
to be created.

For technical reasons, cancellation is not possible. However, you can provide the items with a reason for rejection. These items
are not taken into account for the current billing, and are available for the next billing if they have an appropriate reason for
rejection. This means that if you "cancel" values from a dynamic item , which have been billed already (for example, amount or
quantity), then these values are displayed in the To be billed column in the expenditure view the next time you bill.

Activities
You can de ne the reasons for rejection in Customizing for Sales and Distribution under Sales Sales Documents Sales
Document Item De ne Reasons for Rejection (see also System Settings ).

Billing Between Company Codes


Purpose
In the service branch it is common that employees belonging to one company code sometimes work for other company codes.
Often one company code (the requesting company code such as a particular international subsidiary) of an enterprise carries
out a project in conjunction with external customers, and uses employees from other company codes (the supplying company
codes). In order to distribute the project revenues accrued in your company code according to expenditure fairly, you are billed
for the expenditures of employees belonging to other company codes. These expenditures are collected for all employees
working on a project and you can bill them internally for cost unit rates or any sales prices. All project participants con rm their
expenditures for the same project.

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 35
5/2/2019
You carried out the steps for con guration.For more information, see Con guration .

Process Flow
The process for billing between company codes (resource-related internal billing) is described below. This type of billing is based
on the dynamic item processor(DIP), which is also used for resource-related billing of customers. For more information, see
resource-related billing .

The following example uses a supplying company code only and a project as an account assignment object.

Note
In the supplying company code you can use all objects with order characteristics as account assignment objects, such as
sales orders, WBS elements, network headers, network activities, and service orders .

You can also use cost centers as account assignment objects if you have implemented BAdI: Resource-Related Billing
Between Company Codes in Customizing for Sales and Distribution under Billing Intercompany Billing Resource-Related
Intercompany Billing.

The steps described below correspond to the process depicted in the graphic.

1. The supplying company code creates an internal sales order once, or once a year for example, in which the internal
customer represents the requesting company code.

2. The requesting company code creates a project with its (external) customer. Contract agreements in the form of a real
sales order lie with the requesting company code.
This is custom documentation. For more information, please visit the SAP Help Portal 36
5/2/2019
3. An employee from the supplying company code provides services for the project and reports his or her time directly.
Actual costs (such as travel costs or expenditures) are posted on a corresponding account assignment in the supplying
company code.They are later reposted to the project through CO-reposting in transactions KB11N or KB15N. For more
information, see SAP Note 1463819.

4. In the supplying company code, the functions for billing between company codes identify those time and travel expense
con rmations that exceed the company code boundaries between the supplying and requesting company code. The
system processes line items such as in resource-related billing summarized dynamically, structured, and evaluated. The
system generates an internal billing request.

For more information about this function, see Single Processing .

5. The internal billing and invoicing steps are as follows:

a. In the supplying company code the internal billing document is created based on the internal billing request. It
might then be sent to the requesting company code using the SAP Electronic Data Interchange(SAP-EDI) .

b. In this way, internal revenues are posted on the side of the supplying company code. These internal revenues
balance the employee’s time and travel expenses in this company code. As a rule, revenue surplus is attained,
which balances out the fact that the supplying company code did not use its employees for one single customer
project.

c. In the requesting company code, the system posts the incoming invoice in Financial Accounting.

d. Internal expenditures are posted on the side of the requesting company code. Account assignment in Controlling
is super uous, as a rule, since the actual costs were already account assigned.

6. The requesting company code creates a customer billing document and thereby creates revenues for services as well,
which were provided by the employee from the supplying company code. The requesting company code must not wait for
the incoming invoice, but rather it can create its billing document immediately after time or travel expenses have been
entered by the employee. The requesting company code hereby creates external revenues. A portion of these revenues
must be used to compensate the internal expenditures.

Caution
Within your organization, ensure billing between company codes occurs as soon as the period ends, and before other
period-end processes are carried out. If there is a large amount of data to be processed, billing between company
codes should occur several times during this period.

Alternative Process

If you do not want to use the process described above, you can use the business process described below. Here, the employees
of the supplying company code con rm their time or travel expenses for a sales order, and the employees of the requesting
company code con rm theirs for a project, even though both work for the same project. You must create a purchase order (and
a sales order) for each project belonging to the supplying company code.

1. The requesting company code creates a purchase order for the supplying company code.

2. The supplying company code creates a sales order for the purchase order.

3. The employee belonging to the supplying company code who works on the project, con rms his or her time and travel
expenses for the sales order.

4. The supplying company code bills the sales order to the requesting company code, whereby incurred costs are account
assigned at invoice receipt to the project of the requesting company code.

5. The project costs are billed to the customer belonging to the requesting company code.

Result
This is custom documentation. For more information, please visit the SAP Help Portal 37
5/2/2019
You billed for services provided for other company codes. The revenues you attained from external customers are divided
among all participating company codes.

Con guration
Before you can use the process for billing between company codes, you must complete the con guration. For more information
about the process, see Billing Between Company Codes

To make the settings for con guration, follow the steps described below:

1. Create an internal customer (transaction XD01 )in the supplying company code to represent the requesting company
code.

2. Assign any sales organization of the requesting company code to the internal customer. In Customizing for Sales and
Distribution , choose Billing Intercompany Billing De ne Internal Sales Number by Sales Organization .

Recommendation
We recommend that you assign the internal customer to exactly one sales organization of the company code.
Nevertheless, the internal customer represents the entire requesting company code.

3. If you use the Reconciliation Ledger or New GL with Real-Time Integration, then de ne clearing accounts and alternative
reconciliation accounts for cross-company Controlling transactions using the resource-related intercompany billing
(RRICB) process. In Customizing for Sales and Distribution , under Billing > Intercompany Billing > Resource-Related
Intercompany Billing you can maintain settings in the following activities:

a. Maintain Clearing Accounts for Company Codes

Caution
For company code combinations using billing between company codes, you must enter P&L accounts for credit and
debit postings for both company codes and you must set the activation ag. B oth company codes have to belong to
the same controlling area and the P&L accounts must not be created as cost elements.

Note
These clearing accounts are taken only for cross-company Controlling transactions between company codes entered
in this activity. This is to ensure that no double postings occur in Financial Accounting within this process.

Maintain Optional Account Determination

Note
Optionally, you can maintain alternative reconciliation accounts.

These alternative reconciliation accounts are taken only for cross-company Controlling transactions between
company codes entered in the activity Maintain Clearing Accounts for Company Codes . If no reconciliation account
can be determined, the account determination is used.

4. Set up material determination and pricing in the supplying company code as you require for billing from the supplying to
the requesting company code.

5. Set up a dynamic item process pro le(DIP pro le) with the new source Intercompany – Line Items . In Customizing for
Sales and Distribution , choose Sales Sales Documents Customer Service Service Quotation/Resource-Related
Billing Pro les for Resource-Related Billing/Quotation Creation. For more information, see Resource-Related Billing .

This is custom documentation. For more information, please visit the SAP Help Portal 38
5/2/2019

Note
To ensure this information is available in the accounting documents and incoming invoice, you can set Business Area ,
Partner Business Area , Pro t Center , and Partner Pro t Center as relevant and choose No Summarization . Do not
change Pro t Center , or Partner Pro t Center during this period, as this must be done at the beginning of the period
when no postings to objects already exist.

To have these elds included in the accounting documents, you must implement SAP Note 1511354. After that you
must use a speci c sales order type for the internal sales order and a speci c item category for the item in step 6
as described in the SAP Note.

6. Create an internal sales order with an item in the supplying company code for each requesting company code, and assign
the DIP pro le you created above to the item. You can use this internal sales order at any time. Alternatively, you can use
contracts (transaction VA41 ) instead of sales orders (transaction VA01 ).

Caution
Ensure organizationally, that there is only one internal sales order at this point in time between the supplying and
requesting company codes.

Note
Carry out the following activities only if you want to send the billing document from the supplying company code to
the requesting company code using the SAP Electronic Data Interchange(SAP-EDI) and post it there electronically.

Set up EDI processing. For more information, see SAP Note 31126 or Customizing for Sales and Distribution
under Billing Intercompany Billing Automatic Posting to Supplier Account (SAP-EDI).

Make the settings for invoice receipt, if necessary. For more information see the Customizing for Financial
Accounting under Accounts Receivable and Accounts Payable Business Transactions Incoming
Invoices/Credit Memos EDI .

Single Processing
Use
Using this function you can bill between company codes (resource-related internal billing). To call this function, choose the
following path from the SAP Easy Access Menu : Logistics Sales and Distribution Sales Order Subsequent Functions Billing
Between Company Codes.

Integration
The function reads cross-company code line items from SAP Controlling, for example, costs or quantities con rmed in the
Cross-Application Time Sheet ( CATS ). The system takes all objects with order characteristics into consideration, for example,
sales orders, WBS elements, network headers, network activities, service orders, and cost centers.

Prerequisites
You carried out the steps described under Con guration .

To enable you to work with cost centers, you have implemented BAdI: Resource-Related Billing Between Company Codes in
Customizing for Sales and Distribution under Billing Intercompany Billing Resource-Related Intercompany Billing.

This is custom documentation. For more information, please visit the SAP Help Portal 39
5/2/2019

Features
This function uses the Dynamic Item Processor(see Resource-Related Billing ). The system proceeds as follows:

1. The system determines the requesting and supplying company code in the intercompany sales document.

2. The system reads all line items for combining both company codes from one period and one scal year. Once you enter
the additional selection criteria, the system takes these into account as well.

3. The system summarizes the line items and determines materials and prices. You can adjust the result manually (see also
Processing the Expenditure View and Editing the Sales Price View ).

4. Based on these values you can create a billing request .

Activities
Enter the following data in the initial access screen for Billing Between Company Codes :

Internal sales order of the supplying company code

Period

Fiscal year

Optionally, you can de ne the account assignment objects to be selected in the requesting company code.

Note
Note that you can enter sales documents or service orders or project objects (project de nitions, WBS elements,
networks/orders) or cost centers.

Collective Processing
Use
Youuse this function to process several intercompany sales documents together.To call the transaction, choose the following
path from the SAP Easy Access Menu : Logistics Sales and Distribution Sales Order Subsequent Functions Billing Between
Company Codes (Collective Processing) .

To do so, you must rst enter the Intercompany Sales Documents of the supplying company codes in the selection screen for
Resource-Related Billing Between Company Codes: Collective Processing .

Note
Note

The intercompany sales documents can belong to different Controlling areas. For more information, see Billing Between
Company Codes .

Prerequisites
To enable you to work with cost centers, you have implemented BAdI: Resource-Related Billing Between Company Codes in
Customizing for Sales and Distribution under Billing Intercompany Billing Resource-Related Intercompany Billing .

This is custom documentation. For more information, please visit the SAP Help Portal 40
5/2/2019

Features
In the Optional Selection Parameters area , to reduce the number of objects to which costs are selected, you can de ne the
account assignment objects to be selected in the requesting company code. Account assignment objects include sales orders,
orders, or objects belonging to projects, such as WBS elements.

You can process objects to one project at one time and then process objects to another project at another time.

Note
Note

You can enter sales documents, or service orders, or project objects (project de nitions, WBS elements, networks/orders),
or cost centers .

In the Source area, you determine which Period , Fiscal Year and Posting Date To the system uses during processing. To do this,
you must choose one of the following radio buttons:

Period to Current Date : If you choose this radio button and execute billing, the system selects all the corresponding
objects’ costs for the period and scal year combination of the current date period. The system automatically sets the
Posting Date To parameter to the last day of the period during billing.

Previous Period to Current Date : If you choose this radio button, the system selects the corresponding objects’ costs for
the period and scal year combination before the current date period. The system automatically sets the Posting Date
To parameter to the last day of the previous period during billing.

Period from Selection Screen : If you choose this radio button, the system uses the values you entered in the Period eld,
Fiscal Year eld, and the Posting Date To eld in the selection screen. For this option only, the values in selection screen
in uence the process.

Note
Note

The value in the Posting Date To eld must belong to the period and scal year combination entered in the selection
screen.

If you select the Process Open Items Only checkbox, the system processes only the dynamic items that have not beenfully
billed. If you do not select this indicator the system processes all dynamic items.

In the Further Options area, you can select the Saved data checkbox to determine whether the system should use saved data
for the objects to be billed. You can select the Refresh checkbox to specify whether the system should refresh the saved data for
the objects to be billed: The system reads the saved data rst, and subsequently rereads the cost records to the objects. You
can select the Refresh checkbox only if you have selected the Saved data checkbox. Additionally, you can enter a Pricing date if
you want to determine the prices for all items as of the same date.

In the Save Options area, you can decide if the system saves an extract or creates a debit memo request or a credit memo
request.

Save extract : If you select this checkbox, the system executes the billing between company codes as for Save sales
document but instead of creating a debit memo request and/or a credit memo request, the system writes the result
that is produced during processing to the database. You can reuse the data for another run with or without refreshing it.

Save sales document : If you select this checkbox, the system creates a debit memo request and/or a credit memo
request in case there are amounts or quantities to be billed.

This is custom documentation. For more information, please visit the SAP Help Portal 41
5/2/2019
In the Processing Options area, you can select the Test Run checkbox to specify that an extract or sales document is created.
You can select the Background Processing checkbox to specify that billing is carried out in the background. You can select the
Detail List checkbox to specify that the system shows additional information to processes carried out (for example, error
messages).

Integration of the Billing Plan and the


Resource-Related Billing Document
Use
With this function you can integrate the resource-related billing document into the milestone billing plan (milestone billing). The
following table shows which business processes are affected by the new function: The business process is depicted in the billing
plan as follows:

When you de ne the date type, you de ne whether the date is a down payment date or a planned billing date.

If necessary, enter a billing document value for this date.

For more information, see Billing Plan and Milestone Billing.

Business Process Execution of Down Payment Requests Execution of Milestone Billing and
Contract Billing

Set down payments and resource-related In a set amount using transaction VF01 Resource-related using transaction
billing documents DP90/DP91

Down payments and resource-related billing Resource-related using transaction Resource-related using transaction
documents DP90/DP91 DP90/DP91

Down payments and set resource-related Resource-related using transaction Using a set amount set in transaction VF01
billing documents DP90/DP91

Only resource-related billing documents Not relevant Resource-related using transaction


DP90/DP91

Note
It is also possible to specify a billing document value in the billing plan date for all business processes. The system transfers
this value as the header condition in the document to be created. This then causes system to bill for the billing document
value.

Integration
The billing plan is integrated in the project with milestones .

The following are not supported:

Integration with periodic billing plans

Repair orders

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 42
5/2/2019
You activated integration of the billing plan and resource-related billing document in Customizing for the Project System
for the DIP pro les used in the process (see Revenues and Earnings Integration with SD Documents Creating
Quotations and Project Billing Con gure Integration of Billing Plan and Resource-Related Billing Doc.) .

If you use header conditions, you must make settings in the following activity for Customizing for the Project System:
Revenues and Earnings Integration with SD Documents Creating Quotations and Project Billing De ne Condition Type
for Fixed Price in Billing Plan .

You can create down payment requests and billing requests only if the dates in the billing plan have been released. The
dates are released manually or automatically once the corresponding milestone in the network are con rmed as
completed.

Features
You can allocate received down payments to the billing plan not only with xed billing documents, but also with billing
documents that were created using resource-related billing. The resource-related billing document creates down payment
requests (sales) and billing requests based on expenditures not yet billed.

Even if sales documents with items were created according to expenditures, you can prevent the individual expenditures from
being printed when you print the billing document by using message control.

Activities
1. Create a sales order (transaction VA01) or contract (transaction VA41) with a billing plan on item level.

a. Enter billing plan dates for down payments and billing documents for each item depending upon the business
process.

b. Enter a DIP pro le for each item for which integration with the billing plan is active.

2. Once you have released a data, you can create a down payment or a billing document using the transactions
DP90/DP91 and VF01, independent of the date type, and depending upon the business process.

Note
It is not possible to edit items with different date types together. You must edit these items individually.

You can create down payments (sales) and billing requests only if expenditures exist for the items.

You can edit an item in collective processing only if exactly one date has been released in the billing plan.

This is custom documentation. For more information, please visit the SAP Help Portal 43