ACM Configuration Training

ACM Configuration Training
May 06-10 2013 – São Paulo

Marcos Rahmeier / Thiago Viaro – SAP Custom Development
Content
© 2013 SAP AG. All rights reserved. Internal 2

Basic Settings
Activate Switch for Systems Integration

Maintain Contract Type Determination
Maintain Quantity Types and Profiles
Manage Layout for GTM Contracts
Maintain Text Assignments
Maintain Mode and Means of Transport
Configure Related Trade Types
Allow maintenance of Backdated Master Data
Maintain Title Transfer Settings
Status Management
Optionality
Crop Season
Activate Switch for Systems Integration
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
Once you have activated an option, it is not possible to change this Customizing setting.
For additional details, please refer to SAP Note 1773636

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
D Commodity Contract STO Relevant
S Spot
I Intercompany Contract
R Intracompany Contract

Maintain Quantity Types and Profiles (1)
Define Quantity Types

In this activity, you define the Quantity Type, the Quantity Text (description),
and indicate whether this is a derived quantity.

Define Quantity Profiles

In this activity, you enter the quantity profile and remarks.
Define Quantity Types for Quantity Profile

In this activity, you enter the quantity types for each quantity profile.
Assignment of Quantity Profiles to TC Types
In this activity, you enter the Type, Quantity Profile, and Remarks.

Manage Layout for GTM Contracts (1)
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

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

Tab groups are assigned to business data by:

Company Code
GTM Contract Type
Sales/Purchase area


Maintain Text Assignments (1)
In this Customizing activity, you maintain the assignment of text objects and text IDs to applications and sub-applications
respectively.
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.

Maintain Text Assignments (2)
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

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.

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.
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.
Sts Reqd
Select this checkbox to allow the user to maintain the Status field in the Related Trade tab.

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.

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.

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.

Status Management (1)
Use
In this Customizing activity, you maintain the mapping between the selection ID
and their status.
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:
Doc. Sts (contract application document status)
OTy (object type)
SelProf (selection ID - status selection profile)
SysSt (system status)

Status Management (2)

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

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

Optionality (1)
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
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

Optionality (2)
You use this table to maintain the optionality category IDs and text.
The optionality categories delivered are:
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
Crop Season – Maintain Crop season Id
Use
In this Customizing activity, you maintain Crop Season IDs and their associated descriptions.
Example
ID Description
01 Spring Wheat 2011
02 Fall Wheat 2011

Crop Season – Maintain Crop season
Use
In this Customizing activity, you maintain the crop season IDs for various materials with their season start
and end dates.
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

Business Rules -- Maintain Match Criteria (1)
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.

Business Rules -- Maintain Match Criteria (2)

Content

Set up of Master Data
Pricing Aspects
Assign Pricing Condition to Pricing Condition Type Category
Assign Pricing Aspect to Pricing Aspect Type
Tolerances
Maintain Tolerance Types
DPQS
Maintain Class Type for Material Determination
Maintain Number range for DPQS
Maintain DPQS Parameters
Maintain Rounding Parameters for Tiered Prorated
Assign Value Schedule to TSW Location

Assign Volume Schedule to TSW Location

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 Basis Futures Index and 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
1 Index and 1 Basis condition type category
1 Futures and 1 Ratio condition type category

Assign Pricing Aspect to Pricing Aspect Type (1)

Assign Pricing Aspect to Pricing Aspect Type (2)
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.
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.
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

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.

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

Maintain DPQS Parameters - Governing Analysis
Use
• 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

Maintain DPQS Parameters - Governing Terms
Use
You enter governing terms, which can be used to indicate the price, quality, or quantity of the contract.

Maintain DPQS Parameters - Governing Weight
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:
Code Code for Parent Implied Hierarchy Origin/Destination LDC Certification

Category Description Status
ZDCW ZDOW 2 Destination 02 Destination Certified Analysis
ZDHW ZDCW 3 Destination 03 Destination House Analysis
ZDOW 1 Destination 01 Destination Official Analysis

