Setting Up Advanced Intercompany Sales
Setting Up Advanced Intercompany Sales
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Assign Sales Organization/Distribution Channel to Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Assign Organizational Unit to Delivering Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assign Shipping Point Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Assign Picking Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
4 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1 Define Business Partner for Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2 Define Shipping Data for Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
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.
Abbreviation Explanation
SI Scope Item
BB Building Block
BBB Building Block Builder (functional part of the Solution Builder Tool)
Advanced Intercompany Sales scenario enables data exchange and highly automated posting logics for business
transactions between affiliates (represented by company codes) sharing the same tenant based on Value Chain
Management.
Depending on countries of company codes, we are delivering two SAP Best Practices scope items:
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
The SAP Best Practices sample data ID of such business partners are setup 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).
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 configurations are consistent in both
quality system and production system.
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.
2.1 Prerequisites
You must activate advanced intercompany sales process through SAP Expert Configuration procedure till an SSCUI
is developed. 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 [page 45].
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.
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)
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
Define Sales Organization / Assign Sales 1010 / 1010 to 1010 1710 / 1710 to 1710
Organization to Company Code
Sales Group / Assign Sales Group to 100 / 100 to 100 170 / 170 to 170
Sales Office
Solution content for your country including scope items (at least Sell from Stock BD9) is activated in your client.
The minimal structure data for the second organization entity listed above is extended in your client, for example,
via flex-org tool or SSCUI. For more 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
Note
Depending on your configuration environment, configuration steps can be accessed under Configure Your
Solution in the SAP Fiori launchpad or via the configuration activity in the Product-Specific Configuration phase
in the project experience of SAP Central Business Configuration.
If you encounter any issues in extending organizational structure phase, please create a customer case via the
component SV-CLD-FRM-APP.
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 another affiliate.
This assignment defines that a plant can be used as a delivering plant in sales orders of a sales organization and
distribution channel combination.
Prerequisites
The plant and sales organization/distribution channel have already been created via flex-org tool.
Procedure
1010 10 1710
1010 10 1710
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 via flex-org tool.
Procedure
1. Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role and 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 choose Enter, the list of Configuration Items is
displayed.
In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.
Purpose
For each plant, you can allocate shipping points to all combinations of shipping conditions and loading groups.
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. This step can be skipped if the configuration is already available in
the system.
Before you can allocate the shipping points, you must define plants, shipping points, shipping conditions, and
loading groups.
Procedure
Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role and to access the Manage Your
Solution App by opening the tile.
1. 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.
2. Enter Assign Shipping Points in the searching input box and choose Enter, the list of Configuration
Items is displayed.
3. Click the Supply Chain in Configuration Item s sub area, the Configuration Your Solution – Shipping Point and
Goods Selling Point Determination screen displays.
4. Choose the Configure of the Configuration Step Assign Shipping Points, the Change View Shipping Point
Determination : Overview screen displays.
5. Click the New Entries function to enter the following shipping point determination data, then choose Save:
Result: The Shipping Point Determination data is saved for the new plant, new shipping points, shipping
condition and loading group.
Purpose
Note
Ideally, this chapter is extended via flex-org tool or SSCUI in preparation phase. In case the extension failed, you
can set up necessary relationship as below. 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 via flex-org tool.
Procedure
1. Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role and 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.
Result: The Picking Location Determination data is saved for the new plant, new shipping points and storage
location.
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 code
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.
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 delivering company code.
Business partners with the 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 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.
10401010 (ID, Address, Bank data …) 17401710 (ID, Address, Bank data …)
After performing activity in this chapter, the business partner data representing each company code will look like
this:
10401010 (ID, Address, Bank data …) 17401710 (ID, Address, Bank data …)
1010 (Currency …)
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 Company Code data screen by choosing Company Code.
10. Choose Company Codes. The Customer (Fin.Accounting) Change: dialog box displays.
11. Choose Create. In the Company Codes table, add new entry as below:
• Company Code: <Supplying company code>, for example, 1710
• Customer: <select>
12. Select the above new entry (line) and choose Adopt.
13. The following table lists the most common fields that need to be populated. Make sure you consider local
(country-specific) adjustments as well.
14. Save your entries. Customer code data for company code 1710 of business partner 10401010 is created.
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 using 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 Area dialog box displays.
9. Choose Create. In the Sales Areas table, add new entry 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.
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.
Orders tab
Customer Group 01
Shipping tab
Delivery Priority 2
Shipping Conditions 01
Billing tab
12. Save your entries. Customer code data for sales area 1710/10/00 of business partner 10401010 is created.
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.
1. Log on to the SAP Fiori launchpad using role SAP_BR_BUPA_MASTER_SPECIALISTwith the name Master
Data Specialist - Business Partner Da.
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 entry 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.
13. Save your entries. Customer code data for company code 1010 of business partner 17401710 is created.
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 using 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:
10. Purchasing Organization: <purchasing organization in selling company>, for example, 1010
11. Select above new entry (line) and choose Transfer.
12. 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.
13. Save your entries. Supplier purchasing data for purchasing organization 1010 of business partner 17401710 is
created.
In this section, business partners 10411010 and 17411710 represent plants 1010 and 1710 which are respectively
created/extended in organizations:
After performing activities in this chapter, the business partner data representing each plant will be like this:
10411010 (ID, Address, Bank data …) 17411710 (ID, Address, Bank data …)
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 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 using SAP_BR_BUPA_MASTER_SPECIALIST role 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). 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.
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.
14. Save your entries. Customer code data for company code 1710 of business partner 10411010 is created.
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 using SAP_BR_BUPA_MASTER_SPECIALIST role 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). 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).
6. Choose FLCU01 Customer(defined)in Change in BP role field.
7. 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.
8. Navigate to the Sales Area data screen(s) by choosing Sales and Distribution.
9. Choose Sales Areas. Customer Change: Sales Area 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.
Orders tab
Customer Group 01
Shipping tab
Delivery Priority 2
Shipping Conditions 01
Billing tab
Output Tax for example, 0 ("Tax Exempt") for country US-USA and Tax Category UTXJ
Save your entries. Customer code data for sales area 1710 /10/00 of business partner 10411010 is created.
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 using SAP_BR_BUPA_MASTER_SPECIALIST role 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). 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.
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.
14. Save your entries. Customer code data for company code 1010 of business partner 17411710 is created.
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 using SAP_BR_BUPA_MASTER_SPECIALIST role 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). 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. Choose FLVN01 Supplier(defined) in Change in BP role.
Note
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.
9. Choose Purchasing Organizations. 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
Select 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.
14. Save your entries. Customer code data for purchasing organization 1010 of business partner 17411710 is
created.
In this section, you can extend end 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
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
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. 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). Change Organization: 1 0 100002 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.
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.
7. Navigate to the Sales Area data screen(s) by choosing Sales and Distribution.
8. Choose Sales Areas. Customer Change: Sales Area 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.
13. Select the proper tab.
Orders tab
Customer 01
Group
Cust. Pric. 02
Procedure
“” should be used if the sales organization is outside US.
Shipping tab
Delivery 2
Priority
Shipping 01
Conditions
Billing tab
Output Tax for example, 0 ("Tax Exempt") for country US-USA and Tax Category UTXJ
14. Save your entries. Customer code data for sales area 1010 /10/00 of business partner 17100002 is created.
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 using SAP_BR_PRODMASTER_SPECIALIST role to access the Change
Material App by opening the tile.
2. Choose Create Material tile. Change Material (Initial Screen) displays.
3. Enter the following data and choose Continue:
• Material : for example, TG12
4. Select View(s) dialog box displays.
5. Select Purchasing and MRP 2, then choose Continue.
6. Select view(s): Organizational levels dialog box displays.
7. Maintain following data and choose Continue:
8. Make the following data or actions and click on Save. Material data for the selected views is created in selling
company.
Purchasing tab
MRP 2 tab
9. Repeat the above steps from 3 to 6 to extend the batch material master, for example, TG21 or TG22 to the
selling company code.
Purpose
This process step shows you how to maintain customer discount condition record for affiliated ordering company
code.
Note
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 using role SAP_BR_PRICING_SPECIALIST 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, 10401010
• Amount: for example, 20.000-
• Unit: %
6. The Customer Discount condition record is saved.
Purpose
This process step shows you how to maintain the standard purchase info record.
Note
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 using role SAP_BR_PURCHASER with name PURCHASER.
2. Open Manage Purchasing Info Records. The Manage Purchasing Info Records screen displays.
3. Choose Create, the Purchasing Info Record Screen displays.
4. Make the following entries in Header Tab:
• Purchasing Info Record Category: Standard
• Purchasing Organization: 1010
• Plant: 1010
• Supplier: 17411710
• Material: TG12
• Purchasing Group: 001
5. Make the following entries in General Information Tab:
• Available From: Today
• Available To: 31.12.9999
6. Make the following entries in Purchasing Data Tab:
• Incoterm : EXW
• Incoterm Location 1 : VENDOR
7. Make the following entries in Delivery and Quantity Tab:
• Delivery Time in Days : 1
• Under Delivery Tolerance in % : 10.0
• Over Delivery Tolerance in % : 10.0
• Tax Code: <Input tax code>, e.g.
• Tax Rate Valid From : Select value from F4 help
Note
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
• Order Unit: PC
• Standard Order Quantity: 10
• Goods-Receipt-Based Invoice Verification: select
• No Evaluated Receipt Settlement: select
8. 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: 14.00
• Pricing Unit: 1
• Currency: EUR
• Choose Apply.
9. Choose Create. The purchasing info record is created.
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 using 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.
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.
All sales organizations within a company code must have the same business partner / customer assigned.
Note
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
In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.
Purpose
The purpose of this activity is to define shipping data for plant (to allocate sales organization, distribution channel,
division and internal customer no. to the delivering plant).
Note
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 [page 14] for more details).
Note
Select Set Local Version to create country-/region-dependent settings for the intended local version.
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.
7. Select and double click plant number field (for example, 1710). The Change View Stock Transport Order: Details
screen displays
8. Make the following entries and choose Save:
Detailed information
SlsOrg.Int.B. 1710
DisChannelIB 10
Div.Int.Billing 00
Language Key EN
9. Repeat above steps, assign the plant level business partner to the plant, for example, assign 10411010 to plant
1010.
Detailed information
SlsOrg.Int.B. 1710
DisChannelIB 10
Div.Int.Billing 00
Language Key EN
Purpose
In this activity, you assign tax rates and tax types as sent by your invoicing party to tax codes defined in the system.
Note
Prerequisite
Note
Select Set Local Version to create country-/region-dependent settings for the intended local version.
4. Enter Assign Tax Code in the searching input box and choose enter, the list of Configuration Items is displayed.
5. Choose the Item Name Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configure
Your Solution - Ariba Network Integration for Buyers (SOAP) screen displays.
6. Choose Configure of the Assign Tax Codes for the Transfer of Supplier Invoices, the Change View " Assign Tax
Codes for the Transfer of Supplier Invoices ": Overview screen displays.
7. Click New Entries, The New Entries: Overview of Added Entries screen displays.
8. Make the following entries and choose Save:
Invoicing Party Tax Type Tax Rate Country / Region Key Tax Code
Invoicing Party Tax Type Tax Rate Country / Region Key Tax Code
The purpose of this activity is to configure and assign program parameters to transfer supplier invoice data with a
SOAP service.
Purpose
Configure the program parameters to transfer supplier invoice data with a SOAP service.
Note
Procedure
Note
Select Set Local Version to create country-/region-dependent settings for the intended local version.
4. Enter Configure Program Parameters in the searching input box and choose Enter, the list of
Configuration Items is displayed.
5. Choose the item name Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configure
Your Solution - Ariba Network Integration for Buyers (SOAP) screen displays.
6. Choose Configure of the Configure Program Parameters, the Change View " Configure Program Parameters ":
Overview screen displays.
7. Click New Entries, the New Entries: Overview of Added Entries screen displays.
Note
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.
Program Parameter Invoice Cred. Processing Check Check Unit Check Neg Enable At
Configuration ID doc. type Memo Material of Measure ative Var tachment
doc. Type Number iances Transfer
Note
The option “Enable Attachment Transfer” is not relevant for intercompany processes and will be ignored.
Customer can leave the topic “on”, for example in case B2B SOAP Service is in use and there is such an
attachment requirement.
Purpose
Assign the configuration ID to the corresponding invoicing party to transfer supplier invoice data with a SOAP
service.
Note
Procedure
Note
Select Set Local Version to create country-/region-dependent settings for the intended local version.
4. Enter Assign Program Parameters in the searching input box and choose E nter, the list of Configuration
Items is displayed.
5. Choose the item name Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configure
Your Solution - Ariba Network Integration for Buyers (SOAP) screen displays.
6. Choose Assign Program Parameters, the Change View " Assign Program Parameters ": Overview screen
displays.
7. Click New Entries, The New Entries: Overview of Added Entries screen displays.
8. Make the following entries and choose Save:
• Invoicing Party: “”
• Program Parameter Configuration ID: DEFAULT
9. Assign Program Parameters entry is created.
Purpose
In this activity, you can define business rule for output determination on billing type IV2 and IV2S to exclude the
Channel IDOC. The billing type IV2 and IV2S are integrated with supplier invoice through API instead of IDOC.
Procedure
3. Open Output Parameter Determination. The Output Parameter Determination screen displays.
4. In Select Business Rules subarea, choose the following data:
Purpose
To run advanced intercompany sales process, customer needs to assign transit plant to the selling company code
via an expert configuration request.
The Transit Plant is used in the sales order of the selling company.
Note
Prerequisite
The company code owning the transit plant should be same as the company code to which the transit plant is
assigned in this step.
Procedure
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 via an expert configuration
request.
The purchasing organization and purchasing group is used to create the Purchase Order in the Selling Company.
Note
Prerequisite
Procedure
1. Log on to the SAP Fiori launchpad using the Configuration Expert - Business Process
Configuration role.
2. Access the Manage Your Solution app by opening the tile.
3. Choose Configure Your Solution on the Manager Your Solution screen. The Configure Your Solution screen
displays.
Note
Choose Set Local Version to create country-/region-dependent settings for the intended local version.
4. Enter Purchase Order Defaults in Advanced Intercompany Sales in the searching input box and choose Enter .
The list of All Items displays.
Then choose Save. A system dialog may pop up for transport request, choose the right transport request and
press Enter .
9. Purchase Order Default data has been assigned to the Sales Organization.
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 through an expert configuration
request. Only with this configuration enabled, the Advanced Intercompany Sales process is activated.
Prerequisite
Procedure
1. Raise an expert configuration request in WCR through Product Expert. In case there is no Product Expert
defined, you need to raise a customer case using the component SD-BIL-IV.
2. Please attach this excel where you have filled column "enabled" with "X" for all order type item category
combinations you need from the list.
OR TAN
OR CBXN
CBFD CBXN
3. Send it to SAP.
4. The WCR ticket will get the status “Done” when the expert configuration is done in your Q-environment.
5. Test the advanced intercompany sales process in Q system. Release BCP project to transport the expert
configuration to P system once the testing is confirmed.
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.
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.
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.