Professional Documents
Culture Documents
Management
March 2012 - Marcos Rahmeier – SAP Custom Development
Legal Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed
without the permission of SAP. This presentation is not subject to your license agreement or any other
service or subscription agreement with SAP. SAP has no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation and SAP's strategy and possible future
developments, products and/or platforms directions and functionality are all subject to change and
may be changed by SAP at any time for any reason without notice. The information on this document
is not a commitment, promise or legal obligation to deliver any material, code or functionality. This
document is provided without a warranty of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement. This document is for informational purposes and may not be incorporated into a
contract. SAP assumes no responsibility for errors or omissions in this document, and shall have no
liability for damages of any kind including without limitation direct, special, indirect, or consequential
damages that may result from the use of this document. This limitation shall not apply in cases of
intent or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual
results to differ materially from expectations. Readers are cautioned not to place undue reliance on
these forward-looking statements, which speak only as of their dates, and they should not be relied
upon in making purchasing decisions.
Marketing / Producer
SAP Agriculture Contract Management Management
1 2 3 4 5 6 Update
Capture Create Load Data,
Plan Apply Load Settle
Contract Call-Off Settle,
Close
Create Monitor in- Create call-off Capture Determine Trigger quantity
quantity or car transit order with information for settlement amt and quality
lot contract for inventory reference to load based on updates to load
a period of contract available information
time Conduct (optional) Determine pricing, quality
inventory true- material info, weights Generate
Define quality, ups with 3PT, Validate against additional ABDs
optionality, if used available Trigger Group based on final
and tolerance quantity and generation of settlements information and
terms Create contract terms follow on pricing; settle
nomination documents Generate
Establish price (optional) Price not Agency Billing Recognize
(optional) required to be Validate load Documents Revenue
established against contract
Define terms for Settle with Close contract
expenses quality, counterparty line item and
optionality, and via standard contract
tolerance SD/MM billing
and invoicing
Ag Business Partner
Service
Contract(s)
Service
Contract
Ag Company Invoice(s) Ag Customer
Contract
Invoice(s)
Ag Company’s
Warehouse Ag Customer’s
Warehouse
Weights
Weights
and
and
Analysis
Analysis
Ticket Ticket
Ag Business Partner
Service
Contract(s)
Service
Contract
Ag Company Invoice(s) Spot Contract Farmer F
after delivery
by the farmer
Invoice
Ag Company’s
Elevator
Weights
and
Analysis
Ticket
Headquarter in Illinois
Invoice
Commodities intransit
External Sale
Customer 1
External Purchase
Multiple
Inter-company
Sales
Vendor A Internal
Purchase(s) Internal Company as
Intermediary customer
Headquarter in Illinois
Company A in US Company A in US
Profit Center 1 Profit Center 2
Contract or
Sales Order
Washout:
This process occurs where two trading parties in contract mutually agree to no physical
movement of the goods, resulting in the off-set of purchasing and sales obligations with the
same terms (commodity, quantity, quality, time of shipment, fob / delivery point) on both sides.
String
Is a trading scenario where the physical shipment flows through multiple business partners.
The final party at the end of string (who is physically taking the goods) has an interest in obtaining
the documents quickly; therefore this party manually researches the string and prices, and
proposes a net settlement value for all parties involved. If the parties are in a string and the
counterparties agree to settle with their original counterparty it would just be part of standard
settlement (purchase and sell).
Ticket Summary
of all
Warehouse
Receipts by
Farmer
Unapplied quantities need to be recorded and tracked as warehouse receipts and obligations
to the farmer.
Functionality Description
Master Data for DPQS and Material New Master Data providing the capabilities to define qualtity schedules.
Schedule These quality schedules will be linked to the contract during contact
capture.
Master Data for Tolerances New Master Data providing the capabilities to define quantity schedules.
These quantity schedules will be linked to the contract during contact
capture.
Optionalities New functionality to define optionalities which can be "declared" before
and during contract execution.
Material Determination New functionality to define generic material on a "header level" with
specific materials and their characteristics underneath. These Material
Schedules will be in particular assess/executed during contract application
Commodity Contract Maintenance Capturing of contracts with all specfics to Agricultural Commodity
Contracts and Contracts for Grower Origination - Discounts, Premuims and
Quality Schedules, Quantity Tolerances Schedules (Volume/Value),
Optionalities, Material Schedules; supporting also fully and partially priced
scenarios with flexible pricing mechansims throughout the entire lifecycle
of a deal including provisional pricing during various events of a deal
lifecycle (credit limit checks)
Contract Closure / Underfill / Overfill Features and functionalities for explict contract closure, under- and overfill
functionalties during contract execution and follow-up activities
Trade Amendments Various functionalities to allow for trade amendments (shorten,extending
time periods, extending/reducing quantities,…etc.)
Functionality Description
Contract Application Applying one or mulitple loads (tickets) to one or multiple contracts;
capturing mulitiple sets of quality information for the same load if
necessary; Evaluation qualities, optionalitis and quanties of load(s) with
regards to discounts or premiums to be applied for load(s);
manual/automated assignment of pricing lots to loads applied to contract;
adjustment of contract quantities and inventories based on the DOT
evaluation results (to allow also for MTM valuation)
Non-Standard Settlement Capabilties to handle washouts, strings and circles
Settlement Provisional and final settlement calculations with multiple provisional
settlements possible; expense recovery functionality (if expense is
recoverable); cross settlements between contracts including pre-payments,
downpayment, deferred payments; manual and automated settlement
process; functionality allows for seggregation of duties (create, approve,
release); integration into FI
Revenue Recognition functionality to determine when the revenue can be recognized (FI
postings)
Collects movement and inventory information for end of day true up to
Inventory True-Up update 3rd party trading system
Service
Contract(s)
for Expense
Capturing
Contract
Component Pricing
(Futures, Basis)
partially priced contracts
(No Price Established, No
Basis established, No
Futures established)
Capturing of
Planned Pricing can happen at any
Expenses given time before final
(including settlement
auto-accruals
capabilities)
The Load Data Capture provides the ability to manually enter data for the load
into the system through fast entry screen as well as allows to utilize the load
information from any external source (e.g. weighing bridge)
As part of the Load Data Entry there are means provided to manually
enter quality characteristics data
All subsequently generated system documents will reference the Load Data
entered
The application document is an SAP document that will be created after post good
receipt / post goods issue.
The main purpose is to facilitate the contract application and settlement process
enabling functionalities like the application of discount premium quality schedules,
evaluation of tolerances, evaluation of optionalities.
The application process links the application document to the pricing contract.
Ticket
=
Load Data
Contract
Quality
Repository
Final Settlements
Financial settlement of a load or unit using an established price and actual weights
and grades.
Adjustment Settlements
Adjustment settlement can be created for a settlement document after the final
settlement document has been released for invoicing.
Once the stars align, Purchase Realization or Revenue Recognition may occur.
All 4 stars represent events in the life cycle of a contract. When ever one of these events is successfully
completed then an entry/update will be made in the so called Event Registry. An Event Monitor is
“watching” for the completion of events. Once all events are successfully completed (…all stars align)
then the Purchase will be realized or the Revenue will be recognized through the respective account
postings.
Contract