SAP Custom Development

Agricultural Contract Management

Configuration Guide

Version Status Date

1.0 Released 21 March 2013

© 2013 SAP AG
Dietmar-Hopp-Allee 16
D-69190 Walldorf
Configuration Guide

Table of Contents

1 Organization .................................................................................................. 4
1.1 Document Administration ............................................................................................... 4
1.1.1 Authors ...................................................................................................................... 4
1.1.2 History ....................................................................................................................... 4
1.2 Intended Group of Readers ............................................................................................ 4

2 Getting Started .............................................................................................. 5

2.1 Prerequisites ................................................................................................................... 5
2.2 Related Information ........................................................................................................ 5

3 Solution Overview......................................................................................... 6
3.1 System Landscape ......................................................................................................... 6
3.1.1 SAP ERP 6.0 ............................................................................................................. 6
3.1.2 SAP PI ....................................................................................................................... 6
3.1.3 Third Party Trading System ....................................................................................... 6
3.2 Scenarios ........................................................................................................................ 6

4 ACM Customizing ......................................................................................... 9

4.1 General Settings ............................................................................................................. 9
4.1.1 Basic Settings ............................................................................................................ 9
4.1.2 Setup For Master Data ............................................................................................ 32
4.1.3 Call-Off .................................................................................................................... 42
4.1.4 Load Data Capture .................................................................................................. 45
4.1.5 Orchestration Framework ........................................................................................ 54
4.1.6 Contract Application ................................................................................................ 55
4.1.7 Settlement ............................................................................................................... 62
4.1.8 Revenue Recognition .............................................................................................. 81
4.2 Scenario Specific Settings ............................................................................................ 84
4.2.1 Back-to-Back ........................................................................................................... 84
4.2.2 Intercompany, Intracompany ................................................................................... 88
4.2.3 Comingled Settings ................................................................................................. 91
4.3 Enhancements/BADIs .................................................................................................. 94
4.3.1 Archiving .................................................................................................................. 96
4.3.2 Copy Control ............................................................................................................ 99
4.3.3 Contract Management ........................................................................................... 100
4.3.4 Expense Management .......................................................................................... 105
4.3.5 Inventory True-up .................................................................................................. 107

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 2 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.6 Master Data ........................................................................................................... 109

4.3.7 Optionality.............................................................................................................. 112
4.3.8 Load Data Capture ................................................................................................ 116
4.3.9 SIT Cockpit ............................................................................................................ 119
4.3.10 Contract Application .............................................................................................. 120
4.3.11 Contract Settlement ............................................................................................... 134
4.3.12 Enterprise Services ............................................................................................... 137
4.3.13 Customer Namespace ........................................................................................... 139
4.4 Country Specific Settings ........................................................................................... 142
4.4.1 Brazil ...................................................................................................................... 143

5 Rules Maintenance in Business Rules Framework ............................... 150

5.1 Steps for Maintaining BRF+ Catalogue ...................................................................... 150
5.1.1 Step 1-> Launch BRF+ .......................................................................................... 150
5.1.2 Step 2-> Add Catalog ............................................................................................ 153
5.1.3 Step 3-> Maintenance of values in Catalog .......................................................... 157
5.2 Maintenance of BRF+ for ACM Processes................................................................. 160
5.2.1 BRF+ Rules for Capturing Contracts ..................................................................... 160
5.2.2 BRF+ Rules for Managing Expenses .................................................................... 162
5.2.3 BRF+ Rules for Managing Call-offs ....................................................................... 163
5.2.4 BRF+ Rules for Capturing Load Data ................................................................... 166
5.2.5 BRF+ Rules for Processing Contract Applications ................................................ 170
5.2.6 BRF+ Rules for Settling Contracts ........................................................................ 173

6 Orchestration Framework Configuration ................................................ 175

6.1 Basic Configuration .................................................................................................... 175
6.1.1 Configuration of Junction function ......................................................................... 175
6.1.2 Ticket Type and Execution Mode Configuration for OF ........................................ 183
6.1.3 Configuration of Business Rules (OF rules Framework) ....................................... 191
6.2 OF Configuration for Individual Scenarios .................................................................. 191
6.2.1 External Purchase ................................................................................................. 193
6.2.2 External Sale ......................................................................................................... 204
6.2.3 Inter/Intra Company Sale & Purchase ................................................................... 209
6.2.4 Returns Purchase and Sale .................................................................................. 215
6.2.5 Regular Spot, Accumulate to Own, Undecided, Commingled .............................. 221
6.2.6 Application Call to OE ........................................................................................... 223
6.3 Error Processing ......................................................................................................... 225
6.4 List of API’s ................................................................................................................. 229

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 3 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

1 Organization
1.1 Document Administration
1.1.1 Authors
Name Company Project Role/Comment

Venkatesan Kanna SAP America Author

Alesia Harwood SAP America Author
Chandrakanth Bhattiprolu SAP Labs, LLC. Author
Kirti Schoener SAP Labs, LLC. Reviewer
Alexander Wrobel SAP Labs, LLC. Reviewer
Gabriele Weigel SAP America Reviewer
Pam Keiter SAP America Reviewer

1.1.2 History

Date Version Chapter Name Change/Enhancement Agreed with

1.2 Intended Group of Readers

Target audience:
 Consultants
 Project Managers
 Process Owners

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 4 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

2 Getting Started
This Configuration Documentation provides a proposal for the technical implementation and configuration
of the Agricultural Contract Management (ACM) solution.
The scenarios addressed below include proposed configuration for both standard and ACM functionality.
The business scenarios are only intended as models and do not necessarily run the way they are
described here in your customer-specific system landscape. Ensure to check your requirements and
systems to determine whether these scenarios can be used productively at your site. Furthermore, we
recommend that you test these scenarios thoroughly in your test systems to ensure they are complete
and free of errors before going live.

2.1 Prerequisites
You must read the following SAP Notes before you start the installation. These SAP Notes contain the
most recent information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at http://service.sap.com/notes.

SAP Note Number Title Description

1773636 Release Strategy for ABAP See this note for information
Add-On ACCGO about planning the
installation and upgrade of
the SAP Agricultural Contract
Management.

2.2 Related Information

The operations information for SAP Agricultural Contract Management is included in the Operations
Information section of the Application Help.
For more information, see the SAP Help Portal at http://help.sap.com → SAP Business Suite →
SAP ERP Add-Ons → SAP Agricultural Contract Management.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 5 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

3 Solution Overview
SAP Agricultural Contract Management enables commodity traders to capture and manage these
complex commodity contracts and related processes. It is an end-to-end solution that supports the full
contract life-cycle, including the capture of the contract terms, the logistical processing, and the final
settlement and closure.
To use this solution, the corporate customers must install SAP Agricultural Contract Management as an
add-on to their SAP ERP system. Additionally, SAP Global Trade Management and SAP Trader's and
Scheduler's Workbench must be active.
SAP Agricultural Contract Management is also fully integrated with SAP Financial Accounting.

3.1 System Landscape

SAP Agricultural Contract Management consists of the following software units:

3.1.1 SAP ERP 6.0

SAP Agricultural Contract Management is an add-on on SAP ERP 6.0 Enhancement Package 6.

3.1.2 SAP PI
SAP PI system is an optional system. It can be used to integrate SAP ERP system with a Third Party
trading system.

3.1.3 Third Party Trading System

This is an optional system and can be integrated to SAP ERP system through SAP PI system.

3.2 Scenarios
This section provides an overview of which business scenario of SAP Agricultural Contract Management
uses which software unit.
For the latest component version and patch level requirements, see SAP Note 1773636.

This Master Guide provides just one way to implement each business scenario. For other
ways to implement business scenarios, see the Scenario & Process Component List in
SAP Service Marketplace at http://service.sap.com/scl. The Scenario & Process
Component List helps you to find realization alternatives for SAP solutions, business
scenarios and processes. It shows you which application components are needed to
realize a business scenario or process.

Business Software Units

Scenario
Key: X = mandatory (O) = optional

SAP ERP SAP PI Third Party

6.0 Integration

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 6 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Third Party X (O) (O)

Purchase

Third Party Sale X (O) (O)

Intercompany or X (O) (O)

Intracompany
Trade
Back-to-back X (O) (O)
Trade

Spot Purchase X (O) (O)

Commingled X (O) (O)

Stock
Management
Processing X (O) (O)
Washouts and
Circles
Inventory True-up X X X

The following technical architecture model illustrates the landscape of SAP Agricultural Contract
Management:

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 7 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

SAP ERP

Configuration/master data

Quality Tolerance Value tables

schedules schedules

Commodity contract CAS

Application
Pricing TC Logistic TC
and Order
Data capture for
R
R
Contract
R
loads (LDC)
Contract capture UI
Capture Call off Standard order
process creation Standard doc
generation (OF)
Price component
Material
Declared
determination
contract
Third SAP
Quality options
party PI Application doc
trading requirements
generation
system
Planned and
unplanned R
Contract options
expenses
Manual or rules-
based application
Tolerance data

Planned and Spot contract

unplanned request
expenses

Application
Expense management R message
Pricing distribution using
pricing rules
Vendor billing
document R

R
Agency business
document R R
Contract settlement
Standard billing/invoicing
R
Repository for
provisional prices

R
Inventory update framework R

R R Immediate Inventory update Revenue

updates/periodic rules\configuration recognition
updates R

R R

Figure 1: Technical Architecture Model for SAP Agricultural Contract Management

SAP Agricultural Contract Management is an add-on to SAP ERP 6.0. Enhancement Package 6 or higher
with GTM, iTSW and Business Function ACCGO activated.
SAP PI and Third Party trading system are optional systems. Therefore, the integration between these
systems is needed only if some trading functionalities are carried out in the Third Party trading system.

We strongly recommend that you use a minimal system landscape for test and demo
purposes only. For performance, scalability, high availability, and security reasons, do not
use a minimal system landscape as your production landscape.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 8 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4 ACM Customizing
4.1 General Settings
Note that the customizing transactions for ACM may be reached in two ways. Either by running
transaction /ACCGO/CUST_MAINTAIN, or by running standard SAP customizing (transaction SPRO),
and navigating as shown here:
SAP Customizing Implementation Guide
 Logistics – General
o SAP Global Trade Management
 Agricultural Contract Management

4.1.1 Basic Settings

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 9 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.1 Activate Switch for Systems Integration

Use

In this Customizing activity, you can activate the switch for systems integration:

ECC Only Solution: Indicates that the system is not integrated with a third party trading system. For ECC only
solution the business function /ACCGO/BF_ACC should be activated using transaction SFW5.

3rd Party Integration: Indicates that the system is integrated with a third party trading system.. For 3rd Party
Integration the business function /ACCGO/BF_3PT should be activated using transaction SFW5.

Based on the business fuction that is activated, the details in the screen will be displayed accordingly.

Once you have activated an option, it is not possible to change this Customizing setting.

Standard settings

Optionally, SAP Agricultural Contract Management can be integrated with a third party system for additional
functions such as risk analytics and portfolio management. In this scenario, contracts are captured through the
third party system. The third party system then sends the data for any new contracts, contract amendments, or
cancellations to SAP Agricultural Contract Management. In turn, SAP Agricultural Contract Management sends
certain information to the third party trading system. This includes the following types of information:

 Reference data, such as Discount Premium Quality Schedules, tolerance schedules, and optionality
categories

 Pricing consumption at certain goods movements or settlement events

 Goods movement information

4.1.1.2 Maintain Contract Type Determination

Here, the GTM contract types are assigned to a contract type that determines their behavior within the ACM solution. The GTM
contract types must first be configured prior to configuring this customizing table. The system uses the contract type to
determine which tab pages to display on the contract capture and maintenance screens. Contract types can
be sub-classified as follows:

Code Contract
C Commodity Contract

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 10 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

D Commodity Contract STO Relevant

S Spot
I Intercompany Contract
R Intracompany Contract

4.1.1.3 Maintain Quantity Types and Profiles

Quantity types are defined and assigned to quantity profiles. The profiles are then assigned to GTM
contract types. This configuration determines in the contract what quantity types and in what sequence
should the quantity types appear when selecting the icon for “show quantity types” in the GTM contract
transactions, Commodity Items tab.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 11 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 12 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.4 Manage Layout for GTM Contracts

This configuration defines what ACM-specific tabs appear in the GTM transactions and in what sequence.
There are three sections of this configuration:
 Tabs are maintained/defined with a key of Tab Name. The tab is associated with a program and
screen including subscreens

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 13 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

.
 Tabs are put into groups – each group can contain one or multiple tabs and their sequence, and if
they are display only.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 14 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 15 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Tab groups are assigned to business data by:

o Company Code
o GTM Contract Type
o Sales/Purchase area

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 16 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.5 Maintain Text Assignments

Use

In this Customizing activity, you maintain the assignment of text objects and text IDs to applications and sub-
applications respectively.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 17 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For example, a text object can be assigned to one of the following applications:

 Application

 Commodity Contracts

 Credit Sales and Deferred Payments (CSDP)

 Discount Premium Quality Schedules (DPQS)

 Settlement

 Load Data Capture

Text IDs can be assigned to one of the following sub-applications:

 Internal Notes

 External Notes

 Transportation Details

 Comments

 Weight Remarks

 Analysis Remarks

 Inspection Instructions

 Inspection Results

Requirements

You have created the text objects and text IDs using transaction SE75.

Activities

First, you maintain the assignment of a text object to an application. Then, you can select a particular text
object and maintain the assignment of text IDs to sub-applications.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 18 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.6 Maintain Mode and Means of Transport

Use

In this Customizing activity, you firstly maintain the possible modes of transport, then you maintain the possible
means of transport for each mode of transport relevant for SAP Agricultural Contract Management.

Requirements

You must maintain the modes of transport in Customizing for Logistics Execution under Shipping -> Basic
Shipping Functions -> Routes -> Define Routes -> Define Modes of Transport.

Example

You can define modes of transport such as Road, Sea, and Air. You can then, for example, specify the means
of transport for Road as 25' Truck or 30' Truck.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 19 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.7 Configure Related Trade Types

Use

In this Customizing activity, you define the settings that determine which information can be maintained for the
various related trade types in the Related Trade tab page of a trading contract line item of the GTM trade
transactions.

Activities

The following options are available:

 Allow Maintenance

Select this checkbox if you want to allow the user to maintain this related trade type.

 Related Trade in GTM

Select this checkbox to make this field editable.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 20 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 External Rel. Trade

Select this checkbox to make this field editable.

 Qty Reqd

Select this checkbox to allow the user to maintain the Quantity field in the Related Trade tab page.

 Sts Reqd

Select this checkbox to allow the user to maintain the Status field in the Related Trade tab page.

4.1.1.8 Allow maintenance of Backdated Master Data

Use

In this Customizing activity, you specify whether to allow the maintenance of Discount Premium Quality
Schedule (DPQS) master data with a validity date in the past.

Activities

You have the following options:

 Select the Backdate checkbox to allow backdated DPQS maintenance.

 Deselect the Backdate checkbox to prevent backdated DPQS maintenance.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 21 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.9 Maintain Title Transfer Settings

Use

In this Customizing activity, you configure the title transfer type for international commercial terms
(INCOTERMS).

Activities

You enter the incoterm and then choose one of the following title transfer options:

 Title Transfer at Origin

 Title Transfer in Transit

 Title Transfer at Destination

Example

For example, for the incoterm Free on Board (FOB) you could choose Title Transfer at Origin.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 22 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.10 Process parallelization settings

Use

In this Customizing activity, you maintain the settings for parallel processing.

Activities

You perform the following activities:

1. Select the Process Type.

2. Enter the Logon/Server Group.
3. Enter the number of tasks to be run in parallel.

4.1.1.11 Maintain Currency Mapping

Use

In this Customizing activity, you map an SAP currency code to a trading currency and the relevant ISO
currency code.

The purpose of this Customizing activity is to allow more than 2 decimal places in a currency value field.

Example

For example, you can map the SAP currency USD (supports only 2 decimal places) to the trading currency
USDN (supports more than 2 decimal places).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 23 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.12 Trading Contract Cancellation Code

Use

In this Customizing activity, you maintain cancellation codes which are relevant for Trading Contract
cancellation. These fields are accessible in the Cancellation tab of the GTM contract transactions.

Reason for cancellation text can be maintained along with its code.

Example

Below are the examples to maintain.

01 - Waste

02 - Out of Season Stock

03 - Found Cheaper

4.1.1.13 Status Management

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 24 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this Customizing activity, you maintain the mapping between the selection ID and their status (of application
process, settlement process, etc).

Requirements

Object type, Selection profile ID & System status should be maintained.

Activities

To maintain the mapping, proceed as follows:

1. Click New Entries.

2. Define the following fields:

o Doc. Sts (Document status)

o OTy (object type)

o SelProf (selection ID - status selection profile)

o SysSt (system status)

3. Save the entries.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 25 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.14 Optionality
4.1.1.14.1 Maintain Optionality Customizing

Use

You use this configuration table to store check tables for all the optionality categories that are defined. You can
maintain the value type and permitted UoM for the respective optionality category IDs.

Requirements

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 26 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

You have maintained the optionality categories in the optionality table.

Example

You can maintain the entries as follows where the plant is an optionality and the entry will be validated by the
plant table, T001W:

Field Name Value

Opt Cat. Id 01
Value Type PLANT
Check Table Name T001W
Search Help CC_WERKS
Value UoM Permitted N
Time UoM Permitted N

4.1.1.14.2 Maintain Optionality Customizing

Use

You use this table to maintain the optionality category IDs and text. The categories delivered are as follows:

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 27 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

1. Load Location
2. Discharge Location
3. Incoterms
4. Mode of Transport
5. Means of Transport
6. Load Rate
7. Discharge Rate
8. Delivery Period
9. Crop Season
10. Source Location

You can maintain any custom optionality category in the provided namespace.

Example

You can maintain the custom optionality category as:

Category ID Optionality Text/Field on Application

Y1 Custom Optionality

4.1.1.15 Crop Season

4.1.1.15.1 Maintain Crop Season ID

Use

In this Customizing activity, you maintain Crop Season IDs and their associated descriptions.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 28 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Example

ID Description

01 Spring Wheat 2011

02 Fall Wheat 2011

4.1.1.15.2 Maintain Crop Season ID

Use

In this Customizing activity, you maintain the crop season IDs for various materials with their season start and
end dates.

Example

For example, you could maintain the entries for Material 7 as follows:

Material Crop Season ID Season Start Season End

