0% found this document useful (0 votes)
9 views

3HS Set-Up EN XX

Uploaded by

Jocelito Wagner
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views

3HS Set-Up EN XX

Uploaded by

Jocelito Wagner
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 42

Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud


2022-12-22

Setting Up Sales from Distribution Center (3HS)


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

THE BEST RUN


Content

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

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

3 Master Data Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12


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

4 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1 Define Business Partner for Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2 Assign Tax Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Setting Up Sales from Distribution Center (3HS)


2 PUBLIC Content
4.3 Program Parameters for Supplier Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configure Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Assign Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.4 Define Business Rules for Output Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.5 Assign Transit Plant to Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.6 Define Purchase Order Defaults for Sales Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
4.7 Activate Advanced Intercompany Sales Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Setting Up Sales from Distribution Center (3HS)


Content PUBLIC 3
1 Purpose

1.1 General Purpose

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

 Note

Advanced intercompany sales process is not supported in Czech Republic, Poland, Slovakia countries.

1.1.1 Main Abbreviations Used in the Document

Abbreviation Explanation

SI Scope Item

BB Building Block

BBB Building Block Builder (functional part of the Solution Builder Tool)

SRS Standard Reference Content

CBC Central Business Configuration

EBRR Event-Based Revenue Recognition

WCR World Customer Request

1.2 Business Context

Advanced Intercompany Sales scenario enables data exchange and highly automated posting logics for business
transactions between affiliates (represented by company codes) sharing the same tenant based on Value Chain
Management.

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

• Advanced Intercompany Sales process (5D2_DE)


• Advanced Intercompany Sales process (5D2_US)

Setting Up Sales from Distribution Center (3HS)


4 PUBLIC Purpose
• Sales from Distribution Center (3HS_DE)
• Sales from Distribution Center (3HS_US)

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

The SAP Best Practices sample data ID of such business partners 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 configuration is consistent in your entire
system landscape.

1.3 How to Work through this Document

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

Process Version Selling Company Code Delivering Company Code

Sales from Distribution Cen­ 3HS_DE 1010 1710


ter / AdvancedIntercompany
Sales Process

Setting Up Sales from Distribution Center (3HS)


Purpose PUBLIC 5
2 Preparation

2.1 Prerequisites

2.1.1 Activate Advanced Intercompany Sales

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 [page 39].

2.2 Organizational Setup - General

2.2.1 Organizational Setup

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

The following example refers to Advanced Intercompany Sales process (3HS_DE).

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

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

Company 1010 1710

Company Code 1010 1710

Assign Company Code to Company 1010 to 1010 1710 to 1710

Assign Company Code to Controlling 1010 to A000 1710 to A000


Area

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

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

Setting Up Sales from Distribution Center (3HS)


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

Assign Purchasing Organization to Plant 1010 to 1050 1710 to 1750

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

Assign Distribution Channel to Sales Or­ 50 to 1010 50 to 1710


ganization (Distr. Chain)

Sales Office 100 170

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

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

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

Shipping Point 1750

175R (for return)

Assign Shipping Point to Plant 1750 to 1750

Storage Location 995A

Assign Sales Organization - Distribution 1710/10 to 1750


Channel to Plant

2.3 Organizational Setup – Advanced Intercompany Sales

2.3.1 Assign Sales Organization/Distribution Channel to Plant

Purpose

This process step shows you how to define the allowed relationships for running advanced intercompany business.
A plant of one affiliate can be assigned to several sales organizations of 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.

Setting Up Sales from Distribution Center (3HS)


Preparation PUBLIC 7
Prerequisites

The plant and sales organization/distribution channel have already been created via flex-org tool.

Procedure

1. Log on to the project experience in SAP Central Business Configuration.


2. In the Scope and Organizational Structure phase, navigate to the Activities tab. Search for app Set Up
Organizational Structure, and choose Open.
3. On the Set Up Organizational Structure screen, enter plant code in the search box and press Enter . The plant
node displays.
4. Choose the plant node, and the Edit Plant view displays.
5. Expand Plant to Sales Organization and Distribution Channel, and choose Create Assignment. The Create
Assignment dialog box displays.
6. Select combinations of sales organizations and delivering plants required by your organizations like the
following sample data. Choose Save.