Maintain DPQS Parameters - Regulatory Agency
Use
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

Maintain DPQS Parameters - Calculation Rules
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.

Maintain DPQS Parameters - Derived Rules
Use
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

Maintain DPQS Parameters - Averaging Methods
Use
You enter the averaging methods (a code and description).

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

Assign DPQS Value Schedule to TSW Location
You use this Transaction /ACCGO/TSW_VSA, rule to assign a value schedule to a Trader's and
Scheduler’s Workbench (TSW) location.

Assign DPQS Volume Schedule to TSW Location
You use this BRF+ rule to assign a volume schedule to a Trader's 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.

Content

Load Data Capture
Maintain Number Range for LDC

Define LDC Event Type
Maintain Analysis Types
Maintain Certification Category
Application Instructions
Define Attributes for MOT
LDC Configuration Overrides
Setup Master Data for LDC
Maintain TSW Locations

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'.

Define LDC Event Type
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 LDC can only work with standard event types):
01: Load
02: Unload

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.

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)
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

Application Instructions (1)
Application instructions which are recorded on the LDC event determine the behavior of the Orchestration
Framework (see separate OF Configuration Guide). The above 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).

Application Instructions (2)
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
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.

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.
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:
01: Road
02: Rail
03: Sea
04: Inland Waterway
05: Air
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

LDC Configuration Overrides
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)
For Each Location Type, maintain the locations (where LDC events will be recorded or will occur)
For each Location, Maintain:
Allowed Modes of Transport
Allowed Analysis Types
Allowed Certification Categories
Allowed Analysis (Regulatory) Agencies

Setup Master Data for LDC
Transaction /ACCGO/UIS_CUST

Maintain TSW Locations
Transaction /ACCGO/TSW_CUS

Content

Contract Application
Call-Off
Determine Order type for Sales Contracts
Determine Order type for Purchase Contracts
Maintain CAS relevancy for Sales Orders
Maintain CAS relevancy for Purchase Orders
Application Document
Maintain Number range for Application Document
Maintain Application Document Types
Maintain Application Document Item Categories
Assign Movement type for Follow-on Document creation
Maintain Number range for Application group
Maintain Number range for Application process
Maintain Number range for Application process sequence

Comingled Settings
Maintain Storage Location for Negative Postings
Maintain Movement Types
Maintain Program Types
Maintain Default Storage Programs
Maintain Storage relevant
Maintain Material at Negative Storage Location
Negative Stock Indicator

Call-Off

Use
In this Customizing activity, you establish the trading contract 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 Management -> Agricultural Contract Management -> Basic Settings ->

Use
In this Customizing activity, you establish the trading contract 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.
Requirements
The mapping of the incoterms to the title transfer values should have been maintained prior in Logistics -
General -> SAP Global Trade Management -> Agricultural Contract Management -> Basic Settings ->

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.

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

Application Document
Maintain Number range for Application Document
Maintain Application Document Types
Maintain Application Document Item Categories
Assign Movement type for Follow-on Document creation
Maintain Number range for Application group
Maintain Number range for Application process
Maintain Number range for Application process sequence

Maintain Number Range for Application Document
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.

Maintain Application Document Type (1)
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

Maintain Application Document Type (2)
Document type category

The document type categories available are as follows:
Purchase
Sales
Inter-company Purchase
Inter-company Sales
Intra-company Purchase
Intra-company Sales
Returns
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:
Normal (without True Item)
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.
Maintain Application Document item Category
Use
In this Customizing activity, you maintain the item categories for Application
Documents and the related document types. In addition, you can also
determine whether they are application-relevant or obligation-relevant.

Maintain Movement Types relevant for application document
Use
In this Customizing activity, you determine the stock movement types that trigger the
automatic creation or automatic reversal of an application document or both. The system
uses this Customizing setting to determine whether a movement type is for goods
movement creation or for goods movement reversal.
Requirements
You have determined the movement types in Customizing under Maintain Movement
Types.
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.

