Intercompany Stock Transfer: Setting Up (1P9)

Set-Up Instructions | PUBLIC
SAP S/4HANA Cloud

2021-12-22
Setting Up Intercompany Stock Transfer (1P9)

© 2021 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 General Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1.2 Business Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Organizational Setup - General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Domestic Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
International Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Organizational Setup - Intercompany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Assign Sales Organization/Distribution Channel to Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Assign Organizational Unit to Delivering Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assign Picking Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Localization Highlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Master Data Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1 Create/Extend Business Partners for Domestic Business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Business Partners Representing the Company Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Create/Extend Business Partners Representing the Plants Codes. . . . . . . . . . . . . . . . . . . . . . . . . . .21
4.2 Create/Extend Business Partners for International Business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Business Partners Representing the Company Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Create/Extend Business Partners representing the Plants Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Enhance/Extend Material Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Enhance Material Master in Ordering Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Extend Material Master in Supplying Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
4.4 Maintain Intercompany Condition Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1 Define Shipping Data for Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2 Define Internal Customer Number By Sales Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
5.3 Define Business Rules for Output Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

2 PUBLIC Content
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.2 Business Context
Intercompany scenarios allow for data exchange and highly-automated posting logics for business transactions
between companies (for example, company codes) sharing the same system and client.
In order to make use of such intercompany scenarios, at least two company codes are needed, which are installed
in the same system and client.
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 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 (for example, the SRS already provides business
partners with predefined IDs which do represent the country solution’s standard company code) are set up as
described in the next paragraphs.
 Note
For internal business partner creation to represent company code and plant, only the grouping with external
number range are used. The purpose is to ensure business partner dependent configurations are consistent in
quality system and production system.

Purpose PUBLIC 3
2 Preparation
2.1 Organizational Setup - General
2.1.1 Domestic Setup
Intercompany stock transfer processes require business between two company codes. The activation of one
country solution provides one company code with related organizational structure.
It is necessary to set up a second organizational structure in the same country code for running business in an
additional company code for intercompany stock transfer business.
The following example refers to intercompany stock transfer (1P9_DE). Check if the following organizational
assignments have been maintained in the system.
Extend Organization structure Original (DE) Example for Second Organization Entity (DE)
Company 1010 1020
Company Code 1010 1020
Assign Company Code to Company 1010 to 1010 1020 to 1020
Assign company code to controlling 1010 to A000 1020 to A000

area
Define Plant / Assign Plant to Com 1010 / 1010 to 1010 1030 / 1030 to 1020
pany Code
Maintain Purchasing Organization / 1010 / 1010 to 1010 1030/ 1030 to 1020

Assign Purchasing Organization to
Company Code
Assign Purchasing Organization to 1010 to 1010 1030 to 1030

Plant
Define Sales Organization / Assign 1010 / 1010 to 1010 1030 / 1030 to 1020
Sales Organization to Company Code
Assign Distribution Channel to Sales 10 to 1010 10 to 1030

Organization (Distribution Chain)
Sales Office 100 N/A

4 PUBLIC Preparation
Extend Organization structure Original (DE) Example for Second Organization Entity (DE)
Sales Group / Assign Sales Group to 100 / 100 to 100 N/A

Sales Office
Set up Sales Area 1010/10/00 1030/10/00
Assign Sales Office to Sales Area 100 to 1010/10/00 N/A
Shipping Point 1010 1030
Assign Shipping Point to Plant 1010 to 1010 1030 to 1030
Storage Location 101A 103A
Assign Storage Location to Plant 101A to 1010 103A to 1030
Assign Sales Organization - Distribu 1010/10 to 1010 1030/10 to 1030

tion Channel (Distribution Chain) to
Plant
Assign Shipping Condition/Loading 01/0001/1010/1010 01/0001/1030/1030

Group/Plant to Shipping Points
 Note
: Use Shipping Point Assignment configure
SSCUI to maintain this entry.
Assign Shipping Point/Plant/Storage 1010/1010/<space> to 101A 1030/1030/<space> to 103A

Condition to Picking Locations
 Note
: If this activity is not extended via SSCUI
detailed steps are described in the later As
sign picking locations chapter.
Solution content for your country including scope items (at least Intercompany Stock Transfer 1P9) is activated in
your client.
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:
● Manage Your Solution:

In the SAP S/4HANA Cloud system, in the SAP Fiori launchpad, open the Manage Your Solution app and go to
View Solution Scope.
● SAP Central Business Configuration:
In the Scope and Organizational Structure phase, navigate to the Activities tab. Search for Define Scope and
choose Open.

Preparation PUBLIC 5
The minimal structure data for second organization entity listed above is extended in your client, for example, via
flex-org tool or SSCUI, details you can refer to this link:
https://go.support.sap.com/roadmapviewer/#/group/BE47098A-617A-43EF-A27E-DFD801D70483/roadmap/
IMPS4HANACLDENMGMT/phase/001999B7BD851ED68D97F853D2C742CE/node/
001999B7BD851ED68D97F853D2CD02CE
Any issue in extending organizational structure phase, please create message using the component SV-CLD-FRM-
APP .
2.1.2 International Setup
Intercompany stock transfer processes require business between two company codes. With the activation of two
country solutions the required two company codes with related organizational structure are provided
The following example refers to intercompany stock transfer (1P9_DE and 1P9_US).
Check, if the following organizational assignments have been maintained in the system.
Original (US)
Extend Organization Structure Original (DE)
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 Com 1010 / 1010 to 1010 1710 / 1710 to 1710
pany Code
Maintain Purchasing Organization / 1010 / 1010 to 1010 1710 / 1710 to 1710

