Set-Up Instructions | PUBLIC

SAP S/4HANA
2024-02-23

Setting Up Advanced Intercompany Sales (5D2)

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 General Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Main Abbreviations Used in the Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Business Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 How to Work through this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Activate Advanced Intercompany Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Organizational Setup - General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Organizational Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Organizational Setup – Advanced Intercompany Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Assign Sales Organization/Distribution Channel to Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Assign Organizational Unit to Delivering Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Assign Shipping Point Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Assign Picking Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Master Data Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Create/Extend Business Partners Representing Affiliate Company Codes. . . . . . . . . . . . . . . . . . . . . . . . 11
Create/Extend Customer Company Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Create/Extend Customer Sales Area Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Create/Extend Supplier Company Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Create/Extend Supplier Purchasing Organization Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Create/Extend Business Partners representing Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Create/Extend Customer Company Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create/Extend Customer Sales Area Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Create/Extend Supplier Company Code Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Create/Extend Supplier Purchasing Organization Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3 Extend End Customer Master to the Delivering Company. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Create/Extend Customer Sales Area Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.4 Enhance Material Master in Selling Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.5 Maintain Customer Discount Condition Record for Ordering Company. . . . . . . . . . . . . . . . . . . . . . . . . 28
3.6 Maintain Standard Purchase Info Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7 Maintain Export Tax Condition Record for Delivering Company. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1 Define Business Partner for Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
4.2 Define Shipping Data for Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Setting Up Advanced Intercompany Sales (5D2)

2 PUBLIC Content
4.3 Assign Tax Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.4 Program Parameters for Supplier Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configure Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Assign Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.5 Define Output Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.6 Assign Transit Plant to Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.7 Define Purchase Order Defaults for Sales Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
4.8 (Optional) Configure Posting Date for Processing Advanced Intercompany Invoices. . . . . . . . . . . . . . . . 37
4.9 Activate Advanced Intercompany Sales Process for Sales Document Types and Item Categories. . . . . . . 38

Setting Up Advanced Intercompany Sales (5D2)

Content PUBLIC 3
1 Purpose

1.1 General Purpose

The purpose of this document is to describe how to set up customer systems and to maintain settings which are
currently not supported by automated content activation.

1.1.1 Main Abbreviations Used in the Document

Abbreviation Explanation

SI Scope Item

SRS Standard Reference Content

SSCUI Self Service Configuration UI

EBRR Event-Based Revenue Recognition

WCR World Customer Request

1.2 Business Context

Advanced Intercompany Sales scenario enables data exchange and highly automated posting logics for business
transactions between affiliates (represented by company codes) sharing the same client.

Depending on countries of company codes, we're delivering two SAP Best Practices scope items:

• Advanced Intercompany Sales (5D2_DE)

• Advanced Intercompany Sales (5D2_US)

Company codes are based on different countries. In case intercompany processing has been chosen to be part
of the business scope, a business partner, representing a country solution’s standard company code (usually the
company code is from the SRS), is created with its ID, address, and the main business partner roles needed for
financial accounting, sales, and purchasing.

The SAP Best Practices sample data ID of such business partners is set up as assumed in this scenario:

• International: DE company (e.g. company code 1010) sells goods to customer, and the goods are delivered
from a plant, which belongs to US company (e.g. company code 1710).

Setting Up Advanced Intercompany Sales (5D2)

4 PUBLIC Purpose
For creating internal business partner to represent company code and plant, only the grouping with external
number range can be used. This is to ensure business partner-dependent configuration is consistent in your entire
system landscape.

Quality Management Integration (QM)

You can use QM in the delivering plant and the transit plant. If QM is active in the transit plant for the material, the
goods receipt posting to the storage location in the transit plant will create an inspection lot.

You can avoid the creation of the inspection lot by deactivating QM for the material master data, which is located in
the quality management section of the transit plant.

If you want to activate quality inspection for a material in the transit plant (e.g. as the transit plant is used as
physical plant, too), you have the following options:

• Use information records defined for the supplier number of the delivering company.
• Use a virtual plant as a transit plant.

Extended Warehouse Management (EWM)

The determined storage location in the transit plant cannot be managed by EWM, because you need to execute the
whole EWM inbound and outbound process to receive the material into storage location in the transit plant, and
afterwards to transfer it to the valuated stock in transit in the transit plant.

To avoid additional EWM process steps, you can use a virtual plant as a transit plant.

1.3 How to Work through this Document

Starting with chapter two, this document describes which data and configuration you need to create on top of the
SRS to enable intercompany billing between two company codes.

Process Version Selling Company Code Delivering Company Code

Intercompany Sales Process 5D2_DE 1010 1710

Setting Up Advanced Intercompany Sales (5D2)

Purpose PUBLIC 5
2 Preparation

2.1 Prerequisites

2.1.1 Activate Advanced Intercompany Sales

You must activate advanced intercompany sales process by configuration. For detailed instructions about the
activation, you can refer to a similar procedure in the chapter Activate Advanced Intercompany Sales Process for
Sales Document Types and Item Categories.

2.2 Organizational Setup - General

2.2.1 Organizational Setup

Upon the activation of two country solutions, you will get the required two company codes with related
organizational structure. Besides this, you can also use additionally created organizational structures.

The following example refers to Advanced Intercompany Sales process (5D2_DE).

Check if the following organizational assignments have been maintained in the system for your defined
intercompany sales relationships.

Extend Organization Structure Original Country Solution (DE) Original Country Solution (US)

Company 1010 1710

Company Code 1010 1710

Assign Company Code to Company 1010 to 1010 1710 to 1710

Assign Company Code to Controlling 1010 to A000 1710 to A000

Area

Define Plant / Assign Plant to Company 1010 / 1010 to 1010 1710 / 1710 to 1710
Code

Maintain Purchasing Organization / As- 1010 / 1010 to 1010 1710 / 1710 to 1710
sign Purchasing Organization to Com-
pany Code

Setting Up Advanced Intercompany Sales (5D2)

6 PUBLIC Preparation
 Extend Organization Structure Original Country Solution (DE) Original Country Solution (US)