Maintain Number Range for Application Process
Use
In this Customizing activity, you determine number range intervals for contract application processes.
Requirements
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.

Maintain Number Range for Application Process Sequence
Overfill ID
Number range object - /ACCGO/AID
Configurable Parameter ID - GC_OVERFILL_OBJECT
Number range interval - 05
Configurable Parameter ID - GC_OVERFILL_RANGE
Underfill ID
Configurable Parameter ID - GC_UNDERFILL_OBJ
Configurable Parameter ID - GC_UNDERFILL_NR_INT
Maintain application number sequence

Number range object - /ACCGO/ASQ
Configurable Parameter ID - GC_APPL_SEQ_NR
Configurable Parameter ID - GC_APPL_SEQ_NR_INT

Maintain Number Range for Application Process Sequence
Spot Unique ID
Configurable Parameter ID - GC_SPOT_NR
Configurable Parameter ID - GC_SPOT_NR_INIT
Accumulate to Own ID
Configurable Parameter ID - GC_SPOT_NR
Configurable Parameter ID - GC_AO_SPOT_NR_INIT

Content

Contract Settlement
General Settings
Maintain Split criteria for Settlement Group
Maintain Number Range for Settlement Group
Agency Billing Document – Determine ABD Type
Maintain Number Range for Settlement Documents
Maintain Number Range for Lien
Maintain Number Range for Non-Standard Settlement Processes
Configure Number Range Intervals
Maintain Settlement Document Types
Determine Settlement Document Types
Configure Editable fields on Settlement Document
Maintain Reason Codes for Price override
Maintain Reason Code and Reason Text for Settlement Status Activity
Configure GL/PO Posting Settings
Maintain Central Lien Filling Notification
Maintain Settlement Events for Revenue Recognition

Settlement – General Settings (1)
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:
2. Enter the required fields.
3. Save entries

Settlement – General Settings (2)
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
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

Maintain Split criteria for Settlement Group
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:
2. Enter CoCd (Company Code) and Field Name.
3. Save entries.

Maintain Number Range for Settlement Group
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.
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

Agency Billing 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).
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.

Maintain Number Range for Settlement Documents (1)
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.

Maintain Number Range for Settlement Documents (2)
Requirements
You have defined the document types in table /ACCGO/T_DOCTYP.
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.
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.

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.
.

Maintain Number Range for Non-Standard Settlement Processes (1)
Use
In this Customizing activity, you can define and maintain number range objects for non-standard settlement
documents like washouts, circles,.
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. For example, No. 01 is
the sales area.
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 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.
Maintain Number Range for Non-Standard Settlement Processes (2)
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.
6. Choose the External Assignment checkbox to specify whether it is an internal or external assignment
To edit the NR Status field, proceed as follows:
8. Choose the (edit) NR Status pushbutton.

Maintain Settlement Document Types (1)

Maintain Settlement Document Types (2)
Use
In this Customizing activity, you maintain the different types of standard and non-standard settlement
documents. To view the various document types, see Settlement Document Type.
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.
4. Save the entry.

Determine Settlement Document Types (1)
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.
3. Save the entry.

Determine Settlement Document Types (2)

Configure Editable fields on Settlement Document
Use
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.
Activities
To make a field editable, do the following:
2. Enter Company Code, Doc. Category, and Field Name.
3. Select the Editable checkbox.
4. Save the entry.

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 price override 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

Maintain Reason Code and Reason Text for Settlement Status Activity
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:
5. Enter the reason code and reason text.
6. Save entries.
Configure GL/PO Posting Settings
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:
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.

Maintain Central Lien Filling Notification
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
Activities
To maintain central filling lien notification, proceed as follows:
2. Enter the required details and choose the Active flag
3. Save entries.