Plant Assign Sales Organization Assign Channel/s

1030 1010 10

1010 1030 10

1730 1710 10

1710 1730 10

2.3.2 Assign Organizational Unit to Delivering Plant

Purpose

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

Prerequisite

The Delivering plant and sales area have already been created via flex-org tool.

Setting Up Sales from Distribution Center (3HS)


8 PUBLIC Preparation
Procedure

SAP Central Business Configuration:

In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.

1. Log on to the project experience in SAP Central Business Configuration.


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 column, search for Define Shipping Data for Plants (edit only) and choose the line
item.
4. 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.
5. On the Display View "Stock Transport Order": Details screen, enter the following values and choose Save:
• SlsOrg.Int.B: 1010
• DisCgabbelIB: 10
• Div.Int.Billing: 00

Repeat above steps to maintain sales area 1710:10:00 to plant 1750.

2.3.3 Assign Shipping Point Determination

Purpose

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

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

Prerequisites

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

Setting Up Sales from Distribution Center (3HS)


Preparation PUBLIC 9
Procedure

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
Shipping Points.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Choose New Entries and enter the following data, choose Save:

Table 1: Table 2: Shipping Point Determination

Shipping Loading Plant Pro­


Condi­ Group posed
tion Shipping
Point

01 0001 1750 1750

01 0002 1750 1750

01 0003 1750 1750

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

Setting Up Sales from Distribution Center (3HS)


10 PUBLIC Preparation
Procedure

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
Picking Location.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Choose New Entries and enter the following data, choose Save:

Table 2: Table 2: Picking Location Determination

ShPt Plnt SC SLoc

1750 1750 ""(keep empty) 995A

1750 1750 10 995A

1750 1750 20 995A

Setting Up Sales from Distribution Center (3HS)


Preparation PUBLIC 11
3 Master Data Setup

3.1 Create/Extend Business Partners Representing Affiliate


Company Codes

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

Intercompany Invoice

In intercompany sales process, the delivering company issues an intercompany invoice to the selling company 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.

Intercompany Invoice Receipt

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

Create a business partner to represent the supplying company code.

Create business partners in production system with the same ID in your configuration system, before transporting
intercompany related configuration to the production system.

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

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

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

Business Partner ID Business Partner ID

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

Customer Company Code Data Customer Company Code Data

Setting Up Sales from Distribution Center (3HS)


12 PUBLIC Master Data Setup
Business Partner ID Business Partner ID

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

Supplier Company Code Data Supplier Company Code Data

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

Customer Sales Area Data Customer Sales Area Data

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

Purchasing Organization Data Purchasing Organization Data

1010 (Currency …) 1710 (Currency …)

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

Business Partner ID Business Partner ID

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

Customer Company Code Data Customer Company Code Data

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

1710 (Rec.Acc., Currency …)

Supplier Company Code Data Supplier Company Code Data

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

1010 (Rec.Acc., Currency …)

Customer Sales Area Data Customer Sales Area Data

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

1710/10/10 (Sales tax …)

Purchasing Organization Data Purchasing Organization Data

1710 (Currency …) 1710 (Currency …)

1010 (Currency …)

Setting Up Sales from Distribution Center (3HS)


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

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad using role SAP_BR_BUPA_MASTER_SPECIALIST with name Master Data
Specialist - Business Partner Data.
2. Open Maintain Business Partner.
3. Choose Business Partner. Enter the business partner ID to be enhanced (for example, 10401010) in the
Business Partner field and choose Enter.
4. Choose Switch Between Display and Change ( F6 ). The Change Organization: 10401010 screen displays.
5. Create company code data. Check if BP role FLCU00 Customer (Fin.Accounting) exists. If not, extend BP role
FLCU00 to delivering company, (for example, 1710).
6. Select FLCU00 Customer (Fin.Accounting) (defined) in the Change in BP role field.
7. You can only navigate to the Company Code Data screen when you select this BP role as only in this case the
Company Code button displays.
8. Go to the Control tab and enter / check Trading partner field (for example, 1010).
9. Navigate to the 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.