Assign Purchasing Organization to
Company Code
Assign Purchasing Organization to 1010 to 1010 1710 to 1710

Plant
Define Sales Organization / Assign 1010 / 1010 to 1010 1710 / 1710 to 1710
Sales Organization to Company Code
Assign Distribution Channel to Sales 10 to 1010 10 to 1710

Organization (Distribution Chain)
Sales Office 100 170
Sales Group / Assign Sales Group to 100 / 100 to 100 170/ 170 to 170
Sales Office

Original (US)
Extend Organization Structure Original (DE)
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 1010 1710
Assign Shipping Point to Plant 1010 to 1010 1710 to 1710
Storage Location 101A 171A
Assign Storage Location to Plant 101A to 1010 171A to 1710
Assign Sales Organization - Distribu 1010/10 to 1010 1710/10 to 1710

tion Channel (Distribution Chain) to
Plant
Assign Shipping Condition/Loading 01/0001/1010/1010 01/0001/1710/1710

Group/Plant to Shipping Points
Assign Shipping Point/Plant/Storage 1010/1010/<space> to 101A 1710/1710/<space> to 171A

Condition to Picking Locations
Solution content for your country including scope items (at least Sell from Stock 1P9) is activated in your client.
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:
● Manage Your Solution:

In the SAP S/4HANA Cloud system, in the SAP Fiori launchpad, open the Manage Your Solution app and go to
View Solution Scope.
● SAP Central Business Configuration:
In the Scope and Organizational Structure phase, navigate to the Activities tab. Search for Define Scope and
choose Open.
The minimal structure data for seond organization entity listed above is extended in your client, for example, via
flex-org tool or SSCUI, details you can refer to this link:
https://go.support.sap.com/roadmapviewer/#/group/BE47098A-617A-43EF-A27E-DFD801D70483/roadmap/
IMPS4HANACLDENMGMT/phase/001999B7BD851ED68D97F853D2C742CE/node/
001999B7BD851ED68D97F853D2CD02CE
Any issue in extending organizational structure phase, please create message using the component SV-CLD-FRM-
APP.

2.2 Organizational Setup - Intercompany
2.2.1 Assign Sales Organization/Distribution Channel to Plant
Purpose
To run intercompany business, you need to define the allowed relationships. A plant of one affiliate can be assigned
to several sales organizations of another affiliate.
Prerequisites
The plant and sales organization/distribution channel have already been created via flex-org tool.
Procedure
Configure Your Solution:
1. Log on to the SAP Fiori launchpad using SAP_BR_BPC_EXPERT business role to access the Manage Your Solution
App by opening the tile.
2. Select Configure Your Solution on the Manager Your Solution screen. Configure Your Solution screen displays.
 Note
Select Set Local Version to create country-/region-dependent settings for the intended local version.
3. Enter Organization in the searching input box and press Enter , the list of Configuration Items is displayed.
4. In Configuration Items subarea, choose Organization, the Configuration Your Solution – Organization screen
displays.
5. Choose Configure of the Assign sales organization - distribution channel - plant column, the Change View
Assignment Sales Organization/Distribution Channel – Plans screen displays.
6. Choose the New Entries function to enter your organizations required combinations of selling sales organizations
and delivering plants like the following sample data, choose Save:
SOrg. DCHCust/Mt Plnt
1010 10 1030
1030 10 1010

1710 10 1730
1730 10 1710
SAP Central Business Configuration:
1. Log on to the project experience in SAP Central Business Configuration.

2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. Search for Assign sales
organization - distribution channel - plant.
3. Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration.
4. Choose the New Entries function to enter your organizations required combinations of selling sales
organizations and delivering plants like the following sample data, choose Save:
1010 10 1030
1030 10 1010
1710 10 1730
1730 10 1710
2.2.2 Assign Organizational Unit to Delivering Plant
Purpose
To run intercompany business, you need to define the allowed relationships. A plant of one affiliate can be assigned
to several sales organizations of another affiliate.
Prerequisites
The plant and sales organization/distribution channel have already been created via flex-org tool.

Procedure
1. Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role to access the Manage Your Solution
app by opening the tile.
 Note
3. Search for the following configuration step: Organization. Choose Go. In the search result, select the
configuration item and go to the next screen.
4. On the Configure Your Solution – Organization screen, go to the configuration step Organizational Structure and
choose Configure.
6. Select Company Code for example, 1020 in Organization Hierarchy subarea, then select Plant Code, for example,
1030 in dropdown list, the Plant subscreen displays.
7. In Relationships subarea, choose Add Relationships, the Add Relationships for plant XXX screen displays:
8. Choose Sales Areas in the tab, select the sales area, for example, 1030:10:00(1030:10:00) in Sales Areas
subscreen, and then choose OK. The Sales Area(x):For intercompany billing in Plant subarea displays.
In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Go to App.

2. In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Go to App.
3. In the Configuration Activities cloumn, search for Define Shipping Data for Plants (edit only) and choose the line
item.
4. On the Display View "Stock Transport Order": Details screen, enter the following values and choose Save:
○ SlsOrg.Int.B: DE01
○ DisCgabbelIB: 10
○ Div.Int.Billing: 00

2.2.3 Assign Picking Locations
Purpose
The purpose of this activity is to assign picking location to shipping point / plant.
 Note