Maintain Settlement Events for Revenue Recognition
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.
If the revenue recognition registry has been enhanced with additional custom settlement events, configure the related
indicators and enable them here.
Note that the Physical Receipt indicator is only relevant for purchase realization.
Activities
To maintain settlement events for revenue recognition, proceed as follows:
2. Enter required details.
3. Save entry.

Content

Scenario Specific Settings
Back to Back
Comingled
Intercompany / Intracompany

Back to Back Settings
Maintain Default Settings for Back-to-Back

Map Nomination Movement Scenario to Title Transfer Movement Scenario
Maintain Default Settings for Nomination Peg type

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
Map Nomination Movement Scenario to Title Transfer Movement Scenario

Map Nomination Movement Scenario to Title Transfer
Movement 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.

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

Comingled
Comingled Settings
Maintain Storage Location for Negative Postings
Maintain Movement Types
Maintain Program Types
Maintain Default Storage Programs
Maintain Storage relevant
Maintain Material at Negative Storage Location
Negative Stock Indicator

Comingled - Maintain Storage Location for Negative Postings
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:
2. Define the following fields:
Plant
Location ID
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

Comingled - 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.
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:
2. Define the fields as follows:
Action
Select either Unload Event or Load Event from the dropdown list.
+ StLoc MT (Positive Storage Location Movement Type)Using the input help, select a movement type which should
be assigned to the positive storage location.
- StLoc MT (Negative Storage Location Movement Type) Using the input help, select a movement type which should be
assigned to the negative storage location

Comingled - Maintain Storage 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.

Comingled – 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.

Comingled - Maintain Storage Relevant
On the material master (MM01/MM02/MM03), maintain the

storage relevant indicator at the plant level.

Comingled - Maintain Material at Negative Storage Location
Ensure that the material is extended to the negative storage

location (MM01/MM02/MM03).

Comingled - Maintain Stock Indicator
Ensure that on the material master for the obligation location,

the indicator is set on the General/Plant tab.

Intercompany / Intracompany
Incoterm / Title Transfer configuration - /ACCGO/V_INCOT: Determination of

the title transfer based on Inco term.
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.
In the t-code OMJJ (Customizing: New Movement Types), set the
transaction VL02N, VLPOD for the movement types where the VLPOD is
required.

Content

Enhancements to Business Add-Ins
Archiving
Copy Control
Contract Management
Expense Management
Inventory True-up
Master Data
Optionality
Load Data Capture
SIT Cockpit
Contract Settlement
Enterprise Services
Archiving
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.
Deletion of Additional Data in Tables

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.
Addition of Data in Tables

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.
Additional Checks
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.

Copy Control
Enhancement for Copy Control

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.

Contract Management (1)
Master Data Enhancement for DPQS, Tol., Optn., RelTrad

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
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.
Validation Checks – Pre-Cancellation checks

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.
Pricing Calcuation
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.

Contract Management (2)
Customer screen – Tolerance
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.
Customer Screen – Related Trades
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

Expense Management
Determine Transaction to be Called
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.

Inventory True-up
Maintenance of Stock - Calculate Unrestricted Quantity of Stock

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.
Maintenance of True-up Amount – Calculate total true-up amount

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.
Cross referencing storage location

READ_3PT_LVL_BY_PLANT_LGRT_PRC method which allows you to cross reference the 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.

Master Data
Tolerance – Validate Tolerance Master Data

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
DPQS – Calculate Average Characteristics

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.
DPQS – Generate Adjustment Text

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
DPQS – Settings for Master Class

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.

Optionality (1)
Maintain Default optionality values at Call-off

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.
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)
GET_OPTIONALITY_DATA_PO (Screen 2050)
GET_OPTIONALITY_DATA_UIS
Maintatin Default optionaltiy values in Trading Contract

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
MAINTAIN_OPTIONALITY_3PT

Optionality (2)
Customer subscreen for custom optionality

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
unit information services (UIS).
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
Optionality checks and calculation at Call-off, Application and Settlement

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

Load Data Capture (1)
Process User-Defined Add-On Tabs for LDC screens
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.

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
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.