Field Name Entry Value

Customer: Account Management tab

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


panies")

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

Customer: Payment Transactions tab

Setting Up Sales from Distribution Center (3HS)


14 PUBLIC Master Data Setup
Field Name Entry Value

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

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

Customer: Correspondence tab

Accounting Clerk for example, 01 ("…")

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

3.1.2 Create/Extend Customer Sales Area Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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, 50
• 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.

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 15
Field Name Entry Value

Orders tab

Customer Group 01

Currency for example, EUR

Cust. Pric. Procedure 01

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

Shipping tab

Delivery Priority 2

Shipping Conditions 01

Billing tab

Incoterms for example, EXW

Inco. Location 1 for example, Palo Alto

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

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

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

Partner Functions tab

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

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

Partner Role 3 Payer: for example, own ID

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

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

3.1.3 Create/Extend Supplier Company Code Data

Purpose

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

Setting Up Sales from Distribution Center (3HS)


16 PUBLIC Master Data Setup
Procedure

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.

Field Name Entry Value

Vendor: Account Management tab

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


nies")

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

Vendor: Payment Transactions tab

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

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

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 17
3.1.4 Create/Extend Supplier Purchasing Organization Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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.

Field Name Entry Value

General Data view

Vendor: General Data tab

Customer 17401710

Purchasing Data tab

Order Currency for example, EUR

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

Setting Up Sales from Distribution Center (3HS)


18 PUBLIC Master Data Setup
Field Name Entry Value

GR-Based Inv. Verification <select>

Partner Functions tab

Partner Role 1 Supplier: for example, own ID

Partner Role 2 Ordering Address: for example, own ID

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

3.2 Create/Extend Business Partners representing Plants

In this section, business partners 1050 and 1750 represent plants 1010 and 1710 which are respectively created/
extended in organizations:

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


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

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

Business Partner ID Business Partner ID

1050 (ID, Address, Bank data …) 1750 (ID, Address, Bank data …)

Customer Company Code Data Customer Company Code Data

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

1010 (Rec.Acc., Currency …)

Supplier Company Code Data Supplier Company Code Data

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

1710 (Rec.Acc., Currency …)

Customer Sales Area Data Customer Sales Area Data

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

1010 / 10/ 10 (Sales tax …)

Purchasing Organization Data Purchasing Organization Data

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 19
Business Partner ID Business Partner ID

1010 (Currency …) 1710 (Currency …)

1710 (Currency …)

 Note

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

3.2.1 Create/Extend Customer Company Code Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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, 1050) in the Business
Partner field and choose Enter.
3. Choose Switch Between Display and Change ( F6 ). The Change Organization: 1050 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.

7. Go to Control tab and enter/check Trading partner (for example, 1010).


8. Navigate to the Company Code Data screen(s) by choosing Company Code.
9. Choose Company Codes. Customer (Fin.Accounting) Change: Company Code dialog box displays.
10. Choose Create.

Setting Up Sales from Distribution Center (3HS)


20 PUBLIC Master Data Setup
11. In Company Codes table, add new entry below:
• Company Code: Supplying company code, for example, 1710
• Customer: X
12. Select above new entry (line) and choose Adopt.
13. The following table lists the most common fields which need to be populated. You also need to consider local
(country-specific) adjustments.

Field Name Entry Value

Customer: Account Management tab

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


panies”)

Customer: Payment Transactions tab

Terms of Payment for example, 0001 (“Payable immediately w/o Deduction”)

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

3.2.2 Create/Extend Customer Sales Area Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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, 1050) in the
Business Partner field and choose Enter.
3. Choose Switch Between Display and Change ( F6 ). The Change Organization: 1050 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.

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 21
 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: Supplying sales organization, for example, 1710