7 01 01.12.2011 30.06.2012
7 02 01.07.2012 30.12.2012

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 29 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.1.16 Business Rules

4.1.1.16.1 Maintain Match Criteria

Use

This Customizing maintains the match criteria needed to evaluate selection rules. It lets the customer add
additional checks during contract application or call-off. Once the match ID is assigned, the function modules
assigned to the match ID get executed.

Activities

You must create a function module and a then check ID must be created for this function module.

Several check IDs can be grouped under one match ID.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 30 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 31 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.2 Setup For Master Data

Some of the functions in ‘Setup for Master Data’ are covered within their relevant sections elsewhere in
the document.

4.1.2.1 Pricing Aspects

4.1.2.1.1 Assign Pricing Condition to Pricing Condition Type Category

Use

In this Customizing activity, you maintain the pricing condition type category for a condition type.

The Customizing of the condition type determines the condition that is maintained, such as the pricing aspect
fields open for input and the inputs that are accepted, for a pricing aspect. For example, if a percentage
condition is defined, condition pricing unit or condition unit cannot be the input.

In this step, you further determine the behavior of the condition type for use in pricing aspect calculations.

The pricing condition type categories available are as follows:

 Basis

 Futures

 Index

 Ratio

Requirements

You have defined pricing aspect types in Customizing under Logistics General > Global Trade Management >
Pricing > Purchasing or Sales > Define Condition Types.

There should be a maximum of 1 pricing condition of each category in a pricing aspect. Only certain
combinations of condition categories are allowed in a single pricing aspect. Delivered calculations are
expecting this. Exceptions are not prohibited, but custom coding is required to complete calculations that do not
conform to this practice.

In general, pricing aspects should be defined with conditions in any of the following condition type categories:

 1 Futures and 1 Basis condition type category

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 32 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 1 Index and 1 Basis condition type category

 1 Futures and 1 Ratio condition type category

4.1.2.1.2 Assign Pricing Aspect to Pricing Aspect Type

Use

In this Customizing activity, you assign a pricing aspect type to a logistical side (purchasing or sales) and
pricing aspect. Pricing aspect types are used to determine which pricing aspects are relevant for different
calculations, such as for regular pricing or for overfill pricing.

Each pricing aspect may only be assigned to one pricing aspect type per logistical side.

When you assign pricing aspects to a commodity item in a contract, you can assign a pricing aspect type of
“Pricing relevant” to be used to calculate pricing for the contracted commodity item quantity, or you can assign
a pricing aspect type of “Overfill relevant” to be used to calculate pricing for a quantity in excess of the
contracted quantity, etc.

Requirements

You have defined pricing aspect types in Customizing under Logistics - General -> Global Trade Management -
> Trading Contract -> Commodity Items and Pricing Aspects -> Define Pricing Aspects.

Example

If a commodity item quantity is 1000 KG, you can assign the pricing aspect “ABCD”, which is defined as a
“Pricing relevant” type, for the entire 1000 KG. You can also assign different pricing to the quantity by
assigning multiple “ABCD” pricing aspects (e.g. 4 “ABCD” aspects, each for 250 KG, and each with different
pricing condition values). When pricing for the 1000 KG is calculated, the pricing aspects define as “Pricing
relevant” type. In this case, all the “ABCD” aspects will be retrieved and used for the calculation.

If the load related to this commodity item contained more than 1000 KG, say 1150 KG, you can assign an
additional pricing aspect type for the excess quantity of 150 KG. This would be an “Overfill relevant” type, which
would only be used for price calculation of the excess quantity.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 33 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.2.2 Tolerances
4.1.2.2.1 Maintain Tolerance Types

Use

In this Customizing activity, you maintain tolerance type IDs and descriptions for use in commodity contracts.
These ID values are used in the Tolerance Type ID field on the Tolerance tab page in a commodity contract.
They specify how a tolerance schedule should be applied, for example, to a delivery, a delivery period, or an
entire contract. The logic is built within the tolerance evaluation program only for these three tolerance types.

Activities

You enter an ID (Tol. Type. ID) and a Tolerance Type Description for each of the possible tolerance types.

Example

Tol ID Rel Tol.Typ.ID Tolerance Type Description

Commodity Contract 01 Per Delivery
Commodity Contract 02 Per Delivery Period
Commodity Contract 03 Per Contract

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 34 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.2.3 DPQS
4.1.2.3.1 Maintain Class Type for Material Determination

Use

In this Customizing activity, you maintain the class type that is used for material determination. A material
belongs to a material determination group. The materials in a group share a set of characteristics that can be
measured and used during the evaluation of Discount Premium Quality Schedules (DPQS).

Requirements

You must first have defined material class types in Cross-Application Components > Classification System >
Classes > Maintain Object Types and Class Types.

Activities

Create an entry for each of the following class usages:

 For Volume/Value Schedule – This is the material class type used for adding material classes and their
respective material characteristics that impact volume and value discounts and premiums for each
commodity type.

 Reference Commodity Code – This is the material class that is used for material schedules where you
indicate what reference material is assigned to a material (i.e. Generic material).

 Rank – This material class is used to further rank the material schedule should multiple materials fall
within the material schedule.

Enter a class type for each usage. A Characteristic Name must be assigned to the Reference Commodity
Code and Rank usages only.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 35 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.2.3.2 Maintain Number Range for DPQS

Use

In this Customizing activity, you maintain the number range for value schedule and volume schedule master
data. Each time a new value schedule or volume schedule is created, the system uses this number range to
generate a unique ID.

Activities

To define a number range enter a From No. (From Number) and a To Number. Note that you can define more
than one number range; however, the number ranges must not overlap.

4.1.2.3.3 Maintain DPQS Parameters

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 36 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this Customizing activity, you maintain the Discount Premium Quality Schedule (DPQS) parameters.

Requirements

You have maintained certification categories.

Activities

You maintain the following parameters:

 Governing Analysis

You enter the governing analysis hierarchy, origin/destination details, and certification category. The
following are examples of governing analysis codes:
Code Description
ZDOA Destination Official Analysis
ZDCA Destination Certified Analysis

 Governing Terms

You enter governing terms, which can be used to indicate the price, quality, or quantity of the contract.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 37 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Governing Weights

You enter a governing weight code and description for each governing weight. You can also create a
hierarchy of governing weights.. The governing weights are used in load data capture and contract
application. A weight can be considered final when either the specified weight is received, or a higher
certification. This weight is used to determine the source of the quantity to use during DPQS volume
adjustments. The following is an example of a governing weight hierarchy:
LDC
Code for Implied
Code Origin/Destination Certification Description Status
Parent Hierarchy
Category
Destination
ZDCW ZDOW 2 Destination 02 Certified
Analysis
Destination
ZDHW ZDCW 3 Destination 03
House Analysis
Destination Transferred
ZDOW 1 Destination 01
Official Analysis to 3PT

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 38 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Regulatory Agencies

You enter the regulatory agencies (Agent ID and Description). The following are examples of
regulatory agencies:
Agent ID Description
NAEGA North American Export Grain Assoc
NGFA National Grain and Feed Association

 Calculation Rules

You enter calculation rules (a code and description), and indicate if parameters are required. You must
then define the parameters for each rule that requires parameters.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 39 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Derived Rules

You enter the derived rules (a code and description). The following are examples of derived rules:
Code Description
A Additive
H Take Higher
L Take Lower
S Subtractive

 Averaging Methods

You enter the averaging methods (a code and description).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 40 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.2.3.4 Maintain Rounding Parameters for Tiered Prorated

Use

In this Customizing activity, you indicate if rounding (up and down) is enabled in Discount Premium Quality
Schedule (DPQS) master data for the Tiered Prorated calculation method, which is used in value schedules
and volume schedules.

Activities

You choose the relevant calculation method and then select the Enable Rounding checkbox.

4.1.2.3.5 Assign DPQS Value schedule to location

Transaction /ACCGO/TSW_VSA

4.1.2.3.1 Assign DPQS Volume schedule to location

Transaction BRFPlus

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 41 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.3 Call-Off

4.1.3.1 Determine Order Type for Sales Contracts

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 42 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this Customizing activity, you establish the order types that can be called off against a sales-side GTM
(Global Trade Management) contract. In addition, you determine the title transfer types and the sales document
types that can be associated with each trading contract type.

As a dependent level the item categories for the sales order type are also maintained.

Requirements

The mapping of the incoterms to the title transfer values should have been maintained prior in Logistics -
General -> SAP Global Trade Managernent -> Agricultural Contract Management -> Basic Settings -> Maintain
Title Transfer Settings

4.1.3.2 Determine Order Type for Purchasing Contractsacts

Use

In this Customizing activity, you establish the order types that can be called off against a purchase-side GTM
(Global Trade Management) contract. In addition, you determine the title transfer types and the item categories
for the purchase order type that can be associated with each trading contract type.

As a dependent level the item categories for the purchase order type are also maintained.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 43 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Requirements

The mapping of the incoterms to the title transfer values should have been maintained prior in Logistics -
General -> SAP Global Trade Managernent -> Agricultural Contract Management -> Basic Settings -> Maintain
Title Transfer Settings

4.1.3.3 Maintain CAS relevancy for Sales Orders

Use

In this Customizing activity, you determine the sales order item categories that are relevant for call-off and its
ensuing features available in the application.

If you do not set the indicator for a particular item category, then the Call-Off tab page at item level will not be
active for items within that item category. In addition, the system will not create an application document for
such items.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 44 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.3.4 Maintain CAS relevancy for Purchase Orders

Use

In this Customizing activity, you determine the purchase order types that are relevant for call-off and its ensuing
features available in the application.

If you do not set the indicator for a particular purchase order type, then the Call-Off tab page will not be active
at the item level/header level for that purchase order type. In addition, the system will not create an application
document for such purchase orders.

4.1.4 Load Data Capture

4.1.4.1 Load Data Capture Customizing
Within the Root Node of the ACM Customizing is the customizing for Load Data Capture (LDC) and
Orchestration Framework (OF)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 45 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.4.1.1 Maintain Number Range for LDC

Use

In this Customizing activity, you can maintain the number range (that is, the highest and lowest number that the
system will allow) for creating a Load Data Capture (LDC) object.

Requirements

You have activated SAP Agricultural Contract Management.

Activities

Define the intervals for the number range for a Load Data Capture object. The NR status field displays the
current number, and is internally generated by the system.

Note: The number range number, which identifies a number range interval within an object or sub object, is '01'.

Execute this node and maintain interval ‘01’. Below are suggested number ranges:

4.1.4.1.2 Define LDC Event Type

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 46 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Use

In this Customizing activity, you can define the different event types that are used for recording events within
the Load Data Capture (LDC) Work Center for custom processes. The event type incorporates specification of
the event ID and the structure of the data associated with the event. You must define an event type before an
event of that type can be recorded in LDC.

Activities

Select from the following standard event types (note that the delivered LDC works with only these two event
types) :

 01: Load

 02: Unload

4.1.4.1.3 Maintain Analysis Types

Use

In this Customizing activity, you can define the different analysis types that are used for recording the grades
within the Load Data Capture (LDC) Work Center.

As a load arrives, the system captures the certification or analysis type for the available quality characteristic
information. The analysis type is the type of analysis that was performed on the Load or Unload event (for
example, whether it was performed in-house or by 3rd party).

Activities

Here, you enter the types of analyses that are performed at your facilities so as to enable multiple values for
analyses to be captured for a load. (By doing so, you also instruct the system as to the minimal level required
to allow final application.) Once defined, your settings appear in the Analysis Details tab page in the LDC Work
Center, as selection options for the Analysis Type field.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 47 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.4.1.4 Maintain Certification Category

Use

In this Customizing activity, you define the different certification categories that are used to capture the weights
and grades information during Load Data Capture (LDC). As a load arrives, the system captures the
certification category for the available quality characteristic information. During contract application, this value is
measured against the certification required by the contract, and, if it is the same or a higher level, no further
characteristic values are required (though they may be captured).

Activities

You can choose from the following categories:

 01: Official

 02: Certified

 03: House

 04: Nota Fiscal (valid only for Brazil)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 48 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

It should be noted that when consumed in application and settlement, the certification categories are
considered to have a hierarchy. This hierarchy is set up in DPQS Configuration.

4.1.4.1.5 Application Instructions

Application instructions which are recorded on the LDC event determine the behavior of the Orchestration
Framework (see separate OF Configuration Guide). The below instructions are delivered. Additional
ones may be added, but RICEF work may be required to account for edits and the orchestration
framework behavior.

Use

In this Customizing activity, you define the different application instructions against which a load is recorded
during Load Data Capture (LDC).

Activities

The following options are available:

 03: Existing Contract

You make this setting if you want the application document to be applied to an existing contract (using
application rules).

 04:Open Contract

You make this setting if you want the application document to be applied to an existing sales order or
purchase order (using application rules).
.

 05: Regular Spot

You make this setting if you want the system to generate an automatic (spot) contract in an unplanned
scenario. In this case, the application documents are marked 'Awaiting Spot' in the background, until
further processing is performed in the Manual Application Workcenter to generate the spot contract.

 06: Accumulate to Own

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 49 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

You make this setting if you wish the system to create an accumulate to own contract upon receiving
the first load from a vendor, after which the quantities from future loads will be accumulated or updated
to that contract. This is a type of Spot contract, but the difference is that the accumulation occurs over
a period of time before the ‘Ready to Price’ indicator is set. It is mainly used for commodity purchase
from vendors in an unplanned scenario.

 07: Accumulate to Store

You make this setting if the supplier instructs you that there will be multiple loads and that all are to be
stored but not yet purchased by the Company. In this scenario, the load is processed as commingled
stock.

 08: Returns

You make this setting if you want the system to create a return type application document for a
purchase return or sales return.

 10: Unassigned

You make this setting if you want the system to generate an unassigned load in an unplanned
scenario. In this scenario, the load is processed as commingled stock.

4.1.4.1.6 Define Attributes for MOT

Use

In this Customizing activity, you define which attributes are present in in the Load Data Capture (LDC) screen if
a particular mode of transport is selected. For example, if you select the mode of transport Rail, you can
customize the attributes so that only the Lead Car No, No. of Cars, and Vehicle ID fields appear for input in the
LDC screen.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 50 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Activities

To make this setting, complete the following steps:

1. In the Determine Work Area: Entry dialog box, select a mode of transport from the following options:

o 01: Road

o 02: Rail

o 03: Sea

o 04: Inland Waterway

o 05: Air

o 06: Postal Service

2. Choose Continue. In the Maintenance View for MOT Screen Attributes view, choose New Entries.
3. Select, from the dropdown list, the attributes for the mode of transport you have defined for the load
in question. Save your entries.

4.1.4.1.7 LDC Configuration Overrides (transaction /ACCGO/UIS_CUST - Setup LDC)

It is possible to limit which of the configuration options are available per location. However, if this data is
not maintained, all configurations shall be available at the relevant event location. To limit the options
available at an Event Location:
 Maintain Relevant TSW Location Types (where LDC events will be recorded or will occur)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 51 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 For Each Location Type, maintain the locations (where LDC events will be recorded or will occur)
 For each Location, Maintain:
o Allowed Modes of Transport
o Allowed Analysis Types
o Allowed Certification Categories
o Allowed Analysis (Regulatory) Agencies
o
4.1.4.1.8 Set up Master data for LDC

Transaction /ACCGO/UIS_CUST

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 52 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.4.1.9 Maintain TSW locations

/ACCGO/TSW_CUS

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 53 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.5 Orchestration Framework

Please refer to Section 6.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 54 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6 Contract Application

4.1.6.1 Contract Application – Configuration (SPRO)

4.1.6.1.1 Maintain Number range for Application document

Use

In this Customizing activity, you maintain the number range intervals for Application Document types. You must
do this before you perform the Customizing activity Maintain Application Document Types.

The value in the No. field determines the type of contract application document and the area to which the
contract application document belongs. For example, No. 01 is of CAD Document Type and it is for Purchase,
No. 02 is of IAP Document Type and it is for Intracompany Purchase.

You must enter a valid value in the NR Status field depending on the From No. and To No. The numbering of
the contract application document begins at the number maintained in NR Status field.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 55 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6.1.2 Maintain Application Document Type

Use

In this Customizing activity, you determine the types of application document. You can also maintain the
relation between a contract application document type and item category. To create any application document
type, enter the following details:

 Description of the application document type

 Number range interval

 Item number starting range

 Item increment

 Document type category

The document type categories available are as follows:

o Purchase

o Sales

o Inter-company Purchase

o Inter-company Sales

o Intra-company Purchase

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 56 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

o Intra-company Sales

o Returns

o Washout

 Item generation mode

This field governs whether the application document has a true line item or not. A true line item
maintains the identity of the load, for example the delivered material instead of the derived material.
The values for this field are as follows:

o Normal (without True Item)

o With True Item

 Item category

This field determines whether the item is relevant for application or for commingled application, and so
on.

Requirements

You have maintained the number intervals for application document types in Customizing under Maintain
Application Number Range for Application Document.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 57 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6.1.3 Maintain Application document item category

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 58 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6.1.4 Maintain Movement types relevant for application document

4.1.6.2 Maintain Number Range for Application Group

Use

In this Customizing activity, you determine the number range intervals for contract application groups. Contract
application groups are used to group multiple application documents together for convenient processing.

The value in the No. field determines the type of contract application group and the area to which it belongs.

You must enter a valid value in the NR Status field (falling between the From No. and To No. values). The
numbering of the contract application group begins at the number maintained in NR Status field.

4.1.6.3 Maintain Number Range for Application Process

Use

In this Customizing activity, you determine number range intervals for contract application processes.

Requirements

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 59 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For contract application processes, a unique number is assigned to each process step as follows:.

1. Overfill ID

2. Underfill ID

3. Spot Contract Unique ID

4. Accumulate to Own Contract Unique ID

5. Return Application Unique ID

A number range interval must be defined for each of the above steps.

Activities

To determine a number range, you create a new number interval as follows:

o Specify an alphanumeric key using up to 2 characters.

o Specify the limits of the number range interval. The individual number range intervals may not overlap and
there may only be one instance of each number.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 60 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6.3.1 Overfill ID
Number range object - /ACCGO/AID
Configurable Parameter ID - GC_OVERFILL_OBJECT
Number range interval - 05
Configurable Parameter ID - GC_OVERFILL_RANGE

4.1.6.3.2 Underfill ID
Number range object - /ACCGO/AID
Configurable Parameter ID - GC_UNDERFILL_OBJ
Number range interval - 03
Configurable Parameter ID - GC_UNDERFILL_NR_INT