Load Data Capture (2)
Process User-Defined Fields for LDC Event Business Logic
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.
This BAdI is available in the enhancement spot /ACCGO/CMN/ES_UIS.
Process User-Defined Fields for LDC Event UI Layer
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.
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.
This BAdI belongs to the enhancement spot /ACCGO/CMN/ES_UIS.

Orchestration Framework
Batch Management Handling
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
Movement Type Posting during SIT
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..

SIT Cockpit
Enhancement of ALV view for SIT cockpit
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.
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
This is a single-use BAdI and is available in enhancement spot /ACCGO/CMN_ES_SIT_CCKPT_ENH_UI.

Contract Application - Call-Off
Call-Off UI Layer
This Business Add-In (BAdI) is used to add or change UI display during call-off from Sales Order/Purchase Order.
• CHANGE_SCHEDULE_TEXT_SO
• CHANGE_SCHEDULE_TEXT_PO
• CHANGE_PROPOSED_CO_FCAT
This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_CALL_OFF.
Call-Off Business Layer
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.
• CHANGE_IMPLICIT_OPT_SO
• CHANGE_IMPLICIT_OPT_PO
• COPY_CONTRACT_TO_SO
• COPY_CONTRACT_TO_PO
This BAdI is available in the enhancement spot /ACCGO/CMN_ES_CAS_CALL_OFF.
Settings during Business rules evaluation
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.

Contract Application - Application Document
Average Calculation for Characteristics

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.
Group Application documents

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.
Application Document Business Layer

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

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

This BAdI enables the addition of customer specific sub-screens in the Application Document.
Comingled process
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).

Contract Application - Application Document
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.
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.

Contract Application - Application Process (1)
Return Process for Contract Application

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.
This BAdI belongs to the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS
DPQS Evaluation
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.
This BAdI belongs to the enhancement spot /ACCGO/CMN_ES_CAS_APPL_PROCESS.
Application Rules Evaluation

This BADI is used to change the inputs to the BRF+ function prior to execution.
PRE_RULES_EVALN.
Application Process Save

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

Pricing Trading Contract Validation Framework

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
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.
Read Weights and Analysis Details

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.
Calculate Derived Categories

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
NRM : Normalization

DPQS Material Schedule

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
Material Determination
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
• 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.

Contract Settlement (1)
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
• 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
This is a single-use BAdI and is available in enhancement spot: /ACCGO/CMN_ES_CAS_STL_DOC.

Contract Settlement (2)
Additional Fields for Event Registry
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
• RETRIEVE_EVTREG_BL
• UPDATE_FOR_TRADE_REALIZATION
Requirements
You have added the additional fields to the respective table and structure.
This is a single-use BAdI and is available in enhancement spot: /ACCGO/CAS_ES_REVREC.

Enterprise Services (1)
Goods Movement Call

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.
Goods Movement Call via Contract Request Out

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.

Enterprise Services (2)
Asynchronous Response – Inbound to SAP
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.
CALL_PROXY (Call Proxy Class)
You can use this BAdI method to call the proxy class objects and the methods.
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.
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.

Content

Country Specific Settings -- Brazil
Contract Settlement
Automatic Invoice
Invoice Type
Reversal Scenario
Invoice Verification
Expense Management
Intracompany
Enhancements using Business Add-Ins

Contract 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:
2. Enter the required details.
3. Save entry.

Contract Settlement – Search Hierarchy for Invoice Type
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
To determine selection sequence for settlement document types, proceed as follows:
2. Enter required details.
3. Save the entry.

Contract Settlement - Reversal Scenario
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:
2. Enter the required details in the following fields:
Rev. Scen. (reversal scenario definition)
Class/Interface
Reversal Parameter
3. Save entry.

Expense Management – Relevancy of ABD Billing Type (1)
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.
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.

Expense Management – Relevancy of ABD Billing Type (2)