Assign Purchasing Organization to Plant 1010 to 1010 1710 to 1710

Define Sales Organization / Assign Sales 1010 / 1010 to 1010 1710 / 1710 to 1710
Organization to Company Code

Assign Distribution Channel to Sales Or- 10 to 1010 10 to 1710

ganization (Distr. Chain)

Sales Office 100 170

Sales Group / Assign Sales Group to 100 / 100 to 100 170 / 170 to 170
Sales Office

Set up Sales Area 1010/10/00 1710/10/00

Assign Sales Office to Sales Area 100 to 1010/10/00 170 to 1710/10/00

Shipping Point 1710

171R (for return)

Assign Shipping Point to Plant 1710 to 1710

Storage Location 171A

Assign Sales Organization - Distribution 1710/10 to 1710

Channel to Plant

Solution content for your country including scope items (at least Sell from Stock BD9) is activated in your client.

2.3 Organizational Setup – Advanced Intercompany Sales

2.3.1 Assign Sales Organization/Distribution Channel to Plant

Purpose

This process step shows you how to define the allowed relationships for running advanced intercompany business.
A plant of one affiliate can be assigned to several sales organizations of other affiliates.

This assignment defines that a plant can be used as a delivering plant in sales orders of a sales organization and
distribution channel combination.

Setting Up Advanced Intercompany Sales (5D2)

Preparation PUBLIC 7
Prerequisites

The plant and sales organization/distribution channel have already been created.

Procedure

1. Enter transaction S_ALR_87007463 or use SAP IMG path Enterprise Structure Assignment Sales and
Distribution Assign Sales Organization - Distribution Channel - Plant .
2. Choose New Entries to enter your organizations required combinations of selling sales organizations and
delivering plants as shown in the sample data below, choose Save:

SOrg. DCHCust/Mt Plnt

1010 10 1710

2.3.2 Assign Organizational Unit to Delivering Plant

Purpose

To assign a sales area (sales organization, distribution channel and division) to each delivering plants for which
advanced intercompany sales processing is possible. The assigned sales area is used to create the sales order in
the delivering company and thereby used to process intercompany billing.

Prerequisite

The delivering plant and sales area have already been created.

Procedure

1. Enter transaction S_ALR_87007594 or use SAP IMG path Sales and Distribution Billing Intercompany
Billing Assign Organizational Units By Plant Assign Organizational Units to the Plants .
2. Assign the Sales Organization, Distribution Channel and Division to the Plant and choose Save.

Setting Up Advanced Intercompany Sales (5D2)

8 PUBLIC Preparation
 Plant SOrg DstCH Div.

1710 1710 10 00

2.3.3 Assign Shipping Point Determination

Purpose

For each plant, you can allocate shipping points to all combinations of shipping conditions and loading groups.

For Sell-from-stock and for Intercompany Sales the same shipping point is used for a plant.

This step can be skipped if the configuration is already available in the system.

Prerequisites

Before you can allocate the shipping points, you must define plants, shipping points, shipping conditions, and
loading groups.

Procedure

1. Enter transaction S_ALR_87006845 or use SAP IMG path Logistics Execution Shipping Basic Shipping
Functions Shipping Point and Goods Receiving Point Determination Assign Shipping Points .
2. Click the New Entries function to enter the following shipping point determination data, then choose Save:

Shipping Condition Loading Group Plant Proposed Shipping Point

01 0001 1710 1710

01 0002 1710 1710

01 0003 1710 1710

Setting Up Advanced Intercompany Sales (5D2)

Preparation PUBLIC 9
2.3.4 Assign Picking Locations

Purpose

The purpose of this activity is to assign picking location to shipping point/plant.

For Sell-from-stock and for Intercompany Sales the same picking locations are used for a plant.

This step can be skipped if the configuration is already available in the system

Prerequisites

The Shipping Points and Storage Locations have already been created for the plants.

Procedure

1. Enter transaction S_ALR_87006701 or use SAP IMG path Logistics Execution Shipping Picking
Determine Picking Location Assign Picking Locations .
2. Click the New Entries function to enter the following data, choose Save:

ShPt Plnt SC SLoc

1710 1710 “”(keep empty) 171A

1710 1710 10 171A

1710 1710 20 171A

Setting Up Advanced Intercompany Sales (5D2)

10 PUBLIC Preparation
3 Master Data Setup

3.1 Create/Extend Business Partners Representing Affiliate

Company Codes

In this section, you need to create/extend business partners representing selling and delivering companies.

Intercompany Invoice

In intercompany sales process, the delivering company issues an intercompany invoice to the selling company for
goods delivered to external customer. Customer in this intercompany invoice is represented by business partner ID
assigned to selling sales organization.

Create an internal business partner with customer roles to represent the selling company.

Intercompany Invoice Receipt

The selling company receives an invoice from the delivering company. This invoice triggers a supplier invoice
automatically posted in the selling company. To map this transaction to an internal business partner ID with
supplier role, the business partner ID needs to be assigned to the delivering company code.

Create a business partner to represent the supplying company code.

Business partners with the same ID as on D-development and Q-quality, should be created in P-production system
before Q2P transport of intercompany related configuration.

Business partner data for company codes 1710 and 1010 are respectively created/extended in the following
enterprise organizations:

• 10401010, as customer, for company code 1710 and sales area 1710/10/00
• 17401710, as supplier, for company code 1010 and purchasing organization 1010

After activating the 5D2_US and 5D2_DE country solution, business partner data representing each company
code is like in the table data below: business partner 17401710 represents company codes 1710 and 10401010
represents company codes 1010.

Business Partner ID Business Partner ID

10401010 (ID, Address, Bank data …) 17401710 (ID, Address, Bank data …)

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 11
Customer Company Code Data Customer Company Code Data

1010 (Rec.Acc., Currency …) 1710 (Rec.Acc., Currency …)

Supplier Company Code Data Supplier Company Code Data

1010 (Rec.Acc., Currency …) 1710 (Rec.Acc., Currency …)

Customer Sales Area Data Customer Sales Area Data