• DistrChannel: for example, 50
• Division: for example, 00
11. 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.
13. Select the proper tab.

Field Name Entry Value

Orders tab

Customer Group 01

Currency for example, EUR

Cust. Pric. Procedure 01

Shipping tab

Delivery Priority 2

Shipping Conditions 01

Billing tab

Incoterms for example, EXW

Inco. Location 1 for example, Palo Alto

Terms of Payment for example, 0001 (“Payment immediately w/o Deduction”)

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

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

Partner Functions tab

Partner Role 1 Sold-to Partyfor example, own ID

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

Setting Up Sales from Distribution Center (3HS)


22 PUBLIC Master Data Setup
Field Name Entry Value

Partner Role 3 Payer, for example, 10401010

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

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

3.2.3 Create/Extend Supplier Company Code Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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, 1750) in the
Business Partner field and choose Enter.
3. Choose Switch Between Display and Change. The Change Organization: 1750 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.

7. Go to Control tab and enter/check Trading partner (for example, 1710).


8. Navigate to the Company Code Data screen by choosing Company Code.
9. Choose Company Codes. Supplier (Fin.Accounting), then Change:Company Code dialog box displays.
10. Choose Create.
11. In Company Codes table, add new entries below:
• Company Code: Selling company code, for example, 1010
• Vendor: X
12. Select above new entry (line) and choose Create.

Setting Up Sales from Distribution Center (3HS)


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

Field Name Entry Value

Vendor: Account Management tab

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


nies")

Vendor: Payment Transactions tab

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

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

3.2.4 Create/Extend Supplier Purchasing Organization Data

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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, 1750) in the Business Partner field and
choose Enter.
4. Choose Switch Between Display and Change ( F6 ). The Change Organization: 1750 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 the Vendor: General Data tab and enter/check the Plant (for example, 1710) field.
8. Navigate to the Purchasing Data screen by choosing Purchasing.

Setting Up Sales from Distribution Center (3HS)


24 PUBLIC Master Data Setup
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.
13. Select the proper tab.

Field Name Entry Value

Purchasing Data tab

Order Currency for example, EUR

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

Incoterms for example, EXW ("Ex Works")

Incoterms Location 1 Vendor

GR-Based Inv. Verification X

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

Partner Functions tab

Partner Role 1 Supplier for example, own ID

Partner Role 2 Invoicing Party for example, 17401710

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

3.3 Extend End Customer Master to the Delivering Company

In this section, you can extend end customer, for example, 10113006 to the delivering company 1710 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

10113006 (ID, Address, Bank data …)

Customer Company Code Data

1010 (Rec.Acc., Currency …)

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 25
Business Partner ID

Customer Sales Area Data

1710 / 50 / 10 (Sales tax …)

3.3.1 Create/Extend Customer Sales Area Data

Purpose

In this activity, you create the new sales area data segment, which is needed for the “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, 10113006) in the
Business Partner field and choose Enter.
3. Choose Switch between display and change (F6). Change Organization: 10113006screen 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, 50
• 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.

Setting Up Sales from Distribution Center (3HS)


26 PUBLIC Master Data Setup
13. Select the proper tab.

Field Name Entry Value

Orders tab

Customer 01
Group

Currency for example, EUR

Cust. Pric. 01
Procedure

Shipping tab

Delivery 2
Priority

Shipping 01
Conditions

Billing tab

Incoterms for example, EXW

Inco. for example, Palo Alto


Location 1

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


Payment

Account for example, 02 (“Foreign Revenues”)


Assignment
Group

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

Partner Functions tab

Partner Sold-to Party, for example, own ID


Role 1

Partner Bill -to Party, for example, own ID


Role 2

Partner Payer, for example, own ID


Role 3

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 27
Field Name Entry Value

Partner Ship-to Party, for example, own ID


Role 4

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

3.4 Enhance Material Master in Selling Company Code

Purpose