4.1.6.3.3 Spot Unique ID

Number range object - /ACCGO/AID
Configurable Parameter ID - GC_SPOT_NR
Number range interval - 07
Configurable Parameter ID - GC_SPOT_NR_INIT

4.1.6.3.4 Accumulate to Own ID

Number range object - /ACCGO/AID
Configurable Parameter ID - GC_SPOT_NR
Number range interval - 08
Configurable Parameter ID - GC_AO_SPOT_NR_INIT

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 61 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.6.4 Maintain Number Range for Application Process Sequence

Use

In this Customizing activity, you determine the number range intervals for the contract application process
sequence numbers.

4.1.7 Settlement

4.1.7.1 General Settings

In this Customizing activity, you maintain settings for billing documents, which are generated with
reference to settlement documents depending on information such as company code, profit center,
taxation code, and so on.
The billing document types for the credit and debit memo request along with the document category is
maintained here.
It is mandatory to maintain this Customizing to ensure proper billing of the settlement documents.
Activities
To maintain general settings, proceed as follows:
1. Click New Entries.
2. Enter the required fields.
3. Save entries

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 62 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this activity some general company code dependent settlement settings can be made.
 CR Memo Request Type  Credit memo request type for standard settlement
that is used when settlement generates a credit memo request
 DR Memo Request Type  Debit memo request type for standard settlement
that is used when settlement generates a debit memo request
 Order reason  Order reason that is added to the DR/CR request type
 Rejection Reason CR/DR request type rejection reason which is used in case
a request is rejected prior to its billing
 CR Memo Item Cat.  item category which is used to create the credit memo
request for standard settlements
 DR Memo Item Cat.  item category which is used to create the debit memo
request for standard settlements
 Acc Doc for Pay Split  accounting document type which is used for payment
split postings
 Acc Object for Pay Split  account object document type which is used for
payment split postings
 I/C Post Reason Code  reason code for material ledger price change
document; used in Intra-company FI posting process
 NS CR Memo Request Type  Credit memo request type for non-standard
settlement that is used when settlement generates a credit memo request
 NS DR Memo Request Type  Debit memo request type for non-standard
settlement that is used when settlement generates a debit memo request
 NS CR Memo Item Cat.  item category which is used to create the credit memo
request for non-standard settlements
 NS DR Memo Item Cat  item category which is used to create the debit memo
request for non-standard settlements.
 GR IR Condition Type  identifies the GRIR condition type on an Intra-company
provisional valuation posting

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 63 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 SNB Condition  identifies the shipped not billed condition type on an Intra-
company provisional valuation posting
 Intracompany Postings  activate or deactivate special Intra-company posting
process

4.1.7.2 Settlement Group – Maintain Split Criteria

Use

In this Customizing activity, you maintain settlement group's split criteria. This Customizing ensures that
applications with different split criteria end up in different settlement groups and eventually in different invoices.

It is mandatory that all the fields for the split criteria are specified here for correct invoicing or billing of the
settlements.

This Customizing ensures that irrespective of several grouping criteria that match for the various applications,
they will move to various settlement groups depending on the field that is maintained in the Customizing.

Ensure that the field that is maintained in Customizing has different values in all the applications.

Activities

To maintain settlement group split criteria, proceed as follows:

1. Click New Entries.

2. Enter CoCd (Company Code) and Field Name.
3. Save entries.

4.1.7.3 Settlement Group – Maintain Number Range

Use

In this Customizing activity, you can define and maintain number range objects for settlement group. This
number range generates settlement group numbers when you save a settlement document.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 64 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

You can check the type of settlement group depending on the No. field. The number in this field indicates which
area the settlement group belongs to. For example, No. 01 is in sales area.

If you want the numbering of settlement groups to start at a point other than the starting number mentioned in
the From No. field, you must enter a valid value in the NR Status field depending on the From No. and To
Number range. The settlement group's numbering will begin at the number maintained in NR Status field. Each
time a settlement group is numbered according to the value in the NR Status, the number here is updated
automatically to the next higher number.

You select the To-year-flag checkbox when you reach the maximum limit for your number range in one line.
This adds a new year to the next line. You select this when you reach the maximum limit for your number range
in one line item. The new year will continue to have the same No. This helps you continue the number range for
same type of settlement group.

Requirements

You have defined the document types in table /ACCGO/T_DOCTYP.

Activities

To add a new year as a line item, proceed as follows:

1. Go to transaction SNRO.
2. Enter /ACCGO/STL in the Object field.
3. Choose the Change pushbutton.
4. Select the To-year-flag checkbox.
5. Save your entries

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 65 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.4 Agency Business Document - Determine ABD Type

Use

In this Customizing activity, you can configure the table ABD Type Determination. For a combination of different
settlement types, scenarios, side, and so on, you have to configure the different agency business document
types used in creating the agency business document (expense settlement, vendor billing document,
payment).It is is also used to determine the revenue recognition ABD.

Requirements

You have completed the ABD (Agency Business Document) configuration. You have checked whether the
value in ABD Type fields exist in the table TMFK. In the TMFK table, you can check the VTEXT field to know
the correct ABD type that you must maintain according to your scenario.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 66 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.5 Maintain Number Range for Settlement Documents

Use

In this Customizing activity, you define and maintain number range objects for settlement documents. This
number range generates settlement document numbers when you save a settlement document.

You can check the type of contract settlement document depending on the No. field. The number in this field
indicates the area in which the contract settlement document belongs. For example, 01 for sales settlements,
02 for purchase settlements, 03 for reversals, etc.

If you want the numbering of settlement groups to start at a point other than the starting number mentioned in
the From No. field, you must enter a valid value in the NR Status field depending on the From No. and To
Number. The contract settlement document's numbering begins at the number maintained in NR Status field.
Each time a contract settlement document is numbered according to the value in the NR Status field, the
number here is updated automatically to the next higher number.

In transaction SNRO, enter the object as /ACCGO/STL in the Object field. Choose the Change pushbutton and
select the To-year-flag checkbox and save your entries. You select the To-year-flag checkbox when you reach
the maximum limit for your number range in one line item. The new year that is added in the new line will use
the same number range for same type of settlement document.

Requirements

You have defined the document types in table /ACCGO/T_DOCTYP.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 67 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Activities

You can define and maintain the number range objects for settlement document in the following ways:

To view the settlement document number range entries, proceed as follows:

1. Choose the (display) Intervals pushbutton.

2. The Maintain Intervals: Settlement Document screen appears.

To edit the From No. field and To Number field, proceed as follows:

3. Choose the (edit) Intervals pushbutton.

4. The Maintain Intervals: Settlement Document screen appears.
5. Enter the required values.
6. Choose the External Assignment checkbox to specify whether it is an internal or external
assignment
7. Save the entries.

To edit the NR Status field, proceed as follows:

8. Choose the (edit) NR Status pushbutton.

9. The Maintain Intervals: Settlement Document screen appears.
10. Enter the required values.
11. Save the entries.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 68 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.6 Maintain Number Range for Lien

Use

In this Customizing activity, you can define and maintain number range objects for lien. For each lien
maintained in the master data, a new lien number is generated and assigned. You use this number range to
generate numbers when a new lien is maintained.

In the No. field, the value 01 creates a number range with internal number assignment and the value 02 creates
a number range with external number assignment. Note that when you enter the value 02, you must select the
Ext (External) radio button.

In transaction SNRO, enter the object as /ACCGO/STL in the Object field. Choose the Change pushbutton and
select the To-year-flag checkbox and save your entries. You select the To-year-flag checkbox when you reach
the maximum limit for your number range in one line item. The new year that is added in the new line will use
the same number range for same type of lien.

Activities

You can define and maintain the number range objects for lien in the following ways:

To view the lien number range entries, proceed as follows:

1. Choose the (display) Intervals pushbutton.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 69 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

2. The Maintain Intervals: Lien Number Range screen appears.

To edit the From No. field and To Number field, proceed as follows:

3. Choose the (edit) Intervals pushbutton.

4. The Maintain Intervals: Lien Number Range screen appears.
5. Enter the required values.
6. Choose the External Assignment checkbox to specify whether it is an internal or external
assignment
7. Save the entries.

To edit the NR Status field, proceed as follows:

8. Choose the (edit) NR Status pushbutton.

9. The Maintain Intervals: Lien Number Range screen appears.
10. Enter the required values.
11. Save the entries.

4.1.7.7 Maintain Number Range for Non-Standard Settlement Processes

Use

In this Customizing activity, you can define and maintain number range objects for non-standard settlement
documents like washouts, circles, and cancellations.

You can check the type of non-standard settlement documents depending on the No. field. The number in this
field indicates which area the non-standard settlement documents belong to.

You must enter a valid value in the NR Status field depending on the From No. and To Number. The non-
standard settlement document's numbering will begin at the number maintained in NR Status field. Each time a
non-standard settlement documents is numbered according to the value in the NR Status field, the number
here is automatically updated to the next higher number.

In transaction SNRO, enter the object as /ACCGO/STL in the Object field. Choose the Change pushbutton and
select the To-year-flag checkbox and save your entries. You select the To-year-flag checkbox when you reach

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 70 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

the maximum limit for your number range in one line item. The new year that is added in the new line will use
the same number range for same type of non-standard settlement documents.

Requirements

You have defined the document types in table /ACCGO/T_DOCTYP.

Activities

You can define and maintain the number range objects for lien in the following ways:

To view the lien number range entries, proceed as follows:

1. Choose the (display) Intervals pushbutton.

2. The Maintain Intervals: Wash String, Circle screen appears.

To edit the From No. field and To Number field, proceed as follows:

3. Choose the (edit) Intervals pushbutton.

4. The Maintain Intervals: Wash String, Circle screen appears.
5. Enter the required values.
6. Choose the External Assignment checkbox to specify whether it is an internal or external
assignment
7. Save the entries.

To edit the NR Status field, proceed as follows:

8. Choose the (edit) NR Status pushbutton.

9. The Maintain Intervals: Wash String, Circle screen appears.
10. Enter the required values.
11. Save the entries.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 71 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.8 Configure Number Range Intervals

Use

In this Customizing activity, you configure the number range intervals for various number ranges.

You configure number ranges for lien, non-standard washout settlement, and non-standard circle settlement.

Activities

1. Choose New Entries.

2. Enter the required details.
3. Save the entries.

4.1.7.9 Maintain Settlement Document Types

Use

In this Customizing activity, you maintain the different types of standard and non-standard settlement
documents.

Requirements

You have maintained the document types in the table /ACCGO/T_DOCTYP.

Activities

To enter a document type in the New Entries: Overview of Added Entries table, do the following:

1. Select New Entries.

2. Enter the document type.
3. Enter the settlement document type text.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 72 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4. Save the entry.

4.1.7.10 Determine Settlement Document Types

Use

In this Customizing activity, you assign settlement document types for standard or non-standard settlement
process. The settlement document type will be determined based on the configured criteria. You can configure
the allowed settlement document types like forward, reversal, return, and so on for the combination of contract
type, settlement type, and company code.

Requirements

You have maintained the document types in Customizing for Maintain Settlement Document Type.

Activities

To determine document types, proceed as follows:

1. Choose New Entries.

2. Enter the required details.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 73 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

3. Save the entry.

4.1.7.11 Configure Editable Fields on Settlement Document

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 74 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this Customizing activity, you can control the fields that are editable on the settlement document header for
each document category. Fields maintained here will be editable or non-editable based on the settings.

To view the document categories, see Document Category

Activities

To make a field editable, do the following:

1. Choose New Entries.

2. Enter Company Code, Doc. Category, and Field Name.
3. Select the Editable checkbox.
4. Save the entry.

4.1.7.12 Maintain Reason Codes for Price Override

Use

In this Customizing activity, you maintain reason codes for price override in settlement documents.

Once you enter a reason for cancellation in this Customizing, it will automatically be updated in the table
/ACCGO/T_STLRC.

Activities

To maintain a reason code, do the following:

1. Select New entries

2. Enter the reason for cancellation
3. Save entry

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 75 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.13 Maintain Reason Code and Reason Text for Settlement Status Activity

Use

In this Customizing activity, you maintain reason codes for reason types. Reason codes are used in settlement
documents for reason types such as correction, approval, reversal, adjustment, and transfer to FI. Reason
codes are defined by the user. They are represented by numbers and explained with a detailed text in the
Reason Text field.

The reason codes maintained in this Customizing are automatically updated in the table /ACCGO/T_STLRES.

This Customizing has the following header details:

1. Reason Ty. (Reason Type)

2. Rsn Code (Reason Code)
3. Reason Text

Requirements

You have defined the reason types in the domain /ACCGO/D_REASON_TYPE.

Activities

To maintain reason code and reason text for settlement status activity, proceed as follws:

4. Choose New Entries.

5. Enter the reason code and reason text.
6. Save entries.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 76 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.14 Configure GL/PO Posting Settings

Use

In this Customizing activity, you configure the GL/PO posting settings for condition types.

You can configure if a condition type value must be posted to GL Accounts or PO during Material Management
(MM) invoice creation.

Activities

To configure GL/PO posting settings, proceed as follows:

1. Choose New Entries.

2. Enter required details and set the required flag.
3. Save entry.
4. Note the following:

 If both GL and PO posting active flags are set to True, then the amount will be posted to GL Accounts.

 If PO active flag is set to True and GL active flag is not set, then the amount will be posted to PO.

 If GL active flag is set to True and PO active flag is not set, then the amount will be ignored.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 77 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.15 Maintain Central Lien Filling Notification

Use

In this Customizing activity, you configure the central lien filling and notification.

Lending institutions are required to file their liens in the county in which the commodity is located. This filing
flows to a central database for the entire state.

This Customizing activity is a table provided to update the information about the central filing lien notification. It
maintains the following information:

 Country

 Region

 Currency

 Dates (Start/End)

 Cancellation Fee

 A flag to signify if the lien is currently active or not

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 78 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Activities

To maintain central filling lien notification, proceed as follows:

1. Choose New Entries.

2. Enter the required details and choose the Active flag
3. Save entries.

4.1.7.16 Maintain Condition type for DPQS (Master Data)

Using the transaction code /ACCGO/V_MAPDPQS, you can map a Internal characteristics number to a
condition type.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 79 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.17 Mapping condition type for optionalities (Master Data)

Using the transaction code /ACCGO/CAS_STL_MAPOP, you can map a optionality category to a
condition type.
Example: discounts or premiums for a specific loading location can be mapped to the appropriate
condition type.
Several different optionalities can be mapped to the same condition type.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 80 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.1.7.18 Mapping Expenses Condition types for Settlement

Using the transaction code /ACCGO/CAS_STL_MAPEX, you can map Expense Pricing condition types
for settlement.

4.1.8 Revenue Recognition

4.1.8.1 Maintain Settlement Events for Revenue Recognition

Use

In this Customizing activity, you define the settlement events that are required to determine if an item is ready
for revenue recognition or purchase realization.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 81 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

If the revenue recognition registry has been enhanced with additional custom settlement events, configure the
related indicators and enable them here.

Standard settings

The following settlement event indicators are included in the standard solution and can be activated as
required:

Event Indicator Description Side Enable

FP_INDI Final Price M purchasing X

FP_INDI Final Price V Sales/Distribution X

GQ_INDI Final Quality M purchasing X

GQ_INDI Final Quality V Sales/Distribution X

GW_INDI Final Weight M purchasing X

GW_INDI Final Weight V Sales/Distribution X

PR_INDI Physical Receipt M purchasing X

TT_INDI Title Transfer M purchasing X

TT_INDI Title Transfer V Sales/Distribution X

Note that the Physical Receipt indicator is only relevant for purchase realization.

Activities

To maintain settlement events for revenue recognition, proceed as follows:

1. Choose New Entries.

2. Enter required details.
3. Save entry.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 82 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 83 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2 Scenario Specific Settings

4.2.1 Back-to-Back

4.2.1.1 Maintain Default Settings for Back-to-Back

Use

In this Customizing activity, you can define the pegging type used to create a TSW (The Trader's & Scheduler's
Workbench) nomination.

In SAP Agricultural Contract Management, you use the TSW location to create nomination and pegging type to
define the possible linking of purchase and sales areas.

Requirements

You have maintained standard TSW Location type and Pegging type in Customizing under Logistics Execution
> TSW > Master Data > Business Location Type > Define Business Location Type

and under Logistics Execution > TSW > Basic Functions > Pegging > Define Pegging Type respectively.

Activities

You use this configuration to maintain the following two items:

 Pegging type for linking back-to-back items to one another

 Location type for a TSW location which maps to a transport system

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 84 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.1.2 Map Nomination Mvmt. Scenario to Title Transfer Mvmt. Scenario

Use

In Load Data Capture, a load can be captured against different reference documents, including the nomination.
The nomination is the scheduling and communication document used in the Trader's and Scheduler's
Workbench (TSW). It is the basis for subsequent documents for each line item in the nomination.

In this Customizing activity, you can map a nomination movement scenario to a title transfer movement
scenario for a function group, correction function group, or reversal function group.

Activities

1. In the Mvmt. Scenario field, enter a movement scenario number.

2. In the Tit. Trans (Title Transfer) field, choose from the following values: Title Transfer at Origin, Title
Transfer in Transit, and Title Transfer at Destination.
3. In the Wgt Source (Governing Weight Source) field, choose from the possible values Origin or
Destination.
4. In the GrdsSource (Governing Grade Source) field, choose from the possible values Origin or
Destination.
5. Select a function group, correction function group, or reversal function group.
6. Save your entries.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 85 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 86 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.1.3 Maintain Default Settings for Nomination Peg type

Use

In this Customizing activity, you can define the pegging type and type of pegging to be used for TSW (The
Trader's & Scheduler's Workbench) nomination creation.

In SAP Agricultural Contract Management, pegging type can be defined for a specific nomination functionality.
For example BB is used for Back-to-Back scenario; DD is used for Diversion and so on.

Standard TSW pegging type is mapped to SAP Agricultural Contract Management specific business processes.

Activities

You use this configuration to maintain the following two items:

 Pegging type for linking back-to-back items to one another

 Pegging kind to identify specific business process

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 87 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.2 Intercompany, Intracompany

4.2.2.1 Incoterm / Title Transfer configuration
/ACCGO/V_INCOT: Determination of the title transfer based on Inco term.
If there is a requirement for multiple title transfers, then valuated SIT needs to be configured. For
further information, refer to the details in the following link:
http://help.sap.com/erp2005_ehp_05/helpdata/en/ee/045184edf24e15928397fc12b6296e/content.htm?fra
meset=/en/ee/045184edf24e15928397fc12b6296e/frameset.htm

