SAP Note

308989 - Consulting note for cross-company transactions

Version 5 Validity: 31.08.2010 - active

Language English

Header Data
Released On 31.08.2010 12:48:11
Release Status Released for Customer
Component
SD-BIL-IV-IB Intercompany Billing
Priority
Recommendations / Additional Info
Category
Consulting

Symptom
General information
1. In section I, there is an overview of the process flow and functions in the standard system
to answer general questions about cross-company transactions, cross-company processing and
intercompany billing (ICB).
2. Section II specifies the Customizing settings and required master data for the cross-company
code sales with delivery-related intercompany billing using a sample process.

Other Terms
Intercompany billing, ICB, IC billing, cross-company, CC
Cross-company code sales
Cross-company code stock transport order

Reason and Prerequisites

You require consulting or there is a program error.

Solution
I Process overview
A characteristic of the cross-company code sales is that the sales organization, in which
the sales order is created, and the delivering plant are assigned to different company codes and as
a result, a revenue allocation or cost allocation is required.

I.1 Delivery-related cross-company process

I.1.1 Sales order - delivery - customer billing document - internal billing document
(Cross-company code sales)
Billing relevance (TVAP-FKREL) = A
Example:
The customer orders from sales organization 0001 (selling company code 0001), the goods
are delivered from plant LY02 (company code of the delivering plant LY02).The delivery occurs in
the shipping point provided in the order that is assigned to the delivering plant.The customer
billing document (delivery-related) is created by sales organization 0001, the internal billing
document (delivery-related) is created by the sales organization of the company code that delivers
and it is sent to the selling company code.
Delivering plant LY02 must be assigned to sales organization 0001 so that sales
organization 0001 can sell goods delivered by plant LY02. Plant LY02 can be assigned to several
sales organizations since the relationship of sales organization toplant is a 1: n relationship.
It is possible that the sales organization of the delivering company code (for example,
LY01) belongs to a different company code than the delivering plant LY02. This means that there is
one sales organization of the delivering company code that is used for intercompany billing; the
delivering plants themselves belong to different company codes.
In addition, refer to Note 99641.
Restriction:
The statistics update and the business area determination for the sales area of the delivering plant
(that is, with the "original" organizational data and not with the data of sales area IV that
enables a grouping of several materials from plants from several different company codes into one
delivery) are only possible with a workaround.
You can use the dependency on the distribution channel to differentiate further the
plants of a sales organization.

I.1.2 Order - delivery - internal billing document - customer billing document

You can create the internal billing document before the customer billing document only by
using transaction VF01 (Create Billing Document) and by specifying the billing type IV.Billing can
be carried out using the billing due list (VF04, VF06) only if Note 38501 has been taken into
account.

I.1.3 Purchase order - replenishment delivery - internal billing document

(Cross-company code stock transfer, stock transport order)

Billing relevance (TVAP-FKREL) = D
A plant procures materials from the stocks of a different plant that belongs to a
different company code. Note 109254 contains the relevant Customizing settings.

I.1.4 Internal billing document - internal credit memo

(Cancellation)
The document types of intercompany billing document are not cancelled using the usual
document type "S1" but:
- IV with IVS
- IG with IGS

I.1.5 Returns request (IR) - returns delivery customer credit memo - internal credit memo
(Returns)
The customer credit memo is created for the returns request and the internal credit memo
is created for the returns delivery.

I.2 Order-related cross company process

Order - customer billing document - internal billing document
Billing relevance (TVAP-FKREL) = B
This process of the cross-company code sales without delivery is implemented with the
report RVIVAUFT (as of Release 4.0B). Before Release 4.0B, you can copy this using the report
ZZIVAUFT.
For this, compare Notes 63459 and 381042.
Note that the following text of this note no longer deals with this process.

I.3Order-related cross-company process for third-party business transactions

