3705366 - Advanced Intercompany STO (5HP): New supplier overrides existing one for sales org invoicing after customer master update in SAP S/4HANA Cloud Public Edition

• In SAP S/4HANA Cloud Public Edition  (scope item 5HP), creating a new supplier linked to the existing intercompany customer for a delivering sales organization causes it to become the invoicing party for all intercompany flows from that sales organization including unrelated plant/destination combinations despite STO headers specifying the original plant supplier.
• The sales org 'Customer Interc. Bl.' allows only one entry, so updating the customer master Supplier field triggers universal override across destinations, Hence Invoices switch post-change.

SAP S/4HANA Cloud Public Edition

1. Maintain original supplier A (plant X) and new supplier B (plant Y), both linked to the same intercompany customer for sales org Z.

2. Update Supplier field in the intercompany customer (sales org Z view) to supplier B.

3. Create STO from sales org Z to destination using plant X (supplier A in header) → Intercompany supplier invoice posts to supplier B in receiving company code.​

4. Value Chain Monitoring shows supplier B as invoicing party despite STO header.

Intercompany supplier determination ignores STO header/plant vendor, reading exclusively from Supplier field in intercompany customer master for delivering sales org.​

• Single Supplier field per sales org/customer governs all destinations; plant suppliers handle shipping/logistics only.

• No central table replacement or precedence logic between supplier links—real-time read from active customer master field.

• Sales org single-entry limit prevents plant-specific invoicing without separate sales organizations.

1. Short-term
   1. Extend new supplier vendor to receiving company code with full financial data → Retry STOs in VCM app.​
   2. Verify: Manage Business Partner app → Customer → Sales Area Data → Supplier field value.
2. Long-term
   1. Option 1: Revert field - Customer master → Supplier = original. Restores original flows; test other destinations.​
   2. Option 2: Separate Sales Orgs - Create dedicated sales org per plant with independent customers/Suppliers. Enables plant-specific invoicing.​
   3. Option 3: Classic STO (1P9) - Switch from 5HP where plant vendor may prevail. Loses advanced automation.​

• KBA 3298560 - FAQ Advanced Intercompany Processes (IC-Stock Transfer) Procurement.
• ​KBA 3405510 - Error F5104 'Vendor is not defined in company code' raised when running intercompany allocation.

supplier invoice error, vendor not defined, company code 4400, advanced intercompany stock transfer, STO error, intercompany supplier determination, vendor master data, SAP S/4HANA Cloud Public Edition, 5HP scenario, customer-supplier mapping, intercompany invoice logic , KBA , MM-PUR-GF-STO-2CL , Stock Transfer (Public Cloud) , Problem