4.2.2.2 SPED Output type Configuration for automatic issue

Uncheck the “No Output determination flag” for the Delivery Creation profile “2000” using the t-code
“VL10CUC”. This will ensure to issue the SPED or any other output type when the delivery is
created.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 88 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.2.3 VLPOD configuration

In the t-code OMJJ (Customizing: New Movement Types), set the transaction VL02N, VLPOD for the
movement types where the VLPOD is required

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 89 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

.
I

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 90 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.3 Comingled Settings

4.2.3.1 Maintain Storage Location for Negative Posting

Use

In this Customizing activity, you maintain negative storage locations for commingled stocks.

A commingled stock is accepted only for temporary storage while the title for the commodity quantity remains
with its supplier. To record such commodity movement, which will be followed by a purchase by the company
storing the commodity or by a retrieval to return to the supplier in a later point in time, a negative posting with
the relevant storage location information is necessary.

For each negative storage location, you need to specify a plant, a location ID and a storage location.

Requirements

 The movement types to be used for posting to the positive storage locations, such as MT 501, and to
the negative storage locations, such as MT 562, must have been already available.
Note that you can create these movement types freely as to your requirement.

 The plants and their respective storage locations for negative posting must have been defined prior to
this Customizing activity.
Note that you can only define one storage location per plant for negative postings or commingled
stocks.

Activities

To define a negative storage location, proceed as follows:

1. Click New Entries.

2. Define the following fields:

o Plant

o Location ID

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 91 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

o Storage Location

Example

You can set up as follows using this Customizing activity:

 The plant can be defined as the facility that is licensed to store the commingled commodities

 The location ID can be defined as the TSW location

 The storage location can be defined as the storage location to accept the negative stocks

4.2.3.2 Maintain Movement Types

Use

In this Customizing activity, you maintain commingled actions together with the corresponding storage
location movement types, both positive and negative.

In case of an unload of a commingled commodity, you need to maintain the goods movement types for posting
to both positive and negative storage locations.

Requirements

 The movement types to be used for posting to the positive storage locations, such as MT 501, and to
the negative storage locations, such as MT 562, must have been already available.
Note that you can create these movement types freely as to your requirement.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 92 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 The plants and their respective storage locations for negative posting must have been defined prior to
this Customizing activity.
Note that you can only define one storage location per plant for negative postings or commingled
stocks.

Activities

To define an action with the storage location movement types, proceed as follows:

1. Click New Entries.

2. Define the fields as follows:

o Action
Select either Unload Event or Load Event from the dropdown list.

o + StLoc MT (Positive Storage Location Movement Type)

Using the input help, select a movement type which should be assigned to the positive
storage location.

o - StLoc MT (Negative Storage Location Movement Type)

Using the input help, select a movement type which should be assigned to the negative
storage location.

4.2.3.3 Maintaining Program Types

The creation of storage program types is performed in the application area for ACM under transaction:
/ACCGO/STORAGE_TYPE - Maintain Storage Program Types. Please note that ACM does not perform
any calculations for storage fees.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 93 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.2.3.4 Maintain Default Storage Programs

For a material/TSW location, the allowed storage program types may be maintained. One can be set as
default to enable a program type to be automatically assigned during initial receipt of goods.
Please refer to customizing document on Business Rules Framework for further information on
configuration of this object.
4.2.3.5 Maintain ‘Storage Relevant’
On the material master (MM01/MM02/MM03), maintain the storage relevant indicator at the plant level.
4.2.3.6 Maintain Material at Negative SLoc
Ensure that the material is extended to the negative storage location (MM01/MM02/MM03).
4.2.3.7 ‘Negative Stock’ indicator
Ensure that on the material master for the obligation location, the indicator is set on the General/Plant tab.

4.3 Enhancements/BADIs
The following customizing shows areas where the delivered code can be enhanced by .

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 94 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 95 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.1 Archiving

4.3.1.1 Maintenance of Archiving objects for object /ACCGO/APS

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/ARC_APS. You can use the BAdIs of this enhancement spot to delete, add, and check tables for the
archiving object /ACCGO/APS.

4.3.1.1.1 BAdI: Deletion of Additional Data in Tables

Use

In this Business Add-In (BAdI), you can delete additional data in tables for the archiving object /ACCGO/APS
for application documents. You call this BAdI in write program /ACCGO/CMN_APS_DELETE of archiving
object /ACCGO/APS.

This BAdI contains the method DELETE- Delete Data. You implement this method to delete additional tables
from the database.

It contains the following parameters:

Importing Parameters Description

IM_HANDLE Index of Internal Tables

IM_TEST Test Run

Functionality

You implement this method in order to delete additional tables from the database.

Parameters

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 96 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

· I_HANDLE: This parameter imports the current run identification.

· I_TEST: This parameter imports the information on whether it is a test run.

Requirements

You have implemented the BAdI ARC_OBJECT_ADD_TABLE, which adds structures in archiving object
/ACCGO/APS. Enter the filter value as Archiving Object in this BAdI.

Standard settings

This BAdI is activated in the standard system.

Exception handling is done in the program if the BAdI is activated without first being modified?

The default code is not executed when there is no active customer implementation?

The BAdI is not filter-dependent.

This BAdI is reusable

See also

This BAdI is available in the enhancement spot /ACCGO/ARC_APS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.1.1.2 BAdI: Addition of Data in Tables

Use

In this Business Add-In (BAdI) you can archive additional data of tables for archiving object /ACCGO/APS for
application documents. This BADI is called in write program /ACCGO/CMN_APS_WRITE of Archiving object
/ACCGO/APS.

This BAdI contains the method WRITE- Write Data. You implement this method in order to read additional
tables from the database and to write them to the archive.

It contains the following parameters:

Importing Parameters Description

IM_HANDLE Index of Internal Tables

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 97 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

IM_APPDOC CA Application Document Header

Requirements

You have implemented the BAdI ARC_OBJECT_ADD_TABLE, which adds structures in archiving object
/ACCGO/APS. Enter the filter value as Archiving Object in this BAdI.

Standard settings

This BAdI is activated in the standard system.

Exception handling is done in the program if the BAdI is activated without first being modified?

The default code is not executed when there is no active customer implementation?

The BAdI is not filter-dependent.

This BAdI is reusable

See also

This BAdI is available in the enhancement spot /ACCGO/ARC_APS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.1.1.3 BAdI: Additional Checks

Use

In this Business Add-In (BAdI) you can add additional check for archiving object /ACCGO/APS for application
documents. This BADI is called in write program /ACCGO/CMN_APS_CHECK of archiving object
/ACCGO/APS.

This BAdI contains the method CHECK- Check Data. You can use this method to incorporate additional tests to
check if a document can be archived.

It contains the following parameters:

Importing Parameters Description

IM_APPDOC CA Application Document Header

CH_ERROR Error Flag

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 98 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

CH_EMSG Agency Business: Table with Messages

Requirements

You have first executed the program /ACCGO/CMN_APS_PREPROCESS and then program
/ACCGO/CMN_APS_WRITE in transaction SARA.

Standard settings

This BAdI is activated in the standard system.

Exception handling is done in the program if the BAdI is activated without first being modified?

The default code is not executed when there is no active customer implementation. All checking are there in
program except any customer dependent checks.

The BAdI is not filter-dependent.

This BAdI is reusable

See also

This BAdI is available in the enhancement spot /ACCGO/ARC_APS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.2 Copy Control

4.3.2.1 Enhancement for Copy Control

Use

The Business Add-In (BAdI) grouped under this structure node belongs to the enhancement spot
WB2_COPY_CONTROL. This BAdI provides mapping features when you create a trading contract by copying
another trading contract.

Requirements

You need to add the include /ACCGO/AGRI_WB2_COPY_CONTROL in the implementation of this BADI. This
will incorporate copy control feature of additional tabs. It copies the data of additional tabs in header level as

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 99 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

CSDP and Pre-Payment and for item level as Deferred/Pre-Payment, Cancellation, Tolerances, Related
Trades, Additional Contract Conditions and DPQS.

See also

The BAdI in this enhancement spot is Trading Contract: Copy Control.

4.3.3 Contract Management

4.3.3.1 Commodity Contracts

4.3.3.1.1 Master Data
4.3.3.1.1.1 Settings for Master Data Enhancement

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_ENHANCE_MASTER. You can use the BAdI of this enhancement spot for custom
enhancements to the following types of data:

 Discount Premium Quality Schedules (DPQS)

 Tolerance Schedules

 Related Trades

 Optionalities

 Cancellations

4.3.3.1.1.1.1 BAdI: Master Data Enhancement for DPQS, Tol., Optn., RelTrad

Use

This Business Add-In (BAdI) can be used for custom enhancements to the following types of data:

 Discount Premium Quality Schedules (DPQS)

 Tolerance Schedules

 Related Trades

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 100 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Optionalities

 Cancellations

This BAdI imports the enhanced structures from the third party trading system (3PT) and may be implemented
to map the enhanced fields from the message interface to the enhanced fields of the Create/Update utility
class. It has the following import and changing parameters:

Parameter Description Additional Information

Structure containing all the

enhanced nodes (DPQS,
Trading Order
IM_INPUT Tolerance, Related Trades,
Request
Optionalities, and Cancelation)
from the 3PT

DPQS Header
CH_DPQS_HD DPQS header data table
Details

DPQS Item
CHT_DPQS_IT DPQS item data table
Details

Tolerance
CH_TOLER_HD Tolerance header data table
Header

Tolerance
CHT_TOLER_IT Tolerance item data table
Item

Related
CHT_RELTRADE Related trades data table
Trades

Optionality
CHT_OPT_HDR Optionality header data table
Header

Optionality
CHT_OPT_ITEM Optionality item data table
Item

Cancellation
CHT_CNCL_CC Cancellation data table
Header

Cancellation
CHT_CNCL_PL Canceled pricing Lot data table
Pricing Lot

This BAdI is available in the enhancement spot

/ACCGO/CCK_ES_ENHANCE_MASTER and it has the
method INBOUND_PROCESSING.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 101 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.3.1.2 Validation Checks

4.3.3.1.2.1 Settings for Pre-Cancellation Checks

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_CNCL_CHECKS. You can use the BAdI of this enhancement spot to implement additional
pre-cancellation checks when a user cancels a trade.

4.3.3.1.2.1.1 BAdI: Pre-Cancellation Checks

Use

This Business Add-In (BAdI) is used to implement additional pre-cancellation checks when a user cancels a
trade. Prior to performing the cancellation, the system performs certain pre-cancellation checks to validate
whether cancellation is possible.

This BAdI is available in enhancement spot /ACCGO/CCK_ES_CNCL_CHECKS and it has the method
PERFORM_CHECKS.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancment Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.3.2 Pricing Aspects

4.3.3.2.1 Pricing Calculation

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_CAK. You can use the BAdI of this enhancement spot to calculate price.

4.3.3.2.1.1 BAdI: Price Calculation for Condition Type for a Pricing Asp

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 102 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Use

This Business Add-In (BAdI) is used to calculate the price based on the input components.

It consists of the method CALCULATE_PRICE. You can use this method to calculate the final price, based on
the input components.

Standard settings

The standard calculation calculates based on the following condition type categories of a condition:

 If the input components are assigned to Futures and Basis condition type categories, then the output
price is the sum of the Futures component and the Basis component.

 If the input components are assigned to Index and Basis condition type categories, then the output
price is the sum of the Index component and the Basis component.

 If the input components are assigned to Futures and Ratio condition type categories, then the output
price is the product of the Futures component and the Ratio component.

 If you prefer a different calculation method, you should implement this BAdI and insert your
calculations here.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the Enhancement Spot: /ACCGO/CMN_BADI_CAK_PRICING.

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.3.3 Customer Screens

4.3.3.3.1 Settings for Customer Subscreen for Tolerance

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_TOLR. You can use the BAdI of this enhancement spot to enable the addition of a new
customer screen to the Tolerance tab.

4.3.3.3.1.1.1 BAdI: Customer Subscreen for Tolerance

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 103 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Use

This Business Add-In (BAdI) is used in the Tolerance tab of the trading contract header. The purpose of this
BAdI is to enable the addition of a new customer screen to the Tolerance tab. It is called when the user
navigates to the Tolerance tab of the trading contract header.

The BAdI is a single-use BAdI and is available through enhancement spot /ACCGO/CMN_ES_TOLR.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

In the absence of any active BAdI implementations, the blank screen 1000 of the function group
/ACCGO/CMN_TC_ENCH is assigned to the customer subscreen area of the Tolerance tab.

Example

Example implementation /ACCGO/CMN_BI_TOLR_CUST illustrates the usage of this BAdI.

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.3.3.2 Settings for Customer Subscreen for Related Trades

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_RELTD. You can use the BAdI of this enhancement spot to to enable the addition of a new
customer screen to the Related Trade tab page

4.3.3.3.2.1.1 BAdI: Customer Subscreen for Related Trades

Use

This Business Add-In (BAdI) is used in the Related Trade tab page of the trading contract header. The purpose
of this BAdI is to enable the addition of a new customer screen to the Related Trade tab page. It is called when
the user navigates to the Related Trade tab page of the trading contract header.

The BAdI is a single-use BAdI and is available in the enhancement spot /ACCGO/CCK_ES_RELTD. It contains
the method SET_SCREEN_AND_PROG.

Standard settings

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 104 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.4 Expense Management

4.3.4.1 Invoice Router

4.3.4.1.1 BAdI: Determine Transaction to be Called

Use

This Business Add-In (BAdI) is used in the Expense Management component. You use this BAdI to call a user-
defined transaction for expense settlement using the invoice router. By default, the invoice router routes to the
Settlement with GTM option where VBDs or TCs can be settled against an invoice. If you settle the invoice
using a different transaction (for example, MIRO), based on input parameters on the Invoice Router selection
screen, then this BAdI is implemented and the required transaction is called inside the BAdI interface method.
This BAdI is available in the /ACCGO/EXM_ES_INVOICE_ROUTER enhancement spot.

You can implement the SETTLE_INVOICE method in the /ACCGO/IF_EXM_INVOICE_ROUTER interface to

import all input data that the user enters on the Invoice Router selection screen. Based on the input, the system
determines the appropriate transaction to settle the invoice. If the system calls any user-defined transaction
within the BAdI implementation, then the value of the CH_TRANSACTION_CALLED changing parameter is set
to 'X'. This indicates that the user-defined transaction has been called, which prevents the invoice router from
calling the default GTM settlement screen.

The system can perform validations inside the method for the user inputs on the Invoice Router selection
screen. In the case of any errors, the /ACCGO/CX_EXM_INV_ROUTER exception type is raised and the error
message displayed is populated in the EX_RETURN return table.

The following are the importing parameters used in this BAdI:

 IM_INV_PARAMS: Invoice Router: Selection Screen Parameters

This parameter is structured and contains the following invoice related fields entered by user on the Invoice
Router selection screen.

o Reference

o Invoice Date

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 105 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

o Vendor

 IM_ROUTER_FIELDS: Invoice Router: Selection Screen Search Fields

This parameter will have all search fields on the selection screen. If the search field is of select option type
(range) then corresponding range table will have the required value. The following fields on the Invoice Router
selection screen are contained in this parameter:

o Trading Contract

o External Reference Number

o VBD Creation Date

o Logistics Document Type

o Logistics Document

o Company Code

o Purch. Organization

o Plant

o Service Entry Sheet

o TSW Location ID

 IM_SETTLE_OPTION: Settlement Option

This parameter is the settlement option checkbox on the Invoice Router selection screen. You can only select
one settlement option. The settlement option can have different values based on the settlement option you
select. The following are the settlement option values:

o If 'Settle with GTM' option is selected, then IM_SETTLE_OPTION = 'G'

o If 'Settle with MIRO' option is selected, then IM_SETTLE_OPTION = 'M'

o If 'Settle with FI' option is selected, then IM_SETTLE_OPTION = 'F'

 CH_RETURN: Return Parameter Table

This parameter is the return table containing messages. If a message needs to be displayed on the screen or
logged to the application log, then this table must be filled. In the case that an error message must be displayed
to the user, the /ACCGO/CX_EXM_INV_ROUTER exception type is raised and this return table is populated
with the error message.

 CH_TRANSACTION_CALLED: Flag to Take Decision to Call GTM Settlement Option

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 106 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

If you call any user-defined transaction within the BAdI implementation, then the value of the
CH_TRANSACTION_CALLED changing parameter is set to 'X'. This indicates that user-defined transaction
has been called and the GTM settlement screen should not be called.

If the settlement is done using GTM, then the CH_TRANSACTION_CALLED changing parameter is set to
‘initial’.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the

Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in enhancement spot /ACCGO/EXM_ES_INVOICE_ROUTER.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework .

4.3.5 Inventory True-up

4.3.5.1 Maintenance of Stock

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/INV_ES_CAL_UNRES. You can use the BAdIs of this enhancement spot to calculate the unrestricted
quantity of stock.

4.3.5.1.1 BAdI: Calculate Unrestricted Quantity of Stock

Use

This Business Add-In (BAdI) is used in the Inventory Management component. You can use this BAdI to
implement the READ_UNRESTRICTED_STOCK method which allows you to calculate the unrestricted
quantity of stock. This BAdI method is called from the /ACCGO/CL_INV_TRUE_UP_DB-READ_DATA class.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

More Information

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 107 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View ->Application Server
-> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development ->
Enhancement Framework.

4.3.5.2 Maintenance of True-up Amount

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/INV_ES_CALCULATE_QTY. You can use the BAdIs of this enhancement spot to calculate the total
true-up amount.

4.3.5.2.1 BAdI: Calculate Total True-Up Amount

Use

This Business Add-In (BAdI) is used in the Inventory Management component. You can use this BAdI to
implement the CALCULATE_DATA method which allows you to calculate the total true-up amount. This BAdI
method is called from the /ACCGO/CL_INV_TRUE_UP_BL-PREPARE_CCAK_DATA class.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BadI Builder (transaction SE18).

More Information

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help . In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.5.3 Cross Referencing Storage Locations

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/INV_ES_SLOC_MAP. You can use the BAdIs of this enhancement spot to cross reference your
plant/storage locations with third party storage locations.

4.3.5.3.1 BAdI: Cross Reference ECC Storage Location with 3PT Storage

Use

This Business Add-In (BAdI) is used in the Inventory Management component. You can use this BAdI to
implement the READ_3PT_LVL_BY_PLANT_LGRT_PRC method which allows you to cross reference the

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 108 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

