master guide for acm
TRANSCRIPT
Master Guide SAP® Agricultural Contract Management 1.0
Target Audience Consultants Administrators Others
Public Document version 1.2 – 5/16/2013
Master Guide SAP Agricultural Contract Management
2 May 2013
History of Changes The Master Guide is regularly updated in SAP Service Marketplace at http://service.sap.com/instguides.
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation.
The following table provides an overview of the most important changes that were made in the latest versions.
Master Guide Version Important Changes
1.00 (November 7, 2012) First Document Release
1.1 (February 11, 2013) Updated for SP01 Release
1.2 (May 16, 2013) Updated for Sizing Information
Master Guide for SAP Agricultural Contract Management
May 2013 3
Contents History of Changes ........................................................................... 2
1 Getting Started ................................................................................ 4
1.1 About this Document .................................................................. 4 1.2 Related Information .................................................................... 6
1.2.1 Planning Information .............................................................................. 6 1.2.2 Further Useful Links ............................................................................... 6 1.2.3 Related Master Guides ........................................................................... 7 1.2.4 Related Operations Information............................................................ 7
1.3 Important SAP Notes .................................................................. 7
2 SAP Agricultural Contract Management Overview ..................... 8
2.1 Software Units of Agricultural Contract Management ................ 8 2.2 Software Component Matrix ....................................................... 8 2.3 System Landscape...................................................................... 9 2.4. Overall Implementation Sequence ............................................10
3 Business Scenarios of SAP Agricultural Contract Management...................................................................................... 12
3.1 Third Party Purchase .................................................................12 3.2 Third Party Sale..........................................................................12 3.3 Intercompany or Intracompany Trade .......................................13 3.4 Back-to-Back Trade ...................................................................13 3.5 Spot Purchase............................................................................14 3.6 Commingled Stock Management ...............................................14 3.7 Processing Washouts and Circles.............................................15
4 Solution-Wide Topics ................................................................... 16
4.1 Prerequisites for Using this Solution ........................................16 4.2 Support Component...................................................................16 4.3 Customizing ...............................................................................16
5 Security Considerations ............................................................... 17
5.1 Fundamental Security Guides ...................................................17 5.2 Authorization Objects ................................................................17
6 References ..................................................................................... 22
7 Media List ....................................................................................... 23
8 Release Availability Information ................................................. 24
9 The Main SAP Documentation Types ......................................... 25
1 Getting Started
1.1 About this Document
4 May 2013
1 Getting Started 1.1 About this Document Purpose This Master Guide is the central starting point for the technical implementation of SAP Agricultural Contract Management. You can find cross-scenario implementation information as well as scenario-specific information in this guide.
The central starting point for the technical upgrade of your SAP application/solution is the Upgrade Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/instguides.
Use the Master Guide to get an overview of SAP Agricultural Contract Management, its software units, and its scenarios from a technical perspective. The Master Guide is a planning tool that helps you to design your system landscape. It refers you to the required detailed documentation, mainly:
Installation guides for single software units
SAP Notes
Configuration documentation
SAP Library documentation
For a general overview of the available SAP documentation, see The Main SAP Documentation Types.
The Master Guide consists of the following main sections:
Section 1. Getting Started explains how to use this document and provides related information (documentation and SAP notes) that is crucial for installation and upgrade.
Section 2. SAP Agricultural Contract Management Overview introduces the SAP Agricultural Contract Management and its installable components. It also presents the solution component matrix and the system landscape, and provides the overall implementation sequence.
Section 3. Business Scenarios of SAP Agricultural Contracts Management contains information about the supported business scenario and business processes. This section also provides links to the relevant configuration documentation, which is provided in SAP Solution Manager.
Section 4. Solution-Wide Topics provides the prerequisites for using the application along with the support components.
Section 5. Security Considerations provides security related information for SAP Agricultural Contract Management.
Section 6. References provides the list of documents and notes relevant for the smooth running of the application.
Section 7. Media List provides information about the data carriers along with the software components contained within.
Section 8. Release Availability Information provides information about the available software releases and the required software for SAP Agricultural Contract Management.
Section 9. The Main SAP Documentation Types provides information about the overall documentation concept for SAP systems.
1 Getting Started
1.1 About this Document
May 2013 5
You can find the most current information about the technical implementation of SAP Agricultural Contract Management and the latest installation and configuration guides on SAP Service Marketplace at http://service.sap.com/instguides. We strongly recommend that you use the documents available here. The guides are regularly updated.
Constraints The business scenarios that are presented here serve as examples of how you can use
SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Ensure to check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.
This Master Guide primarily discusses the overall technical implementation of SAP Agricultural Contract Management, rather than its subordinate components. This means that additional software dependencies might exist without being mentioned explicitly in this document. You can find more information on component-specific software dependencies in the corresponding installation guides.
1 Getting Started
1.2 Related Information
6 May 2013
1.2 Related Information 1.2.1 Planning Information For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:
Content Location on SAP Service Marketplace
Latest versions of installation and upgrade guides
http://service.sap.com/instguides Focused Business Solutions SAP Agricultural Contract Management
Application information and the collection of function- and process-related information about SAP Agricultural Contract Management.
http://help.sap.com SAP Business Suite SAP ERP Add-Ons SAP Agricultural Contract Management.
SAP Business Maps - information about applications and business scenarios
http://service.sap.com/businessmaps
Sizing, calculation of hardware requirements - such as CPU, disk and memory resource - with the Quick Sizer tool.
This application is an enhancement to standard EA-GLTRADE 606 (SAP Global Trade Management).
The hardware sizing depends on the number of contracts processed in the GTM standard plus an additional factor due to background document generation and SAP Agricultural Contract Management documents.
Sizing should be based on the foundation defined for GTM multiplied by a factor of 1.3.
http://service.sap.com/quicksizer -> Sizing Guidelines -> SAP ERP -> SAP Global Trade Management.
Released platforms and technology-related topics such as maintenance strategies and language support
http://service.sap.com/platforms
To access the Platform Availability Matrix directly, enter http://service.sap.com/pam.
Network security http://service.sap.com/securityguide
High Availability http://www.sdn.sap.com/irj/sdn/ha
Performance http://service.sap.com/performance
Information about Support Package Stacks, latest software versions and patch level requirements
http://service.sap.com/sp-stacks
Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n
1.2.2 Further Useful Links The following table lists further useful links on SAP Service Marketplace:
1 Getting Started
1.3 Important SAP Notes
May 2013 7
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/message
SAP Notes search http://service.sap.com/notes
SAP Software Distribution Center (software download and ordering of software)
http://service.sap.com/swdc
SAP Online Knowledge Products (OKPs) – role-specific Learning Maps
http://service.sap.com/rkt
1.2.3 Related Master Guides This Master Guide is based on Master Guides for cross-industry applications. You can find more information about the relevant applications in the following documents:
Title Location
SAP ERP 6.0 Master Guide
http://service.sap.com/instguides SAP Business Suite Applications SAP
ERP SAP ERP 6.0 Planning
1.2.4 Related Operations Information The operations information for SAP Agricultural Contract Management is included in the Operations Information section of the Application Help. For more information, see the SAP Help Portal at http://help.sap.com SAP Business Suite SAP ERP Add-Ons SAP Agricultural Contract Management.
1.3 Important SAP Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes.
SAP Note Number Title Description
1773636 Release Strategy for ABAP Add-On ACCGO
See this note for information about planning the installation and upgrade of the SAP Agricultural Contract Management.
2 SAP Agricultural Contract Management Overview
2.1 Software Units of Agricultural Contract Management
8 May 2013
2 SAP Agricultural Contract Management Overview SAP Agricultural Contract Management enables commodity traders to capture and manage these complex commodity contracts and related processes. It is an end-to-end solution that supports the full contract life-cycle, including the capture of the contract terms, the logistical processing, and the final settlement and closure.
To use this solution, the corporate customers must install SAP Agricultural Contract Management as an add-on to their SAP ERP system. Additionally, SAP Global Trade Management and SAP Trader's and Scheduler's Workbench must be active.
SAP Agricultural Contract Management is also fully integrated with SAP Financial Accounting.
2.1 Software Units of Agricultural Contract Management SAP Agricultural Contract Management consists of the following software units:
SAP ERP 6.0 SAP Agricultural Contract Management is an add-on on SAP ERP 6.0 Enhancement Package 6.
SAP PI SAP PI system is an optional system. It can be used to integrate SAP ERP system with a Third Party trading system.
Third Party Trading System This is an optional system and can be integrated to SAP ERP system through SAP PI system.
2.2 Software Component Matrix This section provides an overview of which business scenario of SAP Agricultural Contract Management uses which software unit.
For the latest component version and patch level requirements, see SAP Note 1773636.
This Master Guide provides just one way to implement each business scenario. For other ways to implement business scenarios, see the Scenario & Process Component List in SAP Service Marketplace at http://service.sap.com/scl. The Scenario & Process Component List helps you to find realization alternatives for SAP solutions, business scenarios and processes. It shows you which application components are needed to realize a business scenario or process.
2 SAP Agricultural Contract Management Overview
2.3 System Landscape
May 2013 9
Business Scenario
Software Units
Key: X = mandatory (O) = optional
SAP ERP 6.0
SAP PI Third Party Integration
Third Party Purchase
X (O) (O)
Third Party Sale X (O) (O)
Intercompany or Intracompany Trade
X (O) (O)
Back-to-back Trade
X (O) (O)
Spot Purchase X (O) (O)
Commingled Stock Management
X (O) (O)
Processing Washouts and Circles
X (O) (O)
Inventory True-up X X X
2.3 System Landscape The following technical architecture model illustrates the landscape of SAP Agricultural Contract Management:
2 SAP Agricultural Contract Management Overview
2.4. Overall Implementation Sequence
10 May 2013
ContractCapture
SAP ERP
Revenuerecognition
Thi rdparty
tradingsystem
Quality schedules
Tolerance schedules
Value tables
SAP PI
Commodity contract CAS
Expense management
Inventory update framework
Contract capture UI
Pricing TC Logistic TC and Order
Application
Data capture forloads (LDC)
Standard doc generation (OF)
Material determination
Appl ication doc generation
Manual or rules-based application
Spot contractrequest
Applicationmessage
Standard order creation
Price component
Quality requirements
Contract options
Tolerance data
Planned and unplanned expenses
Call offprocess
Contract settlement
Configuration/master data
Pricing distribution usingpricing rules
Standard bil ling/invoicing
Immediate updates/periodic
updates
Inventory update rules\configuration
Repository for provisional prices
Planned and unplanned expenses
Declared contract options
Vendor billing document
Agency business document
R RR
R
R
R
R
R
R
R R
R
R
R
R
R
R
R
Figure 1: Technical Architecture Model for SAP Agricultural Contract Management
SAP Agricultural Contract Management is an add-on to SAP ERP 6.0. Enhancement Package 6 or higher with business function GTM and iTSW activated.
SAP PI and Third Party trading system are optional systems. Therefore, the integration between these systems is needed only if some trading functionalities are carried out in the Third Party trading system.
We strongly recommend that you use a minimal system landscape for test and demo purposes only. For performance, scalability, high availability, and security reasons, do not use a minimal system landscape as your production landscape.
2.4. Overall Implementation Sequence
2 SAP Agricultural Contract Management Overview
2.4. Overall Implementation Sequence
May 2013 11
SAP Agricultural Contract Management requires the following to be active in the customer system along with a minimum level of support packs:
ERP 6.0 with EhP 6
GTM
iTSW
In addition, other external integration for pricing, position management, and analytics can be integrated to effectively use features supported by this solution. These can include Third Party systems or other SAP products, such as BI, PI, and so on.
Use of SAP Agricultural Contract Management with a Third Party trading system requires custom development for the Third Party trading application and potentially for the integration messages and to and from SAP and their evaluation in SAP. The integration delivered with the FBS is generic and not specific to a particular Third Party trading application.
Purpose The following table describes the overall installation sequence for SAP Agricultural Contract Management. This table contains all available software units.
For the latest component version and patch level requirements, see http://service.sap.com/sp-stacks.
Process Implementation Sequence
Step Action [Required Documentation]
Remarks/Subsequent Steps
1 Complete the implementation of your ECC system in accordance with your business requirement.
2 Installation of SAP Agricultural Contract Management Add-on
For installation details, see SAP Note 1773636 - Release Strategy for ABAP Add-On ACCGO.
3 Complete the customizing of SAP Agricultural Contract Management
For more information, see Customizing (transaction code SPRO) under SAP Customizing Implementation Guide Logistics-General Global Trade Management Agricultural Contract Management.
4 Integration with SAP PI and Third Party Trading system
This is an optional step and depends upon the usage of Third Party system.
Integration can be implemented only after detailed evaluation of the Third Party application and further custom development.
3 Business Scenarios of SAP Agricultural Contract Management
12 May 2013
3 Business Scenarios of SAP Agricultural Contract Management
3.1 Third Party Purchase Overview You use this business scenario for commodity contract involving the SAP Agricultural Contract Management implementer (the firm) and counterparty, such as a farmer, in a situation where the firm purchases a commodity from the farmer.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Third Party Purchase:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.2 Third Party Sale Overview You use this business scenario for a commodity contract involving the firm and counterparty, such as a food processor, in which the firm sells a commodity to the food processor.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Third Party Sale:
3 Business Scenarios of SAP Agricultural Contract Management
May 2013 13
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.3 Intercompany or Intracompany Trade Overview You use the business scenario intercompany trade when entities within the firm purchase and sell commodities to one another.
You use the business scenario intracompany trade when entities within in the same organizational structure purchase and sell commodities to one another with the requirement that their commodity positions are managed and valued separately.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Intercompany or Intracompany Trade:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.4 Back-to-Back Trade Overview You use this business scenario when the firm sells a commodity that is not yet in its physical possession. This scenario requires the ability to relate the movements of the purchase portion of the transaction to the sale portion of the transaction.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
3 Business Scenarios of SAP Agricultural Contract Management
14 May 2013
Further Information The following documents provide more information about Back-to-Back Trade:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.5 Spot Purchase Overview You use this business scenario when the firm receives a commodity from counterparty, but does not have a relevant existing purchase contract with the counterparty to which to apply the receipt. This scenario requires a commodity contract to be generated that matches the conditions of the received goods.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Spot Purchase:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.6 Commingled Stock Management Overview You use this business scenario when the firm receives a commodity from counterparty for storage at the firm’s location for a fee. This obligated quantity is stored in the same location as the firm’s own inventory, where it gets commingled with the firm’s commodities. Therefore, counterparty’s quantity‘s grade and quality characteristics can become indistinguishable.
To ensure that the obligated quantity can be restored to the counterparty in the same or better condition, or be valued for purchase, its quality characteristics must be measured prior to being stored.
Technical System Landscape For more information, see the section System Landscape.
Software Units
3 Business Scenarios of SAP Agricultural Contract Management
May 2013 15
For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Commingled Stock Management:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
3.7 Processing Washouts and Circles Overview You use this business scenario when the firm is engaged in both purchase and sale contract with the same counterparty for the same commodity. Therefore, the firm can settle a portion of the contracted quantity financially, without moving goods.
The scenario also enables you to handle variations, such as, circles and strings.
Technical System Landscape For more information, see the section System Landscape.
Software Units For more information, see the section Software Component Matrix.
Implementation Sequence For more information, see the section Overall Implementation Sequence.
Further Information The following documents provide more information about Processing Washouts and Circles:
Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
4 Solution-Wide Topics
16 May 2013
4 Solution-Wide Topics
4.1 Prerequisites for Using this Solution For more information about prerequisites, see the installation note, the operations information, and the solution manager documentation. You can find the required links in the section References.
4.2 Support Component To get support for SAP Agricultural Contract Management, create a CSS ticket in one of the following components.
Component Description
LO-AGR SAP Agricultural Contract Management
LO-AGR-CC Commodity Contracts, Expenses, Basic Functions
LO-AGR-STL Agency Business Document, Settlement, Revenue Recognition
LO-AGR-3PT 3rd Party Integration
LO-AGR-APP Application and Call Off
LO-AGR-LDC Load Data Capture and Orchestration Framework
LO-AGR-LOC-BR Brazil Localization
4.3 Customizing For more information, see Customizing for Agricultural Contract Management under SAP Customizing Implementation Guide Logistics – General Global Trade Management Agricultural Contract Management.
5 Security Considerations
May 2013 17
5 Security Considerations This section provides an overview of the security considerations that are specific to SAP Agricultural Contract Management. SAP Agricultural Contract Management is built on a SAP ERP 6.0 Enhancement Pack 6 system. Therefore, the corresponding security settings also apply to SAP Agricultural Contract Management.
5.1 Fundamental Security Guides For a complete list of the available SAP security guides, see SAP Security Guides on SAP Service Marketplace at http://service.sap.com/securityguide.
Additional Information For more information about specific security topics, see the following locations on SAP Service Marketplace as shown in the table below: Content Location
Security http://service.sap.com/security
Security Guides http://service.sap.com/securityguide
Released Platforms http://service.sap.com/platforms
Network Security http://service.sap.com/securityguide
Infrastructure Security http://service.sap.com/securityguide
SAP Solution Manager http://service.sap.com/solutionmanager
5.2 Authorization Objects Authorization Object
Field Name(Heading) Value Description
/ACCGO/APS ACTVT (Activity)
01 - Create or generate
02 - Change
03 - Display
06 - Delete
Application Archiving
/ACCGO/ASQ ACTVT (Activity)
/ACCGO/RID (Rule ID)
01 - Create or generate
02 - Change
03 - Display
04 - Print, edit messages
06 - Delete
Application Rules - Access Sequence Data
/ACCGO/ACR ACTVT (Activity)
/ACCGO/RID (Rule ID)
01 - Create or generate
02 - Change
03 - Display
Application Rules - Condition Records
5 Security Considerations
18 May 2013
04 - Print, edit messages
06 - Delete
/ACCGO/UI /ACCGO/NOD (Tree Control: Node Key)
/ACCGO/LEF (Tree Control: Leaf Key)
User Common UI Node Access
/ACCGO/SPM /ACCGO/APL (Application Activites)
/ACCGO/DTY (ApplicationDocument Type)
WERKS (Plant)
User Contract Application Spot Monitor
/ACCGO/STL BUKRS (Company Code)
TCTYP (Trading Contract: Trading Contract Type)
WERKS (Plant)
PRCTR (Profit Center)
VKORG (Sales Organization)
VTWEG (Distribution Channel)
SPART (Division)
EKORG (Purchasing Organization)
/ACCGO/SID (Side)
/ACCGO/STL (Settlement Activities for Authorization Check)
01 - Create/Generate Settlement
02 - Change / Adjust Settlement
03 - Display Settlement
04 - Release Settlement
05 - Approve Settlement
06 - Reverse Settlement
07 - Reject Settlement
08 - Cancel Settlement
09 - Price Override
10 - Release Settlement (Non-Self Billed Invoice)
11 - Negotiate DPQS in DPQS
12 -.Payment Split in Settlement
13 -.Add/Refresh Lien
14.- Deactivate Lien in Settlement
Contract Settlement
5 Security Considerations
May 2013 19
/ACCGO/GDC ACTVT (Activity) 01 - Create or generate
02 - Change
03 - Display
Global Derived Characteristics
/ACCGO/LIN
ACTVT (Activity) 01 - Create or generate
02 - Change
03 - Display
06 - Delete
Lien
/ACCGO/UIS WERKS (Plant)
/ACCGO/UIS (LDC Activity)
01 - Maintain Event Details
02 - Maintain Weights
03 - Maintain Analysis
04 - Release UIS
05 - Display Event Details
06 - Display Weights
07 - Display Analysis
08 - Display Release UIS
Load Data Capture
/ACCGO/NEY EKORG (Purchasing Organization)
PRCTR (Profit Center)
WERKS (Plant)
VKORG (Sales Organization)
VTWEG (Distribution Channel)
SPART (Division)
BUKRS (Company Code)
/ACCGO/DTY (Application Document Type)
/ACCGO/APL (Application Activites)
/ACCGO/SID (Side)
Application Document Type
Application Activites
Side
Manual Application Workcenter - Common Fields
/ACCGO/NEG /ACCGO/NKY (Tree Control: Node Key)
ACTVT (Activity)
01 - Create or generate
02 - Change
03 - Display
Manual Application Workcenter - Node Key
/ACCGO/NSS WERKS (Plant)
BUKRS (Company Code)
01 - Create Washout
Non-Standard Settlement
5 Security Considerations
20 May 2013
/ACCGO/SID (Side)
/ACCGO/NSA (Non-Standard Settlement Activities)
02 - Create Circle
03 - Create Cancellation
04 - Display Washout/Circle
05 - Create Underfill
/ACCGO/DIS ACTVT (Activity) 16 - Execute
Online Pricing Distributions
/ACCGO/OE ACTVT (Activity) 02 - Change
03 - Display
Orchestration Framework and Back-to-Back
/ACCGO/P2S ACTVT (Activity) 01 - Create or generate
16 - Execute
Purchase to Storage
/ACCGO/RRP BUKRS (Company Code)
PRCTR (Profit Center)
VKORG (Sales Organization)
EKORG (Purchasing Organization)
ACTVT (Activity)
SPART (Division)
VTWEG (Distribution Channel)
EKGRP (Purchasing Group)
03 - Display
10 - Post
Revenue Recognition and Purchase Realization
/ACCGO/UIC ACTVT (Activity) 01- W2 Set Up Load Data Capture
/ACCGO/SC WERKS (Plant)
BUKRS (Company Code)
/ACCGO/SCT (Settlement Activity Type - String/Circle)
/ACCGO/SCA (Activity for String or Circle in Settlement)
/ACCGO/SID (Side)
Activity
01 - Create
02 - Change
03 - Display
Settlement Type
01 - String
02 - Circle
String/Circle Authorization for Standard Settlement
/ACCGO/TOL ACTVT (Activity) 01 - Create or generate
02 - Change
03 - Display
Tolerance Schedule
/ACCGO/TSD /ACCGO/MAT (Material Number) 01 - Create or Trader's and
5 Security Considerations
May 2013 21
WERKS (Plant)
ACTVT (Activity)
generate
02 - Change
03 - Display
06 - Delete
Seller's Database
/ACCGO/VAL ACTVT (Activity) 01 - Create or generate
02 - Change
03 - Display
Value Schedule
/ACCGO/ASG
ACTVT (Activity)
/ACCGO/LOC (TSW Location)
01 - Create or generate
02 - Change
03 - Display
Value Schedule Assignment to TSW Location
/ACCGO/VOL ACTVT (Activity)
01 - Create or generate
02 - Change
03 - Display
Volume Schedule
6 References
22 May 2013
6 References List of Documents The following table lists all the documents mentioned in this Master Guide:
Title Where to Find
Application Help See the SAP Help portal at the following location:
http://help.sap.com SAP Business Suite SAP ERP Add-Ons SAP Agricultural Contract Management.
Scenario Documentation See the documentation in SAP Solution Manager.
For more information about SAP Solution Manager, see SAP Service Marketplace at http://service.sap.com/solutionmanager.
Customizing Guide See Customizing for SAP Agricultural Contract Management under SAP Customizing Implementation Guide Logistics – General Global Trade Management
Agricultural Contract Management
List of SAP Notes For more information, see the section Important SAP Notes.
7 Media List
May 2013 23
7 Media List All deliverables for SAP Agricultural Contract Management are shipped electronically and no shipment is made using DVDs (or any similar data carrier medium).
8 Release Availability Information
24 May 2013
8 Release Availability Information For more information about currently available releases for SAP Agricultural Contract Management, and for each release, the SAP standard software required to install and use the solution, see http://www.service.sap.com/fbs/availability.
9 The Main SAP Documentation Types
May 2013 25
9 The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of an SAP solution.
Documentation types in the software life cycle
ImplementationImplementation
Master Guide
ConfigurationDocumentation Release Notes
ComponentInstallation Guide
ComponentUpgrade Guide
Upgrade Master Guide
OperationOperation UpgradeUpgrade
Solution ManagementGuide
Implementation Guide (IMG) Delta and Upgrade IMG
Security Guide
SAP Library
SAPterm
Cross-Phase Documentation SAPterm
SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many definitions and glossary entries in English and German.
Target group:
Relevant for all target groups
Current version:
Located in the SAP Help Portal at help.sap.com Additional Information Glossary (direct Access) or Terminology (available as terminology CD)
In the SAP-System in transaction STERM SAP Library
The SAP Library is a collection of function- and process-oriented documentation for SAP components. The SAP Library also contains the Business Scenario Descriptions.
Target group:
o Consultants
o System administrators
9 The Main SAP Documentation Types
26 May 2013
o Project teams for implementations or upgrades
Current version:
o Located in the SAP Help Portal at help.sap.com
o Also located in the SAP Service Marketplace at service.sap.com/ibc (only the Business Scenario Descriptions)
Implementation Guide (IMG)
The Implementation Guide is a tool for configuring the SAP system to meet customer requirements. Its structure and documentation are component-oriented.
Target group:
o Solution consultants
o Project teams for implementations or upgrades
Current version:
o In the SAP menu of the SAP system under Tools Customizing IMG
Security Guide
The Security Guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This document contains general guidelines and suggestions about system security. Other technologies and individual applications have a Security Guide of their own.
Target group:
o Technology consultants
o Solution consultants
o Project teams for implementations or upgrades
Current version: o Located in the SAP Service Marketplace at service.sap.com/securityguide
Implementation Master Guide
The Master Guide is the starting point for implementing an SAP solution. It lists the required SAP components and third party applications that are required for each Business Scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also offers references to other documents, such as Component Installation Guides and SAP Notes.
Target group:
o Technology consultants
o System administrators
o Project teams for implementations
Current version:
o Located in the SAP Service Marketplace at service.sap.com/instguides
Component Installation Guide
9 The Main SAP Documentation Types
May 2013 27
The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.
Target group:
o Technology consultants
o Project teams for implementations
Current version: o Located in the SAP Service Marketplace at service.sap.com/instguides
Configuration Documentation in SAP Solution Manager
SAP Solution Manager is a tool with various functions, one of its main functions being the configuration of SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as well as documentation. Instead of the configuration documentation in SAP Solution Manager, there may be separate Business Scenario Configuration Guides in the SAP Service Marketplace for earlier shipments of the Business Scenarios.
Target group:
o Solution consultants
o Project teams for implementations
Current version:
o In SAP Solution Manager
o Located in the SAP Service Marketplace at service.sap.com/ibc
Production Operation Solution Operation Guide
The Solution Operation Guide is the starting point for operating an SAP solution. The guide refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. It also refers users to other documents, for example the SAP Library, the Master Guide, and the Component Management Guides.
Target group:
o System administrators
o Technology consultants
o Solution consultants
o Project teams for implementations or upgrades
Current version:
o Located in the SAP Service Marketplace at service.sap.com/instguides
Upgrade Upgrade Master Guide
The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-
9 The Main SAP Documentation Types
28 May 2013
up of an upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAP Notes. Instead of an Upgrade Master Guide, there may be several Business Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the Business Scenarios of an SAP solution.
Target group:
o Technology consultants
o Project teams for upgrades
Current version:
o Located in the SAP Service Marketplace at service.sap.com/instguides
Component Upgrade Guide
The Component Upgrade Guide describes the technical upgrade of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.
Target group:
o Technology consultants
o Project teams for upgrades
Current version:
o Located in the SAP Service Marketplace at service.sap.com/instguides
Release Notes
Release notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs.
Target group:
o Consultants
o Project teams for upgrades
Current version:
o Located in the SAP Service Marketplace at service.sap.com/releasenotes
o In the SAP menu of the SAP system under Help Release information
© Copyright 2013 SAP AG. All rights reserved SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered
trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com
Typographic Conventions Type Style Represents
Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation
Example text Emphasized words or phrases in body text, titles of graphics and tables
EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Icons Icon Meaning
Caution
Example
Note
Recommendation
Syntax