Ideally, this chapter is extended via flex-org tool or SSCUI in preparation phase. In case extension failed, you
can set up necessary relationship as below.
Prerequisites
The Shipping Points and Storage Locations have already been created for the plants via flex-org tool.
Procedure
1. Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role to access the Manage Your Solution
 Note
3. Enter Picking in the searching input box and choose Enter , the list of Configuration Items is displayed:
4. Click the Supply Chain in Configuration Item surarea, the Configuration Your Solution – Picking screen displays:
5. Choose the Configure of the Assign Picking Location column , the Change View Picking Location Determination:
Overview screen displays:
6. Click the New Entries function to enter the following data, choose Save:
Table 1: Picking Location Determination

ShPt Plnt SC SLoc
1030 1030 ""(keep empty) 103A
1030 1030 10 103A
1030 1030 20 103A

Result: The Picking Location Determination data is saved for the new plant, new shipping points and storage
location.

2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. Search for Assign
Picking Location.
4. Choose New Entries and enter the following data, choose Save:
Table 2: Picking Location Determination

ShPt Plnt SC SLoc
1030 1030 ""(keep empty) 103A
1030 1030 10 103A
1030 1030 20 103A

3 Localization Highlight
In this setup documentation, country DE is taken as an example. In your implementation, replace the example data
with your own data.
1. Tax code & rate for countries:
0 and V0 are mentioned for sales and purchase tax code for DE. If you use the document for other countries, please
contact your Tax specialist and implementation consultant for tax related localization setting.
2. Define two companies relationship (who is sending, who is receiving):
3. Mater data for business partner:
The Business Partner, representing the local standard reference content company code/plant is created with a pre-
defined ID like ##40##10/##41##10 with ## being the 2-digit country code; for DE company codes: ##=10.
In case you will not use the reference content company code/plant along with the business partner ##40##10/
##41##10, you need to create the correct BP in your future productive system manually.

Localization Highlight PUBLIC 13
4 Master Data Setup
4.1 Create/Extend Business Partners for Domestic Business
4.1.1 Business Partners Representing the Company Codes
Purpose
In this section, business partners representing delivering and receiving companies need to be created/extended.
Business partners with same ID as on Q-quality, should be created in P-production system before Q2P transport of
Intercompany related configuration.
Business partner data for company codes 1010 and 1020 are respectively created/extended in the following
enterprise organizations:
● 10401010 in company code 1020, sales area 1030/10/00 and purchasing organization 1030.
After activity in this chapter, the business partner data representing each company code looks like this:
Business Partner ID Business Partner ID
10401010 (ID, Address, Bank data …) 10401020 (ID, Address, Bank data …)
Customer Company Code Data Customer Company Code Data
1010 (Rec.Acc., Currency …) 1020 (Rec.Acc., Currency …)
Supplier Company Code Data Supplier Company Code Data
Customer Sales Area Data Customer Sales Area Data
1010 / 10/ 10 (Sales tax …) 1030 / 10 / 10 (Sales tax …)
1030 / 10 / 10 (Sales tax …) 1010 / 10/ 10 (Sales tax …)
Purchasing Organization Data Purchasing Organization Data
1010 (Currency …) 1030 (Currency …)

14 PUBLIC Master Data Setup
4.1.1.1 Create Business Partner General Data
Purpose
Business Partner IDs must be created for all company codes, which are involved in intercompany business -
whether by receiving products from other company code or internal invoice from delivering company code.
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_BUPA_MASTER_SPECIALIST role to access the Maintain
Business Partner App by opening the tile..
2. Choose Create Organization (Ctrl + F5).
3. Enter the following data and choose Save.
Field Name Entry Value
Business Partner 10401020
Grouping BP03 External numeric numbering (higher

range)
Create in BP role 000000 Business Partner (Gen.)
Address tab
Title 0003 Company
Name for example, Company 1020
Search term 1/2 for example, COMP1020
Street/House number for example, Hauptstrasse/30
Postal Code/City for example, 69190/Walldorf
Country for example, DE
Region for example, BW
Time Zone for example, CET
Transportation Zone for example, 0000000002
Language for example, DE German
Identification tab
Legal form 01
Industry 91

Master Data Setup PUBLIC 15
4.1.1.2 Create/Extend Customer Company Code Data
Purpose
In this activity, you create the new Company Code data segment for Business Partner, which needed for the
“sister” company that wants to use the business partner in “Customer-related” FI postings.
Procedure
Business Partner App by opening the tile.
2. Open Business Partner. Enter the Business Partner ID to be enhanced (for example, 10401010) in the
Business Partner field and choose Enter.
3. Choose Switch between display and change (F6). Change Organization: 10401010 screen displays.
4. Create company code data.
Check if BP roleFLCU00 Customer (Fin.Accounting) exists. If not, extend FLCU00 to delivering company, (for
example, 1020).
Choose FLCU00 Customer (Fin.Accounting)(defined) in Change in BP role field.
 Note
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.
Go to Control tab and enter/check Trading partner (for example, 1010).
Navigate to the Company Code data screen(s) by choosing Company Code.
Choose Company Codes. Customer (Fin.Accounting) Change dialog box displays.
Choose Create.
In Company Codes table, add new entries below:
Company Code <Supplying company,code> for example, 1020
Customer X
Select above new entry (line) and choose Adopt.