ECC plant/storage location with the third party storage location. This BAdI method is called from the
/ACCGO/CL_INV_PO_BL-CALCULATE_PO_DET class.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

More Information

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help . In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.6 Master Data

4.3.6.1 Tolerance
4.3.6.1.1 Settings for Tolerance Master Data

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_VALIDT_TOLR_MAST. You can use the BAdI of this enhancement spot to add validation
logic for tolerance master data.

4.3.6.1.1.1 BAdI: Validate Tolerance Master Data

Use

This Business Add-In (BAdI) is used to add additional logic during the creation or change of tolerance master
data. It includes the method VALIDATE_TOLERANCE_MASTER_DATA, which can be used to add additional
validation logic. This method is called when tolerance master data is saved.

This BAdI is a single-use BAdI and is available in enhancement spot

/ACCGO/CCK_ES_VALIDT_TOLR_MAST.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 109 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.6.2 DPQS

4.3.6.2.1 Settings for calculation of Average Characterisitics Values

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_CALCULATE_AVG. You can use the BAdI of this enhancement spot to enable the
calculation of the average value of a characteristic in an application group.

4.3.6.2.1.1 BAdI: Calculate Average Characteristics

Use

This Business Add-In (BAdI) is used to enable the calculation of the average value of a characteristic in an
application group. This is a filter dependent BAdI under the Enhancement Spot
/ACCGO/CCK_ES_CALCULATE_AVG. The filter is AVG_METHOD (Averaging Method), and the possible
values can be selected by pressing F4.

This BAdI has the method CALCULATE_AVERAGE (calculate average characteristic value).

The implementation for filter value W ( Weighted Average ) is already provided. For more information on how to
implement this method for other implementations, refer to the method implementation of the method
CALCULATE_AVERAGE.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.6.2.2 Settings for Generation of Adjustment Text

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 110 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_MASTER_DATA. You can use the BAdI of this enhancement spot to overwrite the
adjustment text generated by the system.

4.3.6.2.2.1 BAdI: Generate Adjustment Text

Use

This Business Add-In (BAdI) is used to overwrite the adjustment text that is generated by the system and then
used for Discount Premium Quality Schedule (DPQS) master data and the settlement document.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_MASTER_DATA and it has the method
GENERATE_ADJUSTMENT_TEXT.

Requirements

This is a filter dependent BAdI, and the implementation is based on the value of the rate type. Rate type has
the following possible values:

Value Description

1 Per Unit

2 Multiplier

3 Percentage of Contract Price

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enh. Spot Element
Definitions tab in the BAdI Builder (transaction SE18).

Example

An example of a system generated adjustment text is: 0.01 USD/BU Premium each 0.5% increment.

This BAdI could be implemented to change the adjustment text generated by the system to: 0.01 USD/BU
Premium each 0.5% increment (valid only for corns of Grade A).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 111 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.6.2.3 Settings for Material Class

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_GET_MATNR_CLASS. You can use the BAdI of this enhancement spot to identify a single
material class for a material.

4.3.6.2.3.1 BAdI: Get Material Class

Use

This Business Add-In (BAdI) is used to identify a single material class for a material. This BAdI should be
implemented to identify a single material class for a material that is associated with multiple material classes.
This BAdI contains the method GET_MATERIAL_CLASS.

This BAdI is available in enhancement spot /ACCGO/CCK_ES_GET_MATNR_CLASS.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancment Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.7 Optionality

4.3.7.1 Default Optionality

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CCK_ES_DEF_CALLOFF. You can use the BAdI of this enhancement spot to set default optionality
values.

4.3.7.1.1 BAdI: Maintain Default Optionality Values at Call-Off

Use

This Business Add-In (BAdI) is used in the SAP Agricultural Contract Management (SAP ACM) component.
You can use this BAdI to enrich the existing business logic (BL) call-off in sales and purchase order. This BAdI
is called from /ACCGO/CAS_CALLOFF_UI.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 112 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

This BAdI has the following methods to extend the current solution to adopt the additional customer-specific
software requirements within Call-Off processing:

 GET_OPTIONALITY_DATA_SO (Screen 2020)

For more information, see Method for SO Optionality Data.

 GET_OPTIONALITY_DATA_PO (Screen 2050)

For more information, see Method for PO Optionality Data.

 GET_OPTIONALITY_DATA_UIS

For more information, see Method for UIS Optionality Data.

Standard settings

This is a multiple use BAdI. All the active implementations are called and executed.

It is not filter-dependent.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the Enhancement Spot: /ACCGO/CCK_ES_DEF_CALLOFF.

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.7.1.2 BAdI: Maintain Default Optionality in Trading Contract

Use

This Business Add-In (BAdI) is used in the SAP Agricultural Contract Management (SAP ACM) component.
You can use this BAdI to enrich the existing business logic (BL) of optionality in the trading contract application.
This BAdI is available in the Enhancement Spot: /ACCGO/CCK_ES_CUSTOM_OPTNLTY.

This BAdI contains the following methods:

 MAINTAIN_DEFAULT_OPTIONALITY

For more information, see Maintain Default Optionality on Trading Contract.

 MAINTAIN_OPTIONALITY_3PT

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 113 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information, see Maintain Optionality 3PT.

Standard settings

The default implementation is designed to default the values for Load Location, Discharge Location, Crop
season, Mode of transport, and Means of transport in the Optionality Table.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.7.2 Custom Optionality

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot:
/ACCGO/CCK_ES_CUSTOM_OPTNLTY. You can use the BAdIs of this enhancement spot to set custom
optionality values.

4.3.7.2.1 BAdI: Customer Subscreen for Custom Optionality

Use

This Business Add-In (BAdI) is used in the SAP Agricultural Contract Management (SAP ACM) component.
You use this BAdI to enrich the existing business logic (BL) of Optionality in the purchase order/sales order,
contract application, and load data capture.

This BAdI has the following methods to extend the solution to adopt the additional customer-specific
requirements within the trading contract processing:

 PUT_DATA_TO_SCREEN

 GET_DATA_FROM_SCREEN

 VALIDATE_DATA

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 114 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Standard settings

This BAdI is filter-dependent with document type as the filter.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the Enhancement Spot: /ACCGO/CCK_ES_CUSTOM_OPTNLTY.

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.7.2.2 BAdI: Optionality Checks and Calculations at Call-Off and Se

Use

This Business Add-In (BAdI) is used in the SAP Agricultural Contract Management (SAP ACM) component.
You use this BAdI to enrich the existing business logic (BL) call-off in sales order, purchase order, application,
and settlement. This allows you to add additional validations and calculations in the areas mentioned above.

This BAdI has the following methods to extend the current solution to adopt the additional customer-specific
software requirements within call-off, application and settlement processing:

 VALIDATE_OPTIONALITY

 VALIDATE_AGAINST_CALL_OFF

 CHANGE_OPTIONALITY_ADJUSTMENT

Standard settings

This is a multiple use BAdI. All the active implementations are called and executed.

It is not filter-dependent.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 115 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

See also

This BAdI is available in the Enhancement Spot: /ACCGO/CCK_ES_OPTNLTY_ENH.

For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.8 Load Data Capture

4.3.8.1 Load Data Capture

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_UIS. You can use the BAdIs of this enhancement spot to manage the use of customer-
defined fields for Load Data Capture (LDC) events.

4.3.8.1.1 BAdI: Process User-Defined Add-On Tabs for LDC Screens

Use

This Business Add-In (BAdI) is used in the Load Data Capture (LDC) component (LO-AGR-LDC). You can use
this BAdI to add tabs to the Create and Change screens in the Load Data Capture Work Center. This BAdI is
called when the screen in question is being created, during processing and before output event.

This BAdI contains the following methods:

 RESET_INACTIVE_TABS_CHG

You can use this Business Add-In (BAdI) method to select and remove an available tab fcode for the
LDC Change screen from the list.

 RESET_INACTIVE_TABS_CRE

You can use this Business Add-In (BAdI) method to select and remove an available tab fcode for the
LDC Create screen from the list.

 CHANGE_TAXI_CAPTIONS_CHG

You can use this Business Add-In (BAdI) method to define the title to be displayed at the LDC Change
screen, based on the fcode selected through the RESET_INACTIVE_TABS_CHG method.

 CHANGE_TAXI_CAPTIONS_CRE

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 116 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

You can use this Business Add-In (BAdI) method to define the title to be displayed at the LDC Create
screen, based on the fcode selected through the RESET_INACTIVE_TABS_CRE method.

 SET_DATA_CHG

You can use this Business Add-In (BAdI) method to provide the program name and screen number to
be displayed at the LDC Change screen for the selected fcode.

 SET_DATA_CRE

You can use this Business Add-In (BAdI) method to provide the program name and screen number to
be displayed at the LDC Create screen for the selected fcode.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the enhancement spot /ACCGO/ARC_APS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.8.1.2 BAdI: Process User-Defined Fields for LDC Event Business Logic

Use

This Business Add-In (BAdI) is used in the Load Data Capture (LDC) component (LO-AGR-LDC). You can use
this BAdI to validate custom fields or to change LDC event data before saving. This BAdI is intended to allow
extensions of LDC events to work within the same validation and persistence flow as core LDC fields. It should
be used together with the Process User Defined Add-On Tabs for LDC Screens BAdI and the Process User
Defined Fields for LDC Event UI Layer BAdI.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

More Information

This BAdI is available in the enhancement spot /ACCGO/CMN/ES_UIS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 117 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.8.1.3 BAdI: Process User-Defined Fields for LDC Event UI Layer

Use

This Business Add-In (BAdI) is used in the Load Data Capture component (LO-AGR-LDC). You can use this
BAdI to map custom field event data from business logic structures to user interface structures, and from user
input to business logic.

This BAdI contains the following methods:

 DISPLAY_EVNT_DATA

You can use this method to change the fields to be displayed in the LDC event ALV.

 MAP_EVNT_DATA

You can use this method to change the values of the fields displayed in the LDC event ALV.

 MAP_EVNT_DATA_UI_TO_BL

You can use this method to transfer data from the event ALV to the business logic layer, for data
validation and persistence.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

More Information

This BAdI belongs to the enhancement spot /ACCGO/CMN/ES_UIS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.8.2 Orchestration Framework

4.3.8.2.1 BAdI: Batch Management Handling

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 118 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Use

This Business Add-In (BAdI) is used in the CD Trading Solution component. You can use this BAdI to enhance
customer-specific processing logic and checks in CD Trading Solution.

This BAdI is used to enable customer specific logic for propagating batch in subsequent logistical documents.

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.8.2.2 BAdI: Movement Type Posting during SIT

Use

This Business Add-In (BAdI) is used in the Load Data Capture (LDC) component (LO-AGR-LDC). You can use
this BAdI to enhance customer-specific processing logic and checks in SAP Agricultural Contract Management.

This BAdI enables the sending of customer-specific logic during SIT (Stock in Transit). With this BAdI, the
movement type for the goods movement postings can be passed to the system to facilitate the creation of
logistical documents..

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.9 SIT Cockpit

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_SIT_CCKPT_ENH_UI. You can use the BAdI of this enhancement spot to enhance or hide
the ALV view for SIT Cockpit UI.

4.3.9.1.1 Maintenance of SIT Cockpit UI

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 119 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.9.1.1.1 BAdI: Enhancement of ALV View for SIT Cockpit

Use

This Business Add-In (BAdI) is used in the Custom Development (CD) Trading Solution component. You can
use this BAdI to enhance customer-specific processing logic and checks in CD Trading Solution.

This BAdI contains the following methods:

 CHANGE_FIELDCATALOGUE

 GET_PLANT_FROM_PROFIT_CENTER

 GET_PROFIT_CENTER_FROM_PLANT

 FILL_NEW_VALUES_MAIN_DISPLAY

 FILL_NEW_VALUES_HU_HDR_DISPLAY

 FILL_NEW_VALUES_HU_ITM_DISPLAY

 FILL_NEW_VALUES_DPQS_DISPLAY

 FILL_NEW_VALUES_CHAR_DISPLAY

See also

This is a single-use BAdI and is available in enhancement spot /ACCGO/CMN_ES_SIT_CCKPT_ENH_UI.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.10 Contract Application

4.3.10.1 Call-Off

4.3.10.1.1 Maintenance of Call-Off

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_CAS_CALL_OFF. You can use the BAdI of this enhancement spot to make specific
settings for call-offs.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 120 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.10.1.1.1 BAdI: Call-Off UI Layer

Use

This Business Add-In (BAdI) is used to add or change UI display during call-off from Sales Order/Purchase
Order.

This BAdI contains the following methods:

 CHANGE_SCHEDULE_TEXT_SO

For more information, see Change Schedule Text for Call-Off UI: Sales side

 CHANGE_SCHEDULE_TEXT_PO

For more information, see Change Schedule Text for Call-Off UI: Purchase side

 CHANGE_PROPOSED_CO_FCAT

For more information, see Change Proposed Call-Off Field Catalog

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_CALL_OFF.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.1.1.2 BAdI: Call-Off BL Layer

Use

This Business Add-In (BAdI) is used to change call-off BL layer fields such as implicit optionalities during call-
off for Sales Order/Purchase Order.

This BAdI contains the following methods:

 CHANGE_IMPLICIT_OPT_SO

For more information see, Changing Implicit Optionalities for SO

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 121 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 CHANGE_IMPLICIT_OPT_PO

For more information see, Changing Implicit Optionalities for PO

 COPY_CONTRACT_TO_SO

For more information see, Copy Contract Data to SO Item if New Call-Off Exists

 COPY_CONTRACT_TO_PO

For more information see, Copy Contract Data to PO Item if New Call-Off Exists

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_CALL_OFF.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.1.2 Settings During Rule Evaluation

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot:
/ACCGO/CMN_ES_CAS_APPL_PROCESS. You can use the BAdI of this enhancement spot to process the
input and result after the evaluation of rules.

4.3.10.1.2.1 BAdI: Contract Application Business Rules

Use

This BADI is used to change the inputs to the BRF+ function prior to execution.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS and it has the
method PRE_RULES_EVALN.

Standard settings

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 122 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2 Application Document

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_CAS_APPL_DOC. You can use the BAdI of this enhancement spot for application
document process, including commingled process.

4.3.10.2.1 BAdI: Average Calculation for Characteristics

Use

You can use this Business Add-In (BAdI) to define your own way of calculating the average for a characteristic
in an application group.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS and it has the
method CALCULATE_AVERAGE.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Example

An application group contains the following two applications documents:

Application Document 1: 100 lb., Moisture 1%

Application Document 2: 200 lb., Moisture 2%

The BAdI is configured such that the weighted average of moisture in the application group = 1% * 100 LB +
2% * 200 LB / (100 LB + 200 LB ).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 123 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

See also

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2.2 BAdI: Group Application Documents

Use

You can use this BAdI to enhance customer-specific processing logic and checks.

You can use this BAdI to implement customer specific checks during the grouping of Application Documents.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_DOC.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

After calling up the Customizing activity, a dialog box displays, in which you can enter a name for the
implementation.

If you have already made other implementations for this BAdI, another dialog box displays, which contains the
existing implementations. In this case, choose Create, and proceed as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

The screen for creating BAdI implementations is now displayed.

2. Enter a short text for the implementation in the Short text for implementation field.

3. From the tab index, choose Interface.

The Name of implemented class field is already filled on the tab page, as a class name was automatically
assigned to the implementation when you named it.

4. Save your entries, and assign the implementation to a development class.

5. Place the cursor on the method, and double-click to enter method processing.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 124 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of
method> and end method.

7. Save and implement your code. Return to the Edit Implementation screen.

8. Save the entries on the Edit Implementation screen.

Note: You can also create an implementation, and then activate it at a later time. In such a case, end the
processing stage at this point.

9. Choose Activate.

The code you stored in the method will be run when the application program is executed.

See also

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2.3 BAdI: Application Document Business Layer

Use

You can use this BAdI to enhance customer-specific processing logic and checks.

This BAdI facilitates the implementation of customer-specific checks in the business layer of an Application
Document.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_DOC.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

In the Customizing activity, a dialog box displays, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box displays, which contains the
existing implementations. In this case, click Create, and proceed as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and click Create.

The screen for creating BAdI implementations displays.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 125 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

2. Enter a short text for the implementation in the Short text for implementation field.

3. From the tab index, click Interface.

The Name of implemented class field is already filled on the tab page because a class name was automatically
assigned to the implementation when you named it.

4. Save your entries and assign the implementation to a development class.

5. Place the cursor on the method and double-click to begin method processing.

6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of
method> and end method.

7. Save and implement your code. Return to the Edit Implementation screen.

8. Save the entries on the Edit Implementation screen.

Note: You can also create an implementation and then activate it at a later time. In such a case, end the
processing stage at this point.

9. Choose Activate.

The code you stored in the method will be run when the application program is executed.

See also

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2.4 BAdI: Application Document Data Collection Process

Use

You can use this BAdI to enhance customer-specific processing logic and checks.

The BAdI enables the customer-specific processing of the Data Collection process for creating the Application
Document.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_DOC.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 126 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing
implementations are displayed. In this case, choose Create, and proceed as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

The screen for creating BAdI implementations is now displayed.

2. Enter a short text for the implementation in the Short text for implementation field.

3. From the tab index, choose Interface.

The Name of implemented class field is already filled on the tab page, as a class name was automatically
assigned to the implementation when you named it.

4. Save your entries, and assign the implementation to a development class.

5. Place the cursor on the method, and double-click to enter method processing.

6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of
method> and end method.

7. Save and implement your code. Return to the Edit Implementation screen.

8. Save the entries on the Edit Implementation screen.

Note: You can also create an implementation, and then activate it at a later time. In such a case, end the
processing stage at this point.

9. Choose Activate

The code you stored in the method will be run when the application program is executed

See also

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2.5 BAdI: Application Document UI Layer

Use

You can use this BAdI to enhance customer-specific processing logic and checks.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 127 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

This BAdI enables the addition of customer specific sub-screens in the Application Document.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_DOC.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

After calling up the IMG activity, a dialog box displays, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box displays, which contains the
existing implementations.. In this case, choose Create, and proceed as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and click Create.

The screen for creating BAdI implementations displays.

2. Enter a short text for the implementation in the Short text for implementation field.

3. From the tab index, choose Interface.

The Name of implemented class field is already filled on the tab page, as a class name was automatically
assigned to the implementation when you named it.