1010/10/10 (Sales tax …) 1710/10/10 (Sales tax …)

Purchasing Organization Data Purchasing Organization Data

1010 (Currency …) 1710 (Currency …)

After performing activity in this chapter, the business partner data representing each company code will look like
this:

Business Partner ID Business Partner ID

10401010 (ID, Address, Bank data …) 17401710 (ID, Address, Bank data …)

Customer Company Code Data Customer Company Code Data

1010 (Rec.Acc., Currency …) 1010 (Rec.Acc., Currency …)

1710 (Rec.Acc., Currency …)

Supplier Company Code Data Supplier Company Code Data

1710 (Rec.Acc., Currency …) 1710 (Rec.Acc., Currency …)

1010 (Rec.Acc., Currency …)

Customer Sales Area Data Customer Sales Area Data

1010/10/10 (Sales tax …) 1010/10/10 (Sales tax …)

1710/10/10 (Sales tax …)

Purchasing Organization Data Purchasing Organization Data

1710 (Currency …) 1710 (Currency …)

1010 (Currency …)

Setting Up Advanced Intercompany Sales (5D2)

12 PUBLIC Master Data Setup
3.1.1 Create/Extend Customer Company Code Data

Purpose

This process step shows you how to create the new company code data segment needed for the affiliated company
that wants to use the business partner in "Customer-related" FI postings.

Procedure

1. Log on to the SAP Fiori launchpad using role SAP_BR_BUPA_MASTER_SPECIALIST with name Master Data
Specialist - Business Partner Data.
2. Open Maintain Business Partner.
3. Choose Business Partner. Enter the business partner ID to be enhanced (for example, 10401010) in the
Business Partner field and choose Enter.
4. Choose Switch Between Display and Change (F6). The Change Organization: 10401010 screen displays.
5. Create company code data. Check if BP role FLCU00 Customer (Fin.Accounting) exists. If not, extend BP role
FLCU00 to delivering company, (for example, 1710).
6. Select FLCU00 Customer (Fin.Accounting) (defined) in the Change in BP role field.
7. You can only navigate to the Company Code Data screen when you select this BP role as only in this case the
Company Code button displays.
8. Go to the Control tab and enter/check Trading partner field (for example, 1010).
9. Navigate to the General Data screen by choosing General Data.
10. Go to the Customer: General Data screen and enter/check the Supplier field (for example, 10401010).
11. Navigate to the Company Code Data screen by choosing Company Code.
12. Choose Company Codes. The Customer (Fin.Accounting) Change: Company Codes dialog box displays.
13. Choose Create. In the Company Codes table, add new entries as below:
• Company Code: <Supplying company code>, for example, 1710
• Customer: <select>
14. Select the above new entry (line) and choose Adopt.
15. The following table lists the most common fields that need to be populated. Make sure you consider local
(country-specific) adjustments as well.

Field Name Entry Value

Customer: Account Management tab