5. The following table lists the most common fields which need to be populated. Local (country-specific)
adjustments need to be considered:
Customer: Account Management tab
Reconciliation Account for example, 12300000 (“Trade Receivables affiliated Compa

nies”)
Sort key for example, 009 “External doc. Number”
Customer: Payment Transactions tab
Terms of Payment for example, 0001 (“Payable immediately Due net”)
Save your entries. Customer code data for company code 1020 of business partner 10401010 is created.
6. Repeat above steps to create/extend company code data of further business partners, for example, create/
extend company code data in company codes 1010 and 1020 for business partner 10401020.
4.1.1.3 Create/Extend Customer Sales Area Data
Purpose
In this activity, you create the new sales area data segment, which is needed for the “sister” company that wants to
use the business partner in “internal invoice” sales billing.
Procedure
Choose Switch between display and change (F6). Change Organization: 10401010 screen displays.
3. Create sales area data. Check if FLCU01 Customer(defined) BP role exists. If not, extend FLCU01 to
delivering company, (for example, 1020).
Choose FLCU01 Customer(defined) in Change in BP role field.
 Note
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.

Navigate to the Sales Area data screen(s) by choosing Sales and Distribution.
Choose Sales Areas. Customer change: Sales Area dialog box displays.
Choose Create. In Sales Areas table, add new entries below:
Sales Organization <Supplying sales organization> for example, 1030
DistrChannel for example, 10
Division for example, 00
Select above new entry (line) and choose Transfer.
adjustments need to be considered. Select the proper tab.
Orders tab
Orders 01
Currency for example, EUR
Shipping tab
Delivery Priority 2
Shipping Conditions 01
Billing tab
Incoterms for example, EXW
Inco. Location 1 for example, Walldorf
Terms of Payment for example, 0001 (“Due net”)
Account Assignment group for example, 03 (“Affiliate Company Revenues)
Output Tax for example, 1 (“Liable for Taxes”) for country DE-Germany
and Tax Category TTX1
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
Save your entries. Customer code data for sales area 1030 /10/00of business partner 10401010 is created.
5. Repeat above steps to create/extend sales area data of further business partners, for example, create/extend
sales area data in company codes 1010/10/ 00 and 1030/10/10for business partner 10401020.

4.1.1.4 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 “sister”
company that wants to use the business partner in “Supplier-related” FI postings.
Procedure
4. Create company code data. Check if FLV00 Supplier (Fin.Accounting) BP role exists. If not, extend
FLV00 to delivering company, (for example,1020).
Choose FLV00 Supplier (Fin.Accounting)(defined) in Change in BP role field.
 Note
Navigate to the Company Code Data screen(s) by choosing Company Code.
Choose Company Codes. Supplier (Fin.Accounting) Change:Compnay Code dialog box displays.
Choose Create. In Company Codes table, add new entries below:
Company Code <Ordering company,code> for example, 1020
Vendor X
adjustments need to be considered.
Vendor: Account Management tab

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

nies”)
Vendor: Payment Transactions tab
6. Repeat above steps to create/extend company code data of further business partners for example, create/
4.1.1.5 Create/Extend Supplier Purchasing Organization

Data
Purpose
In this activity, you create the new purchasing organization data needed for the “sister” company tthat wants to use
the business partner in sales transaction.
Procedure
4. Create purchasing data. Check if FLVN01 Supplier (defined) BP role exists. If not, extend FLV01 to
 Note
You can only navigate to the Purchasing Data screen when you select this BP role as only in this case,
Purchasing is displayed.
Navigate to the Purchasing Data screen(s) by choosing Purchasing.
Choose Purchasing Organizations. Supplier create: Purchasing Organizations dialog box displays.

Choose Create.
In Purchasing Organizations table, add new entry below:
Purchasing Organization <Purchasing Organization in ordering company> for example,

1030
Purchasing Data tab
Order Currency for example, EUR
GR-Based Inv. Verification X
Partner Role 1 Supplier, for example, own ID
Partner Role 2 Ordering Address , for example, own ID
Save your entries. Customer code data for purchasing organization 1030 of business partner 10401010 is created.
6. Repeat above steps to create/extend purchase organization data of further business partners, for example,
create/extend purchase organization data under purchase organization 1010 and 1030 for business partner
10401020.
4.1.2 Create/Extend Business Partners Representing the

Plants Codes
Purpose
In this section, business partners 10411010 and 10411030 representing plants 1010 and 1030 are respectively
created/extended in organizations
● 10411010 in company code 1020, sales area 1030/10/00 and purchasing organization 1030

1010(Currency …) 1030 (Currency …)
 Note
The business partners should be created in P-production system before Q2P transport.
4.1.2.1 Create/Extend Business Partner General Data
Purpose
Business Partner IDs must be created for all company codes, which are involved in intercompany business -
whether by receiving products from other company code or internal invoice from delivering company code.
Procedure
2. Choose Create Organization (Ctrl + F5).
3. Enter the following data and choose Save.

Business Partner 10411030
Grouping BP03 External numeric numbering (higher range)
Create in BP role 000000 Business Partner (Gen.)
Address tab
Title 0003 Company
Name for example, Plant 1030
Search term 1/2 for example, Plant 1030
Street/House number for example, Hauptstrasse/30
Postal Code/City for example, 69190/Walldorf
Country for example, DE
Region for example, BW
Time Zone for example, CET
Transportation Zone for example, 0000000002
Language for example, DE German
Identification tab
Legal form 01
Industry 91
4. Repeat above steps to create/extend general data of further business partners, for example, create/extend
general data for business partner 10411010.
Purpose
In this activity, you create the new Company Code data segment for Business Partner, which needed for the
“sister” company that wants to use the business partner in “Customer-related” FI postings.
Procedure

