PUBLIC - Authorized for SAP Customers Advanced Intercompany Sales Restrictions SAP S/4HANA Cloud 2302 Document Version: 2.0 – 2023-02-14 Document History Version Date Change 1.1 2022-10-10 • Initial Version 1.2 2022-11-16 • • • • Information added on changing ship-to-party after delivery has been created Information added on deliveries with a delivered quantity of 0 Information added on the posting date used for the intercompany supplier invoices Information added on reason for rejection 62 1.3 2023-01-12 • More detailed Information added on the posting date used for the intercompany supplier invoices 2.0 2023-02-14 • • • • Version 2.0 is valid for SAP S/4HANA Cloud 2302 Restriction on ship-to-party in intercompany sales order has been deleted Restriction on fully delivered with a delivered quantity of zero has been deleted Information adjusted on tax date in the intercompany supplier invoice 2 TABLE OF CONTENTS GRAPHICAL OVERVIEW ................................................................................................................................ 4 FUNCTIONAL RESTRICTIONS ....................................................................................................................... 5 UNSUPPORTED FUNCTIONS AND SCENARIOS ........................................................................................... 7 GRAPHICAL OVERVIEW 4 FUNCTIONAL RESTRICTIONS • Standard sales order items can’t be deleted. o Solution 1: Use “Reason for Rejection”. o Solution 2: Change the delivering plant to an intracompany plant. Afterwards, deletion is possible. • Material number in standard sales order can’t be changed after purchase order has been created. • Change of the unit of measure in an outbound delivery is not allowed. o Change will lead to an error during creation of the intercompany supplier invoice. • Manually created intercompany supplier invoices are not visible in the Monitor Value Chains app. o You can prevent the manual creation of intercompany supplier invoices in your configuration environment. • Manually deleted intercompany supplier invoices are still visible in the Monitor Value Chains app. o You can prevent the manual deletion of intercompany supplier invoices in your configuration environment. • SAP Fiori app Manage Sales Orders doesn’t show the transit plant. • Conversion factors (including manually changed conversion factors) in standard sales order are not copied to the intercompany purchase order or the intercompany sales order. • Delivery-related pro forma invoices cannot be created in the delivering company. o Order-related pro forma invoices can be created in the delivering company. • The intercompany sales order is not visible in the document flow of the standard sales order, but can be displayed in the Monitor Value Chains app or in the Sales Order Fulfillment - Analyze and Resolve Issues app. • It’s not allowed to change the ship-to-party number or ship-to-party address in the standard sales order after the outbound delivery has been created. o Wrong ship-to-party information can be copied to the intercompany customer invoice. o Instead of changing the ship-to-party information, you should create a new sales order item with the new ship-to-party information. • If the goods issue from stock in transit in the selling company has not been posted yet, batch split items in the customer invoice won’t determine costs in pricing (for example, condition type PCIP / Internal price). • If line-by-line tax calculation is active for the intercompany customer invoice, the system derives the tax data from the intercompany customer invoice to post the intercompany supplier invoice. o If time-dependent tax is active for the selling company code and the respective tax country, and if the intercompany customer invoice has different service-rendered dates on item level, these dates are used as tax calculation dates during the posting of the intercompany supplier invoice. o If currency conversion for country/region is available and line-by-line tax calculation as well as time-dependent tax calculation are both active for the company code of the supplier invoice at the same time, the creation of the intercompany supplier invoice is not supported for intercompany customer invoices with different service-rendered dates on item level. o To solve the issue of not having a unique date of services rendered on item level, you can create separate intercompany customer invoices instead of collective intercompany customer invoices as follows: In the Create Billing Documents app, you must activate the billing setting “Create separate billing document for each item of billing due list”. o By implementing Business Add-In (BAdI) SD_BIL_DATA_TRANSFER, you can ensure that only intercompany customer invoices with a unique date of services rendered on item level are created. For more information, see SAP Knowledge Base Article 2800221. 5 • The billing date of the intercompany customer invoice is used as the posting date of the intercompany supplier invoice. o The intercompany supplier invoice can’t be created if the posting period of the selling company is closed for the billing date. To continue, you have the following options: ▪ Option 1: Cancel the intercompany customer invoice and recreate it with a billing date where the posting periods are open in the delivering company and the selling company. ▪ Option 2: To set a different posting date of the intercompany supplier invoice, use the BAdI MMIV_IC_MAPPING. ▪ Option 3: To post the IC supplier Invoice, open the posting period in the selling company. o Remarks: ▪ We plan to implement an enhanced logic where the current date is used as posting date in case the posting period of the billing date of the intercompany invoice is closed. ▪ Intercompany supplier invoice creation is only possible after goods receipt in the transit plant has been posted. ▪ You can prevent this issue by creating the intercompany customer invoice after goods receipt in the transit plant has been posted. • Profit center substitution is not enabled in the standard sales order or intercompany sales order. • Delivery items having zero quantity are relevant for intercompany customer invoices. o For delivery items having zero quantity an intercompany invoice will be created. o Intercompany customer invoice items having zero quantity are not transferred into the intercompany supplier invoice. o In the Monitor Value Chains app, the process step “Intercompany Supplier Invoice” won’t always get the document processing stage “Completed”. • In some scenarios of Advanced ICo Sales the system uses the reason for rejection “62” in the sales order in the delivering company. The usage of reason for rejection “62” is fixed in the source code and can’t be configured. o It’s necessary that the reason for rejection 62 is defined. 6 UNSUPPORTED FUNCTIONS AND SCENARIOS • • • • • • • • • • • • • • Subitems in a standard sales order (SO2): o Sales bill of material (BOM) o Advanced ATP o Free goods Order-related customer invoicing Free of charge items without customer invoice relevance Solution orders Scheduling agreements Non-stock materials Non-valuated materials Service materials Returnable packaging Integration with WBS (work breakdown structure) elements Make-to-order o With variant configuration o Sell from stock with “make-to-order production” Deliveries and delivery items without sales order reference Intercompany customer invoice corrections Third-party direct shipment / drop shipment 7 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. 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. See www.sap.com/trademark for additional trademark information and notices.