In the following sections, you’ll learn what to do to enhance the trading material R_3018 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_MD_SPCLST_ITEM_RFM (Master Data Specialist - Product
Data (Retail)) role to access the Display Article (MM43) App by opening the tile.
2. Choose Display Article (MM43) app.
3. Enter the following data and choose Continue:
• Material : for example, R_3018
• Distr. Center: for example, 1050
• Selected view: Logistics Distribution Center
4. Check whether the relevant data for the distribution center 1050 and the distribution center 1750 already
exists (choose button “Switch Validity Area” to change the distribution center)
5. If the article data for the Distribution Centers are missing, please start the listing process Assortments (3I5)
6. Check and, if necessary, maintain the following data the distribution center 1050 and 1750 with the Maintain
Article (MM42) app:

Field Name Entry Value

Organizational levels subarea

Plant for example, 1050

Stor. Loc. for example, 995A

Setting Up Sales from Distribution Center (3HS)


28 PUBLIC Master Data Setup
Field Name Entry Value

New Tax indicator 1

Storage Location 995A

Create Material screen displays.

7. Save the changes

3.5 Maintain Customer Discount Condition Record for


Ordering Company

Purpose

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

 Note

If the sales pricing for the material R_3018 and customer 1050 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: Menu Condition Create .
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, 50
• Customer: for example, 1050
• Amount: for example, 10.000-
• Unit: %
6. The Customer Discount condition record is saved.

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 29
3.6 Maintain Standard Purchase Info Record

Purpose

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

 Note

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

Procedure

1. Log on to the SAP Fiori launchpad using role SAP_BR_MD_SPCLST_ITEM_RFM with name Master Data
Specialist - Product Data (Retail).
2. Open Maintain article app.
3. Make the following entries:
• Article: R_3018
• Purchasing Org. : 1010
• Supplier: 1750
• Selected view: Purchasing
4. Choose Continue
5. Make the following entries:
• Order Unit: PC
• Pur. Group: 002
• Pl. Deliv. Time: 10
• Net. Price: <Maintain the right purchase price>
6. Incoterms: EXW
7. Inco. Loc. 1: VENDO
8. Choose button InfoRec
9. Choose Tab Purch. Org. Data 1
10. Make following entires:
• Tax Code: <Input tax code>, e.g. V1
• Tax Rate Valid From : Select value from F4 help
11. Save the data

Setting Up Sales from Distribution Center (3HS)


30 PUBLIC Master Data Setup
3.7 Maintain Export Tax Condition Record for Delivering
Company

Purpose

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

Procedure

1. Log on to the SAP Fiori launchpad 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.

Setting Up Sales from Distribution Center (3HS)


Master Data Setup PUBLIC 31
4 Configuration

4.1 Define Business Partner for Company Code

Purpose

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

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

All sales organizations within a company code must have the same business partner / customer assigned.

 Note

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

Prerequisite

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

Procedure

SAP Central Business Configuration:

In the Product-Specific Configuration phase, navigate to the Activities tab. Search for Configure Organizational
Entities and choose Open.

1. Log on to the project experience in SAP Central Business Configuration.


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 column, choose Sales Organizations line item.
4. 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.
5. Choose Edit on the Sales Organizations screen, enter your internal customer number, for example,
0017401710 in the Customer Number for Intercompany Billing field, choose Save.

Setting Up Sales from Distribution Center (3HS)


32 PUBLIC Configuration
6. Repeat the above steps to 0010401010 to Company Code 1010.

4.2 Assign Tax Code

Purpose

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

 Note

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

Prerequisite

The required tax codes have been activated in the system.

Procedure

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 Tax
Codes for the Transfer of Supplier Invoices.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Make the following entries and choose Save:

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

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

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

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

The tax code mapping is created.

Setting Up Sales from Distribution Center (3HS)


Configuration PUBLIC 33
4.3 Program Parameters for Supplier Invoice

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

4.3.1 Configure Program Parameters

Purpose

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

 Note

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

Procedure

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 Configure
Program Parameters.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Make the following entries and choose Save:

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