Expense Management – ABD Billing document type and Sales order type
Use
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
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..
Expense Management – ABD Expense Mapping
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
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.

Intracompany
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.
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

Enhancement / Business Add-Ins
Enhancements for Settlement Brazil
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
• Determine Selection Sequence for Settlement Invoice Types
This BAdI contains the method CHANGE_AUTO_INVOICE_DATA - Change BAPI Incoming Invoice data
for automatic incoming

ACM Configuration Training

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACM Configuration Training

Uploaded by

Copyright:

Available Formats

ACM Configuration Training

May 06-10 2013 – São Paulo

© 2013 SAP AG. All rights reserved. Internal 2

Activate Switch for Systems Integration

For additional details, please refer to SAP Note 1773636

© 2013 SAP AG. All rights reserved. Internal 4

© 2013 SAP AG. All rights reserved. Internal 5

Define Quantity Types

© 2013 SAP AG. All rights reserved. Internal 6

Define Quantity Profiles

Define Quantity Types for Quantity Profile

Assignment of Quantity Profiles to TC Types

© 2013 SAP AG. All rights reserved. Internal 8

This configuration defines what ACM-specific tabs appear in the GTM

© 2013 SAP AG. All rights reserved. Internal 9

© 2013 SAP AG. All rights reserved. Internal 10

Tab groups are assigned to business data by:

© 2013 SAP AG. All rights reserved. Internal 11

© 2013 SAP AG. All rights reserved. Internal 12

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

© 2013 SAP AG. All rights reserved. Internal 13

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

© 2013 SAP AG. All rights reserved. Internal 14

© 2013 SAP AG. All rights reserved. Internal 15

© 2013 SAP AG. All rights reserved. Internal 16

© 2013 SAP AG. All rights reserved. Internal 17

© 2013 SAP AG. All rights reserved. Internal 18

© 2013 SAP AG. All rights reserved. Internal 19

© 2013 SAP AG. All rights reserved. Internal 20

© 2013 SAP AG. All rights reserved. Internal 21

© 2013 SAP AG. All rights reserved. Internal 22

© 2013 SAP AG. All rights reserved. Internal 23

© 2013 SAP AG. All rights reserved. Internal 24

© 2013 SAP AG. All rights reserved. Internal 26

© 2013 SAP AG. All rights reserved. Internal 27

© 2013 SAP AG. All rights reserved. Internal 28

© 2013 SAP AG. All rights reserved. Internal 29

© 2013 SAP AG. All rights reserved. Internal 30

Assign Pricing Aspect to Pricing Aspect Type

Maintain Number range for DPQS

Maintain DPQS Parameters

Maintain Rounding Parameters for Tiered Prorated

Assign Value Schedule to TSW Location

© 2013 SAP AG. All rights reserved. Internal 31

© 2013 SAP AG. All rights reserved. Internal 32

© 2013 SAP AG. All rights reserved. Internal 33

© 2013 SAP AG. All rights reserved. Internal 35

© 2013 SAP AG. All rights reserved. Internal 36

© 2013 SAP AG. All rights reserved. Internal 37

© 2013 SAP AG. All rights reserved. Internal 38

© 2013 SAP AG. All rights reserved. Internal 39

Code Code for Parent Implied Hierarchy Origin/Destination LDC Certification

© 2013 SAP AG. All rights reserved. Internal 40

© 2013 SAP AG. All rights reserved. Internal 41

© 2013 SAP AG. All rights reserved. Internal 42

© 2013 SAP AG. All rights reserved. Internal 43

© 2013 SAP AG. All rights reserved. Internal 44

© 2013 SAP AG. All rights reserved. Internal 45

© 2013 SAP AG. All rights reserved. Internal 46

© 2013 SAP AG. All rights reserved. Internal 47

© 2013 SAP AG. All rights reserved. Internal 48

Maintain Number Range for LDC

© 2013 SAP AG. All rights reserved. Internal 49

© 2013 SAP AG. All rights reserved. Internal 50