on ‎2025 Dec 09 6:08 AM
Hello experts,
I need to activate Scheduling agreement LZM with subsequent delivery order TAM which will be referring to each other through Document flow to keep track of the cumulative quantity in SAP Public Cloud. I did not find any Scope item for those documents activation and it is quite essential for the sales processes in automotive. Could you please advise how to activate this functionality?
Request clarification before answering.
Dear @Toma44,
In Public Cloud you generally can’t activate the ECC automotive pair LZM (SA with delivery orders), TAM (delivery order) as a dedicated document-flow chain the way you know it from ECC. That LZM/TAM flow is a classic Scheduling Agreements with Delivery Orders concept from SAP Private /on-premise documentation, not a Public Cloud scope-item switch.
What you can do in Public Cloud and still keep cumulative quantities + traceability:
Option A: Scope item 3NR Sales Scheduling Agreements
This is the Public Cloud-supported way to run automotive-style SSA processes with cumulative quantities and follow-on logistics without a TAM layer. Sales Scheduling Agreements in Public Cloud explicitly support cumulative quantities
More details below:
How to activate:
Integration / EDI note (important for automotive):
Public Cloud typically expects delivery schedule integration via the provided services (not classic IDoc processing). The Delivery Schedule of Sales Scheduling Agreement interface exists for receiving/updating delivery schedules
More details below:
Cumulative quantity corrections:
If you ever need to realign cumulative figures, Public Cloud supports correcting cumulative delivered quantities via correction deliveries in the scheduling agreement context
More details below:
Resulting document flow:
Sales Scheduling Agreement ->Outbound Delivery->PGI->Billing
Your cumulative quantities are tracked on the scheduling agreement so you still get the control you need JUST without a TAM document in between
More details below:
Option B: Scope item 2EM Just-In-Time Supply to Customer
If your TAM usage is really about JIT execution, check whether your target process is actually 2EM Just-In-Time Supply to Customer which is explicitly positioned for JIT supply scenarios
More details below:
Summary:
Best Regards,
Dawid
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 39 | |
| 26 | |
| 21 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.