Professional Documents
Culture Documents
System Landscape
ZDC 400
Users
An intra-company process of a purchase and sale of a commodity between plants within the same
company code or legal entity. To support position management, the process includes a mirroring
process where both purchase and sales documents are created in the background automatically.
These mirrored documents are:
GTM contract
Application document
Settlement document
Process flow
Capture Contract
Create Purchase Order and Call Off to Contract
Load Data Capture – Load Event
Display Application Documents
Load Data Capture – Unload Event
Create, Release and Approve Final Settlement
Run Purchase Realization
Contract capture is the first step in the agricultural commodity contract process. During contract
capture you define the terms and conditions that govern the execution of the remaining steps in the
contract process, including call-off, load data capture, contract application, contract settlement, and
contract closure. The contract details captured include the counterparty, the contract period, the
commodity, the quality terms, and the tolerance terms. When you create a commodity contract, the
system creates a pricing trading contract (TC) in the background. The system uses the pricing TC
along with a logistics TC to manage the contract execution process. For Intra-company contract
types, the lead contract will automatically create a mirror GTM contract in the background. It does
this through GTM output determination. An example would be if the lead contract is on the purchase
side, then the mirror contract would be on the sales side.
During the period of the contract, you can amend the contract terms. For example, you can extend the
period of the contract or increase the contract quantity. However, any contract amendments are
subject to validation, and if a call-off or application document exists for the contract, then certain
amendments are not permitted.
Procedure
Field Data
Distribution Channel 20
Division 00
Plant 0011
Plant 0011
7. Select the Commodity Items tab and click on - Create a new commodity item
8. Enter the following data:
Date to 31.12.2015
9. Press <ENTER>.
13. OPTIONAL - Select Additional Contract Conditions Tab and enter “Any Optionality” for the
Optionality Type
14. OPTIONAL - Enter the following data in the “Additional Optionality Values” area:
15.
17. Click
Price Unit 1
Price Basis 11
Price Unit 1
Price Unit 1
20. Click button - Save and you should come back to the Header Data View. For further
references you can note down the contract number shown in the bottom line.
21. Go to transaction WB22 using the field in the top left. The “Trading Contract Change” window
opens and your external number and the contract number should be already entered.
23. Go to the “Approval” tab and check the “Approval Indicator” box and your name and the current
date should appear below.
The associate responsible for processing a specific trading contract. You can configure your system so
that the logon user is defaulted as the responsible associate. This setting is made in the settings
for the trading contract type.
25. Press button Back to return to the SAP Easy Access Menu.
PO Quantity 1000
Plant 0011
28. Press Enter and click on and enter the following data:
29. Select Confirmations Tab and check the data is set as the following:
Load Data Capture is one of the key functional areas within the SAP Agricultural Management
solution. It comprises the Load Data Capture (LDC) transaction and the Orchestration Framework
(OF) to streamline the capturing, on arrival or departure, of certain attributes of a purchased or sold
load. These attributes are used to determine whether a load conforms to the requirements of the
contract in a planned scenario, to select an appropriate contract to fulfill, or to generate a spot
contract or unassigned load in unplanned scenarios. Load Data Capture allows users to capture
weight, grade, and other logistical data for bulk shipments (both inbound and outbound) of agricultural
commodity products, while the Orchestration Framework oversees the generation of follow-on
documents.
Procedure
1. Call up the transaction as follows:
Field Data
Field Data
Event Load
Mode of transport 01
Field Data
Certification category 01
Field Data
Certification category 01
Analysis type 01
Value 2
Value 1
y
Contract application is the process of linking an application document line item to a pricing trading
contract (TC). The system creates an application document after the generation of a goods receipt or
goods issue (GR/GI) document. For Intra/Inter-company scenarios, two application documents are
generated; one for the purchase side and one for the sales side.
The contract application process links the application document to the pricing TC. The linking occurs
technically through the logistical TC, which is created upon the save of the purchase order (PO) or
sales order (SO).
In a planned purchase scenario, the PO is called-off against a pricing TC. At this point, a link is
established between the logistical TC item and the pricing TC commodity item. The system creates
an application document and establishes a link between that application document and the pricing TC
commodity item.
In both planned and unplanned scenarios, the system validates a load against contract terms. In an
unplanned scenario, you can choose between the following options:
Check if you can apply it to existing contracts, if any, and determine whether the load is to be
applied automatically or manually in the manual application workcenter
Create a spot contract for the load
Place the load in storage and purchase it at a later time
You can also use the manual application workcenter to create, display, and maintain an application
group. By grouping application documents together in application groups, you can facilitate manual
applications.
Procedure
43. Call up the transaction as follows:
Field Data
47. For your application check the status if provisionally applied. Select line item and icon:
Field Data
In this activity, the unload event will be generated to capture the receipt of the goods are the receiving
plant.
Procedure
52. Double click Change LDC Object and enter the following and enter:
Press to execute
53. Select line item and Create then New LDC Event
Field Data
Field Data
Field Data
Certification category 01
Field Data
Analysis type 01
Value 2
Value 1
62. Select .
68. Select button Back to return to the SAP Easy Access Menu.
Use
The final settlement can occur once all pricing conditions for pricing aspect are complete or filled.
During final settlement, the total settlement amount will be calculated minus any previous provisional
settlements.
Procedure
69. Call up the transaction as follows:
Field Data
73. Select line item(s) and click on Simulate Settlement icon - then click on Propose
Groups
79. Press
Field Data
94. Double click Purchase Realization for procurement or Revenue Recognition Processor if sales