ACM - E2E - Commingled - Storage and Load - Out
ACM - E2E - Commingled - Storage and Load - Out
System Landscape
Please check the currently valid system IDs and active clients on the tab strip SYSTEMS of this
process in the Demo Database.
Users
The commingled scenario uses storage agreements that are contracts between a company and a
vendor outlining the terms and conditions under which goods are stored. The process starts with a
Load-In that will determine if the load is going to be applied to a purchase contract, spot contract or
if the load is going to be part of the commingled stock. Once Load Data Capture is saved and the
load will be applied to commingled stock, then goods movement and application documents are
created automatically in the background. The process continues when the firm settle the 3rd party
goods that are in storage at a plant.
Process flow
1. Storage Agreement
3. Capture Loads
5. Load out
Storage Agreement contract capture is the first step in the process. During storage agreement
contract capture, you define the terms and conditions between a company and a vendor under
which goods will be stored.
Procedure
1. Call up the transaction as follows:
Field Data
Plant 0001
8. Click enter and then select the line and click - Display Item Details at the bottom
Rates Locked 0
13. Press Enter and the Characteristics and Range Details should appear below
14. Click button - Save and you should come back to the Header Data View.
15. Take note of the just created Contract number in order to follow the next process steps:
18. 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.
20. Press button - Back to return to the SAP Easy Access Menu.
The condition records will determine the storage calculation(s). The storage condition records are
assigned to a storage agreement and will be used along the settlement process to settle storage
pricings.
Procedure
21. Call up the transaction as follows:
22. Enter “YPRD” for the Day graduate scale. Note that other condition types, especially for event fees
might be setup, but for PoC YPRD (day graduate scale) will be used.
Field Data
Amount 10,00
Unit EUR
Per 1
UoM Kg
2. Press Enter
Field Data
UoM DAY
Amount 10,00
Unit EUR
Per 1
UoM Kg
Amount 20,00
Amount 30,00
Amount 50,00
Capture Loads
Use
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
2. Call up the transaction as follows:
Field Data
Event Unload
Mode of transport 01
5. Click button
6. Double click in the LDC ID-field
Field Data
Certification category 01
UoM Kg
Field Data
Certification category 01
Analysis type 01
9. In case the Characteristics are not retrieved from the Master data please perform the following
steps:
3. Click - OK
Field Data
11. Press Enter and check if all status-fields turn green - Succes
document creation. You can note down the numbers of the reference document for further
references.
Contract Application
20. Call up the transaction as follows:
Field Data
Status shall be Storage what means that the loads got successfully assigned to a storage
agreement
Use
Refers to the process of settling the 3rd party goods that are in storage at a plant.
Procedure
26. Call up the transaction as follows:
Field Data
29. Enter the following data on the selection screen tab: Note that this is a selection screen; you
might use other selection criteria.
32. In the “Settlement Group” window select line item(s) and to generate Settlement Unit(s)
37. Press - Ok
Field Data
44. Select each settlement group and icon to view details. Select the tabs to see view
details available for viewing.
Load out
Use
Refers to the process to load out 3rd party owned commodities stored at a facility as part of a
storage agreement.
It will be initiated from LDC with new UIS App instruction 35.
Gross Quantity will be used to create the Load-Out Document. LAQ is only calculated
during LOAD-OUT MATCH using the DPQS entered in the selection screen.
During LDC release a LAD will be created without any goods movements. All the necessary
inventory posting movements will happen at the time of LOAD-OUT MATCH.
LAD document will be visible in Orchestration Framework Log.
LAD will be created in ‘Ready to Match’ status and will be changed to ‘Matched’ after
matching.
Procedure
48. Call up the transaction as follows:
Field Data
Event Load
Mode of transport 01
Field Data
Certification category 01
UoM Kg
Field Data
Certification category 01
Analysis type 01
6. Click - OK
Field Data
57. Press Enter and check if all status-fields turn green - Success
58. On the upper screen tab, select the Events tab and click on the icon to determine the
outgoing batch.
Field Data
UoM Kg
69. Select the line and press - Document Flow to display the document flow of the automatic
document creation. You can note down the numbers of the reference document for further
references.
Contract Application
Procedure
Field Data
Match Load-out(s) from a physical storage location to previous commingled and/or stored
Unload(s). The washout of obligation stock by identifying the corresponding unloads for the
specific load-out material and clearing off the quantity from the obligation stock.
A match happens between load outs application documents (LAD, MAD) and stored goods
application documents (CAD, AAD). This is a N:M relationship. For example, 4 LADs can be
matched to 5 CADs, or otherwise
Scenarios:
If there is remaining stored goods quantity, the user can choose to keep it in storage or
scrap it.
78. Double click Load Out Matching in the “Application Workcenter” window
79. Enter the following data: Note that this is the Load Out LDC (LAD)
Field Data
Field Data
91. Check Load Data Capture. Check that the process finished by verifying the automatically
generated documents for your load out document.
Field Data