4. Save your entries and assign the implementation to a development class.

5. Place the cursor on the method, and double-click to enter method processing.

6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of
method> and end method.

7. Save and implement your code. Return to the Edit Implementation screen.

8. Save the entries on the Edit Implementation screen.

Note: You can also create an implementation, and then activate it at a later time. In such a case, end the
processing stage at this point.

9. Choose Activate.

The code you stored in the method will be run when the application program is executed.

See also

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 128 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.2.6 BAdI: Commingled Process

Use

This Business Add-In (BAdI) is used for validations during the commingled process, such as assigning a
program, moving to unapplied and so on. This BAdI belongs to the Enhancement Spot
/ACCGO/CMN_ES_CAS_APPL_DOC.

This BAdI has the method VALIDATE (Validate Assign to Storage Program).

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a relevant release
and then Function-Oriented View under Application Help. In SAP Library, choose SAP NetWeaver Library:
Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS
ABAP -> ABAP Customer Development -> Enhancement Framework.

4.3.10.3 Application Process

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_CAS_APPL_PROCESS. You can use the BAdIs of this enhancement spot to make specific
settings for the application process.

4.3.10.3.1 BAdI: Returns Process for Contract Application

Use

This Business Add-In (BAdI) is used in the CD Trading Solution component. You can use this BAdI to enhance
customer-specific processing logic and checks in CD Trading Solution.

You can use this BAdI to implement customer-specific checks and logic in the returns application process.

Standard settings

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 129 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element
Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI belongs to the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.10.3.2 BAdI: DPQS Evaluation

Use

This Business Add-In (BAdI) is used in the CD Trading Solution component. You can use this BAdI to enhance
customer-specific processing logic and checks in CD Trading Solution.

This BAdI enables the customer specific checks during the DPQS evaluation. This option is available within the
contract application process.

See also

This BAdI belongs to the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.10.3.3 BAdI: Application Rules Evaluation

Use

This BADI is used to change the inputs to the BRF+ function prior to execution.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS and it has the
method PRE_RULES_EVALN.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 130 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.3.4 BAdI: Application Process Save

Use

This Business Add-In (BAdI) is used after the systerm has saved the application document and the application
process has taken place.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS and it has the
method SAVE_APPL_PROCESS.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement. Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

See also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.3.5 BAdI: Pricing TC Validation Framework

Use

This Business Add-In (BAdI) is used to default the PTC checks during Call-off validation. It can also be used to
change source fields of the order that are used for validation against the contract.

Standard settings

The BAdI is not filter-dependent.

The BAdI is designed for multiple usage. All activated implementations are accessed and executed.

Activities

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 131 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Information about the implementation of BAdIs in the context of the enhancement concept is available in the
SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

4.3.10.3.6 BAdI: Read Weights and Analysis Details

Use

This Business Add-In (BAdI) is used to enable the retrieval of data from the Q-repository. You can make
changes to the weights and grades as necessary using this BAdI.

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enh. Spot Element
Definitions tab in the BAdI Builder (transaction SE18).

See Also

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development
-> Enhancement Framework.

4.3.10.3.7 BAdI: Calculate Derived Characteristics

Use

This BAdI is a part of the CD trading solution. This can be used for calculating the value of a derived
characteristic based on the values of its constituent basic characteristics. This BAdI contains a method
CALCULATE_CHARACTERISTIC_VALUE.

This is a filter dependent BAdI with a single character-type filter: CALC_RULE (Calculation Rule). Hence there
will be a different implementation for each different Calculation Rule value.

The calculation rules are maintained through customizing. The available calculation rule values (coming from
customizing table /CASTP/T_CALC_RL) are as follows:

 A : Addition

 OCN : Oil Content Normalized

 MAP : Moisture Admixture Premium

 OCP : Oil Content Premium

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 132 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 NRM : Normalization

See also

This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.10.3.8 BAdI: DPQS Material Schedule

Use

This BAdI is a part of the CD trading solution This contains the method GET_MATERIAL_SCHEDULE which is
used to fetching the list of materials based on the input generic material and set of characteristic values.

This is a multiple use BAdI and is currently being called from the following places:

 From the CSL

To get the update material schedule, whenever characteristics are overridden on 3PT side.

 From the DPQS schedule maintenance

To fetch the list of materials to be shown on the Material Schedule tab page.

See also

This BAdI is under the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.10.3.9 BAdI: Material Determination

Use

This Business Add-In (BAdI) provides exit points to be used during the material determination process. This is
a multiple use BAdI that contains the following methods:

 GET_UNIQUE_MAT_CLASS: gets the unique material class for the material

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 133 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 GET_MAT_DET_CHARS: gets the material determining characteristics

 GET_BEST_FIT_MAT_GRADE: gets the unique best fit material and its grade

These methods are called from the material determination functionality.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element
Definitions tab in the BAdI Builder (transaction SE18).

See also

This BAdI is under the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.11 Contract Settlement

4.3.11.1 Enhancement for Settlement

Notes on Implementation

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_CAS_STL_DOC. You can use the BAdI of this enhancement spot to make specific settings
for settlement.

4.3.11.1.1 BAdI: Contract Settlement

Use

You use this Business Add-In (BAdI) to enhance customer-specific fields and checks in contract settlement.

This BAdI consist of the following methods:

 GET_PAYMENT_METHOD - Determines the Payment Method

 GET_TRANSLATION_DATE- Determines the Translation Date While Creating ABD

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 134 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 GET_PREPAYMENT_FI_DOCS- Get Pre-Payment FI Documents

 CHECK_BEFORE_SAVE- Check Before Save

 AFTER_SAVE- After Save

 CHECK_VENDOR_INVOICE_STATUS- Check if the Vendor has Non Self-Billed Invoice Status

 GET_ALT_PAYMENT_DATA- Determine the Alternate Payment Data

 CHECK_BEFORE_RELEASE - Validations Before Release of a Settlement Group

 CHECK_BEFORE_APPROVE - Validations Before Approval of a Settlement Group

 AFTER_APPROVE - Validations After Approval of a Settlement Group

 GET_VENDOR_INVOICE_DATA- Get the Vendor Invoice Data

 GET_SETTLEMENT_DATE- Get Settlement Date

 CONVERT_CURRENCY- Convert Currency

 GET_SETTLEMENT_VALUES- Get Settlement Values

 PREPARE_GROUP_DATA- Prepare Group Data

 CREATE_PURCHASE_INVOICE- Create Purchase Invoice

 CREATE_INVOICE_WO_PO- Create Invoice PO

 ON_REVERSE- For Reverse

 GET_SALES_DOC_TYPE- Get Sales Document Type

 ENABLE_TAX_FIELDS- Enable Tax Payer and Material Usage Fields

 GET_SETTLEMENT_CURRENCY- Update the Document Currency on Settlement

 UPDATE_SALES_CR_DB_MEMO_REQ- Update Debit/Credit Memo

See also

This is a single-use BAdI and is available in enhancement spot: /ACCGO/CMN_ES_CAS_STL_DOC.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 135 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

4.3.11.2 Maintenance of Additional Fields for Revenue Recognition

Notes on Implementation

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CAS_ES_REVREC. You can use the BAdI of this enhancement spot to make specific settings for
revenue recognition.

4.3.11.2.1.1 BAdI: Additional Fields for Event Registry

Use

This Business Add-In (BAdI) is used in the event registry monitor and processor transactions.

You use this BAdI to capture additional fields in the event registry table and to display them on the event
registry monitor and processor .

It consists of the following methods:

 UPDATE_BEFORE_SAVE_BL

For more information see, Update Before Save

 RETRIEVE_EVTREG_BL

For more information see, Retrieve Additional Fields of Event Registry

 UPDATE_FOR_TRADE_REALIZATION

For more information see, Change ALV Data

Requirements

You have added the additional fields to the respective table and structure.

See also

This is a single-use BAdI and is available in enhancement spot: /ACCGO/CAS_ES_REVREC.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP
NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then
Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application
Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer ->
Development -> Enhancement Framework.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 136 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.3.12 Enterprise Services

4.3.12.1 Goods Movement

Notes on Implementation

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_GOODS_MOVEMENT. You can use the BAdI of this enhancement spot to make specific
settings for goods movement.

4.3.12.1.1 BAdI: Goods Movement Call

Use

This Business Add-In (BAdI) is used to modify the inbound and outbound data for the Goods Movement Call
interface to SAP NetWeaver Process Integration (PI).

This BAdI belongs to the Enhancement Spot /ACCGO/CMN_ES_GOODS_MOVEMENT.

This BAdI has the two methods CHANGE_DATA_INBOUND and CHANGE_DATA_OUTBOUND as follows:

 Method CHANGE_DATA_INBOUND (Change Inbound Data for GM Proxy)

By using this method, the inbound data to goods movement proxy can be changed as per the
requirement of the caller. This helps the caller to have an interaction before the data is actually
processed to be sent out to the PI system.

 Method CHANGE_DATA_OUTBOUND (Change Outbound Data for GM Proxy)

By using this method, the caller can change the data after it has been processed and is ready to be
sent out to the PI system. This helps the caller to have an interaction point after the data is prepared to
be sent to the PI system.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Example

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a relevant release
and then Function-Oriented View under Application Help. In SAP Library, choose SAP NetWeaver Library:
Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS
ABAP -> ABAP Customer Development -> Enhancement Framework.

4.3.12.1.2 BAdI: Goods Movement Call via Contract Request Out

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 137 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

This Business Add-In (BAdI) is used to modify the inbound and outbound data for the Goods Movement Call
via Contract Request Out interface to SAP NetWeaver Process Integration (PI).

This BAdI belongs to the Enhancement Spot /ACCGO/CMN_ES_GOODS_MOVEMENT.

This BAdI has the two methods CHANGE_DATA_INBOUND and CHANGE_DATA_OUTBOUND as follows:

 Method CHANGE_DATA_INBOUND (Change Inbound Data for MCAK GM Call)

By using this method, the inbound data to contract request out proxy can be changed as per the
requirement of the caller. This helps the caller to have an interaction before the data is actually
processed to be sent out to the PI system.

 Method CHANGE_DATA_OUTBOUND (Change Outbound Data for MCAK GM Call)

By using this method, the caller can change the data after it has been processed and is ready to be
sent out to the PI system. This helps the caller to have an interaction point after the data is prepared to
be sent to the PI system.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Example

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a relevant release
and then Function-Oriented View under Application Help. In SAP Library, choose SAP NetWeaver Library:
Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS
ABAP -> ABAP Customer Development -> Enhancement Framework.

4.3.12.2 Asynchronous Response – Inbound to SAP

4.3.12.2.1 BAdI: Asynchronous Response - Inbound to SAP

Use

This Business Add-In (BAdI) is used to enhance the data coming from the 3rd party (3PT) proxy structure.

This BAdI is called after an asynchronous response from the 3PT system is received.

This BAdI contains the following methods:

 CALL_PROXY (Call Proxy Class)

You can use this BAdI method to call the proxy class objects and the methods.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 138 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 MAP_2_PROXY (Map to Proxy Structure)

You can use this BAdI method to map the relevant data structure to the prooxy data structure.

 CALLFROM_INBOUND (Called by Inbound Proxy of Asynchronous Message)

This BAdI method is called by the inbound proxy of the asynchronous messages that are
ACCGO/CL_PI_CSLTRANSACTION_S1 and ACCGO/CL_PI_CSLTRANSACTION_ST.

 RETRIGGER_OUTBOUND_MSG (Retrigger Outbound Message)

You can use this BAdI method to retrigger the outbound message to the 3PT system.

Requirements

A 3PT system and the proxy generation must have been activated prior to using this BAdI.

Standard settings

For more information about the standard settings (filter, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

To implement this BAdI, you create an enhancement implementtion first and then create the class.

Once the class is created, then you can implement the relevant methods one by one.

Example

This BAdI is available in the Enhancement Spot /ACCGO/CMN_ES_ASYNC_MSG.

For more information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a relevant release
and then Function-Oriented View under Application Help. In SAP Library, choose SAP NetWeaver Library:
Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS
ABAP -> ABAP Customer Development -> Enhancement Framework.

4.3.13 Customer Namespace

Tables that have been defined with class ‘E’ have delivered entries and customer entries in a separate
namespace. The below table shows the customer namespaces that are allowed for each table.
Table Text Column Namespace
/ACCGO/T_ANTYPE Analysis Type ANALYSIS_TYPE Y*, Z*
/ACCGO/T_APLINS Application Instructions APPL_INSTR Y*, Z*

/ACCGO/T_APP_OBJ TDOBJECT 9*
TDOBJECT TDOBJECTAssignment of text-

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 139 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

objects to applications

Technical customising table to link leaf key

/ACCGO/T_ARFLINK and rule ID LEAF_KEY Y*, Z*
Technical customising table to link leaf key
/ACCGO/T_ARFLINK and rule ID RULE_ID Y*, Z*
CA Maintain Application Document Item
/ACCGO/T_CAS_ICT Category ITEM_CAT Y*, Z*
CA Application Document Item category
/ACCGO/T_CAS_ICX texts ITEM_CAT Y*, Z*
/ACCGO/T_CERTCT Certification Category CERT_CAT Y*, Z*

/ACCGO/T_CHK_FM Function Module Names for Check Criteria ACTIVE_CHECKS 9*

/ACCGO/T_CHK_FMT Texts for Check Criteria ACTIVE_CHECKS
Quantity Profiles for Contrat Types in GTM
/ACCGO/T_CMN_QTP T/Cs QUAN_PROFILE
Quanity Type Texts for Quantity types in
/ACCGO/T_CMN_QTT GTM T/Cs QUAN_TYPE
/ACCGO/T_CMN_QTY Quantity Types used in GTM T/Cs QUAN_TYPE
/ACCGO/T_CMN_QUE Status Queue GRP_TYP Y*, Z*
/ACCGO/T_CMN_QUE Status Queue STATUS_ID Y*, Z*
/ACCGO/T_CMN_SGR Status group table GRP_TYP Y*, Z*
/ACCGO/T_CMN_SGT Text table for group text GRP_TYP Y*, Z*
/ACCGO/T_CMN_SID Status management Table STATUS_ID Y*, Z*
/ACCGO/T_CMN_SIT Status management status text STATUS_ID Y*, Z*
/ACCGO/T_CMN_STA Status ID table GRP_TYP Y*, Z*
/ACCGO/T_CMN_STA Status ID table STATUS_ID Y*, Z*
/ACCGO/T_CSDPCP CSDP: Counter Party Type /ACCGO/CPT 0-9
/ACCGO/T_CSDPCPT CSDP: Counter Part Type /ACCGO/CPT 0-9

/ACCGO/T_DOCTYP Configure the settlement document types DOC_TYP Y*, Z*

/ACCGO/T_DOCTYPT Text Table for Settlement Document Type DOC_TYP Y*, Z*

/ACCGO/T_DOC_TY CA Application Document Type DOC_TYPE Y*, Z*

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 140 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

/ACCGO/T_DOC_TYT CA Application Document Type texts DOC_TYPE Y*, Z*

/ACCGO/T_EVTMAS Settlement events for revenue recognition FIELD_NAME Y*, Z*

/ACCGO/T_EVTMAST Text Table for /ACCGO/T_EVTMAS FIELD_NAME Y*, Z*
/ACCGO/T_GRMATTY : Material group type master MAT_GR_TYPE 0-9
/ACCGO/T_GRMT_TX : Group material type text MAT_GR_TYPE 0-9
/ACCGO/T_GRPCAT Group Category GRPCAT 9*
/ACCGO/T_GRPCATT Text Table for Group Category GRPCAT 9*
Tab Details (GTM Trading Contract Screen
/ACCGO/T_GTMTAB Enhancement) TAB_NAME Y*, Z*
Tab Name (GTM Trading Contract Screen
/ACCGO/T_GTMTABT Enhancement) TAB_NAME Y*, Z*
/ACCGO/T_LEAF Maintain Leaf to Node relation LEAF_KEY Y*, Z*
/ACCGO/T_LEAF Maintain Leaf to Node relation NODE_KEY Y*, Z*

/ACCGO/T_MAT_CHE Table that holds the chosen matching checks ACTIVE_CHECKS 9*

/ACCGO/T_MAT_CRI Matching criteria definition table ACTIVE_CHECKS 9*
/ACCGO/T_NODE Maintain Node Defination NODE_KEY Y*, Z*
/ACCGO/T_OPCATG Contract Optionality Categories OPNLTY_ID Y*, Z*
/ACCGO/T_OPCATGT Contract Optionality CategoryTexts OPNLTY_ID Y*, Z*

/ACCGO/T_RUL_HDR Application Rules Framework Rule header RULE_ID Y*, Z*

/ACCGO/T_RUL_HDR Application Rules Framework Rule header RULE_NAME Y*, Z*

/ACCGO/T_SAPP_ID Assign text-IDs to sub-application IDs TDID 9*, Y*, Z*
/ACCGO/T_SUBSCR Maintain Subscreen Sequence SUBSCREEN_ID Y*, Z*
/ACCGO/T_SUBSCR Maintain Subscreen Sequence TAB_NAME Y*, Z*

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 141 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.4 Country Specific Settings

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 142 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.4.1 Brazil

4.4.1.1 Contract Settlement

4.4.1.1.1 Automatic Invoice
4.4.1.1.1.1 Define Settlement Invoice Type

Use

In this Customizing activity, you can define different invoice types. This will change the Brazilian settlement
behavior from creating invoices with On-Hold status to creating and posting invoices automatically.

You use this Customizing activity to activate Automatic Invoicing along with invoice type selection hierarchy
and automatic invoicing BAdI.

Activities

To define the settlement invoice type, proceed as follows:

1. Choose New Entries.

2. Enter the required details.
3. Save entry.

4.4.1.1.1.2 Determine Selection Sequence for Settlement Invoice Types

Use

In this Customizing activity, you can define the selection sequence of invoice types based on the available
Customizing fields.

It shall be Customizing only if automatic invoicing is needed, together with settlement invoice types and with the
implementation of automatic invoice BAdI.

Activities

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 143 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

To determine selection sequence for settlement document types, proceed as follows:

1. Choose New Entries.

2. Enter required details.
3. Save the entry.

4.4.1.1.2 Reversal Scenario

4.4.1.1.2.1 Configure Settlement Reversal Scenario for Sales

Use

In this Customizing activity, you can define Settlement Reversal Scenarios. This will determine the available
scenarios for Brazilian companies. You also set the texts that describe the Reversal Scenarios.

You use this Customizing activity to assign a determined technical class (see SE24) that enables a reversal
scenario to work for Brazil integrated with Contract Settlement Solution.

Activities

To define the settlement reversal scenario, proceed as follows:

1. Choose New Entries.

2. Enter the required details in the following fields:

o Rev. Scen. (reversal scenario definition)

o Class/Interface

o Reversal Parameter

3. Save entry.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 144 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

4.4.1.2 Expense Management

4.4.1.2.1 Set Relevancy of Billing Types for Brazilian Expense Process

Use

In this Customizing activity, you set the billing types for the expenses used in Brazilian scenarios. You can
activate the Brazilian expense processes according to the billing type.

Activities

To make this setting, proceed as follows:

1. Enter the type of scenario, either P Purchase (MM) or S Sale (SD).

2. Enter the billing type.

3. Check the nota fiscal relevant checkbox. This ensures the Brazil tab appears in the VBD.

4. Save your settings

Example

Assume that you want to create a purchase expense while taking the localization features into account. You do
the following:

1. You have a billing type for the purchase of an expense.

2. You assign the billing type to a purchase expense class.

3. You set the relevancy of Nota Fiscal to 'X' for the documents inthe purchase scenario that is associated with
this ABD billing document type.

Assume that you want to create a sales expense without taking the localization features into account. You do
the following:

1. You have a billing type for the selling of an expense.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 145 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

2. You assign the billing type to a sales expense class.

3. You leave the relevancy of Nota Fiscal blank for the documentsin the sales scenario that is associated with
this ABD billing document type.

Note: You must maintain the billing types for the provisional settlement of an expense and settlement of an
expense. If you do not maintain the billing types for both, the standard GTM expense process takes place.

4.4.1.2.2 Map Sales Area and ABD Billing Type to Sales Billing Type

Use

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 146 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

In this Customizing activity, you maintain the sales organization data associated with the billing type for sales
expense processes.

With the Sales Area and Agency Billing Document (ABD) billing type fields, you determine the sales order type,
the item category, and the billing type used to generate the sales billing document.

Activities

To make this setting, proceed as follows:

1. Enter the sales organization.

2. Enter the distribution channel.

3. Enter the division.

4. Enter the billing type

5. Enter the sales type

6. Enter the item category

7. Enter the billing type.

8. Save your settings.

Example

Assume that you have a sales expense process and need to assign the sales and distribution data to this
expense. You do the following:

1. You create an ABD billing type for the sales expense.

2. You create a sales and distribution billing type that is relevant for nota fiscal for external transaction (this
means that you do not have to create a delivery and sales order document in advance).

3. You enter the sales area data and the sales and distribution document data (sales order, item category, and
billing type) assigned to the ABD billing type.

4.4.1.2.3 Map Expense Condition Type to Material

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 147 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Use

In this Customizing activity, you define the relationship between the expense condition type and the material
transferred to the sales billing document or purchase invoice document.

Activities

To make this setting, proceed as follows:

1. Enter the scenario type, either P Purchase (MM), or S Sales (SD).

2. Enter the condition type.
3. Enter the material.
4. Save your settings.

Example

Assume you have an expense (for fumigation) in which the condition type is defined as GE01. You must create
a material in the material master data and assign it to the GE01 condition type in the customizing table. The
sales billing document or purchase invoice is then created with the material set.

4.4.1.3 Intracompany

4.4.1.3.1 Define Intracompany Inbound Delivery Type

Use

In this Customizing activity, you can define the inbound delivery types for intracompany scenarios. You can
define one delivery type for one purchase order type, usually defining a specific Brazilian inbound delivery for
intracompany stock transfer order (STO).

An inbound delivery is created from an outbound delivery for Brazilian intracompany scenarios. An outbound
delivery retrieves its data from a Purchase Order.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 148 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Prerequisites

You have created the purchase order type in Customizing for Materials Management under Purchasing ->
Purchasing Order -> Define Document Types.

You have created the delivery type in Customizing for Logistics Execution under Shipping -> Deliveries ->
Define Delivery Types.

Activities

To maintain the inbound delivery types for intracompany scenario, proceed as follows:

1. Choose New Entries

2. Enter the required details
3. Save the entry

4.4.1.4 Enhancements using Business Add-Ins

4.4.1.4.1 Contract Settlement

Enhancements for Settlement Bazil -- Maintenance of Automatic Invoice

All Business Add-Ins (BAdIs) grouped under this structure node belong to the enhancement spot
/ACCGO/CMN_ES_BR_STL. You can use the BAdI of this enhancement spot to change an incoming invoice's
data

4.4.1.4.1.1.1 BAdI: Changing Incoming Invoice Creation Data

Use

This Business Add-In (BAdI) is used in the Settlement component. You can use this BAdI to change incoming
invoice data, and therefore allow automatic posting of incoming invoice. This BAdI is called when Automatic
Invoice Settlement invoice type is set to automatic and the settlement data matches the specified values. After
you have implemented this BAdI, you must perform the following Customizing activities:

 Define Settlement Invoice Type

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 149 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

 Determine Selection Sequence for Settlement Invoice Types

This BAdI contains the method CHANGE_AUTO_INVOICE_DATA - Change BAPI Incoming Invoice data for
automatic incoming.

5 Rules Maintenance in Business Rules Framework

Refer to the configuration document “ACM_BRFplus_Configuration_guide” for rules setup.
 Contract Application business rules
 Call-Off Business rules
 OF Business rules
 Settlement Business rules

5.1 Steps for Maintaining BRF+ Catalogue

5.1.1 Step 1-> Launch BRF+
Launch BRF+ is using transaction BRFPLUS or BRF+ in SAP GUI. In case there are issues with step 1,
please contact the system administrator. The installation of BRF+ and troubleshooting of problems with
BRF+ are not in scope of this document.

When you click on the link, below window will open as a part of Internet Explorer.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 150 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

A set of sample rule sets and expressions have been delivered in application
/ACCGO/TEMPLATE_BRULES by SAP. The recommendation is to make a copy of the delivered content
in /ACCGO/TEMPLATE_BRULES in a new application and make changes to the copies and not the
original delivered objects. After this step, create a catalog and add the objects you need to the catalog.
The steps to create net new content in BRF+ is not in scope of this document.
Step 1a) Create Application

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 151 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 1b) Create Catalog in the application

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 152 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Click “Create and Navigate to the Object”.