4. Create company code data. Check if FLCU00 Customer (Fin.Accounting) BP role exists. If not, extend
FLCU00 to delivering company, (for example,1010).
 Note
Choose Company Codes. Customer (Fin.Accounting) Change: Company Codes dialog box displays.
Choose Create. In Company Codes table, add new entries below:
Company Code <Supplying company,code>, for example, 1010
Customer X

nies”)
extend company code data in company codes 1010 and 1020 for business partner 10411010; create/extend
company code data in company code 1020 for business partner 10411030.

Purpose
Procedure
4. Create sales area data. Check if FLCU01 Customer(defined) BP role exists. If not, extend FLCU01 to
 Note
Choose Create. In Sales Areas table, add new entries below:
Sales Organization <Supplying sales organization>, for example, 1010
Select above new entry (line) and choose Create.
Orders tab
Customer Group 01

Shipping tab
Delivery Priority 02
Billing tab
Account Assignment Group for example, 03 (“Affiliate Company Revenues)
Partner Role 1 Sold-to Party, for example, <own ID>
Partner Role 2 Bill -to Party, for example, <10401020>
Partner Role 3 Payer, for example, <10401020>
Partner Role 4 Ship-to Party, for example, <own ID>
6. Repeat above steps to create/extend sales area data of further business partners for example, create/extend
sales area data in sales area 1030/10/ 00 for business partner 10411010.
Purpose
Procedure

4. Create Company Code Data. Check if FLVN00 Vendor(Fin.Accounting) BP role exists. If not, extend FLN00
to delivering company, (for example, 1010).
 Note
Choose Company Codes. Supplier (Fin.Accounting) Change:Compnay Code dialog box displays.
Choose Create.
Company Code <Ordering company,code> for example, 1010
Vendor X

nies”)
extend company code data in company code 1020 for business partner 10411010.

Data
Purpose
In this activity, you create the new purchasing organization data needed for the “sister” company that wants to use
the business partner in sales transaction.
Procedure
4. Create purchasing data.
Check if FLVN01 Supplier (defined) BP role exists. If not, extend FLV01 to delivering company, (for example,
1010).
 Note
Go to Vendor:General Data tab and enter/check Plant (for example, 1030) field.
Choose Purchasing Organizations. Supplier create: Purchasing Organizations dialog box displays.
Choose Create.
Purchasing Organization <Purchasing Organization in ordering company>, for example,

1010
Select the proper tab.

Purchasing Data tab
Schema Grp Supp 02(“Vendor schema group Intercomp”)
Partner Role 1 VN, for example, own ID
Partner Role 2 PI, for example, 10401020
create/extend purchase organization data under purchase organization 1030 for business partner 10411010.
4.2 Create/Extend Business Partners for International

Business
4.2.1 Business Partners Representing the Company Codes
Purpose
In this section, business partners representing delivering and receiving companies need to be created/extended.
 Note
Business partners with same ID as on Q-quality, should be created in P-production system before Q2P
transport of Intercompany related configuration.
Business Partner data for company codes 1010 and 1710 are respectively created/extended in the following
enterprise organizations:
● 10401010 in Company code 1710, sales area 1710/10/00 and purchasing organization 1710.
● 17401710 in Company code 1010, sales area 1010/10/00 and purchasing organization 1010.

Purpose
In this activity, you create the new company code data segment for business partner, which needed for the “sister”
company that wants to use the business partner in “Customer-related” FI postings.
Procedure
Check if BP role FLCU00 Customer (Fin.Accounting) exists. If not, extend FLCU00 to delivering company, (for
example, 1710).

 Note
Go to Control tab and enter/check Trading Partner (for example, 1010).
Navigate to the Company Code Data screen by choosing Company Code.
Choose Company Codes. Customer (Fin.Accounting) Change:Company Code dialog box displays.
Choose Create.
Company Code Supplying company,code, for example, 1710
Customer X

nies”)
Purpose

Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_BUPA_MASTER_SPECIALIST role to Aaess the Maintain
3. Create sales area data.
Check if BP role FLCU01 Customer(defined) exists. If not, extend FLCU01 to delivering company, (for example,
1710).
 Note
Navigate to the Sales Area Data screen by choosing Sales and Distribution.
Choose Create.
In Sales Areas table, add new entries below:
Sales Organization Supplying sales organization for example, 1710
Orders tab
Orders 01
Shipping tab
Delivery Priority 2
Billing tab
Inco. Location 1 for example, Palo Alto

Terms of Payment for example, 0001 (“Pay Immediately w/o Deduction”)
Output Tax for example, 1 (“Liable for Taxes”) for country US-USA and Tax
Category UTXJ
Partner Role 2 Bill -to Party, for example, own ID
Partner Role 3 Payer, for example, own ID
5. Repeat above steps to create/extend sales area data of further business partners, for example, create/extend
sales area data in company codes 1010/10/ 00 for business partner 17401710.
Purpose
Procedure
2. Open Business Partner.
Enter the Business Partner ID to be enhanced (for example, 10401010) in the Business Partner field and
choose Enter.
Check if BP role FLVN00 Supplier (Fin.Accounting) exists. If not, extend FLV00 to delivering company, (for
example, 1710).
Choose FLVN00 Supplier (Fin.Accounting)(defined) Change in BP role field.

 Note