Reconciliation Account for example, 12300000 ("Trade Receivables affiliated Com-

panies")

Sort key for example, 009 ("External doc. Number")

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 13
 Field Name Entry Value

Customer: Payment Transactions tab

Terms of Payment for example, 0001 ("Payable immediately Due net")

Payment Methods for example, T ("Bank Transfer")

Customer: Correspondence tab

Accounting Clerk for example, 01 ("…")

16. Save your entries. Customer code data for company code 1710 of business partner 10401010 is created.

3.1.2 Create/Extend Customer Sales Area Data

Purpose

This process step shows you how to create the new sales area data segment needed for the affiliated company that
wants to use the business partner in intercompany sales billing.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST with name
Master Data Specialist - Business Partner Data.
2. Open Maintain Business Partner.
3. Open Business Partner. Enter the business partner ID to be enhanced (for example, 10401010) in the Business
Partner field and choose Enter .
4. Choose Switch Between Display and Change (F6). The Change Organization: 10401010 screen displays.
5. Create sales area data. Check if BP role FLCU01 Customer (defined) exists. If not, extend BP role FLCU01 to
delivering company, (for example, 1710). Choose FLCU01 Customer (defined) in the Change in BP role field.
6. Note that you can only navigate to the Sales Area Data screen when you select this BP role as only in this case
Sales and Distribution displays.
7. Navigate to the Sales Area section by choosing Sales and Distribution.
8. Choose Sales Areas. The Customer Change: Sales Areas dialog box displays.
9. Choose Create. In the Sales Areas table, add new entries as below:
• Sales Organization: <supplying sales organization>, for example, 1710
• DistrChannel: for example, 10
• Division: for example, 00
10. Select above new entry (line) and choose Transfer.

Setting Up Advanced Intercompany Sales (5D2)

14 PUBLIC Master Data Setup
 11. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments. Select the proper tab.

Field Name Entry Value

Orders tab

Customer Group 01

Currency for example, EUR

Cust. Pric. Procedure 02

“” should be used if the sales organization is outside US.

Shipping tab

Delivery Priority 2

Shipping Conditions 01

Billing tab

Incoterms for example, EXW

Inco. Location 1 for example, Palo Alto

Terms of Payment for example, 0001 ("Due net")

Account Assignment Group for example, 03 ("Affiliate Company Revenue")

Output Tax for example, [USE-USA / UTXJ] 0 ("Tax Exempt")

Partner Functions tab

Partner Role 1 Sold-to Party: for example, own ID

Partner Role 2 Bill-to Party: for example, own ID

Partner Role 3 Payer: for example, own ID

Partner Role 4 Ship-to Party: for example, own ID

12. Save your entries. Customer code data for sales area 1710/10/00 of business partner 10401010 is created.

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 15
3.1.3 Create/Extend Supplier Company Code Data

Purpose

This process step shows you how to create the new company code data segment needed for the affiliated company
that wants to use the business partner in supplier related FI postings.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST with the name
Master Data Specialist - Business Partner Data.
2. Open Maintain Business Partner.
3. Open Business Partner. Enter the business partner ID to be enhanced (for example, 17401710) in the Business
Partner field and choose Enter .
4. Choose Switch Between Display and Change (F6). The Change Organization: 17401710 screen displays.
5. Create company code data. Check if BP role FLVN00 Vendor (Fin.Accounting) exists. If not, extend BP role
FLVN00 to selling company, (for example, 1010). Choose FLVN00 Supplier (Fin.Accounting) (defined) in the
Change in BP role field.
6. Note that you can only navigate to the Company Code Data screen when you select this BP role as only in this
case Company Code displays.
7. Go to Control tab and enter/check Trading partner field (for example, 1710).
8. Navigate to the company code section by choosing Company Code.
9. Choose Company Codes. The Supplier (Fin.Accounting) Change: Company Codes dialog box displays.
10. Choose Create. In the Company Codes table, add new entries as below:
• Company Code: <Selling company code>, for example, 1010
• Vendor: <select>
11. Select the above new entry (line) and choose Adopt.
12. The following table lists the most common fields which need to be populated. You need to consider local
(country-specific) adjustments.

Field Name Entry Value

Vendor: Account Management tab

Reconciliation Account for example, 21300000 ("Trade Payables affiliated Compa-

nies")

Sort key for example, 009 ("External doc. Number")

Vendor: Payment Transactions tab

Setting Up Advanced Intercompany Sales (5D2)

16 PUBLIC Master Data Setup
 Field Name Entry Value

Terms of Payment for example, 0001 ("Payable immediately Due net")

13. Save your entries. Customer code data for company code 1010 of business partner 17401710 is created.

3.1.4 Create/Extend Supplier Purchasing Organization Data

Purpose

This process step shows you how to create the new purchasing organization data segment needed for the affiliated
company that wants to use the business partner in sales transaction.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST with name
Master Data Specialist - Business Partner Data.
2. Open Maintain Business Partner.
3. Open Business Partner. Enter the business partner ID to be enhanced (for example, 17401710) in the Business
Partner field and choose Enter .
4. Choose Switch Between Display and Change (F6). The Change Organization: 17401710 screen displays.
5. Create purchasing data. Check if BP role FLVN01 Supplier (defined) exists. If not, extend BP role FLVN01 to
selling company, (for example, 1010). Choose FLVN01 Supplier (defined) in the Change in BP role field.
6. Note that you can only navigate to the Purchasing Data screen when you select this BP role as only in this case
Purchasing displays.
7. Navigate to the Purchasing Organization section by choosing Purchasing.
8. Choose Purchasing Organizations. The Supplier Create: Purchasing Organizations dialog box displays.
9. Choose Create. In the Purchasing Organizations table, add new entry as below:
• Purchasing Organization: <purchasing organization in selling company>, for example, 1010
10. Select above new entry (line) and choose Transfer.
11. The following table lists the most common fields which need to be populated. You need to consider local
(country-specific) adjustments. Select the proper tab.

Field Name Entry Value

General Data view

Vendor: General Data tab

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 17
 Field Name Entry Value

Customer 17401710

Purchasing Data tab

Order Currency for example, EUR

Terms of Payment for example, 0001 ("Payable immediately Due net")

GR-Based Inv. Verification <select>

Partner Functions tab

Partner Role 1 Supplier: for example, own ID

Partner Role 2 Ordering Address: for example, own ID

12. Save your entries. Supplier purchasing data for purchasing organization 1010 of business partner 17401710 is
created.

3.2 Create/Extend Business Partners representing Plants

In this section, business partners 10411010 and 17411710 represent plants 1010 and 1710 which are respectively
created/extended in organizations.

First, please create new business partners 10411010 and 17411710 under Business Partner (Gen.) role, the
relevant parameter can be directly copied from BP 10100001 for reference. For detailed steps regarding how to
create BP general role, you can also find in MDS BNE.

MDS Description

BNE Create Supplier Master

• 10411010 as customer in company code 1710 and sales area 1710/10/00

• 17411710 as supplier in company code 1010 and purchasing organization 1010

After performing activities in this chapter, the business partner data representing each plant will be like this:

Business Partner ID Business Partner ID

10411010 (ID, Address, Bank data …) 17411710 (ID, Address, Bank data …)

Customer Company Code Data Customer Company Code Data

1010 (Rec.Acc., Currency …) 1710 (Rec.Acc., Currency …)

Setting Up Advanced Intercompany Sales (5D2)

18 PUBLIC Master Data Setup
 1710 (Rec.Acc., Currency …)

Supplier Company Code Data Supplier Company Code Data

1010 (Rec.Acc., Currency …) 1710 (Rec.Acc., Currency …)

1010 (Rec.Acc., Currency …)

Customer Sales Area Data Customer Sales Area Data

1010 / 10/ 10 (Sales tax …) 1710 / 10 / 10 (Sales tax …)

1710 / 10/ 10 (Sales tax …)

Purchasing Organization Data Purchasing Organization Data

1010 (Currency …) 1710 (Currency …)

1010 (Currency …)

Create the business partners in production system before transporting configuration to the production system.

3.2.1 Create/Extend Customer Company Code Data

Purpose

In this activity, you create the new company code data segment for business partner, which is needed for the
affiliated company that wants to use the business partner in “Customer-related” FI postings.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST to access the
Maintain Business Partner App by opening the tile.
2. Open Business Partner. Enter the Business Partner ID to be enhanced (for example, 10411010) in the Business
Partner field and choose Enter .
3. Choose Switch Between Display and Change (F6). The Change Organization: 10411010 screen displays.
4. Create company code data.
5. Check if FLCU00 Customer (Fin.Accounting) BP role exists. If not, extend FLCU00 to delivering
company, (for example, 1710).
6. Choose FLCU00 Customer (Fin.Accounting)(defined) in Change in BP role field.
You can only navigate to the Company Code Data screen when you select this BP role as only in this case,
Company Code is displayed.

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 19
7. Go to Control tab and enter/check Trading partner (for example, 1010).
8. Navigate to the Company Code Data screen(s) by choosing Company Code.
9. Choose Company Codes. The Customer (Fin.Accounting) Change: Company Codes dialog box displays.
10. Choose Create.
11. In Company Codes table, add new entries below:
• Company Code: <Supplying company code>, for example, 1710
• Customer: X
12. Select above new entry (line) and choose Adopt.
13. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments.

Field Name Entry Value

Customer: Account Management tab

Reconciliation Account for example, 12300000 (“Trade Receivables affiliated Com-

panies”)

Customer: Payment Transactions tab

Terms of Payment for example, 0001 (“Payable immediately Due net”)

14. Save your entries. Customer code data for company code 1710 of business partner 10411010 is created.

3.2.2 Create/Extend Customer Sales Area Data

Purpose

In this activity, you create the new sales area data segment, which is needed for the affiliated company that wants
to use the business partner in “internal invoice” sales billing.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST to access the
Maintain Business Partner App by opening the tile.
2. Open Business Partner. Enter the Business Partner ID to be enhanced (for example, 10411010) in the Business
Partner field and choose Enter .
3. Choose Switch Between Display and Change (F6). The Change Organization: 10411010 screen displays.
4. Create sales area data.
5. Check if BP role FLCU01 Customer(defined) exists. If not, extend FLCU01 to delivering company, (for
example, 1710).

Setting Up Advanced Intercompany Sales (5D2)

20 PUBLIC Master Data Setup
 6. Choose FLCU01 Customer(defined) in Change in BP role field.
7. Note that you can only navigate to the Sales Area Data screen when you select this BP role as only in this case,
Sales and Distribution is displayed.
8. Navigate to the Sales Area Data screen(s) by choosing Sales and Distribution.
9. Choose Sales Areas. The Customer Change: Sales Areas dialog box displays.
10. Choose Create.
11. In Sales Areas table, add new entries below:
• Sales Organization: Supplying sales organization, for example, 1710
• DistrChannel: for example, 10
• Division: for example, 00
12. Select above new entry (line) and choose Create.
13. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments. Select the proper tab.

Field Name Entry Value

Orders tab

Customer Group 01

Currency for example, EUR

Cust. Pric. Procedure 02

“” should be used if the sales organization is outside US.

Shipping tab

Delivery Priority 2

Shipping Conditions 01

Billing tab

Incoterms for example, EXW

Inco. Location 1 for example, Palo Alto

Terms of Payment for example, 0001 (“Due net”)

Account Assignment Group for example, 03 (“Affiliate Company Revenues)

Output Tax for example, 0 ("Tax Exempt") for country US-USA and Tax
Category UTXJ

Partner Functions tab

Partner Role 1 Sold-to Party, for example, own ID

Partner Role 2 Bill-to Party, for example, 10401010

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 21
 Field Name Entry Value

Partner Role 3 Payer, for example, 10401010

Partner Role 4 Ship-to Party, for example, own ID

14. Save your entries. Customer code data for sales area 1710 /10/00 of business partner 10411010 is created.

3.2.3 Create/Extend Supplier Company Code Data

Purpose

In this activity, you create the new company code data segment for business partner, which needed for the
affiliated company that wants to use the business partner in “Supplier-related” FI postings.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST to access the
Maintain Business Partner App by opening the tile.
2. Open Business Partner. Enter the Business Partner ID to be enhanced (for example, 17411710) in the Business
Partner field and choose Enter .
3. Choose Switch Between Display and Change (F6). The Change Organization: 17411710 screen displays.
4. Create company code data.
5. Check if BP role FLVN00 Supplier (Fin.Accounting) exists. If not, extend FLV00 to delivering
company, (for example, 1010).
6. Choose FLVN00 Supplier (Fin.Accounting)(defined) in Change in BP role field.
You can only navigate to the Company Code Data screen when you select this BP role as only in this case,
Company Code is displayed.
7. Go to Control tab and enter/check Trading partner (for example, 1710).
8. Navigate to the Company Code Data screen by choosing Company Code.
9. Choose Company Codes. The Supplier (Fin.Accounting) Change: Company Codes dialog box displays.
10. Choose Create.
11. In Company Codes table, add new entries below:
• Company Code: <Selling company code>, for example, 1010
• Vendor: X
12. Select above new entry (line) and choose Create.
13. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments.

Setting Up Advanced Intercompany Sales (5D2)

22 PUBLIC Master Data Setup
 Field Name Entry Value

Vendor: Account Management tab

Reconciliation Account for example, 21300000 (“Trade Payables affiliated Compa-

nies”)

Vendor: Payment Transactions tab

Terms of Payment for example, 0001 (“Payable immediately Due net”)

Incoterms Version for example, 2020

Incoterms for example, EXW

Incoterms Location 1 for example, VENDOR

14. Save your entries. Customer code data for company code 1010 of business partner 17411710 is created.

3.2.4 Create/Extend Supplier Purchasing Organization Data

Purpose

In this activity, you create the new purchasing organization data segment needed for the affiliated company that
wants to use the business partner in sales transaction.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST to access the
Maintain Business Partner App by opening the tile.
2. Open Business Partner.
3. Enter the Business Partner ID to be enhanced (for example, 17411710) in the Business Partner field and
choose Enter.
4. Choose Switch Between Display and Change (F6). The Change Organization: 17411710 screen displays.
5. Create purchasing data. Check if BP role FLVN01 Supplier (defined) exists. If not, extend FLV01 to
selling company, (for example, 1010).
6. Select FLVN01 Supplier(defined) in Change in BP role.
You can only navigate to the Purchasing Data screen when you select this BP role as only in this case,
Purchasing is displayed.
7. Go to Vendor: General Data tab and enter/check Plant (for example, 1710) field.
8. Navigate to the Purchasing Data screen by choosing Purchasing.

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 23
9. Choose Purchasing Organizations. The Supplier Create: Purchasing Organizations dialog box displays.
10. Choose Create.
11. In Purchasing Organizations table, add new entry below:
• Purchasing Organization: <Purchasing Organization in selling company>, for example, 1010
12. Select above new entry (line) and choose Create.
13. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments. Select the proper tab.

Field Name Entry Value

Purchasing Data tab

Order Currency for example, EUR

Payment Terms for example, 0001 (“Payable immediately Due net”)

Incoterms for example, EXW ("Ex Works")

Incoterms Location 1 Vendor

GR-Based Inv. Verification X

Schema Grp Supp 02 (“Vendor schema group Intercomp”)

Partner Functions tab

Partner Role 1 Supplier, for example, own ID

Partner function: VN

Partner Role 2 Invoicing Party, for example, 17401710

Partner function: PI

14. Save your entries. Customer code data for purchasing organization 1010 of business partner 17411710 is
created.

3.3 Extend End Customer Master to the Delivering Company

In this section, you can extend ship-to-partner customer, for example, 10100002 to the delivering company 1010
as Ship-to partner on sales order.

After performing activities in this chapter, the customer data in the delivering company code is like this:

Business Partner ID

10100002 (ID, Address, Bank data …)

Setting Up Advanced Intercompany Sales (5D2)

24 PUBLIC Master Data Setup
 Business Partner ID

Customer Sales Area Data

1710 / 10 / 10 (Sales tax …)

3.3.1 Create/Extend Customer Sales Area Data

Purpose

In this activity, you create the new sales area data segment, which is needed for the delivering company that wants
to use the ship-to-party number in the intercompany sales order or intercompany invoice.

This is an optional step: In case the sales area view of the ship-to-party doesn’t exist in the delivering company
the address of the ship-to-party instead of the ship-to-party number is copied into the sales order in the delivering
company.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_BUPA_MASTER_SPECIALIST to access the
Maintain Business Partner App by opening the tile.
2. Open Business Partner. Enter the Business Partner ID to be enhanced (for example, 10100002) in the Business
Partner field and choose Enter .
3. Choose Switch Between Display and Change (F6). The Change Organization: 10100002 screen displays.
4. Create sales area data.
5. Check if BP role FLCU01 Customer(defined) exists. If not, extend FLCU01 to delivering company, (for
example, 1710).
6. Choose FLCU01 Customer(defined) in the Change in BP role field.
You can only navigate to the Sales Area Data screen when you select this BP role as only in this case, Sales and
Distribution is displayed.
7. Navigate to the Sales Area Data screen(s) by choosing Sales and Distribution.
8. Choose Sales Areas. The Customer Change: Sales Areas dialog box displays.
9. Choose Create.
10. In Sales Areas table, add new entries below:
• Sales Organization: <Delivering sales organization>, for example, 1710
• DistrChannel: for example, 10
• Division: for example, 00
11. Select the above new entry (line) and choose Create.
12. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments. Select the proper tab.

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 25
 Field Name Entry Value

Orders tab

Customer Group 01

Currency for example, EUR

Cust. Pric. Procedure 02

“” should be used if the sales organization is outside US.

Shipping tab

Delivery Priority 2

Shipping Conditions 01

Billing tab

Incoterms for example, EXW

Inco. Location 1 for example, Palo Alto

Terms of Payment for example, 0001 (“Due net”)

Account Assignment Group for example, 02 (“Foreign Revenues”)

Output Tax for example, 0 ("Tax Exempt") for country US-USA and Tax
Category UTXJ

Partner Functions tab

Partner Role 1 Sold-to Party, for example, own ID

Partner Role 2 Bill -to Party, for example, own ID

Partner Role 3 Payer, for example, own ID

Partner Role 4 Ship-to Party, for example, own ID

13. Save your entries. Customer code data for sales area 1010 /10/00 of business partner 17100002 is created.

Setting Up Advanced Intercompany Sales (5D2)

26 PUBLIC Master Data Setup
3.4 Enhance Material Master in Selling Company Code

Purpose

In the following sections, you’ll learn what to do to enhance the trading material TG12 so that they can be used
in Advanced Intercompany Sales processing. If you want to use other materials in Advanced Intercompany Sales
processing, you will have to do the enhancement steps for those materials accordingly.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_PRODMASTER_SPECIALIST to access the
Change Material App by opening the tile.
2. Choose Create Material tile. The Change Material (Initial Screen) displays.
3. Enter the following data and choose Continue:
• Material: for example, TG12
4. The Select View(s) dialog box displays.
5. Select Purchasing and MRP 2, then choose Continue.
6. The Select view(s): Organizational levels dialog box displays.
7. Maintain following data and choose Continue:

Field Name Entry Value

Organizational levels subarea

Plant for example, 1010

Stor. Loc. for example, 101A

The Create Material screen displays.

8. Make the following data or actions and choose Save. Material data for the selected views is created in selling
company.

Field Name Entry Value

Purchasing tab

Tax ind. F. material 1

MRP 2 tab

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 27
 Field Name Entry Value

Storage loc. For External Procurement 101A

3.5 Maintain Customer Discount Condition Record for

Ordering Company

Purpose

This process step shows you how to maintain customer discount condition record for affiliated ordering company
code.

If the sales pricing for the material TG12 and customer 10401010 already exists in the system, you can skip this
step.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_PRICING_SPECIALIST assigned with name
Master Data Specialist - Pricing Data.
2. Open Set Material Prices - Sales. The Change Condition Records screen displays.
3. Navigate to initial screen. Enter Condition Type YK07, choose menu path: More Condition Create and
choose Enter .
4. The Create Price (YK07): Fast Entry screen displays.
5. Maintain condition record for Customer with release status. Enter the following data and choose Save:
• Sales Org. (of Order): for example, 1710
• Distribution Channel: for example, 10
• Customer: for example, 10411010
• Amount: for example, 20.000-
• Unit: %
6. The Customer Discount condition record is saved.

Setting Up Advanced Intercompany Sales (5D2)

28 PUBLIC Master Data Setup
3.6 Maintain Standard Purchase Info Record

Purpose

This process step shows you how to maintain the standard purchase info record.

If the Info Record for the material TG12 and suppliers 17411710 already exists in the system, you can skip this
step.

Procedure

1. Log on to the SAP Fiori launchpad with user the role SAP_BR_PURCHASER with name PURCHASER.
2. Open Create Purchasing Info Record.
3. Make the following entries in the Initial Screen:
• Supplier: 17411710
• Material: TG12
• Purchasing Organization: 1010
• Plant: 1010
• Purchasing Group: 001
• Info Category: Standard
4. Make the following entries in General Data:
• Order Unit: EA
• Var. Order Unit: 2 (Active with own price)

 Note

Please enter value “2” directly in the field. The value is not available via the dropdown list.

• Available From: Today

• Available To: 31.12.9999
5. Make the following entries in Purchasing Data Tab:
• Delivery Time in Days: 1
• Under Delivery Tolerance in %: 10.0
• Over Delivery Tolerance in %: 10.0
• Standard Order Quantity: 10
• Goods-Receipt-Based Invoice Verification: select
• No Evaluated Receipt Settlement: select
• Tax Code: <Input tax code>, for example, V1
• Tax Rate Valid From: Select value from F4 help
When the TDT (time dependent tax) is activated via SSCUI 101016 (Define Tax Codes for Sales and
Purchases) for Country of company code and Tax Code is given, the Tax Rate Valid From field is mandatory.

Setting Up Advanced Intercompany Sales (5D2)

Master Data Setup PUBLIC 29
 You can enter current date, which will be adjusted to validity start date of tax code according to the settings
in SSCUI.
• Incoterm: EXW
• Incoterm Location 1: VENDOR
6. In the Conditions section, choose Create.
Then in the General Information area, make the following entries:
• Valid From: Today
• Valid To: 12.31.9999
• Amount: 11.35
• Currency: EUR
• Pricing Unit: 1
• Unit of measure: EA
7. Choose Save. The purchasing info record is created.

3.7 Maintain Export Tax Condition Record for Delivering

Company

Purpose

In this activity, you maintain the export tax condition records for country solution 5D2_US, if the export tax
condition records have not been pre-delivered in supplying country solution.

Procedure

1. Log on to the SAP Fiori launchpad with a user having role SAP_BR_ TAX_SPECIALIST with name Tax
Specialist.
2. Choose Set Tax Rates – Sales. The Change Condition Records screen displays.
3. Navigate to initial screen. Enter Condition Type UTXJ, choose menu path: More Condition Create and
choose Enter . The Key Combination screen displays.
4. Choose the option Departure Country/ Destination, select Choose. The Create Output Tax Condition (UTXJ):
Fast Entry screen displays.
5. Please contact your Tax Experts of the countries to maintain the required export tax condition records from US
to DE with the detailed information.

Setting Up Advanced Intercompany Sales (5D2)

30 PUBLIC Master Data Setup
4 Configuration

4.1 Define Business Partner for Company Code

Purpose

This process step shows you how to assign an internal customer number for intercompany billing to your sales
organization.

The customer number being assigned to the sales organization of the selling company is used as the customer
(sold-to-party) in the sales order in the delivering company.

The customer number being assigned to the sales organization of the delivering company is used to determine the
supplier number being used to create the intercompany supplier invoice. The supplier number is determined from
the field “Vendor” in the customer master.

If the configuration is already available, this step can be skipped.

Prerequisite

Business partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (refer to the Master Data Setup chapter).

Procedure

1. Enter transaction S_ALR_87007590 or use SAP IMG path Sales and Distribution Billing Intercompany
Billing Define Internal Customer Number By Sales Organization .
2. Assign your internal customer number to the Sales Organization, and choose Save.

Sales org. CustInterC

1710 17401010

1010 10401010

Setting Up Advanced Intercompany Sales (5D2)

Configuration PUBLIC 31
4.2 Define Shipping Data for Plants

Purpose

The purpose of this activity is to assign a customer number to the delivering plant.

This customer number is used as sold-to-party in the sales order in the delivering company.

If the configuration is already available, this step can be skipped.

Prerequisite

Business Partners with all needed data parts for BP customer have been created for both selling company and
delivering company (Please refer to Master Data chapters for more details).

Procedure

1. Enter transaction S_ALR_87002189 or use SAP IMG path Materials Management Purchasing Purchase
Order Set up Stock Transport Order Define Shipping Data for Plants .
2. Assign your internal customer number to the plant, and choose Save.

Plant Customer Number Plant SlsOrg.Int.B. DistChannelIB Div.Int.Billing Language Key

1010 10411010 EN

4.3 Assign Tax Code

Purpose

In this activity, you assign tax rates and tax types as sent by your invoicing party to tax codes defined in the system.

If the configuration is already available, this step can be skipped.

Setting Up Advanced Intercompany Sales (5D2)

32 PUBLIC Configuration
Prerequisite

The required tax codes have been activated in the system.

Procedure

1. Enter transaction S_ER9_52000770 or use SAP IMG path Materials Management Logistics Invoice
Verification Electronic Data Interchange (EDI) SOAP Services Assign Tax Codes for the Transfer of
Supplier Invoices .
2. Click New Entries.
3. Make the following entries and choose Save:

Invoicing Party Tax Type Tax Rate Country / Region Key Tax Code

e.g. “” VAT 0,000000 DE V0

e.g. “” VAT 7,000000 DE V2

e.g. “” VAT 19,000000 DE V1

4.4 Program Parameters for Supplier Invoice

The purpose of this activity is to configure and assign program parameters to transfer supplier invoice data with a
SOAP service.

4.4.1 Configure Program Parameters

Purpose

Configure the program parameters to transfer supplier invoice data with a SOAP service.

If the configuration is already available, this step can be skipped.

Setting Up Advanced Intercompany Sales (5D2)

Configuration PUBLIC 33
Procedure

1. Enter transaction S_ER9_52000920 or use SAP IMG path Materials Management Logistics Invoice
Verification Electronic Data Interchange (EDI) SOAP Services Configure Program Parameters .
2. Click New Entries.
3. Make the following entries and choose Save:

Program Pa-
rameter Check Nega- Enable At-
Configura- Invoice doc. Cred. Memo Check Mate- Check Unit tive Varian- tachment
tion ID type doc. Type Processing rial Number of Measure ces Transfer

DEFAULT RE RE No Error “” “” “” “”

The option “Enable Attachment Transfer” is not relevant for intercompany processes and you can ignore it. You
can leave this data as “Checked”, for example in case B2B SOAP Service is in use and it requires an attachment.

4.4.2 Assign Program Parameters

Purpose

Assign the configuration ID to the corresponding invoicing party to transfer supplier invoice data with a SOAP
service.

If the configuration is already available, this step can be skipped.

Procedure

1. Enter transaction S_ER9_52000921 or use SAP IMG path Materials Management Logistics Invoice
Verification Electronic Data Interchange (EDI) SOAP Services Assign Program Parameters .
2. Click New Entries.
3. Make the following entries and choose Save:
• Invoicing Party: “”
• Program Parameter Configuration ID: DEFAULT

Setting Up Advanced Intercompany Sales (5D2)

34 PUBLIC Configuration
4.5 Define Output Determination

Purpose

In this activity, you should check that intercompany invoices (e.g., invoice type “IV2”) are not send via channel
IDOC.

Intercompany supplier invoices will be created automatically by the system. The creation is independent on the
output management of the intercompany customer invoice.

You can use Transaction “VV32 – Change Output – Condition Record Billing” to adjust your condition records.

Procedure

1. Enter transaction VV32.

2. Create or change relevant condition records.

4.6 Assign Transit Plant to Company Code

Purpose

To run advanced intercompany sales process, customer needs to assign a transit plant to the selling company
code.

The Transit Plant is used in the sales order of the selling company.

If the configuration is already available, this step can be skipped.

Prerequisite

The company code owning the transit plant needs to be same as the company code to which the transit plant is
assigned.

Setting Up Advanced Intercompany Sales (5D2)

Configuration PUBLIC 35
Procedure

1. Enter transaction S_ER9_11002020 or use SAP IMG path Enterprise Structure Assignment Logistics
General Assign Transit Plant to Company Code (Advanced ICO) .
2. Assign the Transit Plant to the Company Code, and choose Save:

CoCd Transit Plant

1010 1010

4.7 Define Purchase Order Defaults for Sales Organization

Purpose

To run advanced intercompany sales process, customer needs to assign a purchasing organization and a
purchasing group to the Sales Organization of the advanced intercompany sales order.

The purchasing organization and purchasing group is used to create the Purchase Order in the Selling Company.

 Note

If the configuration is already available, this step can be skipped.

Prerequisite

The purchasing organization and purchasing group configuration is available.

Procedure

1. Enter transaction S_ER9_52002871 or use SAP IMG path Materials Management Purchasing Purchase
Order Advanced Intercompany Processes Purchase Order Defaults in Advanced Intercompany Sales
2. Assign the correct POrg (Purchase Organization), PGr (Purchase Group) and OTyp (Order Type) to SOrg. (Sales
Organization). The Order Type should always be entered with NBAI. The following is a data example.

Setting Up Advanced Intercompany Sales (5D2)

36 PUBLIC Configuration
 SOrg. POrg POrg OTyp

1010 1010 001 NBAI

Then choose Save. A system dialog may pop up for transport request, choose the right transport request and
press Enter .

3. Purchase Order Default data has been assigned to the Sales Organization.

4.8 (Optional) Configure Posting Date for Processing

Advanced Intercompany Invoices

Purpose

In this activity, you can define for each individual invoicing party which date is to be used for the posting date of the
invoice:

• If you leave the Invoicing Party field blank but specify a value for the posting date, this posting date is used for
all invoicing parties that are not explicitly specified.
• If neither a specific entry nor a default entry exists for an invoicing party, the billing date from the referenced
billing document is used as the default behavior.

 Note

If the configuration is already available, skip this step. This activity is optional.

Prerequisite

The business partner is created for the invoicing party.

Procedure

1. Enter transaction S_ER9_52004323 or use SAP IMG path Materials Management Logistics Invoice
Verification Advanced Intercompany Processes Configure Posting Date for Advanced Intercompany
Invoices .
2. Choose New Entries to switch to the insert mode.

Setting Up Advanced Intercompany Sales (5D2)

Configuration PUBLIC 37
3. Enter a business partner in the field Invoicing Party and select an option for the field Posting Date of Invoices.
The following is an example:

Invoicing Party Posting Date of Invoices

17101010 Billing Document Date

4. Choose Save. A system window may pop up for transport request, choose the right transport request and
press Enter .
The Posting Date option for Processing Advanced Intercompany Invoices has been saved.

4.9 Activate Advanced Intercompany Sales Process for Sales

Document Types and Item Categories

Purpose

Advanced intercompany sales process is disabled for the standard document types and item categories by pre-
delivered configurations. The pre-delivered configurations must be enabled. Only with this configuration enabled,
the Advanced Intercompany Sales process is activated.

If the configuration is already available, this step can be skipped.

Prerequisite

All the above settings and configurations have been completed.

Procedure

1. Enter transaction S_ER9_52002646 or use SAP IMG path Sales and Distribution Sales Sales Documents
Integration with Value Chain Management Assign Document Type and Item Category to Value Chain .
2. Enable all Sales Order Type and Item Category combinations that are relevant for advanced intercompany
sales, and choose Save:

Value Chain Sales Doc. Type Item Cat. Enabled

IC_SALES OR TAN X (enabled)

Setting Up Advanced Intercompany Sales (5D2)

38 PUBLIC Configuration
 Value Chain Sales Doc. Type Item Cat. Enabled

IC_SALES OR CBXN X (enabled)

IC_SALES CBFD CBXN X (enabled)

Setting Up Advanced Intercompany Sales (5D2)

Configuration PUBLIC 39
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Setting Up Advanced Intercompany Sales (5D2)

40 PUBLIC Important Disclaimers and Legal Information
Setting Up Advanced Intercompany Sales (5D2)
Important Disclaimers and Legal Information PUBLIC 41
www.sap.com/contactsap

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN