S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10.pdf¶
来源: S4HANA ACM 蓝图 | 页数: 167 | 提取日期: 2026-06-25
--- 第1页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 1 of 167 `
Global Blueprint
Agricultural Contract Management Delivery Planning & Execution
--- 第2页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 2 of 167
Document Information
Project Name S/4HANA Transformation Project Document Name S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution Version 1.10
Revision History
Version Effective Date Author Description/Reason for Change V0.01 26 November 2025 Anshuman Awasthi Post Delivery Planning & Execution Pre-DCW V0.02 28 November 2025 Anshuman Awasthi Post DCW Revision: Output Forms and Release Credit Blocked Nomination option. V0.03 03 December 2025 Anshuman Awasthi Ship-to-Ship Scenario for Indonesia Weighbridge Integration at Nominations V0.04 08 December 2025 Anshuman Awasthi Additional Process Visualization on Indonesia Goods Movement, Hygiene, and Updates for SG/DO V0.05 12 February 2026 Anshuman Awasthi LDC Journal Postings for SG Moved here LC Export Solution Flexibility V1.00 13 February 2026 Nyoman Arya Wardana Final Version for Signoff
V1.10 02 June 2026 Anshuman Awasthi Lakshya Kalita Shankar Kulkarni Nabil Zaky Addendum based on SG and ID-Key Account, ID-Commercial Control, ID-Logistic HO Team.
Document Objective
•
Provides an overview of the process area covered in this document and describes the Business Process
Hierarchy (BPH) up to Level 4 (Activity).
•
Describes key business requirements gathered during workshops with GAR Business Process Leads
and key business users.
•
Outline the solution and system design in SAP S/4HANA to address the business requirements in
respective process areas.
•
This document serves as the global blueprint template to be used as the basis for S/4HANA
implementation project
--- 第3页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 3 of 167
TABLE OF CONTENTS 1 BUSINESS PROCESS OVERVIEW .......................................................................................... 4 1.1 High-Level Process Overview .............................................................................................................. 4 1.2 Business Process Hierarchy (BPH) and Its Applicable BU .................................................................. 8 2 KEY DESIGN DECISIONS ........................................................................................................ 9 2.1 ACM Product Scope for Upstream Indonesia ....................................................................................... 9 2.2 ACM Product Scope for Downstream Indonesia ................................................................................10 2.3 ACM Product Scope for Palm Kernel Shell (Cangkang) ....................................................................11 3 SAP SOLUTION BLUEPRINT ................................................................................................. 12 3.1 Delivery Planning ................................................................................................................................12 3.1.1 Highlighted Key Business Requirements .......................................................................................12 3.1.2 Business Process Flow ...................................................................................................................20 3.1.3 Solutioning ......................................................................................................................................23 3.2 Goods Movement & Quality Capture ..................................................................................................29 3.2.1 Highlighted Key Business Requirements .......................................................................................29 3.2.2 Business Process Flow ...................................................................................................................41 3.2.3 Solutioning ......................................................................................................................................50 4 COUNTRY SPECIFIC SCENARIO .......................................................................................... 77 4.1 Process Design Variants - With TMS and Without TMS ....................................................................77 4.2 Singapore, Malaysia, & China Deliveries from Futures ......................................................................77 4.3 Indonesia Goods Movement Scenarios ..............................................................................................82 4.3.1 Plant-to-plant / Sloc-to-Sloc Transfers (within the same company code).......................................83 4.3.2 Intercompany (different company code) .........................................................................................85 4.3.3 .3rd Party Purchase .........................................................................................................................97 4.3.4 3rd Party Sales ..............................................................................................................................101 4.3.5 LDC Variations for Backstop Scenarios .......................................................................................106 4.3.6 Intercompany Multi-Modal Destination Scenario ..........................................................................106 4.3.7 Intercompany Multi-Modal Origin Scenario ..................................................................................107 5 APPENDIX............................................................................................................................. 108 5.1 ID Goods Movement Variations ........................................................................................................108 5.2 Requirement List ...............................................................................................................................129
--- 第4页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 4 of 167 1 Business Process Overview 1.1 High-Level Process Overview The diagram below illustrates the end-to-end processes within the Commodity Trading & Risk Management domain. This document specifically focuses on the Delivery Planning & Execution group, outlining the key activities involved in the seamless execution of Commodity Trading & Risk Management.
Figure 1.1 Business Process Hierarchy for CTRM
--- 第5页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 5 of 167 Below diagram shows high level processes which are covered from Pre-Trade to Settlement.
Figure 1.2 – Business Process Flow from Pre-Trade to Settlement
--- 第6页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 6 of 167 This document is created at level L2, which is Delivery Planning & Execution. Below diagram shows high level processes which are covered within Delivery Planning & Execution.
Figure 1.3 - Business Process for Delivery Planning & Execution
--- 第7页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 7 of 167 Table 1.1 Delivery Planning & Execution Process Overview Process Description Delivery Planning & Execution covers part of commodity contract lifecycle during: • Delivery Planning • Goods Movement & Quality Capture The main objective of Delivery Planning & Execution process is to be able to capture schedule goods delivery and capture actual goods details.
Delivery Planning Delivery Planning in Agricultural Contract Management (ACM) starts from Nomination where the scheduling of the goods has been done.
A nomination is a scheduling and communication document that serves as a critical planning tool for bulk shipments of agricultural commodity products. The nomination provides detailed shipment information and acts as a communication link between carriers, customers, and all other parties connected in transport.
Goods Movement & Quality Capture Post Nomination, we have Load Data Capture where the actual goods movement happens.
Load Data Capture is a crucial component that captures the details of loads and unloads, including quality analysis information, typically obtained through weighbridge systems. Key Changes Delivery Planning Key Changes in Delivery Planning which revolves around nominations are: • Integration between ACM-FSCM • Validations for LC • Custom Fields and Validations, for example Certificate Details. • Custom Forms Goods Movement & Quality Capture Key Changes in Goods Movement & Quality Capture which revolves around Load Data Capture are: • Synchronize Goods Movement as per business requirements • Adjustment of Postings at Goods Movement • Custom Fields and Validations • LDC Integration for example WB and Quality Systems • Mass Upload for LDC
--- 第8页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 8 of 167 1.2 Business Process Hierarchy (BPH) and Its Applicable BU This document provides the solution for Delivery Planning & Execution process group with all its detailed processes and activity described in this section.
BPH L1 (Process Category) Commodity Trading & Risk Management BPH L2 (Process Group) Delivery Planning & Execution Table 1.2 - Applicable BU for Delivery Planning & Execution 3.2 Delivery Planning & Execution ID SG CN IND PK EU LATAM US Oleo Sugar 3.2.1 Delivery Planning
3.2.1.1 Create Nomination Y Y Y Y Y Y Y Y Y Y
3.2.1.2 Release Credit Blocked Nomination Y Y Y Y Y Y Y Y Y Y 3.2.2 Goods Movement & Quality Capture
3.2.2.1 Maintain Load Data Capture Y Y Y Y Y Y Y Y Y Y
3.2.2.2 Review Application Document Y Y Y Y Y Y Y Y Y Y
3.2.2.3 Assign Load to Storage Agreement TBC N TBC TBC TBC TBC TBC TBC TBC TBC
3.2.2.4 Reverse Load Data Capture Y Y Y Y Y Y Y Y Y Y
TBC: subject to confirmation on whether respective applicable BU intends to adopt this
--- 第9页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 9 of 167 2 Key Design Decisions 2.1 ACM Product Scope for Upstream Indonesia Decision Point Determine the solution on upstream business unit commercial transaction, especially on the commodity trading related product Impacted L3 ALL L3 (E2E) Background Non-standard solution across business units, e.g. • Buyer (Downstream) utilizes trading platform (CXC, to be replaced with ACM) • Seller (Upstream) do not utilize trading platform (standard SD solution) Leading Practice All GAR companies engaged in Commodity Trading should adopt a standardized solution for Trade Capture to Settlement
Proposed Solution As-Is Solution Solution Description • Utilize ACM for upstream commodity commercial transaction: CPO, PK, PKO, PKE, PKS (cangkang), High FFA CPO. • FFB, Seeds & Services (Toll In/ Toll Out) will remain in SD/MM. • Remain in SD/MM for all products. Pros (Design rationale, benefit) • Transparency through End- to-end streamline solution for affiliated transaction (US – DSI) • Process efficiency through mirroring contract creation triggered by the leading contract. • Standard ACM solution for gain/loss (variance) – not via custom program • Reconciled financial settlement, minimize errors & ensure consistency across entities • Potential to eliminate surrounding system (i.e KUBE) for affiliated transaction – to be review in a separate KDD discussion • Lower change management impact. • Same process flows for all products. Cons (Drawbacks) • Change management on new ACM solution, potential organization restructuring / role re-alignment may be required. • Different process flow between commodity and non- commodity products. • Not aligned with SAP best practices, require heavily customized solution to support the E2E Trade Flow Decision: This option is selected
--- 第10页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 10 of 167 2.2 ACM Product Scope for Downstream Indonesia Decision Point Determine the solution on Downstream Indonesia business unit commercial transaction Impacted L3 ALL L3 (E2E) Background Blurry lines between Trading & Non-Trading Transaction Leading Practice Clear distinction & solution for Trading Transaction (ACM) vs Non-Trading Transaction (SD/MM)
Proposed Solution As-Is Solution Solution Description • Utilize ACM for DSI Commodity Trading commercial transaction : All Bulk & Semi Bulk Products • Minyak Goreng Curah for Maklon Distribusi will utilize ACM • Minyak Goreng Curah for Maklon Murni will remain in SD • Marsho, Branded Products (Industrial, Cooking Oil, include Minyakita), Services (Toll In/ Titip Olah CPO, Toll Out) will remain in SD/MM. Remain in SD/MM for all products. Pros (Design rationale, benefit) • End-to-end streamline solution for Commodity Trading Commercial transaction • Process efficiency through mirroring contract creation triggered by the leading contract. • Standard ACM solution for gain/loss (variance) – not via custom program • Reconciled financial settlement, minimize errors & ensure consistency across entities • Lower change management impact. • Same process flows for all products.
Cons (Drawbacks) • Change management on new ACM solution, potential organization restructuring / role re-alignment may be required. • Different process flow between commodity and non-commodity products. Require custom report to address EoD reporting requirement for Marsho & DMO products. Not aligned with SAP best practices, require heavily customized solution to support the E2E Trade Flow
Decision: This option is selected
--- 第11页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 11 of 167 2.3 ACM Product Scope for Palm Kernel Shell (Cangkang) Decision Point Determine the solution for Palm Kernel Shell (Cangkang), for both Trading & non-Trading transactions (as fuel) Impacted L3 ALL L3 (E2E) Background Palm Kernel Shell (cangkang) is part of GAR commodity trading product, which is part of ACM Product Scope. DSI purchase cangkang as fuel from Upstream & 3rd party, using Coupa (standard PR/PO process). Leading Practice Standardized solution for commodity trading product.
Option 1 Option 2 Solution Description • Utilize ACM for all Cangkang transactions across all BU. • Central Procurement Team need to use ACM to purchase Cangkang from Intercompany (US Mill) & 3rd party. • Cangkang Trading by Commercial CBB team will utilize ACM solution. • DSI Cangkang Purchase from 3rd party as fuel is non-trading transaction & will remain in Coupa/ MM. • Purchase from Intercompany as fuel will follow As-Is for now, where Commercial CBB on Seller side will use ACM 3rd party sales, but Procurement from buyer side will remain in Coupa/ MM. This will be finalized closer to implementation. Pros (Design rationale, benefit) • Standardized process for all PKS/ Cangkang transaction • Auto gain/loss posting to inventory and utilize DPQS parameter for quality settlement, for all transaction • Standard E2E flows in Coupa/MM for Central Procurement Team/ Buyer side. • Standard E2E flows in ACM for Commercial CBB/ Seller side for all transaction. Cons (Drawbacks) • No live auction & sourcing functionality in ACM • Central Procurement Team need to use 2 platforms (Coupa & ACM). ACM will be used only when Procurement needs to purchase commodity trading products. • Manual quantity Gain/Loss posting and quality tracking for purchase as fuel (same with As-Is condition). Decision:
This option is selected
--- 第12页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 12 of 167
3
SAP Solution Blueprint
This section describes SAP solutions to address key business requirements in the Commodity Trading & Risk
Management process area.
3.1
Delivery Planning
3.1.1
Highlighted Key Business Requirements
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
ACM-
019
GAR will do pre-planning on barges outside the
system. Need the ability to enter into the system
once users know which barge belongs with which
contract. There could be multiple contracts loaded
onto the same barge
Fit
Once barge planning is
done outside the
system, multiple LDCs
each corresponding to
contract can have the
same barge ID can be
clubbed and delivered
together
ACM-
092
Ability to manage vessel and shipment data:
- Capture vessel information
- Link vessels to specific sales contracts
- Update planned vessel matches when needed
- Use strategy field to segregate volume by vessel
origin
- Capture shipment-related events and dates
- Track vessel nomination, BL, load, and
discharge dates
- Define document workflow status (reviewed,
approved, ready)
Gap
Additional custom field
at LDC& contract
ACM-
096
Ability to set up and configure parcel fields:
- Copy down fields from contract level to parcel
level
- Include load port, destination port, and other pre-
defined fields
- Support contract-specific terms like PORAM /
FOSFA for scheduling and nomination
Fit
Basic Configuration
ACM-
098
Ability to handle nominations:
- Ability to nominate schedule for FOB and other
incoterms
- Ability to set contract-specific terms like PORAM
/ FOSFA for scheduling and nomination
- Create nominations from various contract types
- Move parcels from planned to nominated status
- Capture best known date and quantity from
operators
- Enable multiple sort levels for open/closed
contracts
- Allocate purchase contracts/inventory to
(execution orders - S4 Team)
- Allocate multiple purchase/sales contracts
against one voyage
- Plan inventory and reserve shipments
Gap
Custom Fields at
Nomination as per the
Requirement
ACM-
102
Ability to establish framework for controlling
execution processes:
- Implement control points on sales order
nominations
- Prevent scheduling without contracts or with
zero-price contracts (validation group at
Fit
Optionality
--- 第13页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 13 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
nomination)
- Ability to proceed with nomination, BL even
without fully priced contracts (SG)
- Edit purchase orders with alternative ship-to
locations (at nomination and auto-populated at
order level provided that it is defined at the
contract optionality)
- Navigate between tickets, counterparty details,
and contracts (default)
- Receive planned deliveries (default)
- Track loads booked, hauled, and remaining (part
of TM scope)
ACM-
217
Ability to manage invoice approvals:
- Bypass contract approval process for proforma
invoice creation for export purpose
Gap
Automation of
settlement release and
approval based on
business specific
conditions can be
leveraged for the
solution
ACM-
220
Ability to manage import documentation:
- Manage arrival documentation (bank documents,
OBL)
- Create PE (Export Permit) in government system
This is related to ACM-946 Fit Forms Enhancement ACM- 221 Ability to track documentation: - Track open customs clearance documents, delivered volumes - Monitor receipt of customer documentation (gap might need to formulate a form/report level) - Track pending justifications and open items (gap might need to formulate a form/report level) - Manage comprehensive documentation parameters (gap might need to formulate a form/report level) This is Agiblock-EU Requirements. Gap Forms / Reports Enhancement ACM- 253 Ability to manage ports: - Define both Load and Destination ports on physical trades - Support port definition regardless of title transfer location Fit TSW Location will carry information about ports ACM- 254 Ability to model transportation movements: - Capture and model physical transportation (Vessel, Barge, Rail, Truck) - Plan physical and material movements within system - Support single vessel/truck transportation - Handle combination vessel and truck transportation (Gap - Multi Modal) - Manage HUB Tank/Titip Timbun combinations (Gap - Multi Modal) - Document customer-arranged trucking and transportation - Support operations across multiple terminals (5- 6) - Manage different locations across the USA Gap Part of ACM-TM Integration
--- 第14页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 14 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
ACM-
255
Ability to process vessel nominations:
- Manage vessel nomination process
- Receive vessel nominations from buyers
- Forward nominations to shippers
- Track and maintain nomination status throughout
process
- Handle complete vessel nomination workflow in
third-party transactions (out of acope ACM)
- Create and manage all possible movements
(Sell, Storage, transport modes)
- Match Back to Back to back transactions
- Model transhipment
- Handle multiple tickets (trucks/railcars) as part of
the same tender
- Model vessel and inventory gains/losses
- Coordinate arrival of stock via vessels shared
with CNF customers
Fit
Standard Solution
Behavior
ACM-
257
Ability to manage surveyors:
- Appoint load port surveyors
- Maintain database of approved surveyors
- Store and manage surveyor reports and
certificates
Gap
Part of ACM-TM
Integration
ACM-
260
Ability to generate shipping documents:
- Generate shipping instructions, packing lists,
appointment letters
- Print shipping documentation
- Create documentation for 3rd party shipments
- Create Memo/Shipping Instruction for QM
- Create tender (shipment advice)
- Create documentation for cross-border
shipments
- Support dedicated freight and documentation
teams
Gap
Custom fields can be
added at contract /
LDC level. ACM-TM
Integration
ACM-
261
Ability to capture transport information:
- Capture GAR-specific information at tender and
ticket level
- Review existing plans and capture actual
shipping information
- Record event dates, quantities, quality, and costs
Gap
Custom fields can be
added at contract /
LDC level. Open KDD
on ACM-TM Integration
ACM-
272
Ability to manage multiple transport modes:
- Support rail cars (DAP and ex-tank)
- Manage trucks (ex-tank for Palm, DDP for Oleo)
- Coordinate barges (ex-tank)
- Handle pipeline transfers (ex-tank)
Fit
Baseline Configuration
ACM-
290
Ability to enable coordinating transportation:
- Book transportation with contracted vendors
- Support DDP/DAP shipment requirements
This relates to ACM-949 Fit Standard Product Behavior ACM- 291 Ability to enable pre-shipment planning: - Manage logistics planning prior to execution - Eliminate reliance on spreadsheets - Provide integrated planning tools Fit Standard Product Behavior ACM- 293 Ability to enter and utilize load port and discharge port information during the nomination process Fit Standard Solution Behavior
--- 第15页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 15 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
rather than solely pulling this data from the
contract level
ACM-
333
Ability to manage inventory sources:
- Differentiate inventory sources (Downstream,
Upstream, 3rd Party)
- Differentiate stock sources (Downstream,
Upstream, 3rd Party)
- Use different accounts based on party type
(downstream/upstream)
Gap
SS: Might need a
separate report
ACM-
397
Ability to configure number range settings for each
printout with different prefixes while maintaining
sequential numbering across various document
types during the nomination process
Gap
Form Requirment
ACM-
400
Ability to generate proforma invoices during the
nomination phase by accessing the output file
functionality
Fit
Form Requirment
ACM-
401
Ability to configure additional required fields such
as Surveyor Name, Consignee, and Notify Party
for generating pre-load documents after
nomination completion
Gap
Enhancement to be
done based on req
ACM-
521
Ability for scheduler or Trade Operations to
perform nomination functions
Fit
Security Roles and
Authorization
ACM-
620
Ability to view quantity status for each contract
showing vessel stages
Gap
Part of Virtual Crush
KDD Solution
ACM-
658
Ability to allow flexible partial deliveries based on
available credit limit (e.g., ship 100MT if credit only
covers partial 500MT order)
Fit
It is a fit. This check
happens at nomination,
where the scheduled
quantity is validated
against contract
quantity to assess the
business model.
ACM-
689
Ability to nominate different destination ports (with
separate contracts for different pricing)
Fit
Nomination can be
created for several
contracts together.
ACM-
713
Ability to limit pegging based on specific criteria
with built-in and extendable validation logic
Gap
Nomination pegging
already has some built
in checks. Further
requirmeents needs to
be discussed in detail
ACM-
714
Ability to reject and re-peg contracts at nomination
level (match and unmatch)
Fit
Can be changed
aslong as there is no
execution
ACM-
747
Ability to trace EUDR compliance and segregate
compliant vs non-compliant inventory
Gap
Interface between SAP
and E-Waybill
ACM-
758
Ability to block nominations based on prepayment
agreement status
Gap
Custom development
needed
ACM-
898
Ability to manage product capacity based on
actual movements and forecasts,i.e., accounting
for inbound / outbound volumes per tank and
commodity properties
Fit
LDC Account Postings
ACM-
905
Ability to manage contracts with multiple ship-to
destinations, support volume exchanges between
related entities, maintain different transportation
Fit
Optionalities for
multiple locations,
inter/intra for volume
--- 第16页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 16 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution costs per location, and control total volume integrity when reallocating between destinations exchanges, primary basis as freight costs with valuation points. Volume integrity is part of standard product offering ACM- 906 Ability to create delivery orders spanning multiple sales contracts for the same customer, with automatic allocation based on contract balances and customer-specific tolerance parameters Fit Back-to-Back Pegging for Different Contracts with Different Details ACM- 907 Ability to generate delivery orders without immediate contract allocation, with subsequent linking capability once actual weights are confirmed from terminal tickets Fit Standard Product Offering. Contract Application after actual weights are confirmed ACM- 913 Ability to track product per tank per BL with MRN- level detail for customs reporting and operational planning Gap Standard Product Offering ACM- 923 Ability to handle containerized and break bulk operations Gap Custom Report ACM- 1016 Ability to restrict Sales Order / Nomination from being sent to Operations team prior to Prepayment Completion, except for multiple Prepayment scenario (Biodiesel) Gap Enhancement at nomination level
This Depends on whether ACM is using Nomination or SO/Approach Decision ACM- 1031 Ability to have a different view on the document flow to see that when we expand Nomination, we can see all the LDCs associated with that specific Nomination
This relates to CTRM-1006
Gap
Doc flow work center is
a workaround. Report
needs to be developed
as per required. SAC
Report might be
needed.
ACM-
1049
Ability to create all the relevant documents for
shipping
(In As-is process Sales Order can be issued
once pre-payment from customer is received, and
SO is required for shipment.)
Fit
Exist in Standard
Functionality. Forms
can be accommodated.
The triggering point
can be the nomination
or Order level
depending on decision
ACM-
1050
Ability to print output forms in PDF, MS Word and
Excel in editable format. Document need to be edit
to update the planned quantity with the actual
delivered quantity (loaded to the ship) for Export
Declaration document purpose.
Gap
SAP by default doesn't
allow form output to be
Excel / Word. The
default form output
accommodated is only
PDF. Enhancement will
be required to allow for
editing of the forms
ACM-
1052
Ability to print Loadport Agent, Notify Party,
Surveyor deatils in output forms.
Gap
Enhancement to add
additional fields
required on
Nomination-level for
fields not provided in
standard Nomination
fields
--- 第17页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 17 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1053 Ability to have dropdown list for surveyor name, Notify Party and Load port Agent
Relates to CTRM-1052
Gap
Needs enhancement to
add dropdown list to
additional fields. Need
custom table to allow
users to easily
maintain these
dropdown lists
ACM-
1068
Ability to verify Credit limit during Order/
Nomination creation with business required
appendix criteria (block/ warning based on the
policy setting)
Gap
Credit Limit Check
Solution
ACM-
1070
Ability to release blocked Nomination after credit
risk validations
Gap
Credit Limit Check
Solution
ACM-
1150
Ability to automatically notify the trader when a
sales order fails the credit check
Gap
Enhancement in
Nomination. Can
explore nomination and
LDC for order level
check and
enhancement to be
done to notify trader.
Part of Credit Limit
Check Solution.
ACM-
1156
The system should have the ability to block Sales
Order in case of breach of credit limit.
Gap
Enhancement in
Nomination. Part of
ACM- FSCM
integration at
Nomination.
ACM-
1157
The system should provide for manual control of
exemptions and overrides to credit status and alert
indicators whilst ensuring appropriate per
missioning.
Sales Order Release function. Gap Enhancement in Nomination. Part of ACM- FSCM integration at Nomination. ACM- 1173 Ability to set scheduled range date for delivery planning. Delivery dates should be within shipping period mentioned in the contract. Fit Exist in Standard Functionality, can set the shipping date range in Nomination ACM- 1174 Ability to accommodate integration to Logistic for all transportation types for delivery planning (Land, Ocean, Multi-modal)
Note for multi-moda: a lot of trucks (number can reach to hundreds) can be used to fill 1 vessel / 1 vessel unload to many trucks (hundreds) Gap Part of ACM-TM integration Solution ACM- 1203 Ability to carry over Contract notes with long text strings to be shown in Nominations Gap Enhancement in nomination / nomination form output ACM- 1204 Ability to add Product additional notes, that need to be carry over until delivery order fulfillment & billing. Gap Enhancement in nomination to copy the information from the contract ACM- 1249 Ability to draft/auto populate delivery planning information (e.g. Nominations) based on the Fit Default fields such as material, commodity is automatically
--- 第18页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 18 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution Contract information: Plant Locations, ShipTo, Delivery Period, etc. after contract approval populated. In nomination, need to mention scheduled date & quantity, optionalities. ACM- 1250 Add validations to ensure that Delivery Planning Quantity does not exceed the Contract Quantity + Tolerance and re-validate after Contract Amendment.
Contract tolerance qty must be align with WB
Tolerance qty (Upstream requirement)
Fit
Exist in Standard
Functionality
ACM-
1257
Ability to prevent GI for sales scenario, prior to
Prepayment Completion & Nomination
Confirmation.
Gap
Don't check the
payment received if
prepayment incoming
has not been done.
Standard check is
during LDC.
Block Nomination
before prepayment
received will require
enhancement.
ACM-
1260
Ability to have flexibility of adding the documents
date while printing without going through MDG
approvals
Relate to CTRM-1259
Fit
Output Forms
ACM-
1261
Ability to have flexibility of adding Vessel name
into system (as dropdown list) without going
through MDG approvals for re-use and printing
purpose
Relate to CTRM-1259
Gap
Standard Functionality:
Vessel ID/ name is
there as free text.
Search help need to be
added (dropdown list)
ACM-
1292
Ability to block sales delivery planning if incoming
prepayment has not been posted / DP Billing has
not been completed (SO cannot be created if
prepayment has not been received).
Fit
Exist in Standard
Functionality. There is
a checkbox for
Prepayment Received
which will allow/prevent
Nomination/SO from
being created
ACM-
1307
Ability to generate, save and print documents for
delivery:
- Land (SPK,IPB, Delivery Order (Surat Jalan))
- Sea (Shipping Instruction, Vessel Nomination)
relate to: TNL-058, TNL-074, TNL-075, TNL-077,
TNL-078, TNL-261
Gap
Forms to be triggered
at Order/nomination for
the operations team
.Nomination solution.
ACM-
1311
Ability to map multiple load events to 1 unload
event, and vice versa, e.g.
- Intercompany US to DS: 3 tanks from US (load
event) with different qty & qlty, combined into 1
shipment (unload event).
- for multi-moda: 1 vessel (load event) to split and
unload to many trucks (unload event) [truck-losing]
Gap
1:1 mapping between
events is available in
LDC. Need to
understand how TM
manages multi modal
scenario.
1 LDC can have only 1
load & 1 unload event,
need to break the
transaction into 2 part
--- 第19页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 19 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution (combine with Intracompany STO) ACM- 1312 Ability to integrate with existing satellite systems for quantity and quality details and ensure any changes in SAP ACM (Contract/Nomination) will be reflected to the satellite systems - Upstream: Currently only GR is integrated with WB, GI still not integrate with SAP (OTB-301), LIS - DSI Bulking non-refinery & Warehouse: WB Smart, COPS - DSI Refinery: WB Smart, iLOGS, JIMS, LIMS - Soci: WB managed by Internal IT (different with US/DS system), Quality Window Gap ACM offers APIs to integrate with 3rd party systems ACM- 1314 Ability to capture all goods movement (GI/GR) details (quantity, quality, sloc, batch, etc.) without any buy/sell transaction eg. movement from one Sloc to another under the same company code As-is: PO STO Fit Non-CAS STO allows transfer within slots of same company code.
Part of KDD Topics: ACM Product Scope, whether STO will be in ACM/ MM ACM- 1414 Ability to accommodate a Biodiesel scenario where SMART buys from SBE with FOB Incoterm. But SMART directly delivers this shipment to customer which should be considered like any other Biodiesel Transactions (can claim BPDP as well). This is like a backstop transaction
note(CH) : there will be 2 contracts
contract #1 : SMART Sell to Customer
contract #2 : SBE Sell to SMART (intercompany),
ship to customer
Fit
Back-to-Back Pegging
ACM-
1422
Ability to capture back to back sales & purchase
scenario, in example:
Contract 1: Upstream (GBE) sales to customer 3rd party Contract 2: Upstream (GBE) purchase from intercompany Upstream (Mill), but Mill need to send directly to the 3rd party customer in Contract 1. This 2 contract need to be linked together as a back-to-back transaction.
Relate to CTRM-1404 Fit ACM Back-to-back Pegging Scenario ACM- 1424 Automation of Nomination Creation from contract approval for ID Intercompany transactions (US- US, US-DSI, DSI-DSI, DSI-SOCI) Gap Enhancement at nomination level
--- 第20页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 20 of 167 3.1.2 Business Process Flow This section provides the process flow diagram at BPH L4 with detailed information for each of the process steps.
3.1.2.1 Create Nomination
Figure 3.1 - Create Nomination Table 3.1 - Create Nomination Activity Role Transaction Code/Fiori App ID Description Open Maintain Nomination Fiori APP and Select Create Nomination Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Create Nomination and enter header details: 1. Nomination Type 2. Trans. System 3. UoM Add Fee (Header Fee) if needed Scheduler (ACM) O4NM/ Fiori Tile: Maintain/ Change Nomination Add unplanned fees during nomination at header level
--- 第21页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 21 of 167 Activity Role Transaction Code/Fiori App ID Description Enter Contract & Item in the Ref Doc & Ref Doc item field if Ref Doc is available Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination If reference document is available, then enter the trading contract number in the Item Ref Doc & Ref Doc Item field.
Nomination line items will inherit respective contract details.
Reference Document Indicator for Sales is “M”
Reference Document Indicator for Purchase is “L”
Reference Document Indicator for Intercompany is “N” For Non-CAS STO, Enter RDI for No Reference Document (Non-CAS STO) Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Reference Document Indicator for Non- CAS STO is “T”
Refer to 3.2.3.6 for Ocean/ Multi-Modal
Scenarios which will be using non-CAS
STOs.
Enter Scheduled Date
Scheduler
(ACM)
O4NM/ Fiori
Tile: Maintain
Nomination
Enter the planned date for the nomination
line item.
Select ACM Back-to-Back
from the Peg Items Icon
Scheduler
(ACM)
O4NM/ Fiori
Tile: Maintain
Nomination
For Back-to-Back scenarios, only if "Back-
to-Back Pegging needed?" is Yes.
Refer to 3.1.3.4 for Back-to-Back Scenario/ Pegging Select the Line Items relevant for B2B and select the PEG Items Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Peg the relevant line-item
Refer to 3.1.3.4 for Back-to-Back Scenario/ Pegging Add Fee/ Expenses (Item Fee/Expenses Relevant) Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Add fees on nomination line item only if "Item Fee/Expenses Relevant?" is Yes. Save Nomination Line Item Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Click Save to trigger the validation and checks. Schedule & Confirm Nomination & Save Scheduler (ACM) O4NM/ Fiori Tile: Maintain Nomination Click Schedule & Confirm to trigger the final validation and checks.
Final confirmation depends on passing the Credit Check Pass, completion of TM Planning (if relevant), and checks whether valid LC is assigned.
--- 第22页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 22 of 167 3.1.2.2 Release Credit Blocked Nomination
Figure 3.2 - Release Credit Blocked Nomination
Table 3.2 – Release Credit Blocked Nomination
Activity
Role
Transaction
Code/Fiori
App ID
Description
Manually Remove Credit
Block
Credit Risk
Manager
O4NM/ Fiori
Tile: Maintain
Nomination
Or
Custom
Report (if
needed)
To remove credit block at Nomination by
manually overriding removal of credit
block (accept risks)
--- 第23页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 23 of 167 3.1.3 Solutioning 3.1.3.1 ACM Nomination In the context of agricultural contracts, a nomination refers to the process of selecting and specifying the details of a specific delivery or shipment of commodities. It is a planned arrangement between the buyer and the seller to designate a specific quantity, quality, and timing for the delivery of goods as per the terms of the contract.
When a nomination is created, it typically involves providing specific information such as the Schedule date, location, quantity, and any other relevant details related to the shipment. This allows both parties to align their operations and logistics to ensure smooth and timely delivery of agricultural commodities.
Table 3.3 - Nomination Header Information for GAR Nomination Type Trans. System ACMC GAR-TS
3.1.3.2 RDI Types RDI or Reference Document Indicator is a key field that identifies the type of reference document being linked to a nomination item. When ACM Contract is used as a reference document in Nomination, RDI Type will be auto populated in the Nomination item. In case of Stock Transfer Order Nomination Planning, RDI Type T is used. Below is the list of RDI Types and its description.
Table 3.4 - Nomination RDI Types for GAR RDI Type Description L Unreleased Trading Contract – Purchase Order M Unreleased Trading Contract – Sales Order N Unrelease Trading Contract – Stock Transfer Order (Intercompany) T Stock Transfer Order (Non-CAS STO)
3.1.3.3 Non-CAS STO Nomination A non-CAS STO nomination refers to a nomination that references a Stock Transport Order (STO) but is not processed through the CAS (Contract Application Settlement) functionality.
Refer to Section 4.3 Indonesia Goods Movement Scenarios Where Non-CAS STO are used in GAR.
--- 第24页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 24 of 167 3.1.3.4 Back-to-Back Nomination Item Pegging Back-to-back nomination pegging functionality is a specialized feature in SAP Agricultural Contract Management that enables the matching and linking of supply and demand nomination items for coordinated bulk shipment planning and scheduling. Below are the visualized to-be process for GAR Back-to-Back Pegging Flow from Contract to Settlement.
Figure 3.3 - ACM Back-to-Back Pegging Process Back-to-Back pegging is used when demand side and supply side quantity are matched. This peggging need at least two nomination pair (supply and demand side) to do the back-to-back pegging.
For Singapore non-backstop transaction, back-to-back pegging still can be leveraged if needed.
3.1.3.5 FU Generation at ACM Nomination* When ACM nominations are marked as "TM Relevant" Bulk Transportation Extension (BTE) facilitates the automatic creation of Freight Units (FUs) in Transportation Management based on nomination data at save.
This FU then is to be used in Transportation Management System (TMS) to be split, assign an FO, and assign a carrier to the FO itself as below. Note that confirmation of Nomination requires the subcontracting status to be carrier assigned.
Figure 3.4 - TM Information Tab at Nomination Item
--- 第25页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 25 of 167 3.1.3.6 Nomination Integration with Satellite System (3rd Party – WBs etc). It is common practice for businesses and it is required to confirm schedules/nominations to the weighbridge for easier linking of deliveries with the ticketing information. In such cases an interface is required between ACM and Weighbridge at Nominations and subsequently at LDC. Indonesia and China WB are to be handled separately.
3.1.3.7
Nomination Integration with TM
Above explanation on FU Generation at ACM Nomination is one of the key highlights from the bigger
subset of available integrations from ACM to TM through Bulk Transportation Extension (BTE).
In the nomination transaction O4NM, there has been BTE specific enhancements done on the UI.
Following are the BTE specific fields added in nomination item list:
1. TM Relevant flag – The TM Relevant flag is to mark a nomination item relevant for TM
integration.
a. When this flag is checked - On nomination save, integration with TM triggered
resulting in creation of Freight Units.
b. When this flag is unchecked - On nomination save, any Freight Units created will be
deleted.
c. The editability of this flag depends on the TM Integration status.
2. FU count – The FU count shows the number of Freight Unit (FU) created after TM integration
for a nomination item. It displays count in format (Total/Unplanned/Planned).
3. FOR count - The FOR count shows the number of Freight Order for the nomination. It displays
in the format (Total/Unplanned/In Tendering/Carrier Assigned)
4. TM integration status – This traffic light status shows the status of TM integration.
5. TM Planning block on Creation – This flag is to block Planning in the FUs created by
Nomination Integration
Note that FU creation is proposed at Nomination Saved. This would be further discussed in the detailed design discussions whether to block FU nomination altogether before a valid LC is assigned.
TM information tab added in ACM view, displaying the following fields: 1. Source Location and Destination location. 2. FU created, FOR assigned to the FU and LDC integrated with FOR. 3. The scheduled, requested, and acceptable dates of FU and FOR. 4. TM planning block flag which, if set, blocks the planning of FU on creation. 5. Planned net weights and Actual Net Weight 6. Carrier and its description. 7. Subcontracting status
ACM-TM Integration is not relevant for Non-TMS Country like Singapore.
--- 第26页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 26 of 167 Bulk transportation extension (BTE) for SAP Agricultural Contract Management involves the following integrations between Agricultural Contract Management and Transportation Management:
Figure 3.5 - ACM-TM Integration through BTE 3.1.3.8 Credit Check at Nomination 1. As detailed in the Business Process Flow on Section 3.1.2.1 Create Nomination, Credit Checks will be done at the point of nomination save. If the Nomination is blocked due to Credit Checks, refer to Business Process Flow on Section 3.1.2.2 Release Credit Blocked Nomination. As explained above, to remove credit block at Nomination, manual override to remove credit block (accept risks) is required by the credit risk team.
--- 第27页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 27 of 167 Lc e 3.1.3.9 LC Check at Nomination As detailed in the Business Process Flow on Section 3.1.2.1 Create Nomination, LC Checks will be done at the point of nomination confirmation with details as below: • For contracts having LC assigned, LC relevant payment term is provided (LCXX). • At Nominations, system validates if LC is provided at line item if reference contract is having LC payment terms. • Checks executed during confirmation Nomination if the LC is Valid. • If any Validations fail, the Nomination is blocked with LC Block status which can be either: ▪ Manually released by authorized personnel ▪ Providing the correct details and reconfirming the Nomination • Updating the LC at Order (generated from LDC) to be automated (Mass Updating). • An LC validation will also be provided at Settlement to prevent postings • At LDC, the Fin Doc information provided at the Nomination level is automatically passed down to the Order level.
Figure 3.6 - Statuses at Nomination
Additionally:
•
Validation group functionality will be utilized at Nominations
•
SAP delivers multiple check routines, and these are included in the standard 01 validation
group. Each validation group is assigned to a nomination type. This validation group leads to
the assigned check routines.
•
The messages produced by the check routines are displayed in the nomination log. In
Customizing for Define Validation Groups, users can determine if the messages are error,
warning, or information messages and whether incomplete nominations are saved as
incomplete
•
Validation group functionality, therefore, allows users to set up multiple checks and status
codes at the Nomination level.
•
Custom check routines can be created by implementing BAdI
--- 第28页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 28 of 167 3.1.3.10 Nomination Output Forms A Nomination Output Form is a document template used to generate transportation requests and other nomination-related documents either at creation of nomination and or at nomination confirmation. Details of forms requirement are captured on section 3.1.1 Highlighted Key Business Requirement for Delivery Planning. Table 3.4 - Export Forms Document Doc. Number Format Proforma Invoice ETP/E3328/0623/00001 Invoice ETI/E3310/0425/00065 Contract Reference ETC/3310/100425/0002 (DDMMYY/RN) — RN should be defaulted to zero on daily basis Shipping Instruction SI/E3328/0623/00001 Packing List PL/E3328/0623/00001 Appointment Letter AL/E3328/0623/00001
This is the format numbering formula that can be changed according to GAR business needs and will be stamped into the Documents Template upon document generation. Details on all nomination output and form numbering across all form types and regions will be elaborated in the detailed design.
Example formula (ID):
return "ETP/E" + COMPCODESALESORG + "/" + MMYY + "/" + RN;
This will generate the ETP Reference Number in the document as: ETP/E3328/0623/00001
COMPCODE = SAP company code SALESORG = SAP sales organization code MMYY = month year RN = database sequence running number
Table 3.5 - Pre-Shipment Forms
No Document 1 Trade Confirmation CxC (for Non-Backstop) 2 Shipping Instruction 3 Appointment Letter 4 Proforma Invoice 5 Packing List
This only applies for Export (Origin) & Non-TM Transactions Table 3.6 - Post-Shipment Forms No Document 1 Tender Document/ Shipment Advice 2 Manual Invoice (include GAR Bank Details)
Please note that form output requirements are still subject to refinement. The mapping of these form outputs will be part of subsequent detailed design discussion.
--- 第29页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 29 of 167
3.2
Goods Movement & Quality Capture
3.2.1
Highlighted Key Business Requirements
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
ACM-
040
Ability to input and update delivery date
Gap
Enhancement to be
done based on req
ACM-
058
Ability to enable direct distribution - External
Warehouse Management (EWM) * Support direct
customer pickup operations * Enable delivery of
palm products from external warehouses * Handle
margarine product deliveries * Facilitate delivery
without further processing
Gap
KDD open for EWM -
ACM
ACM-
097
Ability to tracking parcel status throughout
lifecycle:
- Manage parcels based on
contractual/planned/nominated/actualized status
- Support status tracking even when parcels are
split
- Feed parcel status into position and P&L
management
- Ability to have notification alert based on
PORAM / FOSFA (ex. Receive reminder
notification to receive vessel nomination from
buyer XX days before delivery date)
Fit
Standard ACM
functionality offerings
ACM-
099
Ability to manage the complete parcel lifecycle:
- Split one parcel into multiple parcel allocations
(Application splitting is allowed)
- Support multiple discharge locations (Contract
optionality)
- Handle and Record separate title transfer dates
and documents (Document Flow Workcenter)
- Move parcels from planned > nominated >
actualized status (in ACM status planned
(nominated) > delivered > invoiced) - terminalogy
- Capture all relevant information from supporting
documentation
- Process quality and quantity
adjustments/escalators (DPQS functionality)
- Create multiple plans for execution against open
contracts (Multiple nominations exist based on
quantity for a single contract)
- Capture dates, inventory locations, and
quantities (auto-captured weighbridge and ACM
interface)
- Track settlement instructions and comments
(track status create > release > approve for
settlements + notes)
Fit
Standard Product
Offering
ACM-
100
Ability to handle quantity changes and
adjustments:
- Handle fixings without lower tolerance
- Manage short shipments manually
- Create new cargoes from cumulative short
shipments
- Support splitting (e.g., 10k MT into 2k, 3k, 5k)
- Capture actualized quantities (e.g., 1.8k, 2.8k,
4.8k)
Fit
Load Data Capture
--- 第30页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 30 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
- Close positions and create new cargoes for
remaining quantities
- Manually apply quantities up to overfill tolerance
- Automatically apply quantities without using
tolerance
- Support over-allocation
ACM-
101
Ability to link parcels with inventory:
- Discharge into (build) inventory - GR (ACM)
- Withdraw from inventory- GI (ACM)
- Track losses/gains between load and discharge
ports (ACM)
- Measure differences for insurance purposes
(ACM)
- Transfer cargoes between ships (trans-shipment)
(ACM)
Fit
LDC created GI/GR
which updates the
inventory
ACM-
157
Ability to enable documentation tracking:
- Provide mass balance reporting at any time
- Support filtering and reporting capabilities
(custom report based on confiragtion defined by
business users)
- Manage temporary storage of sugar at port
facilities (part of EDM, ID might not be using port
as a storage location but need for sugar)
- Support dual documentation processes (manual
and electronic) (send output printout and EDI or
email via electronic)
Gap
Mass Balance
Reporting setup
ACM-
198
Ability to manage vessel references:
- Handle cases where Purchase is linked to
Vessel A (Indonesia to Malaysia)
- Support Malaysia to Indonesia routes with
Vessel B linked to Sell deal
- Show Vessel B on invoices
- Use Vessel A in SAP posting
Gap
Form output can be
enhanced to show
Vessel B
ACM-
214
Ability to track BL information:
- Track barges/batches back to original vendor PO
- Allocate freight based on BL/loaded quantity
- Input quality per truck/vessel
Fit
LDC and Forms
ACM-
219
Ability to include sustainability certifications:
- Mark CPO with sustainability labels (ISCC)
where needed
- Maintain 1:1 relationship between contract and
certificate on load side
- Capture certification information (number, type,
premium)
Gap
Enhancement to be
done based on req
(add fields for
certificate details at the
contract level)
ACM-
321
Ability to manage quality standards:
- Enforce NIOP standards as agreed in customer
contracts
- Validate compliance with quality requirements
Gap
DPQS Solution +
Enhancement for field
ACM-
332
Ability to match inventory in postings
- Match FIFO upon discharge
- Link sales and purchases in combined postings
- Support drawing from multiple contracts based
on FIFO
Gap
KDD Batch
Determination
ACM-
390
Ability to handle Proof of Delivery in the unload
event of the LDC process, requiring POD input to
Gap
POD works in unload
event
--- 第31页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 31 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
complete the process when unload events are
needed based on incoterms.
ACM-
393
Ability to control reversal of settlement/LDC
processes through authorization settings, with
reversals reopening nominations and returning
quantities to the contract level
Fit
Auth can be controled
through SAP Security
ACM-
399
Ability to have the flexibility to facilitate different
size of LDC linked to BL and vice versa
- Example, Multiple BLs linked to 1 LDC
Gap
Enhancement to be
done based on req
ACM-
410
Ability to view intercompany sales invoice
numbers through the Document Flow of the
contract or Stock Transport Order, rather than
directly on the intercompany purchase invoice
Fit
Doc flow
ACM-
476
Ability to allow goods to remain classified as
inventory throughout the transaction lifecycle until
final settlement. Inventory status should be
maintained regardless of intercompany billing
status.
Fit
Aligned with standard
solution behavior
ACM-
523
Ability to automatically generate journal entries for
both load and unload events based on
weighbridge integration
Fit
Standard Product
Behavior
ACM-
524
Ability to create system entries for goods
movement at both loading and unloading stages
Fit
Standard Product
Behavior
ACM-
543
Ability to access and utilize the outturn formula via
DPQS within the system
Fit
This requires DPQS
set up - Customization
ACM-
549
Ability to manage multiple LDCs separately when
there are multiple Bills of Lading (e.g., 5 BLs
requiring management of 5 separate LDCs)
Fit
System Design will
allow 1LDC to have
multiple BLs
ACM-
552
Ability to process 2 BLs with individual document
bypass to ADM requiring 2 separate outturns
Gap
DocByPass solution
via Strings Work
Center
ACM-
553
Ability to establish outturn threshold percentage
primarily at the contract level
Gap
DocByPass solution
via Strings Work
Center
ACM-
622
Ability to enter batch numbers at Loading
Discharge Certificate (LDC) stage for tracking PK
to PKO conversion
Gap
Part of Virtual Crush
KDD Solution
ACM-
698
Ability to configure pricing completion
requirements before or after execution with
custom logic at LDC level
Update:
Ability to Price contract during or after LDC
Gap
Pricing routine creation
required
ACM-
706
Ability to execute LDC without pegging contracts
for individual purchases and sales
Fit
Standard ACM
functionality.
ACM-
707
Ability to create multiple LDCs in mass
Gap
Excel upload for Mass
LDC creation will need
a cUstom Development
ACM-
708
Ability to attach surveyor documents at the LDC
level
Fit
Attachments can be
added at LDC Level.
Recommended to have
them stored at a
--- 第32页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 32 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution different server and attach a link instead ACM- 710 Ability to capture and track Bill of Lading information through LDC with visibility in goods movement documents Gap Any other details other than the Bill of Lading number needs custom development to accommodate ACM- 711 Ability to automatically create purchase orders, deliveries, goods movements, and corresponding sales documents during LDC execution Fit SD/MM documents are automatically created at the background when LDC is posted. ACM- 740 Ability to link DPQS to customer specifications Fit Separate DPQS can be defined per certification level/customer expectation for the same list of materials and plant combination ACM- 742 Ability to compare quality results at load event with contract quality parameters Fit DPQS added ot the Contract has the details of the expected Quality.
LDC Load event records the actual Quality per Load.
Application Document for that LDC will show the Accept/reject status. ACM- 743 Ability to track CoAs, certifications, and quality parameters with customer linkage Fit Separate DPQS can be defined per certification level/customer expectation for the same list of materials and plant combination ACM- 749 Ability to manually select pricing lots during load application Fit Can achieve this using the Manual Application Workcenter ACM- 802 Ability to change materials within DPQS schedule during LDC with automatic premium/discount recalculation Fit Standard Solution Behavior ACM- 803 Ability to handle negotiated premiums through optionalities without requiring fixed DPQS rules Fit Standard Solution Behavior ACM- 812 Ability to mass upload gate pass data through Excel for Load Data Capture Fit Standard Solution Behavior ACM- 818 Ability to cancel partial quantities after goods receipt for error corrections (not for standard transit losses which should be captured at actual receipt) Fit Standard Solution Behavior
--- 第33页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 33 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 839 Ability to adjust inventory for rejected/damaged goods through complaints process Fit Can use dispute process at LDC to achieve this ACM- 852 Ability to monitor gain and loss (cause: evaporation) and post it to finance side.
Current solution:
1) Downstream Bulk - custom program to auto
GR/GI for the "lost in transit"
2) Upstream - GI Loss from temporary storage
location
[27 May - I2C] Need to enhance system to avoid manual adjustment due to error POD. Ensure POD reversal can automatically posted when Billing reversal is posted
Transferred to CTRM-1339 Fit Setup required for auto trigerring loss- movement ACM- 897 Ability to manage blending operations with standardization for quality parameter control, and reprocessing through both external service providers and internal operations Fit ACM Production Services Functionality ACM- 911 Ability to select and allocate stock based on commodity properties defined at contract level, with filtering capability for quality parameters, customs attributes, and usage specifications Gap Batch Management Solution ACM- 933 Ability to generate DUA form directly from trading platform. Information needed includes HS Code, usage type, DUA number, MRN, TORO Information,etc so that selling contract can get correct incoming batch.
Assume batch characteristics is used, user request for auto derivation from contract to batch (instead of manual fill when GR). Gap TORO/DUA Validations and output forms generation to be configured ACM- 1006 Ability to settle multiple GR/GI in one contract altogether to be able to match the quantity with the invoice / prepayment invoice quantity for tax tracking purposes (There should be a view similar to ME23 for this purpose)
e.g. during GR, we can knock off the prepayment
invoice with the exact GR quantity according to
the prepayment amount.
Gap
- Ability to settle
multiple GR/GI can be
done via settlement
(multiple LDCs can be
settled together).
- For Purchase:
Application Splitting
per Quantity as per
Invoice from Vendor
requires enhancement
- However, custom
view similar to ME23
needs to be created
per business
requirement.
ACM-
1019
Ability to create LDC events prior to prepayment
execution (Purchase scenario ONLY) in the event
that goods are received even before any
prepayment has been done
Fit
Proposed Solution is
using the workaround
to manually tick the
"Prepayment Paid" to
--- 第34页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 34 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution allow for LDC. Or we can use a custom logic to enable LDC for Indonesia Purchase only ACM- 1033 Ability to track debit/credit note for claims tracking purpose (ex. Biodiesel Claim to BPDP, Claims to Transporter) under one contract document flow and to know whether a claims has been processed or unprocessed
(For BPDP Claims, 1 Debit/Credit Note could apply to multiple Contracts) Gap Enhancement needed at DFW and debit/credit note. Reference field at credit /debit note can be utilized. The enhancement will allow the Document Flow to pick up contract- relevant Credit/Debit Note
Claims to BPDP -> integration with SD Billing Claims quality/ quantity to vendor/ transporter -> claims via separate FI Billing, or use Credit/ Debit Memo ACM- 1041 Ability to input AJU number (AJU Number can be received from Surat Persetujuan Pemasukan Barang (SPPB) and Dokumen Bea Cukai (BC)) into the each GR for purchase delivery to Bonded Zone. (Vendor needs to have SPPB and BC to be able to deliver to bonded zone) Gap Custom check which prevents LDC creation incase the details are not available ACM- 1056 Ability to maintain PEB details (PEB Date & Number) in system (Export Declaration required right after loading)
As-Is:
EA unit raises PEB details and these details (PEB
Number & Date) shared with Back Office team.
BO team input these details into system for billing
purpose.
Gap
Enhancement will be
required to add this
PEB details field at
Settlement Level or
LDC level. But
workaround is
available
ACM-
1172
Ability to accommodate conversion of unit of
measurement (eg. L to kg, kg to L)
eg. for Biodiesel FAME, contract, billing and
physical goods loaded are recorded in Liters, but
goods movement in SAP need to be recorded in
Kg.
As-is: this unit of conversion from L to Kg is done
manually using ASTM table based on density ,
temperature, etc. and users need to input the
actual PGI weight during GI.
Relate to CTRM -1213
Update from E2E session on 09 Oct: Users want the conversion to be done by system; users will input the necessary paramters (eg. temperatures, Gap Add Kg and liters field in LDC to be manually updated and provided by users. Enhancement.
--- 第35页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 35 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution density) and system will automatically do the conversion based on the ASTM tables (ASTM 54/54B 53, 56) ACM- 1174 Ability to accommodate integration to Logistic for all transportation types for delivery planning (Land, Ocean, Multi-moda)
Note for multi-moda: a lot of trucks (number can
reach to hundreds) can be used to fill 1 vessel / 1
vessel unload to many trucks (hundreds)
Gap
Critical gap based on
ACM-TM integration
solution
ACM-
1175
Ability to capture GI/GR when there is no
weighbridge integration, eg.
- for ocean deliveries
- jual-beli dalam satu tangki - buy and sell in one
tank without physical goods movement (3rd party,
intercompany)
*) For intercompany jual-beli dalam satu tangki,
since load and unload quantity is the same,
possible to automate unload event once load
event is created.
Gap
Implement API.
Standard APIs will be
provided with mapping
to all the custom field
ACM-
1176
Ability to capture full / partial reject or returns
process including the applicable return accounting
posting (eg. reverse GI/GR). This includes "Tukar
Guling" (similar goods swap)
- As-is for goods reject: customer reject goods
once arrival at customer location because quality
does not meet expectations, hence no billing to
customer yet.
partial reject: reverse/cancel GI qty, GI qty that customer accept and GR rejected qty to penerimaan lain-lain full reject: reverse/cancel GI qty, if there are any gain/loss, gain/loss tanki with remarks. if loss qty exceed tolerance, will be charged to transporter. - As-is for goods return (very rare case): goods
arrival at customer location, kept in customer tank,
then goods are returned to GAR after several
days. Hence. billing to customer is done.
Fit Exist in Standard Functionality.
Use return order to capture the returned product from customer (not using GI reversal), with goods movement type to a spesific restricted inventory. Option 1: Perform return and create new delivery against the same contract. (can see if returns have happened) Option 2: Perform LDC correction (reversal - reverse outbound delivery, goods movement, etc.) and generation of new documents, and then continue with settlement. (cannot see if there are any returns) ACM- 1251 Auto create Journal of Gain/Loss in transit based on the Incoterm, e.g. - For purchase incoterm Origin, discrepancy between GR in Transit vs Qty received in WB buyer, posted as gain/loss in buyer side.
- For sales incoterm Destination, discrepancy between GI in Transit vs Qty received in WB seller, posted as gain/loss in seller side . Fit Exist in Standard Functionality ACM- 1256 Ability to do GR prior to Prepayment (ex. In some Purchase scenarios, some longstanding vendors Gap Prepayments , enhancement needed to based on req.
--- 第36页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 36 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution want to push items into Sinarmas before prepayment has been completed) - Create Contract - Prepayments Request - Contract Approval - Checkbox: Release for Settlement - Prepayment Request Posting (KDD topic: Noted Items vs ABD) - Checkbox : Payment Received/ Payment Made (when payment has been made/ received) - LDC (for GI/GR posting) Use Manual workaround or custom logic required to automate this. ACM- 1275 Ability to capture product batch details during goods movement (GI/GR) for traceability purposes 1. Purchase GR - input batch according to the policy ruling 2. Sales GI - need to be able to automatically select batches based on certain rules (e.g. FIFO or FEFO), or select multiple batch manually (e.g. for packed products), select based on minimum shelf life 3. Intercompany transaction: - GI one batch, GR one batch (1 to 1) - GI one batch, GR one batch with different naming (1 to 1') - GI multiple batch, GR one batch (many to 1) - GI one batch, GR no batch (1 to none)
Refer to e-mail from 02 July "Batch Split Requirement"
for EWM relevant materials - batch information will
be fetched from EWM order to LDC
Gap
Enhancement to trace
batch
ACM-
1287
Ability to capture all goods movement (GI/GR)
details (quantity, quality, sloc, batch, etc.) for
standard incoterms (eg. FCO/LCO/FOB/CIF/DAP,
etc.)
Fit
Exist in Standard
Functionality;
Incoterm tells when
title transfer happens.
Governing weight is
tied to billing.
ACM-
1288
Ability to capture all goods movement (GI/GR)
details (quantity, quality, sloc, batch,etc.) for
special incoterms
eg.
1. Weightbase and/or grade is different compared
to incoterm title transfer
2. Based on contract terms, governing weight and
grade is from Origin -> but different points, eg.
Governing weight is from Origin (Vessel) -
Fit
Exist in Standard
Functionality;
create LDC per tank,
need to track quantity
per tank if need to
track quality per tank
--- 第37页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 37 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution meaning qty is inputted based on BL in vessel [Shipped tank] Governing grade is from Origin (Tank) - meaning it is required to track the quality per tank [Shore tank] ACM- 1300 Ability to integrate with QM to push delivery information needed for Certificate of Analysis such as: - No Delivery - Vessel / truck number - Batch (barang yang dibawa di truck tsb) - Quality info Refer to email on 3 Jul : Downstream Indonesia CoA Template - Fields Required
Relate to CTRM-1301
Gap
Standard APIs are
provided; QM and
ACM interface
ACM-
1305
Ability to generate, save and print out documents
(as-is documents: contract, PO, SO, DO)
Gap
Form Output
ACM-
1306
Ability to generate document (as-is: Sales/Delivery
Order/E-mail) to inform Operations on:
Material, Quantity, Quality, Delivery Period,
Incoterms, Plant locations, Certifications, Extra
Remarks on packaging/accessories etc.
Gap
Form Output
ACM-
1308
For Third Party transactions, Load and Unload
events are not mandatory according to incoterm
and governing weight & grades.
eg. Purchase --> Incoterm, Governing weight &
grades: Destination, Load Event is not mandatory
Sales --> Incoterm, Governing weight & grades:
Origin, Unload Event is not mandatory
Fit
This is the designed
behavior of ACM
ACM-
1309
For intercompany transactions, need to make load
and unload events mandatory.
eg. US --> DS -- (GR/GI in transit with Inventory)
- Incoterm: Origin. Governing weight & grades:
Origin
US GI based on Load event. Billing based on
Load Event. DS GR based on GR in transit. DS
inventory updated based on Unload Event, with
gain/loss (if any).
- Incoterm: Destination. Governing weight &
grades: Destination
US GI in transit based on Load Event. DS GR
based on inventory or Unload Event / US GI
gain/loss. Billing based on Unload Event
Fit
This is the designed
behavior of ACM
ACM-
1311
Ability to map multiple load events to 1 unload
event, and vice versa, eg.
- Intercompany US to DS: 3 tanks from US (load
event) with different qty & qlty, combined into 1
shipment (unload event).
- for multi-moda: 1 vessel (load event) to split and
unload to many trucks (unload event) [truck-losing]
Gap
1:1 mapping between
events is available in
LDC. Need go
understand how TM
manages multi modal
scenario.
1 LDC can have only 1
load & 1 unload event,
need to break the
transaction into 2 part
(combine with
Intracompany STO)
--- 第38页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 38 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1313 Ability to capture all goods movement (GI/GR) details (quantity, quality, sloc, batch, etc.) and compare tolerance between quantity from seller vs. quantity received by buyer eg. compare quantity from seller's weighbridge must be within tolerance of 0.3% with quantity received on buyer's weighbridge Gap Currently there is no validation at LDC if there is difference in Load and Unload event weights. Enhancement needed based on business expectations If any action is required if the qtty change is greater than 0.3% Separate report can also be created to inform about the variances in load & unload event weights for further action ACM- 1315 Ability to add approval workflow when goods movement data is not automatically integrated to system (manually entered/ upload)
Relate to: CTRM-1175 Fit Roles and Authorizations to execute LDC will provide the desired results ACM- 1316 Ability to split 1 delivery (truck/vessel) to fulfill multiple contracts/PO/SO Fit Application split allows splitting 1 delivery across multiple contracts ACM- 1317 Ability to input AJU number into each GI for sales delivery from Bonded Zone
Relate to CTRM-1041 Gap AJU field to be added in LDC and becomes mandatory for Bonded scenario. Custom field ACM- 1318 Ability to link multiple BLs to 1 LDC (eg. customer request to split BLs from 1 shipment for 1 contract) - BL number is to be added in invoice to customer Gap Enhancement for a custom table can be added in LDC to show the quantity and BL number for a delivery. Ideally, recommendation is to have 1 BL per LDC ACM- 1319 Ability to capture additional costs related to goods return process (if any, eg. demurrage/truck overnight costs).
As-Is process differentiated between reject & return process due to quality issues: - Bulk & semi bulk products = Reject process = cancel the GI (reversal GI), can be full or partial qty - Branded = Return process, has billing/ tax implication and goods might not always be returned (e.g. broken packaging, oil already spilled)
relate to: TNL-259, TNL-288 Fit A relevant fee type can be added at the settlement for returns scenario. ACM- 1338 ACM should have different Order Type for both SO & PO compared to standard SD/MM document. This is to differentiate ACM documents Fit ACM need to config a different order type
--- 第39页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 39 of 167
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
from non-ACM docs. And also to differentiate
when there's enhancement required only for ACM
from standard SD
(OR).
ACM-
1339
Ability to post gain/loss movement when load and
unload quantity is different
eg. for Purchase, incoterm, governing weight:
origin,
if there is a Loss --> scrap movement, as expense
Current solution:
1) Downstream Bulk - custom program to auto
GR/GI for the "loss in transit"
2) Upstream - GI Loss from temporary storage
location
[27 May - I2C] Need to enhance system to avoid manual adjustment due to error POD. Ensure POD reversal can automatically posted when Billing reversal is posted
Relate to CTRM-1251
Gap
Movement types to be
configured and
mapped for LDC
scenarios considering
the Gain/loss based on
the title transfer.
ACM-
1348
OTB-274:
Ability to integrate SAP and WB during contract
termination. WB should have interface with SAP
on the last shipment information upon contract
completion / rejection.
Action in SAP is to close Contract / Sales Order
Fit
WB Integration with
LDC is part of
integration while auto
closure of contracts
based on the
consumed quantity can
be done via batch job.
LDC cannot be created
for contract with zero
qty to be fulfilled.
ACM-
1349
OTB-287:
Need to have integration between WB and SAP
for GI Reversal.
SAP is expected to reverse the GI and POD (if
applicable) based on WB ticket reversal.
Fit
LDC correction allows
reversals of GM and it
can be triggered from
the WB.
ACM-
1350
Ability to connect with QM master data to capture
the quality grade spec (MSDS - Master Safety
Data Sheet/ RPS - for Oleo, CP grade data for
DSI). e.g. during loading outbound delivery, need
to check the quality analysis details from QM
Fit
QM integration will
update the analysis
and quality details in
the LDC for any
delivery.
ACM-
1403
Ability to ensure automatic posting of the correct
gain/loss for inventory in-transit.
e.g. for Sales Transaction posting with Incoterm
Destination, should ensure that the Goods Issue
Quantity + Gain/Loss Quantity = Billing Quantity.
(e.g. Currently the POD Error is fixed via T-Code:
MBST/ MB1A, MB1C)
Gap
Enhancement as per
GAR's requirement.
Based on the
scenarios, few of the
Gain/Loss postings
deviate from standard
and require
enhancement.
ACM-
1404
Ability to ensure that the accounting postings
generated from LDC process assigned the correct
person for "Created by" field. (e.g. Operations PIC
that will input the LDC details will be the "Created
by" PIC for the LDC Accounting Postings)
Concern is because in As-Is process, the POD posting is done by Back Office Sales based on the Fit SAP ACM Standard Behavior. PIC of the postings will always refer to the one responsible for LDC.
--- 第40页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 40 of 167 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution POD details from the operation team (???) - confirm with Vienna
14/10 : [WW] For Incoterm = Destination, since the gain/loss posting is triggered together with revenue recognition, the posting "Created By" is showing as Back Office, while actually this should be the responsibility of Logistic team who perform the POD/ Unload Event. ACM- 1417 Ability to have a contract reference field in debit/credit memo creation form in FI module to be linked to the contract (this would allow debit/credit memo created in FI to be seen in document flow view). Gap Enhancement to link and show at DocFlow ACM- 1423 * For purchase scenario (FOB), freight cost need to be settled into material valuation/inventory account (with reference to company code buyer). * For sales scenario (CIF), freight cost need to be settled into profitability analysis/COPA (with reference to company code seller). * For intercompany transaction that trigger STO- Intercompany based on above incoterms, system can automatically determined how the freight cost is settled (inventory for purchase and COPA for sales)
Refer to E-mail from Joseph (sent 24 Sept 2025) Fit Product offering ACM- 1435 Ability to add EUDR-related fields (eg. Mill Name, Mill UML ID, EUDR Status) in Goods Movement level Note: EUDR planning to go-live by 2026 Gap Custom Fields at LDC
--- 第41页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 41 of 167 3.2.2 Business Process Flow This section provides the process flow diagram at BPH L4 with the detail information for each of the process steps.
3.2.2.1 Maintain Load Data Capture for 3rd Party
Figure 3.7 – Maintain Load Data Capture for 3rd Party Table 3.7 - Maintain Load Data Capture for 3rd Party Activity Role Transaction Code/Fiori App ID Description Maintain Load Data Capture (LDC) Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture
or LDC Mass Upload Report There could be three ways of capturing LDC: 1. WB & QM Systems Integrated 2. Manual (Single) 3. Mass Uploads For WB & QM Systems Integrated LDC Generated Automatically
For Mass Upload Select LDC Mass Upload Report, complete details, upload, and validate.
For Manual (Single)
Select Maintain Load Data Capture
Fiori Tile and subsequent process
explained below.
Select Create LDC Object
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the create button
Enter details LDC
Document Reference
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Enter Nomination Key to-be linked
with Load Data Capture (Load/
Unload Event)
Select Execute Button
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the execute button
Enter LDC Details
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Weight Details, Analysis Details,
Transportation Information, Event
Information
Add Fee (optionally)
Operations &
Logistics
/ACCGO/LDC_WC
Add unplanned fees at LDC level
--- 第42页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 42 of 167 Fiori: Maintain Load Data Capture Select Release Icon to Release LDC Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture LDC is in released status
Auto-Release LDC Topic will be discussed further in the detailed design phase. Save Load Data Capture Data Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture LDC status becomes Orchestration Framework (OF) Execution Successful
--- 第43页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 43 of 167 3.2.2.2 Maintain Load Data Capture for Intercompany
Figure 3.8 – Maintain Load Data Capture for Intercompany Table 3.8 - Maintain Load Data Capture for Intercompany Process Step (Sales Side) Role T-Code / Fiori App Description Maintain Load Data Capture (LDC) Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture
or LDC Mass Upload Report There could be three ways of capturing LDC: 4. WB & QM Systems Integrated 5. Manual (Single) 6. Mass Uploads For WB & QM Systems Integrated LDC Generated Automatically
For Mass Upload Select LDC Mass Upload Report, complete details, upload, and validate.
For Manual (Single)
Select Maintain Load Data
Capture Fiori Tile and
subsequent process explained
below.
Select Create LDC Object
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the create button
Enter details LDC
Document Reference
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Enter Nomination Key to-be
linked with Load Data Capture
(Load/ Unload Event)
Select Execute Button
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the execute button
Enter LDC Details
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Weight Details, Analysis
Details, Transportation
Information, Event Information
--- 第44页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 44 of 167 Add Fee (optionally) Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture Add unplanned fees at LDC level Select Release Icon to Release LDC Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture LDC is in released status.
Auto-Release LDC Topic will be
discussed further in the detailed
design phase.
Save Load Data Capture
Data
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
LDC status becomes
Orchestration Framework (OF)
Execution Successful
Process Step
(Purchase Side)
Role
T-Code / Fiori App
Description
Maintain Load Data
Capture (LDC)
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
or LDC Mass Upload Report There could be three ways of capturing LDC: 7. WB & QM Systems Integrated 8. Manual (Single) 9. Mass Uploads For WB & QM Systems Integrated LDC Generated Automatically
For Mass Upload Select LDC Mass Upload Report, complete details, upload, and validate.
For Manual (Single)
Select Maintain Load Data
Capture Fiori Tile and
subsequent process explained
below.
Select Create LDC Object
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the create button
Enter details LDC
Document Reference
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Enter Nomination Key to-be
linked with Load Data Capture
(Load/ Unload Event)
Select Execute Button
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the execute button
Enter LDC Details
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Weight Details, Analysis
Details, Transportation
Information, Event Information
Add Fee (optionally)
Operations &
Logistics
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Add unplanned fees at LDC
level
--- 第45页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 45 of 167 Select Release Icon to Release LDC Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture LDC is in released status Save Load Data Capture Data Operations & Logistics /ACCGO/LDC_WC Fiori: Maintain Load Data Capture LDC status becomes Orchestration Framework (OF) Execution Successful
--- 第46页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 46 of 167 3.2.2.3 Review Application Document
Figure 3.9 – Review Application Document
Table 3.9 - Review Application Document
Activity
Role
Transaction
Code/Fiori App ID
Description
Open Manual Application
Work Center
Generic
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Open Maintain Application Work
Center
Select Contract
Application with certain
Selection Criteria
Generic
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Common Selection Criteria:
1. Application Document
2. Document Date
3. LDC ID
4. PO/ SO
5. Nomination Key
Display Application
Documents
Generic
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Select Display Application
Document
Select Application
Document Item
Generic
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Select Application Document Item
to be reviewed
Review Document Flow
Generic
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Review Document Item
--- 第47页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 47 of 167 3.2.2.4 Maintain Load of Storage Agreement
Figure 3.10 – Assign Load to Storage Agreement
Table 3.10 – Assign Load to Storage Agreement
Activity
Role
Transaction
Code/Fiori App ID
Description
Maintain Load of Storage
Agreement through
Maintain Load Data
Capture (LDC)
Logistic &
Operations
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select Maintain Load Data Capture
Fiori Tile
Select Create LDC Object
Logistic &
Operations
/ACCGO/LDC_WC
Fiori: Maintain Load
Data Capture
Select the create button and fill in
the Storage Agreement/ Item.
We have an option to add storage
agreement at LDC level, in case we
miss it, we can also assign it to the
application work center as below.
Open Maintain Application Logistic &
Operations
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Open Maintain Application Work
Center
Select Commingled with
certain Selection Criteria
Logistic &
Operations
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Common Selection Criteria:
1. Application Document
2. Document Date
3. LDC ID
4. PO/ SO
5. Nomination Key
Display Application
Documents
Logistic &
Operations
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Select Display Application
Document
Select Application
Document Line Item
Logistic &
Operations
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
If you wanted to add storage
agreement to it, select the icon
Storage and Select Assign Storage
Agreement to it
--- 第48页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 48 of 167 Activity Role Transaction Code/Fiori App ID Description Once completed application item will be changed to “Storage” Select “Move to Unassign” if we wanted to remove storage agreement Logistic & Operations /ACCGO/APP_WC Fiori: Maintain Application Work Center If you wanted to remove storage agreement to it, select the icon Storage and Select “Move to Unassign”
Optional step to remove application
documents from storage agreement
Save Application
Logistic &
Operations
/ACCGO/APP_WC
Fiori: Maintain
Application Work
Center
Select save to save application
document of storage agreement
--- 第49页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 49 of 167 3.2.2.5 Reverse Load Data Capture
Figure 3.11 - Reverse Load Data Capture Table 3.11 - Reverse Load Data Capture Activity Role Transaction Code/Fiori App ID Description Select Maintain Load Data Capture Logistic & Operations /ACCGO/LDC_WC Fiori: Maintain Load Data Capture From the Fiori Tile Menu Select Change LDC Object Logistic & Operations /ACCGO/LDC_WC Fiori: Maintain Load Data Capture From the side panel select Change LDC Object Enter Selection Criteria Logistic & Operations /ACCGO/LDC_WC Fiori: Maintain Load Data Capture Common Selection Criteria: 1. LDC Object Created 1. LDC General Information 2. LDC Event Information 3. LDC Reference Document Select LDC Line and Press Reversal Icon Logistic & Operations /ACCGO/LDC_WC Fiori: Maintain Load Data Capture Find and Select Reversal Icon
--- 第50页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 50 of 167 3.2.3 Solutioning 3.2.3.1 Load Data Capture Load Data Capture (LDC) is one of the key functional areas within SAP Agricultural Contract Management, serving as the central mechanism for capturing, processing, and managing load information for agricultural commodity transactions.
The load information includes details of what was loaded or unloaded, as well as the corresponding quality and measurement schema. The primary objective is to automate the processing of these loads as much as possible, minimizing manual intervention.
For GAR there are three different ways of capturing Load Data which are: 1. Weighbridge Generated 2. Manual Single Entry 3. Mass Load Data Capture Upload (Excel) as Custom Report To automate the creation of LDC documents, often integrate their weighbridge systems with ACM APIs. Multiple Interfaces we have captured as a WRICEF list for GAR are: 1. LDC Interface 1 (WBSMART-LDC) 2. LDC Interface 2 (ILOGS-LDC) 3. LDC Interface 3 (JIMS-LDC) 4. LDC Interface 4 (LIMS-LDC) 5. LDC Interface 5 (COPS-LDC) 6. LDC Interface 6 (LIS-LDC) China-Agri Weighbridge Integration, will be covered separately.
This integration allows for the automatic generation of LDC documents based on the information received from the Satellite systems. Documents generated are Order, Goods movement documents, delivery document and application document depending on the scenario.
In case of single entries, we have a separate Load Data Capture work center for creating LDC manually. This work center serves as the central hub for manual data entry requirements. When there is a need to enter information manually, this work center provides the necessary interface. It offers a user-friendly area where you can input the reference document. Once the reference document is entered, the system automatically populates a significant portion of the required information.
Figure 3.12 - Load Data Capture Screen
--- 第51页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 51 of 167
3.2.3.2 Load Data Capture Reference Document Load Data Capture Work Center itself supports various reference documents in which data need to be populated from the reference documents. The reference document for GAR mainly is the nomination key.
In the case using nomination as a reference, you would input the nomination key, and the associated contract and relevant information would be automatically populated. And if GAR decides to use Storage Agreement, there will be a choice to assignment storage agreement, or it can be determined automatically based on the system logic.
3.2.3.3 Transport Storage Location While the transport storage location will default if it is specified in the contract, it's common practice not to include the storage location in the contract since there may be multiple tanks involved. For nominations, the transport storage location will default if it is specified in the nomination.
3.2.3.4 Goods Weight & Governing Weight Governing weight refers to the agreed measurement basis used between buyer and seller when determining the final settlement quantity. This is aligned with contractual negotiations and can depend on your customer's commercial requirements.
Governing weight is defined at contract item level, where for example, we specify origin weight as the
governing weight for the contract. In this case, load event of LDC will be required to capture this weight.
Similarly, when we define the governing weight as destination, unload event of LDC will be required
to capture this weight. Please refer to section 3.2.3.7 and 3.2.3.8 for LDC Applicability matrix based
on Governing Weight + Governing Grades + Incoterm.
Load Data Capture is the generic process to capture actual weight detail (and also quality/ grades, see 3.2.3.5 below) at load or unload and be applicable for trucks, vessel, etc.
3.2.3.5 Goods Quality & Governing Grades Governing analysis defines which quality measurements or certification results should drive contractual quality-based adjustments. Similar to governing weight, this is agreed with the counterparty as part of commercial terms.
Governing analysis is defined at contract item level, where for example, we specify origin analysis as the governing analysis for the contract. In this case, load event of LDC will be required to capture this quality details. Similarly, when we define the governing analysis as destination, unload event of LDC will be required to capture this quality detail. Please refer to section 3.2.3.7 and 3.2.3.8 for LDC Applicability matrix based on Governing Weight + Governing Grades + Incoterm.
Figure 3.13 - Governing Weight & Analysis
--- 第52页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 52 of 167
3.2.3.6
Title Transfer
Title transfer defines clear understanding of when the transfer of ownership will occur. These decisions
will have implications for subsequent document generation and goods movements at Load Data
Capture.
Figure 3.14 - Title Transfer Title Transfer at Origin (TTO) This refers to the transfer of ownership at the point of origin. Stock ownership is transferred to Origin. As a result, the stock becomes responsibility of receiving party from origin itself. Title Transfer will occur at Load event.
Title Transfer at Destination (TTD) Ownership is transferred upon reaching the designated destination Stock ownership is transferred at its destination. So stock is in obligation of supplying party until it arrives at destination. Title Transfer will occur at Unload event.
3.2.3.7 LDC Applicability Matrix for Inbound Governing Weights and Grades: LDC Events Details - Inbound Scenario mapping as below table. ‘W’ means weight, ‘G’ means grade, ‘O’ means origin, ‘D’ means destination. Table 3.12 - LDC Applicability Matrix for Inbound
3.2.3.8
LDC Applicability Matrix for Outbound
Governing Weights and Grades: LDC Events Details - Outbound Scenario mapping as below table.
Table 3.13 - LDC Applicability Matrix for Outbound
Outbound
Load
Unload
TTD WOGO
X
X
TTD WDGD
X
X
TTD WDGO
X
X
TTD WOGD
X
X
TTO WOGO
X
TTO WDGD X X TTO WDGO X X TTO WOGD X X Inbound Load Unload TTD WOGO X X TTD WDGD
X
TTD WDGO
X
X
TTD WOGD
X
X
TTO WOGO
X
X
TTO WDGD
X
X
TTO WDGO
X
X
TTO WOGD
X
X
--- 第53页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 53 of 167 3.2.3.9 Incoterms ACM Load Data Capture determines the event type, whether it is a load or unload event, that we are expecting during Load Data Capture mostly based on the appropriate Incoterms and the contract lifecycle itself. Indicative List of Incoterms and details for GAR as below. Table 3.14 - Incoterm Matrix (Non-Exhaustive List) Aspect / Responsibility Franco Franco Hybrid Loco Loco Hybrid FOB FCA FOB Hybrid CIF CIF Hybrid DAP DAT Mode(s) of Transport Land Land Land Land Ocean / Multi- modal Land / Air / Sea (Multi- modal) Ocean / Multi- modal Ocean / Multi- modal Ocean / Multi- modal Ocean / Multi- modal Ocean / Multi- modal Transport Arrangement Seller Seller Buyer Buyer Buyer Buyer Buyer Seller Seller Seller Seller Who Books Freight Seller Seller Buyer Buyer Buyer Buyer Buyer Seller Seller Seller Seller Export Customs Clearance Seller Seller Buyer Buyer Seller Seller Seller Seller Seller Seller Seller Main Carriage Risk Buyer (after dispatch) Buyer (after dispatch) Buyer Buyer Buyer (once onboard vessel) Buyer (after handover to carrier at named place) Buyer (on delivery at dest. port) Seller (until destination port) Seller (until destination port) Seller (until goods delivered at named destination) Seller (until goods delivered at terminal) Insurance Responsibility Buyer Buyer Buyer Buyer Buyer Buyer Buyer Seller (mandatory) Seller (mandatory) Buyer Buyer Weighbridge Governing Billing Qty Buyer’s Seller’s Seller’s Buyer’s BL @ Port Origin Seller’s weighbridge (before handover) Port Destination (Sounding/Wei ghbridge) Port Destination (Sounding/Wei ghbridge) BL @ Port Origin Destination (Sounding/Wei ghbridge) Terminal (Sounding/Wei ghbridge) Title / Risk Transfer Point On departure from seller’s site On departure from seller’s site On pickup at seller’s site On pickup at seller’s site Once goods loaded onboard vessel Once goods handed to carrier at named place (origin or terminal) Once goods received at destination port On arrival port destination On BL at origin port Once goods delivered to named place of destination Once goods delivered at named terminal at destination Unloading Responsibility Buyer Buyer Buyer Buyer Buyer Buyer (at carrier handover) Buyer Buyer Buyer Buyer Seller Import Customs & Duties Buyer Buyer Buyer Buyer Buyer Buyer Buyer Buyer Buyer Buyer Buyer Billing Base Buyer’s weighbridge Seller’s weighbridge Seller’s weighbridge Buyer’s weighbridge BL quantity (origin) Seller’s dispatch quantity Port destination sounding Port destination sounding BL quantity (origin) Destination weighbridge Destination terminal weighbridge Relevant Transport Document Truck Waybill Truck Waybill Truck Waybill Truck Waybill Bill of Lading (Origin) Forwarder Receipt / Proof of Handover Bill of Lading (Destination Sounding) Bill of Lading + Insurance Certificate Bill of Lading + Insurance Certificate Bill of Lading + Proof of Delivery Bill of Lading + Proof of Delivery
Please note that this list is non-exhaustive and may not reflect the latest incoterm.
--- 第54页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 54 of 167 3.2.3.10 Load Data Capture Processing The process can be summarized as a two-step communication flow. After entering the required data, the first step is to release and save the information. Subsequently, the system initiates a series of actions.
This step helps identify the specific configuration table required for further processing. Once the appropriate configuration table is determined, the system proceeds to execute a set of function modules in the background. This orchestration framework is responsible for coordinating and calling the necessary modules to generate the required documents and perform additional automated tasks. After release and saving the LDC the LDC status changes to Orchestration Framework (OF) Execution Successful.
Load Data Capture would be created with nomination as reference. Based on the scenarios Title transfer Origin or Title Transfer Destination the events of LDC are decided.
For sales side Load event is always there and for destination side Unload event is always there.
Once the LDC status is Orchestration Framework (OF) Execution Successful documents are automatically generated in the background.
Documents generated are: 1. Order 2. Delivery 3. Goods movement 4. Application Document
3.2.3.11 Application Document An application document is an intermediate SAP document that is delivered with Agricultural Contract Management and used to facilitate contract application and settlement. The application document has a one-to-one relationship with a goods receipt (GR) document or goods issue (GI) document and is created at the time of posting.
The primary use of the application document is to enable processes such as the application of discount premium quality schedules, evaluation of tolerances, evaluation of optionalities, and so on.
The application document displays the vendor or customer, the material, in addition to the quantity and quality details. Other application details (such as quantity adjustments) are also displayed.
The system creates an application document when you release a Load Data Capture (LDC) event. The creation of the goods movement document is automated through the Orchestration Framework (OF), but it can also be performed manually for exceptional cases if required.
--- 第55页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 55 of 167 3.2.3.12 Delivery to Fulfill Multiple Contracts In Agricultural Contract Management (ACM), one truck can be utilized to deliver multiple deliveries for the stakeholders in vicinity. In such cases, there would be individual Load Data Captures (LDCs) created for each contract with the correct quantity having same vehicle details.
3.2.3.13 Document Flow Workcenter The Document Flow Workcenter acts as a central cockpit to track the lifecycle of ACM documents. Users can select document criteria (such as Trading Contract, Nomination, LDC, Application, or Settlement) using a single unified selection screen. Based on the input, the system displays all relevant documents and their follow-on records in a hierarchical structure, allowing users to trace progress from contract creation to final settlement.
Additional filtering options are available for transportation details and partner roles. Users may view multiple document flows at once, navigate to original documents, or switch the display focus to a specific branch when multiple flow legs exist. The tool provides quick visibility into processing status and system-generated artifacts throughout the execution chain.
In summary, Document Workcenter can be useful for these activities: 1. Track End-to-End Document Lifecycle 2. Search and Filter Documents 3. Display and Navigate to Original Documents 4. Display and Focus Specific Document Flow 5. Reverse Documents 6. Simulate Reversal 7. Cancel Invoices 8. View Reversal Log and Reason Codes
Figure 3.15 - Track End-to-End Document Lifecycle
--- 第56页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 56 of 167
Figure 3.16 - Search and Filter Documents
Figure 3.17 - Additional Features from DocFlow Workcenter
--- 第57页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 57 of 167 3.2.3.14 Batch Management ACM is designed to work with Bulk/Semi-bulk materials where the Quality and grades are captured at the delivery. ACM offers basic functionality of capturing the Batch details such as: 1. Batch input / determination for Goods Issue 2. Generate the Batches at Goods receipt (standard MM setup)
Enhancements will be required to provide comprehensive solution for the Batch requirements.
Batch management is supported in SAP Agricultural Contract Management but may not be necessary for all soft commodities. For instance, wheat seed multipliers necessitate batch management to track the origin and quality of seeds. However, commodities may not require batch management unless specifically required by the customer. The decision regarding batch management implementation depends on the commodity type and customer's specific needs. Expectation is to ensure Batch managed materials can be handled in ACM. The requirement is therefore classified into following 3 areas: 1. Purchase or Goods Receipt - Generate batch according to the policy ruling at GR. This is a standard MM setup. 2. Sales or Goods Issue - need to be able to automatically select batches based on certain rules (e.g. FIFO or FEFO), select multiple batches manually (e.g. for packed products), or select batches based on inputs from EWM system/ integration. 3. Intercompany Scenarios - system should be able to handle the following scenarios: a. GI one batch, GR one batch (one to one) [SOCI to GAI] b. GI one batch, GR one batch with different naming (one to one) [others] c. GI multiple batches, GR one batch (many to one) d. GI one batch, GR no batch (one to none) System should also be able to manage Batch split scenarios. 3.2.3.15 EWM-Batch Integration with ACM Batch details are captured from EWM and processed during LDC. Batch details need to be provided/ determined at the time of LDC creation if LDC is created manually, subsequent documents will have the batch attribute details inherited
Figure 3.18 - Sales Batch Traceability
--- 第58页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 58 of 167 3.2.3.16 Sales Goods Movement Type Table 3.15 - Outbound Goods Movement Type Sales (Outbound)
Incoterm Governing Weight Goods Movement Type Load Event Unload Event No Gain/Loss Origin Origin 601 x Gain x x Loss x x No Gain/Loss Origin Destination 601 601 Gain 601 601 No GM for gain after Rev Rec Loss 601 601 No GM for loss after Rev Rec No Gain/Loss Destination Destination 687 601 Gain 687 687 After rev rec 601 is posted Loss 687 687 After rev rec 601 is posted No Gain/Loss Destination Origin 687 687 After rev rec 601 is posted Gain 687 687 After rev rec 601 is posted Loss 687 687 After rev rec 601 is posted
Note 601 – Goods Issue for Delivery 687 – Goods Delivery to Issuing Valuated Stock-in-Transit
Goods Movement Types are given in standard SAP. Any changes specific to SG business scenarios will be detailed in SG BSDD.
--- 第59页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 59 of 167 3.2.3.17 Purchase Goods Movement Type Table 3.16 - Purchase Goods Movement Type Purchase (Inbound) Incoterm Governing Weight Goods Movement Type Load Event Unload Event No Gain/Loss Origin Origin 107 109 Gain 107 107 107 for gain 109 for total qty Loss 107 107 108 for loss 109 for total qty No Gain/Loss Origin Destination 107 109 Gain 107 107 107 for gain 109 for total qty Loss 107 107 108 for loss 109 for total qty No Gain/Loss Destination Destination x 101 Gain x x Loss x x No Gain/Loss Destination Origin x 101 Gain x 101 Loss x 101
Note 101 — Goods Receipt 107 — Goods Receipt to Valuated Goods Receipt Blocked Stock 108 — Goods receipt to Valuated Blocked Stock - Reversal 109 — Goods Receipt from Valuated Goods Receipt Blocked Stock
Goods Movement Types are given in standard SAP. Any changes specific to SG business scenarios will be detailed in SG BSDD.
--- 第60页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 60 of 167 3.2.3.18 Intercompany Goods Movement Type Table 3.17 - Intercompany Goods Movement Type Intercompany Goods Movement
Incoterm Goods Movement Type Load Event Unload Event No Gain/Loss Origin 683 107 109 Gain 683 107 560 for gain 109 for total qty Loss 683 107 559 for loss 109 for load qty No Gain/Loss Destination 681 685 107 109 Gain 681 685 107 560 for gain 109 for total qty Loss 681 685 107 559 for loss 109 for unload qty
Note 107 — Goods Receipt to Valuated Goods Receipt Blocked Stock 109 — Goods Receipt from Valuated Goods Receipt Blocked Stock 559 — Scrapping (or Goods Issue) from Valuated Goods Receipt Blocked Stock (Adjustment Posting 560 — Return Scrapping (or Reversal to Goods Issue) from Valuated Goods Receipt Blocked Stock (Adjustment Posting) 681 — Stock Transfer to Issuing Valuated Cross-Company-Code Stock in Transit (CST) 683 — Stock Transfer to Receiving Valuated CST 685 — Stock Transfer from Issuing Valuated CST
Goods Movement Types are given in standard SAP. Any changes specific to SG business scenarios will be detailed in SG BSDD.
--- 第61页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 61 of 167 3.2.3.19 Non-CAS STO Goods Movement Type Table 3.18 - Non-CAS STO Goods Movement Type Non-CAS STO Goods Movement
Incoterm Goods Movement Type Load Event Unload Event No Gain/Loss Destination 68A 68E Gain 68A 68E 560 for gain qty 109 for total qty Loss 68A 68E 559 for loss qty 109 for unload qty
Note 109 — Goods Receipt from Valuated Goods Receipt Blocked Stock 559 — Scrapping (or Goods Issue) from Valuated Goods Receipt Blocked Stock (Adjustment Posting) 560 — Return Scrapping (or Reversal to Goods Issue) from Valuated Goods Receipt Blocked Stock (Adjustment Posting) 68A — Stock Transfer to Issuing Valuated Intra-Company-Code Stock in Transit (IST) 68E — Stock Transfer from Issuing Valuated IST to Receiving Valuated Stock in Transit
Goods Movement Types are given in standard SAP. Any changes specific to SG business scenarios will be detailed in SG BSDD.
--- 第62页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 62 of 167 3.2.3.20 LDC Reversal You can perform an LDC reversal to restore quantities back on their original batches, from where the stock was retrieved during the load event. An LDC reversal results in the generation of a reverse goods movement, which results in an increase in the stock quantity on the original batch at the storage location.
To perform an LDC reversal from the LDC Workcenter, please refer to Business Process Flow on the Section 3.2.2.5 Reverse Load Data Capture.
You can also perform an LDC reversal in the Document Flow Workcenter, enter the trading contract or application document, and select the LDC. Click on the Reverse button in the toolbar. A confirmation prompt will be displayed for approval.
Once the reversal has been successfully performed, you can check the increased stock quantity by navigating to the Stock Overview screen (using the transaction MMBE in SAP).
All Reversal Scenarios (Prepayment, settlement, etc), will be covered in Detailed Design phase.
3.2.3.21 Commodity Sales Return There are two parts for executing Commodity Sales Return which are the regular Forward transaction and the Return Transaction itself explained in below figure.
Figure 3.19 - High-Level Commodity Sales Return Flow Commodity Sales Return process is not relevant Singapore. Please also note that for Sales Return process, will be further refined on detail design discussion including segregation of duties as well.
3.2.3.22 KG to L Conversion This requirement is captured on RTM ACM-1172 and ACM-1213 to accommodate conversion of unit of measurement (eg. L to kg, kg to L) eg. for Biodiesel FAME, contract, billing and physical goods loaded are recorded in Liters, but goods movement in SAP need to be recorded in Kg.
This conversion is to be done by system; users will input the necessary parameters (eg. temperatures, density) and system will automatically do the conversion based on the ASTM tables (ASTM 54/54B 53, 56).
--- 第63页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 63 of 167
KG to L conversion is not relevant for Singapore.
3.2.3.23 LDC Integration with TM Load Data Capture records actual ACM loading and unloading data like weights, resources, seals and so on. By integrating LDCs with freight units, actual data is sent to TM. This is important for follow-up processes like execution and freight costing based on actual data.
Figure 3.20 - ACM-TM Integration through BTE Cost distribution is a process in TM, involving allocation of freight costs across a number of charge sources to manage various business processes. As a part of this solution, the standard functionality in TM has been enhanced to include fields relevant to nominations and allocating costs to trading contracts. This information is, in turn, reflected in the freight settlement documents created.
ACM-TM Integration is not relevant for Non-TMS Country like Singapore.
--- 第64页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 64 of 167 3.2.3.24 Final Delivery Indicator Final Delivery Indicator to signify that no more new application documents can be applied against that particular trading contract commodity item. This is important for the Underfill scenarios. Users can set the final delivery indicator during the creation of application document; however, User can only trigger an underfill by setting the final delivery indicator for the item in the manual application workcenter.
Process Steps: 1. Launch Fiori app Manual Application Workcenter. 2. Enter the filter criteria such as contract to search the application document items and then choose Go. 3. Navigate to the object details of the specific application document item. 4. In the Contract section, choose Final Delivery Set or Final Delivery Unset.
Figure 3.21 - Maintain Final Delivery Flag on Manual Application Workcenter (Step 1)
Figure 3.22 - Maintain Final Delivery Flag on Manual Application Workcenter (Step 2)
--- 第65页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 65 of 167
Figure 3.23 - Maintain Final Delivery Flag on Manual Application Workcenter (Step 3) The Truck Icon at item level is to set the FDI:
While the icon at the contract (Header) level is used to Unset the FDI:
Figure 3.24 - Maintain Final Delivery Flag on Manual Application Workcenter (Step 4)
--- 第66页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 66 of 167 3.2.3.25 Order Statuses To standardize Order Statuses, similar S/4 statuses will be used for ACM Generated SO/PO. Based on the workshops and requirement gathering, critical order statuses are Technically Completed (TeCo) and Completed (marking delivery is fully delivered). These order statuses are to be configured during Build phase with few iterations to match the business requirements.
Figure 3.25 - Statuses at Order
--- 第67页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 67 of 167 3.2.3.26 Load Data Capture Journal Postings Note The accounting postings illustrated in this blueprint reflect the Indonesia scenario as the primary reference. Accounting postings for Singapore and Destination Offices (DO) will be finalized during the Detailed Design phase and may differ based on country-specific business and statutory requirements.
3.2.3.27 Load Data Capture Journal Postings for Indonesia 3.2.3.27.1 Sales Destination Scenario
Table 3.19 - LDC Sales Destination Journal Postings for Indonesia
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
Goods loaded
Dr
GI NYB (Goods Issue Not-yet-Billed)
1.900.000
Standard (For Destination Scenario with
Governing Weight Destination), Movement
Type: 687 - Inventory In Transit to be
renamed by Goods Issue Not yet Billed
Cr Inventory - 1.900.000
Goods Unloaded Standard: No good movement generated- N/A
3.2.3.27.2 Sales Origin Scenario
Table 3.20 - LDC Sales Origin Journal Postings for Indonesia
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
Goods loaded
Dr
GI NYB (Goods Issue Not-yet-Billed)
2.000.000
Custom
In Standard Movement Type: 601 -
COGS Dr
Inventory Cr
The COGS account to be replaced by GI-
NYB
Cr Inventory - 2.000.000
--- 第68页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 68 of 167 Goods Unloaded
Standard: No good movement generated- N/A
3.2.3.27.3 Purchase Destination Scenario
Table 3.21 - LDC Purchase Destination Journal Postings for Indonesia
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
Create LDC
Event
(Load)
N/A Not Applicable
Create LDC
Event
(Unload)
OTP / NOTP
Standard Movement Type:101 Gain/Loss not applicable for Purchase Destination scenario
Dr TBD Inventory 5.000.000
Cr TBD GR/IR (5.000.000)
Dr TBD PurchAcct 3Pty 5.000.000
Cr TBD PurchOffset 3Pty (5.000.000)
--- 第69页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 69 of 167
3.2.3.27.4 Purchase Origin Scenario
Table 3.22 - LDC Purchase Origin Journal Postings for Indonesia
Transaction
Dr/Cr GL Account GL Description
Amount
Notes
OTP & NOTP
Standard
Contract/PO Quantity Recorded
Create LDC Event
(Load)
Dr
TBD
Inventory
5.000.000
Cr
TBD
GR/IR
(5.000.000)
Dr TBD Purchase Acct 5.000.000
Cr TBD Purchase Offset (5.000.000)
Custom:
1) Standard GM 109 is triggered with no
accounting document
2) For Gain/Loss (movement type-107 for
Gain;108 for loss) the standard posting is
to Inventory to GR/IR account Credit, the
requirement is to hit the LOSS Account
(COGS)
Create LDC Event
(Unload)
Sample Gain (OTP / NOTP)
Dr TBD Inventory 250.000 Cr TBD Gain Account (COGS Item) (250.000)
Sample Loss (OTP/NOTP)
Dr TBD Loss Account (COGS Item) 250.000
Cr TBD Inventory (250.000)
--- 第70页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 70 of 167
3.2.3.27.5 Intercompany Destination Scenario
Table 3.23 - Intercompany Destination LDC Load Event Journal Postings
Transaction (Seller Side) Goods Movement Dr/Cr GL Account GL Description Amount Seller’s Book Notes
Standard- Movement Type 681 for Seller's books Goods Loaded 681 Dr TBD GI NYB (Goods Issue Not-yet- Billed) 2.000.000 Cr TBD Inventory (2.000.000)
Transaction (Buyer Side) Goods Movement Dr/Cr GL Account GL Description Amount Buyer’s Book Notes
Goods Loaded¶
-¶
-¶
Standard-
--- 第71页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 71 of 167
Table 3.24 - Intercompany Destination LDC Unload Event Journal Postings
Transaction (Seller Side) Goods Movement Dr/Cr GL Account GL Description Amount Seller’s Book Notes
Custom 1) In Standard for Seller's books Movement type 685 is triggered with accounting as below for full qty/value: COGS Dr Inventory in Transit Cr Requirement is not to have any accounting entry posted for Seller books during Unload
Goods Unloaded¶
-¶
-¶
Transaction (Buyer Side) Goods Movement Dr/Cr GL Account GL Description Amount Buyer’s Book Notes
1)For buyer movement type is 107, and it posts to inventory with full qty Inventory To GR/IR The requirement is to post in buyers books with actual qty and value received (Custom) 2) In Standard, For buyer movement type 559 is triggered, to capture loss qty COGS Account Dr to Inventory Ac Cr The requirement is to not capture any loss posting during unload for Buyer. Goods Unloaded 107 Dr TBD Inventory 4.750.000 Cr TBD GR/IR (4.750.000)
Dr TBD Purchase acct 4.750.000 Cr TBD Purchase Offset Acct (4.750.000)
--- 第72页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 72 of 167
3.2.3.27.6 Intercompany Origin Scenario
Table 3.25 - Intercompany Origin LDC Load Event Journal Postings
Transaction (Seller Side) Goods Movement Dr/Cr GL Account GL Description Amount Seller’s Book Notes
Custom In Standard for Seller's book Movement Type 683 posts below: COGS Dr Inventory Act The requirement is to debit the Inventory-NYB account instead of COGS (custom)
Goods Loaded 683 Dr TBD GI NYB (Goods Issue Not-yet- Billed)- Posting Date use BL Date 2.000.000 Cr TBD Inventory (2.000.000)
Transaction (Buyer Side) Goods Movement Dr/Cr GL Account GL Description Amount Buyer’s Book Notes
Goods Loaded 107 Dr TBD Inventory - Posting Date use BL Date 5.000.000 Standard For buyers books, the movement type 107 is triggered with below: Inventory Dr GR/IR Cr (Standard meets the requirements) Cr TBD GR/IR (5.000.000) Dr TBD Purchase 5.000.000 Cr TBD Purchase Offset Acct (5.000.000)
--- 第73页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 73 of 167 Table 3.26 - Intercompany Origin LDC Unload Event Journal Postings
Transaction (Seller Side) Goods Movement Dr/Cr GL Account GL Description Amount Seller’s Book Notes
1) In Standard for Seller's books no accounting entry is generated during unload event (meets GAR's requirements)
Goods Unloaded -¶
-¶
Transaction (Buyer Side) Goods Movement Dr/Cr GL Account GL Description Amount Buyer’s Book Notes
For buyer books movement type 559 is triggered for loss/560 for gain , and it posts to inventory and COGS account for loss/gain qty: Inventory To COGS The requirement is to post to Gain/Loss Account instead of COGS account (Custom) Goods Unloaded 560 Gain
Sample Gain Posting
Dr TBD Inventory (Sloc GIT) 500.000 Cr TBD Gain Account (COGS) (500.000)
559 (Loss Qty)
Sample Loss Posting
Dr TBD Loss Account (COGS) 250.000 Cr TBD Inventory (Sloc GIT) (250.000)
--- 第74页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 74 of 167
3.2.3.27.7 Non-CAS Scenario
Table 3.27 - Non-CAS Scenario LDC Journal Postings
Transaction
Dr/Cr GL Account GL Description
Amount
Notes
Standard
Create LDC Event
(Load)
No Account Postings happen; only Material ledger postings applicable for this scenario.
Custom:
1) Standard GM 109 is triggered with no
accounting document
2) For Gain/Loss (movement type-560 for
Gain;559 for loss) the standard posting is
to Inventory to GR/IR account Credit, the
requirement is to hit the LOSS Account
(COGS)
Create LDC Event
(Unload)
Sample Gain
Dr TBD Inventory 250.000 Cr TBD Gain Account (COGS Item) (250.000)
Sample Loss
Dr TBD Loss Account (COGS Item) 250.000
Cr TBD Inventory (250.000)
3.2.3.27.8 Hybrid-Incoterm Hybrid-Incoterm like Franco or Loco LDC Journal Postings will be further explained during Detail Design.
--- 第75页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 75 of 167
3.2.3.28 Load Data Capture Journal Postings for Singapore
3.2.3.28.1 Sales Scenario
Table 3.28 - Sales LDC Journal Postings
Transaction
Dr/Cr
GL Account
GL Description
MT
Amount
Notes
Goods loaded (LDC
event)
Dr
GI NYB (Goods Issue Not-yet-Billed)
1.000,00 2.000.000
Custom
In Standard Movement Type: 601 -
COGS Dr; Inventory Cr
The COGS account to be replaced by
GI-NYB
Cr Inventory - 2.000.000
*Based on moving average inventory cost
Goods Unloaded Standard: No good movement generated- N/A
3.2.3.28.2 Purchase Scenario Table 3.29 - Purchase LDC Journal Postings Transaction Dr/Cr GL Account GL Description
Amount Notes
Create LDC Event
(Load)
Dr
Cr
TBD
Inventory
5.000.000 Standard
Contract/PO Quantity/Price Recorded
TBD GR/IR
(5.000.000)
Dr TBD Purchase Acct
5.000.000
Cr TBD Purchase Offset
(5.000.000)
--- 第76页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 76 of 167 3.2.3.28.3 Intercompany Scenario Table 3.30 - Intercompany LDC Journal Postings Transaction Goods Movement Dr/Cr GL Account GL Description Amount Transaction Goods Movement Dr/Cr GL Account GL Description Amount
Transaction
Goods
Movement
Dr/Cr
GL
Account
GL Description
Amount
Goods
Loaded
683
Dr
TBD
GI NYB (Goods
Issue Not-yet-Billed)
2.000.000 Goods
Unloaded
107
Dr
TBD
Inventory - Posting
Date use BL Date
5.000.000
Cr
TBD
Inventory
(2.000.000)
Cr
TBD
GR/IR
(5.000.000)
Dr TBD Purchase 5.000.000
Cr TBD Purchase Offset Acct (5.000.000)
--- 第77页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 77 of 167
4
Country Specific Scenario
4.1
Process Design Variants - With TMS and Without TMS
Solution is expected for BU with no TMS interface as explained on Section 3.1.3.6. It is common practice for businesses and required (China) to send
the confirmed schedules/nominations to the weighbridge for easier linking of deliveries with the ticketing information. In such cases an interface is required
between ACM and Weighbridge at Nominations and subsequently at LDC.
4.2
Singapore, Malaysia, & China Deliveries from Futures
Once generated with reference to futures, the physical contract can be executed as regular contract. Physical execution is necessary to update the
inventory while to accommodate the Accounting. ACM handles this scenario as follows:
- For Purchase Scenario a. Post settlement approval, the Back-office if required can adjust the physical delivery’s amount against the Futures margin posting via FI Clearing posting (recommended). b. Payment Block at Settlement Approval should be set-up to ensure that no payments happen to Supplier for this delivery.
- For Sales Scenario a. Another storage location type for reserved quantities would be created and the commodities corresponding to a futures contract quantity would be moved from ‘unrestricted’ to this ‘reserved’ stock. This Scenario in ACM is called as “Instore Sales” where the Nomination is created with reference to contract and LDC (App Inst 30) transfers the commodity to obligatory stock with Title transfer to customer. b. A commingled application document is generated in the above step which can be linked to a Storage Agreement for any storage related charges (to be confirmed / might be relevant later). c. Post this LDC, settlement & Invoicing will be performed. Post Invoicing, the Back-office if required can adjust the physical delivery’s amount against the Futures margin posting via FI Clearing posting (recommended). d. Enhancements can be done to ensure the Invoice amount can be suppressed (showing 0 amount) or Invoice not triggered to the Customer. e. For actual deliveries i.e. physical delivery(s) to customer after some time. Load Outs can happen from the obligatory stock by setting the load out flag at nomination and doing LDC (App Instr. 35) with the option of Sell outs (App Inst 31) available to customers.
--- 第78页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 78 of 167
Figure 4.1 - Physical Trade Cycle for Realized Long Futures
--- 第79页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 79 of 167
Figure 4.2 - Physical Trade Cycle for Realized Short Futures
--- 第80页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 80 of 167
Figure 4.3 - Physical Trade Cycle for Realized Long Futures with Back-to-Back Sales
--- 第81页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 81 of 167
Figure 4.4 - Physical Trade Cycle for Realized Short Futures with Back-to-Back Purchase for Order Fulfillment (TBC)
--- 第82页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 82 of 167 4.3 Indonesia Goods Movement Scenarios In this section, it will cover Goods Movement Scenarios for Indonesia that we have captured so far. This is an indicative list which includes Plant-to-Plant or Sloc-to-Sloc Transfers, Intercompany, 3rd Party Purchase, and 3rd Party Sales Scenarios. The following are the steps for each scenario and its examples.
For further details, please find the excel documents link S4_P2_ACM_ID Goods Movement Variations_V1.00.xlsx. Process visualization provided on Appendix Section 5.1 ACM ID Goods Movement Variations and solution details in tabular format below.
--- 第83页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 83 of 167
4.3.1 Plant-to-plant / Sloc-to-Sloc Transfers (within the same company code) Table 4.1 - Plant-to-Plant/ Sloc-to-Sloc Transfers Transaction Scenario Document Solution Details US Mill to US Bulking
Intracompany Commingled
Stock (Titip Timbun)
Land
Nomination
ACM Non-CAS Nomination – TM Relevant
LDC
US Mill Plant (Valuated)
1. Load Event: WB Out Mill (68A)
3. Unload Event: GR to Sloc BULK (68E) – auto triggered by 2
US Bulking Plant (Non-valuated)
2. WB in Bulking: GR to Sloc Tank (921)
Gain/Loss
Multi-modal (Land
→ Ocean)
Nomination
ACM Non-CAS Nomination – TM Relevant
LDC
US Mill Plant (Valuated)
4. Load Event: total cumulative WB Out Mill (68A). Need a final truck
indicator in WB to trigger total truck qty as Load Event
3. Unload Event: GR to Sloc BULK (68E) – auto triggered by 2
US Bulking Plant (Non-valuated)
2. Sounding in Bulking: GR to Sloc Tank (921)
Gain/Loss
DSI Bulking/Warehouse to
DSI Refinery
Refinery A to Refinery B
DSI Refinery to DSI Bulking *Olein, FAME
Intracompany Ocean Nomination ACM Non-CAS Nomination #1 – Not TM Relevant ACM Non-CAS Nomination #2 (Ocean) – TM Relevant ACM Non-CAS Nomination #3 – Not TM Relevant LDC ACM Non-CAS Nomination #1 (Origin Tank to Port) 1. Load Event based on each origin tank 2. Unload Event: Load Event ACM Non-CAS Nomination #2 (Ocean)
--- 第84页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 84 of 167 Transaction Scenario Document Solution Details
- Load Event: cumulative Origin Tanks qty / BL qty
- Unload Event: cumulative Receiving Tanks qty
ACM Non-CAS Nomination #3 (Port to Receiving Tank) - Load Event: Unload Event
- Unload Event based on each receiving tank In real life, finish discharging first, and then update ACM Non-CAS Nomination
2 Unload and then ACM Non-CAS Nomination #3 Load and Unload Event.¶
Gain/Loss captured in ACM Non-CAS Nomination #2
Multi-Modal (Ocean → Land)
Nomination
ACM Non-CAS Nomination #1 – Not TM Relevant
ACM Non-CAS Nomination #2 (Ocean) – TM Relevant
ACM Non-CAS Nomination #3 (Land) – TM Relevant
LDC
ACM Non-CAS Nomination #1 (Origin Tank to Port)
1. Load Event based on each origin tank
2. Unload Event: Load Event
ACM Non-CAS Nomination #2 (Ocean)
1. Load Event: cumulative Origin Tanks qty / BL qty
2. Unload Event: cumulative trucks qty of Non-CAS Nomination #2
ACM Non-CAS Nomination #3 (Land)
3. Load Event: Unload Event
4. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM Non-CAS Nomination
2 Unload and then ACM Non-CAS Nomination 3 Load and Unload Event.¶
Gain/Loss captured in ACM Non-CAS Nomination #2
Multi-Modal (Land
→ Ocean → Land)
*PK
Nomination
ACM Non-CAS Nomination #1 (Land) – TM Relevant
ACM Non-CAS Nomination #2 (Ocean) – TM Relevant
ACM Non-CAS Nomination #3 (Land) – TM Relevant
--- 第85页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 85 of 167 Transaction Scenario Document Solution Details
LDC
ACM Non-CAS Nomination #1 (Land):
1. Load Event based on each truck: WB qty
2. Unload Event: Load Event
ACM Non-CAS Nomination #2 (Ocean):
3. Load Event: BL qty
4. Unload Event: cumulative trucks qty of Non-CAS Nomination #2
ACM Non-CAS Nomination #3 (Land)
5. Load Event based on each truck: WB qty
6. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM Non-CAS Nomination
2 Unload and then ACM Non-CAS Nomination #3 Load and Unload Event.¶
Gain/Loss captured in ACM Non-CAS Nomination #2 *Sample Case/Cargo
Note: Purple – S/4 Gain/Loss Postings will happen automatically for Non-CAS STO upon unload for all entities except for Upstream. Currently, we are still discussing this automatic gain/loss posting for Upstream which will be covered in the detailed design discussion. 4.3.2 Intercompany (different company code) Table 4.2 - Intercompany Transaction Scenario Govt. Weight Document Solution Details Estate to Mill
Mill A to Mill B/ GBE
LCO 1. Origin 2. Destination Contract ACM Intercompany Contract (US – US/GBE) Nomination ACM Nomination – TM relevant
--- 第86页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 86 of 167 Transaction Scenario Govt. Weight Document Solution Details
LDC 1. Load Event: Seller WB qty 2. Unload Event: Buyer WB qty Gain/Loss captured in LDC Settlement 1. Origin: Settlement based on Load Event Details 2. Destination: Settlement based on Unload Event Details FCO 1. Destination 2. Origin Contract ACM Intercompany Contract (US – US/GBE) Nomination ACM Nomination – TM relevant LDC 1. Load Event: Seller WB qty 2. Unload Event: Buyer WB qty Gain/Loss captured in LDC Settlement 1. Destination: Settlement based on Unload Event Details 2. Origin: Settlement based on Load Event Details Buy sell in 1 tank (no physical movement)
Contract ACM Intercompany Contract (US – US/GBE) Nomination - LDC 1. Load Event: by Seller 2. Unload Event: by Buyer No Gain/Loss Settlement Settlement based on Load/Unload Event Details US Estate/Mill to DSI Refinery/ Bulking /Warehouse LCO 1. Origin 2. Destination Contract ACM Intercompany Contract (US – DSI) Nomination ACM Nomination – TM relevant LDC 1. Load Event: Seller WB qty 2. Unload Event: Buyer WB qty
--- 第87页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 87 of 167 Transaction Scenario Govt. Weight Document Solution Details Gain/Loss captured in LDC Settlement 1. Origin: Settlement based on Load Event Details 2. Destination: Settlement based on Unload Event Details FCO 1. Destination 2. Origin Contract ACM Intercompany Contract (US – DSI) Nomination ACM Nomination – TM relevant LDC 1. Load Event: Seller WB qty 2. Unload Event: Buyer WB qty Gain/Loss captured in LDC Settlement 1. Destination: Settlement based on Unload Event Details 2. Origin: Settlement based on Load Event Details US Mill (US Bulking) to DSI Refinery/ Bulking/ Warehouse
Buy sell in 1 tank (no physical movement)
Contract ACM Intercompany Contract (US – DSI) Nomination - LDC US Mill Plant (Valuated) 1. Manual Load Event from Sloc BULK according to each Tank qty Refinery Plant (Valuated) 2. a) Unload Event to Sloc Tank – auto triggered by 1 US Bulking Plant (Non-valuated) 2. b) MM TP Batch Mill to Batch Refinery – auto triggered by 1 (outside ACM) No Gain/Loss Settlement Settlement based on Load/Unload Event FOB 1. Origin 2. Destination Contract ACM Intercompany Contract (US – DSI) Nomination ACM Nomination – TM relevant ACM Non-CAS Nomination – Not TM Relevant
--- 第88页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 88 of 167 Transaction Scenario Govt. Weight Document Solution Details LDC ACM Nomination: ➔ US Bulking Plant (Non-valuated) Manual GI from each Sloc Tank with corresponding qty and qlty details ➔ US Mill Plant (Valuated) 1. Load Event from Sloc BULK*, per line item of Manual GI per tank (using partial weight functionality) ➔ DSI Refinery/Bulking/Warehouse 2. Unload Event: cumulative Receiving Tanks qty ACM Non-CAS Nomination (Port to Receiving Tank) 3. Load Event: Unload Event 4. Unload Event based on each receiving tank In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination Load and Unload Event.
Gain/Loss captured in LDC of ACM Nomination
Settlement
1. Origin Settlement based on ACM Nomination Load Event
2. Destination: Settlement based on ACM Nomination Unload
Event
CIF
1. Destination
2. Origin
Contract
ACM Intercompany Contract (US – DSI)
Nomination
ACM Nomination – TM relevant
ACM Non-CAS Nomination – Not TM Relevant
LDC
ACM Nomination:
➔ US Bulking Plant (Non-valuated)
Manual GI from each Sloc Tank with corresponding qty and
qlty details
➔ US Mill Plant (Valuated)
1. Load Event from Sloc BULK*, per line item of Manual GI
per tank (using partial weight functionality)
--- 第89页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 89 of 167 Transaction Scenario Govt. Weight Document Solution Details ➔ DSI Refinery/Bulking/Warehouse 2. Unload Event: cumulative Receiving Tanks qty ACM Non-CAS Nomination #3 (Port to Receiving Tank) 3. Load Event: Unload Event 4. Unload Event based on each receiving tank In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination Load and Unload Event.
Gain/Loss captured in LDC of ACM Nomination
Settlement
1. Destination: Settlement based on ACM Nomination Unload
Event
2. Origin: Settlement based on ACM Nomination Load Event
FOB
Multi-modal
(Ocean → Land)
1. Origin
2. Destination
Contract
ACM Intercompany Contract (US – DSI)
Nomination
ACM Nomination (Ocean) – TM relevant
ACM Non-CAS Nomination (Land) – TM Relevant
LDC
ACM Nomination:
➔ US Bulking Plant (Non-valuated)
Manual GI from each Sloc Tank with corresponding qty and
qlty details
➔ US Mill Plant (Valuated)
1. Load Event from Sloc BULK*, per line item of Manual GI
per tank (using partial weight functionality)
➔ DSI Refinery/Bulking/Warehouse
2. Unload Event: cumulative trucks qty of Non-CAS
Nomination
ACM Non-CAS Nomination (Land)
3. Load Event based on each truck: WB qty
4. Unload Event based on each truck: WB qty
--- 第90页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 90 of 167 Transaction Scenario Govt. Weight Document Solution Details In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination Load and Unload Event.
Gain/Loss captured in LDC of ACM Nomination
Settlement
1. Origin Settlement based on ACM Nomination Load Event
2. Destination: Settlement based on ACM Nomination Unload
Event
CIF
Multi-modal
(Ocean → Land)
1. Destination
2. Origin
Contract
ACM Intercompany Contract (US – DSI)
Nomination
Ocean: ACM Nomination – TM Relevant
Land: ACM Non-CAS Nomination – TM Relevant
LDC
ACM Nomination:
➔ US Bulking Plant (Non-valuated)
Manual GI from each Sloc Tank with corresponding qty and
qlty details
➔ US Mill Plant (Valuated)
1. Load Event from Sloc BULK*, per line item of Manual GI
per tank (using partial weight functionality)
➔ DSI Refinery/Bulking/Warehouse
2. Unload Event: cumulative trucks qty of Non-CAS
Nomination
ACM Non-CAS Nomination (Land)
3. Load Event based on each truck: WB qty
4. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination Load and
Unload Event.
Gain/Loss captured in LDC of ACM Nomination
--- 第91页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 91 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
Settlement
1. Destination: Settlement based on ACM Nomination Unload
Event
2. Origin: Settlement based on ACM Nomination Load Event
FOB
Multi-modal
(Land → Ocean
→ Land)
PK in Demta
Bulking
1. Origin
2. Destination
Contract
ACM Intercompany Contract (US – DSI)
Nomination
ACM Non-CAS Nomination #1 (Land) – TM Relevant
ACM Nomination (Ocean) – TM Relevant
ACM Non-CAS Nomination #2 (Land) – TM Relevant
LDC
ACM Non-CAS Nomination #1 (Land):
➔ US Bulking Plant (Non-valuated)
Manual GI per trucks (961)
➔ US Mill Plant (Valuated)
1. Load Event from Sloc BULK, per line item of Manual GI
per tank (using partial weight functionality)
2. Unload Event: Load Event
ACM Nomination (Ocean):
3. Load Event: BL qty
4. Unload Event: cumulative trucks qty of ACM Non-CAS
Nomination #2
ACM Non-CAS Nomination #2 (Land)
5. Load Event: Unload Event
6. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination #2 Load
and Unload Event.
Gain/Loss captured in ACM Nomination Settlement 1. Origin: Settlement based on ACM Nomination Load Event 2. Destination: Settlement based on ACM Nomination Unload Event
--- 第92页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 92 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
CIF Multi-modal
(Land → Ocean
→ Land)
PK in Demta
Bulking
1. Destination
2. Origin
Contract
ACM Intercompany Contract (US – DSI)
Nomination
ACM Non-CAS Nomination #1 (Land) – TM Relevant
ACM Nomination (Ocean) – TM Relevant
ACM Non-CAS Nomination #2 (Land) – TM Relevant
LDC
ACM Non-CAS Nomination #1 (Land):
➔ US Bulking Plant (Non-valuated)
Manual GI per trucks (961)
➔ US Mill Plant (Valuated)
1. Load Event from Sloc BULK per line item of Manual GI
ACM Nomination (Ocean):
2. Load Event: BL qty
3. Unload Event: cumulative trucks qty of ACM Non-CAS
Nomination #2
ACM Non-CAS Nomination #2 (Land)
4. Load Event: Unload Event
5. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination #2 Load
and Unload Event.
Gain/Loss captured in ACM Nomination Settlement 1. Destination: Settlement based on ACM Nomination Unload Event 2. Origin: Settlement based on ACM Nomination Load Event US Mill to DSI Refinery CIF Ship-to-ship (Truck → Barge → Vessel) *CPO from Belian Mill to DSI 1. Destination 2. Origin
Contract ACM Intercompany Contract (US – DSI) Nomination
ACM Non-CAS Nomination #1 (Truck (US)) – TM Relevant
ACM Non-CAS Nomination #2 (Barge (US)) – TM Relevant
ACM Nomination (Vessel) - TM Relevant
--- 第93页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 93 of 167 Transaction Scenario Govt. Weight Document Solution Details
ACM Non-CAS Nomination #3 (Port to Receiving Tank (DSI)) – TM Relevant LDC ACM Non-CAS Nomination #1 (Truck): 1. Load Event based on each truck: WB qty 2. Unload Event = Load Event ACM Non-CAS Nomination #2 (Barge): 3. Load Event based on each Barge; utilize partial weight functionality 4. Unload Event: ship-to-ship qty to Vessel ACM Nomination (Vessel) 5. Load Event: ship-to-ship qty to Vessel 6. Unload Event based on received qty in DSI ACM Non-CAS Nomination #3 (Port to Receiving Tank) 7. Load Event: Unload Event 8. Unload Event based on each receiving tank In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination #3 Load and Unload Event. Gain/Loss captured in ACM Nomination
Settlement 1. Destination: Settlement based on ACM Nomination Unload Event 2. Origin: Settlement based on ACM Nomination Load Event DSI Bulking/Warehouse to DSI Refinery
Refinery A to Refinery B
CIF 1. Destination 2. Origin Contract ACM Intercompany Contract (DSI – DSI) Nomination ACM Non-CAS Nomination #1 – Not TM Relevant ACM Nomination (Ocean) – TM Relevant ACM Non-CAS Nomination #2 – Not TM Relevant LDC ACM Non-CAS Nomination #1 (Origin Tank to Port) 1. Load Event based on each origin tank
--- 第94页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 94 of 167 Transaction Scenario Govt. Weight Document Solution Details DSI Refinery to DSI Bulking *Olein, FAME
- Unload Event: Load Event ACM Nomination (Ocean)
- Load Event: cumulative Origin Tanks qty / BL qty
- Unload Event: cumulative Receiving Tanks qty
ACM Non-CAS Nomination #2 (Port to Receiving Tank) - Load Event: Unload Event
- Unload Event based on each receiving tank In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination #2 Load and Unload Event.
Gain/Loss captured in ACM Nomination
Settlement
1. Destination: Settlement based on ACM Nomination Unload
Event
2. Origin: Settlement based on ACM Nomination Load Event
CIF
Multi-modal
(Ocean → Land)
1. Destination
2. Origin
Contract
ACM Intercompany Contract (DSI – DSI)
Nomination
ACM Non-CAS Nomination #1 – Not TM Relevant
ACM Nomination #2 (Ocean) – TM Relevant
ACM Non-CAS Nomination #3 (Land) – TM Relevant
LDC
ACM Non-CAS Nomination #1 (Origin Tank to Port)
1. Load Event based on each origin tank
2. Unload Event: Load Event
ACM Non-CAS Nomination (Ocean)
3. Load Event: cumulative Origin Tanks qty / BL qty
4. Unload Event: cumulative trucks qty of ACM-Non CAS
Nomination #2
ACM Non-CAS Nomination #2 (Land)
5. Load Event: Unload Event
--- 第95页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 95 of 167 Transaction Scenario Govt. Weight Document Solution Details 6. Unload Event based on each truck: WB qty In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination #2 Load and Unload Event
Gain/Loss captured in ACM Nomination
Settlement
1. Destination: Settlement based on ACM Nomination Unload
Event
2. Origin: Settlement based on ACM Nomination Load Event
CIF
Multi-modal
(Land → Ocean
→ Land)
*PK
1. Destination
2. Origin
Contract
ACM Intercompany Contract (DSI – DSI)
Nomination
ACM Non-CAS Nomination #1 (Land) – TM Relevant
ACM Nomination #2 (Ocean) – TM Relevant
ACM Non-CAS Nomination #3 (Land) – TM Relevant
LDC
ACM Non-CAS Nomination #1 (Land):
1. Load Event based on each truck: WB qty
2. Unload Event: Load Event
ACM Non-CAS Nomination (Ocean):
3. Load Event: BL qty
4. Unload Event: cumulative trucks qty
ACM Non-CAS Nomination #2 (Land)
5. Load Event based on each truck: WB qty
6. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination #2 Load
and Unload Event.
Gain/Loss captured in ACM Nomination Settlement 1. Destination: Settlement based on ACM Nomination Unload Event
--- 第96页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 96 of 167 Transaction Scenario Govt. Weight Document Solution Details 2. Origin: Settlement based on ACM Nomination Load Event *Sample Case/Cargo
Note: Purple – S/4 Gain/Loss Postings will happen automatically for upon contract revenue recognition for all entities
--- 第97页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 97 of 167 4.3.3 .3rd Party Purchase Table 4.3 - 3rd Party Purchase Transaction Scenario Govt. Weight Document Solution Details 3rd party to US/GBE
3rd party to DSI
Buy sell in 1
tank (no
physical
movement)
CPO (US)
FAME (DSI)
Contract
ACM 3rd party Purchase Contract
Nomination
-
LDC
Unload Event
No Gain/Loss
Settlement
Settlement based on Unload Event
LCO
1. Origin
2. Destination
Contract
ACM 3rd party Purchase Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty
2. Unload Event: Buyer WB qty
Gain/Loss captured in LDC
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
FCO
1. Destination
2. Origin
Contract
ACM 3rd party Purchase Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty (only required when Govt
weight: Origin)
2. Unload Event: Buyer WB qty
Gain/Loss captured in LDC
Settlement
1. Destination: Settlement based on Unload Event Details
2. Origin: Settlement based on Load Event Details
FOB
1. Origin
2. Destination
Contract
ACM 3rd party Purchase Contract
Nomination
ACM Nomination – TM relevant
ACM Non-CAS Nomination - Not TM Relevant
LDC
ACM Nomination:
--- 第98页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 98 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
1. Load Event: BL qty; if needed, can utilize partial weight
functionality to track per tank quality
2. Unload Event: cumulative Receiving Tanks qty
ACM Non-CAS Nomination (Port to Receiving Tank)
3. Load Event: Unload Event
4. Unload Event based on each receiving tank
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination Load and
Unload Event.
Gain/Loss captured in ACM Nomination
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
FOB
Multi-modal
(Ocean → Land)
1. Origin
2. Destination
Contract
ACM 3rd party Purchase Contract
Nomination
ACM Nomination – TM relevant
ACM Non-CAS Nomination – TM Relevant
LDC
ACM Nomination:
1. Load Event: BL qty; if needed, can utilize partial weight
functionality to track per tank quality
2. Unload Event: cumulative trucks qty of Non-CAS
Nomination
ACM Non-CAS Nomination (Land)
3. Load Event based on each truck: WB qty
4. Unload Event based on each truck: WB qty
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination Load and
Unload Event.
Gain/Loss captured in LDC of ACM Nomination
--- 第99页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 99 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
CIF
1. Destination
2. Origin
Contract
ACM 3rd party Purchase Contract
Nomination
ACM Nomination – not TM relevant
LDC
ACM Nomination:
1. Load Event: BL qty; if needed, can utilize partial weight
functionality to track per tank quality (only required if Govt
weight: Origin)
2. Unload Event: cumulative Receiving Tanks qty
ACM Non-CAS Nomination (Port to Receiving Tank)
3. Load Event: Unload Event
4. Unload Event based on each receiving tank
In real life, finish discharging first, and then update ACM
Nomination Unload and then ACM Non-CAS Nomination Load and
Unload Event.
Gain/Loss captured in ACM Nomination Settlement 1. Destination: Settlement based on ACM Nomination Unload Event 2. Origin: Settlement based on ACM Nomination Load Event CIF Multi-modal (Land) 1. Destination 2. Origin Contract ACM 3rd party Purchase Contract Nomination Ocean: ACM Nomination – not TM Relevant Land: ACM Non-CAS Nomination – TM Relevant LDC ACM Nomination: 1. Load Event: BL qty; if needed, can utilize partial weight functionality to track per tank quality (only required if Govt weight: Origin) 2. Unload Event: cumulative trucks qty of Non-CAS Nomination ACM Non-CAS Nomination (Land)
--- 第100页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 100 of 167 Transaction Scenario Govt. Weight Document Solution Details 3. Load Event based on each truck: WB qty 4. Unload Event based on each truck: WB qty In real life, finish discharging first, and then update ACM Nomination Unload and then ACM Non-CAS Nomination Load and Unload Event.
Gain/Loss captured in LDC of ACM Nomination Settlement 1. Destination: Settlement based on ACM Nomination Unload Event 2. Origin: Settlement based on ACM Nomination Load Event
Note Gain/Loss Postings will happen automatically for upon unload for origin incoterm.
--- 第101页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 101 of 167
4.3.4
3rd Party Sales
Table 4.4 - 3rd Party Sales
Transaction
Scenario
Govt. Weight
Document
Solution Details
Mill to 3rd party
LCO
1. Origin
2. Destination
Contract
ACM 3rd party Sales Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty
2. Unload Event: Buyer WB qty (only required if Govt weight:
Destination)
Gain/Loss captured in LDC
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
GBE to 3rd party
*Palm Kernel Shell
LCO
1. Origin
2. Destination
Contract
ACM 3rd party Sales Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty
2. Unload Event: Buyer WB qty (only required if Govt weight:
Destination)
Gain/Loss captured in LDC
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
FOB
1. Origin
2. Destination
Contract
ACM 3rd party Sales Contract
Nomination
ACM Nomination – not TM relevant
LDC
1. Load Event: BL qty
2. Unload Event: Qty received by Buyer (only required if Govt
weight: Destination)
Settlement
1. Origin: Settlement based on ACM Nomination Load Event
Details
2. Destination: Settlement based on ACM Nomination Unload
Event Details
Contract ACM 3rd party Sales Contract
--- 第102页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 102 of 167 Transaction Scenario Govt. Weight Document Solution Details DSI Refinery to 3rd party
DSI Bulking to 3rd party
CPO, CPKO, Olein,
FAME
Buy sell in 1
tank (no
physical
movement)
FAME (DSI)
Nomination
-
LDC
Load Event
No Gain/Loss
Settlement
Settlement based on Load Event
LCO
1. Origin
2. Destination
Contract
ACM 3rd party Sales Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty
2. Unload Event: Buyer WB qty (only required if Govt weight:
Destination)
Gain/Loss captured in LDC
Settlement
1. Origin: Settlement based on Load Event Details
2. Destination: Settlement based on Unload Event Details
FCO
1. Destination
2. Origin
Contract
ACM 3rd party Sales Contract
Nomination
ACM Nomination – TM relevant
LDC
1. Load Event: Seller WB qty
2. Unload Event: Buyer WB qty
Gain/Loss captured in LDC
Settlement
1. Destination: Settlement based on Unload Event Details
2. Origin: Settlement based on Load Event Details
FOB/FCA
1. Origin
2. Destination
Contract
ACM 3rd party Sales Contract
Nomination
ACM Non-CAS Nomination - Not TM Relevant
ACM Nomination – TM relevant
LDC
ACM Non-CAS Nomination (Origin Tanks to Port):
1. Load Event based on each origin tank
2. Unload Event: Load Event
ACM Nomination:
3. Load Event: BL qty
4. Unload Event: Qty received by Buyer (only required if Govt
weight: Destination
Gain/Loss captured in LDC of ACM Nomination
--- 第103页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 103 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
Settlement
1. Origin: Settlement based on ACM Nomination Load Event
Details
2. Destination: Settlement based on ACM Nomination Unload
Event Details
FOB
Multi-modal
(Land)
- Origin
- Destination Contract ACM 3rd party Sales Contract Nomination ACM Non-CAS Nomination - Not TM Relevant ACM Nomination – TM relevant LDC ACM Non-CAS Nomination (Land)
- Load Event based on each truck: WB qty
- Unload Event: Load Event ACM Nomination:
- Load Event: BL qty
- Unload Event: Qty received by Buyer (only required if Govt weight: Destination Gain/Loss captured in LDC of ACM Nomination Settlement
- Origin: Settlement based on ACM Nomination Load Event Details
- Destination: Settlement based on ACM Nomination Unload Event Details CIF/CFR
- Destination
- Origin Contract ACM 3rd party Sales Contract Nomination ACM Non-CAS Nomination - Not TM Relevant ACM Nomination – TM relevant LDC ACM Non-CAS Nomination (Origin Tanks to Port):
- Load Event based on each origin tank
- Unload Event: Load Event ACM Nomination:
- Load Event: BL qty
- Unload Event: Qty received by Buyer Gain/Loss captured in LDC of ACM Nomination
--- 第104页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 104 of 167
Transaction
Scenario
Govt. Weight
Document
Solution Details
Settlement
1. Destination: Settlement based on ACM Nomination Unload
Event Details
2. Origin: Settlement based on ACM Nomination Load Event
Details
CIF
Multi-modal
(Land →
Ocean)
1. Destination
2. Origin
Contract
ACM 3rd party Sales Contract
Nomination
ACM Non-CAS Nomination - Not TM Relevant
ACM Nomination – TM relevant
LDC
ACM Non-CAS Nomination (Land)
1. Load Event based on each truck: WB qty
2. Unload Event: Load Event
ACM Nomination:
3. Load Event: BL qty
4. Unload Event: Qty received by Buyer
Gain/Loss captured in LDC of ACM Nomination
Settlement
1. Origin: Settlement based on ACM Nomination Load Event
Details
2. Destination: Settlement based on ACM Nomination Unload
Event Details
DAP/DAT
(as-is similar
with CIF Multi-
modal (Land →
Ocean)
1. Destination
2. Origin
Contract
ACM 3rd party Sales Contract
Nomination
Land: ACM Non-CAS Nomination – TM Relevant
Ocean: ACM Nomination – TM Relevant
LDC
ACM Non-CAS Nomination (Land)
1. Load Event based on each truck: WB qty
2. Unload Event: Load Event
ACM Nomination:
3. Load Event: BL qty
4. Unload Event: Qty received by Buyer / BL qty
Settlement
1. Origin: Settlement based on ACM Nomination Load Event
Details
--- 第105页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 105 of 167 Transaction Scenario Govt. Weight Document Solution Details 2. Destination: Settlement based on ACM Nomination Unload Event Details *Sample Case/Cargo
Note Gain/Loss Postings will happen automatically for upon contract revenue recognition for all entities.
--- 第106页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 106 of 167
4.3.5 LDC Variations for Backstop Scenarios LDC variations for Backstop Scenarios will be covered separately as part of the backstop solution. Currently this detail is captured at Backstop Process Blueprint. Further discussions will be required at the detailed design discussions to validate the solution. This will also include for example DSI-GAI scenario.
4.3.6 Intercompany Multi-Modal Destination Scenario Multi-Modal Scenario can be broken into distinct parts and can be tackled independently. Below is the figure for Intercompany Multi-Modal Destination Scenario.
Figure 4.5 - Intercompany Multi-Modal Destination Scenario
--- 第107页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 107 of 167 4.3.7 Intercompany Multi-Modal Origin Scenario Multi-Modal Scenario can be broken into distinct parts and can be tackled independently. Below is the figure for Intercompany Multi-Modal Origin Scenario.
Figure 4.6 - Intercompany Multi-Modal Origin Scenario
--- 第108页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 108 of 167 5 Appendix 5.1 ID Goods Movement Variations
--- 第109页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 109 of 167
--- 第110页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 110 of 167
--- 第111页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 111 of 167
--- 第112页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 112 of 167
--- 第113页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 113 of 167
--- 第114页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 114 of 167
--- 第115页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 115 of 167
--- 第116页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 116 of 167
--- 第117页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 117 of 167
--- 第118页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 118 of 167
--- 第119页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 119 of 167
--- 第120页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 120 of 167
--- 第121页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 121 of 167
--- 第122页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 122 of 167
--- 第123页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 123 of 167
--- 第124页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 124 of 167
--- 第125页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 125 of 167
--- 第126页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 126 of 167
--- 第127页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 127 of 167
--- 第128页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 128 of 167
--- 第129页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 129 of 167 5.2 Requirement List Please refer to the link below for the complete list of requirements, including those related to SAP ACM that have been cancelled or reassigned to other modules. For ease of navigation, requirements can be filtered by Process Level 2 (e.g., Trade Capture, Delivery Planning & Execution, Settlement & Invoicing, Trade Control, and Backstop Process) to identify the relevant items.
GAR_Requirement Traceability Matrix_CTRM_v1.1 (Cleaned)
Process L1: Commodity Trading & Risk Management Process L2: Delivery Planning & Execution
Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 019 2.1 Delivery Planning Barge pre- planning GAR will do pre-planning on barges outside the system. Need the ability to enter into the system once users know which barge belongs with which contract. There could be multiple contracts loaded onto the same barge Low Medium Fit Once barge planning is done outside the system, multiple LDCs each corresponding to contract can have the same barge ID can be clubbed and delivered together ACM- 040 2.2 Goods Movement & Quality Capture – LDC & Applications Input and Update Delivery Date Ability to input and update delivery date High Medium Gap Enhancement to be done based on req ACM- 058 2.2 Goods Movement & Quality Capture – LDC & Applications Direct Distribution Ability to enable direct distribution - External Warehouse Management (EWM) * Support direct customer pickup operations * Enable delivery of palm products from external warehouses * Handle margarine product deliveries * Facilitate delivery without further processing High High Gap KDD open for EWM -ACM ACM- 092 2.1 Delivery Planning Trade-Related Master Data - Ability to manage vessel and shipment data: High Medium Gap Additional custom field at LDC& contract
--- 第130页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 130 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Vessel & Shipment Data - Capture vessel information - Link vessels to specific sales contracts - Update planned vessel matches when needed - Use strategy field to segregate volume by vessel origin - Capture shipment-related events and dates - Track vessel nomination, BL, load, and discharge dates - Define document workflow status (reviewed, approved, ready) ACM- 096 2.1 Delivery Planning Parcel Field Attribute Configuration Ability to set up and configure parcel fields: - Copy down fields from contract level to parcel level - Include load port, destination port, and other pre-defined fields - Support contract-specific terms like PORAM / FOSFA for scheduling and nomination High High Fit Basic Configuration ACM- 097 2.2 Goods Movement & Quality Capture – LDC & Applications Parcel Status Tracking Mechnism Ability to tracking parcel status throughout lifecycle: - Manage parcels based on contractual/planned/nominated/actualized status - Support status tracking even when parcels are split - Feed parcel status into position and P&L management - Ability to have notification alert based on PORAM / FOSFA (ex. Receive reminder notification to receive vessel nomination from buyer XX days before delivery date) High Medium Fit Standard ACM functionality offerings
--- 第131页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 131 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
ACM-
098
2.1 Delivery
Planning
Nomination
Processing
Ability to handle nominations:
- Ability to nominate schedule for FOB
and other incoterms
- Ability to set contract-specific terms like
PORAM / FOSFA for scheduling and
nomination
- Create nominations from various
contract types
- Move parcels from planned to
nominated status
- Capture best known date and quantity
from operators
- Enable multiple sort levels for
open/closed contracts
- Allocate purchase contracts/inventory to
(execution orders - S4 Team)
- Allocate multiple purchase/sales
contracts against one voyage
- Plan inventory and reserve shipments
High
High
Gap
Custom Fields at
Nomination as per the
Requirement
ACM-
099
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Parcel
Operations
Ability to manage the complete parcel
lifecycle:
- Split one parcel into multiple parcel
allocations (Application splitting is
allowed)
- Support multiple discharge locations
(Contract optionality)
- Handle and Record separate title
transfer dates and documents (Document
Flow Workcenter)
- Move parcels from planned >
nominated > actualized status (in ACM
status planned (nominated) > delivered >
invoiced) - terminalogy
- Capture all relevant information from
supporting documentation
- Process quality and quantity
High
High
Fit
Standard Product
Offering
--- 第132页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 132 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions adjustments/escalators (DPQS functionality) - Create multiple plans for execution against open contracts (Multiple nominations exist based on quantity for a single contract) - Capture dates, inventory locations, and quantities (auto-captured weighbridge and ACM interface) - Track settlement instructions and comments (track status create > release > approve for settlements + notes) ACM- 100 2.2 Goods Movement & Quality Capture – LDC & Applications Quantity Changes & Adjustments Ability to handle quantity changes and adjustments: - Handle fixings without lower tolerance - Manage short shipments manually - Create new cargoes from cumulative short shipments - Support splitting (e.g., 10k MT into 2k, 3k, 5k) - Capture actualized quantities (e.g., 1.8k, 2.8k, 4.8k) - Close positions and create new cargoes for remaining quantities - Manually apply quantities up to overfill tolerance - Automatically apply quantities without using tolerance - Support over-allocation High High Fit Load Data Capture ACM- 101 2.2 Goods Movement & Quality Capture – LDC & Applications Inventory Linkage and Integration Ability to link parcels with inventory: - Discharge into (build) inventory - GR (ACM) - Withdraw from inventory- GI (ACM) - Track losses/gains between load and discharge ports (ACM) High High Fit LDC created GI/GR which updates the inventory
--- 第133页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 133 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
- Measure differences for insurance
purposes (ACM)
- Transfer cargoes between ships (trans-
shipment) (ACM)
ACM-
102
2.1 Delivery
Planning
Control and
Processing
Framework
Ability to establish framework for
controlling execution processes:
- Implement control points on sales order
nominations
- Prevent scheduling without contracts or
with zero-price contracts (validation
group at nomination)
- Ability to proceed with nomination, BL
even without fully priced contracts (SG)
- Edit purchase orders with alternative
ship-to locations (at nomination and auto-
populated at order level provided that it is
defined at the contract optionality)
- Navigate between tickets, counterparty
details, and contracts (default)
- Receive planned deliveries (default)
- Track loads booked, hauled, and
remaining (part of TM scope)
High
High
Fit
Optionality
ACM-
157
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Ops
Documentation
Reporting
Ability to enable documentation tracking:
- Provide mass balance reporting at any
time
- Support filtering and reporting
capabilities (custom report based on
confiragtion defined by business users)
- Manage temporary storage of sugar at
port facilities (part of EDM, ID might not
be using port as a storage location but
need for sugar)
- Support dual documentation processes
(manual and electronic) (send output
printout and EDI or email via electronic)
High
Medium
Gap
Mass Balance Reporting
setup
--- 第134页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 134 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
ACM-
198
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Vessel
Reference
Ability to manage vessel references:
- Handle cases where Purchase is linked
to Vessel A (Indonesia to Malaysia)
- Support Malaysia to Indonesia routes
with Vessel B linked to Sell deal
- Show Vessel B on invoices
- Use Vessel A in SAP posting
High
Medium
Gap
Form output can be
enhanced to show Vessel
B
ACM-
214
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
BL Tracking and
Allocation
Ability to track BL information:
- Track barges/batches back to original
vendor PO
- Allocate freight based on BL/loaded
quantity
- Input quality per truck/vessel
High
High
Fit
LDC and Forms
ACM-
217
2.1 Delivery
Planning
Invoice Approval
Ability to manage invoice approvals:
- Bypass contract approval process for
proforma invoice creation for export
purpose
High
Medium
Gap
Automation of settlement
release and approval
based on business
specific conditions can be
leveraged for the solution
ACM-
219
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Sustainability
Certification
Ability to include sustainability
certifications:
- Mark CPO with sustainability labels
(ISCC) where needed
- Maintain 1:1 relationship between
contract and certificate on load side
- Capture certification information
(number, type, premium)
High
High
Gap
Enhancement to be done
based on req (add fields
for certificate details at
the contract level)
ACM-
220
2.1 Delivery
Planning
Import
Documentation
Ability to manage import documentation:
- Manage arrival documentation (bank
documents, OBL)
- Create PE (Export Permit) in
government system
This is related to ACM-946 High High Fit Forms Enhancement ACM- 221 2.1 Delivery Planning Ops Document Tracking Ability to track documentation: - Track open customs clearance High High Gap Forms / Reports Enhancement
--- 第135页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 135 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions documents, delivered volumes - Monitor receipt of customer documentation (gap might need to formulate a form/report level) - Track pending justifications and open items (gap might need to formulate a form/report level) - Manage comprehensive documentation parameters (gap might need to formulate a form/report level) This is Agiblock-EU Requirements. ACM- 253 2.1 Delivery Planning Port Management Ability to manage ports: - Define both Load and Destination ports on physical trades - Support port definition regardless of title transfer location High Medium Fit TSW Location will carry information about ports ACM- 254 2.1 Delivery Planning Movement Modeling Ability to model transportation movements: - Capture and model physical transportation (Vessel, Barge, Rail, Truck) - Plan physical and material movements within system - Support single vessel/truck transportation - Handle combination vessel and truck transportation (Gap - Multi Modal) - Manage HUB Tank/Titip Timbun combinations (Gap - Multi Modal) - Document customer-arranged trucking and transportation - Support operations across multiple terminals (5-6) - Manage different locations across the USA High High Gap Part of ACM-TM Integration
--- 第136页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 136 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 255 2.1 Delivery Planning Nomination Processing Ability to process vessel nominations: - Manage vessel nomination process - Receive vessel nominations from buyers - Forward nominations to shippers - Track and maintain nomination status throughout process - Handle complete vessel nomination workflow in third-party transactions (out of acope ACM) - Create and manage all possible movements (Sell, Storage, transport modes) - Match Back to Back to back transactions - Model transhipment - Handle multiple tickets (trucks/railcars) as part of the same tender - Model vessel and inventory gains/losses - Coordinate arrival of stock via vessels shared with CNF customers High Medium Fit Standard Solution Behavior ACM- 257 2.1 Delivery Planning Surveyor Appointment Ability to manage surveyors: - Appoint load port surveyors - Maintain database of approved surveyors - Store and manage surveyor reports and certificates High Medium Gap Part of ACM-TM Integration ACM- 260 2.1 Delivery Planning Shipment Document Generation Ability to generate shipping documents: - Generate shipping instructions, packing lists, appointment letters - Print shipping documentation - Create documentation for 3rd party shipments - Create Memo/Shipping Instruction for QM High High Gap Custom fields can be added at contract / LDC level. ACM-TM Integration
--- 第137页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 137 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - Create tender (shipment advice) - Create documentation for cross-border shipments - Support dedicated freight and documentation teams ACM- 261 2.1 Delivery Planning Transport Information Capture Ability to capture transport information: - Capture GAR-specific information at tender and ticket level - Review existing plans and capture actual shipping information - Record event dates, quantities, quality, and costs High Medium Gap Custom fields can be added at contract / LDC level. Open KDD on ACM-TM Integration ACM- 272 2.1 Delivery Planning Multi-modal Transport Ability to manage multiple transport modes: - Support rail cars (DAP and ex-tank) - Manage trucks (ex-tank for Palm, DDP for Oleo) - Coordinate barges (ex-tank) - Handle pipeline transfers (ex-tank) High Medium Fit Baseline Configuration ACM- 290 2.1 Delivery Planning Transport Coordination Ability to enable coordinating transportation: - Book transportation with contracted vendors - Support DDP/DAP shipment requirements
This relates to ACM-949 High Medium Fit Standard Product Behavior ACM- 291 2.1 Delivery Planning Pre-Shipment Planning Ability to enable pre-shipment planning: - Manage logistics planning prior to execution - Eliminate reliance on spreadsheets - Provide integrated planning tools High Medium Fit Standard Product Behavior ACM- 293 2.1 Delivery Planning Nomination- Level Port Specification Ability to enter and utilize load port and discharge port information during the High Medium Fit Standard Solution Behavior
--- 第138页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 138 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions nomination process rather than solely pulling this data from the contract level ACM- 321 2.2 Goods Movement & Quality Capture – LDC & Applications Quality Standards Ability to manage quality standards: - Enforce NIOP standards as agreed in customer contracts - Validate compliance with quality requirements High Medium Gap DPQS Solution + Enhancement for field ACM- 332 2.2 Goods Movement & Quality Capture – LDC & Applications Inventory Matching Ability to match inventory in postings - Match FIFO upon discharge - Link sales and purchases in combined postings - Support drawing from multiple contracts based on FIFO High High Gap KDD Batch Determination ACM- 333 2.1 Delivery Planning Inventory Source Identification Ability to manage inventory sources: - Differentiate inventory sources (Downstream, Upstream, 3rd Party) - Differentiate stock sources (Downstream, Upstream, 3rd Party) - Use different accounts based on party type (downstream/upstream) High High Gap SS: Might need a separate report ACM- 390 2.2 Goods Movement & Quality Capture – LDC & Applications Unload Event Documentation Workflow Ability to handle Proof of Delivery in the unload event of the LDC process, requiring POD input to complete the process when unload events are needed based on incoterms. High High Gap POD works in unload event ACM- 393 2.2 Goods Movement & Quality Capture – LDC & Applications Process Reversal Control Workflow Ability to control reversal of settlement/LDC processes through authorization settings, with reversals reopening nominations and returning quantities to the contract level High Medium Fit Auth can be controled through SAP Security ACM- 397 2.1 Delivery Planning Document Prefix Configuration Ability to configure number range settings for each printout with different prefixes High High Gap Form Requirment
--- 第139页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 139 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
with Sequential
Numbering
while maintaining sequential numbering
across various document types during
the nomination process
ACM-
399
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Flexible BL-LDC
Linkages for
different size of
quantity (BL or
LDC in MT)
Ability to have the flexibility to facilitate
different size of LDC linked to BL and
vice versa
- Example, Multiple BLs linked to 1 LDC
High
Medium
Gap
Enhancement to be done
based on req
ACM-
400
2.1 Delivery
Planning
Generate
Proforma
Invoice and
Shipping Doc
during
Nomination
Ability to generate proforma invoices
during the nomination phase by
accessing the output file functionality
High
High
Fit
Form Requirment
ACM-
401
2.1 Delivery
Planning
Additional
Shipping
Document
Fields
Configuration
Ability to configure additional required
fields such as Surveyor Name,
Consignee, and Notify Party for
generating pre-load documents after
nomination completion
High
Medium
Gap
Enhancement to be done
based on req
ACM-
410
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Intercompany
Invoice Visibility
Via Document
Flow
Ability to view intercompany sales invoice
numbers through the Document Flow of
the contract or Stock Transport Order,
rather than directly on the intercompany
purchase invoice
High
Medium
Fit
Doc flow
ACM-
476
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Inventory
Management
During Pending
Transactions
Ability to allow goods to remain classified
as inventory throughout the transaction
lifecycle until final settlement. Inventory
status should be maintained regardless
of intercompany billing status.
High
No
Change
Fit
Aligned with standard
solution behavior
ACM-
521
2.1 Delivery
Planning
Multi-Role
Nomination
Execution
Ability for scheduler or Trade Operations
to perform nomination functions
High
Medium
Fit
Security Roles and
Authorization
--- 第140页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 140 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 523 2.2 Goods Movement & Quality Capture – LDC & Applications Automated Journal Entry Generation for Goods Movement Ability to automatically generate journal entries for both load and unload events based on weighbridge integration High Medium Fit Standard Product Behavior ACM- 524 2.2 Goods Movement & Quality Capture – LDC & Applications Automated Journal Entry Generation for Goods Movement Ability to create system entries for goods movement at both loading and unloading stages High Medium Fit Standard Product Behavior ACM- 543 2.2 Goods Movement & Quality Capture – LDC & Applications Outturn Formula Ability to access and utilize the outturn formula via DPQS within the system High Medium Fit This requires DPQS set up - Customization ACM- 549 2.2 Goods Movement & Quality Capture – LDC & Applications One-to-One BL to LDC Mapping Ability to manage multiple LDCs separately when there are multiple Bills of Lading (e.g., 5 BLs requiring management of 5 separate LDCs) High Medium Fit System Design will allow 1LDC to have multiple BLs ACM- 552 2.2 Goods Movement & Quality Capture – LDC & Applications Individual BL Processing with Separate Outturns Ability to process 2 BLs with individual document bypass to ADM requiring 2 separate outturns High High Gap DocByPass solution via Strings Work Center ACM- 553 2.2 Goods Movement & Quality Capture – Contract-Level Threshold Percentage Establishment Ability to establish outturn threshold percentage primarily at the contract level High Low Gap DocByPass solution via Strings Work Center
--- 第141页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 141 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
LDC &
Applications
ACM-
620
2.1 Delivery
Planning
Vessel Stage
Visibility
Ability to view quantity status for each
contract showing vessel stages
High
High
Gap
Part of Virtual Crush KDD
Solution
ACM-
622
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Loading
Discharge Batch
Entry
Ability to enter batch numbers at Loading
Discharge Certificate (LDC) stage for
tracking PK to PKO conversion
High
High
Gap
Part of Virtual Crush KDD
Solution
ACM-
658
2.1 Delivery
Planning
Partial Delivery
Credit
Ability to allow flexible partial deliveries
based on available credit limit (e.g., ship
100MT if credit only covers partial 500MT
order)
High
Medium
Fit
It is a fit. This check
happens at nomination,
where the scheduled
quantity is validated
against contract quantity
to assess the business
model.
ACM-
689
2.1 Delivery
Planning
Port Nomination
Ability to nominate different destination
ports (with separate contracts for different
pricing)
High
No
Change
Fit
Nomination can be
created for several
contracts together.
ACM-
698
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Pricing
Completion
Control
Ability to configure pricing completion
requirements before or after execution
with custom logic at LDC level
Update:
Ability to Price contract during or after
LDC
High
No
Change
Gap
Pricing routine creation
required
ACM-
706
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Independent
LDC Execution
Ability to execute LDC without pegging
contracts for individual purchases and
sales
High
No
Change
Fit
Standard ACM
functionality.
--- 第142页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 142 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 707 2.2 Goods Movement & Quality Capture – LDC & Applications Mass LDC Creation Ability to create multiple LDCs in mass High Low Gap Excel upload for Mass LDC creation will need a cUstom Development ACM- 708 2.2 Goods Movement & Quality Capture – LDC & Applications Document Attachment Ability to attach surveyor documents at the LDC level High No Change Fit Attachments can be added at LDC Level. Recommended to have them stored at a different server and attach a link instead ACM- 710 2.2 Goods Movement & Quality Capture – LDC & Applications BL Information Tracking Ability to capture and track Bill of Lading information through LDC with visibility in goods movement documents High Low Gap Any other details other than the Bill of Lading number needs custom development to accommodate ACM- 711 2.2 Goods Movement & Quality Capture – LDC & Applications Automatic Document Creation Ability to automatically create purchase orders, deliveries, goods movements, and corresponding sales documents during LDC execution High No Change Fit SD/MM documents are automatically created at the background when LDC is posted. ACM- 713 2.1 Delivery Planning Pegging Validation Rules Ability to limit pegging based on specific criteria with built-in and extendable validation logic High Medium Gap Nomination pegging already has some built in checks. Further requirmeents needs to be discussed in detail ACM- 714 2.1 Delivery Planning Re-pegging Functionality Ability to reject and re-peg contracts at nomination level (match and unmatch) High No Change Fit Can be changed aslong as there is no execution ACM- 740 2.2 Goods Movement & Quality Customer DPQS Linking Ability to link DPQS to customer specifications High No Change Fit Separate DPQS can be defined per certification level/customer
--- 第143页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 143 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Capture – LDC & Applications expectation for the same list of materials and plant combination ACM- 742 2.2 Goods Movement & Quality Capture – LDC & Applications Quality Results Matching Ability to compare quality results at load event with contract quality parameters High No Change Fit DPQS added ot the Contract has the details of the expected Quality.
LDC Load event records the actual Quality per Load.
Application Document for
that LDC will show the
Accept/reject status.
ACM-
743
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Certification
Tracking
Ability to track CoAs, certifications, and
quality parameters with customer linkage
High
No
Change
Fit
Separate DPQS can be
defined per certification
level/customer
expectation for the same
list of materials and plant
combination
ACM-
747
2.1 Delivery
Planning
EUDR
Compliance
Tracking
Ability to trace EUDR compliance and
segregate compliant vs non-compliant
inventory
High
Medium
Gap
Interface between SAP
and E-Waybill
ACM-
749
2.2 Goods
Movement &
Quality
Capture –
LDC &
Applications
Manual Pricing
Lot Selection
Ability to manually select pricing lots
during load application
High
No
Change
Fit
Can achieve this using
the Manual Application
Workcenter
ACM-
758
2.1 Delivery
Planning
Prepayment
Nomination
Blocking
Ability to block nominations based on
prepayment agreement status
High
Medium
Gap
Custom development
needed
ACM-
802
2.2 Goods
Movement &
Quality
Material
Substitution with
DPQS
Ability to change materials within DPQS
schedule during LDC with automatic
premium/discount recalculation
High
No
Change
Fit
Standard Solution
Behavior
--- 第144页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 144 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Capture – LDC & Applications ACM- 803 2.2 Goods Movement & Quality Capture – LDC & Applications Negotiation- Based Premium Management Ability to handle negotiated premiums through optionalities without requiring fixed DPQS rules High No Change Fit Standard Solution Behavior ACM- 812 2.2 Goods Movement & Quality Capture – LDC & Applications Mass Gate Pass Upload Ability to mass upload gate pass data through Excel for Load Data Capture High No Change Fit Standard Solution Behavior ACM- 818 2.2 Goods Movement & Quality Capture – LDC & Applications [Quantity Difference Case] Post- Receipt Quantity Adjustment Ability to cancel partial quantities after goods receipt for error corrections (not for standard transit losses which should be captured at actual receipt) High No Change Fit Standard Solution Behavior ACM- 839 2.2 Goods Movement & Quality Capture – LDC & Applications Damage Goods- Based Inventory Adjustment Ability to adjust inventory for rejected/damaged goods through complaints process High No Change Fit Can use dispute process at LDC to achieve this ACM- 852 2.2 Goods Movement & Quality Capture – LDC & Applications Gain/Loss in- transit Ability to monitor gain and loss (cause: evaporation) and post it to finance side.
Current solution:
1) Downstream Bulk - custom program to
auto GR/GI for the "lost in transit"
2) Upstream - GI Loss from temporary
storage location
Medium
High
Fit
Setup required for auto
trigerring loss-movement
--- 第145页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 145 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
[27 May - I2C] Need to enhance system to avoid manual adjustment due to error POD. Ensure POD reversal can automatically posted when Billing reversal is posted
Transferred to CTRM-1339 ACM- 897 2.2 Goods Movement & Quality Capture – LDC & Applications Product Transformation Management Ability to manage blending operations with standardization for quality parameter control, and reprocessing through both external service providers and internal operations High
Fit ACM Production Services Functionality ACM- 898 2.1 Delivery Planning Capacity Planning and Allocation (Tank Management) Ability to manage product capacity based on actual movements and forecasts,i.e., accounting for inbound / outbound volumes per tank and commodity properties High
Fit LDC Account Postings ACM- 905 2.1 Delivery Planning Macro Contracts with Multiple Delivery Locations Ability to manage contracts with multiple ship-to destinations, support volume exchanges between related entities, maintain different transportation costs per location, and control total volume integrity when reallocating between destinations High
Fit Optionalities for multiple locations, inter/intra for volume exchanges, primary basis as freight costs with valuation points. Volume integrity is part of standard product offering ACM- 906 2.1 Delivery Planning Multi-Contract Delivery Order Allocation Ability to create delivery orders spanning multiple sales contracts for the same customer, with automatic allocation based on contract balances and customer-specific tolerance parameters High
Fit Back-to-Back Pegging for Different Contracts with Different Details ACM- 907 2.1 Delivery Planning Unallocated Delivery Order Management Ability to generate delivery orders without immediate contract allocation, with subsequent linking capability once actual High
Fit Standard Product Offering. Contract
--- 第146页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 146 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions weights are confirmed from terminal tickets Application after actual weights are confirmed ACM- 911 2.2 Goods Movement & Quality Capture – LDC & Applications Property-Based Matching for Stock Selection Ability to select and allocate stock based on commodity properties defined at contract level, with filtering capability for quality parameters, customs attributes, and usage specifications High
Gap Batch Management Solution ACM- 913 2.1 Delivery Planning Tank Management and Document Tracking Ability to track product per tank per BL with MRN-level detail for customs reporting and operational planning High No Change Gap Standard Product Offering ACM- 923 2.1 Delivery Planning Multi-Modal Vessel Support Ability to handle containerized and break bulk operations High
Gap Custom Report ACM- 933 2.2 Goods Movement & Quality Capture – LDC & Applications DUA form generation Ability to generate DUA form directly from trading platform. Information needed includes HS Code, usage type, DUA number, MRN, TORO Information,etc so that selling contract can get correct incoming batch.
Assume batch characteristics is used, user request for auto derivation from contract to batch (instead of manual fill when GR). High High Gap TORO/DUA Validations and output forms generation to be configured ACM- 1006 Goods Movement & Quality Capture, Settlement Creation, Adjustment, & Approval Settlement of Multiple GR/GI to match with Invoice from Vendor Ability to settle multiple GR/GI in one contract altogether to be able to match the quantity with the invoice / prepayment invoice quantity for tax tracking purposes (There should be a view similar to ME23 for this purpose)
e.g. during GR, we can knock off the
prepayment invoice with the exact GR
High
High
Gap
- Ability to settle multiple
GR/GI can be done via
settlement (multiple LDCs
can be settled together).
- For Purhase: Application
Splitting per Quantity as
per Invoice from Vendor
requires enhancement
- However, custom view
similar to ME23 needs to
--- 第147页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 147 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions quantity according to the prepayment amount. be created per business requirement. ACM- 1016 Delivery Planning Nomination Restriction Prior to Prepayment Completion Ability to restrict Sales Order / Nomination from being sent to Operations team prior to Prepayment Completion, except for multiple Prepayment scenario (Biodiesel) High High Gap Enhancement at nomination level
This Depends on whether ACM is using Nomination or SO/Approach Decision ACM- 1019 Goods Movement & Quality Capture Local Purchase - Remove LDC restriction for Prepayment Ability to create LDC events prior to prepayment execution (Purchase scenario ONLY) in the event that goods are received even before any prepayment has been done High Medium Fit Proposed Solution is using the workaround to manually tick the "Prepayment Paid" to allow for LDC. Or we can use a custom logic to enable LDC for Indonesia Purchase only ACM- 1031 Delivery Planning Different Document Flow View on Nomination Level Ability to have a different view on the document flow to see that when we expand Nomination, we can see all the LDCs associated with that specific Nomination
This relates to CTRM-1006
Medium
High
Gap
Doc flow workcenter is a
workaround. Report
needs to be developed as
per required. SAC Report
might be needed.
ACM-
1033
Goods
Movement &
Quality
Capture
Contract-based
Claims Tracking
Ability to track debit/credit note for claims
tracking purpose (ex. Biodiesel Claim to
BPDP, Claims to Transporter) under one
contract document flow and to know
whether a claims has been processed or
unprocessed
(For BPDP Claims, 1 Debit/Credit Note could apply to multiple Contracts) High High Gap Enhancement needed at DFW and debit/credit note. Reference field at credit /debit note can be utilized. The enhancement will allow the Document Flow to pick up contract-relevant Credit/Debit Note
Claims to BPDP -> integration with SD Billing
--- 第148页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 148 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
Claims quality/ quantity to
vendor/ transporter ->
claims via separate FI
Billing, or use Credit/
Debit Memo
ACM-
1041
Goods
Movement &
Quality
Capture
Local Purchase
- Bonded Zone
AJU Number for
GR
Ability to input AJU number (AJU Number
can be received from Surat Persetujuan
Pemasukan Barang (SPPB) and
Dokumen Bea Cukai (BC)) into the each
GR for purchase delivery to Bonded
Zone. (Vendor needs to have SPPB and
BC to be able to deliver to bonded zone)
High
High
Gap
Custom check which
prevents LDC creation
incase the details are not
available
ACM-
1049
Delivery
Planning
Export Sales
Biodiesel:
Shipping
document
generation
Ability to create all the relevant
documents for shipping
(In As-is process Sales Order can be
issued
once pre-payment from customer is
received, and SO is required for
shipment.)
High
Medium
Fit
Exist in Standard
Functionality. Forms can
be accommodated. The
triggering point can be the
nomination or Order level
depending on decision
ACM-
1050
Delivery
Planning
Output form
types
Ability to print output forms in PDF, MS
Word and Excel in editable format.
Document need to be edit to update the
planned quantity with the actual delivered
quantity (loaded to the ship) for Export
Declaration document purpose.
High
Medium
Gap
SAP by default doesn't
allow form output to be
Excel / Word. The default
form output accomodated
is only PDF.
Enhancement will be
required to allow for
editing of the forms
ACM-
1051
Export Admin Documents Ability to generate print Proforma Invoice (PI), Shipping Instruction (SI), Packing List (PL), Appointment Letter (AL) and etc during nomination creation/confirmation. High Medium Gap Any additional fields required to present all information in the tender document output need to be added. But afterward, forms can be used to generate these documents
--- 第149页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 149 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1052 Delivery Planning Export Sales: Document Printing Ability to print Loadport Agent, Notify Party, Surveyor deatils in output forms. High Medium Gap Enhancement to add additional fields required on Nomination-level for fields not provided in standard Nomination fields ACM- 1053 Delivery Planning Export Sales: Document Printing Ability to have dropdown list for surveyor name, Notify Party and Load port Agent
Relates to CTRM-1052 High Medium Gap Needs enhancement to add dropdown list to additional fields. Need custom table to allow users to easily maintain these dropdown lists ACM- 1055
Tender Document Ability to generate tender document
AS-Is:
After loading completion, Export Admin
need to prepare and send tender to
buyer.
tender document is done manually,
contains the following information:
Shipment advice, contract number,
vessel name, commodity, quantity, BL
number, Date, ship tank number,
Destination
High
Medium
Gap
Any additional fields
required to present all
information in the tender
document output need to
be added. But afterward,
forms can be used to
generate these
documents
ACM-
1056
Goods
Movement &
Quality
Capture
PEB
Ability to maintain PEB details (PEB Date
& Number) in system (Export Declaration
required right after loading)
As-Is: EA unit raises PEB details and these details (PEB Number & Date) shared with Back Office team. BO team input these details into system for billing purpose. Medium Medium Gap Enhancement will be required to add this PEB details field at Settlement Level or LDC level. But workaround is available ACM- 1058
Benificiary Documents Ability to generate after shipment documents (beneficiary documents, Medium Medium Fit Exist in Standard Functionality
--- 第150页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 150 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Packing List to buyer, manufacturers certificates, etc by system) ACM- 1060
Vessel Nomination Ability to have notification alert based on FOSFA/PORAM standards Ex: Reminder notification to receive vessel nomination from buyer XX days before delivery date Medium High Gap Custom Report. Manually retriggering of form ACM- 1061
Late BL date
alert
Ability to calculate/alert on all the contract
fulfilment pricing & charges
Ex: Need to charge buyer if BL is given
late
High
High
Gap
Custom Report. Manually
monitoring, generate
automated daily
notification based on the
late status
ACM-
1068
Delivery
Planning
Credit limit
check
Ability to verify Credit limit during Order/
Nomination creation with business
required appendix criteria (block/ warning
based on the policy setting)
High
High
Gap
Credit Limit Check
Solution
ACM-
1070
Delivery
Planning
Blocked
Nomination
Ability to release blocked Nomination
after credit risk valoidations
High
High
Gap
Credit Limit Check
Solution
ACM-
1150
Delivery
Planning
Credit limit
notification
Ability to automatically notify the trader
when a sales order fails the credit check
Medium
High
Gap
Enhancement in
Nomination. Can explore
nomination and LDC for
order level check and
enhancmeent to be done
to notify trader
Part of KDD discussion
for Credit Check
ACM-
1156
Delivery
Planning
Credit Limit
The system should have the ability to
block Sales Order in case of breach of
credit limit.
Medium
High
Gap
Enhancement in
Nomination. ACM- FSCM
integration at Nomination.
KDD discussion
ACM-
1157
Delivery
Planning
Collateral and
Credit Support
The system should provide for manual
control of exemptions and overrides to
credit status and alert indicators whilst
ensuring appropriate permissioning.
Medium
High
Gap
Enhancement in
Nomination. ACM- FSCM
integration at Nomination.
KDD discussion
--- 第151页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 151 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
Sales Order Release function.
ACM-
1172
Goods
Movement &
Quality
Capture
Unit of
Measurement
Conversion
Ability to accommodate conversion of unit
of measurement (eg. L to kg, kg to L)
eg. for Biodiesel FAME, contract, billing
and physical goods loaded are recorded
in Liters, but goods movement in SAP
need to be recorded in Kg.
As-is: this unit of conversion from L to Kg
is done manually using ASTM table
based on density , temperature, etc. and
users need to input the actual PGI weight
during GI.
Relate to CTRM -1213
Update from E2E session on 09 Oct: Users want the conversion to be done by system; users will input the necessary paramters (eg. temperatures, density) and system will automatically do the conversion based on the ASTM tables (ASTM 54/54B 53, 56) High Medium Gap Add Kg and liters field in LDC to be manually updated and provided by users. Enhancement. ACM- 1173 Delivery Planning Delivery Date Ability to set scheduled range date for delivery planning. Delivery dates should be within shipping period mentioned in the contract. High Low Fit Exist in Standard Functionality, can set the shipping date range in Nomination ACM- 1174 Delivery Planning, Goods Movement & Quality Capture Transportation Types Ability to accommodate integration to Logistic for all transportation types for delivery planning (Land, Ocean, Multi- moda)
Note for multi-moda: a lot of trucks (number can reach to hundreds) can be used to fill 1 vessel / 1 vessel unload to many trucks (hundreds) High Low Gap Critical gap based on ACM-TM integration solution
--- 第152页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 152 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
ACM-
1175
Goods
Movement &
Quality
Capture
Goods
Movement
Ability to capture GI/GR when there is no
weighbridge integration, eg.
- for ocean deliveries
- jual-beli dalam satu tangki - buy and
sell in one tank without physical goods
movement (3rd party, intercompany)
*) For intercompany jual-beli dalam
satu tangki, since load and unload
quantity is the same, possible to
automate unload event once load event
is created.
High
Medium
Gap
Implement API. Standard
APIs will be provided with
mapping to all the custom
field
ACM-
1176
Goods
Movement &
Quality
Capture
Full / Partial
Goods Reject &
Return
Ability to capture full / partial reject or
returns process including the applicable
return accounting posting (eg. reverse
GI/GR). This includes "Tukar Guling"
(similar goods swap)
- As-is for goods reject: customer reject
goods once arrival at customer location
because quality does not meet
expectations, hence no billing to
customer yet.
partial reject: reverse/cancel GI qty, GI qty that customer accept and GR rejected qty to penerimaan lain-lain full reject: reverse/cancel GI qty, if there are any gain/loss, gain/loss tanki with remarks. if loss qty exceed tolerance, will be charged to transporter. - As-is for goods return (very rare case):
goods arrival at customer location, kept in
customer tank, then goods are returned
to GAR after several days. Hence. billing
to customer is done.
High Medium Fit Exist in Standard Functionality.
Use return order to capture the returned product from customer (not using GI reversal), with goods movement type to a spesific restricted inventory. Option 1: Perform return and create new delivery against the same contract. (can see if returns have happened) Option 2: Perform LDC correction (reversal - reverse outbound delivery, goods movement, etc.) and generation of new documents, and then continue with settlement. (cannot see if there are any returns)
--- 第153页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 153 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1203 Contract Capture & Approval, Delivery Planning Carry Over Contract Notes to Nominations Ability to carry over Contract notes with long text strings to be shown in Nominations High High Gap Enhancement in nomination / nomination form output ACM- 1204 Contract Capture & Approval, Delivery Planning, Settlements Creation & Approval Product Additional Notes in Contract Ability to add Product additional notes, that need to be carry over until delivery order fulfillment & billing. High High Gap Enhancement in nomination to copy the information from the contract ACM- 1247
PO Hub tracebility Ability to link PO source and PO Hub to know the PO landed price. In PO Hub case, there's currently a need to trace back the PO hub transactions to customer to the original purchase PO
relate to: TNL-253, TNL-270, TNL-296 High High Gap Form Solution ACM- 1249 Delivery Planning Auto populate Nominations based on Contract Ability to draft/auto populate delivery planning information (e.g. Nominations) based on the Contract information: Plant Locations, ShipTo, Delivery Period, etc. after contract approval Low Medium Fit
Default fields such as material, commodity is automitcally populated. In nomination, need to mention scheduled date & quantity, optionalities. ACM- 1250 Delivery Planning Validate against Contract Tolerance in Sales Order Add validations to ensure that Delivery Planning Quantity does not exceed the Contract Quantity + Tolerance and re- validate after Contract Amendment.
Contract tolerance qty must be align with WB Tolerance qty (Upstream requirement) High Medium Fit Exist in Standard Functionality
--- 第154页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 154 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1251 Goods Movement & Quality Capture Auto create Gain/Loss Journal Auto create Journal of Gain/Loss in transit based on the Incoterm, e.g. - For purchase incoterm Origin, discrepancy between GR in Transit vs Qty received in WB buyer, posted as gain/loss in buyer side. - For sales incoterm Destination, discrepancy between GI in Transit vs Qty received in WB seller, posted as gain/loss in seller side . High Medium Fit Exist in Standard Functionality ACM- 1256 Prepayment Management, Goods Movement & Quality Capture Local Purchase - Option to do GR Before Prepayment Ability to do GR prior to Prepayment (ex. In some Purchase scenarios, some longstanding vendors want to push items into Sinarmas before prepayment has been completed) Medium High Gap Prepayments , enhancement needed to based on req. - Create Contract - Prepayments Request - Contract Approval - Checkbox: Release for Settlement - Prepayment Request Posting (KDD topic: Noted Items vs ABD) - Checkbox : Payment Received/ Payment Made (when payment has been made/ received) - LDC (for GI/GR posting) Use Manual workaround or custom logic required to automate this. ACM- 1257 Delivery Planning Local Sales - Prevent GI Before Prepayment and Nomination Ability to prevent GI for sales scenario, prior to Prepayment Completion & Nomination Confirmation. High High Gap Don't check the payment received if prepayment incoming has not been done. Standard check is during LDC. Block Nomination before
--- 第155页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 155 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions prepayment received will require enhancement. ACM- 1259
Export Admin Documents Ability to Print Shipping Instruction (SI), Packing List (PL),Appointment Letter (AL) together as combined docs with same input date and running document number
Relate to: CTRM-XXX
High
High
Gap
Forms, enhancement for
generating running
document number
ACM-
1260
Delivery
Planning
Export Admin
Documents
Ability to have flexibilty of adding the
documents date while printing without
going through MDG approvals
Relate to CTRM-1259
Medium
High
Fit
Output Forms
ACM-
1261
Delivery
Planning
Export Admin
Documents
Ability to have flexibility of adding Vessel
name into system (as dropdown list)
without going through MDG approvals for
re-use and printing purpose
Relate to CTRM-1259
High
High
Gap
Standard Functionality:
Vessel ID/ name is there
as free text.
Search help need to be
added (dropdown list)
ACM-
1275
Goods
Movement &
Quality
Capture
Batch Details
Traceability
Ability to capture product batch details
during goods movement (GI/GR) for
traceability purposes
1. Purchase GR - input batch according
to the policy ruling
2. Sales GI - need to be able to
automatically select batches based on
certain rules (e.g. FIFO or FEFO), or
select multiple batch manually (e.g. for
packed products), select based on
minimum shelf life
3. Intercompany transaction:
- GI one batch, GR one batch (1 to 1)
- GI one batch, GR one batch with
different naming (1 to 1')
- GI multiple batch, GR one batch (many
to 1)
- GI one batch, GR no batch (1 to none)
High
High
Gap
Enhancement to trace
batch
KDD topic for batch
traceability
--- 第156页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 156 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
Refer to e-mail from 02 July "Batch Split Requirement"
for EWM relevant materials - batch
information will be fetched from EWM
order to LDC
ACM-
1287
Goods
Movement &
Quality
Capture
Goods
Movement &
Quality for
standard
incoterms
Ability to capture all goods movement
(GI/GR) details (quantity, quality, sloc,
batch, etc.) for standard incoterms (eg.
FCO/LCO/FOB/CIF/DAP, etc.)
High
Medium
Fit
Exist in Standard
Functionality;
Incoterm tells when title
transfer happens.
Governing weight is tied
to billing.
ACM-
1288
Goods
Movement &
Quality
Capture
Goods
Movement &
Quality for
special
incoterms
Ability to capture all goods movement
(GI/GR) details (quantity, quality, sloc,
batch,etc.) for special incoterms
eg.
1. Weightbase and/or grade is different
compared to incoterm title transfer
2. Based on contract terms, governing
weight and grade is from Origin -> but
different points, eg.
Governing weight is from Origin (Vessel)
- meaning qty is inputted based on BL in
vessel [Shipped tank]
Governing grade is from Origin (Tank) -
meaning it is required to track the quality
per tank [Shore tank]
High
Medium
Fit
Exist in Standard
Functionality;
create LDC per tank,
need to track quantity per
tank if need to track
quality per tank
ACM-
1292
Delivery
Planning
Local Sales &
Export - Block
Delivery
Planning Prior to
DP Billing
Ability to block sales delivery planning if
incoming prepayment has not been
posted / DP Billing has not been
completed (SO cannot be created if
prepayment has not been received).
High
Medium
Fit
Exist in Standard
Functionality. There is a
checkbox for Prepayment
Received which will
allow/prevent
Nomination/SO from
being created
--- 第157页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 157 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1300 Goods Movement & Quality Capture Integration with QM: Push Delivery Info Ability to integrate with QM to push delivery information needed for Certificate of Analysis such as: - No Delivery - Vessel / truck number - Batch (barang yang dibawa di truck tsb) - Quality info Refer to email on 3 Jul : Downstream Indonesia CoA Template - Fields Required
Relate to CTRM-1301
Medium
High
Gap
Standard APIs are
provided; QM and ACM
interface
ACM-
1305
Goods
Movement &
Quality
Capture
Documents
Printout
Ability to generate, save and print out
documents
(as-is documents: contract, PO, SO, DO)
High
High
Gap
Form Output
ACM-
1306
Goods
Movement &
Quality
Capture
Sales -
Operations
Documents
Ability to generate document (as-is:
Sales/Delivery Order/E-mail) to inform
Operations on:
Material, Quantity, Quality, Delivery
Period, Incoterms, Plant locations,
Certifications, Extra Remarks on
packaging/accessories etc.
High
High
Gap
Form Output
ACM-
1307
Delivery
Planning
Logistics
Documents
Ability to generate, save and print
documents for delivery:
- Land (SPK,IPB, Delivery Order (Surat
Jalan))
- Sea (Shipping Instruction, Vessel
Nomination)
relate to: TNL-058, TNL-074, TNL-075, TNL-077, TNL-078, TNL-261 Medium High Gap Forms to be triggered at Order/nomination for the operations team .Nomination solution. ACM- 1308 Goods Movement & Third Party - Not Mandatory For Third Party transactions, Load and Unload events are not mandatory according to incoterm and governing High High Fit This is the designed behavior of ACM
--- 第158页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 158 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
Quality
Capture
Load and
Unload Events
weight & grades.
eg. Purchase --> Incoterm, Governing
weight & grades: Destination, Load Event
is not mandatory
Sales --> Incoterm, Governing weight &
grades: Origin, Unload Event is not
mandatory
ACM-
1309
Goods
Movement &
Quality
Capture
Intercompany -
Mandatory Load
and Unload
Events
For intercompany transactions, need to
make load and unload events mandatory.
eg. US --> DS -- (GR/GI in transit with
Inventory)
- Incoterm: Origin. Governing weight &
grades: Origin
US GI based on Load event. Billing
based on Load Event. DS GR based on
GR in transit. DS inventory updated
based on Unload Event, with gain/loss (if
any).
- Incoterm: Destination. Governing weight
& grades: Destination
US GI in transit based on Load Event. DS
GR based on inventory or Unload Event /
US GI gain/loss. Billing based on Unload
Event
High
High
Fit
This is the designed
behavior of ACM
ACM-
1311
Delivery
Planning,
Goods
Movement &
Quality
Capture
Load and
Unload Events
Ability to map multiple load events to 1
unload event, and vice versa, eg.
- Intercompany US to DS: 3 tanks from
US (load event) with different qty & qlty,
combined into 1 shipment (unload event).
- for multi-moda: 1 vessel (load event) to
split and unload to many trucks (unload
event) [truck-losing]
High
High
Gap
1:1 mapping between
events is available in
LDC. Need go understand
how TM manages multi
modal scenario.
1 LDC can have only 1
load & 1 unload event,
need to break the
transaction into 2 part
(combine with
Intracompany STO)
--- 第159页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 159 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1312 Delivery Planning Integration with satellite systems systems (Quantity, Quality) Ability to integrate with existing satellite systems for quantity and quality details and ensure any changes in SAP ACM (Contract/Nomination) will be reflected to the satellite systems - Upstream: Currently only GR is integrated with WB, GI still not integrate with SAP (OTB-301), LIS - DSI Bulking non-refinery & Warehouse: WB Smart, COPS - DSI Refinery: WB Smart, iLOGS, JIMS, LIMS - Soci: WB managed by Internal IT (different with US/DS system), Quality Window High High Gap ACM offers APIs to integrate with 3rd party systems ACM- 1313 Goods Movement & Quality Capture Goods Movement & Quality for special incoterms with tolerance Ability to capture all goods movement (GI/GR) details (quantity, quality, sloc, batch, etc.) and compare tolerance between quantity from seller vs. quantity received by buyer eg. compare quantity from seller's weighbridge must be within tolerance of 0.3% with quantity received on buyer's weighbridge Low High Gap Currently there is no validation at LDC if there is difference in Load and Unload event weights. Enhancement needed based on business expectations If any action is required if the qtty change is greater than 0.3% Separate report can also be created to inform about the variances in load & unload event weights for further action ACM- 1314 Delivery Planning Goods Movement Only for Intracompany (No Buy/Sell) Ability to capture all goods movement (GI/GR) details (quantity, quality, sloc, batch, etc.) without any buy/sell transaction eg. movement from one Sloc to another High High Fit Non CAS STO allows transfer within slocs of same company code. KDD Topics: ACM Product Scope, whether STO will be in ACM/ MM
--- 第160页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 160 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions under the same company code As-is: PO STO ACM- 1315 Goods Movement & Quality Capture Approval Goods Movement Ability to add approval workflow when goods movement data is not automatically integrated to system (manually entered/ upload)
Relate to: CTRM-1175 Low Medium Fit Roles and Authorizations to execute LDC will provide the desired results ACM- 1316 Goods Movement & Quality Capture One Delivery for Multiple Contracts / PO / SO Ability to split 1 delivery (truck/vessel) to fulfill multiple contracts/PO/SO High Medium Fit Application split allows splitting 1 delivery across multiple contracts ACM- 1317 Goods Movement & Quality Capture Sales - Bonded Zone AJU Number for GI Ability to input AJU number into each GI for sales delivery from Bonded Zone
Relate to CTRM-1041 High Medium Gap AJU field to be added in LDC and becomes madatory for Bonded scenario. Custom field ACM- 1318 Goods Movement & Quality Capture Export - Multiple BL number to 1 LDC Ability to link multiple BLs to 1 LDC (eg. customer request to split BLs from 1 shipment for 1 contract) - BL number is to be added in invoice to customer Medium Medium Gap Enhancement for a custom table can be added in LDC to show the quantity and BL number for a delivery . Ideally , recommendation is to have 1 BL per LDC ACM- 1319 Goods Movement & Quality Capture Process and Track Costs from Transporter Ability to capture additional costs related to goods return process (if any, eg. demurrage/truck overnight costs).
As-Is process differentiated between reject & return process due to quality issues: - Bulk & semi bulk products = Reject process = cancel the GI (reversal GI), can be full or partial qty - Branded = Return process, has billing/ tax implication and goods might not Medium Medium Fit A relevant fee type can be added at the settlement for returns scenario.
--- 第161页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 161 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions always be returned (e.g. broken packaging, oil already spilled)
relate to: TNL-259, TNL-288 ACM- 1330
LC and Prepayment against Available Credit Ability to have letters of credit and prepayments included in the credit limit check in ACM, but not for parental guarantees (although still recorded and tracked). There was a customer who has ToP for L/C and open account. Report for remaining receivable (AR Aging Report that has been settled with the prepayments)
Rajesh to include SAP while discussing with user High
Gap
Need to check what open
accout means, part of
KDD discussion for credit
check
ACM-
1338
Goods
Movement &
Quality
Capture
SO/ PO Type for
ACM
ACM should have different Order Type
for both SO & PO compared to standard
SD/MM document. This is to differentiate
ACM documents from non-ACM docs.
And also to differentiate when there's
enhancement required only for ACM
High
Medium
Fit
ACM need to config a
different order type from
standard SD (OR).
ACM-
1339
Goods
Movement &
Quality
Capture
Gain/Loss
Movement
Ability to post gain/loss movement when
load and unload quantity is different
eg. for Purchase, incoterm, governing
weight: origin,
if there is a Loss --> scrap movement, as
expense
Current solution:
1) Downstream Bulk - custom program to
auto GR/GI for the "loss in transit"
2) Upstream - GI Loss from temporary
storage location
[27 May - I2C] Need to enhance system High High GAP Movement types to be configured and mapped for LDC scenarios cosidering the Gain/loss based on the title transfer.
--- 第162页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 162 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions to avoid manual adjustment due to error POD. Ensure POD reversal can automatically posted when Billing reversal is posted
Relate to CTRM-1251 ACM- 1341
Make to Order
Processing
Ability to trigger production order based
on sales order (Make to Order).
As-Is in Sales Order, user change item
category to MTO (Make to Order) to
trigger the production order and become
a special stock reserved to fulfill that
order - SOCIMAS only
High
Medium
Gap
S/4 - if the order is
required to be triggered
from SO
ACM - If Order is to be
triggered in LDC based
on any logic or condition.
Need more info.
ACM-
1348
Goods
Movement &
Quality
Capture
Last Shipment
Information
OTB-274:
Ability to integrate SAP and WB during
contract termination. WB should have
interface with SAP on the last shipment
information upon contract completion /
rejection.
Action in SAP is to close Contract / Sales
Order
High
High
Fit
WB Integration with LDC
is part of integration while
auto closure of contracts
based on the consumed
quantity can be done via
batch job.
LDC cannot be created
for contract with zero qty
to be fulfilled.
ACM-
1349
Goods
Movement &
Quality
Capture
Integration with
Weighbridge
OTB-287:
Need to have integration between WB
and SAP for GI Reversal.
SAP is expected to reverse the GI and
POD (if applicable) based on WB ticket
reversal.
Medium
High
Fit
LDC correction allows
reversals of GM and it
can be triggered from the
WB.
ACM-
1350
Goods
Movement &
Quality
Capture
Outbound
delivery quality
spesification
Ability to connect with QM master data to
capture the quality grade spec (MSDS -
Master Safety Data Sheet/ RPS - for
Oleo, CP grade data for DSI). e.g. during
loading outbound delivery, need to check
the quality analysis details from QM
Medium
High
Fit
QM integration will update
the analysis and quality
details in the LDC for any
delivery.
--- 第163页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 163 of 167
Req.
No.
Process
Level 3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
ACM-
1403
Goods
Movement &
Quality
Capture
Automatic
Gain/Loss
Posting for
Transit
Ability to ensure automatic posting of the
correct gain/loss for inventory in-transit.
e.g. for Sales Transaction posting with
Incoterm Destination, should ensure that
the Goods Issue Quantity + Gain/Loss
Quantity = Billing Quantity.
(e.g. Currently the POD Error is fixed via
T-Code: MBST/ MB1A, MB1C)
High
Gap Enhancement as per GAR's requirement. Based on the scenarios, few of the Gain/Loss postings deviate from standard and require enhancement. ACM- 1404 Goods Movement & Quality Capture Correct "Created By" in LDC Posting Ability to ensure that the accounting postings generated from LDC process assigned the correct person for "Created by" field. (e.g. Operations PIC that will input the LDC details will be the "Created by" PIC for the LDC Accounting Postings)
Concern is because in As-Is process, the POD posting is done by Back Office Sales based on the POD details from the operation team (???) - confirm with Vienna
14/10 : [WW] For Incoterm = Destination, since the gain/loss posting is triggered together with revenue recognition, the posting "Created By" is showing as Back Office, while actually this should be the responsibility of Logistic team who perform the POD/ Unload Event. Low
Fit SAP ACM Standard Behavior. PIC of the postings will always refer to the one responsible for LDC. ACM- 1414 Delivery Planning New Scenario Biodiesel Ability to accommodate a Biodiesel scenario where SMART buys from SBE with FOB Incoterm. But SMART directly delivers this shipment to customer which should be considered like any other Biodiesel Transactions (can claim BPDP as well). This is like a backstop transaction High
Fit Back-to-Back Pegging
--- 第164页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 164 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
note(CH) : there will be 2 contracts
contract #1 : SMART Sell to Customer
contract #2 : SBE Sell to SMART
(intercompany), ship to customer
ACM-
1417
Goods
Movement &
Quality
Capture
Contract
Reference Field
for Debit/Credit
Note
Ability to have a contract reference field
in debit/credit memo creation form in FI
module to be linked to the contract (this
would allow debit/credit memo created in
FI to be seen in document flow view).
Medium
Gap Enhancement to link and show at DocFlow ACM- 1422 Delivery Planning Back to back Sales & Purchase scenario Ability to capture back to back sales & purchase scenario, in example:
Contract 1: Upstream (GBE) sales to customer 3rd party Contract 2: Upstream (GBE) purchase from intercompany Upstream (Mill), but Mill need to send directly to the 3rd party customer in Contract 1. This 2 contract need to be linked together as a back-to-back transaction.
Relate to CTRM-1404 High
Fit ACM Back-to-back Pegging Scenario ACM- 1423 Goods Movement & Quality Capture Freight Cost linked to contract * For purchase scenario (FOB), freight cost need to be settled into material valuation/inventory account (with reference to company code buyer). * For sales scenario (CIF), freight cost need to be settled into profitability analysis/COPA (with reference to company code seller). * For intercompany transaction that trigger STO-Intercompany based on above incoterms, system can automatically determined how the freight cost is settled (inventory for purchase High
Fit Product offering
--- 第165页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 165 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions and COPA for sales)
Refer to E-mail from Joseph (sent 24 Sept 2025) ACM- 1424 Delivery Planning Nomination Automation Automation of Nomination Creation from contract approval for ID Intercompany transactions (US-US, US-DSI, DSI-DSI, DSI-SOCI) Medium
Gap Enhancement at nomination level ACM- 1431 Report Reports needed by Logistics team Ability to generate reports needed by Transport Logistics team: 1. Incoming/Outgoing report by LDC by date (eg. daily/monthly) 2. Daily Outstanding Contract Report - captured in CTRM-1065 3. List of sales/purchase contracts by date (as-is: T-code ZRLG) High
Gap Custom Report ACM- 1435 Goods Movement & Quality Capture EUDR-related fields Ability to add EUDR-related fields (eg. Mill Name, Mill UML ID, EUDR Status) in Goods Movement level Note: EUDR planning to go-live by 2026 Medium
Gap
Custom Fields at LDC
ACM-
1439
Delivery
Planning
Default TM
relevant tick
Expected to have the TM relevant tick by
default in Nomination
Since majority transactions require
physical movement compared to buy-sell
in 1 tank
Low
Gap Enhancement for ticking logic ACM- 1440 Goods Movement & Quality Capture Automate creation of STO Nomination For commercial transaction with multi- modal, ability to automate the creation of STO based on ACM Nomination with reference to contract. example transactions: 1. Bulking --truck--> Port Origin -- barge--> Port Destination (PK from Demta Bulking) 2. Mill --truck--> Jetty --barge --vessel - Low
Gap Enhancement required as per the business logic
--- 第166页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 166 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions -> Port Destination (ship-to-ship CPO from Belian Mill ) ACM- 945 2.1.1 Nomination Scheduling (20% payment validation for exchange scenario) Exchange- Specific Settlement Ability to handle exchange-specific settlements: - Prevent scheduling until full payment (final 20%) received (Gap - validation groups at nomination but need to be customized)
This is related to ACM-207, ACM-943, ACM-944
(split)
ACM- 946 2.1.1 Nomination Scheduling (Import Delivery to China) Import Process Ability to support import process for soybeans: - Track port import → Delivery to Ningbo plants → Processing - Track import → Delivery to China plant or external warehouse - Support complete import process for Palm & Margarine
This is related to ACM-220
(split)
ACM- 949 2.1.1 Nomination Scheduling (GAR USA Transport Coordination Ability to enable transportation coorditation - Manage variable rates by origin/destination pairs - Schedule loading activities with
(split)
--- 第167页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Delivery Planning & Execution
File Name: S4_P2_ACM_PR05_Blueprint_Delivery Planning & Execution_V1.10 Status: Final
Page 167 of 167 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Loading terminals) terminals
This relates to ACM-290 ACM- 950 Report Logistics Reporting Ability to generate Month End Stock Reports for destination warehouses/tanks [Singapore]
This was split from ACM-367
(split)
ACM- 954 2.2.1 LDC & Goods Movement (overfill scenario) Flexible Delivery Tolerance Management Ability to deliver quantities beyond the set tolerance (overfill scenario), with delivery documents by linking to a different contract when exceeding tolerance.
This is related to ACM-388
(split)
ACM- 955 Form Generate Shipping Docs during Nomination Ability to generate shipping documents (SI/PL/AL) during the nomination phase by accessing the output file functionality
This was split from ACM-400
(split)
ACM- 962
Actual Quantity Capture & Adjustment The ability to capture and manage actualized quantities against planned amounts, including handling short shipment scenarios and applying quantity adjustments based on operational outcomes.
This was split from ACM-100
(split)
ACM- 967
Mass nomination creation Ability to do mass nomination creation and confimation through excel upload
(new)