Go to Control tab and enter/check Trading Partner (for example, 1010).
Choose Company Codes. Supplier (Fin.Accounting) Change:Company Code dialog box displays.
Choose Create.
Company Code Ordering company,code, for example, 1710
Vendor X

nies”)
Vendor: Correspondence tab
Accounting Clerk for example, 01 (“…”)
Account with vendor (Supplier) for example, “…”

Data
Purpose
In this activity, you create the new purchasing organization data segment needed for the “sister” company tthat
wants to use the business partner in sales transaction.
Procedure
Check if BP role FLVN01 Supplier (defined) exists. If not, extend FLVN01 to delivering company, (for
example, 1710).
Choose FLV01 Supplier(defined) in Change in BP role field.
 Note
Choose Purchasing Organizations. Supplier Create: Purchasing Organizations dialog box displays.
Choose Create.
Purchasing Organization Purchasing Organization in ordering company, for example,

1710

Purchasing Data tab
Schema Grp Supp 02 (“Vendor schema group Intercomp”)
Partner Role 1 Supplier, for example, <own ID>
Partner Role 2 Ordering Address , for example, <own ID>
Save your entries. Supplier purchasing data for purchasing organization 1710 of business partner 10401010 is
created.
4.2.2 Create/Extend Business Partners representing the Plants

Codes
Purpose
In this section, business partners 10411010 and 17411710 representing plants 1010 and 1710 are respectively
created/extended in organizations:
● 10411010 in company code 1710, sales area 1710/10/00 and purchasing organization 1710
After activity in ths chapter, the business partner data representing each company code looks like this:

1010(Currency …) 1710 (Currency …)
 Note
The business partners should be created in P-production system before Q2P transport.
Purpose
In this activity, you create the new company code data segment for business partner, which needed for the “sister”
company that wants to use the business partner in “Customer-related” FI postings.
Procedure
4. Create company code Data.
Check if FLCU00 Customer (Fin.Accounting) BP role exists. If not, extend FLCU00 to delivering company, (for
example, 1010).
 Note

Choose Company Codes. Customer (Fin.Accounting) Change: Company Code dialog box displays.
Choose Create.
In Company Codes table, add new entry below:
Company Code Supplying company code, for example, 1010
Customer X

nies”)
extend company code data in company code and 1710 for business partner 10411010.
Purpose
Procedure

3. Create sales area data.
Check if BP role FLCU01 Customer(defined) exists. If not, extend FLCU01 to delivering company, (for example,
1710).
 Note
Choose Sales Areas. Customer Change: Sales Area dialog box displays.
Choose Create.
In Sales Areas table, add new entries below:
Sales Organization Supplying sales organization, for example, 1010
Orders tab
Orders 01
Shipping tab
Delivery Priority 2
Billing tab

Partner Role 2 Bill -to Party, for example, 17401710
Partner Role 3 Payer, for example, 17401710
5. Repeat above steps to create/extend sales area data of further business partners for example, create/extend
sales area data in company codes 1710/10/ 00 for business partner 10411010.
Purpose
Procedure
Check if BP role FLVN00 Supplier (Fin.Accounting) exists. If not, extend FLV00 to delivering company, (for
example, 1010).
Choose FLVN00 Supplier (Fin.Accounting)(defined) in Change in BP role field.
 Note

Choose Company Codes. Supplier (Fin.Accounting) Change:Company Code dialog box displays.
Choose Create.
Company Code Ordering company code, for example, 1010
Vendor X

nies”)

Data
Purpose
In this activity, you create the new purchasing organization data segment needed for the “sister” company that
wants to use the business partner in sales transaction.
Procedure
2. Open Business Partner.
Enter the Business Partner ID to be enhanced (for example, 17411710) in the Business Partner field and
choose Enter.

Check if BP role FLVN01 Supplier (defined) exists. If not, extend FLV01 to delivering company, (for example,
1710).
Choose FLVN01 Supplier(defined) in Change in BP role.
 Note
Go to Vendor: General Data tab and enter/check Plant (for example, 1710) field.
Navigate to the Purchasing Data screen by choosing Purchasing.
Choose Purchasing Organizations. Supplier Create: Purchasing Organizations dialog box displays.
Choose Create.
Purchasing Organization <Purchasing Organization in ordering company>, for example,

1010
Purchasing Data tab
GR-Based Inv. Verification x
Schema Grp Supp 02 (“Vendor schema group Intercomp”)
Partner Role 1 VN, for example, own ID
Partner Role 2 PI, for example, 17401710

4.3 Enhance/Extend Material Master
4.3.1 Enhance Material Master in Ordering Company Code
Purpose
In the following sections, it is described what to do to enhance the trading material TG11 so that they can be used
in Intercompany stock transfer processing. If you want to use other materials in intercompany stock transfer
processing, you will have to do the enhancement steps for those materials accordingly.
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_PRODMASTER_SPECIALIST role to access the Change Material
2. Choose Create Material tile. Change Material (Initial Screen) displays.
3. Enter the following data and choose Continue:
Material for example, TG11
Select View(s) dialog box displays.
4. Select Purchasing and choose Continue:
Select view(s): Organizational levels dialog box displays.
5. Maintain following data and choose Continue:
Organizational levels subarea
Plant for example, 1010
Create Material screen displays.
Make the following data or actions and click on Save. Material data for the selected views is created in receiving
company.
Purchasing tab
Tax ind. F. material 1
6. Repeat the above steps from 3 to 6 to extend the batch material master, for example, TG21 or TG22 to the
ordering company code.