Order - purchase order - invoice
Billing relevance (TVAP-FKREL) = F
The vendor who delivers the sales order is assigned to a sales organization that works in
a different company code than the sales organization that has received the sales order.
Note that the following text of this note no longer deals with this process.

***********************************************************************
IIDetails on the cross-company code sales with delivery-related intercompany billing
II.1 Sample process:
Customer 11 orders a material from sales organization 0001 in company code 0001. The
goods are delivered from plant LY02.
VBAK-VKORG 0001
VBAK-VTWEG 01
VBAK-SPART 01
VBAK-KUNNR 11
VBAP-WERKS LY02
In the delivery, the fields for the intercompany billing are filled.
Rule: If the intercompany billing is configured completely, the system fills all fields listed
below.If the configuration is incorrect, the system does not fill any fields.
LIKP-VKORG 0001
LIKP-KUNNR 11
LIKP-VKOIV LY01!!
LIKP-VTWIV L1!!
LIKP-SPAIV L1!!
LIKP-KUNIV 22!!
LIKP-FKDIV DD.MM.YYYY
LIPS-VTWEG 01
LIPS-SPART 01
LIPS-WERKS LY02
In status tables VBUK (header status) and VBUP (item status), the system sets the billing
totals status and intercompany billing in each case.
VBUK-FKIVKA
VBUP-FKIVPA
After the inbound delivery of the goods, you can create the customer billing document
(external billing document) for customer 11. The overall processing status VBUK-GBSTK of the
delivery remains "B" (in process) after the customer billing document since the intercompany billing
document has not yet been created.
VBRK-VKORG 0001
VBRK-VTWEG 01
VBRK-BUKRS 0001
VBRK-KUNAG 11
VBRK-SPART 01
VBRP-WERKS LY02
To allocate the costs and revenues, you create the intercompany billing document in the
company code of delivering plant GB02 and send it to internal customer 22.Internal customer 22
represents selling sales organization 0001 and is created for sales organization LY01 in the company
code of delivering plant GB02.
VBRK-VKORG LY01
VBRK-VTWEG L1
VBRK-BUKRS GB02
VBRK-KUNAG 22
VBRK-SPART L1
VBRP-WERKS LY02
The status is also updated when the intercompany billing document is created.
VBUK-FKIVKC
VBUK-GBSTKC
VBUP-FKIVPC
VBUP-GBSTAC

Short:

Sales organization dataDelivering organizational data

Company code 0001Company codeGB02
Sales organization 0001Sales organization LY01
Distribution channel 01 Distribution channel L1
Division 01DivisionL1
PlantLY02PlantLY02
Customer11Internal customer 22

II.2 Customizing for the sample process:

II.2.1 Enterprise structure
l

Plant - allocate company code: Transaction OX18

Company code plant

00010001
GB02LY02
l

Sales organization - allocate company code: Transaction OVX3

Company codeSales organization

00010001
GB01LY01
GB02LY02
l

Sales organization/distribution channel - Assign plant: Transaction OVX6

Sales organization/distribution channel - plant:

0001 / 010001
LY02
LY01 / L1LY01
LY02
Compare the table entries of transaction OVV9; both entries must be maintained.
l

Sales organization - assign internal customer number: Transaction OVX5

Sales organization Customer number IV

000122
This table entry is identical to the entry in transaction OVVA.

II.2.2 Sales and distribution/billing/intercompany billing document

l

Define order types for the intercompany billing document:Transaction OVV8

Depending on the order types used, the corresponding billing document types for
the internal billing document are maintained here.
l

Assign organizational units per plant:Transaction OVV9

PlantSales organization IVDistribution channel IVDivision IV

LY02LY01L1L1
Note: For IS-R, these assignments must be carried out in plant maintenance
(transaction WB01 or WB02) directly.
l

Define internal customer number for each sales organization:

Transaction OVVA
Sales organization Customer IV
0001 22
l

Automatic posting to vendor account with SAP-EDI:

Transaction VOFC, transaction WEL1, transaction V/40

If you want to post the invoice receipt to accounting directly with SAP-EDI
instead of manually, you have to maintain the settings according to the documentation.Notes 137686
and 31126 contain more detailed explanations. Problem messages for this are processed under the
component SD-EDI.

II.3 Master data for the sample process:

l

Create master data for customer 11 in the selling sales organization: Transaction XD01

Customer 11
Company code 0001
Sales organization 0001
Distribution channel01
Division01
l

Create customer master record for internal customer 22 in the sales organization of the
delivering company code (Sales and Distribution segment):Transaction XD01
IMPORTANT: The customer master record must be created with the account group of the sold-to
party completely.

Customer 22
Sales organization LY01

Distribution channelL1
DivisionL1
The accounting segment of the customer master for internal customer 22 must be created in
the company code of the delivering plant so that the intercompany billing document can be
transferred to accounting.
Customer 22
Company code GB02
l

Create material master record in the sales organization of the selling and of the delivering
company code:Transaction MM01

Material
PlantLY02andLY02
Sales organization0001LY01
Distribution channel01L1
l

Condition master record PI01 or IV01 (quantity-dependent) or

PI02 or IV02 (percentage)

Create: Transaction VK11
Sales organization orderPlant Material
0001LY02 PUMP
l

The corresponding condition type is included in the pricing procedure used with requirement 22.

Note on pricing:
Condition type PI01/PI02 (condition category = I) is flagged as a statistical condition
in the sales order or customer billing document. As a result, it has no effect on the pricing for
the customers.Up to Release 4.0, no particular pricing procedures were used for intercompany
billing documents; only the standard procedure RVAA01 was used. Instead, a fixed logic was specified
in the program.
As of Release 4.0, we recommend that you define and assign a specific calculation procedure for the
intercompany billing document (procedure ICAA01, document pricing procedure "I"). However, due to
upward compatibility, you should still be able to use the old logic. Therefore, if you want to use
your own pricing procedure, set the specific procedure indicator so that the fixed logic in the
program is not used.
In the intercompany billing document, the price PR00 is inactive and the condition type
PI01/PI02 is replaced with condition category IV01/IV02. Due to the reference to condition type
PI01/PI02 determined in the definition of condition type IV01/IV02, the system determines identical
condition values.While condition type PI01/PI02 in the customer billing document represents the
costs of the selling company code, condition type IV01/IV02 in the intercompany billing document is
the price and, as a result, it represents the revenues of the delivering company code. If you use
these two condition types, you can ensure that the transfer to the profitability analysis (CO-PA) is
correct.

Other Attributes
Transaction codes

GB01
GB02
HIER
MM01
OVV8
OVV9
OVVA
OVX3
OVX5
OVX6
OX18
PR00
V/40
VF01
VF04
VF06
VK11
VOFC
WB01
WB02
WEL1
XD01

Validity
This document is not restricted to a software component or software component version

References
This document refers to:
SAP Notes
1032869 Tax determination in intercompany billing
137686 ALE_INVOIC01: Internal allocatn Customizing in FI
338922 Analysis note for cross-company transactions (delivery)
354290 Message KI100 adj.for statistical accnt assignment
381042 Order-related intercompany billing in Releases 4.5*/4.6*
394481 Intercompany with make-to-order production
543821 FAQ: Cross-company processing
63459 Order and third-party-related intercompany billing
69314 Cross company without intercompany billing

This document is referenced by:

SAP Notes (8)
137686 ALE_INVOIC01: Internal allocatn Customizing in FI
381042 Order-related intercompany billing in Releases 4.5*/4.6*
354290 Message KI100 adj.for statistical accnt assignment
69314 Cross company without intercompany billing
63459 Order and third-party-related intercompany billing
338922 Analysis note for cross-company transactions (delivery)
1032869 Tax determination in intercompany billing
543821 FAQ: Cross-company processing