DEFAULT RE RE Unclarified Er­ “” “” “” “”


ror: Park In­
voice

6. Program Parameter Configuration is created.

Setting Up Sales from Distribution Center (3HS)


34 PUBLIC Configuration
 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.

4.3.2 Assign Program Parameters

Purpose

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

 Note

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

Procedure

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
Program Parameters.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Make the following entries and choose Save:
• Invoicing Party: “”
• Program Parameter Configuration ID: DEFAULT
6. Program Parameter Configuration is created.

Setting Up Sales from Distribution Center (3HS)


Configuration PUBLIC 35
4.4 Define Business Rules for Output Determination

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

1. Log on to the SAP Fiori launchpad using SAP_BR_ADMINISTRATOR role.


2. Access the Output Parameter Determination App by opening the tile.

Access via FIORI Launchpad

Business Role ID SAP_BR_ADMINISTRATOR

Business Role 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 no 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 a new row.
10. Make the following entries and choose Check & Activate.

Setting Up Sales from Distribution Center (3HS)


36 PUBLIC Configuration
Output Type Billing Type Channel Exclusive Indicator

First entry =BILLING_DOCUME =IV2 PRINT(Printout) X (true)


NT (Billing (Intercompany
Document) Invoice)

=BILLING_DOCUME =IV2S PRINT(Printout) X (true)


NT (Billing
Document)

Output channel IDOC for billing type IV2 is excluded.

4.5 Assign Transit Plant to Company Code

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

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

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

1. Raise an expert configuration request via WCR.


2. Please attach this excel where you have filled column “Company Code” and “Transit Plant” you need from the
list.
• Company Code: e.g. 1010
• Transit Plant: e.g. 1050

Setting Up Sales from Distribution Center (3HS)


Configuration PUBLIC 37
3. Send it to SAP.
4. The WCR ticket will get the status “Done” when the expert configuration is done in your configuration
environment.
5. Test the advanced intercompany sales process in your configuration system. Release BCP project to transport
the expert configuration to production system once the testing is confirmed.

4.6 Define Purchase Order Defaults for Sales Organization

Purpose

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

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

 Note

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

Prerequisite

The purchasing organization and purchasing group configuration is available.

Procedure

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 Purchase
Order Defaults in Advanced Intercompany Sales.
3. Choose the line item in the search result to see more details about this configuration activity.
4. 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.
5. Assign the correct POrg (Purchase Organization), PGr (Purchase Group) and OTyp (Order Type) to SOrg. (Sales
Organization). The Order Type should always be entered with NBAI. The following is a data example.

Setting Up Sales from Distribution Center (3HS)


38 PUBLIC Configuration
SOrg. POrg POrg OTyp

1010 1010 001 NBAI

Then choose Save.


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

4.7 Activate Advanced Intercompany Sales Process

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.

 Note

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

Prerequisite

All the above settings and configurations have been completed.

Procedure

All the above settings and configurations have been completed.

1. Raise a pre-approved incident using the component XX-S4C-SRV-CON.


2. Attach this excel with the following data:
• Activate Advanced Intercompany Sales Process for Sales Document Types and Item Categories:

Sales Order Type Item Category Enabled

OR TAN X

OR CBXN X

Setting Up Sales from Distribution Center (3HS)


Configuration PUBLIC 39
Sales Order Type Item Category Enabled

CBFD CBXN X

• Assign Transit Plant to Company Code:

Company Code Transit Plant

1010 1010

1710 1710

3. Send it to SAP.
4. SAP Cloud Opeartion will implement 5D2 How to Guide by considering the customer data above.
5. Test the advanced intercompany sales process in quality or test system. Release BCP project to transport the
expert configuration to production system once the testing is confirmed.

Setting Up Sales from Distribution Center (3HS)


40 PUBLIC Configuration
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.

Setting Up Sales from Distribution Center (3HS)


Important Disclaimers and Legal Information PUBLIC 41
www.sap.com/contactsap

© 2022 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

You might also like