4.3.2 Extend Material Master in Supplying Company Code
Purpose
You enhance an existing material master so that it is available in supplying plant and distribution chain.
In the following sections it is described what to do to enhance the trading material TG11 so that they can be used in
intracompany stock transfer processing. If you want to use other materials in intracompany stock transfer
processing, you will have to do the enhancement steps for those materials accordingly.
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_PRODMASTER_SPECIALIST role to access the Create Material
2. Choose Create Material tile. Create Material (Initial Screen) displays.
3. Enter the following data and choose Continue:
Material Type for example, Trading Goods
Material (in subarea: Copy from…) for example, TG11--OPTIONAL (Copy from another org. level)
Select View(s) dialog box displays.
4. Select the following entries and choose Continue:
● Sales: Sales Org.Data 1

● Sales: Sales Org.Data 2
● Sales: General/Plant Data
● Purchasing
● General Plant Data / Storage 1
● General Plant Data / Storage 2
● Accounting 1
● Accounting 2
Select View(s): Organizational levels dialog box displays.
5. Maintain following data and choose Continue:
Organizational levels subarea
Storage location for example, 103A

Sales Org. for example, 1030
Distr.Channel for example, 10
Copy from subarea
Storage location for example, 101A
Sales Org. for example, 1010
Distr.Channel for example, 10
Create Material screen displays
6. Make the following data or actions and click on Save. Material data for the selected views is created in supplying
company.
Sales: Sales Org. 1 tab
Delivering Plant for example, 1030
Sales: Sales Org. 2 tab
All fields unchanged
Sales: General/Plant tab
Purchasing tab
Plant data / Stor. 1 tab
Plant data / Stor. 2 tab
Accounting 1 tab
Standard Price Change if needed
Per Unit Price Change if needed
Accounting 2 tab
7. Repeat the above steps from 3 to 7 to extend the batch material, for example, TG21 or TG22 to the supplying
company code.

4.4 Maintain Intercompany Condition Record
Purpose
In this activity, you maintain the intercompany condition record.
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_PRICING_SPECIALIST role to access the Set Material Prices
Sales App by opening the tile.
2. Choose Set Material Prices Sales tile. Change Condition Records displays.
3. Navigate to initial screen.
Enter Condition Type, PI01, choose menu path: More Condition Create and choose Enter.
Create Intercompany % Condition (PI01): Fast Entry screen displays.
4. Maintain condition record for Sales Org (for example, 1030) and Plant (for example, 1010) for domestic
business. Enter the following data and choose Save:
Sales Org. (of Order) for example, 1030
Amount for example, 15
Intercompany Condition Record is saved.
5. Repeat above steps with the following data for international business:
Sales Org. (of Order) for example, 1710
Amount for example, 15
Intercompany Condition Record is saved.
6. Repeat above steps from 4 to 6 to create intercompany pricing condition records for batch material master, for
instance, TG21 or TG22.

5 Configuration
5.1 Define Shipping Data for Plants
Purpose
The purpose of this activity is to define shipping data for plant (to allocate sales organization, distribution channel,
division and customer no.to the plant for which intercompany stock transfer processing is possible).
Prerequisites
Business Partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (Please refer to Master Data chapter).
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_BPC_EXPERT role.
2. Access the Manage Your Solution App by opening the tile.
Access via FIORI Launchpad
Business Role ID SAP_BR_BPC_EXPERT
APP Manage Your Solution
3. Select Configure Your Solution on Manager Your Solution screen. Configure Your Solution screen displays.
 Note
4. Enter Define Shipping Data for Plants in the searching input box and choose enter , the list of Configuration
Items is displayed.
5. Choose the Logistics in Configuration Item area, the Configuration Your Solution – Organization screen displays.
6. Choose Configure of the Define Shipping Data for Plants, the Change View Stock Transport Order: Overview
screen displays.

Configuration PUBLIC 47
7. Select and double click plant number field (for example, 1030). The Change View Stock Transport Order: Details
screen displays
8. Make the following entries and choose Save:
Detailed information
Customer No. Plant 10411030
SlsOrg.Int.B. 1030
DisChannelIB 10
Div.Int.Billing 00
Language for stock transport order texts
Language Key EN
The shipping data for plants are created.
9. Repeat above steps, assign the plant level business partner to the plant, for example, assign 10411010 to plant
1010.

2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. Search for Define
Shipping Data for Plants.
4. Make the following entries and choose Save:
Detailed information
Customer No. Plant 10411030
SlsOrg.Int.B. 1030
DisChannelIB 10
Div.Int.Billing 00
Language for stock transport order texts
Language Key EN
5. Repeat above steps, assign the plant level business partner to the plant, for example, assign 10411010 to
plant .

48 PUBLIC Configuration
5.2 Define Internal Customer Number By Sales Organization
Purpose
In this section, you assign an internal customer number for intercompany billing to your sales organization.
Prerequisites
Business Partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (Please refer to Master Data chapter).
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_BPC_EXPERT role.
2. Access the Manage Your Solution App by opening the tile.
Business Role ID SAP_BR_BPC_EXPERT
APP Manage Your Solution
3. Select Configure Your Solution on Manager Your Solution screen. Configure Your Solution screen displays.
 Note
