1. Objective and Scope

1.1 Objective of this Operation

At the end of this procedure, you will be able to create the sale invoice, starting from the data acquisition, carrying out a new billing data determination in some cases and ending by the sale invoice creation.

1.2 Scope

WW scope 

2. Definitions

See Finance Glossary:

• WBS

3. Billing creation

Cost based revenue - Posting schema

Main services invoicing posting schema:

Cost based revenue (main case):

Revenue determination based on costs:

• At Costs

• Costs + (mark-up)

• Price according to the quantity

Engineering, maintenance, R&I, CBS services, expatriate costs

3.1. I transfer the amount based on cost based to be invoiced to the WBS, in case of need

Go to KB15N transaction and create a manual allocation

1 → Enter the document date and the posting data: Mandatory;

2 → Enter a document header text: Optional (Can be used in the invoice text);

3 → Chose the screen variant: Define which fields are available in the document item screen;

4 → Enter financial data: Cost element/Amount/Transaction currency/Quantity/Unit of measure;

5 → Enter a document item text: Optional (Can be used in the invoice text);

6 → Enter the sender cost object: In service billing process it is the service provider cost center or the cost center to which the costs to invoice are posted;

7 → Enter the billing WBS element: In the services invoicing process the receiver object is always the billing WBS element

3.2. I perform the billing data acquisition

3.2.1. I Perform the data acquisition and the billing data determination

Notice that step is an automatic step even if it is still possible to perform it at any time for immediate invoicing for instance

 Key transaction Z1F_CRC_DATA_ENRICH Data acquisition, enrichment

1→ Project or WBS selection: Same selection possibility as from any project reporting transaction (CIJ3, CJIC). Optional

• By project
• By WBS
• Using data from the project and/or WBS (dynamic selection)

2→ Posting date: Always from the first day of the previous month to the last day of current calendar month

3 → Greyed out parameters:

• Dr/Cr indicator
• Filter of credit from settlement
• Reference transaction (VBRK)
• Filter items from sale invoice
• Document type and cost element
• Filter revenue recognition posting
• Invoicing calendar
• Default calendar if no one is found

4 → ALV layout variant

Then execute the transaction.

1→ Reference of the CO document to be invoiced

2→ Billing data determination

 Such as (main ones):

• Value in both Transaction and Obj curr
• Cost element
• Partner CO acct assignment
• Customer
• Material
• Activity (OECD)
• …

 3→ Log

•  Number of new CO documents extracted
• Number of billing data records (should be equal to the number of CO doc.)
• Number of text records should be equal to number of CO doc
• No of incomplete data (enrichment records)  should be 0

4→ Incomplete enrichment: show line items with incompletion status (cannot be invoiced). Correction and new billing data determination is required

Key transaction Z1F_CRC_NEW_ENRICH New line items enrichment

 - this step needs to be done whenever a change/correction is made in the billings WBS master data level after the first enrichment is done

1→ First option: Items without enrichment ID (only)

2→ Second option: All other items not yet invoiced. Most of time after a change that has an impact on the billing date (invoicing currency for instance)

3→ Project management selections: Filter according to project data

4→ Document selections: Filter according to  financial data so at CO document level

5→ ALV Layout variant

Then execute the transaction.

2→ Text data enrichment: Perform a new text determination (only)

3→ New enrichment ALL: Perform a complete new billing data determination (text and sale data)

4→ Display text data: Display text of the line item selected

5→ Incomplete Enrich. data: Show line items with incompletion status (cannot be invoiced). Correction and new billing data determination is required

3.2.2 I Create the sale invoice

Notice that step is an automatic step even if it is still possible to perform it at any time for immediate invoicing for instance.

Key transaction Z1V_CRC_BILLING Croco billing due list

1→ Project management selections: Filter according to project data

2→ Posting date: Filter according to posting date so at CO document level; Default posting to date is today date

3→ Billing data: Filter according to billing data; Default billing to date is today date

4→ Default data:

• Billing date from data acquisition
• Service rendered date = pricing date = billing date
• Here you can force any of them as from the SAP standard billing due list VF04

Then execute the transaction.

1→ CO document: CO document that has been invoiced

2→  Sales order and sale order item number: 

That step is required to determine how the system groups CO items in which sale invoice and in which sale invoice items . It focus on splitting characteristics values:

• at invoice level (header)
• At billing item leve

A sale order and a sale order item number is assigned to any CO items to materialize the summarization 

3→ Invoice, invoice item number and billing date: After the invoice creation the system updates the CO document with the invoice, the item number and the billing date

Then, go to VF03

1→ Sale invoice has been created: Document number 9000660805

2→ Billing Item analysis: 

• Item 10 is the standard one (category ZDLS): Always end by 0; Has a net value
• Item 11 is the technical item (category ZDLT): Always end by 1; Hasn't any net value

1→ Condition type ZTBA Actual:

•  Get its value from the CO items
•  Is statistical

2→ Condition type ZTBB COST+

Price condition calculated value

• - ZTBA Actual costs
• - ZTBB Overhead surcharge (condition record)
• - ZTBC Mark-up (condition record) on total ZTBA + ZTBB condition 

3→ Condition type ZTBG PA Costs of sces

• Get its value from the CO items
• Is an accrual condition to transfer the value to COPA COS value field

1→ Condition type ZTBH COS technical 

This is the unique active condition type for that technical item (ZDLT):

• Get its value from the CO items
• Is an accrual condition to credit the WBS and thus balance it

  End of document.