S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10.pdf¶
来源: S4HANA ACM 蓝图 | 页数: 215 | 提取日期: 2026-06-25
--- 第1页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 1 of 215
Global Blueprint
Agricultural Contract Management Trade Capture
--- 第2页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 2 of 215 Document Information
Project Name S/4HANA Transformation Project Document Name S4_P2_ACM_PR05_Blueprint_Trade Capture Version 1.10
Revision History Version Effective Date Author Description/Reason for Change V0.01 15 October 2025 Sneha Sripadaraja China Margin Management V0.02 14 November 2025 Anshuman Awasthi & Sneha Sripadaraja Section 3.1 Pre-Trade Activities Section 3.2 Contract Capture & Approval Section 3.3 Prepayment Management V0.03 19 November 2025 Anshuman Awasthi & Sneha Sripadaraja Section 3.5 Fees & Expenses moved to Settlements & Invoicing Section 4 Country Specific Scenarios Additional context on Section 3.1.3 Solutioning V0.04 08 December 2025 Anshuman Awasthi & Sneha Sripadaraja
Section 4 Country Specific Scenarios Additional context on Section 3.2.3.8 Pricing Component Additional examples on Section 3.2.3.11 Contract Outputs V0.05 10 December 2025 Sneha Sripadaraja Post-DCW Revisions V0.06 17 December 2025 Anshuman Awasthi Hygiene Update V0.07 23 January 2026 Nabil Zaky Prepayment Reversal Scenario Update V0.08 25 February 2026 Nabil Zaky Draft Version for Signoff V0.09 06 April 2026 Nabil Zaky Updates based on Feedback V1.00 08 April 2026 Nyoman Arya Wardana Final version for sign off V1.10 02 June 2026 Anshuman Awasthi Mahak Raithatha Lakshya Kalita 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) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 3 of 215 TABLE OF CONTENTS 1 BUSINESS PROCESS OVERVIEW .......................................................................................... 5 1.1 High-Level Process Overview .............................................................................................................. 5 1.2 Business Process Hierarchy (BPH) and Its Applicable BU ................................................................11 2 KEY DESIGN DECISIONS ...................................................................................................... 12 2.1 Product Scoping & Segregation for Indonesia Upstream ...................................................................12 2.2 Product Scoping & Segregation for Indonesia Downstream ..............................................................13 2.3 Product Scoping & Segregation for Parm Kernel Shell (Cangkang) ..................................................14 2.4 Pre-Trade Workflow for Upstream Commercial Transactions ............................................................15 2.5 Intercompany Contract Capture & Approval .......................................................................................16 2.6 Margin Management for China BU .....................................................................................................17 2.7 GAR Global Business Models and Product Matrix for SG & Destination Offices ...............................17 3 SAP SOLUTION BLUEPRINT ................................................................................................. 18 3.1 Pre-Trade Activities ............................................................................................................................18 3.1.1 Highlighted Key Business Requirements .......................................................................................18 3.1.2 Business Process Flow ...................................................................................................................24 3.1.3 Solutioning ......................................................................................................................................30 3.2 Contract Capture & Approval ..............................................................................................................39 3.2.1 Highlighted Key Business Requirements .......................................................................................39 3.2.2 Business Process Flow ...................................................................................................................58 3.2.3 Solutioning ......................................................................................................................................65 3.3 Prepayment Management ..................................................................................................................81 3.3.1 Highlighted Key Business Requirements .......................................................................................81 3.3.2 Business Process Flow ...................................................................................................................87 3.3.3 Solutioning ......................................................................................................................................95 3.4 Contract Management ......................................................................................................................103 3.4.1 Highlighted Key Business Requirements .....................................................................................103 3.4.2 Business Process Flow .................................................................................................................110 3.4.3 Solutioning ....................................................................................................................................112 4 COUNTRY SPECIFIC SCENARIO ........................................................................................ 128 4.1 Indonesia Contracts ..........................................................................................................................128 4.1.1 Custom Fields at Contract ............................................................................................................128 4.1.2 OK to Pay – Not Ok to Pay ...........................................................................................................128 4.1.3 Custom Report for Prepayment/Advances paid ...........................................................................128 4.1.4 GAR ID Bonded Zone Requirements ...........................................................................................128 4.2 China Margin Management ..............................................................................................................130 4.2.1 Highlight Key Business Requirements .........................................................................................130 4.2.2 Business Process Flow .................................................................................................................132 4.2.3 Solutioning ....................................................................................................................................134 4.2.4 Special Prepayment Request Process .........................................................................................138 4.2.5 Custom Report - Customer Deposit Summary .............................................................................138 4.3 Pakistan Broker Contract ..................................................................................................................139 4.3.1 Broker Contract & ACM Contract (with actual BP) .......................................................................139
--- 第4页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 4 of 215 4.4 Singapore Contracts .........................................................................................................................139 4.4.1 Title Transfer .................................................................................................................................139 4.4.2 Singapore and Malaysia Sequence Number ................................................................................139 5 APPENDIX............................................................................................................................. 140 5.1 ACM Product Segregation for Indonesia ..........................................................................................140 5.2 GAR Global Business Models and Product Matrix ...........................................................................142 5.3 Requirement List ...............................................................................................................................143
--- 第5页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 5 of 215 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 Trade Capture group, outlining the key activities involved in the seamless execution of Commodity Trading & Risk Management.
Figure 1.1 - Business Process Hierarchy for CTRM
--- 第6页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 6 of 215 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
--- 第7页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 7 of 215 This document is created at L2 level, which is Trade Capture. Below diagram shows high level processes which are covered within Trade Capture.
Figure 1.3 - Business Process Flow for Trade Capture
Table 1.1 - Trade Capture Process Overview Process Description Trade Capture covers the activities of capturing the commodity contract data according to the areas below: • Pre-Trade Activities • Contract Capture & Approval • Prepayment Management • Contract Management Trade Capture enables users to create, modify, and monitor contracts efficiently, ensuring transparency and compliance throughout the process. Key features include contract creation, contract amendments, contract snapshots, and real-time visibility into contract status and performance.
Agricultural Contract Management (ACM) solution is designed to support this dynamic nature of contracts and streamline the entire contract lifecycle.
It offers flexibility, allowing for the inclusion of various details as they become available. Pricing negotiations can be outright or staggered (deferred) ensuring contracts remain adaptable throughout their lifecycle. SAP ACM emphasizes the collection of specific information necessary for processing contracts and subsequent steps, enabling efficient and accurate contract management.
Pre-Trade Activities ACM Master data is an important topic, and this module is crafted to provide a high level overview of some of the essential configurations needed in ACM. We have discount and premium quality schedules, tolerance schedules, optionality and standard master data such as materials and business partners.
--- 第8页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 8 of 215 Plant Locations and Inter/Intra-Company Transactions For inter and intra-company processes, such as shipping between plant/storage locations, it is necessary to set up plant locations as business partners. This enables the creation of inter or intra- company contracts to facilitate the movement of commodity.
Commodities and Materials ACM requires the setup of commodities as materials to track and manage inventory effectively. Soft commodities like soybeans may have different grades representing varying levels of quality. Material numbers can be assigned to each grade to facilitate inventory management as per the requirements.
Discounts, Premiums, Quality Schedule (DPQS) The DPQS schedule, an essential component of SAP Agricultural Contract Management (ACM), plays a critical role in calculating volume and value adjustments using the captured weight and quality characteristics of each load.
Tolerance Schedule The Tolerance Schedule on ACM Contract governs the allowable quantity that can be applied to a contract through one or more application documents. Type of tolerance schedule (Contract, Delivery Period, Per Delivery).
Optionalities Optionalities are a way to extend specific contract terms and allow for more possible values. They can be used to apply additional premiums or discounts based on certain contract terms.
Pricing Pricing in ACM is a highly complex process. The pricing requirements are driven based on whether or not the commodity is priced based on a futures market or not. Pricing needs to be flexible to allow the breakdown of the price into multiple components. To support the requirements ACM uses the Commodity Pricing Engine (CPE) to price the commodities. The futures price is defined through CPE configuration, BRF+ rules and Pricing Tables. There is various master data required for Pricing in ACM.
Contract Capture & Approval When creating a contract, it starts as a draft in draft mode, which doesn't affect risk reporting. This preliminary phase provides the opportunity to add or modify information later, facilitating a quick and efficient contract entry process. This allows industry partners to initiate contracts swiftly while ensuring accuracy and completeness before finalization.
After contract is created and saved in a draft status, contract then will be reviewed by the approver for approval purpose. Multiple contracts can be approved in one-shot by approver.
--- 第9页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 9 of 215 Prepayment Management Prepayment management in SAP Agricultural Contract Management (ACM) encompasses two key components: prepayment agreements and prepayment requests, which work together to support agricultural businesses in managing financial advances for farmers and trading partners.
Contract Management
Contract Management consist of actions to be taken to the contract after
contract is approved such as contract amendment, cancellation, or closure.
Key Changes
•
Pre-Trade Activities, Contract Capture & Approval
ACM for E2E Contract Capture Process for selected preliminary scope
Contract Types are created for:
1. ZC3P for 3rd Party Purchase Contract
2. ZC3S for 3rd Party Sales Contract
3. ZCIP for Intercompany Purchase Contract
4. ZCIS for Intercompany Sales Contract
5. ZSTO for Storage Agreement
6. ZCRP for Intracompany Purchase Contract
7. ZCRS for Intracompany Sales Contract
• Prepayment Noted Item The noted item approach in SAP Agricultural Contract Management (ACM) is a specialized accounting methodology that manages financial transactions without immediately updating account balances.
• Contract Management Supported process under Contract Management includes: 1. Contract Amendment a. Contract snapshot functionality setup b. Contract Amendment fields to include custom fields as well. c. Intermediary contract statuses i. Trader Approved requires final approval ii. Credit Check Required 2. Contract Cancellation Set-up of contract cancellation includes: a. Conditions for cancellation b. Authorizations for cancellation c. Any fee linked to contract cancellation process 3. Contract Closure Set-up of contract closure includes: a. Conditions for closure b. Authorizations for closure c. Automation of closure process
--- 第10页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 10 of 215 Table 1.2 - Margin Management for China Process Overview Process Description Margin Management for China GAR China operates with a unique deposit management system combining credit limits and rolling deposits. China team calculates and monitors sufficient prepaid lumpsum credit for each Customer to make sure GAR China is never under risk of Commodity pricing and/or payment defaults.
The solution process is combination of the ACM Prepayment Request
process and the FSCM Credit management process. The following is an
overview of the E2E process:
1. For every new customer there would be an initial Credit Update
provided by the insurance
2. For every contract Prepayment are expected before any deliveries are
done to the Customer
3. The advance amount received is maintained as a deposit for that
Customer
4. If there are any price fluctuations, there is a corresponding increase in
the Required deposit and fresh Prepayment Request is put in.
5. After each delivery the expected deposit is recalculated to make sure
the prepayment amount covers it.
6. Once all deliveries are done, Contract Settlement is done to net off the
prepayments received.
This supports processing of margins on Commodity Derivative transactions.
Different types of margins are processed:
•
Initial Margin
•
Variation Margin
•
Close Margin
Key Changes
In as-is, margin management process and the relevant reports were
managed manually by the GAR China Trader team.
In to-be, there will be a custom process integrated with the overall SAP ACM Contract Lifecycle. Also, there will be a custom report summarizing Customer Deposit details.
• Contract Types – In SAP ACM the same contract can have different pricing status. There is no need for separate Contracts/Contract Types for that • Integrated Solution – The advances received for the prepayment request are part of the Credit management process for Customers.
--- 第11页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 11 of 215 1.2 Business Process Hierarchy (BPH) and Its Applicable BU This document provides the solution for Trade Capture process group with all its processes and activity described in this section.
BPH L1 (Process Category) Commodity Trading & Risk Management BPH L2 (Process Group) Trade Capture Table 1.3 – Applicable BU for Trade Capture 3.1 Trade Capture ID SG CN IND PK EU LATAM US Oleo Sugar 3.1.1 Pre-Trade Activities
3.1.1.1 Maintain ACM Master Data Y Y Y Y Y Y Y Y Y Y
3.1.1.2 Maintain/ Upload Market Prices Y Y Y Y Y Y Y Y Y Y 3.1.2 Contract Capture & Approval
3.1.2.1 Create Agricultural Trading Contract Y Y Y Y Y Y Y Y Y Y
3.1.2.2 Approve Agricultural Trading Contract Y Y Y Y Y Y Y Y Y Y
3.1.2.3 Create Storage Agreements TBC N TBC TBC TBC TBC TBC TBC TBC TBC
3.1.2.4 Approve Storage Agreements TBC N TBC TBC TBC TBC TBC TBC TBC TBC 3.1.3 Prepayment Management
3.1.3.1 Maintain Prepayment Request at Contract Y Y Y Y Y Y Y Y Y Y
3.1.3.2 Maintain Prepayment Agreement Y TBC TBC TBC TBC TBC TBC TBC TBC TBC
3.1.3.3 Process Prepayment Request for Purchase Y Y Y Y Y Y Y Y Y Y
3.1.3.4 Process Prepayment Request for Sales Y Y Y Y Y Y Y Y Y Y 3.1.4 Contract Management
3.1.4.1 Contract Amendment Y Y Y Y Y Y Y Y Y Y
3.1.4.2 Contract Cancellation Y Y Y Y Y Y Y Y Y Y
3.1.4.3 Contract Closure Y Y Y Y Y Y Y Y Y Y 4 Country Specific
4.1 Margin Management for China
4.1.1 Maintain Deposit for China 3rd Party Sales N N Y N N N N N N N
TBC: subject to confirmation on whether respective applicable BU intends to adopt this
--- 第12页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 12 of 215
2 Key Design Decisions 2.1 Product Scoping & Segregation for Indonesia Upstream Decision Point Determine the solution on upstream business unit commercial transaction, especially on the commodity trading related product Impacted L3 ALL (E2E) Background Unstandard solution across business unit, e.g. •Buyer (Downstream) utilizes trading platform (CXC, to be replace 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
--- 第13页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 13 of 215 2.2 Product Scoping & Segregation for Indonesia Downstream 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
For further details please refer to Section 5.1 ACM Product Segregation for Indonesia.
--- 第14页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 14 of 215 2.3 Product Scoping & Segregation for Parm 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 transaction 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 are 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) • Standardize process for all PKS/ Cangkang transaction • Auto gain/loss posting to inventory and utilize DPQS parameter for quality settlement, for all transaction • Standard E2E flow in Coupa/MM for Central Procurement Team/ Buyer side. • Standard E2E flow 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 platform (Coupa & ACM). ACM will be use 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
--- 第15页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 15 of 215 2.4 Pre-Trade Workflow for Upstream Commercial Transactions Decision Point Replacement of KUBE functionality (Trade Capture workflow & match intercompany transaction) for Upstream Commercial Transaction Impacted L3 ALL L3 (E2E) Background Upstream currently utilize custom workflow (KUBE platform) for commodity commercial transaction, especially for Trade capture & intercompany transaction. KUBE integrate to SAP and use RPA to generate SC/SO. Leading Practice Standardize solution for E2E Trading transaction, including the Pre-Trade activities
Option 1 Option 2 Solution Description • US will capture & approve all contracts directly in SAP ACM, including intercompany transaction as the Lead Contract, with following pre-requisite: • DSI provide buyer plant mapping • Material Pricing calculation has been agreed with DSI Trader • As-Is control point from Back Office Upstream & DSI side by Trader will be accommodated in ACM Flow. • Build custom form & workflow to capture Pre-Trade Activities (refer to KUBE Sales Doc Creation design): • Sales/ Trader will input sales/ purchase request and approve in the Custom Form/ Workflow • Auto create contract in ACM • Back Office will review contract details & approve Contract in ACM Pros (Design rationale, benefit) • Standard solution for Pre-Trade activities across all intercompany transaction. • Lean Process steps. • UI/UX friendly, all required fields displayed in one screen. • Prior control/ check & balance in a separate screen/ workflow, before contracts are captured in SAP. • Cleaner data in SAP, only approved contracts are created in ACM. Cons (Drawbacks) • Concern from user due to no prior control/ check & balance (US – DSI, US Sales – I2C Back Office), before the contract is captured in SAP – need enhancement • UI/UX is less user-friendly than the current process, capturing contract from scratch requires filling out multiple tabs/ screens. • Extra Effort for Customization to build Pre-Trade Form/ workflow to connect with SAP ACM. Decision: This option is selected
--- 第16页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 16 of 215 2.5 Intercompany Contract Capture & Approval Decision Point Auto Approve Intercompany Contract (US-US, DSI-DSI, Backstop Contracts between DSI-SG and SG-DO), based on Lead Contract Approval Impacted L3 ALL L3 (E2E) Background ACM standard flow for intercompany contract approval: Approving Lead contract will trigger auto approval for the mirroring contract. As-Is process requires independent approval from both sides (Sales Contract/ Order & Purchase Order). Leading Practice Auto approval for both sides of Intercompany Contract.
Option 1 Option 2 Solution Description • Lead Contract for intercompany transaction can be triggered by any side (seller/ buyer). As per business agreement, lead contract will be triggered from Seller side. • For Intercompany contract within BU (US-US, DSI-DSI) and Backstop Contracts between DSI- SG and SG-DO, lead contract approval will automatically approve a mirroring contract, with notification to all the relevant parties. In case of disagreement, counterparty can reach out to the lead contract for contract amendment/cancellation • Hardcopy contract can be print out & signed independently as required. • As discussed with Tactical Tax Team, no concern from Tax POV on this auto approval in system (As-Is also not shown in system), if there's no impact on the output document • Independent sales & purchase approval in each system for each legal entity Pros (Design rationale, benefit) • Operational Efficiency, where both intercompany contracts can be automatically approved in one step.
Cons (Drawbacks) • Additional SOP required due to auto-integration with TMS in case of contract amendment/ cancellation. • Change management • Risk of document not reconciled between seller & purchase side • Need additional/ double effort for review & approval on both seller & buyer side • Minor Enhancement will be required Decision: This option is selected
--- 第17页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 17 of 215 2.6 Margin Management for China BU Decision Point Margin Management for China BU Impacted L3 Pre-Trade Activities, Contract Capture & Approval, Contract Management, Goods movement & Quality Capture, Prepayment Management, Settlement Creation, Adjustment & Approval Background • Deposit to be collected from Customers before delivery • Deposit amount recalculation for Price changes and after each delivery to be done to maintain minimum risk to GAR China • Commodity Settlement to refresh the Credit for the Customer Leading Practice SAP ACM Contracts with Prepayment Requests
Proposed Solution As-Is Solution Solution Description SAP ACM Contracts with Prepayment Requests and custom logic for margin recalculation • Manual calculations and independent FI Downpayment requests Pros (Design rationale, benefit) • Document Flow Traceability is by default • Prepayment Settlements and ACM settlements are integrated into the Credit process for the Customer • Custom solution tailored to business requirements
Cons
(Drawbacks)
• Additional project effort for custom
development
• Additional maintenance effort
• Manual effort and possibility for human
error
Decision:
This option is selected
2.7 GAR Global Business Models and Product Matrix for SG & Destination Offices Refer to Section 5.2 for GAR Global Business Models and Product Matrix. Discussion might be needed to fill in the gap (e.g. CN Marsho/Cooking Oil, Pakistan Toll In/Toll Out.
--- 第18页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 18 of 215
3
SAP Solution Blueprint
This section describes SAP solutions to address key business requirements in the Commodity Trading & Risk
Management process area.
3.1
Pre-Trade Activities
3.1.1
Highlighted Key Business Requirements
Req.
No
Business Requirement
Requirement
Analysis
(Fit/Gap)
Solution
ACM-
001
Configure all exchange-traded products for the
GAI Proprietary Trading Desk:
- CME Exchange Products: - Palm: CPO, SWAP
CPO - Crude & Refined Products: Gas oil -
Metals: COPPER, GOLD, SILVER - FX:
AUDUSD, CADUSD, EURO, EURUSD,
GBPUSD, JPYUSD - Agricultural: LUMBER,
LIVE CATTLE, LEAN HOG, FEEDER CATTLE
- CBOT Exchange Products: - Soy bean: SBM
(Futures & Options), SBO (Futures & Options),
SB (Futures & Options)
- ICE Exchange Products: - Crude & Refined
Products: BRENT, GAS OIL, WTI (Futures &
Options) - Agricultural: CANOLA, WHITE
SUGAR
- NYMEX Exchange Products: - Metals:
PLATINUM, PALLADIUM - Crude & Refined
Products: RBOB GASOLINE, HEATING OIL
- MDEX Exchange Products: - CPO (Futures &
Options)
- NYB Exchange Products: - FX: DOLLAR
INDEX - Sugar: SUGAR (Futures & Options)
- MGEX Exchange Products: - Grains: RW
WHEAT, MPLS WHEAT
- EPA Exchange Products: - Grains: MILL
WHEAT, RAPESEED
- Swaps: - CIF Rotterdam CPKO - PKPG RBD
Olein - PKPG CPKO
Fit
CPE Master Data Setup
ACM-
002
Configure all products traded by GAI Trading
Lauric Profit Centre:
- Lauric Products: - Palm Kernel - Crude Palm
Kernel Oil - RBD Palm Kernel Olein - Palm
Kernel Expeller - RBD Palm Kernel Stearin -
RBD Palm Kernel Oil - Palm Kernel Fatty Acid
Distillate - Hydrogenated Palm Kernel Oil -
Hydrogenated Palm Kernel Olein -
Hydrogenated Palm Kernel Stearin
- Grain Products: - Cochin - Crude Coconut Oil
(CCNO) - Sunflower Oil
Fit
Material Master - Part of
Initial Setup
ACM-
003
Configure all products traded by GAI Trading
Palm Profit Centre:
- Palm Products: - Crude Palm Oil - Refined
Bleached Deodorized Crude Palm Oil - Palm
Fatty Acid Distillate - Refined Bleached
Deodorized Olein - Refined Bleached
Deodorized Stearin
Fit
Material Master - Part of
Initial Setup
--- 第19页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 19 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 004 Configure all products traded by GAI Trading Beans Profit Centre: - Soybean Products: - Soybeans - Soybean Oil - Soybean Meal Fit Material Master - Part of Initial Setup ACM- 005 Configure all products traded by Indonesia Profit Centre: - Biodiesel Products: - FAME - Crude Glycerine - Fatty Matter - USP Glycerine - Yellow Glycerine - Crude Biodiesel Fit Material Master - Part of Initial Setup ACM- 006 Configure all products traded by GAR China Business Unit and China Desk: - Physical Products: - Soybean - Soybean Oil - Soybean Meal - Exchange-Traded Products (via China Desk): - CBOT: SBM, SBO, SB (Futures & Options) - DCE: RBDOL, SBM, SBO - EPA: MILL WHEAT, RAPESEED - ICE: BRENT, GAS OIL, WTI, CANOLA, WHITE SUGAR - MGEX: RW WHEAT, MPLS WHEAT - NYB: DOLLAR INDEX, SUGAR (Futures & Options) - NYMEX: PLATINUM, PALLADIUM, RBOB GASOLINE, HEATING OIL Fit Material Master - Part of Initial Setup ACM- 050 Ability to track flagged/blacklisted customer or vendor (due to failing to meet contractual obligations) Gap Part of MDM & FSCM; The blacklisted items can be configured, e.g., at counterparty level ACM- 065 Ability to create and maintain forward price curves: - Derive local price curves from international forward curves - Assign location-based price curves to contract prices - Base curve assignments on product shipment origin - Apply specific price curves for different ports/regions (e.g., Belawan for Indonesian ports) - Support various term structures (daily, weekly, monthly) Fit Forward price curves is through price upload at ACM. FX rate is through TRM.
VM: Addressed by Market Data Management ACM- 070 Ability to create custom and composite indices: - Support in-house indices - Manage composite indices for in-scope products - Link indices to trading locations - Support GAI's weekly base price publishing - Provide reference for destination offices Gap Baseline Configuration for CTE Setup.
VM: Combination of SAP Benchmark feature and custom development ACM- 088 Ability to configure core master data: Holiday Schedules: - Upload holiday schedules from pre-defined sources - Set up holiday schedules for exchanges and markets: * SG, ID, CN, MY Federal Public Holidays * NY Bank Holiday * Exchange holidays (CME Group, ICE Europe, EURONET, Fit Basic Configuration
--- 第20页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 20 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ICE US, etc.) Localization Settings: - Configure different number formats (comma/dot separation) - Support different date formats (DDMM or MMDD) Currency Setup: - Configure currencies traded by GAI: * Primary: USD, EUR, MYR, CNY, CNH, IDR, INR, PKR, SGD * Additional: JPY, GBP, CHF, AED, CAD UOM Configuration: - Set up Units of Measure: * BBL, Metric Ton, KG, Bushel, Pounds * Short Ton, Mounds (37.324kg), Litres, Kilolitres ACM- 089 Ability to set up business organization structure - Model existing business structure - Configure offices, legal entities, and profit centers - Maintain strategy and sub-strategy relationships - Assign specific sub-strategies to strategies - Ability to distinguish plant titip timbun, location, company Gap Basic Configuration ACM- 090 Ability to manage counterparty (business partner) information: - Capture customer and supplier information - Store addresses and contacts for trade entry, confirmation, invoices - Link counterparty groups to individual counterparties - Flag counterparties as 'Vendor' (Buys) or 'Customer' (Sells) - Filter counterparty pick lists based on transaction type - Display counterparty long names in pick lists - Ability to distinguish Counterparty for 3rd/Upstream/Affiliates Gap Custom Field ACM- 093 Ability to manage product information: - Configure byproducts: * Soy hull * SBN Oilstock * Soapstock * Lecithin - Configure palm products: * RBD Palm Olein * Margarine Shortening * PFAD - Configure grain products: * Rapeseed * Rapeseed Oil * Rapeseed Meal - Setup DCE Exchange products: * DCE - CORN - Create new product data Gap Custom Field ACM- 103 Ability to configure system security: - Implement security groups aligned with functional groups - Support different access levels (manager vs. executive) - Cover Trading, Trade Support, Contract, Risk, Operations, etc. Gap Security Roles and Authorization
--- 第21页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 21 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution - Lock down SAP-interfaced counterparty data - Allow editing of non-SAP fields ACM- 120 Ability to manage contract pricing components and optionality, including: - Receive market-based price updates - Calculate transfer pricing for Inter-Company sales - Handle FX exposure with settlement currency changes - Allocate futures and FX components to contracts - Support and differentiate contract types: - Unprice / Fixed Price - Basis and Fixing - Deferred Pricing - Futures (Contract) delivery - Support multiple entries per dimension - Specify premium/discount rates - Support custom UOM/currency - Automate flat price settlement adjustments - Specify hierarchy of payment terms for purchases and sales - Capture additional deliveries beyond contractual quantity at renegotiated price - Ability to capture special request from customer such as additives (vitamins, etc) - Can select the vitamins / other additives required and assign the appropriate cost center which will later be automatically captured in the expense section of the contract - Automate the creation of production transformation services for operations team to execute and proceed with goods movement (blending) Fit Optionality and pricing in ACM, need to discuss if any enhancement is req. ACM- 208 Ability to configure CBOT products: - Configure products traded by GAI Proprietary Trading Desk: * CBOT - CORN (Futures & Options) * CBOT - ETHANOL * CBOT - RW WHEAT * CBOT - WHEAT (Futures & Options) - Configure products traded by China Desk: * CBOT - CORN (Futures & Options) * CBOT - ETHANOL * CBOT - RW WHEAT * CBOT - WHEAT (Futures & Options) Fit DCS ID config ACM- 209 Ability to configure China products: - Configure ZCE Exchange Products traded by China Desk: * ZCE - RM * ZCE - RO * ZCE - RS Fit DCS ID config ACM- 320 Ability to define quality parameters: - Support tracking of quality parameters - Monitor FFA, M&I, and other cost factors - Track factors influencing outcome calculations - Track factors affecting settlement values - Support polarization and other quality measurements - Configure Material Specifications through DPQS functionality as part of the ACM Master Data Setup Fit DPQS Solution
--- 第22页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 22 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 525 Ability to configure and maintain incoterms within the system - For Singapore trades, CIF, FOB and all related incoterms are defined as Title Transfer at Origin. [DUPLICATE] ACM-1287
Gap
Incoterms can be created
and maintained as origin or
destination. To be enhanced
as per the request specific
for SG.
ACM-
629
Ability to update reference price using SAP
BADI functionality
Gap
SAP has a BADI to update
the reference price
ACM-
695
Ability to integrate with external data sources for
automatic daily reference price updates
Gap
Standard Interfaces are
available. Ex BRISKEN. Will
need custom develeopment
for the automation to be
mapped as per GAR specific
requirments.
ACM-
699
Ability to configure unlimited quality parameters
in SAP ACM
Fit
List of quality parameters are
maintained as Global
Characteristics in MM
module. Can be maintained
as many as the Business
needs. Can be grouped
accordingly under separate
DPQS Schedules.
ACM-
700
Ability to configure DPQS by commodity at
master data level with default quality parameters
Fit
ACM Baseline configuration
for DPQS
ACM-
723
Ability to load market prices from internal and
external sources via APIs or manual upload
Gap
Custom development would
be needed.
ACM-
745
Ability to handle multiple units of measure
including pounds, KG, MT with conversions
Fit
Standard ACM functionality
allows contract capture in
Packing unit of measure
instead of market unit of
measure.
UoM conversions to be maintained at Material Master ACM- 746 Ability to manage TORO/DUA authorization requirements and validity checks Gap Exact requirements and process to be detailed out later during the implementation and validations shall be custom development ACM- 792 Ability to configure and maintain multiple basis components (20+) in the pricing engine Fit Standard Solution Behavior ACM- 837 Ability to enable DPQS selectively for specific products (tolling) while disabling for others Fit DPQS schedule has material schedule that lists the materials to which the DPQS schedule is applicable ot. This can be utilized to maintain different set of rule for differnet type of mateirals ACM- 849 Ability to support multiple languages Fit SAP offering
--- 第23页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 23 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 850 Ability to record salesman who responsible for the sales process. Ability to record salesman name / trader responsible for the sales process and carried to A/R report (FBL5N)
Sales Admin who key in the contract might be
different with the real Salesman/ Trader
Gap
Custom Field at Contract
Level
ACM-
881
Ability to determine pricing procedure based on
incoterm in transaction (current ABAP
enhancement)
Gap
Retrofit of custom
ACM-
1067
Ability to add formulas inside market indices
Gap
Custom formulas require to
be added & created
ACM-
1115
Ability to associate specific market indices to
specific product/location
combinations e.g. associate a market index
showing the value of CPO at Lampung. These
market indices should default when the specified
product/location combination is selected on a
trade
Fit
Exist in Standard
Functionality. Creation of
DCS (Derivative Commodity
Structure) ID, part of CPE
setup
ACM-
1177
Ability to specify premium/discount rates
Fit
Exist in Standard
Functionality, DPQS
ACM-
1196
Ability to make sure DPQS will not have impact
on Financial Amount (default DPQS ranges to 0)
Fit
If the details are manually
entered then we can use the
free text, else we can do
enhancement as per the req
ACM-
1201
Ability to add commodity group (Palm, Lauric,
Biodiesel) in Contract Capture and Approval
based on Commodity Group
CH: will utilize Sales Division: TR = Trading Palm TP = Trading Lauric TB = Trading Biodiesel Fit Exist in Standard Functionality. MDG to maintain commodity group and assign material to the commodity groups. System can check material role and user role during approval process. ACM- 1405 Ability to have Standardized fundamental data between ACM & SAP S4 (eg. Material Desc, payment term, field name, price per UoM, etc) Fit Already drafted L4 for Maintain ACM Master Data and its separation between MDG. Will discuss the separation of master data with MDG.
--- 第24页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 24 of 215 3.1.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.1.2.1 Maintain ACM Master Data
Figure 3.1 - Maintain ACM Master Data
Table 3.1 - Maintain ACM Master Data
Process Steps
Prerequisite
Role
Transaction
Code/Fiori App ID
Description
Maintain DPQS
1.Material
master should
be created
(MDG)
2.Material
should be
extended
(MDG)
ACM Functional Maintain Value and Volume Schedules Create DPQS Characteristics
Example:
Moisture (%)
Free Fatty Acid (FFA) (%)
Iodine Value
Late Days
DPQS
Characteristics
are created
ACM Functional CL02/ Maintain Value and Volume Schedules Create DPQS Class
Example: YMC_PALM_OIL
--- 第25页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 25 of 215 Process Steps Prerequisite Role Transaction Code/Fiori App ID Description DPQS Characteristics are assign in the class
ACM Functional CT04/ Maintain Value and Volume Schedules Assign DPQS Class to Material Master DPQS Class is Assign to Material Master
ACM Functional Maintain Value and Volume Schedules Create Volume Schedule
Example: VOL_PALM KERNEL_02 Volume Schedule exists
ACM Functional Maintain Value and Volume Schedules Create Value Schedule
Example: VAL_PALM KERNEL_02 Tolerance Schedule NA
ACM Functional Maintain Tolerance Schedules Tolerance is the Master data and a prerequisite and mandatory field in trading contract
Example: TOL_+/-5% Valuation Point
NA ACM Functional Maintain Valuation Point Valuation point is the Master data and a prerequisite and is required for price determination
Example:
EXPORT.RBDOLN.BELAWA N/DUMAI
This is yet to be finalized during detailed design discussion.
Fees/ Expenses If GL Posting is required, then GL needs to be created first ACM Functional Maintain Fees/ Expenses Fees/Expenses is the Master data and can be used in ACM cycle
Example: HALF COST FEE
Refer to Fees/ Expense
Document for detailed
information.
Commodity
1.Material
master should
be created
(MDG)
ACM
Functional
/ACCGO/MAINT_MA
TNR
Linking material to commodity
Example:
--- 第26页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 26 of 215 Process Steps Prerequisite Role Transaction Code/Fiori App ID Description
PALM KERNEL CRUDE PALM OIL Purchase info records 1.Supplier 2.Material 3.Purchasing Org 4. Plant
ACM Functional ME11 When ACM creates follow‑on purchase orders via LDC, these POs will behave like normal MM POs and can consume info‑record data (price, texts, etc.).
Users will not be allowed to modify/edit back-end generated POs after LDC release process.
Example: 5300000013 – Supplier, Material, Purchasing Org, Plant combination Condition Record 1.Material 2.Valuation Point ACM Functional MEK1, VK11 Maintain condition record
Example: ACM Contract Price Condition Create Portfolio 1.Material 2.Plant
ACM Functional POFO31 Maintain Portfolio
Example: P6 - Shining Gold Business Partner NA MDG BP Business partner needs to be created. For example:
ACM Transacting BP (Contract Transacting Counterparty, can be Vendor/ Customer)
ACM Purchase Contract (follow standard MM) • Vendor • Ordering address • Invoicing party • Goods supplier
ACM Sales Contract (follow standard SD) • Sold‑to party • Ship‑to party • Bill‑to party • Payer
--- 第27页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 27 of 215 Process Steps Prerequisite Role Transaction Code/Fiori App ID Description
ACM I/C Contract (follow standard MM/SD Intercompany) • Internal customer (intercompany sold‑to party) • Intercompany bill‑to party • Intercompany payer • Intercompany vendor (on the purchasing side)
Apart from this, Broker can also be added as a business partner at contract Level. This information will be cascaded to subsequent documents by default. Inco Terms NA MDG BP Incoterm needs to be maintained in BP (Optional)
Payment Terms NA MDG BP Payment Terms needs to be maintained in BP (Optional)
Maintain Futures Price 1.Material 2.MIC 3.DCS ID
ACM Functional FDCS17 Maintain Futures Price
Example: Quotation Price – 4300 IDR/KG for a combination of Material, Market Identifier Code (MIC), Derivative Commodity Specification (DCS ID) on a given Price Date, Price Time, Price Type, MatKeyDate (Maturity Key Date) Maintain Basis Prices 1.Material 2.Basis ID 3.DCS ID
ACM Functional FDCS17B Maintain Basis Price
Example:
Quotation Price – 300 IDR/KG
for combination of Basis
Category, Basis Type on a
given Basis ID, Derivative
Commodity Specification
(DCS ID), Material, Market
Identifier Code (MIC), Price
Date, Price Type, Start/End
Date, MatKeyDate (Maturity
Key Date)
TSW Setup:
BP, Plant,
Storage
ACM
Functional
O4T0
Assign Value Schedule to
TSW
--- 第28页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 28 of 215 Process Steps Prerequisite Role Transaction Code/Fiori App ID Description Assign Value Schedule to TSW Location, Org. Data and DPQS should be there
TSW Setup: Maintain Transport Unit Assign Value Schedule to TSW should be done as prerequisite
ACM Functional O4T0 Maintain Transport Unit
Example: Trucks, Vessel, etc. TSW Setup: Maintain Transport System Maintain Transport Unit should be done as prerequisite ACM Functional O4T0 Maintain Transport System
Example: GAR-TS TSW Setup: Maintain Node Location Maintain Transport System should be done as prerequisite ACM Functional O4T0 Maintain Node Location
Example: Refer to Section 3.1.3.6 TSW Setup: Maintain Location Hierarchy Maintain Node Location should be done as prerequisite ACM Functional O4T0 Maintain Location Hierarchy TSW Setup: Maintain Partner Role Maintain Location Hierarchy should be done as prerequisite ACM Functional O4T0 Maintain Partner Role
Example: Supplier, Plant, Customer
--- 第29页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 29 of 215 3.1.2.2 Maintain/ Upload Market Price
Figure 3.2 - Maintain/ Upload Market Price Table 3.2 - Maintain/ Upload Market Price Process Steps Role Transaction Code/Fiori App ID Description Maintain basis prices Trader (ACM) FDCS17B Maintain location-based basis differentials (premium/discount) that reflect local cash price adjustments relative to the futures market, including primary (freight) and possibly secondary (quality, etc.) basis components.
Refer to 3.2.3.8 Pricing Component (FDCS17B) Maintain futures prices Trade Control (ACM) FDCS17 Maintain the market-linked futures price component used in pricing of hedge able commodities; serves as the core reference price from external futures markets that basis and other adjustments are added to.
Refer to 3.2.3.8 Pricing Component (FDCS17)
--- 第30页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 30 of 215 3.1.3 Solutioning 3.1.3.1 Agricultural Trading Contract (ACM) Master Data SAP Agricultural Contract Management (ACM) Master Data encompasses the foundational data objects and configurations required for commodity trading and agricultural contract management. This master data serves as the backbone for capturing, processing, and managing agricultural contracts throughout their lifecycle
SAP Agricultural Contract Management (ACM) Master Data includes but not limited to: Discount Premium Quality Schedules (DPQS), Tolerance Schedules, Commodities, Pricings, etc. The details of ACM Master Data Setup and Maintenance will be discussed in the detail design.
3.1.3.2 Maintain Discount Premium Quality Schedule (DPQS) The DPQS schedule, an essential component of SAP Agricultural Contract Management (ACM), plays a critical role in calculating volume and value adjustments using the captured weight and quality characteristics of each load.
The DPQS schedule consists of two parts: volume and value. The volume schedule, created initially, determines volume adjustments by flagging characteristics in the schedule to calculate adjustments based on gross weight or net weight.
The value schedule, the second part, is utilized during settlement to calculate discounts and premiums based on quality.
The DPQS schedule is applied and used at various stages. During contract capture, it can be assigned specifically to a contract. When a load is received, the volume schedule is used to determine quantity adjustments, and the adjusted quantity is then consumed against the contract. The DPQS schedule is also utilized during settlement, where both the volume and value schedules are used. The logistically adjusted quantity (LAQ), which includes the applied quantity from the volume schedule, is carried into the application document and used for settlement. The value schedule handles discounts and premiums to adjust the value accordingly.
Overall, the DPQS schedule provides a structured framework for managing discounts, premiums, and quality adjustments throughout the ACM process. It ensures accurate calculations of volume and value, facilitating efficient settlement operations. By leveraging actual weight and quality characteristics, the DPQS schedule enables effective management of diverse agricultural contracts.
--- 第31页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 31 of 215
Figure 3.3 - Maintain DPQS Schedule 3.1.3.3 Maintain Tolerance Schedule The Tolerance Schedule on an ACM Contract governs the allowable quantity that can be applied to a contract through one or more application documents. The type of tolerance schedule (Contract, Delivery Period, Per Delivery) determines how the allowable Overfill or Underfill quantity is calculated.
Figure 3.4 - Tolerance Schedule Diagram
When assigning the tolerance schedule, it is essential to create it as master data and then assign it to the contract.
During the assignment of the schedule, you must specify when the tolerance evaluation should occur. There are three options available: evaluating based on the last load, which applies to all line items of the contract and accumulates the effect; evaluating based on the delivery period, considering each line item individually and performing the evaluation when the last load is received for that specific line item; or evaluating on a per-delivery basis, where you define the allowable tolerance for each load. If the delivery method is utilized, it is necessary to provide the mean value per delivery to determine the tolerances for quantities exceeding or falling below this mean.
--- 第32页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 32 of 215
The tolerance schedule allows you to indicate how overfills and underfills should be handled. You can assign a percentage range, such as zero to % for overfills and zero to % for underfills. Alternatively, you can assign a specific quantity, allowing, for example, up to bushels for overfills and up to bushels for underfills. It is also possible to use a combination of both approaches.
Considering the timing of the evaluation is important. While overfills are automatically managed by the system, underfills require explicit instruction. In the application manual application works center, you can set the underfill indicator to trigger the evaluation for underfills. However, if the evaluation is performed on a per-delivery basis, both overfills and underfills are automatically handled by the system.
In case of underfill, Final Delivery Indicator has to be manually set before the creation of settlement.
Figure 3.5 - Maintain Tolerance Schedule Tolerance schedules are assigned per contract line item (Tolerances tab). The Tolerance Type controls how the tolerance rules are evaluated: • Per Delivery: tolerance is checked per individual load against the Expected Delivery Quantity of that line item. • Per Delivery Period: tolerance is checked on the total delivered quantity within the delivery period of each line item. • Per Contract: tolerance is checked on the total delivered quantity across all line items of the commodity within the contract For example, if total 200MT quantity is spread across Jan-Apr, contract line items can be maintained as: One Contract, One Line Item with Delivery period Jan-Apr with total 200 MT. In this case: • Using per-contract tolerance schedule means will check the last delivery on Apr to determine Overfill/ Underfill. • Using per-delivery period will be same as above since there is only one line item • Using per-delivery will check overfill/underfill per delivery itself. One Contract, Three Line Item with Delivery period Jan (100MT), Mar (75MT), Apr (25MT). In this case: • Using per-contract tolerance schedule means will check the last delivery on Apr to determine Overfill/ Underfill. • Using per-delivery period means will check the total quantity on each delivery period to determine Overfill/ Underfill. • Using per-delivery will check overfill/underfill per delivery itself
--- 第33页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 33 of 215 3.1.3.4 Commodities Commodities at SAP Agriculture Contract Management are the master data being used throughout the contract lifecycle itself. Commodities here are being map to product groups similar to MDG for reporting purposes. Each material code are then being mapped to commodity. Further detail are laid out on the Trade Control blueprint document.
Figure 3.6 - Commodity to Material Number Mapping
Figure 3.7 - Commodity Setup
--- 第34页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 34 of 215 3.1.3.5 Upload/Maintain Market Prices The pricing requirements for Agri Companies is driven based on whether the commodity is priced based on a futures market or not. Commodities that are futures driven are called “hedge able”, such as CPO, Soybeans, etc. Commodities that are not futures driven are called “non-hedge able”, such as Palm Kernel, FFB.
Pricing needs to be flexible to allow the breakdown of the price into multiple components, particularly for hedge able” commodities. For “hedge able”, Agri companies’ breakdown the price into a Futures” component and at least one or more Basis” component(s). “Non-hedge able” typically only needs one price component, which we handle as a Basis” component.
Regardless of which type, the pricing needs to be flexible in terms of when and how the commodity is priced in the contract.
It is not unusual in this industry to perform logistics prior to pricing all price components as well as carrying out invoicing bas ed on provisional or partial pricing. In addition to this, there is a need to be able to price multiple times against the same contract line item, hence there is a requirement to support multiple pricing lots per contract line item.
The FX (foreign exchange) requirement adds a further layer of complexity in that, if the contract currency is different from the futures market currency, then there is a need to capture provisional exchange rates as well as have the ability to “fix” the exchange rate on the pricing lot based on the agreement with the counterparty at any point in time. Also here too, there needs to be an ability to provisionally invoice based on provisional exchange rate as well as final invoice based on “fixed” exchange rate.
To support these requirements, ACM uses the Commodity Pricing Engine (CPE) to price both types of commodities.
--- 第35页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 35 of 215 Price Components The price is broken down into two component types: • Futures • Basis (one or more) Futures price can be automated through futures market interface or manually uploaded in FDSC17 as below.
Figure 3.8 - Maintain Futures Prices (FDCS17)
Basis price entry is manually entered by Basis ID based on DCS and key maturity date (example is for a primary basis) in FDCS17B.
Figure 3.9 - Maintain Basis Prices (FDCS17B)
--- 第36页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 36 of 215 3.1.3.6 TSW Location Naming Convention (Relevant to TM) To standardize Location maintenance, naming convention used as below rules similar to TM. For countries without TMS Implementation, standard SD configuration for Shipping Point is sufficient and will be used as there are no conflict of naming convention between ACM-TM.
Table 3.3 - TSW Location Naming Convention
Type of Location
Naming Convention
Business Partner
(Customer, Vendor, Carrier)
Align with BP Number
Shipping / Receiving Point
“SP_” +
3.1.3.7 Storage Location While the 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 storage location will default if it is specified in the nomination.
3.1.3.8 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.1.3.11 and 3.1.3.12 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.1.3.9 below) at load or unload and be applicable for trucks, vessel, etc. Details of LDC process are covered in Delivery Planning & Execution blueprint.
3.1.3.9 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.1.3.11 and 3.1.3.12 for LDC Applicability matrix based on Governing Weight + Governing Grades + Incoterm.
--- 第37页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 37 of 215
Figure 3.10 - Governing Weight & Analysis
--- 第38页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 38 of 215
3.1.3.10 Title Transfer
Title transfer defines clear understanding of when the transfer of ownership will occur. These decisions
will have implications for downstream document generation and goods movements at Load Data
Capture.
Figure 3.11 - 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.1.3.11 LDC Applicability Matrix for Inbound Scenario 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.4 - LDC Applicability Matrix for Inbound
3.1.3.12 LDC Applicability Matrix for Outbound Scenario Governing Weights and Grades: LDC Events Details - Outbound Scenario mapping as below table.
Table 3.6 - 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
--- 第39页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 39 of 215 3.2 Contract Capture & Approval 3.2.1 Highlighted Key Business Requirements Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 013 Ability to monitor credit line from banks -Clean Line (Fixed line, can only draw up to the limit. system needs to monitor both net and gross) Gap SAP can monitor credit line but cannot stop transactions when credit line is breached. For this, will need custom development ACM- 014 Ability to monitor credit line from banks -CSA Line (Based on MTM of specific trades - trades will be marked as CSA by trader) Gap SAP can monitor credit line but cannot stop transactions when credit line is breached. For this, will need custom development ACM- 024 Ability to save a deal to a draft status - so it does not go into position and exposure reporting, PnL, Credit and Risk monitoring
Relate to ACM-1195 Fit Contract Status ACM- 038 Configure contract confirmation capabilities for Pakistan operations: - Confirmation Management: - Sales Processing: * Manage sales confirmations * Track confirmations sent to Singapore * Support contract issuance process Gap Form Requirement - Status can be defined and configured ACM- 109 Ability to support physical trade capture: - Easy capture of physical buy and sell transactions with minimal keystrokes - Intuitive interface optimized for trader / local trader workflow - Standardized core templates across regions - Standardized field definitions and validation rules - Common reference data (products, locations, etc.) Fit LDC Workcenter ACM- 110 Ability to streamline trade entry process: - Physical Multi-trade Blotter (ACM has functionality to mass upload contract from excel - fit for purpose) - Ability to capture comments on deals (Picklist of predefined comment types) (at contract level ACM we can add "notes" on contracts) Gap Enhancement at contract level to ensure comments passed to LDC ACM- 111 Ability to categorize different types of trades: - Trade Classification & Differentiation: - Phys- Phys/Phys-Paper Differentiator: * Clear distinction between physical-physical and physical-paper trades * Visual indicators for different trade types - Trade Type Fields: * Priced/Unpriced/Provisional field at parcel level * Structured Trade Finance (STF) indicator field for position reporting Gap Enhancement to be done based on req ACM- 113 Ability to capture fundamental trade information across all trade types, including: Gap Enhancement to be done based on req
--- 第40页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 40 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution - Capture fundamental trade data: - Prices, product types, specifications - Contract date, incoterms - Payment terms with calculation of due dates (dates are only expected and delivery dates i.e. commodity periods and based on this, they can fetch the prices) - Generate unique system contract numbers at entity level (default) - Monitor new trades daily through system (default) - Save deals to draft status (exclude from position/exposure reporting, P&L, credit/risk monitoring) - Ability to allow deal entry only with approved counterparties - Attach customer PO during Trade Capture - Indicate/overwrite intended use - Indicate taxable/non-taxable contracts based on bonded/non-bonded locations (ID - enhancement at contract level) - Indicate deal type (Spot, Long Term Contract, Long Term Agreement) ACM- 114 Ability to capture and manage physical trade transactions, including: - Create detailed sales contracts with outright price terms - Capture fixed price CPO trade and allocate profit between internal entities - Link sales contracts to customers to purchase contracys from vendors / intercompany entities through Back to Back Scenarios - Create, validate, confirm and manage various physical trade types: - Standard physical trades - Backstop trades - GAI B2B trades with Destination Offices - Inter/intra-company trades - Staggered and outright contract trades - Unplanned deliveries - Priced and unpriced contracts - Hedge contracts for physical and paper positions - Capture SB trade on resell into China (internal Profit Centre) - Generate and manage SBO and SBM equivalents upon event date - Create backdated trades for purchases and sales - Merge and Split the Backstop quantity from the same or different contracts Gap LDC functionlaity, need more discussion ACM- 121 Ability to manage trade documentation and specialized attributes, including: - Process, verify, and manage trade data across formats - Coordinate trade sheet data with destination offices - Create, validate, and amend GAIM trade documentation - Manage regulatory compliance processes - Handle trade registration and contract Gap Enhancement for Non- Bonded/ Bonded solution
--- 第41页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 41 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution declarations to authorities - Ability to generate barcode in trade confirmation to be included with Sales Contract and PO for payment processing - Capture additional Indonesia input fields: - Broker Reference Codes - Sales Area Code (Bonded vs. Non-Bonded) - Commodity Specifications - Certifications (Health, RSPO, etc) - Trade Capture Notes with Long text string - Incoterm (ex. FOB, CIF, LCO, FCO) - Packaging Specification - Material Code - Packaging Code - Optional Add-on Accessories (ex. Palette, Heating Pad, etc) - Tolerance Level - Tax ID - Product Type (ex. Bulk, Semi-bulk) - Contractual Terms for Export (ex. PORAM, FOSFA, etc) - Terms of Payment (ex. 1x DP, 2x DP) - Location, Plant Code, Destination Location, Load Port, Destination Port - Support multiple Incoterms: FOB, CNF, CIF ACM- 122 Ability to capture open prices for future fixing: - Capture open price trades for later fixing - Support initial open price recording - Maintain contract history including original open price terms Fit ACM pricing ACM- 123 Ability to manage the price fixing process: - Fix prices for entire quantity or portions - Support partial quantity fixing - Allow multiple fixing events against a single contract - Track fixed versus unfixed quantities Fit ACM pricing ACM- 124 Ability to manage splits in price fixing: - Handle conflicts between trading splits and operational splits - Give precedence to trading splits for price fixing - Support reversal of operational splits when needed for price fixing - Maintain audit trail of split changes and reversals Fit ACM pricing ACM- 162 Ability to provide pre-trade visibility: - Display outstanding contracts before trade approval (part of FSCM credit management) - Show quantity, credit, AR overdue information (part of FSCM credit management) - Provide visibility for both purchases and sales (part of FSCM credit management) - Provide visibility into customer credit limits (part of FSCM credit management) - Show current usage levels (part of FSCM credit management) - Support local operational decision-making Gap Visibility will be part of FSCM, blocking trade execution is part of ACM based on visibility details ACM- 165 Ability to validate transactions against credit limits: - Integrate contract management with credit control - Provide real-time validation - Validate transactions against forward sales limits - Check during contract creation Gap Part of CIS Solution
--- 第42页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 42 of 215
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
- Compare against established counterparty limits
- Verify against approved trading thresholds
- Validate before committing to deliveries
ACM-
166
Ability to check credit during order management:
Perform credit checks based on SO when GI
precedes it (FSCM)
Maintain credit control even with altered process
flow (FSCM)
Automatic Block / warning during sales trade
capture due to overdue or overlimite (ACM)
Automatic Block / Warning for Purchase
Downpayment (ACM)
Gap
Part of CIS Solution
ACM-
170
Ability to manage credit-related notifications:
- Automatic notification to traders and counterparty
on block
- Automatic Block / warning during sales trade
capture due to overdue or overlimite (ACM)
Gap
Part of CIS Solution
ACM-
171
Ability to manage approval workflows:
- Support Proposed, Pending, New, and Validated
statuses
- Require Back Office (settlement) approval
- Require Trading (control) approval
Gap
Workflow to be setup
as per the requirement
ACM-
172
Ability to configure order types:
- Create various order types: * Sales orders *
Credit orders * Stock transfer orders
- Support diverse contract types * Include
complete logistics parameters * Enable optionality
execution * Track cancellations
- Have multiple Sales Orders in one contract, and
multiple delivery orders for each Sales Order
Fit
Standard Solution
Behavior
ACM-
188
Ability to manage contract templates:
- Long Form Contracts for Physical Trades: *
India, Bangladesh, Myanmar + Africa template *
Mediterranean template * China (English)
template * China (English+Mandarin) template *
Russia (English+Russian) template
- Common contract elements and standard
clauses
- Standard document types and templates
Fit
Contract Template
ACM-
191
Ability to monitor contract status:
- Follow up on outstanding sales contracts with
customers
- Comprehensive documentation of contract terms
including: * Quantity * Commodity * Transportation
mode * Pricing information
- Ability to price in the quantity and price on a
selective basis for physical contracts
Fit
Contract status
Approval
ACM-
239
Ability to manage multi-delivery contracts:
- Support sales to parent with delivery to multiple
child units
- Enable separate invoicing for each child unit
- Retain original contract number with subset
indicators
- Ability to amend port of loading / unloading
Gap
ACM supports multi
delivery model with
independent/ collective
billing - specific
number ranges is a
gap
--- 第43页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 43 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 242 Ability to track contract status: - Track outstanding contract summary information - View quantity, contract price, weighted average price - Monitor days outstanding compared to delivery date - Monitor open invoice - Ensure contract closure during month-end - Finalize and distribute to counterparties Gap Report to be developed - only if GAR wants to see all fields in one sigular report ACM- 287 Ability to manage dual-nature costs: - Handle provisional and actualized expenses - Support for items like Freight, Brokerage, Surveyor fees Fit Expense Management / Fees ACM- 294 Ability to display and post transaction details in accounting showing gross amount and payments received, while presenting zero billing amount on final invoices for fully prepaid transactions Gap Fit for ABD approach, Gap for noted item approach ACM- 377 Ability to configure additional fields in filtering criteria and apply multiple filter options for contracts Fit Fiori has the option to filter ACM- 381 Ability to navigate directly from the contract page to the nomination page or LDC page without exiting and searching again Fit Document flow ACM- 392 Ability to customize sales contract printouts to display location/port names instead of plant/tank information, with configurable dropdown lists for location fields and Trading Portfolio/Strategies, subject to establishing plant-to-port mapping logic Gap Contract Forms ACM- 394 Ability to set up contract optionality using templates that automatically populate optionality values when creating similar contracts, eliminating the need for manual entry Fit Optionlaity type needs to be selected manually ACM- 408 Ability to utilize unique contract identifier numbers that are shared and accessible across all entities in the system Fit Contract identifier can be used as per the req ACM- 409 Ability to customize number sequences for contracts by legal entity, with intercompany contracts potentially using separate numbering series, subject to further SAP validation and audit requirement assessment Gap Number sequence is assigned to contract type ACM- 415 Ability to search contracts using wildcards in the red box search field, limited to key fields including external identifier, contract number, and company code Fit Fiori filters available ACM- 416 Ability to search contracts by date range using Adapt Filter functionality with "Created On" parameter, and by contract number through the contract search box Fit Fiori filters available ACM- 417 Ability to use expanded free text fields with greater character limits than current SAP systems, with text content configurable to carry forward to subsequent documents without truncation Gap Free test avaialble in contract, Enhancement for copying to preceeding doc
--- 第44页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 44 of 215
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
ACM-
425
Ability to include VAT in both OTP and non-OTP
transactions, with VAT charged separately on
prepayment invoices while being included in credit
limit calculations
Fit
Tax Configuration
ACM-
445
Ability to have valuation point as market curve
reference for price lots. Valuation point can't be
blank for a price lots. Make sure you cannot save
a trade without a curve. Specific market indices
whave specific product/location combinations e.g.
associate a market index showing the value of
CPO at Lampung. These market indices should
default when the specified product/location
combination is selected on a trade
Fit
Valuation points
commodity, location
and time
ACM-
496
Ability to create multiple contracts simultaneously
using Excel spreadsheet input through SAP API
integration. Wrapper program might be required to
capture the required custom fields. - Standard API
might require a wrapper API to ensure all
information is captured at contract
Fit
Standard API might
require a wrapper API
to ensure all
information is captured
at contract
ACM-
513
Ability to support EUDR (European Union
Deforestation Regulation) reporting requirements
through consolidated contract visibility
Gap
Custom Report
ACM-
534
Ability to split contract into multiple lines
maintaining same contract number but assigning
different customers to each line
Gap
Contract split and
optionality functionality
can be explored
ACM-
544
Ability to support flexible agreed prices across all
transaction parties
Fit
Default business
partner will have
negotiated contract
price while alternate
partner will have string
/ reference price
ACM-
665
Ability to define payment terms at customer level
by Credit team with system enforcement of
specified terms
Fit
SAP provides custom
validation to happen
during contract
approval. Need more
details to set exact
checks.
Payment terms can be define at business partner level, which could be defaulted at contract ACM- 666 Ability to override payment terms at contract level for regulatory changes (e.g., Indonesia export requirements) Fit Default product offerings ACM- 667 Ability to implement single tier approval structure based on roles rather than transaction values Fit Role-based authorization is provided by SAP ACM- 683 Ability to manage contract statuses (draft, approved, etc.) with configurable workflows based on contract values and approval authorities Fit Company Code level Configuration. Part of Implementation
--- 第45页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 45 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 684 Ability to configure multiple contract parameters including status and workflows based on specific requirements Fit Company Code level Configuration. Part of Implementation ACM- 685 Ability to perform mass approval on multiple contracts Fit Using Standard ACM Fiori Application to manage ACM Trading Contracts ACM- 686 Ability to create third-party contracts Fit Using Standard ACM Fiori Application to manage ACM Trading Contracts ACM- 688 Ability to create contracts with multiple line items having different Incoterms Fit Contract Optionality. Different IncoTerm can be maintained during nomination. ACM- 690 Ability to handle contracts with mixed incoterm scenarios, i.e., GAR USA deliver half the quantity, and customer picks up the other half scenario Fit Contract Optionality. Different IncoTerm can be maintained during nomination. ACM- 691 Ability to configure different pricing basis for different line items within the same contract Fit Company Code level Configuration. Part of Implementation ACM- 692 Ability to configure contract summary reports as customizable views Fit Fiori Maintain ACM Contract with user specific view variants ACM- 694 Ability to price contracts in different basis currencies with fixed FX rates Fit Standard ACM functionality. CPE needs to be configured accordingly ACM- 696 Ability to configure multiple pricing types within a single contract line item Gap Refer to CTRM-3009. Maintain different valuation points for different pricing approaches on different line itmes. ACM- 697 Ability to configure premium in contract currency while futures are in different currency Fit Standard ACM functionality. CPE needs to be configured accordingly ACM- 702 Ability to change payment terms after contract creation with appropriate controls and restrictions Gap Will need custom logic to override the standard behavior. Not advisable to do after the execution has started.
BackstopCheck¶
ACM- 703 Ability to set validation rules on payment terms with credit risk approval requirements Gap Will need a custom development. Details in the KDD for Credit check ACM- 705 Ability to define tolerance at both contract and item level Fit Choose the right option on the contract to
--- 第46页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 46 of 215
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
select at what level the
Tolerance should be
applied.
ACM-
719
Ability to link mirror contracts as related trades at
item level
Fit
Standard ACM
Functionality
ACM-
720
Ability to create mirror contracts from either entity
with appropriate edit controls
Fit
Standard ACM
Functionality. Leading
Contract always has
the execution and
Settlement controls
ACM-
737
Ability to use templates for trade capture with
predefined fields
Fit
Template Contracts
can be saved say per
Commodity and can be
used to create
executable Contracts.
ACM-
752
Ability to have multiple pricing lots within one
contract item
Fit
Part of basic ACM
functionality
ACM-
765
Ability to manage documents across contract
lifecycle with proper lineage and accessibility
Fit
Attachments can be
added at Different
Levels. Recommended
to have them stored at
a different server and
attach a link instead
ACM-
766
Ability to attach documents with drag-and-drop
functionality
Fit
Attachments can be
added at Different
Levels. Recommended
to have them stored at
a different server and
attach a link instead
ACM-
797
Ability to handle contracts in different currencies
based on transaction type (domestic vs
international)
Fit
Similar question on
handling multi-
currency; this can be
clubbed together
ACM-
799
Ability to create child contracts from master
contracts when partial quantities require different
billing parties
Gap
If BU accepts to
manual workaround,
i.e., cancel old contract
and make a new one. If
not, it is a gap, SAP
needs to develop
solution for this
ACM-
800
Ability to manage different ship-to and bill-to
parties within a single contract
Fit
Standard Solution
Behavior
ACM-
801
Ability to specify different delivery periods at
individual line item level within a contract
Fit
Standard Solution
Behavior
ACM-
804
Ability to create separate contract lines for
different material grades during initial contract
creation
Fit
Standard Solution
Behavior
ACM-
821
Ability to cancel quantities from broker master
contracts and create new direct customer
contracts while maintaining traceability to original
broker contract for fee calculation purposes
Fit
Separate Broker
contracts need to be
cancelled if not acted
upon within 7-15 days?
This would be a
custom development
--- 第47页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 47 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 822 Ability to enforce and track contract validity periods of 7-15 days for pending expirations specific to broker transactions Fit Standard ACM Applications and reports can be used to track such contracts manually and close them manually. IF automation is needed then we might need custom development. Separate Broker contracts need to be cancelled if not acted upon within 7-15 days. This would be a custom development ACM- 823 Ability to record and track broker guarantee arrangements where brokers cover payment risk for end customers, including broker liability limits and coverage terms Fit Proposed solution is to have separate contracts for brokers and actual counterparties.
Actual Contracts can have Broker as bill-to party who inturn collects from the Counterparty ACM- 825 Ability to maintain hierarchical contract relationships with systematic numbering (e.g., master contract 123 splits into 123-1, 123-2, 123- 3) for audit trail and fee tracking Fit Standard ACM Functionality ACM- 830 Ability to split single CNF contracts into multiple sub-contracts while maintaining parent contract reference Gap CNF Contracts are the ones that GAR PK does NOT create, but only gives information to GAI SG. Cases that requires splitting may be explored. ACM- 859 Ability to print Contract based on contract document
Relate to: CTRM-1228 Gap Form output ACM- 868 Need to use same language in the contract print out.
Relate to: CTRM-1345 Gap Form output ACM- 893 Ability for physical (ACM contract) templates for manual upload into system Fit Standard contract creation APIs are available. ACM- 925 Ability to support premium, flat, and NPE pricing with T+1 allocation Fit SS[Jan07]: Flagged this as a Fit. Standard ACM Functionality and GAR version have both been demoed for different components
--- 第48页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 48 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution of ACM Pricing components. The same has been documented in Trade capture as well as Trade Control blueprint documents ACM- 1002 Ability to segregate OTP vendor (pay full payment amount include tax) & Non-OTP vendor (pay only the base payment amount & only pay the tax amount upon tax invoice received), then interface to the payment team & tax posting correctly.
Need to have validation to show error - if vendor is OTP but trader select the wrong tax code on transaction level: U8 = NOTP Tax Code/ VAT In Block for Payment UA = OTP Tax Code/ VAT In Free for Payment
Relates to CTRM-1002, CTRM-1279, CTRM- 1280, CTRM-1289, CTRM-1290 Gap Custom Table for OTP/NOTP Vendor will be maintained by ACM. ACM- 1018 Ability to have different Trade Execution workflow for different payment terms (Prepayment blocks nomination confirmation, while credit allows/ credit limit check triggered) Gap This Depends on whether ACM is using Nomination or SO/Approach Decision
Nomination Validation Groups. Nomination validation / blocks
Payment terms : Prepayment / Down Payment, then need to complete Prepayment process before doing Nominations
Payment terms Credit / LC , need to complete credit check (or credit release by credit risk team) before doing nominations ACM- 1025 Ability to have Partner PCA information fields in contract level for consolidation purposes Gap Add Custom field in contract level ACM- 1040 Ability to include product certification in the Sales invoice Gap Enhancement in contract level. Field addition in Contract to specify the Certificate Name / Type ACM- 1149 Ability to allow deal entry only with approved counterparties, only allow for active counterparties to be available for selection during contract Gap MDG team to set the flag to prevent contract creation
--- 第49页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 49 of 215
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
creation.
If the counterparty is not approved/ active, don't
show in contract.
ACM-
1179
Ability to add Broker Reference Codes and show
in Contract output form (if this field is empty then
no need to show in Contract) and carry over to
Delivery Documents
As-is: broker as business partner
Broker Reference Code will be filled with Broker ID and need to be printout in Contract Output form usually broker GAC request to include this Broker Ref Code in contract Gap add custom field for broker ref field ACM- 1180 Ability to add Sales Area Code (Bonded and Non Bonded identifications)
--> Bonded / Non Bonded is maintained in Plant Master Data, ACM Contract can refer to that field Gap add custom field to be added for bonded and non bonded
Bonded and non- bonded zones to be maintained at enterprise structure or contract level?
If to be maintained at contract level, need additional field to indicate whether it is bonded and non- bonded.
Plant Master Data got information to indicate bonded / non bonded, can utilize that field ACM- 1181 Ability to add commodity certifications (eg. health, RSPO) and is automatically populated to subsequent steps (eg. Delivery forms, Billing) Gap add custom field and the data will flow to nomination and then printed on form and then to billing doc
At item level (per product)
If to be printed as forms output, no enhancement is required.
If fields want to be seen in the Delivery document in SAP - same enhancements
--- 第50页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 50 of 215
Req. No
Business Requirement
Requirement
Analysis (Fit/Gap)
Solution
are required at delivery
level
ACM-
1182
Ability to add Commodity Specifications, Port of
Loading, Port of Discharge, Plant, etc. during
Contract Capture and show it at Nominations (for
Delivery Documents Forms)
Gap
add custom field and
the data will flow to
nomination and then
printed on form
ACM-
1183
Ability to add Packaging Code and Packaging
Specification
Ability to add extra cost (packaging / accessories)
in Contract Capture. Packaging and accessories
can be pulled from Master Data instead of Free
Text and show it at Nominations (for Delivery
Documents Forms)
Gap
put in the free text /
comment. add custom
field having drop down
and along with it
additional space to add
comment and this
details should be flown
to nomination and then
priinted on the form, for
cost we can use/
explore fee/expense.
ACM-
1184
Ability to add Contract Tolerance Level
Fit
Standard functionality.
Can utilize tolerance
schedule.
ACM-
1185
Ability to add VAT Tax ID / Tax Code
Gap
a new field can be
added based on req.
Standard practice from
ACM. User determined
tax code will override
the automatically
determined tax code.
Enhancement to get
tax code at contract
level and flow it in to
the precceding docs
ACM-
1186
Ability to add Product Type (ex. Bulk, Semi-bulk).
This need to link to packaging selection for semi-
bulk product only.
Gap
a new field in contract
with a dropdown list. If
semi-bulk is selected,
packaging dropdown
list will be available.
ACM-
1189
Ability to select/ setup different Payment Terms
(e.g. 1x DP, 2x DP, etc) on transaction level
Fit
FI baseline
configurations. Exist in
Standard Functionality
ACM-
1190
Ability to differentiate contract types :
- Unpriced contract
- Fixed Price/ Flat price contract
Fit Exist in Standard Functionality ACM- 1194 Ability to configure Mandatory Fields for Contract Creations Gap Enhancement to be made to make fields mandatory ACM- 1195 Ability to save a deal to a draft status - so it does not go into position and exposure reporting, PnL, Credit and Risk Monitoring Fit Exist in Standard Functionality ACM- 1198 Ability to capture special request from customer such as additives (vitamins, etc) Can select the vitamins / other additives required Gap add custom field
--- 第51页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 51 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution and assign the appropriate cost center which will later be automatically captured in the expense section of the contract (e.g. Delivery Documents) ACM- 1199 Ability to search & select the materials & show the Material Code for additional and Optional Add-on Accessories (ex. Palette, Heating Pad, etc) and carry over to Delivery Documents & posting GI to expense Gap put in the free text / comment. if the details are manually entered then we can use the free text, else we can do enhancement as per the req ACM- 1200 Ability to add extra cost (packaging / accessories) in Contract Capture. Packaging and accessories can be pulled from Master Data instead of Free Text and show it at Nominations (for Delivery Instructions Forms)
As-Is: Packaging material is GI as expense to Trader Cost Center every end of month Gap Extra cost can be added using Fee/Expense basis and Forms needs to be enhanced. KDD discussion ACM- 1202 Ability to add Contract notes with long text strings, that need to be shown in sales contract print output. Fit Exist in Standard Functionality. ACM can capture long text (up to pages length), form output also can be config as needed 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- 1205 Ability to create detailed sales contracts with outright price terms, including all relevant details Ability to only enter one flat price during contract capture without entering both Basis and Future Price Fit Exist in Standard Functionality ACM- 1206 Ability to attach docs (scanned/pdf) to contract, such as PO from customer / Sales Contract from Vendor, as basis doc to split the parcel (i.e. split into 5 SO with different fulfillment date) Fit Exist in Standard Functionality ACM- 1207 Ability to capture Plant Code and Multiple Locations / Shipping Points in Contract Capture Fit Exist in Standard Functionality
1 plant can have multiple shipping points, but shipping points are not shown at contract level; more relevant during nomination.
Plant code can be provided at the nomination level ACM- 1209 Ability to enter Contract Date during Contract Creation and support Back Date Contract Gap add custom field. Free text tab can be used. KDD discussion
--- 第52页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 52 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1212 Ability to differentiate between Allocated PSO, Allocated Non PSO, Non Allocated in Contract for Biodiesel Gap Add custom field at contract level
3 fields needed
Allocated / Non Allocated
PSO / Non PSO
Subsidized / Non Subsidized
These fields are needed only forBiodiesel
For others we can put is as NA ACM- 1214 Ability to differentiate between LTC, LTA or Spot Contract Gap Custom field at contract level.
or use External Reference ID (Fit) ACM- 1215 Ability to only enter only one of Purchase / Sales Org (e.g. ony Purchase Org for Purchase and Sales Org for Sales Transactions) Gap Required for management reporting purposes, therefore these fields are mandatory ACM- 1216 Ability to setup and use Template for easy Trade Capture according to Contract Term (to minimize user input). Fit Exist in Standard Functionality. Use copy contract / contract template functionality ACM- 1217 Ability to duplicate from existing contract with pre- populated Field. Fit Exist in Standard Functionality ACM- 1219 There should be a field that contains plant number so it is easier to link between intercompany Purchase order with its respective Sales contract Fit Exist in Standard Functionality ACM- 1220 Ability to reconcile contract details from vendor against what we created, to check if there are any mistake in our contract entry. Gap no solution (require another product to scan pdf doc). Contract can be validated in change mode
To be done manually
ACM-
1222
Ability to manage deal approval workflow:
- send email notifications for contract approval
- send email notifications to related stakeholders
after contract approved (by Commodity Group and
Plant Location)
- Provide summary page with key information for
Mass Contract Approval
Fit
Exist in Standard
Functionality.
Notifications - part of forms, can be configured
--- 第53页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 53 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1223 Ability to setup template to generate trade confirmations : - Short form contract for physical trades (single template regardless of terms) - Addendum template for physical trades - Deal slip template for physical trades - Physical trade confirmations - Generation of addendums to sales & purchase contracts Gap Form output ACM- 1224 Ability to mass approve contract based on specific criteria e.g. Material, Company Code, etc. Fit Exist in Standard Functionality in contract Approval workcenter ACM- 1225 Ability to show specific informations during mass approval : Counterparty, Material, Qty, Price, Incoterm, Payterm, Shipment, Prepayment Gap Custom Report. View of Summary Information upon Approval ACM- 1226 Ability to approve trade contract using mobile phone Fit Exist in Standard Functionality ACM- 1227 Ability to approve or authorize based on commodity group (Palm, Lauric, Biodiesel)
Related with CTRM - 1076 Fit Exist in Standard Functionality ACM- 1228 Ability to printout hardcopy/softcopy of Contract after Contract Approval Contract print output need to have barcode - follow as-is Gap Form Solution ACM- 1230 Ability to maintain automated FX rate during contract creation and choose FX Rates based on Trade / Contract Date. Fit Exist in Standard Functionality. Only provisional FX Rates are provided, user need to manually select ACM- 1253 Ability to capture Intercompany transaction when we still don't know the counterparty details (legal entity & plant) Currently Seller side (Upstream) use KUBE to create open request, and Buyer side (Downstream) can update the buyer plant information. Gap Report - Use the Workcenter - KDD Discussion ACM- 1265 Ability to change / use different material description in Contract to be printed on Contract Form Output.
OTB-415: Print out sales contract for export transaction can accomodate material description more than 40 character Fit Exist in Standard Functionality. Update Contract material descrip.
1 material code can have multiple material name/ description in MDG (up to 40 character).
Need to utilize the basic data text
--- 第54页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 54 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution functionality OR create custom table to accommodate long material description ACM- 1266 Ability to add Certifications Reference Number in Contract and carry over this informations to Delivery Document Gap Add custom field at contract level and also on delivery (free text) ACM- 1267 Ability to add Counterparty (Buyer/Seller) Reference Number in Contract and carry over this informations to Delivery Document Gap Enhancement would be needed to pull and display on delivery doc. can use customer ref for sale and your ref field for purchase on basic data tab ACM- 1269 Ability to add additional material outside BOM, e.g. Antioxidant, Vitamin K, etc. for the purpose of tracking the "naked" / raw price of commodity for the contract
Relate to : CTRM-1198, CTRM-1199 Gap Enhancement to be done as per req. Text tab can be used for adding text details and fess and expense can be explored for price
SS: ACM Expense can
only cover the cost of
the additional materials
but does not cover
Goods movement for
the additional
materials. Standard SD
process to be followed.
ACM-
1270
Ability to add special condition / disclaimer term to
be print out in Contract Output form.
e.g. Buyer to countersign and return none copy of
this Sales Contract to Seller at the latest of 3
working days since being sent, otherwise Buyer
shall be deemed to confirm and agree to this
Contract.
Gap
Enhancement to be
done as per req, if field
is needed with drop
down values we can .
Text tab
ACM-
1271
Ability to enter estimate delivery date in Range
(Date from and Date To) in contract level
Fit
Exist in Standard
Functionality: Delivery
date from/ to
ACM-
1272
Ability to send email Notification before Delivery,
have email functionality to send out sales contract
& sales order via email to related parties.
Need to config the group of email recipient e.g.
Palm Trader Team, Logistic Team, etc.
Fit
Exist in Standard
Functionality, need to
be configured
ACM-
1273
Ability to have a notification/reminder mechanism
to remind the traders to follow up with the vendor
to process the Bonded Zone documents (SPPB
and BC) as soon as contract has been approved
Related to CTRM - 1041 Gap Form, triggered only when location is Bonded zone ACM- 1274 Ability to prevent trade capture of raw materials sales of CPO or Palm Kernel from bonded zone plants to non-bonded plants before further processing of these raw materials. (Raw materials Gap enhancement at contract level, to apply the check & block
--- 第55页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 55 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution should still be allowed to be moved from one bonded zone to another, but the sale of raw materials from bonded zone should be blocked) ACM- 1276 Ability to setup multiple approver (or delegate approver) for Contract Approval. Approval will be based on Traders ID (or Trader Group) that create the Contract. (Pending confirmation from Trader on the approval grouping - TBD on detailed design) Fit Exist in Standard Functionality ACM- 1279 Ability to have separate list for OTP and NOTP Vendor. Registering a vendor into OTP category requires special approval matrix to Commercial Director and CFO. 90% currently is NOTP vendor. As-Is = maintain in custom table, with manual approval via email
Relates to CTRM-1002, CTRM-1279, CTRM-
1280, CTRM-1289, CTRM-1290
Gap
Custom Table for
OTP/NOTP Vendor will
be maintained by ACM.
ACM-
1295
Ability to have different tax accounting posting
based on tax code variations (e.g. Bonded Zone
tax code, Non-Bonded tax code and other tax
code variations) for prepayment and final payment
Gap
Bonded/Non-Bonded
Solution
ACM-
1325
Ability to detect and provide a hardstop notification
when more than one purchase contract is created
with reference to the same sales contract vendor.
This is to prevent the possibility of the same
purchase contract being processed more than
once.
Currently there is a hardstop notification for the
same seller contract number in the e-deal slip
program
Gap
Enhancement at
contract save is
needed during the
approval. Not to allow
same external
reference field, if
there's any duplicate,
cannot be save.
ACM-
1344
Ability to have custom table to determine the
authorized signee for each documents (e.g. sales
contract, billing) - print out
Gap
Role based
authorization can be
provided for document
approval. Custom table
can also be created for
doc validation.
ACM-
1345
Need to define the language/ use the same
language in the contract print out.
Fit
Forms can be multi-
lingual. Default
functionality.
ACM-
1346
Ability to mass upload Sales Contract document
(e.g. from excel / csv templates)
Fit
SAP provided Mass
creation of Contracts
via APIs.
ACM-
1347
OTB-191:
Ability to have control for price update in SO and
contract.
Only approved user (ZSD_USRID) who are able
to do price update
Fit
Pricing can be done
and contract approval
will happen based on
role and authorization.
ACM-
1410
Ability to record the name of trader / salesman
responsible for the contract capture input process
(for both sales & process). The trader admin who
Gap
Custom Field
Enhancement at
Contract Level
--- 第56页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 56 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution input the transaction is not the actual trader/ salesman, therefore need this field to mention the trader name/ user ID.
Related to CTRM-1416
ACM-
1418
Ability to create Certificate Master Data that
contains :
- Plant/PCA
- Unit
- Issued Date
- Valid Until (date)
- Certificate No.
- Type Product (CPO/PK/CKG/etc.)
- Value
- CB
- Certificates Type (RSPO MB/RSPO GGL/etc.)
- PSM
- PT
- SC
- Status (Enabled/Disabled)
- Short Description
- Active (Y/N)
US currently maintain in KUBE table for master
data, DSI maintain in Smart Trace
Gap
Custom Field
Enhancement at
Contract Level
ACM-
1427
Ability to capture all intercompany trading
transactions, for example:
- US to US
- US to GBE
- US to DSI
- DSI to DSI
- DSI to SOCI
- DSI to GAI
- GAI to DO
As-is: DSI maintain same material number even
though with different quality. SOCI segregates
different material number based on quality.
However, to use the intercompany functionality in
ACM, seller and buyer company needs to use the
same material number.
Gap
Enhancement at
contract level for
valuation type
ACM-
1438
Ability to differentiate and auto generate the
correct Bank account number in Contract Print
output based on the logic of: Company code -
PSM (US), Company code - Dist Channel (DSI).
Gap
Form Output
ACM-
1441
For scenario of intercompany commercial
transaction with no physical goods movement (eg.
jual-beli dalam 1 tanki), ability to have a
flag/checkbox during contract capture to indicate
of such scenario, so Nomination is no longer
needed since it's not TM relevant, no credit check
& LDC can be automated since the contract qty =
load qty = unload qty
As-is: Upstream Sales & Logistics already know
Gap
Custom Fields at
Contract
--- 第57页 ---
S/4HANA Transformation Project Solution Blueprint – Trade & Origination (ACM) Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 57 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution that it is a scenario of no physical goods movement during input in KUBE
Note: Part of CIS (Customer Innovation Service) Solution means the solution will be built in a dedicated workshop by SAP CIS Team.
--- 第58页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 58 of 215 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 Create Agricultural Trading Contract
Figure 3.12 - Create Agricultural Trading Contract
Table 3.5 - Create Agricultural Trading Contract Process Steps Role Transaction Code/Fiori App ID Description Check Similar Contract Availability Trader (ACM) WB22/W23/ Fiori Tile: Display Trading Contract Applies for 3rd Party Purchase, 3rd Party Sales, and Lead Intercompany Side.
For details on Intercompany process, please refer to Solutioning Section 3.2.3.10
A reference document can be a template or a contract
When copying a template more data will need to be populated then when copying a contract.
Validate before moving forward: 1. Counterparty 2. Transaction 3. Payment Terms 4. Incoterm 5. DPQS 6. Tolerance 7. Optionality 8. Commodity To and From Date
--- 第59页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 59 of 215
Process Steps
Role
Transaction
Code/Fiori App ID
Description
9. Pricing
Enter Contract Details
for New Contract or
Contract to be
Referenced
Trader (ACM)
WB21/ Fiori
Application:
Maintain ACM
Trade Contract
Data to input:
1. Counterparty
2. Transaction
3. Payment Terms
4. Incoterm
5. DPQS
6. Tolerance
7. Optionality
8. Commodity To and From Date
Price Contract Details
Trader (ACM)
WB21/ Fiori
Application:
Maintain ACM
Trade Contract
Or
WB22/ Fiori
Application:
Maintain ACM
Pricing
Maintain Quantity and Pricing
Components (Futures and Basis)
Maintain ACM Pricing and Maintain ACM Contracts are two different fiori app. While creating ACM Contract, users can also price immediately or price it later.
Maintain ACM Pricing is also given in standard to see lists of pricing lots and its status. Users can also price in mass. Assign Expenses if needed Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Expenses can be added at trading contract level Assign Fees if needed Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Fees can be added at trading contract level Assign Prepayment Request if needed Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Prepayment request needs to be added at contract level Attach Document (ex: Customer Purchase Order) if needed Trader (ACM) Fiori Application: Maintain ACM Trade Contract Attach relevant document on the contract level Select Save Button Trader (ACM) N/A Click on save button.
At save, optionally, there is a credit check for SG/DO. There will be an intermediary status “Awaiting Credit Confirmation” if credit fails at contract. Otherwise, if success it will go to default “Draft” status to be approved.
--- 第60页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 60 of 215 3.2.2.2 Change Agricultural Trading Contract
Figure 3.13 - Change Agricultural Trading Contract
Table 3.6 - Change Agricultural Trading Contract Process Steps Role Transaction Code/Fiori App ID Description Enter Contract Number Trader (ACM) WB22/W23/ Fiori Tile: Display Trading Contract Applies for 3rd Party Purchase, 3rd Party Sales, and Lead Intercompany Side.
For details on Intercompany process, please refer to Solutioning Section 3.2.3.10
Changing Intercompany Lead Side Contract is will change Intercompany Mirror Purchase Contract. Enter Contract Details for New Contract or Contract to be Referenced Trader (ACM) WB21/ Fiori Application: Maintain ACM Trade Contract Data to input: 9. Counterparty 10. Transaction 11. Payment Terms 12. Incoterm 13. DPQS 14. Tolerance 15. Optionality 16. Commodity To and From Date Price Contract Details Trader (ACM) WB22/ Fiori Application: Maintain ACM Pricing Maintain Quantity and Pricing Components (Futures and Basis) Assign Expenses if needed Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Expenses can be added at trading contract level Assign Fees if needed Trader (ACM) WB21/WB22/ Fiori Application: Fees can be added at trading contract level
--- 第61页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 61 of 215 Process Steps Role Transaction Code/Fiori App ID Description Maintain ACM Trade Contract Assign Prepayment Request if needed Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Prepayment request needs to be added at contract level Attach Document (ex: Customer Purchase Order) if needed Trader (ACM) Fiori Application: Maintain ACM Trade Contract Attach relevant document on the contract level Select Save Button Trader (ACM) N/A Click on save button.
At save, optionally, there is a credit check for SG/DO. There will be an intermediary status “Awaiting Credit Confirmation” if credit fails at contract. Otherwise, if success it will go to default “Draft” status to be approved.
--- 第62页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 62 of 215 3.2.2.3 Approve or Reject Agricultural Trading Contract
Figure 3.14 - Approve or Reject Agricultural Trading Contract Table 3.7 - Approve or Reject Agricultural Trading Contract Process Steps Role Transaction Code/Fiori App ID Description Select Approve Trading Contract Tile Trading Manager (ACM) WB22/ Fiori Application: Approve ACM Trading Contract Applies for 3rd Party Purchase, 3rd Party Sales, and Lead Intercompany Side.
For details on Intercompany process, please refer to Solutioning Section 3.2.3.11 Set Selection Criteria Trading Manager (ACM) Fiori Application: Approve ACM Trading Contract Filter appropriate document attribute to be approved Review individual contract Trading Manager (ACM) WB22/ Fiori Application: Approve ACM Trading Contract Review appropriate details on the contract Approve/ Reject contract Trading Manager (ACM) WB22/ Fiori Application: Approve ACM Trading Contract Approve/ Reject based on details on the contract. Status of contract will be changed to “Approved”.
--- 第63页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 63 of 215 3.2.2.4 Create Storage Agreement
Figure 3.15 - Create Storage Agreement Table 3.8 - Create Storage Agreement Process Steps Role Transaction Code/Fiori App ID Description Storage Agreement Creation Logistic & Operation (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Contract Type = ZSTO to create a Storage Agreement (3rd Party Storage).
Storage Agreement (3rd Party Storage is created in GAR usually in a long-term agreement format. Creation of Agreement is independent but can be linked during Delivery at Load Data Capture. Add \Fees optionally Logistic & Operation (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Fees can be added if relevant
--- 第64页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 64 of 215 3.2.2.5 Approve or Reject Storage Agreement
Figure 3.16 – Approve or Reject Storage Agreement
Table 3.9 - Approve or Reject Storage Agreement
Process Steps
Role
Transaction
Code/Fiori App
ID
Description
Select Storage
Agreement Number
Logistic &
Operation
Manager
(ACM)
WB22/ Fiori
Application:
Approve ACM
Trading Contract
Applies for Contract Type = ZSTO (Storage
Agreement/ 3rd Party Storage)
Approve/ Reject
Storage Agreement
Logistic &
Operation
Manager
(ACM)
WB22/ Fiori
Application:
Approve ACM
Trading Contract
Approve/ Reject based on details on the
contract. Status of contract will be changed to
“Approved”.
--- 第65页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 65 of 215 3.2.3 Solutioning 3.2.3.1 Contract Creation Contract creation with your counterparties. It involves managing contracts throughout their lifecycle, including any necessary amendments or updates that fall under contract maintenance. This ensures that contracts are accurately documented and reflect the agreed-upon terms and conditions.
In Agriculture contract Management various types of contracts can be created base based on the document types available in system.
3.2.3.2 ACM Contract Types There are standard Agricultural Trading Contract on ACM. For GAR, we will maintain a custom version of the standard contract type with ‘Z’ prefix as below. Table 3.10 - ACM Std. and Contract Type Contract Types Reference SAP Standard Document Types User Document Type Third Party Purchase AC3P ZC3P Third Party Sale AC3S ZC3S Intercompany Sales ACIS ZCIS Intercompany Purchase ACIP ZCIP Intracompany Sales ACRS ZCRS Intracompany Purchase ACRP ZCRP
For GAR specific we can have a different number range assigned to these document types for easy identification for the user.
3.2.3.3
Document Number Ranges
There are standard Agricultural Trading Contract on ACM. For GAR, we will maintain a custom version
of the standard contract type with ‘Z’ prefix as below.
Table 3.11 - Number Ranges
User Document Type
Number ranges*
ZC3P
1000000000 - 1999999999
ZC3S
2000000000 – 299999999
(custom version explained below)
ZCIS
3300000000 - 3399999999
ZCIP
3400000000 – 3499999999
ZCRS
4300000000 - 4399999999
ZCRP
4400000000 - 4499999999
--- 第66页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 66 of 215
3.2.3.4
Custom Field Sales Contract Number Range
SAP Sales Contract Number Range comprises of 2 components Prefix and Running Number
illustrated as below:
XXY0000000 – XXY9999999
2 digits Prefix to identify Company
1 digits Running Number to identify Contract Document Type
7 digits Running Number.
Table 3.12 - Sales Contract Type Number Range
Document
Type
Description
Create
with
Reference
Number Range Format
ZC01
Sales Contract -
Multiple
Shipment
No
XX10000000 – XX19999999
ZC02
Sales Contract -
Single Shipment
No
XX10000000 – XX19999999
ZC03
Contract Down
Payment
Yes
XX10000000 – XX19999999
Example: PT. SMART Upstream – ZC01: 1010000000 - 1019999999 PT. SMART Downstream – ZC01: 3310000000 – 3319999999 GAI – ZC01: 8310000000 – 8319999999 *Notes: Downstream trading has different solution which may lead to different number range format.
The SAP S/4HANA Flexible Number Range functionality has been activated to enable the assignment of different sales contract number ranges based on the Company Code. This ensures that each Company can have its own distinct set of contract numbers, streamlining the management and tracking of contracts across various organizational units.
--- 第67页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 67 of 215 3.2.3.5 GAR Sequence Number Despite SAP document number, GAR also require another number range called sequence number. The sequence number come with the pre-defined format as below. Note that the number range & sequence for sales contract is an example only (non-exhaustive). Full list for all document numbering range & sequence will be finalized during detailed design phase.
Sequence number (20 Characters) AAB/ZZZZ/DDMMYY/0000 2 digits identify channel of distribution
1 digit identify the document type
4 digits identify Sales Org (For Local & Export Trading, 4 digits will represent
Plant code to identify source of product)
6 digits identify document issuance date, month and year
4 digits identify document running number (reset per day) For Example: LTC/3320/120824/0001 Read: Local Trading Contract / DSI Trading / Twelve August 2024 / Number 0001 in that day. Table 3.13 - GAR Channel of Distribution Distribution Channel Downstream Distribution Channel Upstream LT - Local Trading DI - Domestic Intercompany ET - Export Trading DT - Domestic Third Party
XI - Export Intercompany
XT - Export Third Party
Table 3.14 - GAR Doc Type Document Type C - Contract I - Invoice P - Proforma Invoice DP S – Sales Order
Manage Search Model apps will be utilized to enable searching by GAR Sequence Number.
This feature allows business users to find contract documents in SAP based on the GAR sequence
number. The GAR sequence number can be used as information in a customized report related to
the contract transaction to be developed.
Contract entry and maintenance via API ACM now provides ACM specific APIs to provide greater flexibility in process design to its customers and allow the creation and update of contracts from external sources.
--- 第68页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 68 of 215 3.2.3.6 Contract Scenario Indicator Fields This section describes the contract scenario indicator fields used to classify and control different business scenarios in contract management. These indicators help the assist the system and business users to identify how a contract should be processed, monitored, and reported based on its commercial and operational characteristics. 1. No Goods Movement Relevant Scenario (i.e. Buy-Sell in 1 Tank) 2. LRD Relevant Scenario 3. Long-Term Contract (LTC) 4. Long-Term Agreement (LTA) 5. PSO/ Non-PSO 6. Etc. 3.2.3.7 Optionalities Through the Optionalities functionality, GAR can maintain additional logistics options along with the discounts or premiums to be applied for those options. This additional flexibility can be helpful to GAR for the cases where the Load/discharge location or Incoterms are not confirmed at the time of Contract creation/approval.
Optionality Categories The solution is delivered with a set of predefined optionality categories. For example, these categories include Discharge Location, Incoterms, Mode of Transport, and Means of Transport.
Optionality Types The Optionality Type determines how the system evaluates different decisions during delivery planning & execution. Optionality can be Implicit, Explicit, or "Any" depending on how optionality should be evaluated in the system. Implicit and Explicit optionality means system needs to evaluate optionality decision during delivery planning & execution based on what is being modeled at contract. While implicit allows for different values, explicit will hard-block if value is different with the contract optionality.
"Any" optionality means there is no need for the system to evaluate different decision during delivery planning & execution.
User can define optionalities on the Additional Contract Conditions tab page for a commodity item. Additionally, default values for the Mode of Transport, Means of Transport, Crop Season ID, and Source Location can be specified too by entering further optionalities in the Additional Optionality Values screen area. Each optionality can be added by entering the following information: • Optionality Category • Value Type • Option Value • Premium or Discount Details
--- 第69页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 69 of 215
Figure 3.17 - Optionality Example for Vendor, Plant, IncoTerm
Figure 3.18 - Optionality Example for Material
--- 第70页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 70 of 215 3.2.3.8 Pricing Component As explained above, SAP Agricultural Contract Management (ACM) utilizes a comprehensive pricing framework built on several key components that work together to manage commodity pricing throughout the contract lifecycle. Table 3.15 - Pricing Component (System Fetched) No ACM Price Component Description How to Record Values Example 1a ACM Market Futures Price (ZMFT) Market FOB Futures Price Reference. This price is used for Mark-to-Market reference. System fetches FOB market reference, where prices are uploaded in FDCS17 ZMFT = $100 1b ACM Market Primary Basis (ZMBS) Freight Estimates. System fetches freight estimates, which are uploaded in FDCS17B periodically with correct validity to cover until next update ZMBS = $8
Price Components in Table 3.15 will be maintained in the background for each of the price lot. The users who are pricing the contract will have no
direct influence on these price components. During contract pricing, users will be maintaining price components mentioned in Table 3.16 below.
Table 3.16 - Pricing Component (User-Driven Inputs)
No
ACM Price Component
Description
How to Record Values
Example
1
ACM Contract Flat Price
Contract Flat Price. This price will be
used for Settlement.
User Input Flat Price
FLAT = $120
2
ACM Contract Primary Basis
(ZCBS)
Negotiated Freight Estimates
Users Input OR users can also fetch freight
estimates from FDCS17B and override, if
necessary, based on contractual negotiations
ZCBS = $8 (auto fetched)
ZCBS = $10 (user override)
3
ACM Contract Secondary
Basis (ZCB2, ZCB3, …)
All Other Costs aside from Freight
Estimates (Primary Basis) that are
part of the Price
User Inputs the individual components of
Secondary Basis.
ZCB2, ZCB3, … = $5
(sum of all different components
entered)
4
ACM Contract Futures Price
(ZCFT)
Contract Adjusted Price which can
be FOB/ Landed. This price is used
for Mark-to-Market.
System Automatic Calculation.
Adjusted Origin Price (FOB/ Landed) = Flat Price - Primary Basis (freight estimates) - Secondary Basis (other costs) ZCFT = FLAT - ZCBS - ZCB2, ZCB3 - …
ZCFT = $120 - $10 - $5 ZCFT = $105 5 (Optional) Marketing Reference Price Marketing Reference Price. This price is used for Marketing P&L. User Input Marketing Reference Price Marketing Reference Price = $101
--- 第71页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 71 of 215 For further explanations, please see figure 3.19 – Pricing Expected To-Be Flow below.
Figure 3.19 - Pricing Expected To-Be Flow
--- 第72页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 72 of 215 Table 3.17 - Basis Price Components for Indonesia Name Part of Price FOB MTM To bill to customer separately To receive as invoice from Vendor To allocate contracts to it Accrual Posting in SAP per deal per cost * Variance Comparison as of now To Be Process Container Fee/ Isotank (included in Freight cost) Yes Yes No No Yes No No Price Component Interest Fee/ Financing Cost (due to longer credit payment term) Yes Yes No No No No No Price Component Packaging Fee (Flex bag, IBC, Sticker) & Additional request (Heating pad, Vitamin, Antioxidant, Anti-bulging, etc.) Yes Yes No No No No No Price Component Broker Fee Yes Yes No Yes Yes Yes No Price Component + Expense w/ Accrual posting + Comparative Report Freight cost (Inbound) Yes Yes No Yes Yes Yes, capitalized to Inventory Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report Freight cost (Outbound) Yes Yes No Yes Yes Yes Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report Delivery Insurance (Purchase Transaction) Yes Yes No Yes Yes Yes, capitalized to Inventory Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report Delivery Insurance (Sales Transaction) Yes Yes No Yes Yes As-Is = No Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report PBM/EMKL (Load/ Unload Fee) Yes Yes No Yes Yes Yes, capitalized to Inventory Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report Pump Fee/ Handling Fee (Vessel Only) Yes Yes No Yes Yes Yes, capitalized to Inventory Yes Price Component + TMS Accrual + TMS Actualization + Comparative Report Surveyor Fee (ocean transport only) Yes Yes No Yes Yes As-Is = No No Price Component + TMS Accrual + TMS Actualization + Comparative Report Premium Quality for Sales (3MCPD, RSPO SG, Low IV, etc.) Yes Yes No No Yes No Yes Price Component Premium quality for purchase (RSPO SG, RSPO MB) Yes Yes No No Yes No Yes Price Component
--- 第73页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 73 of 215 Table 3.18 – Basis Price Components for Singapore Name Part of Price FOB MTM To bill to customer separately To receive as invoice from Vendor To allocate contracts to it Accrual Posting in SAP per deal per cost * Variance Comparison as of now To Be Process (SG) Cost_In Yes Yes No No No No No Price Component (SG) ADD.FIN COST Yes Yes No No, estimates from Trader No No No Price Component (SG) CARGO INSURANCE Yes Yes No No, estimates from Trader No No No Price Component (SG) DEMURRAGE COST Yes Yes No No, estimates from Trader No No No Price Component (SG) DEMURRAGE COST - LOADING PO Yes Yes No No, estimates from Trader No No No Price Component (SG) FFA ADJUSTMENT Yes Yes No No, estimates from Trader No No No Price Component (SG) INTEREST Yes Yes No No, estimates from Trader No No No Price Component (SG) IV ADJUSTMENT Yes Yes No No, estimates from Trader No No No Price Component (SG) LATE PENALTY SHIPMENT COST Yes Yes No No, estimates from Trader No No No Price Component (SG) M&I ADJUSTMENT Yes Yes No No, estimates from Trader No No No Price Component (SG) OTHER COST Yes Yes No No, estimates from Trader No No No Price Component (SG) PREMIUM Yes Yes No No, estimates from Trader No No No Price Component (SG) QUALITY PREMIUM COST Yes Yes No No, estimates from Trader No No No Price Component (SG) VESSEL INSURANCE Yes Yes No No, estimates from Trader No No No Price Component (SG) BROKER COMM Yes Yes No Yes Yes Yes Yes Price Component + Expense w/ Accrual + Comparative report (SG) FREIGHT COST Yes Yes No Yes Yes Yes Yes Price Component + Expense w/ Accrual + Comparative report (SG) SHRINKAGE COST Yes Yes No Yes Yes No Yes Price Component + Expense w/ Accrual + Comparative report (SG) STORAGE & HANDLING Yes Yes No Yes Yes Yes Yes Price Component + Expense w/ Accrual + Comparative report
--- 第74页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 74 of 215 In scenarios where the market reference is CIF, but the Purchase Contract is priced on an FOB basis with freight handled separately (i.e., not included in the contract price), it is necessary to capture an estimated freight cost as a price component to align the contract value with the market reference. This estimated freight enables: • Comparable valuation against CIF market prices for MtM purposes • Subsequent comparison between estimated and actual freight costs upon realization
In this scenario, Statistical Condition can be configured to record this information on the Contract. The information recorded in this condition can then be used both to compare between the estimated and actual and also in the ‘markup’ of the Contracts FOB price while doing the MtM. However, there needs to be a clear indication of such cases for relevant logic to be included in the Custom Reports. Details can be verified during the next phase of the Project. 3.2.3.9 Expense at Contract Expense can be assigned to an ACM Contract. Later, this expense can be accrued and settled. The process of this is covered on the Settlement and Invoicing Blueprint – Section 3.2 Fees & Expense Management.
3.2.3.10 Intercompany Mirror Side Contract Generation For Intercompany Contracts in ACM, Mirror side contract is generated on saving the lead contract. This mirror contract is visible in the related trades tab of the contract. To understand the concept of Mirror side, lets quickly understand the concept of Related trades and it’s setting as below: • A commodity contract may be related to other contracts, and this function is used to view the related trades for a contract as well as to add and delete related trades. A commodity contract can be related to other contracts and these related trades are listed on the Related Trades tab page for the commodity item. You can add a related trade, delete a related trade, or display a related contract directly from the Related Trades tab page. • A contract can be linked to an internal (SAP ACM Contract) as well as External Document. In case of linking the contract with another ACM contract, user can navigate to that contract as well.
--- 第75页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 75 of 215 3.2.3.11 Intercompany Contract Approval
Figure 3.20 - Intercompany Contract Approval
Sales and Purchase Contract will be generated simultaneously with a linked Contract Number. Contract approval will be required only from the lead contract side. In Indonesia, for Cross-BU Intercompany Contract Approval (US-DSI, DSI-Oleo), approval is still required from the mirror side. Approval from the buyer side is still required to maintain the existing control point.
--- 第76页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 76 of 215 3.2.3.12 Contract Output SAP Agricultural Contract Management follows standard output determination processes but also allows for enhancements that enable customers to capture amendments and transfer changes in the form of documents, such as emails, which can be used for obtaining the counterparty's signature.
Agricultural contracts provide a flexible framework that accommodates the evolving needs of industry partners, necessitating the capture of diverse information over time. SAP Agricultural Contract Management is designed to support this dynamic nature of contracts and streamline the entire contract lifecycle through highly automated processing.
Multiple Contract outputs can be triggered from the contract at the time of contract creation, approval or amendments to various assigned stakeholders.
The notifications can be sent as pdf attached to form or EDI as per the business expectations.
Following screen shot shows a sample of the different output types that can be triggered manually or automatically (event based) from a contract. This can be configured to cater to any requirement from the customer.
Figure 3.21 - Output Type
Commonly used Contract Output Types can be:
1. Contract Header Output
2. Contract Item Output
3. Contract Partner Output
4. Contract Amendment Output
5. Contract Cancellation Output
6. Barcodes
--- 第77页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 77 of 215 3.2.3.13 Approval by Mobile Phone Following FIORI Apps are specifically designed in the Trade capture area to assist Users are:
Figure 3.22 - Fiori Apps With the “Approve ACM Trading Contracts” app user can approve or reject Agricultural Contract Management (ACM) trading contracts.
If data change is required before approving or rejecting, this app also provides the navigation to the relevant SAP GUI transactions where change of contract or pricing is possible. Alternatively, “Maintain ACM Trading Contracts” App can be provided. The Apps access can be limited based on the roles assigned to user.
This app is meant to be used by ACM traders. On the Fiori Launchpad (FLP) tile, it displays the number of contracts in different types like Sales Contract, Purchase Producer Contract and Purchase Commercial Contract. For ease of searching, adaptable filters (contract no./type/status, sales/purchase side, counterparty, material, commodity and so on) are provided.
--- 第78页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 78 of 215
Figure 3.23 - Fiori App: Approve Trading Contract Role: To be able to access these apps, security administrator needs to assign the following roles to user: • Business Role: SAP_BR_TRADER_ACM (Trader) • Backend Sample Role: SAP_ACM_CNTRCTAQS1_APP This app is used to: • Approve or reject the contracts • Navigate to the relevant SAP GUI (back end) transactions in case data change is required • Display the number of contracts in different types on the FLP tile • Search desired data rapidly by using the flexibly adaptable filters
User can also run a free text search on the following fields in the app: • Trading Contract Number • Trading Contract Type • Contract Status • Counterparty • Incoterms • External ID • Original Trader ID • Amending Trader ID
Supported Device Types • Desktop • Tablet • Smartphone
Based on GAR requirements, we need to extend the Approve ACM Trading Contracts app. For this purpose, the following extensibility options are available which will be utilized:
--- 第79页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 79 of 215
Extensibility Entities Extension Points for ACM – Traders have the following extension points are available:
Table 3.19 - Extension Points View Extension Point Use ContractDetail.view.xml extContractDetailSections Allows you to add new section on contract detail screen. ContractItemDetail.view.xml extItemDetailSections Allows you to add new section on contract item detail screen. If there are additional fields available in the OData service, we can display these fields on the UI e.g. Prepayment details related to the contract. In case the values are not available we need to: A. Extend the FIORI Apps B. Create a custom Report.
3.2.3.14 Adding Notes on Contract Header or Line Items In SAP Agricultural Contract Management (ACM), notes functionality provides a flexible way to add textual information at both contract header and line item levels. This capability is implemented through a reusable Fiori component that allows for structured text management across different contract types.
Figure 3.24 - Adding Notes on Contract Header/ Item
--- 第80页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 80 of 215 3.2.3.15 Adding Attachment to Contract SAP Agricultural Contract Management (ACM) provides comprehensive attachment functionality that allows users to add file attachments and URL links to trading contracts at both header and line-item levels. This capability enhances contract documentation and supports the complete contract lifecycle management process.
The attachment functionality extends to individual contract line items, allowing for granular document management at the most detailed level of the contract structure. This enables traders to attach specific documentation relevant to particular commodity items or contract terms.
Figure 3.25 - Adding Attachment to Contract 3.2.3.16 Backstop Requirement Details For backstop scenarios there are 3 major changes executed in the trade capture. These are: • A custom Workcenter to be able to generate intercompany contract between the relevant stakeholders. • Ability to link multiple contracts to particular back stop flow. • A backstop ID filed in the contract which can be only updated by a backstop Workcenter. Please refer to Backstop Process Blueprint for further explanation of Backstop.
--- 第81页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 81 of 215 3.3 Prepayment Management 3.3.1 Highlighted Key Business Requirements
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
ACM-228 Ability to track and allocate prepayments
- Track all prepayments against overall contracts
- Draw down prepayments as deliveries occur
- Default unutilized prepayment as deduction against
delivery invoices
- Allow adjustment of prepayment utilization
- Make unutilized prepayment balance available for
next delivery
- Move orders from prepayment contracts into hold
status until funds received
- Support multiple prepayments on one contract
- Capture down payments for both purchases and
sales
- Support multiple down payments for single
contracts
Fit
Report to be developed
ACM-229 Ability to manage down payments:
- Process down payment invoices for PO
transactions
- Process down payment invoices for Non-PO
transactions
- Process down payment invoices for trading
products
- Track that 95% of sales are cash advance
- Monitor the 5% on credit terms
- Manually allocate a single down payment against
multiple deposits
Gap
Part of Prepayment
Solution
ACM-732 Ability to configure prepayment terms and dates
Fit
Standard ACM
functionality and
configuration. Will be
addressed during
project implementation
ACM-734 Ability to generate prepayment summaries across
multiple contracts with counterparty details
Gap
Exact requirements for
the report to be
addressed using
custom development
ACM-748 Ability to link prepayments to actual deliveries and
net off during settlement
Fit
PPR can be added at
Nomination instead of
Contract if quantity
tracking is needed.
ACM-757 Ability to generate prepayment invoices at contract
level with breakdown by shipment
Fit
PPR can be added at
Nomination instead of
Contract if quantity
tracking is needed.
Also linked ot CTRM-
3065. to be discussed
and tested together
ACM-783 Ability to manage prepayment requirements for
purchase transactions, particularly for sugar trade
Fit
Standard Solution
Behavior
--- 第82页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 82 of 215
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
ACM-784 Ability to track and manage margin money payments
throughout contract lifecycle with automatic
adjustment at final lifting
Fit
China Margin
Management. Part of
KDD Solution
ACM-808 Ability to create different prepayment document
types to model various deposit types with rules for
linking to single or multiple sales contracts
Fit
Prepayment Agreement
can be used
ACM-840 Ability to link multiple advance payments to a single
contract OR distribute a single advance payment
across multiple contracts, with functionality to track
payment-to-contract relationships and adjust excess
payments to future contracts
Fit
Multiple advances on
the same contract =
prepayment Requests
Single advance for
multiple contracts =
prepayment
agreements
ACM-841 Ability to configure prepayments as noted items for
proper invoice generation and netting
Similar with ACM-1412
Fit
This is a Company code
level configuration and
applies to both
Purchase and Sales
sides alike
ACM-866 Ability to generate Commercial Invoice Print Out
when Advance Payment has been received.
Gap
Form output
ACM-1001 Ability to input prepayment percentage at contract
capture level, and auto-calculate the prepayment
amount as well as the applicable VAT tax
OTB-340:
Down payment calculation is based on quantity, to
avoid any rounding issue.
Gap
Prepayment
Percentage Field needs
to be added at Contract
Level to auto-calculate
the Prepayment
Amount and Applicable
VAT. This is applicable
for both Purchase and
Sales
ACM-1004 Ability to limit the prepayment amount to the contract
total value (while taking into account VAT as well).
Prepayment amount shouldn't exceed contract value
Fit
Exist in Standard
Functionality
ACM-1009 Ability to submit a prepayment request for approval
process and to be further processed for payment /
Incoming without posting to a GL account (e.g.
Currently utilize a posting to noted items upon
approval of prepayment / DP request)
Advanced Payment amount (during posting) should
not contain the tax amount
The prepayment request posting as noted Items
shouldn't contain the tax amount.
Relate to: OTB-086
Fit
Exist in Standard
Functionality. Indonesia
will use the Noted Item
Approach for the
Prepayment
ACM-1010 Ability to have the correct recon accounts
information (material account, service account,
and/or project account) for each prepayment request
Fit
Exist in Standard
Functionality. Change
Configuration from ACM
to required GL Account.
ACM-1021 Ability to show on line item level for each
prepayment: Prepayment Base Amount, VAT
Gap
- Possibility to enter
Quantity Percentage
--- 第83页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 83 of 215
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
Amount, and Total Prepayment Amount in the
Prepayment Request Tab
- Split the Base Amount
and VAT Amount
- Prepayment Quantity
Determination
ACM-1036 Ability to generate proforma invoices for custom
declaration. This Proforma Invoice should be able to
be generated as soon as possible to accelerate the
customs process required for export transactions.
OTB-314: Print out invoice for Export Transaction
Declaration
Fit
Exist in Standard
Functionality. Manual
DN from Finance
ACM-1042 Ability to accommodate multiple downpayment
process for purchase transactions with separate
approval process for each downpayment.
Fit
Exist in Standard
Functionality. Release
for Settlement can be
utilized as approval
process.
If the release for
settlement is not
marked it will not be
availabe for posting the
prepayment.
Security Authorization
can be used
ACM-1043 Ability to attach documents (ex. Bill of Lading / BL)
to a Down Payment Request for Approvers to review
prior to Approval and Payment Processing
Gap
Enhancement at
Maintain Prepayment
Request
ACM-1044 Ability to have 2 types of purchase prepayment:
- Contract-level Prepayment (1x DP, Multiple DP)
- Prepayment based on netting against Prepayment
Balance with a specific vendor (ex. GAR places IDR
50 Bio prepayment balance on a vendor and for
each contract 90% of the contract value will be
netted off with the Prepayment Balance until the
balance is depleted)
Fit
- Contract-level
Prepayment can be
accomodated by basic
Prepayment request.
- Prepayment Balance
with Vendor using
Prepayment Agreement
Functionality in ACM
ACM-1045 Ability to have 2 types of sales prepayment:
- Contract-level Prepayment (1x DP, Multiple DP)
- Prepayment based on Sales Order quantity (1
Prepayment per Sales Order) - Biodiesel
For Export Fatty Matter, there are condition where
contract qty is e.g. 100, but SO/ delivery is 50-50
(partial shipment). Then the DP is collected based
on the SO/ delivery quantity (@50).
Need to generate the Prepayment Request/ DP
billing according to the shipment quantity (split
prepayment request line item)
If Sales Contract TOP = DP x%, then the Term of
Payment is DP x% as stated on the contract. In case
of non-priced contract for Biodiesel, As-Is contract
still need to be priced with latest price. When the
Fit
- Contract-level
Prepayment can be
accomodated by basic
Prepayment request.
- However,
enhancement will be
required to integrate SO
with Prepayment
Request
--- 第84页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 84 of 215
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
updated price is available, need to update the price
in the contract as well.
ACM-1046 Ability to clear Customer Down Payment Advance
and VAT Out Clearing Account based on Incoming
from Customer
Fit
This could potentially be
accommodated through
FI since FI will be doing
the posting
ACM-1047 Ability to accommodate partial DP payment (or split
payment) from Customer and create the necessary
DP Billing for the customer
e.g. sales contract prepayment request 90%, but
customer only pay 50%, then 40% in another day
Fit
Exist in Standard
Functionality
But Potential
Workaround can be
done where
Prepayment Request is
posted only after
Incoming is received
ACM-1211 Ability to add approval process for Prepayment
"Release for Settlement" process at Contract.
at Contract Page when changing checkbox "Release
for Settlement" add Approval Process (contract
amendment) to replace existing Prepayment
Approval process. the reason because this action
trigger Prepayment Request.
After "Release for Settlement" saved, auto-post
Noted Item based on PPR.
Gap
Prepayments. Release
for Settlement can be
utilized as approval
process.
If the release for
settlement is not
marked it will not be
availabe for posting the
prepayment.
Security Auth can be
used
ACM-1229 Ability to show information regarding Prepayment
(request, amount, status) on Contract Page
Relate to CTRM-1225
Gap
Create/copy fiori and
modify. can make use
of Release for
settlement field
ACM-1282 Ability to setup multiple approver (or delegate
approver) for Prepayment Approval.
Relate to: CTRM-1276
Fit
Exist in Standard
Functionality. Release
for Settlement can be
utilized as approval
process.
If the release for
settlement is not
marked it will not be
availabe for posting the
prepayment.
Security Auth can be
used, based on the
Sales Division
ACM-1290 Ability to process outgoing prepayment request, with
specific tax invoice & tax posting treatment for OTP
non OTP vendor
Relates to CTRM-1002, CTRM-1279, CTRM-1280,
CTRM-1289, CTRM-1290
Gap
Prepayment with Tax ,
based on OTP and Non
OTP enhancement this
req must be addressed
--- 第85页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 85 of 215
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
ACM-1291 Ability to process incoming prepayment from
customer & create DP billing & final billing+ tax
invoice
For Sales to Kaber area, need to input AJU Number
in the create Settlement step and ensure this
information flows to the Billing header text field in
VF01 to be printed in the Billing form output.
Relate to OTB-085
Fit
Exist in Standard
Functionality. ACM is
for proforma invoice
only, actual billing for
DP billing + Final billing
happen in SD/FI side
ACM-1326 Ability to generate form outputs similar to e-deal slip
and memo payment to be printed out and sent to
Payment Processing Team
Gap
Form Solution
ACM-1372 Ability to determine O/S Qty % compared to Total
PO Qty
Gap
This will be a gap, PPR
is recorded , processed
and settled in terms of
amount and not directly
linked to quantity
ACM-1373 Ability to determine the outstanding PO status (O/S
Del, UM Bulk)
Gap
Custom PPR Report
ACM-1374 Ability to determine PO Status based on aging
(current or overdue)
Gap
Custom PPR Report
ACM-1398 Ability to auto generate Sequence number for
Proforma Invoice. This is applicable for local and
export (for export, this is typically used to generate
PEB)
Gap
Enhancement required
for Number Range in
Billing as per the req
ACM-1408 Ability to accommodate prepayment balance with
certain vendors. (e.g. we paid a prepayment to a
vendor that is applicable to multiple purchase
contract until fully depleted)
Prepayment paid to vendor based on agreement on
vendor level, not contract level
Gap
Customize/ Enhance
current Prepayment
Agreement Solution to
cater with business
requirements
ACM-1412 Ability to post to Noted Item Accounting Posting for
Prepayment without including VAT Tax
Related to CTRM-1009
Fit
SAP Prepayment
Standard Behavior
ACM-1421 Ability to retain the same Proforma Invoice number
for all Export Sales Transaction, and retain the same
SO Number (Nomination) for Local Sales
Transaction from Bonded zone area, even when the
relevant doc flow are reversed. This is due to the
number submission to government for tax
requirement (Export supporting docs for Export
declaration, Surat Setoran Pajak/ Tax info for
bonded zone)
Gap
Prof invoice number
generated from
Contract (number is not
change)
SSP refer to the
Contract number.
Create Nomination =
As-Is SO
Confirm Nomination =
As-Is DO
ACM-1426 Trigger workflow and notification in SAP Workflow
Inbox/ SBWP to CBS Finance/ back office team to
process task:
e.g.
Gap
Custom Workflow
--- 第86页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 86 of 215
Req. No Business Requirement
Requirement
Analysis (Fit/Gap) Solution
- for purchase prepayment noted item & all payment
request, need to trigger workflow to SAP inbox to
BO/I2P invoice team to review
- for sales prepayment, trigger workflow to BO Sales
Team to print DP Billing & Cash App Team to clear
incoming
- for sales contract approval trigger workflow to
create nomination,
- for load qty with final delivery indicator, trigger
workflow to BO Sales Team to create Settlement &
Billing,
etc.
--- 第87页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 87 of 215 3.3.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.3.2.1 Maintain Prepayment Request at Contract
Figure 3.26 - Maintain Prepayment Request
Table 3.20 - Maintain Prepayment Request
Process Steps
Roles
Transaction
Code/Fiori App ID
Description
Select Maintain ACM
Contract Fiori App and
Enter Contract
Selection Criteria or
click on Create button
to create a New
Contract
Trader
(ACM)
WB21 or WB22/
Fiori Application:
Maintain ACM
Trading Contract
Can directly filter ACM contract based on
contract Payment Terms.
Enter Contract Details
for New Contract or
Contract to be
Referenced
Trader
(ACM)
WB21 or WB22/
Fiori Application:
Maintain ACM
Trading Contract
For Selected Contract
Enter Prepayment
Request Data at
Contract Line Item
Trader
(ACM)
WB21 or WB22/
Fiori Application:
Maintain ACM
Trading Contract
Details Required:
1. Terms of Payment
2. Prepayment Type
3. Prepayment Amount
4. Prepayment Date
5. Prepayment Currency
Save Prepayment
Request at Selected
Contract
Trader
(ACM)
WB21 or WB22/
Fiori Application:
Maintain ACM
Trading Contract
Prepayment Request details saved on
Contract
--- 第88页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 88 of 215 3.3.2.2 Maintain Prepayment Agreement
Figure 3.27 - Maintain Prepayment Agreement
Table 3.21 - Maintain Prepayment Agreement Process Steps Roles Transaction Code/Fiori App ID Description Create Prepayment Agreement Trader (ACM) Maintain Prepayment Agreement Trader defines and maintains the prepayment terms for upcoming contracts. Settle Prepayment Agreement Trader (ACM) Maintain Prepayment Agreement Agreement is settled to make prepayment funds available for use. Payment (Advance) Back Office (ACM) F110 Back Office processes advance payment through F110.
--- 第89页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 89 of 215 Process Steps Roles Transaction Code/Fiori App ID Description Create Agricultural Trading Contract (Purchase 3rd Party) Trader (ACM) WB21/WB22/ Fiori Application: Maintain ACM Trade Contract Trader creates purchase contract for 3rd party using ACM transactions or Fiori app. Price Agricultural Trading Contract (Purchase 3rd Party) Trader (ACM) WB22/ Fiori Application: Maintain ACM Pricing Trader updates and confirms pricing details for the purchase contract. Assign Prepayment Agreement Trader (ACM) WB22/ Fiori Application: Maintain ACM Pricing Linked prepayment agreement is assigned to the priced contract. Approve Agricultural Trading Contract (Purchase 3rd Party) Trader (ACM) WB22/ Fiori Application: Approve ACM Trading Contract Trader approves contract for execution and downstream processing. Create Nomination Scheduler (ACM) O4NM Scheduler captures delivery and shipment details for the contract. Maintain Load Data Capture Logistic & Operation (ACM) /ACCGO/LDC_WC Logistics team records actual loading data for goods movement. Create Settlement Back Office (ACM) /ACCGO/STL_WC Back Office consolidates pricing and quantity data to generate settlement. Consume Prepayment Agreement Back Office (ACM) - Prepayment amount is utilized against payable settlement. Release Settlement Back Office (ACM) /ACCGO/STL_WC Settlement is released for approval and financial posting. Approve Settlement Back Office (ACM) /ACCGO/STL_APQ Final settlement is approved by Back Office for closure.
--- 第90页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 90 of 215 3.3.2.3 Process Prepayment Request for Purchase
Figure 3.28 - Process Prepayment Request for Purchase
Table 3.22 - Process Prepayment Request for Purchase
Process Steps
Roles
Transaction
Code/Fiori App ID
Description
Identify Prepayment
Request Item
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trade Contract
Identify Prepayment Request Item on the
Contract Line-Item Level
Release Prepayment
Request
Trader (ACM)
WB21/ Fiori
Application:
Maintain ACM
Trading Contract
Mark Prepayment Request Item as
‘Released for Settlement’ on the contract
Level
Receive Sales
Contract from Vendor
Back Office
(ACM)
N/A
N/A
Verify SC from Vendor
against Our Purchase
Contract
Back Office
(ACM)
WB23/ Fiori Tile:
Maintain ACM
Trading Contract
(Display access
only) or Display
Trading Contract
Check Sales Contract from Vendor against
Purchase contract on Display Trading
Contract with corresponding contract
number
Follow-up to Vendor to
revise Sales Contract
(if not match)
Back Office
(ACM)
N/A
N/A
Receive Revised
Sales Contract
Back Office
(ACM)
N/A
N/A
Attach Vendor Sales
Contract to ACM
Purchase Contract
Back Office
(ACM)
WB22/ Fiori
Application:
Maintain ACM
Trading Contract
Attach Vendor Sales Contract as an
attachment on the Maintain ACM Trading
Contract with corresponding contract
number
Review and update
Prepayment Request
if needed
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trading Contract
If an update is needed:
Remove the ’Released for Settlement’ check
on the Prepayment Request item
--- 第91页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 91 of 215
Process Steps
Roles
Transaction
Code/Fiori App ID
Description
Update the amount
Check the ’Released for Settlement’ again
Post Prepayment
Request as Noted
Item
Back Office (ACM)
Prepayment
Request
Post/Reverse
Post Prepayment Request as Noted Item.
Release for Settlement + Contract
"Approved" status are the prerequisite for
PPR to be ready for posting. When these
two conditions are met, the transaction
Prepayment Request Post/ Reverse needs
to be executed for the posting to happen.
Detailed Process will be discussed in
detailed design.
Review Purchase
Prepayment Noted
Item
Back Office -
Payment Specialist
(ACM)
N/A
FI
Create & Approve
Payment Proposal
(F110)
Back Office -
Payment Specialist
(ACM)
F110
FI
Receive Prepayment
Invoice & Tax Invoice Back Office
N/A
FI
Scan Invoice & Tax
Invoice in VIM
Back Office
N/A
FI
--- 第92页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 92 of 215 3.3.2.4 Process Prepayment Request for Sales
Figure 3.29 - Process Prepayment Request for Sales
Table 3.23 - Process Prepayment Request for Sales
Process Steps
Roles
Transaction
Code/Fiori App
ID
Description
Identify Prepayment
Request Item
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trading Contract
Identify Prepayment Request Item on the
Contract Line-Item Level
Release Prepayment
Request
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trading Contract
Mark Prepayment Request Item as ‘Released
for Settlement’ on the contract line-item Level
Receive PO from
Customer
Back Office
(ACM)
N/A
N/A
Verify Sales Contract
against PO from
Customer
Back Office
(ACM)
WB22/W23/ Fiori
Tile: Display
Trading Contract
Check Sales Contract from Vendor against
Purchase contract on Display Trading Contract
with corresponding contract number
Follow-up to Trader to
revise Sales Contract
(if not match)
Trader (ACM)
N/A
N/A
Receive Revised
Sales Contract
Back Office
(ACM)
N/A
N/A
Attach Customer PO
to Sales Contract
Back Office
(ACM)
WB21/ Fiori
Application:
Maintain ACM
Trade Contract
Attach Vendor Sales Contract as an attachment
on the Maintain Trading Contract with
corresponding contract number
Generate Proforma
Invoice
Back Office
(ACM)
N/A
For each nomination/ delivery,
--- 第93页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 93 of 215
Process Steps
Roles
Transaction
Code/Fiori App
ID
Description
Print, sign, stamp &
send SC and
Proforma Invoice to
Customer
Back Office
(ACM)
N/A
N/A
Receive proof of SC
and Invoice Receipt
from Customer
Back Office
(ACM)
N/A
N/A
Inform Trader for
Prepayment Request
amendment
Back Office
(ACM)
N/A
N/A
Amend Prepayment
Request
Trader (ACM)
WB21/ Fiori
Application:
Maintain ACM
Trade Contract
Open Prepayment Request Item on the
contract Level
Release Prepayment
Request
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trading Contract
Release Prepayment Request Item on the
contract line-item Level
Post Prepayment
Request as Noted
Item
Back Office
(ACM)
Maintain
Prepayment
Request
Post Prepayment Request as Noted Item
Release for Settlement + Contract "Approved"
status are the prerequisite for PPR to be ready
for posting. When these two conditions are met,
the transaction Prepayment Request Post/
Reverse needs to be executed for the posting
to happen.
Detailed Process will be discussed in detailed
design.
Create DP Billing / DP
Tax Invoice and
Validate with Tax
Team
Back Office
(ACM)
N/A
FI
Send DP Billing and
Tax Invoice to
Customer & get proof
of receipt
Back Office
(ACM)
N/A
FI
Inform Prepayment
Completion to Back
Office
Back Office
(ACM)
N/A
FI
Settle Incoming with
DP Billing Number
Back Office
(ACM) / I2C
F-29
FI
Monitor FBL5N for
Incoming
Back Office
(ACM) / I2C
FBL5N
FI
Detailed Process will be discussed in detailed
design
Receive Incoming
Payment from
Customer
Back Office
(ACM) / I2C
N/A
FI
As-Is: GAR Indonesia is using F-29. For this
approach, users need to then go to the contract
to flag the payment received checkbox at
contract.
--- 第94页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 94 of 215 3.3.2.5 Process Prepayment Reversal All Reversal Scenarios (Prepayment, settlement, etc.), will be covered in Detailed Design phase.
--- 第95页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 95 of 215
3.3.3
Solutioning
3.3.3.1
Prepayment Requests on Purchase Contracts
This section will detail out the scenarios related to Prepayment Requests on the 3rd Party Purchase
Side. And next section for 3rd Party Sales Side.
•
Trader negotiates and records the Payment Terms on the ACM Purchase Contract. For
example: DP00.
•
Trader puts in a Prepayment Request entering the below details: Prepayment Amount,
Currency, Prepayment Date. Trader then checks the box ‘Released for Settlement’ and
saves the Contract.
•
The follow-on steps are done by the Accounting Team:
•
The back-office accounting team posts all the Prepayment requests that are set to
‘Released for Settlement’ as a Noted Item. A down payment request with a special GL
indicator = F.
•
Accounting team makes the Payment based on ‘Ok to Pay’ Status. Accounting team then
posts the accounting document ‘Payment Made’ for the amount paid with Special GL
Indicator = A.
•
The Status ‘Payment Made’ needs to be updated back on the Prepayment Request on the
Contract. GAR requested this to be automatic.
3.3.3.2
Prepayment Requests on Sales Contracts
•
Trader negotiates and records the Payment Terms on the Sales Purchase Contract. For
example: DP00, DP01, DP02.
•
Trader creates a Prepayment Request entering the below details: Prepayment Amount,
Currency, Prepayment Date. Trader then checks the box ‘Released for Settlement’ and saves
the Contract. Proforma Invoice can then be sent to the customer to request for Prepayment.
•
When the Customer send the requested amount, accounting team posts the accounting
document ‘Payment Received’ for the amount received with Special GL Indicator = A.
o
If amount Incoming prepayment amount matches with Prepayment request, back-office
accounting team will post the Prepayment requests that are set to ‘Released for
Settlement’ as a Noted Item.
o
If the amount does not match, back office team will amend the prepayment request and
re-set the prepayment request to “Release for Settlement” and post the Prepayment
requests.
o
A down payment request is posted with a special GL indicator = F.
•
The Back Office team can then settle the Noted Item against the Bank Incoming.
•
The Status ‘Payment Received’ needs to be updated back on the Prepayment Request on
the Contract. GAR requested this to be automatic.
3.3.3.3
Prepayment Recovery Step
In the current design, Account Receivables will get posted for the full amount and we do a clearing
using a custom program to net-off. Forms/PDF output can always be configured to what the business
needs.
3.3.3.4 Contract Cancellation or Closure for Paid Prepayment ACM Contract cannot be cancelled/ closed if there's any open prepayment request attached to it. To continue the contract lifecycle, the following are expected: 1. Receive incoming refund from vendor & clear with the Prepayment Account to knock off the advance (follow FI process). 2. Cancel the Prepayment Request (ACM) - might not be needed anymore/ prepayment already settled. 3. Close the Contract (ACM).
--- 第96页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 96 of 215 3.3.3.5 Prepayment 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.3.3.6
Prepayment Requests Journal Postings for Indonesia
3.3.3.6.1
Sales Prepayment Requests Journal Postings (ID)
Table 3.24 - Sales Prepayment Request Journal Postings for Indonesia
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
Prepayment
Received
Dr
Bank Balance
4.995.000
Standard
Cr
Bank Incoming
- 4.995.000
Noted Item Posting
Dr
Noted Item - Customer Advance
4.500.000
Standard
Incoming Prepayment
Clearing
Dr
Bank Incoming
4.995.000
Standard
Cr
Customer Advance
- 4.500.000
Cr VAT Out - 495.000
--- 第97页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 97 of 215
3.3.3.6.2
Purchase Prepayment Requests Journal Postings (ID)
Table 3.25 – Purchase Prepayment Request Journal Postings for Indonesia
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
Purchase Prepayment
Request Posted
Custom: Tax code determination in the Noted item from contract Dr
Noted Item - Vendor Advance 4.500.000
Custom:
1) segregation OTP & NOTP
Vendor
2) fetching Tax Code from
contract (ACM);
3) VAT posting to interim VAT
A/c (FI) for NOTP the tax
portion is posted to Vendor
Account with blocked for
payment indicator
Purchase Prepayment
Scheduled
OTP
Dr
Vendor Advance
4.500.000
Dr
VAT In (OTP)
495.000
Cr
Bank Outgoing (4.995.000)
NOTP
Dr
Vendor Advance
4.500.000
Cr
Bank Outgoing (4.500.000)
Dr
VAT In (NOTP)
495.000
Cr
Account Payables (Payment Blocked) (495.000)
Prepayment Paid
OTP
Standard FI Payment Run Dr
Bank Outgoing
4.995.000
Cr
Bank Balance (4.995.000)
NOTP
Dr
Bank Outgoing
4.500.000
Cr
Bank Balance (4.500.000)
VAT Reclass upon Tax Invoice Receipt (Custom Program)
Custom: 1) Reclass from VAT interim to VAT main (General) A/c (FI)
OTP
Dr
TBD
VAT In (General)
495.000
Cr
TBD
VAT In (OTP)
(495.000)
--- 第98页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 98 of 215
Transaction
Dr/Cr
GL Account
GL Description
Amount
Notes
NOTP
Dr
TBD
VAT In (General)
495.000
Cr
TBD
VAT In (NOTP)
(495.000)
Dr
TBD
Account Payables
495.000
Cr TBD Back Out (495.000)
--- 第99页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 99 of 215 3.3.3.6.3 Prepayment Reversal Note that Prepayment Reversal scenarios will be finalized during detailed design. Below figure are entries based on initial preliminary discussions.
To-be Indonesia - Reverse DP after Good issue partial
Transaction
Dr/Cr
GL Account
GL Description
Amount
Prepayment
Received
Dr
Bank Balance
5.550.000
Cr
Bank Incoming
- 5.550.000
Noted Item Posting Dr Noted Item - Customer Advance 5.000.000
Incoming Prepayment
Clearing
Dr
Bank Incoming
5.550.000
Cr
Customer Advance
- 5.000.000
Cr
VAT Out
- 550.000
Goods loaded (LDC)
Dr
GI NYB (Goods Issue Not-yet-Billed)
1.850.000
Cr
Inventory
- 1.850.000
Customer Billing (Settlement)
Dr
Account Receivables
5.383.500
Cr
Revenue
- 4.850.000
Cr
VAT Out (Clearing) - 533.500
Revenue Recognition Dr
COGS
1.850.000
Cr
GI NYB (Goods Issue Not-yet-Billed)
- 1.850.000
The first entry with actual unloaded Qty
FI posting Reclass posting for revised DP & Clearing previous DP Dr
Customer Advance
5.000.000
Dr
VAT out
550.000
Cr
Customer Advance
- 4.850.000
Cr
VAT out
- 533.500
Cr
Customer Advance
- 166.500
FI posting
Clearing VAT out to CTR
Dr
VAT out
533.500
Cr
VAT out
- 550.000
--- 第100页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 100 of 215 Dr
Est.Tax Refund-VAT
16.500
FI posting
Reclass Customer advance to other
payable
Dr
Customer Advance
166.500
Cr
Other payable
- 166.500
FI posting
Paid to Customer
Other payable 166.500
Bank out - 166.500
--- 第101页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 101 of 215 3.3.3.7 Prepayment Requests Journal Postings for Singapore 3.3.3.7.1 Sales Prepayment Requests Journal Postings (SG) Table 3.26 - Sales Prepayment Request Journal Postings for Singapore Transaction Dr/Cr GL Account GL Description Amount Notes
Prepayment
Received
Dr
Bank Balance
4.500.000 Standard
Cr
Bank Incoming
- 4.500.000
Noted Item Posting Dr Noted Item - Customer Advance
4.500.000 Standard
Incoming Prepayment
Clearing
Dr
Bank Incoming
4.500.000 Standard Cr Customer Advance - 4.500.000
--- 第102页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 102 of 215 3.3.3.7.2 Purchase Prepayment Requests Journal Postings (SG) Table 3.27 - Purchase Prepayment Request Journal Postings for Singapore Transaction Dr/Cr GL Account GL Description Amount Notes Purchase Prepayment Request
Dr
Noted Item - Vendor Advance 4.500.000
Purchase Prepayment Scheduling
Dr
Vendor Advance
4.500.000
Cr
Bank Outgoing (4.500.000)
Outgoing Prepayment Dr
Bank Outgoing
4.500.000
Standard FI Payment Run
Cr
Bank Balance (4.500.000)
--- 第103页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 103 of 215
3.4
Contract Management
3.4.1
Highlighted Key Business Requirements
Req.
No
Business Requirement
Requirement
Analysis
(Fit/Gap)
Solution
ACM-
068
Ability to close outstanding contract and put
necessary reason for closure
Relate to : ACM-1015 Fit Contract Cancelation or makring of final delivery in application workcenter can be used. ACM- 116 Ability to manage trade processing workflows, including: - Manage full lifecycle from creation to archiving - Generate and circulate confirmations (form outputs that need configured) - Process sign-offs and amendments - Convert documents and upload to platforms (PDF) - Track unsigned contracts - Apply to both physical and paper trades - Facilitate deal approval workflow: - Admin Traders enter fields and save transactions - Senior Traders review and approve each trade - Handle E-trade claims with contract number assignment - Enter & approve E-Deal Slips in SAP (for Purchase) - Create PO & payment settlement for export surveys (captured in expense management under surveyor expense) Gap Enhancement to be done based on req ACM- 189 Ability to generate trade confirmations: - Short form contract for physical trades (single template regardless of terms) - Addendum template for physical trades - Deal slip template for physical trades - Physical & swap short form trade confirmations - Generation of addendums to sales & purchase contracts Fit Contract Form / Amendment Functionality ACM- 240 Ability to process amendments: - Process amendments for physical trades - Implement appropriate validation steps - Perform Contract Value and Contract Price recalculation upon amendment
This is related to ACM-947 Fit Contract amendment functionality and can be utilized for price change ACM- 388 Ability to deliver quantities beyond the set tolerance (overfill scenario), with delivery documents requiring tolerance level adjustment
This is related to ACM-954 Fit Linking to contract available ACM- 389 Ability to configure form output to display initial contract quantity when reprinting contracts after closure. Gap Contract Forms ACM- 426 Ability to add or change contract optionalities after prepayment has been made, though with a Fit Prepayment Request
--- 第104页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 104 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution business recommendation to complete such changes before the nomination phase ACM- 756 Ability to formally close contracts with revenue recognition and automatic closure when executions complete Fit Depends on CTRM-3073. Discussion ongoing regarding Contract Closure ACM- 813 Ability to manually close contracts or automate closure based on final delivery completion Fit During project implementation, scheduling the background job ACM- 827 Ability to revise contract prices on the 1st of each month based on new corporate FX rates, applying updated prices only to undelivered quantities while preserving original FX-based prices for already delivered portions Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 828 Ability to automatically pass through FX rate fluctuations to customer prices at 1:1 ratio for undelivered quantities, with price adjustments calculated based on monthly corporate FX rate changes Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 068 Ability to close outstanding contract and put necessary reason for closure
Relate to : ACM-1015 Fit Contract Cancelation or makring of final delivery in application workcenter can be used. ACM- 116 Ability to manage trade processing workflows, including: - Manage full lifecycle from creation to archiving - Generate and circulate confirmations (form outputs that need configured) - Process sign-offs and amendments - Convert documents and upload to platforms (PDF) - Track unsigned contracts - Apply to both physical and paper trades - Facilitate deal approval workflow: - Admin Traders enter fields and save transactions - Senior Traders review and approve each trade - Handle E-trade claims with contract number assignment - Enter & approve E-Deal Slips in SAP (for Purchase) - Create PO & payment settlement for export surveys (captured in expense management under surveyor expense) Gap Enhancement to be done based on req ACM- 189 Ability to generate trade confirmations: - Short form contract for physical trades (single template regardless of terms) - Addendum template for physical trades - Deal slip template for physical trades - Physical & swap short form trade confirmations - Generation of addendums to sales & purchase contracts Fit Contract Form / Amendment Functionality
--- 第105页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 105 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 240 Ability to process amendments: - Process amendments for physical trades - Implement appropriate validation steps - Perform Contract Value and Contract Price recalculation upon amendment
This is related to ACM-947 Fit Contract amendment functionality and can be utilized for price change ACM- 388 Ability to deliver quantities beyond the set tolerance (overfill scenario), with delivery documents requiring tolerance level adjustment
This is related to ACM-954 Fit Linking to contract available ACM- 389 Ability to configure form output to display initial contract quantity when reprinting contracts after closure. Gap Contract Forms ACM- 426 Ability to add or change contract optionalities after prepayment has been made, though with a business recommendation to complete such changes before the nomination phase Fit Prepayment Request ACM- 756 Ability to formally close contracts with revenue recognition and automatic closure when executions complete Fit Depends on CTRM-3073. Discussion ongoing regarding Contract Closure ACM- 813 Ability to manually close contracts or automate closure based on final delivery completion Fit During project implementation, scheduling the background job ACM- 827 Ability to revise contract prices on the 1st of each month based on new corporate FX rates, applying updated prices only to undelivered quantities while preserving original FX-based prices for already delivered portions Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 828 Ability to automatically pass through FX rate fluctuations to customer prices at 1:1 ratio for undelivered quantities, with price adjustments calculated based on monthly corporate FX rate changes Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 1003 Ability to change receiving plant/location/port prior to prepayment processing using contract amendment Fit If contract is approved, we need to add a new line item on the plant field and remove the old one ACM- 1005 Ability to apply the correct profit center & Cost Center journal posting as per receiving plant including after contract amendment Fit If there is already an existing journal posting before contract amendment. These postings need to be reversed manually. In case the existing journal posting is not available, amendment can be done
--- 第106页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 106 of 215
Req.
No
Business Requirement
Requirement
Analysis
(Fit/Gap)
Solution
and posting will be done
afterward properly by
default according to the
updated value
ACM-
1015
Ability to auto-close contract after final settlement
has been completed after a set amount of time
e.g. close all outstanding intercompany contract > 3
months; close contract with qty < 1%, etc.
Fit
Batch Job can be
configured to auto-close
contract every week / end
of month
ACM-
1062
to have proper numbering to identify between
proforma invoice, down payment billing, and final
billing after quantity settlement
OTB-076:
Able to generate Document Sequence Number with
specific format. This document sequence number is
different with SAP document number.
Document:
- Contract
- Proforma
- Invoice
Example:
Contract Running Number :
Upstream
Contract : DIC/1050/091024/0002
DI= kode Distribution Channel --> DI, DT, XI, XT
C = Contract
1050 = Kode Sales org
091024 = DDMMYY
0002 = running number / no urut. --> reset annually
Billing : DII/1050/1024/00150 DI= kode Distribution Channel I = Invoice 1050 = Kode Sales org 1024 = MMYY 00150 = running number / no urut.
Downstream Indonesia Contract : LTC/3324/200125/0001 LT= kode Distribution Channel --> LT, ET C = Contract 3324 = Kode 2 angka comp code + 2 angka Sales org 200125 = DDMMYY 0001 = running number / no urut --> reset annually
Invoice : LTI/3320/0125/000250 LT= kode Distribution Channel I = Invoice 3324 = Kode 2 angka comp code + 2 angka Sales org 0125 = MMYY 000250 = running number / no urut. Gap Additional custom field required at contract to show additional customized numbering.
--- 第107页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 107 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1151 Ability to finalise existing trades with counterparties (take decision whether to continue the open transaction) who are no longer compliant / should not be traded with Gap Enhancement at Nomination/billing will prevent document creation ACM- 1166 Original Requirement: Generate approval template to credit risk manager when there is request to change TOP in the transaction. An email notification after contract approval, should be triggered if there is a discrepancy between the TOP in the transaction and the customer master data. The email will be sent only once, the first time the differing TOP is used in a sales order for that customer.
Frequency = 2-3 times/ month Gap Enhancement to validated TOP during contract approval and send notification to CR manager in case of change in TOP.
Logic need to be applied to check if previous notification has been triggered, to ensure only 1 time notification is sent. ACM- 1221 Ability to navigate to Nomination and LDC creation page from Contract Page without exiting Contract Page Fit Exist in Standard Functionality
Open in multiple tabs, usually contract, nomination & LDC is created by different roles ACM- 1232 Ability to amend contract price if market prices are not loaded to system. Fit Exist in Standard Functionality ACM- 1233 Purchase - Ability to identify and change the receiving plant in PO (in bonded / non-bonded zone) If prepayment has been collected & plant need to change from bonded to non bonded-zone, need to accommodate the tax adjustment collection & posting. Fit Exist in Standard Functionality
Optionality can be utilized
ACM-
1234
Ability to add Approval for Mass Contract
Cancellations
Fit
Exist in Standard
Functionality. Amendment
functionality
ACM-
1235
Ability to perform Mass Cancellations based on
Residual Quantity
Fit
Exist in Standard
Functionality
ACM-
1236
Ability to do Reversal of Contract Cancellations
Fit
Exist in Standard
Functionality
ACM-
1237
Ability to add Reason / Remarks for Contract
Cancellations
Fit
Exist in Standard
Functionality
ACM-
1239
Ability to run a report which shows all changes
made to open contracts and associated PnL impact
by region/desk/contract
Gap
Exist in Standard
Functionality. Custom
report
ACM-
1240
Ability to track outstanding quantity as a percentage
of Total Contract Quantity (Purchase & Sales)
Gap
add functionlaity for
percentage. Contract qty
type option can be used
where you can see the qty
details
Position report (custom)
--- 第108页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 108 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM- 1241 Ability to view Contract End to End Lifecycle (Contract Amount & Qty, Payterm, Prepayment Amount & Qty, BLs, Delivered Qty, Billed Qty, Outstanding Amount & Qty, etc) Group by Bulk (Palm, Lauric, Biodiesel) and SemiBulk
As-Is : Contract- SO-DO-GI-Billing (custom report) Gap
Custom report ACM- 1242 Ability to track the overall purchase contract realization (total contract value, Prepayment amount (and remaining), GR Amount, and how much has been payment has been processed/paid) Gap
Custom report ACM- 1243 Ability to track the overall sales contract realization (total contract value, DP amount (and remaining), GI Amount, Billed/Unbilled amount) Gap
Custom report ACM- 1244 Ability to monitor contract status: - Follow up on outstanding sales contracts with customers - Comprehensive report of contract including: * Quantity * Commodity * Transportation mode * Pricing information Gap Custom report ACM- 1247 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 Gap Form Solution ACM- 1340 Ability to control, which field are still allowed to be updated/ contract amendment with re-approval (non commercial impact), which field are not allowed to be amended & need to cancel/ create new contract (have commercial impact) Fit ACM does allows selection of fields trggering the snapshot functionality causing the status to be updated to amended requiring re-approval ACM- 1413 Ability to change Contract Price even after LDC for payment terms: Credit (No Prepayment) e.g. In Biodiesel, sometimes we haven't received the price for BBM / BBN during trade contract creation, traders need to update the price once the gov't has published the new price for the applicable month. So sometimes we have to ship the goods before the price has been finalized Fit SAP Standard Behavior ACM- 1415 Ability to accommodate the following Scenario: - Purchase scenario: SMART buys FOB (pick up goods from Load Port, but then during delivery (ship has loaded the goods), counterparty or destination port must be changed due to stock level consideration.
note(ch) : consider both scenario of port change during sales transaction, within same sales org / Fit Cancel and recreate the contract and change counterparty/company code
--- 第109页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 109 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution company code and different sale org / company code ACM- 1429 Ability to generate report for supplier evaluation performance by formula (quality, gain/loss quantity, delivery, Quantity per month, Sustainability, Fraudness)
As-is: this report is consolidated manually, purpose for this report is for Management Review Unit. Sample report is provided and available in Sharepoint Gap Custom Report ACM- 1436 Need to inform Operation team upon contract amendment/ cancellation, to amend/ cancel the relevant customs documents Option 1: Authorized operational team to access contract (view only), As-Is the operation team access PO from ME23N -> need to confirm with Bu Yenti Option 2: Trigger notification output for the contract approved/ amendment/ cancellation (via email) Gap Form Output ACM- 1442 Extract all As-Is existing & actively used RICEFW in SAP ECC (EDM, SD, MM, FI), need to be available in the To-Be solution, in example: - Material UoM & conversion calculation (e.g. for Biodiesel 0,87 kg = 1 Litre) - All document numbering convention/ sequencing - All existing Approval, Workflow, Print Output, Reports - etc. Gap Retrofitting can be done. Analysis is required alongside with the previous report. But it will be a different effort
--- 第110页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 110 of 215 3.4.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.4.2.1 Contract Amendment
Figure 3.30 - Contract Amendment Table 3.28 - Contract Amendment Process Steps Role Transaction Code/Fiori App ID Description Enter Contract Details for the Contract Trader (ACM) WB21/ Fiori Application: Maintain ACM Trade Contract Trading Contract Status “Approved” to be amended Amend Contract Details Trader (ACM) WB21/ Fiori Application: Maintain ACM Trade Contract Amend Contract Details: • Prices • Expenses • Fees • Prepayment • Documents Attached • Override DPQS • Custom Fields Save Contract Amendment Trader (ACM) WB21/ Fiori Application: Maintain ACM Trade Contract For Amendment Relevant Fields, Contract Status changed to “Amendment Approval Required” while non-amendment relevant fields would not require additional approval.
--- 第111页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 111 of 215 3.4.2.2 Cancel or Close Agricultural Trading Contract
Figure 3.31 - Cancel or Close Agricultural Trading Contract
Table 3.29 - Cancel or Close Agricultural Trading Contract
Process Steps
Role
Transaction
Code/Fiori App
ID
Description
Enter Contract
Selection Criteria
Details
Trader (ACM)
WB21/ Fiori
Application:
Maintain ACM
Trade Contract
Filter contract criteria details to cancel/ close.
Close Contract
Trader (ACM)
WB22/ Fiori
Application:
Maintain ACM
Trade Contract
Change contract status to “Closed”. Only
authorized personnel can close a contract.
Contract closure should be done for:
•
If user needs to remove the contract
from risk reporting
•
If the contract is fully consumed
Contract closure cancels any remaining open
quantity.
Contract closure can be done in mass, while close contract can be reopened individually. Cancellation of Contract Trader (ACM) WB22/ Fiori Application: Maintain ACM Trade Contract • Select line item having open quantity to be cancelled • Cancellation can be full quantity of the line item or partial quantity • Cancellation can be done with cancellation fees • Post setting the status of contract to cancelled, business can decide if the contract can be pulled into risk reporting for the realized part.
--- 第112页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 112 of 215
3.4.3
Solutioning
3.4.3.1
Contract Statuses
Multiple contract statuses can be configured based on business requirement. Furthermore,
cancellation codes can be maintained which are relevant for trading contract cancellation. The
following statuses are provided by default
Figure 3.32 - Contract Statuses
However, for GAR, the following contract statuses would be configured as below. Please see the status behaviour can be updated based on user inputs.
Table 3.30 - Contract Statuses
Status
Details
Reporting
Relevant
Logistic
Execution
Draft
•
This is the default status whenever a new contract
is created
•
Draft contract is not picked for reporting or any
subsequent logistic execution
X
X
Awaiting
Amendment
Approval
•
This is the status for the contract where changes
are made to the amendment relevant fields post
contract approval
•
A contract in this status is not picked for reporting
or any subsequent logistic execution
X
X
Amendment
Rejected
•
This is the status for the contract where the
changes are rejected by authorized personnel, and
this can only happen post-Awaiting Amendment
Approval
•
A contract in this status is not picked for reporting
or any subsequent logistic execution
X
X
Trader
Approved
•
This is an intermediary status which informs the
validation done by the trader and approval is
needed from I2C for subsequent logistic execution
X
X
--- 第113页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 113 of 215
3.4.3.2 Contract Amendment The meaning of Contract Amendment in ACM is to change details in the contract (e.g., price, quantity) without changing the contract number.
Contract Amendment Preconditions Any changes to contract details that are amendment relevant or not should obey contract amendment constrains as below: 1. Contract status should be “Approved”. 2. Check if commodity line-item quantity equal to contract item quantity, if not, amendment can't be made. 3. Check if application document exists for the contract, if exists, then cannot change the settlement currency of the contract. 4. Check if call-offs exists for the contract, if yes, then can't change tolerance type/ optionality header and details data. 5. Check if sufficient open quantity for contract amendment, if not sufficient, amendment can't be made. 6. Check if application document/ settlement has been done, if amendment also needs to be reflected on the respective follow-on document, those documents needs to be reversed.
Amendment Relevant Changes
The specific amendment fields that require re-approval will be defined and finalized during the detailed
design phase. When changes are made for contract that has been created and approved, the system
may mark the contract status as “Awaiting Amendment Approval”. Below are important points for
contract with this status:
1. This will require re-approval and regenerate output.
2. Contracts can be individually, or mass approved/rejected via standard Fiori Applications.
3. Contract with missing or invalid fields will trigger errors on approval.
4. System will ensure only valid contracts are processed.
5. There will be no notifications of Contract Amendment in case the respective Contract is being
opened by another user, amended contract needs to be closed and re-open / refresh contract
page to reflect the changes.
•
This is a custom status and contract having this
status will not be picked for reporting or any
subsequent logistic execution
•
SG/DO may not require this status
Approved
•
A contract once approved will be picked for
reporting and subsequent logistic execution
Y
Y
Cancelled
•
This is the status for the contract whose quantity is
cancelled and is no longer expected for subsequent
logistic execution.
X
X
Closed
•
This is the status for the contract which is no longer
required for reporting or logistic execution purposes
•
There is no open quantity in this contract
X
X
Completed
•
This is the status of the contract which has no open
quantity and is outside the commodity period
•
This contract cannot be used for subsequent
logistic execution
Y
X
--- 第114页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 114 of 215 Table 3.31 - Trade Capture Matrix Field (Non-Exhaustive) Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Contract Ref DRAFT_XXXX Custom. Search based on this Contract Ref, Flow to all follow-on documents, reporting Yes Header Custom Custom Field on Header Level refer to Sequence Number Contract Date 24-Feb-23 Document Date - Initially same as contract creation date. Useful for backdate for forms & reporting Yes Header Yes Refer to Document date on header level, initially same with contract creation date. Standard. In-case not right behaviour, we will custom.
Contract creation date will be automatically generated in Administration Tab on Contract Header level Trading Time (24HH:MM) 17:30 Contract Creation Time - Standard No Header - Check purpose of this whether it is used for trading pricing purposes
Contract creation time will be automatically generated in Administration Tab on Contract Header level. Seller* ABC_AGRO_LESTARI_BANGKA Counterparty - Standard Yes Header Yes Header Level Field. Counterparty.
--- 第115页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 115 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Seller Ref
Customer PO - Standard No Header Yes Header Level Field Buyer * BPSD Counterparty - Standard Yes Header Yes Header Level Field. Counterparty. Buyer Ref
Customer Reference - Standard Yes Header Yes Header Level Field Broker * (DIRECT) Partner Function - Standard No Header/ Item Yes Broker to be Partner function Broker Ref
Partner Function - Standard No Header/ Item Yes Broker to be Partner function Contract Type * PHYSICAL Contract Type - Standard Yes Header No Contract type is to be decided during creation of contract and will show at administration tab on contract header level Profit Center * TRADING PALM Will follow EDM Definition of Enterprise Structure for Profit Center No Header Definition of Profit Center is the area of EDM Contract Pricing Origin NA (to be : market price) Valuation Point - Standard Yes Item Yes Standard Valuation Point
--- 第116页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 116 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Commodity * CPO Material can be added linked to a commodity. Multiple material can be added to one commodity Yes Item Yes Use material - Standard Commodity Description * CRUDE PALM OIL Material description - Standard Yes Item Yes Use material description - Standard Commodity Brand Name * 80000001 Material code - Standard Yes Item Yes Use material code - Standard Packing Opts * BULK, Container, Flexibag, Isotank, Carton, Returnable Foldable Steel IBC, Truck Tanker Custom Field Yes Item Custom Country Specific - ID Estimated Delivery Date * (Shipment Period) 24-Feb-23 Start date and end date on Item Level - Standard Yes Item Yes We have commodity start date and end date on Item Level - commodity tab and it is manually input Basis (Incoterm)* FOB Standard - Incoterm Yes Header Yes Incoterm is available on Header level - basic data tab. Manually input or maintain in BP and will be auto generated Loading Port BELINYU Location - Standard No Item Yes Optionality tab at Item Level for Load Location
--- 第117页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 117 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Discharge Port BOOM BARU Location - Standard No Item Yes Optionality tab at Item Level for Discharge Location Pricing Basis * (OUTRIGHT) ACM Basis Component No Item Yes Pricing tab at Item level. Can be priced later - before settlement (provisional) - after priced (final) Currency IDR Document Currency - Standard Yes Header Yes Document currency is at header - Basic Data tab Price (KG) 10000 Pricing Currency - Standard No Item Yes Pricing tab at Item level. Can be priced later - before settlement (provisional) - after priced (final). Additional enhancement for adjusting price per 100KG
There could be a different pricing/UoM such as USA is
--- 第118页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 118 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail LBS, and Pakistan is using TON Payment Terms * DP00 Payment Term - Standard Yes Header Yes Payment Term is available on Header level - basic data tab Tax Free * No
Utilize Tax Code.
Tax Free will be indicated by using specific Tax Code for No Tax. Tax Code * VM Custom
Custom Quantity (MT) * 10.000 Standard Yes Item Yes Overview Tab at Item level Area Code * DT01/RJ2 Standard Yes Header No Purchase Org/ Purch. Area or Sales Org/ Sales Area is needed at contract creation and will be displayed at header level - Administration tab Stock Locations / Plant * BLDL BANGKA TI10 Plant & Storage Location - Standard Yes Item Yes At contract mandatory for Plant. Storage Location can be provided at LDC level. Or ideally at Item level of contract so not mandatory.
Plant and Enterprise Setup for SG will be detailed down on the detail down during the detailed discussion phase.
--- 第119页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 119 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Custom Terms Delivery Remark : Loss Tolerance: Other Terms: Standard - Texts No Header/ Item Yes Standard - Texts Tolerance % * 2 Standard - Tolerance tab Yes Item Yes Tolerance tab at item level. Input manually Discount/Premium Value
Standard - DPQS tab Yes Item Yes DPQS tab at Item level. Input manually Pre Advice Details
LP Days 30 LP = Late Penalty DPQS DPQS Yes Will use Standard DPQS Vessel Nomination Days 14 Standard - Texts No Header/ Item Yes Standard - Texts Tender Days 10 Standard - Texts No Header/ Item Yes Standard - Texts Shipment Extention Not Allowed
Additional (Optional) Ports BELINYU Optionality - Standard No Item Yes Optionality Additional (Optional) Specifications CPO - FFA 5% MAX DPQS - Standard - Master Data No Item Yes DPQS Not in CxC
Commodity Certifications (Type) RSPO, EUDR Custom Field No Header Custom Custom Additional Notes
Standard - Texts
No
Header/
Item
Yes
Standard - Texts
Fees
Broker, Load/Unload Fee, Freight
Charges, Insurance Fee,
Surveyor
Fee - Standard
No
Header/
Item
Can be added as per req Expenses Export Duty / Levy Expense - Standard No Header/ Item
Can be added as per req
--- 第120页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 120 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Allocated / Non Allocated
Custom PSO / Non PSO TBC (PSO : selisih harga + ongkos angkut --> ditanggung Non PSO : ongkos angkut --> ditanggung (wacana))
PSO
1. Jika HIP BBM < HIP BBN + OA
= Billing ke customer harga HIP
BBM, dan ada claim BPDP untuk
selisihnya --> Harga yang
tercantum di Kontrak = Harga
HIP BBM
2. Jika HIP BBM > HIP BBN + OA
= Billing customer harga HIP
BBN + OA, tanpa ada claim
BPDP --> Harga yang tercantum
di Kontrak = Harga HIP BBN +
OA
Custom Field to flow up
until billing
Yes (for
Biodiesel)
Header
Custom
Custom. ID Country Specific
Distribution Date
(Period
Penyaluran)
Custom Field to flow up until billing Yes (for Biodiesel) Header Custom Custom. ID Country Specific Subsidized / Non Subsidized
Custom External Reference ID
External Identifier - Standard No Header Yes Standard
--- 第121页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 121 of 215 Point of Change (* = Mandatory Field)
Sample Value To Be ACM Mandatory Field? Level Possible to Change at Draft Status? Solution Detail Notify Party
Partner Function - Standard No Header Yes Standard Surveyor Details
Partner Function -
Standard. Used for
Surveyor Fee.
No
Header
Yes
MDG: Will be using BP -
Vendor Master Data.
Registry beforehand as
Vendor
Loadport Agent
Partner Function - Standard No Header Yes Standard Bank Details
Maintained and Approved via MDG MDG: Part of BP - Customer Master Yes Header Yes Header Level Field. Counterparty. Ideally Provided during customer creation Prepayment Percentage
Prepayment Percentage - Custom No Item Custom Custom Item Level - Prepayment Req Tab Prepayment Date
Prepayment Date - Standard No Item
Standard Item Level - Prepayment Req Tab From SAP ACM
Incoterm Location 1
Standard - BP Master Data. Not relevant during contract creation. Yes Header Yes Standard - BP Master Data Incoterm Location 2
Standard - BP Master Data Yes Header Yes Standard - BP Master Data Backstop ID - Number Based on Backstop
Custom No Header Custom Custom Trader Info Tab
Standard - Trader Info Tab No Header
Standard - Trader Info Tab
--- 第122页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 122 of 215 3.4.3.3 Reverting Subsequent Documents Revert subsequent documents means reversing all SAP-generated documents linked to the contract before it can be amended. These include: • Nomination • LDC (Load Confirmation) • Accounting postings (e.g., Settlement, Invoice) • Possibly: Sales Order (SO), Delivery, Goods Movement, PGI. These reversals are not always automatic — some require manual coordination across teams (e.g., Finance, Ops).
3.4.3.4 Contract Cancellations The meaning Contract Cancellations in ACM is to cancel the remaining / unconsumed Quantity that for some reason will not be delivered anymore. During Contract Cancellations, we can also add Cancellation Fee (if there are any). Contract Cancellations does not require Approval but required a specific role to execute. After Contract Cancellations we can still view Contract Report fields based on our configurations.
Figure 3.33 - Contract Cancellations
--- 第123页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 123 of 215 3.4.3.5 Contract Closure The meaning of Contract Closure in ACM is to change the status of Contract to “Close”, no further delivery can be done once the contract is closed. Closed Contract will not be considered for MtM, EoD Reporting. Contract Closure cannot be done while there are remaining qty, this qty needs to be cancelled first before Contract Closure.
Main Purpose of Contract Closure: • Hygiene & System Performance Closing completed contracts helps clean up open items in the system, preventing unnecessary processing and improving performance. • Reporting Impact Closed contracts are excluded from MTM, EOD, and unrealized P&L reports. Realized P&L can still reference closed contracts (since the realization is already done). Closure acts as a signal that the contract is fully executed and no longer relevant to future positions or P&L reporting. • Archiving Contract closure enables archiving activities and clears out contracts past their business relevance. When to Close Contract: In most cases, closing of contract is not to be done immediately upon completion. It is ideally done: • Monthly or quarterly, based on business volume and priorities. • Year-end if monthly closure isn’t feasible. Mass Contract Closure Automatic mass contract closure will automatically cancel any residual qty and close the contract. SAP recommends GAR to have a policy: e.g., close contracts with 0 open quantity + all settlement completed + no expected future activity. Contract closure should be part of routine operations, not just year-end clean-up. This batch job can also be triggered manually.
Contract Reopen Contract Reopen process will be used for Closed Contract. Upon Contract Reopen, system will check whether we want to reactivate cancelled qty as well (or to reverse contract cancellation qty), or just to change Contract Status to ‘Open’.
--- 第124页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 124 of 215 3.4.3.6 Contract Amendment, Cancellation, and Closure Difference Table 3.32 - Contract Amendment, Cancellation, and Closure Process Definition / Purpose Key Rules & Constraints Approval Requirement Impact / Notes Contract Amendment Changes details in the contract (e.g., price, quantity) without changing the contract number. Must pass Contract Amendment Preconditions:
• Commodity line-item qty = contract item qty. • Cannot change settlement currency if application doc exists. • Cannot change tolerance/optionality if call- offs exist. • Sufficient open qty must exist. • If amendment impacts follow- on docs, they must be reverted first. • System may mark as “Awaiting Amendment Approval.” • Requires re-approval & output regeneration. • Can be individually or mass approved / rejected via Fiori apps. • Contracts with invalid fields trigger errors on approval. • Snapshot triggered when trader changes fields. • System ensures only valid contracts are processed. • Amendments cannot proceed if follow-on docs not yet reversed. Contract Cancellation Used to cancel remaining / unconsumed quantity of the contract that will not be delivered anymore. May include cancellation fee if applicable. • Can cancel part or full open quantity. • Cannot cancel quantities already tied to subsequent processes (e.g., orders, deliveries). • Must specify cancellation qty, reason, and optional price. • Cancellations don’t always involve goods movement. • System may mark as “Awaiting Qty Cancellation Approval” • Requires re-approval (will follow contract creation approval matrix) • Requires a specific role to execute. • After cancellation, contract reports remain viewable as per configuration. • Quantity reduced but contract number remains the same.
--- 第125页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 125 of 215 Process Definition / Purpose Key Rules & Constraints Approval Requirement Impact / Notes Contract Closure Changes contract status to “Closed” → no further delivery allowed. Closed contracts excluded from MtM, EoD, and unrealized P&L reports. Enables archiving. • Cannot close contract if any open qty remains → must be cancelled first. • Typically done monthly/quarterly or at year- end (not immediately upon completion). • Mass Contract Closure batch job can automatically cancel residual qty and close contracts. • SAP recommends policy: close contracts with 0 open qty + all settlement done + no future activity. • No separate approval once criteria met (can be triggered manually or via batch job). • Improves hygiene & system performance by cleaning up open items. • Supports archiving and removes contracts from future processing. • Realized P&L remains linked to closed contracts. • Acts as a signal that contract is fully executed and no longer relevant for future positions or P&L reporting.
--- 第126页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 126 of 215 3.4.3.7 Maintain Contract Snapshot (i.e. Document Revision History/ Change Logs) Agricultural Contract Management offers Contract Snapshots, which capture specific data when saving a contract. These snapshots are created when the contract is in the appropriate status and serve as a reference for generating outputs. Each snapshot is timestamped, allowing for easy identification of changes over time. It enables tracking of changes that have been used in previous outputs and highlights which changes require a counterparty's signature.
The Contract Snapshots feature allows for the management and assignment of contract attributes that govern the creation of new snapshot versions. It facilitates the management of contract attributes that determine the relevancy of a counterparty's signature and tracks the signature status, such as "Signature sent to counterparty" or "Signature received." Different snapshot versions can be directly monitored in the contract maintenance transactions, providing a clear overview of contract history.
The functionality of Contract Snapshots can be leveraged to support custom form creations, such as contract amendments. Contract Snapshots capture specific data when saving a contract and can be configured to send notifications or trigger certain jobs based on defined contract attributes. How Contract Snapshot works explained as below.
Figure 3.34 - Contract Snapshots During the contract creation process, Contract Snapshots are triggered upon saving the contract. The initial save generates the first snapshot, marking it as the starting point for evaluation. Subsequently, whenever changes are made to the contract fields and saved, the evaluation process is initiated. This evaluation refers to configuration tables that define the fields to capture in the snapshots. If any of the designated fields have been modified, a new snapshot is created, clearly indicating the change that was made. Consequently, each amendment generates a new snapshot, allowing for a comprehensive historical record of contract revisions.
--- 第127页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 127 of 215 For forms or output determination, standard GTM (Global Trade Management) output determination configuration is used, like other SAP documents. Customization of form selection and configuration for output determination can be done through customer project work, tailoring it to specific business requirements.
Snapshots Configurations Snapshot fields can be added anytime via config. Historical changes before snapshot setup won’t be shown in the snapshot report. Snapshot can impact: • Status changes (e.g., approval required) • Output triggers (e.g., re-generating contract printouts) Each Contract Fields can be configured, as to which fields changes will require or relevant to Contract Amendment Approval. • Tracks changes to specific fields (standard or custom). • Helps trigger status changes like “amendment approval required”. • Snapshot = advanced change log for configured fields. • Allows approvers to review what was changed in which contract. • Useful for transparency and audit trail.
--- 第128页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 128 of 215
4
Country Specific Scenario
4.1
Indonesia Contracts
4.1.1
Custom Fields at Contract
1. Tax Code: The Trader enters this Tax code on the ACM Contract to be applicable throughout the
Contract Lifecycle – for Prepayments and Invoices.
2. Contract Terms, Commodity Specs, Packaging, Add Ons, Additional Material, Partner PCA,
Counterparty Ref. No., Salesman/ Trader name, etc.
3. Flag to indicate no physical goods movement during contract creation (for Buy/Sell in One Tank
scenario)
4. Exhaustive list will be provided at later stages
5. This are captured on RICEFW ACM002.
4.1.2
OK to Pay – Not Ok to Pay
1. Custom Table is used to store OTP-NOTP relevant details.
2. Prepayment Request payments are made in full if the Vendor status is OTP and the GL account
to be posted into would be an interim account.
If the Vendor status is NOTP, only the Net amount without tax is paid to the Vendor and also
posted to and interim account.
3. Tax amounts pay out and Account reclassification happens when Tax invoice is received from the
vendor.
4. This are captured on RICEFW ACM001.
4.1.3
Custom Report for Prepayment/Advances paid
GAR Indonesia pay Advances on the Purchase Contracts to the Vendors before the delivery of the
Commodity. The Trade Control team needs a report to indicate the total Advance amount paid to a
particular Vendor, how much of the prepaid deliveries are already made and how much is
pending/delayed. The Team uses this information to follow up with the Vendors.
The details of this report is yet to be finalized and will be done in the next phase of the project. There is
a report that the team currently uses for this purpose which can be used as a guide for the exact
structure of the report.
4.1.4
GAR ID Bonded Zone Requirements
In Bonded/Non-Bonded scenario, system need to have the ability to block trade capture of raw materials
sales of CPO or Palm Kernel from bonded zone plants to non-bonded plants before further processing
of these raw materials. Raw materials should still be allowed to be moved from one bonded zone to
another, but the sale of raw materials from bonded zone should be blocked.
At most scenario, it is not yet known whether a raw material transaction (CPO or Palm Kernel) will ultimately result in a movement from a bonded zone plant to a non-bonded plant during the trade capture (contract) stage, as this is only determined at later stages (before delivery).
To cater with Bonded/ Non-Bonded scenario, optionality will be used to allow goods to be loaded/received at different a plant aside from what has been defaulted at contract. Alternate plant mentioned at optionality can be from Bonded/ Non-Bonded which is different than the default plant refer to RICEFW ACM007, ACM026, and ACM040.
Changes in Bonded/ Non-Bonded during Contract Lifecycle
--- 第129页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 129 of 215 Changes in Bonded/ Non-Bonded should reflect changes in Tax Code determination as well. By SAP Standard, Tax Code can be determined based on parameter/ condition of plant, Storage Location, Customer, Company Code, etc. During the transaction (contract/ settlement), default tax code will be determined based on provided business logic. If incorrect or need to be updated, Tax Code can still be updated on the Contract. If a plant with different tax code is maintained in the optionalities (e.g Bonded/ Non-Bonded Zone), the tax code will be updated based on parameter/ condition of plant, Storage Location, Customer, Company Code, etc.
--- 第130页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 130 of 215 4.2 China Margin Management 4.2.1 Highlight Key Business Requirements Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution ACM-112 Ability to manage deposits: - Support percentage of contract value method - CN - Handle specific sales conditions method - CN Gap Statistical Condition for Margin Management ACM-230 Ability to manage deposits: - Calculate deposit requirements based on configurable percentages - Free up contract deposit based on sale order volume - Reverse funds available to down payment - Process deposit requests based on downpayment excession report - Create margin calls when price exceeds fixed percentage - Manage deposit-based payment models (5%–20%) - Track received amounts for invoicing Gap KDD ACM-FSCM Integration ACM-780 Ability to execute China Trading Basis Advance Sales Management Scenario 2: Basis Advance Sales: Customer pays 105-110% advance with futures+basis pricing, can cancel/reprice with basis adjustment penalty. Both use price lot modifications, not contract changes. Fit Standard Solution Behavior ACM-781 Ability to configure different prepayment blocking rules for sales and purchase transactions based on entity requirements Fit Standard Solution Behavior ACM-782 Ability to process transactions when prepayment amount is within customer credit limit thresholds Fit Standard Solution Behavior ACM-785 Ability to configure different payment term structures based on product type Fit Standard Solution Behavior ACM-786 Ability to configure percentage- based margin conditions that automatically adjust at contract completion Gap It is a gap. GAR China needs custom solution for margin adjustment. ACM-787 Ability to calculate prepayment amounts as percentage of fixed contract value for flat-priced contracts Fit Standard Solution Behavior ACM-788 Ability to track and manage short- term customer deposits at contract Gap Prepayment agreement demonstration to be conducted
--- 第131页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 131 of 215 Req. No Business Requirement Requirement Analysis (Fit/Gap) Solution level with adjustment at final delivery ACM-809 Ability to recalculate prepayment amounts based on changing market conditions for margin call functionality Gap Prepayment-Margin Calculation Enhancement ACM-819 Ability to automatically calculate prepayment amounts as a percentage of contract value Gap Enhancement at Contract Level
--- 第132页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 132 of 215 4.2.2 Business Process Flow This section provides the process flow diagram for China specific Trade Capture Process.
4.2.2.1 Maintain Deposit for China 3rd Party Sales
Figure 4.1 - Maintain Deposit for China 3rd Party Sales
Table 4.1 - Maintain Deposit for China 3rd Party Sales
Process Steps
Role
Transaction Code/Fiori App
ID
Description
Create ACM Sales
Contracts
Commodity
Trader
WB21/Maintain ACM Trading
Contracts
Trade Support team creates ACM
Sales Contracts with the Customer
Price ACM Sale
Contract
Commodity
Trader
WB22/Maintain ACM Trading
Contracts
Trade Support team prices ACM
Sale Contract
Create Prepayment
Request
Commodity
Trader
WB22/Maintain ACM Trading
Contracts
Trade Support team adds the initial
Prepayment Request and marks
them as ‘Released for Settlement’
Post Prepayment
Request to Accounting
Back
Office -
Accounting
PPMGCO_PMT_REQ_POST
/ Prepayment Request
Post/Reverse
Accounting team posts these
Prepayment Requests to create
Noted Item Downpayment
Requests
Payment Received
Back
Office –
Accounting
F-32 / Clear Downpayment
Request
--- 第133页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 133 of 215
Process Steps
Role
Transaction Code/Fiori App
ID
Description
Create Nomination and
LDC
Trade
Execution
/ACCGO/LDC_WC / Create
Load Data Capture
Trade Operations team posts LDC
(Goods Issue). Deposit is
recalculated and fresh Prepayment
request is posted if needed.
Margin Call
Commodity
trader
Create & Approve ACM
Settlement
Trade
Execution
/ACCGO/STL_WC /
Settlement Workcenter
ACM Settlement posts the
complete amount as Invoice.
Before printing to the Customer
prepayments received needs to be
checked and updated by a custom
program.
Prepayment recovery
Trade
Execution
PPMGAG_PMT_CLR_SETL
/ Prepayment Recovery
Clearing
The Prepayment amount received
is netted off, updating the open AR
of the Customer.
--- 第134页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 134 of 215 4.2.3 Solutioning 4.2.3.1 Timeline of Updates • Step 0: [FSCM] Initial Credit update to the Customer due to Insurance Cover.
• Step 1: [ACM] Create and Approve ACM Sale Contract. Basis Price maintained. (Note: PPR cannot be posted to accounting in Step 4 if the Contract is not Approved)
• Step 3: [ACM] Initial (Contract Specific) Deposit requested. Expected Deposit Amount = 5% of (Basis Priced Quantity X DCE EoD Closing Price. Price is manually entered in the condition ZA02 on the contract). PPR1 Amount = Expected Deposit Amount. Review and set the prepayment request status to ‘Released for Settlement’.
• Step 4: [ACM] PPR1 post to Account receivables as Noted Item - Special G/L Indicator F.
• Step 5 & 6: [FI] [FSCM] Payment Received posting – Special G/L Indicator A. Amount updated to Special Liabilities.
• Step 7: [ACM] Price Fixation on Contract for Partial Quantity.
•
Step 8: [ACM] Expected Deposit amount recalculated = 10% of (Flat Priced Quantity X Flat Price on
Contract Pricing Lot) + 5% of (Remaining Contract Basis Priced Quantity X DCE EoD Closing Price).
Is Expected Deposit amount > Total PPR amount? => Yes => PPR2 Amount = Delta amount needed.
Review and set the prepayment request status to ‘Released for Settlement’.
Step 4, 5 & 6: [ACM] [FI] [FSCM]: Same as above.
Repeat Steps 7 & 8 for each new Pricing Lot created (Partial Quantity Price Fixation).
When an existing Price Lot is deleted / price is lifted, the Expected Deposit needs to be recalculated
since the quantity is back to ‘Basis Priced Quantity’. However, no refund or no PPR is triggered.
•
Step 9: [ACM] [FI] [FSCM] Custom Credit check is triggered when Nomination line is attempted to be
‘Confirmed’.
Successful if enough credit (Regular + Special Liabilities) for the Scheduled quantity is available.
If not successful, Customer is contacted for a Lump Sum payment and Payment Received posted as
independent FI document.
Updates Special Liabilities Credit Exposure of the Customer.
Nomination confirmation needs to be re-done.
•
Step 10: [ACM] [FI] [FSCM] Load Data Capture (LDC) is created.
SD documents created at the backend Standard FSCM credit check is triggered.
Successful if enough credit (Regular + Special Liabilities) for the Scheduled quantity is available.
Default code check for PPR posted to Account but payment not received needs to be overridden.
If not successful, Customer is contacted for a Lump Sum payment and Payment Received posted as
independent FI document. Updates Special Liabilities Credit Exposure of the Customer. (LDC) needs
to be re-processed.
• Step 11: [ACM] Expected Deposit recalculated = 10% of ((Flat Priced Quantity – GI Quantity) X Flat Price on Contract Pricing Lot) + 5% of (Remaining Basis Priced Quantity X DCE EoD Closing Price). Is Expected Deposit Quantity > Total PPR Amount (PPR1 + PPR2)? => No. No new PPRs posted.
Repeat Steps 7 thru 10 for each Delivery.
• Step 11: [ACM] Whenever the DCE Market Price drops or rises by Margin Call % (negotiated and entered at Contract), Expected Deposit is recalculated in increments of 8%. Say Margin Call happens as per Agnes email, Margin Call Deposit % = 24%
--- 第135页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 135 of 215
•
Step 3: [ACM] Expected Deposit recalculated = (24% +10%) of ((Flat-Priced Quantity – Nomination
Quantity if any) X Flat Price on Contract Pricing Lot) + 5% of (Remaining Contract Basis Priced
Quantity X DCE EoD Closing Price)
Is Expected Deposit Amount > Total PPR amount (PPR1 + PPR2)? => Yes => PPR3 Amount = Delta
amount needed. Review and set the prepayment request status to ‘Released for Settlement’.
If Margin call results in negative delta when market prices decrease, Expected Deposit is recalculated.
However, no refund or no PPR is triggered.
Step 4, 5 & 6: [ACM] [FI] [FSCM]: Same as before.
Repeat for each Margin Call
• Partial Quantity was Cancelled on Contract, triggers deposit recalculation. Expected Deposit recalculated = 10% of ((Flat Priced Quantity – GI Quantity if any) X Flat Price on Contract Pricing Lot) + 5% of ((Remaining Basis Priced Quantity – Cancelled Quantity) X DCE EoD Closing Price). Is Expected Deposit Quantity > Total PPR Amount (PPR1 + PPR2)? => No. No new PPRs posted.
• Step 12: [ACM] Standard settlement process is done for all Deliveries together. Invoice amount (AR) posted = Total GI Quantity X Relevant Price fixations. • Step 13: [FI] [ACM][FI] Standard PPR recovery program: Invoice amount - Total PPR amount = X >> SAP Std Payment run Lump Sum – X => Open AR = 0
PPR recovery1 >> Inv1 – Total PPR1 = 70000 PPR recovery2 >> Inv2 – Total PPR2 = 20000
Std Payment Run >> 100000 – 70000 – 20000 = 10000 Open AR = 0 (Since we are already +10000)
--- 第136页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 136 of 215
4.2.3.2
Account Postings
Event
Account
Description
Dr/Cr
Amount
Day1 : Initial Credit update to new
Customer = 10000(Step 0)
No posting
Day1: Contract1 created and fully priced. Initial Deposit PPR1 amount on Contract1 = 8000 (Step 4) ACM_CUST ACM Business Partner Dr (Spl. G/L Ind. F, DPR) 8000
Day1 : Payment Received on the PPR1
(Step 5)
ACM_CUST
ACM Business Partner
(Advance Account)
Cr (Spl. G/L Ind. A,
DPR received)
8000
Day2 : Margill Call. PPR2 amount on
Contract1 = 2000 (Step 4)
ACM_CUST
ACM Business Partner
Dr (Spl. G/L Ind. F,
DPR)
2000
Day2 : Payment Received on the PPR2
(Step 5)
ACM_CUST
ACM Business Partner
(Advance Account)
Cr (Spl. G/L Ind. A,
DPR received)
2000
Event
Account
Description
Dr/Cr
Amount
Day3: Contract1 created and fully priced.
Initial Deposit PPR1 amount on Contract1
= 2000 (Step 4)
ACM_CUST
ACM Business Partner
Dr (Spl. G/L Ind. F,
DPR)
2000
Day3 : Payment Received on the PPR1
(Step 5)
ACM_CUST
ACM Business Partner
(Advance Account)
Cr (Spl. G/L Ind. A,
DPR received)
2000
Day4 : Margill Call. PPR2 amount on
Contract1 = 500 (Step 4)
ACM_CUST
ACM Business Partner
Dr (Spl. G/L Ind. F,
DPR)
500
Day4 : Payment Received on the PPR2
(Step 5)
ACM_CUST
ACM Business Partner
(Advance Account)
Cr (Spl. G/L Ind. A,
DPR received)
500
--- 第137页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 137 of 215
100000
Event
Account
Description
Dr/Cr
Amount
Day20 : Invoice on Contract1 = 80000
(Step 12)
ACM_CUST
ACM Business Partner (AR) Dr
80000
12XXXXXX
Revenue
Cr
80000 - Tax
16XXXXXX
Output Tax Account
Cr
Tax
Day20 : Payment Adjustment (Step 13)
ACM_CUST
ACM Business Partner
(Netting off AR)
Cr
80000
ACM_CUST
ACM Business Partner
(Clearing Advance Account)
Dr (Spl. G/L Ind. A,
DPR received)
8000 + 2000
ACM_CUST
ACM Business Partner
(Lump Sum Consumed)
Dr
70000
Day30 : Invoice on Contract2 = 20000
(Step 12)
ACM_CUST
ACM Business Partner (AR) Dr
20000
12XXXXXX
Revenue
Cr
20000 - Tax
16XXXXXX
Output Tax Account
Cr
Tax
Day30 : Payment Adjustment (Step 13)
ACM_CUST
ACM Business Partner
(Netting off AR)
Cr
20000
ACM_CUST
ACM Business Partner
(Clearing Advance Account)
Dr (Spl. G/L Ind. A,
DPR received)
2000 + 500
ACM_CUST
ACM Business Partner
(Lump Sum Consumed)
Dr
17500
Remaining Lump sum
12500
--- 第138页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 138 of 215
4.2.3.3
Key Custom Development
1. [CONFIG] Statistical Conditions to record the Expected Deposit % for NPE and Expected
Deposit % for Flat priced and Margin Call % Drop/Rise, Expected Deposit % for Margin Call.
2. [New Fields] Indicators on the Contract for ‘Deposit Relevant’, ‘Margin Relevant’, ‘Deposit Type’
(A/B/C)
3. [BACKGROUND PROGRAM] Margin Call program to monitor Market price changes and trigger
recalculation of Expected Deposit
4. [BACKGROUND PROGRAM] Recalculation of Expected Deposit after Goods Issue
4.2.3.4
Custom fields of Contract
For Margin Management, the Contract would need an extra field for persisting the value for ‘Expected
Deposit’. This field gets continuously recalculated based on various events during the Contract
lifecycle. Indicators on the Contract Header for ‘Deposit Relevant’, ‘Margin Relevant’, ‘Deposit Type’
(A/B/C).
A custom table structure at Contract header that displays the list of Margin Calls that has occurred and the relevant details of each margin call. This table at contract is related to 4.2.4 Custom Report. The full details of this requirement are yet to be discussed with the China team during the Implementation phase.
4.2.3.5 Specific Statistical Conditions on CPE For Margin Management The Percentage that should be used to calculate the Expected Deposit for priced quantity and the unpriced quantity needs to be negotiated with the Business Partner and recorded during Contract Capture using statistical condition.
The Contract would also need statistical condition on the Contract to record the percentage change in the Market Value at which the Margin Call needs to be triggered.
Statistical Conditions to record the: 5. Expected Deposit % for NPE 6. Expected Deposit % for Flat priced 7. Margin Call % Drop/Rise 8. Expected Deposit % for Margin Call 4.2.4 Special Prepayment Request Process Additional Prepayment Requests are added automatically for the scenarios when Expected Deposit is more than the current Prepayment requests already added on the Contracts. 4.2.5 Custom Report - Customer Deposit Summary Supporting the Margin Management process requirements, GAR China needs a report to show the Expected deposit that is currently updated on the Contracts and current status of the amount – Posted, received, etc.
The details of this report are yet to be discussed. This will be done as part of the next phase of the project.
--- 第139页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 139 of 215
4.3
Pakistan Broker Contract
4.3.1
Broker Contract & ACM Contract (with actual BP)
GAR Pakistan makes initial contract (paper contract) with the Brokers and the Broker in turn brings in
actual Business Partners to transact with GAR. ACM Contract (with the actual BP) will be linked with
the Broker Contract at the Related Trades Tab. Using Standard ACM processes this requirement can
be realized as below:
1. Make a Contract with broker as the counterparty for the entire quantity
2. As and when the Broker updates GAR about the actual Business Partners, make a new contract
for the partial quantity committed by the particular Business partner and cancel the same
quantity on the original Broker Contract created in step 1 above.
3. Add Brokerage as Expense on each of the new contracts created in step2 to be settled
separately and paid to the Broker
Above solution is still conceptual and may change during the detailed discussion.
4.4
Singapore Contracts
4.4.1
Title Transfer
For Singapore trades, CIF, FOB and all related incoterms are defined as Title Transfer at Origin.
4.4.2
Singapore and Malaysia Sequence Number
Despite SAP document number, Singapore and Malaysia also require another number range called
sequence number. Sequence number definition for Singapore and Malaysia are to be defined during
detailed design. Example of GAR Indonesia Sequence Number are on Section 3.2.3.5 GAR Sequence
Number.
--- 第140页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 140 of 215 5 Appendix 5.1 ACM Product Segregation for Indonesia
--- 第141页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 141 of 215
--- 第142页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 142 of 215 5.2 GAR Global Business Models and Product Matrix Table 5.1 GAR Global Business Models and Product Matrix No Region & Office Business Model Palm & Lauric Oleo Sugar Soft Oils Beans Europe 1 Netherlands (BV) Trading, Marketing & Distribution X X X* X
2 Spain Marketing & Distribution X
3 Italy Marketing & Distribution X X
X (Ex-tank)
North America 1 USA Marketing & Distribution X X
LATAM 1 Colombia Origination, Marketing & Distribution X
2 Mexico Marketing & Distribution X X (soon, GAR BV)
3 Brazil Origination
X*
Asia & Middle East 1 India Trading, Marketing & Distribution X (Palm only) X (Sales) X (Export to DO) X (Sunflower oil) X (Soybean, SBO, SBM) 2 Pakistan Trading, Marketing & Distribution X (Palm only) X (Sales)
X (Future)
China Trading 1 China Production, Marketing & Distribution X X** (Sales)
X
Notes * Sugar is managed by GAI ** Sales is done by Sales team in respective offices, not GAR entity (e.g., GAR India, GAR Pakistan, GAR China) business model
Above information may not reflect the latest information.
--- 第143页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 143 of 215 5.3 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: Trade Capture
--- 第144页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 144 of 215
Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 001 1.1 Pre-Trade Activities GAI Proprietary Trading Desk Configure all exchange-traded products for the GAI Proprietary Trading Desk: - CME Exchange Products: - Palm: CPO, SWAP CPO - Crude & Refined Products: Gas oil - Metals: COPPER, GOLD, SILVER - FX: AUDUSD, CADUSD, EURO, EURUSD, GBPUSD, JPYUSD - Agricultural: LUMBER, LIVE CATTLE, LEAN HOG, FEEDER CATTLE - CBOT Exchange Products: - Soy bean: SBM (Futures & Options), SBO (Futures & Options), SB (Futures & Options) - ICE Exchange Products: - Crude & Refined Products: BRENT, GAS OIL, WTI (Futures & Options) - Agricultural: CANOLA, WHITE SUGAR - NYMEX Exchange Products: - Metals: PLATINUM, PALLADIUM - Crude & Refined Products: RBOB GASOLINE, HEATING OIL - MDEX Exchange Products: - CPO (Futures & Options) - NYB Exchange Products: - FX: DOLLAR INDEX - Sugar: SUGAR (Futures & Options) - MGEX Exchange Products: - Grains: RW WHEAT, MPLS WHEAT High Medium Fit CPE Master Data Setup
--- 第145页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 145 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - EPA Exchange Products: - Grains: MILL WHEAT, RAPESEED - Swaps: - CIF Rotterdam CPKO - PKPG RBD Olein - PKPG CPKO ACM- 002 1.1 Pre-Trade Activities GAI Trading Lauric Trading Desk Configure all products traded by GAI Trading Lauric Profit Centre: - Lauric Products: - Palm Kernel - Crude Palm Kernel Oil - RBD Palm Kernel Olein - Palm Kernel Expeller - RBD Palm Kernel Stearin - RBD Palm Kernel Oil - Palm Kernel Fatty Acid Distillate - Hydrogenated Palm Kernel Oil - Hydrogenated Palm Kernel Olein - Hydrogenated Palm Kernel Stearin - Grain Products: - Cochin - Crude Coconut Oil (CCNO) - Sunflower Oil High Medium Fit Material Master - Part of Initial Setup ACM- 003 1.1 Pre-Trade Activities GAI Trading Palm Trading Desk Configure all products traded by GAI Trading Palm Profit Centre: - Palm Products: - Crude Palm Oil - Refined Bleached Deodorized Crude Palm Oil - Palm Fatty Acid Distillate - Refined Bleached Deodorized Olein - Refined Bleached Deodorized Stearin High Medium Fit Material Master - Part of Initial Setup ACM- 004 1.1 Pre-Trade Activities GAI Trading Beans Trading Desk Configure all products traded by GAI Trading Beans Profit Centre: - Soybean Products: - Soybeans - Soybean Oil - Soybean Meal High Medium Fit Material Master - Part of Initial Setup
--- 第146页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 146 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 005 1.1 Pre-Trade Activities DSI Trading Biodiesel Trading Desk Configure all products traded by Indonesia Profit Centre: - Biodiesel Products: - FAME - Crude Glycerine - Fatty Matter - USP Glycerine - Yellow Glycerine - Crude Biodiesel High Medium Fit Material Master - Part of Initial Setup ACM- 006 1.1 Pre-Trade Activities China Physical & Derivatives Trading Desk Configure all products traded by GAR China Business Unit and China Desk: - Physical Products: - Soybean - Soybean Oil - Soybean Meal - Exchange-Traded Products (via China Desk): - CBOT: SBM, SBO, SB (Futures & Options) - DCE: RBDOL, SBM, SBO - EPA: MILL WHEAT, RAPESEED - ICE: BRENT, GAS OIL, WTI, CANOLA, WHITE SUGAR - MGEX: RW WHEAT, MPLS WHEAT - NYB: DOLLAR INDEX, SUGAR (Futures & Options) - NYMEX: PLATINUM, PALLADIUM, RBOB GASOLINE, HEATING OIL High Medium Fit Material Master - Part of Initial Setup ACM- 013 1.2 Contract Capture & Approval FX credit line Ability to monitor credit line from banks -Clean Line (Fixed line, can only draw up to the limit. system needs to monitor both net and gross) Low High Gap SAP can monitor credit line but cannot stop transactions when credit line is breached. For this, will need custom development ACM- 014 1.2 Contract Capture & Approval FX credit line Ability to monitor credit line from banks -CSA Line (Based on MTM of Low High Gap SAP can monitor credit line but cannot stop transactions when credit line is breached. For this,
--- 第147页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 147 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions specific trades - trades will be marked as CSA by trader) will need custom development ACM- 024 1.2 Contract Capture & Approval What-if deal Ability to save a deal to a draft status - so it does not go into position and exposure reporting, PnL, Credit and Risk monitoring
Relate to ACM-1195 High Low Fit Contract Status ACM- 038 1.2 Contract Capture & Approval Contract Confirmation (PK) Configure contract confirmation capabilities for Pakistan operations: - Confirmation Management: - Sales Processing: * Manage sales confirmations * Track confirmations sent to Singapore * Support contract issuance process High High Gap Form Requirment - Status can be defined and configured ACM- 050 1.1 Pre-Trade Activities Monitor Blacklisted Counterparty Ability to track flagged/blacklisted customer or vendor (due to failing to meet contractual obligations) High Medium Gap Part of MDM & FSCM; The blacklisted items can be configured, e.g., at counterparty level ACM- 051 1.2 Contract Capture & Approval Deal Entry Validation Pre-trade validation controls mapped to pre-trade limits The trade entry screen contains a number of validation controls, and all of the key fields are pre- defined drop down menus
Update- Rajesh 16th Mar: As confirmed by Siow Young LACIMA related RTM won't be part of current RTM High Medium Gap Available via partner solution: LACIMA ACM- 065 1.1 Pre-Trade Activities Forward Curve Generation Ability to create and maintain forward price curves: High High Fit Forward price curves is through price upload at
--- 第148页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 148 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - Derive local price curves from international forward curves - Assign location-based price curves to contract prices - Base curve assignments on product shipment origin - Apply specific price curves for different ports/regions (e.g., Belawan for Indonesian ports) - Support various term structures (daily, weekly, monthly) ACM. FX rate is through TRM.
VM: Addressed by Market Data Management ACM- 068 1.3 Contract Management (Amendment, Cancellation, Closure) Close Outstanding Contract Ability to close outstanding contract and put necessary reason for closure
Relate to : ACM-1015 High Medium Fit Contract Cancelation or makring of final delivery in application workcenter can be used. ACM- 070 1.1 Pre-Trade Activities Custom Index Development Ability to create custom and composite indices: - Support in-house indices - Manage composite indices for in-scope products - Link indices to trading locations - Support GAI's weekly base price publishing - Provide reference for destination offices High Medium Gap Baseline Configuration for CTE Setup.
VM: Combination of SAP Benchmark feature and custom development ACM- 088 1.1 Pre-Trade Activities Core Master Data Configuration Ability to configure core master data: Holiday Schedules: - Upload holiday schedules from pre-defined sources - Set up holiday schedules for exchanges and markets: * SG, ID, CN, MY Federal Public Holidays * NY Bank Holiday * High Medium Fit Basic Configuration
--- 第149页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 149 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Exchange holidays (CME Group, ICE Europe, EURONET, ICE US, etc.) Localization Settings: - Configure different number formats (comma/dot separation) - Support different date formats (DDMM or MMDD) Currency Setup: - Configure currencies traded by GAI: * Primary: USD, EUR, MYR, CNY, CNH, IDR, INR, PKR, SGD * Additional: JPY, GBP, CHF, AED, CAD UOM Configuration: - Set up Units of Measure: * BBL, Metric Ton, KG, Bushel, Pounds * Short Ton, Mounds (37.324kg), Litres, Kilolitres ACM- 089 1.1 Pre-Trade Activities Organizational Structure Ability to set up business organization structure - Model existing business structure - Configure offices, legal entities, and profit centers - Maintain strategy and sub- strategy relationships - Assign specific sub-strategies to strategies - Ability to distinguish plant titip timbun, location, company High Medium Gap Basic Configuration ACM- 090 1.1 Pre-Trade Activities Counterparty Data Configuration Ability to manage counterparty (business partner) information: - Capture customer and supplier information High Medium Gap Custom Field
--- 第150页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 150 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - Store addresses and contacts for trade entry, confirmation, invoices - Link counterparty groups to individual counterparties - Flag counterparties as 'Vendor' (Buys) or 'Customer' (Sells) - Filter counterparty pick lists based on transaction type - Display counterparty long names in pick lists - Ability to distinguish Counterparty for 3rd/Upstream/Affiliates ACM- 093 1.1 Pre-Trade Activities Product Master Data Ability to manage product information: - Configure byproducts: * Soy hull * SBN Oilstock * Soapstock * Lecithin - Configure palm products: * RBD Palm Olein * Margarine Shortening * PFAD - Configure grain products: * Rapeseed * Rapeseed Oil * Rapeseed Meal - Setup DCE Exchange products: * DCE - CORN - Create new product data High Medium Gap Custom Field ACM- 103 1.1 Pre-Trade Activities Security Configuration Ability to configure system security: - Implement security groups aligned with functional groups - Support different access levels (manager vs. executive) - Cover Trading, Trade Support, High Medium Gap Security Roles and Authorization
--- 第151页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 151 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Contract, Risk, Operations, etc. - Lock down SAP-interfaced counterparty data - Allow editing of non-SAP fields ACM- 109 1.2 Contract Capture & Approval Physical Trade Template Configuration Ability to support physical trade capture: - Easy capture of physical buy and sell transactions with minimal keystrokes - Intuitive interface optimized for trader / local trader workflow - Standardized core templates across regions - Standardized field definitions and validation rules - Common reference data (products, locations, etc.) High Medium Fit LDC Workcenter ACM- 110 1.2 Contract Capture & Approval Trade Entry Optimization Ability to streamline trade entry process: - Physical Multi-trade Blotter (ACM has functionality to mass upload contract from excel - fit for purpose) - Ability to capture comments on deals (Picklist of predefined comment types) (at contract level ACM we can add "notes" on contracts) High High Gap Enhancement at contract level to ensure comments passed to LDC ACM- 111 1.2 Contract Capture & Approval Trade Type Classification Ability to categorize different types of trades: - Trade Classification & Differentiation: - Phys-Phys/Phys- Paper Differentiator: * Clear distinction between physical- physical and physical-paper High Medium Gap Enhancement to be done based on req
--- 第152页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 152 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions trades * Visual indicators for different trade types - Trade Type Fields: * Priced/Unpriced/Provisional field at parcel level * Structured Trade Finance (STF) indicator field for position reporting ACM- 112 1.5 Prepayment Management (China) Bank Deposit Management Ability to manage deposits: - Support percentage of contract value method - CN - Handle specific sales conditions method - CN High High Gap Part of CIS Solution ACM- 113 1.2 Contract Capture & Approval Fundamental Trade Capture Ability to capture fundamental trade information across all trade types, including: - Capture fundamental trade data: - Prices, product types, specifications - Contract date, incoterms - Payment terms with calculation of due dates (dates are only expected and delivery dates i.e. commodity periods and based on this, they can fetch the prices) - Generate unique system contract numbers at entity level (default) - Monitor new trades daily through system (default) - Save deals to draft status (exclude from position/exposure reporting, P&L, credit/risk monitoring) - Ability to allow deal entry only with approved counterparties High Medium Gap Enhancement to be done based on req
--- 第153页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 153 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - Attach customer PO during Trade Capture - Indicate/overwrite intended use - Indicate taxable/non-taxable contracts based on bonded/non- bonded locations (ID - enhancement at contract level) - Indicate deal type (Spot, Long Term Contract, Long Term Agreement) ACM- 114 1.2 Contract Capture & Approval Physical Trade Capture Ability to capture and manage physical trade transactions, including: - Create detailed sales contracts with outright price terms - Capture fixed price CPO trade and allocate profit between internal entities - Link sales contracts to customers to purchase contracys from vendors / intercompany entities through Back to Back Scenarios - Create, validate, confirm and manage various physical trade types: - Standard physical trades - Backstop trades - GAI B2B trades with Destination Offices - Inter/intra-company trades - Staggered and outright contract trades - Unplanned deliveries - Priced and unpriced contracts - Hedge contracts for physical and paper positions - Capture SB trade on resell into High High Gap LDC functionlaity, need more discussion
--- 第154页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 154 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions China (internal Profit Centre) - Generate and manage SBO and SBM equivalents upon event date - Create backdated trades for purchases and sales - Merge and Split the Backstop quantity from the same or different contracts ACM- 116 1.3 Contract Management (Amendment, Cancellation, Closure) Trade Processing and Workflow Management Ability to manage trade processing workflows, including: - Manage full lifecycle from creation to archiving - Generate and circulate confirmations (form outputs that need configured) - Process sign-offs and amendments - Convert documents and upload to platforms (PDF) - Track unsigned contracts - Apply to both physical and paper trades - Facilitate deal approval workflow: - Admin Traders enter fields and save transactions - Senior Traders review and approve each trade - Handle E-trade claims with contract number assignment - Enter & approve E-Deal Slips in SAP (for Purchase) - Create PO & payment settlement for export surveys (captured in expense High High Gap Enhancement to be done based on req
--- 第155页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 155 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions management under surveyor expense) ACM- 120 1.1 Pre-Trade Activities Contract Pricing and Optionality Ability to manage contract pricing components and optionality, including: - Receive market-based price updates - Calculate transfer pricing for Inter-Company sales - Handle FX exposure with settlement currency changes - Allocate futures and FX components to contracts - Support and differentiate contract types: - Unprice / Fixed Price - Basis and Fixing - Deferred Pricing - Futures (Contract) delivery - Support multiple entries per dimension - Specify premium/discount rates - Support custom UOM/currency - Automate flat price settlement adjustments - Specify hierarchy of payment terms for purchases and sales - Capture additional deliveries beyond contractual quantity at renegotiated price - Ability to capture special request from customer such as additives (vitamins, etc) - Can select the vitamins / other additives required and assign the appropriate cost center which will High High Fit Optionality and pricing in ACM, need to discuss if any enhancement is req.
--- 第156页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 156 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions later be automatically captured in the expense section of the contract - Automate the creation of production transformation services for operations team to execute and proceed with goods movement (blending) ACM- 121 1.2 Contract Capture & Approval Trade Documentation and Attributes Ability to manage trade documentation and specialized attributes, including: - Process, verify, and manage trade data across formats - Coordinate trade sheet data with destination offices - Create, validate, and amend GAIM trade documentation - Manage regulatory compliance processes - Handle trade registration and contract declarations to authorities - Ability to generate barcode in trade confirmation to be included with Sales Contract and PO for payment processing - Capture additional Indonesia input fields: - Broker Reference Codes - Sales Area Code (Bonded vs. Non-Bonded) - Commodity Specifications - Certifications (Health, RSPO, etc) - Trade Capture Notes with Long text string - Incoterm (ex. FOB, CIF, LCO, FCO) - Packaging High High Gap Enhancement for Non- Bonded/ Bonded solution
--- 第157页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 157 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Specification - Material Code - Packaging Code - Optional Add- on Accessories (ex. Palette, Heating Pad, etc) - Tolerance Level - Tax ID - Product Type (ex. Bulk, Semi-bulk) - Contractual Terms for Export (ex. PORAM, FOSFA, etc) - Terms of Payment (ex. 1x DP, 2x DP) - Location, Plant Code, Destination Location, Load Port, Destination Port - Support multiple Incoterms: FOB, CNF, CIF ACM- 122 1.2 Contract Capture & Approval Open Price Capture Ability to capture open prices for future fixing: - Capture open price trades for later fixing - Support initial open price recording - Maintain contract history including original open price terms High High Fit ACM pricing ACM- 123 1.2 Contract Capture & Approval Price Fixing Ability to manage the price fixing process: - Fix prices for entire quantity or portions - Support partial quantity fixing - Allow multiple fixing events against a single contract - Track fixed versus unfixed quantities High Medium Fit ACM pricing ACM- 124 1.2 Contract Capture & Approval Price Splits in Fixing Ability to manage splits in price fixing: - Handle conflicts between trading splits and operational High Medium Fit ACM pricing
--- 第158页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 158 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions splits - Give precedence to trading splits for price fixing - Support reversal of operational splits when needed for price fixing - Maintain audit trail of split changes and reversals ACM- 162 1.2 Contract Capture & Approval Pre-Trade Credit Visibility Ability to provide pre-trade visibility: - Display outstanding contracts before trade approval (part of FSCM credit management) - Show quantity, credit, AR overdue information (part of FSCM credit management) - Provide visibility for both purchases and sales (part of FSCM credit management) - Provide visibility into customer credit limits (part of FSCM credit management) - Show current usage levels (part of FSCM credit management) - Support local operational decision-making High High Gap Visibility will be part of FSCM, blocking trade execution is part of ACM based on visibility details ACM- 165 1.2 Contract Capture & Approval Credit Validation and Checking Ability to validate transactions against credit limits: - Integrate contract management with credit control - Provide real-time validation - Validate transactions against forward sales limits - Check during contract creation - Compare against established High High Gap Part of CIS Solution
--- 第159页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 159 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions counterparty limits - Verify against approved trading thresholds - Validate before committing to deliveries ACM- 166 1.2 Contract Capture & Approval Order Management Credit Checks Ability to check credit during order management: Perform credit checks based on SO when GI precedes it (FSCM) Maintain credit control even with altered process flow (FSCM) Automatic Block / warning during sales trade capture due to overdue or overlimite (ACM) Automatic Block / Warning for Purchase Downpayment (ACM) High High Gap Part of CIS Solution ACM- 170 1.2 Contract Capture & Approval Credit Risk Notifications Ability to manage credit-related notifications: - Automatic notification to traders and counterparty on block - Automatic Block / warning during sales trade capture due to overdue or overlimite (ACM) High High Gap Part of CIS Solution ACM- 171 1.2 Contract Capture & Approval Approval Workflows Ability to manage approval workflows: - Support Proposed, Pending, New, and Validated statuses - Require Back Office (settlement) approval - Require Trading (control) approval High High Gap Workflow to be setup as per the requirement ACM- 172 1.2 Contract Capture & Approval Order Type Configuration Ability to configure order types: - Create various order types: * Sales orders * Credit orders * High Medium Fit Standard Solution Behavior
--- 第160页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 160 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
Stock transfer orders
- Support diverse contract types *
Include complete logistics
parameters * Enable optionality
execution * Track cancellations
- Have multiple Sales Orders in
one contract, and multiple
delivery orders for each Sales
Order
ACM-
188
1.2 Contract
Capture &
Approval
Contract
Template
Configuration
Ability to manage contract
templates:
- Long Form Contracts for
Physical Trades: * India,
Bangladesh, Myanmar + Africa
template * Mediterranean
template * China (English)
template * China
(English+Mandarin) template *
Russia (English+Russian)
template
- Common contract elements and
standard clauses
- Standard document types and
templates
High
Medium
Fit
Contract Template
ACM-
189
1.3 Contract
Management
(Amendment,
Cancellation,
Closure)
Contract
Confirmation
Templates
Ability to generate trade
confirmations:
- Short form contract for physical
trades (single template
regardless of terms)
- Addendum template for physical
trades
- Deal slip template for physical
trades
- Physical & swap short form
trade confirmations
High
High
Fit
Contract Form /
Amendment Functionality
--- 第161页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 161 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions - Generation of addendums to sales & purchase contracts ACM- 191 1.2 Contract Capture & Approval Contract Monitoring Ability to monitor contract status: - Follow up on outstanding sales contracts with customers - Comprehensive documentation of contract terms including: * Quantity * Commodity * Transportation mode * Pricing information - Ability to price in the quantity and price on a selective basis for physical contracts High High Fit Contract status Approval ACM- 208 1.1 Pre-Trade Activities CBOT Exchange Products Ability to configure CBOT products: - Configure products traded by GAI Proprietary Trading Desk: * CBOT - CORN (Futures & Options) * CBOT - ETHANOL * CBOT - RW WHEAT * CBOT - WHEAT (Futures & Options) - Configure products traded by China Desk: * CBOT - CORN (Futures & Options) * CBOT - ETHANOL * CBOT - RW WHEAT * CBOT - WHEAT (Futures & Options) High High Fit DCS ID config ACM- 209 1.1 Pre-Trade Activities China Exchange Products Ability to configure China products: - Configure ZCE Exchange Products traded by China Desk: * ZCE - RM * ZCE - RO * ZCE - RS High High Fit DCS ID config
--- 第162页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 162 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 228 1.4 Prepayment Management Prepayment Tracking and Allocation Ability to track and allocate prepayments - Track all prepayments against overall contracts - Draw down prepayments as deliveries occur - Default unutilized prepayment as deduction against delivery invoices - Allow adjustment of prepayment utilization - Make unutilized prepayment balance available for next delivery - Move orders from prepayment contracts into hold status until funds received - Support multiple prepayments on one contract - Capture down payments for both purchases and sales - Support multiple down payments for single contracts High High Fit Report to be developed ACM- 229 1.4 Prepayment Management Down Payment Processing Ability to manage down payments: - Process down payment invoices for PO transactions - Process down payment invoices for Non-PO transactions - Process down payment invoices for trading products - Track that 95% of sales are cash advance - Monitor the 5% on credit terms - Manually allocate a single down High High Gap Part of KDD (Prepayment)
--- 第163页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 163 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions payment against multiple deposits ACM- 230 1.5 Prepayment Management (China) Deposit Management Ability to manage deposits: - Calculate deposit requirements based on configurable percentages - Free up contract deposit based on sale order volume - Reverse funds available to down payment - Process deposit requests based on downpayment excession report - Create margin calls when price exceeds fixed percentage - Manage deposit-based payment models (5%–20%) - Track received amounts for invoicing High High Gap KDD ACM-FSCM Integration ACM- 239 1.2 Contract Capture & Approval Multi-Delivery Configuration Ability to manage multi-delivery contracts: - Support sales to parent with delivery to multiple child units - Enable separate invoicing for each child unit - Retain original contract number with subset indicators - Ability to amend port of loading / unloading High High Gap ACM supports multi delivery model with independent/ collective billing - specific number ranges is a gap ACM- 240 1.3 Contract Management (Amendment, Cancellation, Closure) Contract Amendment Processing Ability to process amendments: - Process amendments for physical trades - Implement appropriate validation steps - Perform Contract Value and High High Fit Contract amendment functionality and can be utilized for price change
--- 第164页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 164 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Contract Price recalculation upon amendment
This is related to ACM-947 ACM- 242 1.2 Contract Capture & Approval Contract Monitoring and Tracking Ability to track contract status: - Track outstanding contract summary information - View quantity, contract price, weighted average price - Monitor days outstanding compared to delivery date - Monitor open invoice - Ensure contract closure during month-end - Finalize and distribute to counterparties High High Gap Report to be developed - only if GAR wants to see all fields in one sigular report ACM- 287 1.2 Contract Capture & Approval Dual-Nature Cost Management Ability to manage dual-nature costs: - Handle provisional and actualized expenses - Support for items like Freight, Brokerage, Surveyor fees High Medium Fit Expense Management / Fees ACM- 294 1.2 Contract Capture & Approval Prepaid Transaction Zero-Value Invoice Display Ability to display and post transaction details in accounting showing gross amount and payments received, while presenting zero billing amount on final invoices for fully prepaid transactions High High Gap Fit for ABD approach, Gap for noted item approach ACM- 320 1.1 Pre-Trade Activities Quality Parameter Definition Ability to define quality parameters: - Support tracking of quality parameters - Monitor FFA, M&I, and other High High Fit DPQS Solution
--- 第165页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 165 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions cost factors - Track factors influencing outcome calculations - Track factors affecting settlement values - Support polarization and other quality measurements - Configure Material Specifications through DPQS functionality as part of the ACM Master Data Setup ACM- 377 1.2 Contract Capture & Approval Filtering Configuration Ability to configure additional fields in filtering criteria and apply multiple filter options for contracts High Medium Fit Fiori has the option to filter ACM- 381 1.2 Contract Capture & Approval Ease of Navigation Within Contract Workflow Ability to navigate directly from the contract page to the nomination page or LDC page without exiting and searching again High Low Fit Document flow ACM- 388 1.3 Contract Management (Amendment, Cancellation, Closure) Flexible Delivery Tolerance Management Ability to deliver quantities beyond the set tolerance (overfill scenario), with delivery documents requiring tolerance level adjustment
This is related to ACM-954 High Medium Fit Linking to contract available ACM- 389 1.3 Contract Management (Amendment, Cancellation, Closure) Contract Print Configuration Ability to configure form output to display initial contract quantity when reprinting contracts after closure. High High Gap Contract Forms ACM- 392 1.2 Contract Capture & Approval Port/Location- based Contract Ability to customize sales contract printouts to display location/port names instead of plant/tank High High Gap Contract Forms
--- 第166页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 166 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Display Configuration information, with configurable dropdown lists for location fields and Trading Portfolio/Strategies, subject to establishing plant-to- port mapping logic ACM- 394 1.2 Contract Capture & Approval Automated Optionality Contract Templates Ability to set up contract optionality using templates that automatically populate optionality values when creating similar contracts, eliminating the need for manual entry High Low Fit Optionlaity type needs to be selected manually ACM- 408 1.2 Contract Capture & Approval Shared Contract Identifiers Across Entities Ability to utilize unique contract identifier numbers that are shared and accessible across all entities in the system High Medium Fit Contract identifier can be used as per the req ACM- 409 1.2 Contract Capture & Approval Entity-Based Contract Number Logics on Contracts Ability to customize number sequences for contracts by legal entity, with intercompany contracts potentially using separate numbering series, subject to further SAP validation and audit requirement assessment High Medium Gap Number sequence is assigned to contract type ACM- 415 1.2 Contract Capture & Approval Wildcard Contract Search Functionality Ability to search contracts using wildcards in the red box search field, limited to key fields including external identifier, contract number, and company code High Medium Fit Fiori filters available ACM- 416 1.2 Contract Capture & Approval Date Range Contract Search Ability to search contracts by date range using Adapt Filter functionality with "Created On" parameter, and by contract High Medium Fit Fiori filters available
--- 第167页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 167 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
number through the contract
search box
ACM-
417
1.2 Contract
Capture &
Approval
Extended Free
Text Field
Support
Ability to use expanded free text
fields with greater character limits
than current SAP systems, with
text content configurable to carry
forward to subsequent
documents without truncation
High
Medium
Gap
Free test avaialble in
contract, Enhancement for
copying to preceeding doc
ACM-
425
1.2 Contract
Capture &
Approval
VAT Handling in
Prepayment
Transactions
Ability to include VAT in both
OTP and non-OTP transactions,
with VAT charged separately on
prepayment invoices while being
included in credit limit
calculations
High
High
Fit
Tax Configuration
ACM-
426
1.3 Contract
Management
(Amendment,
Cancellation,
Closure)
Post-Prepayment
Optionality
Changes
Ability to add or change contract
optionalities after prepayment has
been made, though with a
business recommendation to
complete such changes before
the nomination phase
High
Medium
Fit
Prepayment Request
ACM-
496
1.2 Contract
Capture &
Approval
SAP API
Integration for
Contract
Management
Ability to create multiple contracts
simultaneously using Excel
spreadsheet input through SAP
API integration. Wrapper program
might be required to capture the
required custom fields. - Standard
API might require a wrapper API
to ensure all information is
captured at contract
High
Medium
Fit
Standard API might require
a wrapper API to ensure all
information is captured at
contract
ACM-
513
1.2 Contract
Capture &
Approval
Consolidated
Contract View
Reporting
Ability to support EUDR
(European Union Deforestation
Regulation) reporting
requirements through
consolidated contract visibility
High
High
Gap
Custom Report
--- 第168页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 168 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 525 1.1 Pre-Trade Activities Incoterms Configuration and Maintenance Ability to configure and maintain incoterms within the system - For Singapore trades, CIF, FOB and all related incoterms are defined as Title Transfer at Origin. [DUPLICATE] ACM-1287
High No Change Gap Incoterms can be created and maintained as origin or destination. To be enhanced as per the request specific for SG. ACM- 534 1.2 Contract Capture & Approval Contract Line Splitting by Customer Ability to split contract into multiple lines maintaining same contract number but assigning different customers to each line High High Gap Contract split and optionality functionality can be explored ACM- 544 1.2 Contract Capture & Approval Multi-Party Price Flexibility Ability to support flexible agreed prices across all transaction parties High No Change Fit Default business partner will have negotiated contract price while alternate partner will have string / reference price ACM- 629 1.1 Pre-Trade Activities BADI Price Update Ability to update reference price using SAP BADI functionality High High Gap SAP has a BADI to update the reference price ACM- 666 1.2 Contract Capture & Approval Payment Terms Flexibility Ability to override payment terms at contract level for regulatory changes (e.g., Indonesia export requirements) High Medium Fit Default product offerings ACM- 667 1.2 Contract Capture & Approval Role-Based Authorization Ability to implement single tier approval structure based on roles rather than transaction values High Medium Fit Role-based authorization is provided by SAP ACM- 683 1.2 Contract Capture & Approval Contract Status Management Ability to manage contract statuses (draft, approved, etc.) with configurable workflows based on contract values and approval authorities High Low Fit Company Code level Configuration. Part of Implementation
--- 第169页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 169 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 684 1.2 Contract Capture & Approval Contract Parameter Configuration Ability to configure multiple contract parameters including status and workflows based on specific requirements High Low Fit Company Code level Configuration. Part of Implementation ACM- 685 1.2 Contract Capture & Approval Mass Contract Approval Ability to perform mass approval on multiple contracts High No Change Fit Using Standard ACM Fiori Application to manage ACM Trading Contracts ACM- 686 1.2 Contract Capture & Approval Third-party Contract Creation Ability to create third-party contracts High No Change Fit Using Standard ACM Fiori Application to manage ACM Trading Contracts ACM- 688 1.2 Contract Capture & Approval Multiple Incoterms Support Ability to create contracts with multiple line items having different Incoterms High Low Fit Contract Optionality. Different IncoTerm can be maintained during nomination. ACM- 690 1.2 Contract Capture & Approval Mixed Delivery Options Ability to handle contracts with mixed incoterm scenarios, i.e., GAR USA deliver half the quantity, and customer picks up the other half scenario High Low Fit Contract Optionality. Different IncoTerm can be maintained during nomination. ACM- 691 1.2 Contract Capture & Approval Line Item Pricing Basis Ability to configure different pricing basis for different line items within the same contract High No Change Fit Company Code level Configuration. Part of Implementation ACM- 692 1.2 Contract Capture & Approval Contract Summary Reporting Ability to configure contract summary reports as customizable views High No Change Fit ACM Risk Reports with user specific view variants ACM- 694 1.2 Contract Capture & Approval Multi-Currency Pricing Ability to price contracts in different basis currencies with fixed FX rates High No Change Fit Standard ACM functionality. CPE needs to be configured accordingly ACM- 695 1.1 Pre-Trade Activities Automatic Price Updates Ability to integrate with external data sources for automatic daily reference price updates High Low Gap Standard Interfaces are available. Ex BRISKEN. Will need custom develeopment for the automation to be mapped
--- 第170页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 170 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions as per GAR specific requirments. ACM- 696 1.2 Contract Capture & Approval Multiple Pricing Types Ability to configure multiple pricing types within a single contract line item High High Gap Refer to CTRM-3009. Maintain different valuation points for different pricing approaches on different line itmes. ACM- 697 1.2 Contract Capture & Approval Multi-Currency Premium Ability to configure premium in contract currency while futures are in different currency High No Change Fit Standard ACM functionality. CPE needs to be configured accordingly ACM- 699 1.1 Pre-Trade Activities Quality Parameter Configuration Ability to configure unlimited quality parameters in SAP ACM High No Change Fit List of quality parameters are maintained as Global Characteristics in MM module. Can be maintained as many as the Business needs. Can be grouped accordingly under separate DPQS Schedules. ACM- 700 1.1 Pre-Trade Activities DPQS Configuration Ability to configure DPQS by commodity at master data level with default quality parameters High No Change Fit ACM Baseline configuration for DPQS ACM- 702 1.2 Contract Capture & Approval Payment Terms Modification Ability to change payment terms after contract creation with appropriate controls and restrictions High Medium Gap Will need custom logic to override the standard behavior. Not advisable to do after the execution has started. #BackstopCheck ACM- 703 1.2 Contract Capture & Approval Payment Terms Validation Ability to set validation rules on payment terms with credit risk approval requirements High High Gap Will need a custom development. Details in the KDD for Credit check ACM- 705 1.2 Contract Capture & Approval Tolerance Configuration Ability to define tolerance at both contract and item level High No Change Fit Choose the right option on the contract to select at
--- 第171页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 171 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
what level the Tolerance
should be applied.
ACM-
719
1.2 Contract
Capture &
Approval
Mirror Contract
Linking
Ability to link mirror contracts as
related trades at item level
High
No
Change
Fit
Standard ACM
Functionality
ACM-
720
1.2 Contract
Capture &
Approval
Flexible Mirror
Creation
Ability to create mirror contracts
from either entity with appropriate
edit controls
High
No
Change
Fit
Standar ACM Functionality.
Leading Contract always
has the execution and
Settlement controls
ACM-
723
1.1 Pre-Trade
Activities
Market Price
Integration
Ability to load market prices from
internal and external sources via
APIs or manual upload
High
Medium
Gap
Custom development
would be needed.
ACM-
732
1.4 Prepayment
Management
Prepayment
Terms
Configuration
Ability to configure prepayment
terms and dates
High
No
Change
Fit
Standar ACM functionality
and configuration. Will be
addressed during project
implementation
ACM-
734
1.4 Prepayment
Management
Prepayment
Summary
Reporting
Ability to generate prepayment
summaries across multiple
contracts with counterparty
details
High
Medium
Gap
Exact requeirments for the
report to be addressed
using custom development
ACM-
737
1.2 Contract
Capture &
Approval
Trade Capture
Templates
Ability to use templates for trade
capture with predefined fields
High
No
Change
Fit
Template Contracts can be
saved say per Commodity
and can be used to create
executable Contracts.
ACM-
744
1.1 Pre-Trade
Activities
Labelling
Configuration
Ability to configure labelling and
packaging requirements as
dropdown selections in trade
capture
[DUPLICATE] ACM-1183 High No Change Fit Labelling and Packaging requirements can be recorded in the 'texts' section of the ACM contract . ACM- 745 1.1 Pre-Trade Activities Unit of Measure Support Ability to handle multiple units of measure including pounds, KG, MT with conversions High No Change Fit Standard ACM functionality allows contract capture in Packing unit of measure
--- 第172页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 172 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions instead of market unit of measure.
UoM conversions to be
maintained at Material
Master
ACM-
746
1.1 Pre-Trade
Activities
TORO/DUA
Authorization
Ability to manage TORO/DUA
authorization requirements and
validity checks
High
Medium
Gap
Exact requirements and
process to be detailed out
later during the
implementation and
validations shall be custom
development
ACM-
748
1.4 Prepayment
Management
Prepayment
Delivery Linking
Ability to link prepayments to
actual deliveries and net off
during settlement
High
High
Fit
PPR can be added at
Nomination instead of
Contract if quantity tracking
is needed.
ACM-
752
1.2 Contract
Capture &
Approval
Multiple Pricing
Events
Ability to have multiple pricing lots
within one contract item
High
No
Change
Fit
Part of basic ACM
functionality
ACM-
756
1.3 Contract
Management
(Amendment,
Cancellation,
Closure)
Formal Contract
Closing
Ability to formally close contracts
with revenue recognition and
automatic closure when
executions complete
High
No
Change
Fit
Depends on CTRM-3073.
Discussion ongoing
regarding Contract Closure
ACM-
757
1.4 Prepayment
Management
Shipment-Level
Prepayments
Ability to generate prepayment
invoices at contract level with
breakdown by shipment
High
High
Fit
PPR can be added at
Nomination instead of
Contract if quantity tracking
is needed. Also linked ot
CTRM-3065. to be
discussed and tested
together
ACM-
765
1.2 Contract
Capture &
Approval
Document
Lifecycle
Management
Ability to manage documents
across contract lifecycle with
proper lineage and accessibility
High
No
Change
Fit
Attachments can be added
at Different Levels.
Recommended to have
--- 第173页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 173 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions them stored at a different server and attach a link instead ACM- 766 1.2 Contract Capture & Approval Drag-and-Drop Document Support Ability to attach documents with drag-and-drop functionality High No Change Fit Attachments can be added at Different Levels. Recommended to have them stored at a different server and attach a link instead ACM- 767 1.2 Contract Capture & Approval Contract Document Generation Ability to generate contract documents as PDF with customized formatting
[DUPLICATE] ACM-1228 High Medium Gap Custom development to be handled during implementation ACM- 780 1.5 Prepayment Management (China) [China Trading Scenario] Basis Advance Sales Management Ability to execute China Trading Basis Advance Sales Management Scenario 2: Basis Advance Sales: Customer pays 105-110% advance with futures+basis pricing, can cancel/reprice with basis adjustment penalty. Both use price lot modifications, not contract changes. High No Change Fit Standard Solution Behavior ACM- 781 1.5 Prepayment Management (China) Configurable Prepayment Blocking Rules Ability to configure different prepayment blocking rules for sales and purchase transactions based on entity requirements High No Change Fit Standard Solution Behavior ACM- 782 1.5 Prepayment Management (China) Credit Limit- Based Processing Override Ability to process transactions when prepayment amount is within customer credit limit thresholds High No Change Fit Standard Solution Behavior ACM- 783 1.4 Prepayment Management Purchase-Side Prepayment Ability to manage prepayment requirements for purchase High No Change Fit Standard Solution Behavior
--- 第174页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 174 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Management [GAR India] transactions, particularly for sugar trade ACM- 784 1.4 Prepayment Management Margin Money Lifecycle Management [GAR India] Ability to track and manage margin money payments throughout contract lifecycle with automatic adjustment at final lifting High No Change Fit China Margin Management. Part of KDD Solution ACM- 785 1.5 Prepayment Management (China) Product-Specific Payment Terms Ability to configure different payment term structures based on product type High No Change Fit Standard Solution Behavior ACM- 786 1.5 Prepayment Management (China) Automated Margin Adjustment Ability to configure percentage- based margin conditions that automatically adjust at contract completion High High Gap It is a gap. GAR China needs custom solution for margin adjustment (WIP) ACM- 787 1.5 Prepayment Management (China) Percentage- Based Prepayment Calculation Ability to calculate prepayment amounts as percentage of fixed contract value for flat-priced contracts High No Change Fit Standard Solution Behavior ACM- 788 1.5 Prepayment Management (China) Short-Term Deposit Management Ability to track and manage short- term customer deposits at contract level with adjustment at final delivery High High Gap Prepayment agreement demonstration to be conducted ACM- 791 1.5 Prepayment Management (China) Threshold-Based Settlement Automation Ability to automate settlement release and approval based on configurable amount thresholds High No Change Fit Standard Solution Behavior ACM- 792 1.1 Pre-Trade Activities Multiple Basis Component Configuration Ability to configure and maintain multiple basis components (20+) in the pricing engine High No Change Fit Standard Solution Behavior ACM- 797 1.2 Contract Capture & Approval Multi-Currency Contract Support Ability to handle contracts in different currencies based on transaction type (domestic vs international) High No Change Fit Similar question on handling multi-currency; this can be clubbed together
--- 第175页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 175 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 799 1.2 Contract Capture & Approval Parent-Child Contract Creation Ability to create child contracts from master contracts when partial quantities require different billing parties High High Gap If BU accepts to manual workaround, i.e., cancel old contract and make a new one. If not, it is a gap, SAP needs to develop solution for this ACM- 800 1.2 Contract Capture & Approval Flexible Partner Assignment Ability to manage different ship-to and bill-to parties within a single contract High No Change Fit Standard Solution Behavior ACM- 801 1.2 Contract Capture & Approval Line Item-Level Delivery Period Ability to specify different delivery periods at individual line item level within a contract High No Change Fit Standard Solution Behavior ACM- 804 1.2 Contract Capture & Approval Proactive Contract Line Splitting Ability to create separate contract lines for different material grades during initial contract creation High No Change Fit Standard Solution Behavior ACM- 808 1.4 Prepayment Management Flexible Deposit Type Management Ability to create different prepayment document types to model various deposit types with rules for linking to single or multiple sales contracts High No Change Fit Prepayment Agreement can be used ACM- 809 1.5 Prepayment Management (China) Dynamic Margin Call Calculation Ability to recalculate prepayment amounts based on changing market conditions for margin call functionality High High Gap Prepayment-Margin Calculation Enhancement ACM- 813 1.3 Contract Management (Amendment, Cancellation, Closure) Automated Contract Closure Ability to manually close contracts or automate closure based on final delivery completion High No Change Fit During project implementation, scheduling the background job ACM- 819 1.5 Prepayment Management (China) Automated Percentage- Based Ability to automatically calculate prepayment amounts as a percentage of contract value High High Gap Enhancement at Contract Level
--- 第176页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 176 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Prepayment Calculation ACM- 821 1.2 Contract Capture & Approval [Ex-Tank] Broker-to- Customer Contract Transfer Ability to cancel quantities from broker master contracts and create new direct customer contracts while maintaining traceability to original broker contract for fee calculation purposes High High Fit Separate Broker contracts need to be cancelled if not acted upon within 7-15 days? This would be a custom development ACM- 822 1.2 Contract Capture & Approval [Ex-Tank] Short- Duration Contract Management Ability to enforce and track contract validity periods of 7-15 days for pending expirations specific to broker transactions High High Fit Standard ACM Applications a nd reüports can be used to track such contracts manually and close them manually. IF automation is needed then we might need custom development. Separate Broker contracts need to be cancelled if not acted upon within 7-15 days? This would be a custom development ACM- 823 1.2 Contract Capture & Approval [Ex-Tank] Broker Risk Coverage Tracking Ability to record and track broker guarantee arrangements where brokers cover payment risk for end customers, including broker liability limits and coverage terms High High Fit Proposed solution is to have separate contracts for brokers and actual counterparties.
Actual Contracts can have Broker as bill-to party who inturn collects from the Counterparty ACM- 825 1.2 Contract Capture & Approval [CNF Model] Parent-Child Ability to maintain hierarchical contract relationships with systematic numbering (e.g., High High Fit Refer to CTRM-4051
--- 第177页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 177 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Contract Numbering master contract 123 splits into 123-1, 123-2, 123-3) for audit trail and fee tracking ACM- 827 1.3 Contract Management (Amendment, Cancellation, Closure) Monthly FX- Driven Price Revision Ability to revise contract prices on the 1st of each month based on new corporate FX rates, applying updated prices only to undelivered quantities while preserving original FX-based prices for already delivered portions High No Change Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 828 1.3 Contract Management (Amendment, Cancellation, Closure) FX Pass-Through Pricing Mechanism Ability to automatically pass through FX rate fluctuations to customer prices at 1:1 ratio for undelivered quantities, with price adjustments calculated based on monthly corporate FX rate changes High No Change Fit Fx applied can be updated at individual load during LDC. Fx Hedging is not done by GAR Pakistan. Need to be checked if SG's Fx Hedging affects GAR Pakistan ACM- 830 1.2 Contract Capture & Approval [CNF Model] Contract Quantity Splitting for CNF Ability to split single CNF contracts into multiple sub- contracts while maintaining parent contract reference High High Gap CNF Contracts are the ones that GAR PK does NOT create, but only gives information to GAI SG?? In what cases would this require splitting ACM- 837 1.1 Pre-Trade Activities Product-Specific DPQS Activation Ability to enable DPQS selectively for specific products (tolling) while disabling for others High No Change Fit DPQS schedule has material schedule that lists the materials to which the DPQS schedule is applicable ot. This can be utilized to maintain different set of rule for differnet type of mateirals
--- 第178页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 178 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 840 1.4 Prepayment Management Multiple Advance Payment Allocation Ability to link multiple advance payments to a single contract OR distribute a single advance payment across multiple contracts, with functionality to track payment-to-contract relationships and adjust excess payments to future contracts High No Change Fit Multiple advances on the same contract = prepayment Requests
Single advance for multiple contracts = prepayment agremeents ACM- 841 1.4 Prepayment Management Noted Item Prepayment Configuration Ability to configure prepayments as noted items for proper invoice generation and netting
Similar with ACM-1412 High No Change Fit This is a Company code level configuration and applies to both Purchase and Slaes sides alike ACM- 849 1.1 Pre-Trade Activities Language Support Ability to support multiple languages High Medium Fit SAP offering ACM- 850 1.1 Pre-Trade Activities Salesman master data Ability to record salesman who responsible for the sales process. Ability to record salesman name / trader responsible for the sales process and carried to A/R report (FBL5N)
Sales Admin who key in the contract might be different with the real Salesman/ Trader Medium High Gap Custom Field at Contract Level ACM- 851 1.2 Contract Capture & Approval Traceability Ability to record the applicable certification (e.g.: RSPO, mass balance) for each respective sales transaction (not as Text).
Upstream proposed to put the information in header additional data A (Sales Order level) and it can be printed in Contract, Sales Medium Low Gap Custom Fields at Contract to be flow to subsequent documents
--- 第179页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 179 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Order and Billing
Transferred to CTRM: - CTRM-1181 (Master Data certification) - CTRM-1266 (Contract Capture : Certification Field) - CTRM-1306 (SO/DO include the certification info to operation) - CTRM-1040 (include product certification info in Sales Invoice)
[DUPLICATE] ACM-1181, ACM- 1266, ACM-1306, ACM-1040
Update-Rajesh: Found duplicate between SG and Indo RICEF list RICEFW-ID-013, RICEFW-SG-004 ACM- 859 1.2 Contract Capture & Approval Contract Print Out Ability to print Contract based on contract document
Relate to: CTRM-1228 Medium No Change Gap Form output ACM- 860 1.4 Prepayment Management Proforma Invoice Print Out for DP Ability to print Proforma Invoice based on contract document. Currently proforma invoice is used as down payment request
Relate to: CTRM-1036
[DUPLICATE] ACM-1036 Medium No Change Gap Form output ACM- 866 1.4 Prepayment Management Commercial Invoice for Down Payment Ability to generate Commercial Invoice Print Out when Advance Payment has been received. Medium No Change Gap Form output
--- 第180页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 180 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
Relate to: CTRM-xxxx ACM- 868 1.2 Contract Capture & Approval Contract Language Need to use same language in the contract print out.
Relate to: CTRM-1345
Medium
Low
Gap
Form output
ACM-
881
1.1 Pre-Trade
Activities
Pricing
Procedure
Determination
based on
Incoterm
Ability to determine pricing
procedure based on incoterm in
transaction (current ABAP
enhancement)
Medium
Low
Gap
Retrofit of custom
ACM-
893
1.2 Contract
Capture &
Approval
Physical ACM
Contract
Template Manual
Upload Capability
Ability for physical (ACM contract)
templates for manual upload into
system
High
Medium
Fit
Standard contract creation
APIs are available.
ACM-
925
1.2 Contract
Capture &
Approval
Advanced Pricing
Models
Ability to support premium, flat,
and NPE pricing with T+1
allocation
High
Fit SS[Jan07]: Flagged this as a Fit. Standard ACM Functionality and GAR version have both been demoed for different components of ACM Pricing components. The same has been documented in Trade capture as well as Trade Control blueprint documents ACM- 1001 3. Prepayment Management Percentage Input for Prepayment Request Ability to input prepayment percentage at contract capture level, and auto-calculate the prepayment amount as well as the applicable VAT tax
OTB-340: High Low Gap Prepayment Percentage Field needs to be added at Contract Level to auto- calculate the Prepayment Amount and Applicable VAT. This is applicable for both Purchase and Sales
--- 第181页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 181 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Down payment calculation is based on quantity, to avoid any rounding issue. ACM- 1002 2. Contract Capture & Approval Local Purchase - OTP and NOTP Vendor Treatment for Purchase Scenario Ability to segregate OTP vendor (pay full payment amount include tax) & Non-OTP vendor (pay only the base payment amount & only pay the tax amount upon tax invoice received), then interface to the payment team & tax posting correctly.
Need to have validation to show error - if vendor is OTP but trader select the wrong tax code on transaction level: U8 = NOTP Tax Code/ VAT In Block for Payment UA = OTP Tax Code/ VAT In Free for Payment
Relates to CTRM-1002, CTRM- 1279, CTRM-1280, CTRM-1289, CTRM-1290 High Low Gap Custom Table for OTP/NOTP Vendor will be maintained by ACM. ACM- 1003 4. Contract Management Receiving Plant Change Before Prepayment Ability to change receiving plant/location/port prior to prepayment processing using contract amendment High High Fit If contract is approved, we need to add a new line item on the plant field and remove the old one ACM- 1004 3. Prepayment Management Prepayment Limit Control Ability to limit the prepayment amount to the contract total value (while taking into account VAT as well). Prepayment amount shouldn't exceed contract value High Medium Fit Exist in Standard Functionality
--- 第182页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 182 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1005 4. Contract Management Local Purchase - Profit Center Posting by Receiving Plant Ability to apply the correct profit center & Cost Center journal posting as per receiving plant including after contract amendment High Medium Fit If there is already an existing journal posting before contract amendment. These postings need to be reversed manually. In case the existing journal posting is not available, amendment can be done and posting will be done afterward properly by default according to the updated value ACM- 1009 3. Prepayment Management Prepayment Requests Ability to submit a prepayment request for approval process and to be further processed for payment / Incoming without posting to a GL account (e.g. Currently utilize a posting to noted items upon approval of prepayment / DP request)
Advanced Payment amount (during posting) should not contain the tax amount
The prepayment request posting as noted Items shouldn't contain the tax amount.
Relate to: OTB-086 High Medium Fit Exist in Standard Functionality. Indonesia will use the Noted Item Approach for the Prepayment ACM- 1010 3. Prepayment Management Correct Reconciliation Accounts for Ability to have the correct recon accounts information (material account, service account, and/or High
Fit Exist in Standard Functionality. Change Configuration from ACM to required GL Account.
--- 第183页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 183 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
each Prepayment
Request
project account) for each
prepayment request
ACM-
1015
4. Contract
Management
Auto-Closure of
Contracts Post-
Settlement
Ability to auto-close contract after
final settlement has been
completed after a set amount of
time
e.g. close all outstanding
intercompany contract > 3
months; close contract with qty <
1%, etc.
Low
Low
Fit
Batch Job can be
configured to auto-close
contract every week / end
of month
ACM-
1018
2. Contract
Capture &
Approval
Local Sales -
Different
Workflow by
Payment Terms
Ability to have different Trade
Execution workflow for different
payment terms (Prepayment
blocks nomination confirmation,
while credit allows/ credit limit
check triggered)
High
Medium
Gap
This Depends on whether
ACM is using Nomination
or SO/Approach Decision
Nomination Validation Groups. Nomination validation / blocks
Payment terms : Prepayment / Down Payment, then need to complete Prepayment process before doing Nominations
Payment terms Credit / LC , need to complete credit check (or credit release by credit risk team) before doing nominations ACM- 1021 3. Prepayment Management Line-Item Prepayment Breakdown Ability to show on line item level for each prepayment: Prepayment Base Amount, VAT Medium High Gap - Possibility to enter Quantity Percentage
--- 第184页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 184 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Amount, and Total Prepayment Amount in the Prepayment Request Tab - Split the Base Amount and VAT Amount
- Prepayment Quantity Determination ACM- 1025
- Contract Capture & Approval Intercompany - Partner PCA Fields at Contract Level Ability to have Partner PCA information fields in contract level for consolidation purposes High High Gap Add Custom field in contract level ACM- 1036
- Prepayment Management Generate Proforma Invoice Ability to generate proforma invoices for custom declaration. This Proforma Invoice should be able to be generated as soon as possible to accelerate the customs process required for export transactions.
OTB-314: Print out invoice for
Export Transaction Declaration
High
High
Fit
Exist in Standard
Functionality. Manual DN
from Finance
ACM-
1040
2. Contract
Capture &
Approval
Certification
Information in
Sales Invoice
Ability to include product
certification in the Sales invoice
Medium
Medium
Gap
Enhancement in contract
level. Field addition in
Contract to specify the
Certificate Name / Type
ACM-
1042
3. Prepayment
Management
Local Purchase -
For Payment
term with Multiple
DP, a separate
Approval Process
for each DP
round
Ability to accommodate multiple
downpayment process for
purchase transactions with
separate approval process for
each downpayment.
High
High
Fit
Exist in Standard
Functionality. Release for
Settlement can be utilized
as approval process.
If the release for settlement is not marked it will not be availabe for posting the prepayment.
--- 第185页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 185 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Security Authorization can be used ACM- 1043 3. Prepayment Management Local Purchase - Attach Documents to DP Request Ability to attach documents (ex. Bill of Lading / BL) to a Down Payment Request for Approvers to review prior to Approval and Payment Processing High High Gap Enhancement at Maintain Prepayment Request ACM- 1044 3. Prepayment Management Local Purchase - Prepayment Variation Ability to have 2 types of purchase prepayment: - Contract-level Prepayment (1x DP, Multiple DP) - Prepayment based on netting against Prepayment Balance with a specific vendor (ex. GAR places IDR 50 Bio prepayment balance on a vendor and for each contract 90% of the contract value will be netted off with the Prepayment Balance until the balance is depleted) High Medium Fit - Contract-level Prepayment can be accomodated by basic Prepayment request.
- Prepayment Balance with Vendor using Prepayment Agreement Functionality in ACM ACM- 1045
- Prepayment Management Local Sales - Prepayment Variation Ability to have 2 types of sales prepayment:
- Contract-level Prepayment (1x DP, Multiple DP)
- Prepayment based on Sales Order quantity (1 Prepayment per Sales Order) - Biodiesel
[WW] - already confirm with
Vienna on 11/11:
For Export Fatty Matter, there are
condition where contract qty is
e.g. 100, but SO/ delivery is 50-
50 (partial shipment). Then the
DP is collected based on the SO/
High
Medium
Fit
- Contract-level
Prepayment can be
accomodated by basic
Prepayment request.
- However, enhancement will be required to integrate SO with Prepayment Request
--- 第186页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 186 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions delivery quantity (@50). Need to generate the Prepayment Request/ DP billing according to the shipment quantity (split prepayment request line item)
If Sales Contract TOP = DP x%, then the Term of Payment is DP x% as stated on the contract. In case of non-priced contract for Biodiesel, As-Is contract still need to be priced with latest price. When the updated price is available, need to update the price in the contract as well. ACM- 1046 3. Prepayment Management Local Sales - Clearing Customer DP Account based on Incoming Ability to clear Customer Down Payment Advance and VAT Out Clearing Account based on Incoming from Customer High High Fit This could potentially be accommodated through FI since FI will be doing the posting ACM- 1047 3. Prepayment Management Local Sales - Partial Invoice Receipt Ability to accommodate partial DP payment (or split payment) from Customer and create the necessary DP Billing for the customer
e.g. sales contract prepayment request 90%, but customer only pay 50%, then 40% in another day High Low Fit Exist in Standard Functionality
But Potential Workaround can be done where Prepayment Request is posted only after Incoming is received ACM- 1062 4. Contract Management Document & Contract Numbering to have proper numbering to identify between proforma invoice, down payment billing, and final billing after quantity High Medium Gap Additional custom field required at contract to show additional customized numbering.
--- 第187页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 187 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions settlement
OTB-076:
Able to generate Document
Sequence Number with specific
format. This document sequence
number is different with SAP
document number.
Document:
- Contract
- Proforma
- Invoice
Example:
Contract Running Number :
Upstream
Contract : DIC/1050/091024/0002
DI= kode Distribution Channel -->
DI, DT, XI, XT
C = Contract
1050 = Kode Sales org
091024 = DDMMYY
0002 = running number / no urut.
--> reset annually
Billing : DII/1050/1024/00150 DI= kode Distribution Channel I = Invoice 1050 = Kode Sales org 1024 = MMYY 00150 = running number / no urut.
Downstream Indonesia Contract : LTC/3324/200125/0001
--- 第188页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 188 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions LT= kode Distribution Channel --> LT, ET C = Contract 3324 = Kode 2 angka comp code + 2 angka Sales org 200125 = DDMMYY 0001 = running number / no urut - -> reset annually
Invoice : LTI/3320/0125/000250 LT= kode Distribution Channel I = Invoice 3324 = Kode 2 angka comp code + 2 angka Sales org 0125 = MMYY 000250 = running number / no urut. ACM- 1067 1. Pre-Trade Activities Local Market data setup Ability to add formulas inside market indices Low High Gap Enhancement in TRM. Custom formulas require to be added & created ACM- 1115 1. Pre-Trade Activities Associate Market Price Index with Plant Location and Commodity Ability to associate specific market indices to specific product/location combinations e.g. associate a market index showing the value of CPO at Lampung. These market indices should default when the specified product/location combination is selected on a trade
note : during Contract Capture, when user select spesific Plant (e.g. Lampung) then automatically the Valuation Point Medium Low Fit Exist in Standard Functionality. Creation of DCS (Derivative Commodity Structure) ID, part of CPE setup
--- 第189页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 189 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
will use Lampung price index if
available
ACM-
1149
2. Contract
Capture &
Approval
Approved
counterparties
Ability to allow deal entry only
with approved counterparties,
only allow for active
counterparties to be available for
selection during contract creation.
If the counterparty is not
approved/ active, don't show in
contract.
Medium
Gap MDG team to set the flag to prevent contract creation ACM- 1151 4. Contract Management Credit Limit Ability to finalise existing trades with counterparties (take decision whether to continue the open transaction) who are no longer compliant / should not be traded with Medium Medium Gap Enhancement at Nomination/billing will prevent document creation ACM- 1166 4. Contract Management Payment terms review Original Requirement: Generate approval template to credit risk manager when there is request to change TOP in the transaction. An email notification after contract approval, should be triggered if there is a discrepancy between the TOP in the transaction and the customer master data. The email will be sent only once, the first time the differing TOP is used in a sales order for that customer.
Frequency = 2-3 times/ month Medium Medium Gap Enhancement to validated TOP during contract approval and send notification to CR manager in case of change in TOP.
Logic need to be applied to check if previous notification has been triggered, to ensure only 1 time notification is sent.
--- 第190页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 190 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1177 1. Pre-Trade Activities DPQS Ability to specify premium/discount rates High Low Fit Exist in Standard Functionality, DPQS ACM- 1179 2. Contract Capture & Approval Contract Field Details : Broker Ability to add Broker Reference Codes and show in Contract output form (if this field is empty then no need to show in Contract) and carry over to Delivery Documents As-is: broker as business partner
Broker Reference Code will be filled with Broker ID and need to be printout in Contract Output form usually broker GAC request to include this Broker Ref Code in contract High Low Gap add custom field for broker ref field ACM- 1180 2. Contract Capture & Approval Contract Field Details : Sales Area Ability to add Sales Area Code (Bonded and Non Bonded identifications)
--> Bonded / Non Bonded is maintained in Plant Master Data, ACM Contract can refer to that field High Medium Gap add custom field to be added for bonded and non bonded
Bonded and non-bonded zones to be maintained at enterprise structure or contract level?
If to be maintained at contract level, need additional field to indicate whether it is bonded and non-bonded.
Plant Master Data got
--- 第191页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 191 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions information to indicate bonded / non bonded, can utilize that field ACM- 1181 2. Contract Capture & Approval Contract Field Details : Certifications Ability to add commodity certifications (eg. health, RSPO) and is automatically populated to subsequent steps (eg. Delivery forms, Billing) High High Gap add custom field and the data will flow to nomination and then printed on form and then to billing doc
At item level (per product)
If to be printed as forms output, no enhancement is required.
If fields want to be seen in
the Delivery document in
SAP - same enhancements
are required at delivery
level
ACM-
1182
2. Contract
Capture &
Approval
Contract Field
Details :
Specifications
Ability to add Commodity
Specifications, Port of Loading,
Port of Discharge, Plant, etc.
during Contract Capture and
show it at Nominations (for
Delivery Documents Forms)
High
High
Gap
add custom field and the
data will flow to nomination
and then printed on form
ACM-
1183
2. Contract
Capture &
Approval
Contract Field
Details :
Packaging
Ability to add Packaging Code
and Packaging Specification
Ability to add extra cost
(packaging / accessories) in
Contract Capture. Packaging and
accessories can be pulled from
Master Data instead of Free Text
and show it at Nominations (for
Delivery Documents Forms)
High
High
Gap
put in the free text /
comment. add custom field
having drop down and
along with it additional
space to add comment and
this details should be flown
to nomination and then
priinted on the form, for
cost we can use/ explore
fee/expense.
--- 第192页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 192 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1184 2. Contract Capture & Approval Contract Field Details : Tolerance Level Ability to add Contract Tolerance Level High Low Fit Standard functionality. Can utilize tolerance schedule. ACM- 1185 2. Contract Capture & Approval Contract Field Details : Tax ID Ability to add VAT Tax ID / Tax Code High High Gap a new field can be added based on req. Standard practice from ACM. User determined tax code will override the automatically determined tax code.
Enhancement to get tax
code at contract level and
flow it in to the precceding
docs
ACM-
1186
2. Contract
Capture &
Approval
Contract Field
Details : Product
Type
Ability to add Product Type (ex.
Bulk, Semi-bulk).
This need to link to packaging
selection for semi-bulk product
only.
High
Medium
Gap
a new field in contract with
a dropdown list. If semi-
bulk is selected, packaging
dropdown list will be
available.
ACM-
1189
2. Contract
Capture &
Approval
Contract Field
Details : Terms of
Payment
Ability to select/ setup different
Payment Terms (e.g. 1x DP, 2x
DP, etc) on transaction level
High
Medium
Fit
FI baseline configurations.
Exist in Standard
Functionality
ACM-
1190
2. Contract
Capture &
Approval
Contract Type
based on Pricing
Ability to differentiate contract
types :
- Unpriced contract
- Fixed Price/ Flat price contract
High High Fit Exist in Standard Functionality ACM- 1194 2. Contract Capture & Approval Mandatory Fields in Contract Ability to configure Mandatory Fields for Contract Creations High Medium Gap Enhancement to be made to make fields mandatory ACM- 1195 2. Contract Capture & Approval Contract Draft Status Ability to save a deal to a draft status - so it does not go into position and exposure reporting, PnL, Credit and Risk Monitoring High Medium Fit Exist in Standard Functionality
--- 第193页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 193 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1196 1. Pre-Trade Activities Default DPQS application Ability to make sure DPQS will not have impact on Financial Amount (default DPQS ranges to 0) High Medium Fit if the details are manually entered then we can use the free text, else we can do enhancement as per the req ACM- 1198 2. Contract Capture & Approval Sales - Contract Capture - special request from Customer Ability to capture special request from customer such as additives (vitamins, etc) Can select the vitamins / other additives required and assign the appropriate cost center which will later be automatically captured in the expense section of the contract (e.g. Delivery Documents) High High Gap add custom field ACM- 1199 2. Contract Capture & Approval Contract Field Details : Optional Add-on accesories Ability to search & select the materials & show the Material Code for additional and Optional Add-on Accessories (ex. Palette, Heating Pad, etc) and carry over to Delivery Documents & posting GI to expense Medium High Gap put in the free text / comment. if the details are manually entered then we can use the free text, else we can do enhancement as per the req ACM- 1200 2. Contract Capture & Approval Contract Field Details : Packaging Cost Ability to add extra cost (packaging / accessories) in Contract Capture. Packaging and accessories can be pulled from Master Data instead of Free Text and show it at Nominations (for Delivery Instructions Forms)
As-Is: Packaging material is GI as expense to Trader Cost Center every end of month High High Gap Extra cost can be added using Fee/Expense basis and Forms needs to be enhanced. KDD discussion
--- 第194页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 194 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1201 1. Pre-Trade Activities Contract Field : Commodity Grouping in Contract Ability to add commodity group (Palm, Lauric, Biodiesel) in Contract Capture and Approval based on Commodity Group
CH: will utilize Sales Division : TR = Trading Palm TP = Trading Lauric TB = Trading Biodiesel High Low Fit Exist in Standard Functionality. MDG to maintain commodity group and assign material to the commodity groups. System can check material role and user role during approval process. ACM- 1202 2. Contract Capture & Approval Long Text Notes / Descriptions in Contract Ability to add Contract notes with long text strings, that need to be shown in sales contract print output. High High Fit Exist in Standard Functionality. ACM can capture long text (up to pages length), form output also can be config as needed ACM- 1204 2. Contract Capture & 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- 1205 2. Contract Capture & Approval Input Purchase / Sales Contract with Outright Price terms Ability to create detailed sales contracts with outright price terms, including all relevant details Ability to only enter one flat price during contract capture without entering both Basis and Future Price High High Fit Exist in Standard Functionality ACM- 1206 2. Contract Capture & Approval Attach Documents to Contract Ability to attach docs (scanned/pdf) to contract, such as PO from customer / Sales Contract from Vendor, as basis doc to split the parcel (i.e. split into 5 SO with different fulfillment date) High High Fit Exist in Standard Functionality
--- 第195页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 195 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1207 2. Contract Capture & Approval Multiple Locations in Contract Ability to capture Plant Code and Multiple Locations / Shipping Points in Contract Capture High High Fit Exist in Standard Functionality
1 plant can have multiple shipping points, but shipping points are not shown at contract level; more relevant during nomination.
Plant code can be provided at the nomination level ACM- 1209 2. Contract Capture & Approval Contract Field Details : Contract Date and Time Ability to enter Contract Date during Contract Creation and support Back Date Contract High Low Gap add custom field. Free text tab can be used. KDD discussion ACM- 1211 3. Prepayment Management Purchase - Approval for "Release for Settlement" on Contract Ability to add approval process for Prepayment "Release for Settlement" process at Contract. at Contract Page when changing checkbox "Release for Settlement" add Approval Process (contract amendment) to replace existing Prepayment Approval process. the reason because this action trigger Prepayment Request.
After "Release for Settlement" saved, auto-post Noted Item based on PPR. Low High Gap Prepayments. Release for Settlement can be utilized as approval process.
If the release for settlement is not marked it will not be availabe for posting the prepayment.
Security Auth can be used
Discuss in KDD for prepayment approach ACM- 1212 2. Contract Capture & Approval Biodiesel - PSO / Non PSO Contract Ability to differentiate between Allocated PSO, Allocated Non PSO, Non Allocated in Contract for Biodiesel High Medium Gap Add custom field at contract level
3 fields needed
--- 第196页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 196 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions
Allocated / Non Allocated
PSO / Non PSO
Subsidized / Non Subsidized
These fields are needed only forBiodiesel
For others we can put is as NA ACM- 1214 2. Contract Capture & Approval Purchase - Long Term Contract (LTC) Ability to differentiate between LTC, LTA or Spot Contract Medium High Gap Custom field at contract level.
or use External Reference ID (Fit) ACM- 1215 2. Contract Capture & Approval Purchase and Sales Org in Contract Capture Ability to only enter only one of Purchase / Sales Org (e.g. ony Purchase Org for Purchase and Sales Org for Sales Transactions) High High Gap Required for management reporting purposes, therefore these fields are mandatory ACM- 1216 2. Contract Capture & Approval Template for Trade / Contract Capture Ability to setup and use Template for easy Trade Capture according to Contract Term (to minimize user input). High High Fit Exist in Standard Functionality. Use copy contract / contract template functionality ACM- 1217 2. Contract Capture & Approval Duplicate Contract with Prepopulated Field Ability to duplicate from existing contract with pre-populated Field. High High Fit Exist in Standard Functionality ACM- 1219 2. Contract Capture & Approval Intercompany Indo purchase & sales - Contract linking There should be a field that contains plant number so it is easier to link between High Medium Fit Exist in Standard Functionality
--- 第197页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 197 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions intercompany Purchase order with its respective Sales contract ACM- 1220 2. Contract Capture & Approval Validate Contract against Vendor/Customer documents Ability to reconcile contract details from vendor against what we created, to check if there are any mistake in our contract entry. Medium Medium Gap no solution (require another product to scan pdf doc). Contract can be validated in change mode
To be done manually ACM- 1221 4. Contract Management Create Nomination and LDC directly from Contract Page Ability to navigate to Nomination and LDC creation page from Contract Page without exiting Contract Page Low Medium Fit Exist in Standard Functionality
Open in multiple tabs,
usually contract,
nomination & LDC is
created by different roles
ACM-
1222
2. Contract
Capture &
Approval
Trade
Confirmations
Workflow
Ability to manage deal approval
workflow:
- send email notifications for
contract approval
- send email notifications to
related stakeholders after
contract approved (by Commodity
Group and Plant Location)
- Provide summary page with
key information for Mass Contract
Approval
High
Medium
Fit
Exist in Standard
Functionality.
Notifications - part of forms, can be configured ACM- 1223 2. Contract Capture & Approval Trade Confirmation Templates Ability to setup template to generate trade confirmations : - Short form contract for physical trades (single template regardless of terms) - Addendum template for physical trades - Deal slip template for physical High Medium Gap Form output
--- 第198页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 198 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions trades - Physical trade confirmations - Generation of addendums to sales & purchase contracts ACM- 1224 2. Contract Capture & Approval Contract Approval : Mass approval contract based on specific criteria Ability to mass approve contract based on specific criteria e.g. Material, Company Code, etc. High Medium Fit Exist in Standard Functionality in contract Approval workcenter ACM- 1225 2. Contract Capture & Approval Contract Approval : Show specific informations during mass approval Ability to show specific informations during mass approval : Counterparty, Material, Qty, Price, Incoterm, Payterm, Shipment, Prepayment High High Gap Custom Report. View of Summary Information upon Approval ACM- 1226 2. Contract Capture & Approval Contract Approval : Approve Trade via mobile phone Ability to approve trade contract using mobile phone Low High Fit Exist in Standard Functionality ACM- 1227 2. Contract Capture & Approval Contract Approval based on Commodity Group Ability to approve or authorize based on commodity group (Palm, Lauric, Biodiesel)
Related with CTRM - 1076 High Medium Fit Exist in Standard Functionality ACM- 1228 2. Contract Capture & Approval Printout Contract after Contract Approval Ability to printout hardcopy/softcopy of Contract after Contract Approval Contract print output need to have barcode - follow as-is High High Gap Form Solution ACM- 1229 3. Prepayment Management Prepayment Informations on Contract Page Ability to show information regarding Prepayment (request, amount, status) on Contract Page
Relate to CTRM-1225 Medium Medium Gap Create/copy fiori and modify. can make use of Release for settlement field
--- 第199页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 199 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1230 2. Contract Capture & Approval Automated FX Rate calculations Ability to maintain automated FX rate during contract creation and choose FX Rates based on Trade / Contract Date. High High Fit Exist in Standard Functionality. Only provisional FX Rates are provided, user need to manually select ACM- 1232 4. Contract Management Ament Contract Price Ability to amend contract price if market prices are not loaded to system. High High Fit Exist in Standard Functionality ACM- 1233 4. Contract Management Purchase - Change Receiving Plant Purchase - Ability to identify and change the receiving plant in PO (in bonded / non-bonded zone) If prepayment has been collected & plant need to change from bonded to non bonded-zone, need to accommodate the tax adjustment collection & posting. High Medium Fit Exist in Standard Functionality
Optionality can be utilized
ACM-
1234
4. Contract
Management
Approval for
Mass Contract
Cancellations
Ability to add Approval for Mass
Contract Cancellations
High
Medium
Fit
Exist in Standard
Functionality. Amendment
functionality
ACM-
1235
4. Contract
Management
Mass
Cancellations
based on
Residual
Quantity
Ability to perform Mass
Cancellations based on Residual
Quantity
High
Medium
Fit
Exist in Standard
Functionality
ACM-
1236
4. Contract
Management
Reverse
Cancellations
Ability to do Reversal of Contract
Cancellations
High
Medium
Fit
Exist in Standard
Functionality
ACM-
1237
4. Contract
Management
Reason for
Contract
Cancellations
Ability to add Reason / Remarks
for Contract Cancellations
High
Medium
Fit
Exist in Standard
Functionality
ACM-
1239
4. Contract
Management
Reporting - Track
Contract
Changes
Ability to run a report which
shows all changes made to open
contracts and associated PnL
impact by region/desk/contract
Medium
Medium
Gap
Exist in Standard
Functionality. Custom
report
--- 第200页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 200 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1240 4. Contract Management Reporting - Track Outstanding Contract Quantity Ability to track outstanding quantity as a percentage of Total Contract Quantity (Purchase & Sales) High Medium Gap add functionlaity for percentage. Contract qty type option can be used where you can see the qty details
Position report (custom) ACM- 1241 4. Contract Management Reporting - Contract End to End Lifecycle Ability to view Contract End to End Lifecycle (Contract Amount & Qty, Payterm, Prepayment Amount & Qty, BLs, Delivered Qty, Billed Qty, Outstanding Amount & Qty, etc) Group by Bulk (Palm, Lauric, Biodiesel) and SemiBulk
As-Is : Contract- SO-DO-GI- Billing (custom report) High High Gap
Custom report ACM- 1242 4. Contract Management Local Purchase - Contract Realization Tracking Ability to track the overall purchase contract realization (total contract value, Prepayment amount (and remaining), GR Amount, and how much has been payment has been processed/paid) High High Gap
Custom report ACM- 1243 4. Contract Management Local Sales - Contract Realization Tracking Ability to track the overall sales contract realization (total contract value, DP amount (and remaining), GI Amount, Billed/Unbilled amount) High High Gap
Custom report ACM- 1244 4. Contract Management Contract Monitoring Ability to monitor contract status: - Follow up on outstanding sales contracts with customers - Comprehensive report of High High Gap Custom report
--- 第201页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 201 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions contract including: * Quantity * Commodity * Transportation mode * Pricing information ACM- 1247 4. Contract Management 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- 1253 2. Contract Capture & Approval Intercompany: Seller - Buyer pre trade activities to connect between seller plant & buyer plant Ability to capture Intercompany transaction when we still don't know the counterparty details (legal entity & plant) Currently Seller side (Upstream) use KUBE to create open request, and Buyer side (Downstream) can update the buyer plant information. High High Gap Report - Use the Workcenter - KDD Discussion ACM- 1265 2. Contract Capture & Approval Contract Field Details : Material Description Ability to change / use different material description in Contract to be printed on Contract Form Output.
OTB-415: Print out sales contract for export transaction can accomodate material description more than 40 character High Low Fit Exist in Standard Functionality. Update Contract material descrip.
1 material code can have multiple material name/ description in MDG (up to 40 character).
Need to utilize the basic data text functionality OR create custom table to
--- 第202页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 202 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions accommodate long material description ACM- 1266 2. Contract Capture & Approval Contract Field Details : Certifications Ref. No. Ability to add Certifications Reference Number in Contract and carry over this informations to Delivery Document High Medium Gap Add custom field at contract level and also on delivery (free text) ACM- 1267 2. Contract Capture & Approval Contract Field Details : Counterparty Ref. No. Ability to add Counterparty (Buyer/Seller) Reference Number in Contract and carry over this informations to Delivery Document High Medium Gap Enhancement would be needed to pull and display on delivery doc. can use customer ref for sale and your ref field for purchase on basic data tab ACM- 1269 2. Contract Capture & Approval Contract Field Details : Additional Material and Cost Ability to add additional material outside BOM, e.g. Antioxidant, Vitamin K, etc. for the purpose of tracking the "naked" / raw price of commodity for the contract
Relate to : CTRM-1198, CTRM- 1199 High Medium Gap Enhancement to be done as per req. Text tab can be used for adding text details and fess and expense can be explored for price
SS: ACM Expense can
only cover the cost of the
additional materials but
does not cover Goods
movement for the
additional materials.
Standard SD process to be
followed.
ACM-
1270
2. Contract
Capture &
Approval
Contract Field
Details : Special
Condition /
Disclaimer
Ability to add special condition /
disclaimer term to be print out in
Contract Output form.
e.g. Buyer to countersign and
return none copy of this Sales
Contract to Seller at the latest of
3 working days since being sent,
otherwise Buyer shall be deemed
High
Medium
Gap
Enhancement to be done
as per req, if field is
needed with drop down
values we can . Text tab
--- 第203页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 203 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions to confirm and agree to this Contract. ACM- 1271 2. Contract Capture & Approval Contract Field Details : Estimate Delivery Date Ability to enter estimate delivery date in Range (Date from and Date To) in contract level Medium Medium Fit Exist in Standard Functionality: Delivery date from/ to ACM- 1272 2. Contract Capture & Approval Contract Field Details : Email Notification Ability to send email Notification before Delivery, have email functionality to send out sales contract & sales order via email to related parties. Need to config the group of email recipient e.g. Palm Trader Team, Logistic Team, etc. Low High Fit Exist in Standard Functionality, need to be configured ACM- 1273 2. Contract Capture & Approval Local Purchase (Bonded Zone) - Trader Follow-up Notification Ability to have a notification/reminder mechanism to remind the traders to follow up with the vendor to process the Bonded Zone documents (SPPB and BC) as soon as contract has been approved
Related to CTRM - 1041 Medium High Gap Form, triggered only when location is Bonded zone ACM- 1274 2. Contract Capture & Approval Local Sales / Intercompany - Block Raw Material Sales from Bonded Zone Ability to prevent trade capture of raw materials sales of CPO or Palm Kernel from bonded zone plants to non-bonded plants before further processing of these raw materials. (Raw materials should still be allowed to be moved from one bonded zone to another, but the sale of raw materials from bonded zone should be blocked) Medium High Gap enhancement at contract level, to apply the check & block
--- 第204页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 204 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
ACM-
1276
2. Contract
Capture &
Approval
Multiple contract
approval /
approval
delegation
Ability to setup multiple approver
(or delegate approver) for
Contract Approval. Approval will
be based on Traders ID (or
Trader Group) that create the
Contract.
(Pending confirmation from
Trader on the approval grouping -
TBD on detailed design)
High
Medium
Fit
Exist in Standard
Functionality
ACM-
1279
2. Contract
Capture &
Approval
Local Purchase
- OTP and NOTP
Vendor List and
Approval
Ability to have separate list for
OTP and NOTP Vendor.
Registering a vendor into OTP
category requires special
approval matrix to Commercial
Director and CFO.
90% currently is NOTP vendor.
As-Is = maintain in custom table,
with manual approval via email
Relates to CTRM-1002, CTRM-
1279, CTRM-1280, CTRM-1289,
CTRM-1290
High
Medium
Gap
Custom Table for
OTP/NOTP Vendor will be
maintained by ACM.
ACM-
1282
3. Prepayment
Management
Multiple
Prepayment
approval /
approval
delegation
Ability to setup multiple approver
(or delegate approver) for
Prepayment Approval.
Relate to: CTRM-1276 High Medium Fit Exist in Standard Functionality. Release for Settlement can be utilized as approval process.
If the release for settlement is not marked it will not be availabe for posting the prepayment.
Security Auth can be used, based on the Sales Division
--- 第205页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 205 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1290 3. Prepayment Management Local Purchase - Prepayment OTP or NOTP Ability to process outgoing prepayment request, with specific tax invoice & tax posting treatment for OTP non OTP vendor
Relates to CTRM-1002, CTRM- 1279, CTRM-1280, CTRM-1289, CTRM-1290 High Medium Gap Prepayment with Tax , based on OTP and Non OTP enhancement this req must be addressed ACM- 1291 3. Prepayment Management Local Sales - Process Incoming Prepayment from Trading Customer Ability to process incoming prepayment from customer & create DP billing & final billing+ tax invoice
For Sales to Kaber area, need to input AJU Number in the create Settlement step and ensure this information flows to the Billing header text field in VF01 to be printed in the Billing form output.
Relate to OTB-085 High Medium Fit Exist in Standard Functionality. ACM is for proforma invoice only, actual billing for DP billing + Final billing happen in SD/FI side ACM- 1295 2. Contract Capture & Approval Tax Code Accounting Postings Ability to have different tax accounting posting based on tax code variations (e.g. Bonded Zone tax code, Non-Bonded tax code and other tax code variations) for prepayment and final payment High
Gap Bonded/Non-Bonded Solution ACM- 1325 2. Contract Capture & Approval Local Purchase - Prevent double purchase contract input Ability to detect and provide a hardstop notification when more than one purchase contract is created with reference to the same sales contract vendor. This High High Gap Enhancement at contract save is needed during the approval. Not to allow same external reference
--- 第206页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 206 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
is to prevent the possibility of the
same purchase contract being
processed more than once.
Currently there is a hardstop
notification for the same seller
contract number in the e-deal slip
program
field, if there's any
duplicate, cannot be save.
ACM-
1326
3. Prepayment
Management
Local Purchase -
Form Output for
Payment
Processing
Ability to generate form outputs
similar to e-deal slip and memo
payment to be printed out and
sent to Payment Processing
Team
Medium
High
Gap
Form Solution
ACM-
1340
4. Contract
Management
Contract
amendment
control
Ability to control, which field are
still allowed to be updated/
contract amendment with re-
approval (non commercial
impact), which field are not
allowed to be amended & need to
cancel/ create new contract (have
commercial impact)
High
Medium
Fit
ACM does allows selection
of fields trggering the
snapshot functionality
causing the status to be
updated to amended
requiring re-approval
ACM-
1344
2. Contract
Capture &
Approval
Document
Signee
Ability to have custom table to
determine the authorized signee
for each documents (e.g. sales
contract, billing) - print out
Medium
Medium
Gap
Role based authorization
can be provided for
document approval.
Custom table can also be
created for doc validation.
ACM-
1345
2. Contract
Capture &
Approval
Contract
Language
Need to define the language/ use
the same language in the
contract print out.
High
Medium
Fit
Forms can be multi-lingual.
Default functionality.
ACM-
1346
2. Contract
Capture &
Approval
Mass Upload
Sales Contract
Ability to mass upload Sales
Contract document (e.g. from
excel / csv templates)
Low
Medium
Fit
SAP provided Mass
creation of Contracts via
APIs.
ACM-
1347
2. Contract
Capture &
Approval
Contract
Authorization
OTB-191: Ability to have control for price High Medium Fit Pricing can be done and contract approval will
--- 第207页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 207 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
update in SO and contract.
Only approved user
(ZSD_USRID) who are able to do
price update
happen based on role and
authorization.
ACM-
1372
3. Prepayment
Management
Prepayment
Information
Ability to determine O/S Qty %
compared to Total PO Qty
Low
Gap Comment by Sneha:
This will be a gap, PPR is recorded , processed and settled in terms of amount and not directly linked to quantity ACM- 1373 3. Prepayment Management Prepayment Information Ability to determine the outstanding PO status (O/S Del, UM Bulk) Low
Gap Custom PPR Report ACM- 1374 3. Prepayment Management Prepayment Information Ability to determine PO Status based on aging (current or overdue) Low
Gap Custom PPR Report ACM- 1398 3. Prepayment Management Auto Proforma Invoice Numbering Ability to auto generate Sequence number for Proforma Invoice. This is applicable for local and export (for export, this is typically used to generate PEB) High
Gap Enhancement required for Number Range in Billing as per the req ACM- 1405 1. Pre-Trade Activities ACM & S4 Data Standardization Ability to have Standardized fundamental data between ACM & SAP S4 (eg. Material Desc, payment term, field name, price per UoM, etc) High
Fit Already drafted L4 for Maintain ACM Master Data and it's separation between MDG. Will discuss the separation of master data with MDG. ACM- 1408 3. Prepayment Management Local Purchase - Prepayment Balance with Vendors (Multiple Contracts) Ability to accommodate prepayment balance with certain vendors. (e.g. we paid a prepayment to a vendor that is applicable to multiple purchase contract until fully depleted) Medium
Gap Customize/ Enhance current Prepayment Agreement Solution to cater with business requirements
--- 第208页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 208 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
Prepayment paid to vendor based
on agreement on vendor level,
not contract level
ACM-
1410
2. Contract
Capture &
Approval
Record Trader
Name
Ability to record the name of
trader / salesman responsible for
the contract capture input
process (for both sales &
process). The trader admin who
input the transaction is not the
actual trader/ salesman, therefore
need this field to mention the
trader name/ user ID.
Related to CTRM-1416 Medium
Gap Custom Field Enhancement at Contract Level ACM- 1412 3. Prepayment Management Noted Item Posting for Purchase & Sales Ability to post to Noted Item Accounting Posting for Prepayment without including VAT Tax
Related to CTRM-1009 High
Fit SAP Prepayment Standard Behavior ACM- 1413 4. Contract Management Contract Price Change after LDC Ability to change Contract Price even after LDC for payment terms: Credit (No Prepayment) e.g. In Biodiesel, sometimes we haven't received the price for BBM / BBN during trade contract creation, traders need to update the price once the gov't has published the new price for the applicable month. So sometimes we have to ship the goods before the price has been finalized High
Fit SAP Standard Behavior ACM- 1415 4. Contract Management New Scenario: Change Ability to accommodate the following Scenario: High
Fit Cancel and recreate the contract and change
--- 第209页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 209 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions Destination mid- contract - Purchase scenario: SMART buys FOB (pick up goods from Load Port, but then during delivery (ship has loaded the goods), counterparty or destination port must be changed due to stock level consideration.
note(ch) : consider both scenario
of port change during sales
transaction, within same sales
org / company code and different
sale org / company code
counterparty/company
code
ACM-
1418
2. Contract
Capture &
Approval
Create Certificate
Master Data
Ability to create Certificate Master
Data that contains :
- Plant/PCA
- Unit
- Issued Date
- Valid Until (date)
- Certificate No.
- Type Product
(CPO/PK/CKG/etc.)
- Value
- CB
- Certificates Type (RSPO
MB/RSPO GGL/etc.)
- PSM
- PT
- SC
- Status (Enabled/Disabled)
- Short Description
- Active (Y/N)
US currently maintain in KUBE High
Gap Custom Field Enhancement at Contract Level
--- 第210页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 210 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions table for master data, DSI maintain in Smart Trace ACM- 1421 3. Prepayment Management Retain the same Proforma Invoice number & SO number/ Nomination number during reversal Ability to retain the same Proforma Invoice number for all Export Sales Transaction, and retain the same SO Number (Nomination) for Local Sales Transaction from Bonded zone area, even when the relevant doc flow are reversed. This is due to the number submission to government for tax requirement (Export supporting docs for Export declaration, Surat Setoran Pajak/ Tax info for bonded zone) High
Gap Prof invoice number generated from Contract (number is not change)
SSP refer to the Contract number.
Create Nomination = As-Is SO
Confirm Nomination = As-
Is DO
ACM-
1426
3. Prepayment
Management
Workflow to SAP
Inbox to process
task
Trigger workflow and notification
in SAP Workflow Inbox/ SBWP to
CBS Finance/ back office team to
process task:
e.g.
- for purchase prepayment noted
item & all payment request, need
to trigger workflow to SAP inbox
to BO/I2P invoice team to review
- for sales prepayment, trigger
workflow to BO Sales Team to
print DP Billing & Cash App Team
to clear incoming
- for sales contract approval
trigger workflow to create
nomination,
- for load qty with final delivery
indicator, trigger workflow to BO
Sales Team to create Settlement
Medium
Gap Custom Workflow
--- 第211页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 211 of 215
Req.
No.
Process Level
3
Requirement
Requirement Description
Criticality
Degree
of
Change
Fit/Gap
Assessment
Solutions
& Billing,
etc.
ACM-
1427
2. Contract
Capture &
Approval
Intercompany
Transactions
Ability to capture all intercompany
trading transactions, for example:
- US to US
- US to GBE
- US to DSI
- DSI to DSI
- DSI to SOCI
- DSI to GAI
- GAI to DO
As-is: DSI maintain same
material number even though
with different quality. SOCI
segregates different material
number based on quality.
However, to use the
intercompany functionality in
ACM, seller and buyer company
needs to use the same material
number.
High
Gap Enhancement at contract level for valuation type ACM- 1429 4. Contract Management Supplier Evaluation Performance Ability to generate report for supplier evaluation performance by formula (quality, gain/loss quantity, delivery, Quantity per month, Sustainability, Fraudness)
As-is: this report is consolidated manually, purpose for this report is for Management Review Unit. Sample report is provided and available in Sharepoint Low
Gap Custom Report
--- 第212页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 212 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions ACM- 1436 4. Contract Management Notification for Contract Cancellation Need to inform Operation team upon contract amendment/ cancellation, to amend/ cancel the relevant customs documents Option 1: Authorized operational team to access contract (view only), As-Is the operation team access PO from ME23N -> need to confirm with Bu Yenti Option 2: Trigger notification output for the contract approved/ amendment/ cancellation (via email) Medium
Gap Form Output ACM- 1438 2. Contract Capture & Approval Bank Account Number in Contract Output Form Ability to differentiate and auto generate the correct Bank account number in Contract Print output based on the logic of: Company code - PSM (US), Company code - Dist Channel (DSI). Low
Gap Form Output ACM- 1441 2. Contract Capture & Approval Flag to indicate scenario of no physical goods movement during Contract Capture For scenario of intercompany commercial transaction with no physical goods movement (eg. jual-beli dalam 1 tanki), ability to have a flag/checkbox during contract capture to indicate of such scenario, so Nomination is no longer needed since it's not TM relevant, no credit check & LDC can be automated since the contract qty = load qty = unload qty As-is: Upstream Sales & Logistics already know that it is a scenario Low
Gap Custom Fields at Contract
--- 第213页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 213 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions of no physical goods movement during input in KUBE ACM- 1442 4. Contract Management Review & carry over all existing RICEFW from SAP ECC to SAP ACM Extract all As-Is existing & actively used RICEFW in SAP ECC (EDM, SD, MM, FI), need to be available in the To-Be solution, in example: - Material UoM & conversion calculation (e.g. for Biodiesel 0,87 kg = 1 Litre) - All document numbering convention/ sequencing - All existing Approval, Workflow, Print Output, Reports - etc. High
Gap Retrofitting can be done. Analysis is required alongside with the previous report. But it will be a different effort ACM- 934 Report Certified Quantity Balance Tracking Ability to record and monitor for certification balance & valuation, per product (i.e. 920001 - RSPO MB RBD PALM OIL) (for example, buy 100 MT of EUDR Certified RBDPO but GAR can sell 100 MT of uncertified RBDPO while saving the certification for another 100 MT of RBDPO)
(new)
ACM- 939 1.2.2 Pricing & FX Terms (manual “price reference” field for trader market comparison) Field to capture Price reference For Singapore, there is a need to have a field to capture Price reference that needs to be input manually by traders. This can be part of price component items. Traders will use this field to input the current market price reference for the applicable contract as a measurement to
(new)
--- 第214页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 214 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions see how much Margin they are making vs market ACM- 943 1.2.1 Physical Contract Capture (exchange specific contract creation) Exchange- Specific Settlement Ability to handle exchange- specific settlements: - Generate physical contract based on exercised futures contract (with exchange and closing price)
This is related to ACM-207, ACM- 944, ACM-945
(split)
ACM- 944 1.4.1 Prepayment Terms & Schedules (80- 20% split forbuying from exchange) Exchange- Specific Settlement Ability to handle exchange- specific settlements: - Settle physical position into new contract at same closing price - Support 80%/20% settlement split for physical trades - Pay 80% at expiry date of futures contract
This is related to ACM-207, ACM- 943, ACM-945
(split)
ACM- 947 Form Contract Amendment Proforma Invoice Processing Ability to Void previous proforma invoice/posting and generate new Proforma Invoice/posting upon Contract Amendment
This was split from ACM-240
(split)
ACM- 965
Purchase Prepayment Report by Vendor The ability to provide a custom report within SAP ACM (or integrated with FI/MM) to monitor vendor prepayments against goods receipt (GR), highlighting outstanding and overpaid
(new)
--- 第215页 ---
S/4HANA Transformation Project Solution Blueprint – Commodity Trading & Risk Management Trade Capture
File Name: S4_P2_ACM_PR05_Blueprint_Trade Capture_V1.10 Status: Final
Page 215 of 215 Req. No. Process Level 3 Requirement Requirement Description Criticality Degree of Change Fit/Gap Assessment Solutions positions, in order to prevent excessive prepayments relative to quantities received.