4. Enter Organization in the searching input box and choose enter , the list of Configuration Items is displayed.
5. Choose the Organization in Configuration Item Area, the Configuration Your Solution – Organization screen
displays.
6. Choose Configure of the OrgStructure-configure column, the Organizational Structure screen displays.
7. Select the Company Code for example, 1010 in Organization Hierarchy area, then choose the Sales Area for
example, 1010 the dropdown list, the Sales Organizations screen displays.
8. Choose the Sales Organizations in Activities area, the Sales Organizations screen displays.

9. Choose Edit in Sales Organizations area, enter the following data in Customer Number for Intercompany Billing
field, and choose Save:
Field Name Field Name
Sales Org. 1030
Customer Number for Intercompany Billing 0010401030
In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.

2. In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.
3. In the Configuration Activities cloumn, choose Sales Organizations line item.
4. hoose Edit in Sales Organizations area, enter the following data in Customer Number for Intercompany Billing
field, and choose Save:
Sales Org. 1030
Customer Number for Intercompany Billing 0010401030
5.3 Define Business Rules for Output Determination
Purpose
In this activity, you can enter the allowed channels for billing document.
Procedure
1. Log on to the SAP Fiori launchpad using SAP_BR_ADMINISTRATOR role.
2. Access the Output Parameter Determination App by opening the tile.

50 PUBLIC Configuration
Business Role ID SAP_BR_ADMINISTRATOR
Name Administrator
APP Output Parameter Determination
3. Open Output Parameter Determination. The Output Parameter Determination screen displays.
4. In Select Business Rules subarea, choose the following data:
Show Rules for Billing Document
Determination Step Channel
Maintain Business Rules subarea displays.
5. In Maintain business rules subarea, choose Edit.
6. If there is not Billing Types field in Table Contents list, choose Table Settings in Table Contents. The Table Settings
screen displays.
7. On Table Setting screen, Condition Columns tab, choose Inset Column, select From Context Data Objects from
drop list. The Context Query screen displays.
8. Select Billing Types and choose OK, go back to Table Settings screen, and choose OK again, the Billing Type field
displays in the Table Contents list.
9. In Table Contents, choose + to insert new row.
10. Make the following entries and choose Check & Activate.
First entry
Output Type =BILLING_DOCUMENT (Billing Document)
Billing Type =CBST (Intercompany Billing for STO)
Channel PRINT（Printout）
Exclusive Indicator X (true)
Output channel for billing type CBST is created.

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 a 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.

52 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 53
www.sap.com/contactsap
© 2021 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

Intercompany Stock Transfer: Setting Up (1P9)

Uploaded by

Copyright:

Available Formats

You might also like

Intercompany Stock Transfer: Setting Up (1P9)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Intercompany Stock Transfer: Setting Up (1P9)

Uploaded by

Copyright:

Available Formats

Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

Setting Up Intercompany Stock Transfer (1P9)

THE BEST RUN

1.1 General Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

1.2 Business Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1 Organizational Setup - General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 Organizational Setup - Intercompany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Assign Sales Organization/Distribution Channel to Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Assign Organizational Unit to Delivering Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Assign Picking Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Master Data Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1 Create/Extend Business Partners for Domestic Business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Business Partners Representing the Company Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Create/Extend Business Partners Representing the Plants Codes. . . . . . . . . . . . . . . . . . . . . . . . . . .21

4.2 Create/Extend Business Partners for International Business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Business Partners Representing the Company Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Create/Extend Business Partners representing the Plants Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.3 Enhance/Extend Material Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Enhance Material Master in Ordering Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Extend Material Master in Supplying Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

4.4 Maintain Intercompany Condition Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.1 Define Shipping Data for Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.2 Define Internal Customer Number By Sales Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

5.3 Define Business Rules for Output Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Setting Up Intercompany Stock Transfer (1P9)

1.1 General Purpose

1.2 Business Context

Setting Up Intercompany Stock Transfer (1P9)

2.1 Organizational Setup - General

2.1.1 Domestic Setup

Company 1010 1020

Company Code 1010 1020

Assign Company Code to Company 1010 to 1010 1020 to 1020

Assign company code to controlling 1010 to A000 1020 to A000

Maintain Purchasing Organization / 1010 / 1010 to 1010 1030/ 1030 to 1020

Assign Purchasing Organization to 1010 to 1010 1030 to 1030

Assign Distribution Channel to Sales 10 to 1010 10 to 1030

Sales Office 100 N/A

Setting Up Intercompany Stock Transfer (1P9)

Sales Group / Assign Sales Group to 100 / 100 to 100 N/A

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

Assign Sales Office to Sales Area 100 to 1010/10/00 N/A

Shipping Point 1010 1030

Assign Shipping Point to Plant 1010 to 1010 1030 to 1030

Storage Location 101A 103A

Assign Storage Location to Plant 101A to 1010 103A to 1030

Assign Sales Organization - Distribu­ 1010/10 to 1010 1030/10 to 1030

Assign Shipping Condition/Loading 01/0001/1010/1010 01/0001/1030/1030

Assign Shipping Point/Plant/Storage 1010/1010/<space> to 101A 1030/1030/<space> to 103A

● Manage Your Solution:

Setting Up Intercompany Stock Transfer (1P9)

2.1.2 International Setup

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

Maintain Purchasing Organization / 1010 / 1010 to 1010 1710 / 1710 to 1710

Assign Sales Organization - Distribu 1010/10 to 1010 1030/10 to 1030

Assign Sales Organization - Distribu 1010/10 to 1010 1710/10 to 1710