5.1.2 Step 2-> Add Catalog

Step 2a) Click on the personalize button on the top right corner.

Step 2b) When you click on the button, below Personalization pop up window will appear.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 153 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 2c) Navigate to “Catalogs” tab.

Step 2d) Enter the newly added catalog by clicking on the “Add” button and click on Save.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 154 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 2e) Enter the newly added catalog in the “Name” field and click on “Search”.

Step 2f) Catalog appears in the result list.

Step 2g) Click on the Object and Press “OK”.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 155 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 2h) Default Catalog change message will appear after successful addition of the catalog

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 156 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 2i) Press “Save”

5.1.3 Step 3-> Maintenance of values in Catalog

Step 3a) Click on “Catalog” Tab and now the newly added Catalog will appear as below

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 157 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 3b) Right Click on Catalog and navigate as below

Step 3c) An Object Query Window will open as below

Step 3d) Enter the name of the expression created in the “Name” field. Wildcard searches are also
permitted.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 158 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Step 3e) Select the object and Press “OK”

Step 3f) Insert Values to the particular Rule by using “Insert New Row” Button.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 159 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

5.2 Maintenance of BRF+ for ACM Processes

Below are the ACM Component Areas for which BRF+ rules needs to be maintained.
1. BRF+ Rules for Capturing Contracts

2. BRF+ Rules for Managing Expenses

3. BRF+ Rules for Managing Call-Offs

4. BRF+ Rules for Capturing Load Data

5. BRF+ Rules for Processing Contract Applications

6. BRF+ Rules for Settling Contracts

5.2.1 BRF+ Rules for Capturing Contracts

SAP Agricultural Contract Management provides a set of template Business Rule Framework plus
(BRF+) rules. You can either use these rules as they are delivered, or you can create your own rules.
The screenshots displayed are for the content delivered. In case, standard rules are not used and net
new custom rules are developed, the screenshots will not be valid.

The following table lists the BRF+ rules that are relevant for Capturing Contracts:
ID Name Mandatory/Optio Description
nal
DP01 Assign Volume Optional You use this rule to assign a
Schedule to volume schedule to a Trader's
TSW Location and Scheduler’s Workbench
(TSW) location. The TSW
location links a volume
schedule to a plant, and the
system uses the plant to
determine whether the
volume schedule is permitted
in a particular contract.
PR01 Pricing Rules for Optional You use this rule to distribute
Lots the load quantity over pricing
Consumption lots under one commodity
item.
PR02 BU Lock Optional This rule implements business
unit (BU) locking for a
particular load while applying
it against pricing lot of a
contract.

Sample Maintenance of above Rules would look as below

DP01

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 160 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

PR01

PR02

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 161 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

5.2.2 BRF+ Rules for Managing Expenses

The following table lists the BRF+ rules that are relevant for Managing Expenses :
ID Name Mandatory/Optio Description
nal
E001 Expense Optional You set this rule so that the
Recovery Rule system can determine whether
an expense is recoverable
using the SAP Agricultural
Contract Management
settlement process or not.
When setting this rule, you
define a combination of
expense class, material,
vendor, and plant details.
When the vendor billing
document is created, the
system evaluates this rule.
The expenses that can be
recovered using SAP
Agricultural Contract
Management are settled in the
Settlement Work center.

Sample Maintenance of E001 Rule would look as below

E001

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 162 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

5.2.3 BRF+ Rules for Managing Call-offs

The following table lists the BRF+ rules that are relevant for Call-offs:

ID Name Mandatory/Optio Description

nal
C001 Call-off Mode Optional You use this rule to determine
Determination the mode while calling off a
contract. Based on whether
the mode is automatic
proposed, or manual, the
pricing TC is selected for the
contract. Default behavior is
manual.

C002 Firming Indicator Optional You use this rule to firm a call-
Rules during off process after the order is
Call-off created. If the rule is not
configured, you cannot set the
firming indicator, and thereby
you cannot perform call-off on
the contract.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 163 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

C003 Tolerance Mode Optional You use this rule to set the
Rules during tolerance mode for a given
contract. By setting this
indicator, the system considers
the tolerance values underfill
Or overfill) while calling off a
contract.

Sample Maintenance of above rules would look as below

C001

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 164 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

C002

C003

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 165 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

5.2.4 BRF+ Rules for Capturing Load Data

ID Name Mandatory/Optional Description

OE01 OF Determination Mandatory This Rule allows Orchestration
Scenario Framework to determine the
business scenario for an
application instruction and calling
application.
OE02 OF Execution Mandatory This Rule allows Orchestration
Scenario Framework to execute specific
TSW movement scenario
depending on Title Transfer,
Calling Application and Transaction
Type(Purchase/Sale/Intercompany)
ST07 Vendor Default Optional This Rule determines the list of
Split vendors and their percentages.

Important Note: All the Rules in OE01 and OE02 involve Standard TSW Junction Function Movement
Scenarios and it does not involve any transactional data values. Please ensure configuration mentioned
in ACM_OF_Configuration_guide is complete before preceding the rules for OE01 and OE02.
Below Screen shot shows all the values (possible scenarios) which needs to be maintained in OE01.
OE01 (For External Purchase/Sale Scenarios/Return Scenarios)

OE01 (Inter-Intra Company Scenarios)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 166 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OE02 (External Sale/Purchase)-Sequence 1

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 167 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

List_of_OE02_LDC_P
OSTING_Sequence_1.xlsx

Import for Excel can be used to get values from above excel sheet. This has the comprehensive list of all
the scenarios supported by ACM.
OE02 (Spot/Accumulate to Own/Accumulate to Store/Unassigned)-Sequence 2

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 168 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OE02 (Inter/Intra Company Scenario)-Sequence 3

List_of_OE02_INTER
_INTRA_Sequence2.xlsx

OE02 (Returns Purchase/Sale Scenario)-Sequence 4

OE02 (Application Scenario)-Sequence 5

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 169 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

5.2.5 BRF+ Rules for Processing Contract Applications

The following table lists the BRF+ rules that are relevant for Contract Application:
ID Name Mandatory/Optional Description
AP04 Application Optional You use this rule to
Mode determine whether
application is to be
automatic or manual. If
you set the application
mode as manual for a
particular plant and
commodity then all the
application documents
created in that particular
plant for that commodity
will be always sent to
the manual application
work center for manual
application. This rule is
only applicable in
unplanned scenario.
The default behavior is
manual mode.
AP01 Application Mandatory You can maintain
Rules/Call-off application rules at
Sequencing plant level to select
contracts and sort them.
You can base the
sorting of the selected
contracts on the
following criteria:
-Pricing type of the
contract– no price, no
futures, fully priced, and
so on.
-Price status

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 170 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

-Creation date (oldest to

newest)
-Delivery period
selection(oldest open to
the newest open –
including future given
tolerance)
-Settlement status, for
example, with advance
or pre-payment

AP02 Preliminary Optional Using this rule, you can

Overfill set a preliminary overfill
Tolerance tolerance that works in
conjunction with the
contract overfill
tolerance (an additional
percentage). You can
set the provisional
application to proceed
with a warning, without a
warning, or to stop with
an error message based
on the values you
maintain in the rule. For
example, if the open
quantity is 100 MT, the
contract tolerance is
10%, and the
preliminary overfill
tolerance business rule
range is 5% to 15%.
AP06 Early Delivery Optional You maintain this rule at
Tolerance the plant/commodity
level to relax the
delivery period
restriction. You must use
the number of days that
you maintain in the rule
in conjunction with the
delivery period
maintained for the
commodity item in the
contract (delivery to date
minus the number of
days). For example, if 7
days is maintained, and
the delivery start date in
the contract for the
commodity item is 2013-

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 171 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

12-01, then a load

arriving in the last 7days
of November also can
be applied.

AP05 Preliminary Optional You use this rule to

Underfill issue a warning or error
Tolerance message during
evaluation of the
underfill tolerance
maintained in the
contracts. You can set
the preliminary underfill
tolerance to a
percentage figure that
operates in conjunction
with the contract
underfill tolerance.
Furthermore, you can
use the rule to
determine whether the
system issues a warning
or error message should
the quantity fall into the
underfill tolerance range
maintained in the
business rule.
AP08 Late Delivery Optional You maintain this rule at
Tolerance a plant/commodity level
to relax the delivery
period restriction. The
number of days you
maintain in the rule has
to be used in
conjunction with the
delivery period
maintained for the
commodity item in the
contract (delivery to date
plus the number of
days). For example, if
you set the rule to 7
days, and the delivery
end date for the
commodity item in the
contract is 2010-10-31,
then a load arriving in
the first 7 days of
November also can be
applied.
AP09 Automatic Fill Optional This business rule
comes into effect during

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 172 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

and Roll the application process

to determine firstly
whether a fill and roll to
the next contract should
occur or not, and
secondly whether a fill
and roll to another
commodity item within
the same contract
should occur or not.

5.2.6 BRF+ Rules for Settling Contracts

The following table lists the BRF+ rules that are relevant for Settling Contracts:
ID Name Mandatory/Optional Description
ST02 Auto Settle Optional This rule determines if
automatic settlement is
allowed for the Different
combination of inputs.
For example, Material,
Mode of transport, Profit
Center, Plant, Company
Code. This rule is
executed only during
batch report. The batch
report picks an
application which can be
settled (and the rule for
auto settle is
maintained) If the rule is
not maintained, the
settlement will not be
created for those
applications.
ST03 Auto Release Optional This rule determines the
or Approve & range for which auto
Tolerance release and auto
approval is allowed for
the criteria material and
plant.
ST04 Auto Optional This rule determines if
Settlement automatic final
Stop settlement should be
prevented for certain
Purchase Organizations
or Sales Area. This rule
is evaluated if there are
open contracts attached
to the contract.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 173 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

ST06 Advance Optional This rule determines if

Percentage the settlement value
Rounding should be rounded up or
down .If this rule is not
maintained, we do not
round up or round down
the value. The value is
invoiced as it is.
ST07 Vendor Default Optional This rule determines the
Split list of split vendor and
Percentage their percentage.
ST08 Auto Grouping Optional This rule determines the
Settlement list of field which forms
Documents the grouping criteria for
settlement. The inputs
are based on the
following:
Company code
(BUKRS)
Purchase Organization
(EKORG)
Material Number
(MATNR)
Vendor (LIFNR)
Plant (WERKS_D)
Side (WLF_PR_SIDE)
ST09 Advance Optional This rule determines the
Percentage threshold to be
Provisional defaulted on the
settlement value.
Example
input to this rule is
Material
Number (MATNR),
Vendor
(LIFNR),
Plant( WERKS_D)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 174 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

6 Orchestration Framework Configuration

6.1 Basic Configuration
Orchestration Framework Configuration Includes below Steps.
1. Configuration of Junction function as a part of Trader’s and Scheduler’s Workbench(TSW)
2. Configuration of Business Rules as a part of Orchestration Framework rules

6.1.1 Configuration of Junction function

This Configuration includes below steps
a) Define Junction
b) Define Function to a Junction
c) Define Groups
d) Assign functions to groups
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code NA
Scenarios Non Nominated Scenarios
External Purchase
External Sale
CCAK Returns Purchase
CCAK Returns Sale
Inter & Company Sale & Purchase
Commingled
Accumulate to Store/Accumulate to Own/Regular Spot/ Unassigned
Nominated Back to Back Scenarios
Back to Back External Purchase and External Sale
Back to Back External Purchase and Inter/Intra-Company Sale
Back to Back External Sale and Inter/Intra Company Purchase
Back to Back Inter/Intra Company Purchase and Inter/Intra Company Sale
Application Spot Scenarios
Application Call to OF during Spot ,Accumulate to Own and Other scenarios
Screen Shot Number OF_CONFIG_1,OF_CONFIG_2,OF_CONFIG_3,OF_CONFIG_4,OF_CONFIG_
5, OF_CONFIG_6
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 175 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note This is the Main Configuration for OF. This setting is Mandatory For Document
Posting. Always Define junction function groups and assign functions to
junctions. The function groups that you define are called by the junctions
(system interfaces). By entering a function module ID, specific function is called.
The function that is called includes a dynamic call to the functions assigned to
the function group. The functions that belong to the function group must have
identical interfaces within the application.
Function Modules Defined in particular Junction can be re-used in multiple
groups configured
Steps 1. Define Junction

->2. Define Functions

