Advanced Intercompany Stock Transfer: Setting Up (5HP)
Advanced Intercompany Stock Transfer: Setting Up (5HP)
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 Organizational Setup - General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Organizational Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Assign Picking Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1 Define Business Partner for Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2 Define Shipping Data for Plants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.3 SOAP Settings for Supplier Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Assign tax code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configure Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Assign Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.4 Define Business Rules for Output Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
The purpose of this documents 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 Stock Transfer scenarios enable 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 this SAP Best Practices scope item:
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 set up as assumed in this scenario:
● International: DE company (for example company code 1010) sells goods to customer, and the goods are
delivered from a plant, which belongs to US company (for example company code 1710).
For creating internal business partner to represent company code and plant, only the grouping with external
number range can be used. The purpose 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.
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 (5HP_US and 5HP_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)
Define Plant / Assign Plant to Company 1010 / 1010 to 1010 1710 / 1710 to 1710
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 message via the component
SV-CLD-FRM-APP.
Purpose
The purpose of this activity is to assign picking location to shipping point / plant.
Note
Ideally, this chapter is extended via flex-org tool or SSCUI in preparation phase. In case extension failed, you
can set up necessary relationship as below.
The Shipping Points and Storage Locations have already been created for the plants via flex-org tool.
Procedure
1. Log on to the SAP Fiori launch pad using SAP_BR_BPC_EXPERT business role to access the Manage Your
Solution 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 Picking in the searching input box and choose Enter, the list of Configuration Items displays.
4. Click the Supply Chain in Configuration Item subarea, the Configuration Your Solution – Picking screen displays.
5. Choose the Configure of the Assign Picking Location column, the Change View Picking Location Determination:
Overview screen displays.
6. Click the New Entries function to enter the following data, choose Save:
Table 1: Picking Location Determination
7. Result: The Picking Location Determination data is saved for the new plant, new shipping points and storage
location.
Purpose
In this section, you need to create/extend business partners representing delivering and receiving companies.
Business partners with same ID as on Q-quality, should be created in P-production system before Q2P transport of
Intercompany related configuration.
Business partner data for company codes 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 the activation of the 5HP_DE and 5HP_US country / region solution, the business partner data representing
each company code are like below, business partners 10401010 representing company codes 1010 and 17401710
representing company codes 1710.
10401010 (ID, Address, Bank data …) 17401710 (ID, Address, Bank data …)
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 "sister" company
that wants to use the business partner in "Customer-related" FI postings.
Procedure
1. Log on to the SAP Fiori launchpad using the role SAP_BR_BUPA_MASTER_SPECIALIST with name Master
Data Specialist - Business Partner Data.
2. Open Maintain Business Partner.
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 "sister" company that
wants to use the business partner in intercompany invoice 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.
Note
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.
Orders tab
Customer Group 01
Shipping tab
Delivery Priority 2
Shipping Conditions 01
Billing tab
10. 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 "sister" 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_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 company code data. Check if BP role FLVN00 Vendor (Fin.Accounting) exists. If not, extend BP role
FLVN00 to receiving company, (for example, 1010). Choose FLVN00 Supplier (Fin.Accounting) (defined) in the
Change in BP role field.
Note
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.
6. Go to Control tab and enter / check Trading partner field (for example, 1710).
7. Navigate to the company code section by choosing Company Code.
8. Choose Company Codes. The Supplier (Fin.Accounting) Change: Company Codes dialog box displays.
9. Choose Create. In the Company Codes table, add new entries as below:
○ Company Code: <ordering company code>, for example, 1010
○ Vendor: <select>
Select above new entries (line) and choose Adopt.
10. The following table lists the most common fields which need to be populated. Make sure that you consider
local (country-specific) adjustments as well.
11. 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 "sister"
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
receiving company, (for example, 1010). Choose FLVN01 Supplier (defined) in the Change in BP role field.
Note
Note that you can only navigate to the Purchasing Data screen when you select this BP role as only in this
case Purchasing displays.
10. Save your entries. Supplier purchasing data for purchasing organization 1010 of business partner 17401710 is
created.
Purpose
In this section, business partners 10411010 and 17411710 representing plants 1010 and 1710 are respectively
created/extended in the following organizations:
After performing activities in this chapter, the business partner data representing each company code will look 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
“sister” 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). The Change Organization: 10411010 screen displays.
4. Create company code Data.
5. Check if FLCU00 Customer (Fin.Accounting) BP role exists. If not, extend FLCU00 to delivering
company, (for example, 1710).
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.
13. Save your entries. Customer code data for company code 1710 of business partner 10411710 is created.
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.
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, 10
○ Division: for example, 00
Select above new entries (line) and choose Create.
11. The following table lists the most common fields which need to be populated. Make sure you consider local
(country-specific) adjustments as well.
Select the proper tab.
Orders tab
Orders 01
Shipping tab
Delivery Priority 2
Shipping Conditions 01
Billing tab
Output Tax for example, 1 (“Liable for Taxes”) for country DE-Germany
and tax category TTX1
12. 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 “sister”
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.
13. Save your entries. Customer code data for company code 1010 of business partner 17411710 is created.
14. Repeat above steps to create/extend company code data for further business partners for example, creating/
extending company code data in company code 1710 for business partner 10401010.
Purpose
In this activity, you create the new purchasing organization data segment needed for the “sister” company that
wants to use the business partner in sales transaction.
Procedure
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.
Note
You can only navigate to the Purchasing Data screen when you select this BP role as only in this case,
Purchasing is displayed.
8. Go to Vendor: General Data tab and enter/check Plant (for example, 1710) field.
9. Navigate to the Purchasing Data screen by choosing Purchasing.
10. Choose Purchasing Organizations. Supplier Create: Purchasing Organizations dialog box displays.
11. Choose Create.
12. In Purchasing Organizations table, add new entry below:
○ Purchasing Organization : <Purchasing Organization in ordering company>, for example, 1010
Select above new entry (line) and choose Create.
13. The following table lists the most common fields which need to be populated. Make sure you consider local
(country-specific) adjustments as well.
Select the proper tab.
14. Save your entries. Customer code data for purchasing organization 1010 of business partner 17411710 is
created.
Purpose
The following sections describe how to enhance the trading materials TG11 for them to be used in intercompany
stock transfer processing. If you want to use other materials in intercompany stock transfer processing, you will
need to perform 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, TG11
Select View(s) dialog box displays.
4. Select Purchasing , and MRP2, then choose Continue.
5. The Select view(s): Organizational levels dialog box displays.
Maintain the following data and choose Continue:
Purchasing tab
MRP2 Tab
7. 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 the intercompany condition record.
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 TG0011 and suppliers (13300001, 13300002 and 13300003) already exists in
the system, you can skip these steps.
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 the H eader tab:
○ Purchasing Info Record Category: Standard
○ Purchasing Organization: 1010
○ Supplier: 17411710
○ Material: TG11
○ Purchasing Group: 002
5. Make the following entries in the General Information tab:
○ Available From: Today
○ Available To: 31.12.9999
6. Make the following entries in the Purchasing Data tab:
○ Incoterm : EXW
○ Incoterm Location 1 : VENDO
7. Make the following entries in the 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>
○ 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 xountry of company code and tax code is given, the Tax Rate Valid From field is
mandatory. You can enter current date, which will be adjusted to validity start date of tax code
according to the settings in SSCUI.
Purpose
In this activity, you maintain the export tax condition records for country solution 5HP_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 TypeUTXJ, choose menu path: More > Condition> Create and choose
Enter. The Key Combination screen displays.
4. Choose the option Departure Country / Destination Country, select Choose. The Create Tax Jurisdict. Code
Condition (UTXJ): Fast Entry screen displays.
5. Please contact your Tax Experts of the countries to maintain the required export tax condition records from DE
to US with the detailed information.
Purpose
This process step shows you how to assign an internal customer number for intercompany billing to your sales
organization.
All the sales organizations within a company code must have the same business partner / customer assigned.
Prerequisites
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 [page 10] chapters).
Procedure
Purpose
The purpose of this activity is to define shipping data for plant (to allocate sales organization, distribution channel,
division and customer No.to the plant for which intercompany stock transfer processing is possible).
Note
Prerequisites
Business Partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (Please refer to Master Data Setup [page 10] chapters).
Procedure
3. Select Configure Your Solution on 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.
4. Enter Define Shipping Data for Plants in the searching input box and choose E nter, 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, 1030). 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
Detailed information
SlsOrg.Int.B. 1710
DisChannelIB 10
Div.Int.Billing 00
Language Key EN
Purpose
The purpose of this activity is to assign tax codes to transfer supplier invoice data with a SOAP service. In this
activity, you assign tax rates and tax types as sent by your invoicing party to tax codes defined in the system.
Prerequisites
Business Partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (Please refer to Master Data Setup [page 10] chapters).
Procedure
3. Select Configure Your Solution on 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.
4. Enter Assign Tax Codes in the searching input box and choose enter, the list of Configuration Items is
displayed.
5. Choose the Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configuration 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. Choose New Entries on the Change View " Assign Tax Codes for the Transfer of Supplier Invoices ": Overview
8. Make the following entries and choose Save:
Invoice Party Tax Type Tax Rate Country/region Key Tax Code
Invoicing Party Tax Type Tax Rate Country / Region Key Tax Code
Purpose
The purpose of this activity is to configure the program parameters to transfer supplier invoice data with a SOAP
service.
Prerequisites
Business Partners with all needed data parts for BP customer and BP supplier have been created for both company
codes (Please refer to Master Data Setup [page 10] chapters).
Procedure
3. Select Configure Your Solution on 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.
4. Enter Configure Program Parameters in the searching input box and choose E nter, the list of Configuration
Items is displayed.
5. Choose the Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configuration Your
Solution – Ariba Network Integration for Buyers (SOAP) screen displays.
DEFAULT RE RE Unclarifie “” “” “” “”
d Error:
Park
Invoice
Note
The option “Enable Attachment Transfer” is not relevant for Intercompany processes and you can ignore it.
You can leave this data “Checked” for example in case B2B SOAP Service is in use and requires an
attachment.
DEFAULT RE RE Unclarifie “” “” “” “”
d Error:
Park
Invoice
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
The purpose of this activity is to assign the configuration ID to the corresponding invoicing party to transfer
supplier invoice data with a SOAP service.
Note
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
3. Select Configure Your Solution on 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.
4. Enter Assign Program Parameters in the searching input box and choose E nter, the list of Configuration Items is
displayed.
5. Choose the Ariba Network Integration for Buyers (SOAP) in Configuration Item area, the Configuration Your
Solution – Ariba Network Integration for Buyers (SOAP) screen displays.
6. Choose Configure of the Assign Program Parameters, the Change View "SOAP: Program Parameter Mapping":
Overview screen displays.
7. Choose New Entries on the Change View "SOAP: Program Parameter Mapping": Overview screen.
8. Make the following entries and choose Save:
○ Invoicing Party: e.g. “”
○ Program Parameter Configuration ID: IC_DEFAULT
9. The data of program Parameter Mapping 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
Advanced intercompany stock transfer is disabled for the purchase document type NBIC by pre-delivered
configurations. The pre-delivered configurations must be enabled through an expert configuration request. Only
with this configuration enabled, the advanced intercompany stock transfer process is activated.
Note
Prerequisites
Purchase Order Type Adv. Intercompany Stock Transfer Value Chain Type
NBIC ICO_STOCKTRANSFER
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 stock transfer 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.