->3.Define Groups
->4.Assign Functions to Groups

6.1.1.1 Define Junction

Traverse through below IMG Configuration for defining Junctions
SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s Scheduler’s Workbench-
>General Settings->Junction Functions-> Define Functions-> Define Junction

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 176 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_1
Create or Maintain Junction Function for Each of the Scenarios

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 177 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG 2
03->Carrier Ticket – For Ticket Creation with Nomination reference
13-> CIP without Nomination – For Ticket creation without Nomination Reference

6.1.1.2 Define Function to a Junction

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 178 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Define all the Individual API’s to a particular Junction Function as below by creating a Junction Indicator
number and API.

OF_CONFIG_3
6.1.1.3 Define Groups
Define Individual Business Scenarios by Groups for particular Junction

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 179 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_4

6.1.1.4 Assign functions to groups

For each of the Function Group, Enter Junction Indicator either by using Search help or manually.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 180 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG 5
Search help can also be used to select Function Modules

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 181 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG 6

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 182 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

6.1.2 Ticket Type and Execution Mode Configuration for OF

6.1.2.1 Execution Mode Configuration for OF
IMG Path SPRO->Display SAP Reference ->Logistics General-> Global Trade
Management->Agricultural Contract Management->Load Data Capture->Define
Execution Mode for Orchestration Framework

Transaction Code NA
Scenarios LDC Call to OF
Application Call to OF

Screen Shot Number OF_CONFIG_7, OF_CONFIG_8, OF_CONFIG_9

Pre-requisite - Optional
Optional/Mandatory
Note In this customizing, you maintain whether the Orchestration Engine is called in the
online mode, QRFC or the background mode.

Steps Execution Mode for Orchestration Engine

Traverse through below IMG Configuration for defining Execution Mode

SPRO->Display SAP Reference ->Logistics General-> Global Trade Management->Agricultural Contract

Management->Load Data Capture->Define Execution Mode for Orchestration Framework

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 183 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 184 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_7

Define Execution Mode in below modes for a particular user.

- Online
- Queue
- Background

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 185 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 186 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_8

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 187 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_9
6.1.2.2 Ticket Type Configuration for OF
IMG Path SPRO->Display SAP Reference ->Logistics General-> Global Trade
Management->Agricultural Contract Management->Load Data Capture->Define
TSW Ticket Types for OF Events

Transaction Code NA

Scenarios Ticket type for Nomination

Ticket type for LDC
Ticket type for Application

Screen Shot Number OF_CONFIG_10, OF_CONFIG_11

Pre-requite - Mandatory
Optional/Mandatory
Note In this customizing, you maintain the TSW ticket types which are created for the OF
execution process. It is mandatory to maintain this customizing for OF execution to
work for the following scenarios:

1. Execution of the Back to Back scenario - Please maintain the ticket type
for "Ticket type for Nomination".
2. Scenario determination and Logistical execution for all scenarios other
than Back to Back - Please maintain the ticket type for "Ticket type for
LDC".
3. Regular Spot, Accumulate and Own and Purchase of Comingled stock
scenarios - Please maintain the ticket type for "Ticket type for Application".

Steps Maintain TSW Ticket types for OF Events

Traverse through below IMG Configuration for defining Execution Mode for Orchestration Engine
SPRO->Display SAP Reference ->Logistics General-> SAP Global Trade Management->Trading
Solution->LDC & Orchestration Engine ->Execution Mode for Orchestration Engine

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 188 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 189 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_10
Different Standard TSW Tickets needs be configured as below

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 190 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_11

6.1.3 Configuration of Business Rules (OF rules Framework)

6.1.3.1 OF Determination Business Rules
Refer BRF+ Rule OE01 in Section 4.5.2.
6.1.3.2 OF Execution Business Rules
Refer BRF+ OE02 Rule in Section 4.5.2.

6.2 OF Configuration for Individual Scenarios

Non-Nominated Scenarios/External Party Scenarios
Common Determination Configuration needs to be maintained for

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 191 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

-External Purchase Title Transfer Origin (TTO)

-External Purchase Title Transfer Destination (TTD)
-External Sale Title Transfer Origin (TTO)
-External Sale Title Transfer Destination (TTD)
Execution Scenarios differ depending on Contract and Order Entry in LDC.
This Function Group will determine Contract, Order and Title Transfer Associated with Line item entered
rd
respectively. This Configuration once Maintained under OF rule Node, should suffice for all 3 Party
Scenarios.

OF_CONFIG_12

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 192 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_13
13-> CIP without Nomination – For Ticket creation without Nomination Reference

6.2.1 External Purchase

6.2.1.1 Title Transfer Origin (TTO)
6.2.1.1.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction
Transaction Code BRF+
Scenarios External Purchase – TTO- Planned Unscheduled

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 193 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Screen Shot Number OF_CONFIG_14, OF_CONFIG_15

Pre-requisite - Mandatory
Optional/Mandatory
Note In this Execution Rules Framework, IBD,GR and Application Document
Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code BRF+(OE01 Rule)
 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.1)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_14, OF_CONFIG_15)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_14

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 194 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_15

6.2.1.1.2 Unplanned Unscheduled

IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios External Purchase – TTO- Unplanned Unscheduled
Screen Shot Number OF_CONFIG_16, OF_CONFIG_17

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 195 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Pre-requisite - Mandatory
Optional/Mandatory
Note In this Execution Rules Framework, PO,IBD,GR and Application Document
Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code BRF+(OE01 Rule)
 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.1)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_16, OF_CONFIG_17)

3) Configure Rule in BRF+(OE02 Rule)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 196 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_16

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 197 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_17
6.2.1.2 Title Transfer Destination (TTD)
6.2.1.2.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction
Transaction Code BRF+
Scenarios External Purchase – TTD- Planned Unscheduled
Screen Shot Number OF_CONFIG_18, OF_CONFIG_19
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 198 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, IBD,GR and Application Document

Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code BRF+(OE01 Rule)
 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.1)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_18, OF_CONFIG_19)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_18

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 199 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_19
6.2.1.2.2 Unplanned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction
Transaction Code BRF+
Scenarios External Purchase – TTD- Unplanned Unscheduled

Screen Shot Number OF_CONFIG_20, OF_CONFIG_21

Pre-requisite - Mandatory
Optional/Mandatory
Note In this Execution Rules Framework, PO,IBD,GR and Application Document
Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 200 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

- Scenario

Steps 1) Transaction Code BRF+(OE01 Rule)

 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.1)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_20, OF_CONFIG_21)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_20

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 201 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_21

6.2.1.2.3 Brazil External Purchase Triangular Operation TTD

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 202 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_21BR_01

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 203 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_21BR_02

6.2.2 External Sale

6.2.2.1 Title Transfer Origin & Destination (TTO/TTD)
6.2.2.1.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction
Transaction Code BRF+
Scenarios External Sale- TTO & TTD- Unplanned Unscheduled

Screen Shot Number OF_CONFIG_22, OF_CONFIG_23

Pre-requisite - Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 204 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Optional/Mandatory

Note In this Execution Rules Framework, OBD,GI and Application Document

Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code BRF+(OE01 Rule)
 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.2)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_22, OF_CONFIG_23)

3) Configure Rule in BRF+(OE02 Rule)

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 205 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_22

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 206 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_23

6.2.2.1.2 Unplanned Unscheduled

IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction
Transaction Code BRF+
Scenarios External Sale- TTO & TTD- Unplanned Unscheduled

Screen Shot Number OF_CONFIG_24, OF_CONFIG_25

Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 207 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, OBD,GI and Application Document

Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code BRF+(OE01 Rule)
 OE Determination Scenarios(Screen Shot OF_CONFIG_12,
OF_CONFIG_13 in Section 2.1.2)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group (Screen Shot OF_CONFIG_24, OF_CONFIG_25)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_24

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 208 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_25

6.2.3 Inter/Intra Company Sale & Purchase

Common Determination Configuration needs to be maintained for
- Title Transfer Origin (TTO)
- Title Transfer Destination (TTD)
- Title Transfer In-transit (TTI)
Execution Scenarios differ depending on STO and Outbound Delivery Entry in LDC.
Important Note – This Configuration mentioned in the guide of Orchestration Framework is only for
Scenario when IBD Creation is automatically via standard SPED Configuration. In a scenario when SPED
has been turned off, Necessary API to create IBD needs to be added in all the Scenarios of Inter/Intra
company

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 209 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_25

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 210 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_26

6.2.3.1 Title Transfer Origin (TTO) & Title Transfer In transit (TTI)
6.2.3.1.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios Inter-Intra Company – TTO/TTI- Planned Unscheduled
Screen Shot Number OF_CONFIG_27, OF_CONFIG_28
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 211 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, OBD,IBD,GR,GI,VLPOD, Application

Document Creation is performed using Ticket Without Nomination Functionality
based on
- Title Transfer
- Scenario
Steps 1) Transaction Code Transaction Code BRF+(OE01 Rule)
OE Determination Scenarios(Screen Shot OF_CONFIG_25,
OF_CONFIG_26 in Section 2.1.3 )

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
Define Group ( Screen Shot OF_CONFIG_27, OF_CONFIG_28)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_27

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 212 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_28

6.2.3.2 Title Transfer Destination (TTD)

6.2.3.2.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios Inter-Intra Company – TTD- Planned Unscheduled
Screen Shot Number OF_CONFIG_29, OF_CONFIG_30
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 213 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, OBD,IBD,GR,GI,VLPOD, Application

Document Creation is performed using Ticket Without Nomination Functionality
based on
- Title Transfer
- Scenario
Steps 1) Transaction Code Transaction Code BRF+(OE01 Rule)
OE Determination Scenarios(Screen Shot OF_CONFIG_25,
OF_CONFIG_26 in Section 2.1.3)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
Define Group ( Screen Shot OF_CONFIG_29, OF_CONFIG_30)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_29

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 214 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_30

6.2.4 Returns Purchase and Sale

Common Determination Configuration needs to be maintained for
- Return Sale
- Return Purchase
Execution Scenarios differ depending on Return Order and Outbound Delivery Entry in LDC.
This Function Group will determine Return and Outbound Delivery and Associated with Line item entered
respectively. This Configuration once Maintained under node below OE rule Node should suffice for all
the CCAK Return Sale and Purchase Scenarios.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 215 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_31

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 216 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_32

6.2.4.1 Return Purchase

6.2.4.1.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios Returns Purchase
Screen Shot Number OF_CONFIG_33, OF_CONFIG_34
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 217 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, Return OBD,GI, Application Document

Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code Transaction Code BRF+(OE01 Rule)
OE Determination Scenarios(Screen Shot, OF_CONFIG_30,
OF_CONFIG_31 in Section 2.1.4)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
Define Group ( Screen Shot OF_CONFIG_33, OF_CONFIG_34)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_33

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 218 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_34

6.2.4.2 Return Sale

6.2.4.2.1 Planned Unscheduled
IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios Returns Purchase
Screen Shot Number OF_CONFIG_35, OF_CONFIG_36
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 219 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework, Return IBD,GI, Application Document

Creation is performed using Ticket Without Nomination Functionality based on
- Title Transfer
- Scenario
Steps 1) Transaction Code Transaction Code BRF+(OE01 Rule)
OE Determination Scenarios(Screen Shot, OF_CONFIG_30,
OF_CONFIG_31 in Section 2.1.4)

2) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
Define Group ( Screen Shot OF_CONFIG_35, OF_CONFIG_36)

3) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_35

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 220 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_36

6.2.5 Regular Spot, Accumulate to Own, Undecided, Commingled

IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios -Regular Spot
-Accumulate to Own
-Unassigned
-Commingled/Accumulate to Store
Screen Shot Number OF_CONFIG_37, OF_CONFIG_38

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 221 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Pre-requisite - Mandatory
Optional/Mandatory
Note In this Execution Rules Framework GR +, GR -, Application Document Creation
is performed using Ticket Without Nomination Functionality based on
- Application Instruction

Steps 1) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_37, OF_CONFIG_38)

2) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_37

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 222 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_38

6.2.6 Application Call to OE

IMG Path SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s
Scheduler’s Workbench->General Settings->Junction Functions-> Define
Functions-> Define Junction

Transaction Code BRF+

Scenarios Application Call to OE during Spot and Accumulate to Own Scenarios to Create
PO, IBD & GR
Screen Shot Number OF_CONFIG_39, OF_CONFIG_40
Pre-requisite - Mandatory
Optional/Mandatory

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 223 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Note In this Execution Rules Framework PO,IBD, GR Creation is performed using

Ticket Without Nomination Functionality based on
- Calling Application

Steps 1) SPRO->Display SAP Reference ->Logistics Execution-> TSW (Trader’s

Scheduler’s Workbench->General Settings->Junction Functions->
Define Functions-> Define Junction
 Define Group ( Screen Shot OF_CONFIG_39, OF_CONFIG_40)

2) Configure Rule in BRF+(OE02 Rule)

OF_CONFIG_39

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 224 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_40

6.3 Error Processing

IMG Path

Transaction Code /ACCGO/OE_RECOVERY

Scenarios Back to Back Nominated Scenarios
Non Nominated Scenarios/External Party Scenario
Screen Shot Number OF_CONFIG_041, OF_CONFIG042, OF_CONFIG043, OF_CONFIG044,
OF_CONFIG_045
Pre-requisite - NA

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 225 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

Optional/Mandatory

Note Using this Report, Ticket Processing Status, Error log, Document Flow and Re-
processing of error records is possible.

Steps 1) Transaction Code /ACCGO/OE_RECOVERY

 Recovery Report (Screen Shot OF_CONFIG_041)

 Document Flow(Screen Shot OF_CONFIG_042)

 Error Log( Screen Shot OF_CONFIG_043)

 Ticket Error Log( Screen Shot OF_CONFIG_044)

 Re-Generate( Screen Shot OF_CONFIG_045)

OF_CONFIG_41

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 226 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_42

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 227 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_43

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 228 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

OF_CONFIG_44

6.4 List of API’s

Function
Code Function Name Description
9A01 /ACCGO/OEP_APPDOC_TRIGGER Create App Doc
9A03 /ACCGO/OEP_CREATE_CALL_OFF Create Call Off
9A04 /ACCGO/OEP_INB_GDMOV_INTO_SIT PGR 107 / 101 against IBD
9A05 /ACCGO/OEP_INB_GDMOV GR 109
9A06 /ACCGO/OEP_OBDEL_CONF PGI against OBD
9A07 /ACCGO/OEP_POST_IBD Create Change Delete IBD
9A08 /ACCGO/OEP_POST_OBD Create Change Delete OBD
9A09 /ACCGO/OEP_POST_PO Create Change Delete PO STO
9A10 /ACCGO/OEP_POST_SO Create Change Delete SO
9A11 /ACCGO/OEP_STOP_FUNC STOP FM
9A12 /ACCGO/OEP_VLPOD_TRIGGER VLPOD
9A13 /ACCGO/OED_DET_MATERIAL Material Determination
9A17 /ACCGO/OEP_SCP_STOP_FUNC May Stop FM
9A18 /ACCGO/OED_DET_CAK_ORD_DELV Determine Scenario and Txn Type

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 229 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013
Configuration Guide

9A19 /ACCGO/OEP_READ_IBD_FOR_STO Read IBD for STO

9A20 /ACCGO/OEP_POST_OBD_FOR_STO Create OBD for STO
9A22 /ACCGO/OEP_INB_GDMOV_INTO_SIT GR for 107 posting
9A24 /ACCGO/OEP_UPDATE_IBD Update IBD created by SPED or for PO
9A26 /ACCGO/OED_AUTO_APPL Auto Apply
9A27 /ACCGO/OEP_POST_IBD_FRM_OBD Post IBD for OBD
9A28 /ACCGO/OEP_INBDEL_CONF Create GR for IBD(STO)
9A01 /ACCGO/OEP_APPDOC_TRIGGER Create app doc
9A03 /ACCGO/OEP_CREATE_CALL_OFF Create Call off
9A04 /ACCGO/OEP_INB_GDMOV_INTO_SIT PGR 107 / 101 against IBD
9A05 /ACCGO/OEP_INB_GDMOV GR 109
9A06 /ACCGO/OEP_OBDEL_CONF PGI against OBD
9A07 /ACCGO/OEP_POST_IBD Create Change Delete IBD
9A08 /ACCGO/OEP_POST_OBD Create Change Delete OBD
9A09 /ACCGO/OEP_POST_PO Create Change Delete PO STO
9A10 /ACCGO/OEP_POST_SO Create Change Delete SO
9A11 /ACCGO/OEP_STOP_FUNC STOP FM
9A12 /ACCGO/OEP_VLPOD_TRIGGER VLPOD
9A13 /ACCGO/OED_DET_MATERIAL Material Determination
9A14 /ACCGO/CMGL_CREATE_GR_WO_REF Create GR w/o reference
9A15 /ACCGO/CMGL_CREATE_GI_IN_NEG_S create GI into negative S Loc
9A17 /ACCGO/OED_DET_TT Determine Title Transfer
9A18 /ACCGO/OED_DET_CAK_ORD_DELV Determine Scenario and Txn Type
9A19 /ACCGO/OEP_READ_IBD_FOR_STO Read IBD for STO
9A20 /ACCGO/OEP_POST_OBD_FOR_STO Create OBD for STO
9A21 /ACCGO/OED_DET_RETURNS_DELV
9A22 /ACCGO/OEP_INB_GDMOV_INTO_SIT GR for 107 posting
9A23 /ACCGO/OED_INTER_STO_DELV
Update IBD created by SPED or
9A24 /ACCGO/OEP_UPDATE_IBD for PO
9A25 /ACCGO/OEP_INBDEL_CONF
9A26 /ACCGO/OED_AUTO_APPL Auto Apply
9A27 /ACCGO/OFP_POST_IBD_FRM_OBD IBD from OBD
9A28 /ACCGO/OEP_APPDOC_UPDATE
9A29 /ACCGO/OEP_APP_ASGMNT
9A30 /ACCGO/OEP_TRIGGER_GM Trigger GM
9A31 /ACCGO/CMGL_CREATE_EVNT_RGSTRY
9A32 /ACCGO/OEP_COPY_EXPENSE Copy Expenses for Commingled
9B01 /ACCGO/BR_OEP_INB_TROP_GDMOV Brazilian GR for Triangular Oper.

© 2013 SAP AG Title: Agricultural Contract Management Configuration Guide Page 230 of 230
Dietmar-Hopp-Allee 16 Version: 1.0
D-69190 Walldorf Date: March 21, 2013