Business Functions

Business Functions Trade SAP ERP 6.0 EHP6

Release 706

AD

DO

NX

.BF

_T

RA

DE

(C) SAP AG ADDONX.BF_TRADE 2

Copyright © Copyright 2011 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, and PowerPoint 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, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. 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. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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.


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.


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.


Business Functions Trade SAP ERP 6.0 EHP6 ............................................... 6

Trade, Commodity Management 5 ............................................................... 6 Trade, Fund Settlement .............................................................................. 10 Trade, Agency Business 5 ......................................................................... 12 Trade, Invoice Forecasting ......................................................................... 15 Retail, Connectivity to F&R 5.2................................................................... 17 Retail, Inbound Promotions 2 ..................................................................... 19


Business Functions Trade SAP ERP 6.0 EHP6

Trade, Commodity Management 5

Technical Data

Technical Name of Business Function ISR_GLT_COMMODITY_5

Type of Business Function Enterprise Business Function

Available From SAP enhancement package 6 for SAP ERP 6.0

Technical Usage Global Trade

Application Component Global Trade (LO-GT)

Required Business Function Trade, Agency Business 5 (ISR_APPL_AGENCY_5)

Trade, Commodity Management 4 (ISR_GLT_COMMODITY_4)

You can use this business function to activate new mid- and back-office functionality with a fully integrated, scalable, and comprehensive solution for sourcing, selling, trading, and logistics processing for all commodities when deployed with a front-end tool. The solution gives you full transparency and control over all aspects of the commodities business by managing trading order processing, commodity positions, and commodity risk control. The enhancement in services enables more alternatives for trading contract processing.

The new functionality provides a rich, scalable, and future-proof SOA interface to enable customers to model customer-specific business scenarios in a reliable and well-defined manner. The unified SOA interface enables a flexible architecture for establishing an integrated platform with other applications.

Integration

Prerequisites

You have installed the following components as of the version mentioned:

Type of Component Component Required for the

Following Features Only

Software Component EA-GLTRADE 606, SAP_APPL 606

XI/ESR Content EA-GLTRADE 606 with namespace http://sap.com/XI/EA-GLTRADE/Global

After activating this business function, you make the Customizing settings under:

Logistics - General Global Trade Management Trading Contract

Logistics - General Global Trade Management Expenses


Logistics - General Global Trade Management Pricing

Logistics - General Agency Business

For commodity pricing and differential invoicing on the SD and/or MM side you have to activate business functions Contract-to-Cash for Commodities (LOG_SD_COMMODITY) and/or Procure-to-Pay for Commodities (LOG_MM_COMMODITY). If you want to use the invoice forecasting worklist (IFW) in this context you have to activate business function Trade, Invoice Forecasting (ISR_GLT_IFW).

Features

Pricing and Payment Events (PPE) Within Trading Contract Processing

Pricing and Payment Events functionality provides a means to add additional date-related information that can be used in pricing, invoicing, and billing to the trading contract and its successor documents. Dates can be entered as planned or actual dates that refer to a business event in the logistics process. Typical examples for such business events are title transfer, arrival, load, discharge, invoice-related dates, and payment-related dates.

SAP delivers a set of pre-defined business events within switched business configuration sets that are automatically activated via this business function.

Customers can add their own event definitions in the Customizing for Pricing and Payment Events.

Enhanced Expense Management for Agri Processes

Planned expenses on trading contract for price fixing level can be used as planned expenses on trading contract for load level if the trading contract for load is assigned to trading contracts for price fixing.

The planned cost is show automatically within expense settlement processing. Therefore, no manual steps are necessary to calculate the correct planned expenses. As a consequence, all planned process costs are shown to the user and therefore all costs can be covered easily. In addition, the profit or the margin of the business process can be influenced and tracked in a transparent way.

Multi Level Bill of Material (BOM) Explosion Within Trading Contract Application

For sales only processes, the trading contract application supports multi-level sales BOMs on contract item level. Basically, the trading contract application now provides the same functionality as the sales order with regards to BOM explosion.

The user can maintain multi-level BOM on trading contract level to fulfill customer needs.

The outbound messages of the A2A and A2X SOA services for the business object Trading Order provide the information about the exploded bill of material.

Agricultural Processes based on Trading Contract Application

Note

SAP provides only a foundation for agri processes that can be used in customer development projects. For more information see SAP note 1617823.

New UI: A new user interface to maintain commodity items and assignments was developed for trading contracts for price fixing, trading contracts for load and for trading contracts load planning.

A new set of trading contracts is defined to support the basic Agri processes within Commodity Management.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1617823&_NLANG=en&_NVERS=0


To store the contractual information concerning pricing information a new kind of trading contract was defined the trading contract for price fixing. This document is able to store the pricing information for soft commodities. To drive the load processes two new kinds of trading contracts were developed.

The trading contract for load processing also consumes the pricing information of a trading contract for price fixing.

The trading contract for load planning is used to define the contractual data, for example, for a season or as a long term living contract and to consume the pricing information of a trading contract for price fixing. The trading contract for load planning is used to make call off’s for the load processing, which includes the transfer of the pricing information, too.

The outbound messages of the A2A and A2X SOA services for the business object Trading Order provide the information about the kind of trading contracts.

Creation and Cancellation Processes Within Trading Contract Application

Supports the automatic generation or cancellation of entire predefined business processes within one step based on trading contracts.

One aspect of this feature is automatic generation of documents to reduce human errors. Another aspect is a reduction of manual processes based on predefined process steps.

Reduce manual effort to generate or to cancel follow-on documents of a trading contract if the follow-on document processing can be done automatically based on business rules.

Create Batches Within Trading Contract Application

UI: On trading contract level, the UI has been enhanced to allow the user to jump to the batch maintenance application to define new batches out of the trading contract application.

Within the trading contract application, you can now create batches and maintain their characteristics.

On trading contract level, you can create processing batches and their characteristics that are used within the pricing application. The definition of batches on trading contract level prevents the user from making mistakes or to miss maintaining important data at contract entry.

Document Flow on Item Level for Trading Contract Processes

New UI: On item level of a trading contract as well as on item level of the follow-on documents of a trading contract, a new user interface is provided to show details of the actual item based on the JNet application process. Besides document-flow-specific data, the JNet Graphic provides the assignments network of the commodity items.

There are the following key capabilities:

To provide process information to the user and provide assignment information about the commodity items and assigned documents

To be up-to-date with the underlying business process

To see the process network on a graphical interface.

Incoterms within Expense Management

Based on a new Customizing setting, Agency Business applications provide a new feature to maintain Incoterms on header and on item level of a document. If this new feature is activated for a certain expense management document type the Incoterms are copied automatically from the underlying document, for example, outbound delivery to the expense document.


Furthermore, it is possible to maintain Incoterms manually if different Incoterms are foreseen for the actual expense document.

Settle Invoice Requests for Energy Business

With Contract Settlement for Energy Business, you can run an integrated commodity management scenario to trade power, gas, and similar energy products that do not require dedicated logistics follow-on processing. In addition you can utilize a third-party application optimized for front- and mid-office activities to handle contracts and related settlement data, while using Global Trade Management for contract settlement and invoicing. SOA A2A services are used for the communication between the applications within a company.

Streamlined contract settlement of invoice request in energy business without the need for dedicated logistics follow-on processing.

Application Log for Trading Contract Release Processing

A new application log on trading contract header level will provide the capability to analyze the cause of a release error. The application log is stored on the database and contains the messages of the release process.


Trade, Fund Settlement

Technical Data

Technical Name of Business Function ISR_GLT_VENDOR_FUND




Application Component Global Trade(LO-GT)

Required Business Function Trade, Agency Business 5(ISR_APPL_AGENCY_5)

You can use this business function to perform condition contract-related settlement, based on a revenue table in SAP ERP that can be filled by any data sources, even external ones.

Prerequisites


Type of Component Component Required for the Following Features Only

Software Component EA-GLTRADE 606

After activating this business function, you make the following settings in Customizing:

Basic settings of the settlement document in Customizing for Agency Business.

Other prerequisites are to fill the revenue table, for example, by updating and aggregating the documents in SAP BW, enhancing the contract type with the required settlement type, and maintaining the relevant condition tables in Customizing.

Features

The following feature is available within the Trade, Fund Settlement business function:

Condition Contract-Related Settlement

Condition contract-related settlement provides a means to settle any document types or combinations of document types, for example, purchase orders, deliveries, settlement documents, or POS data. Cumulated statistical revenue data can be used for larger document volumes.

The advantages of this form of settlement are flexibility and independence from the data source desired, and high performance when processing mass data, which can be processed with aggregated data and only one settlement document need be created for each condition contract.

Multiple documents can be created for each condition contract.

Contract settlements can also be made periodically without revenue tables.

Example


A retailer agrees on a rebate scale with his or her vendors on the basis of sales revenue. He or she specifies conditions in a condition contract. The retailer’s POS data is used as a revenue basis. Fortnightly invoicing is intended for this vendor and exactly one chargeback document is created for the vendor


Trade, Agency Business 5

Technical Data

Technical Name of Business Function ISR_APPL_AGENCY_5



Technical Usage Central Application

Application Component Agency Business (LO-AB)

Required Business Function Trade, Agency Business (ISR_RET_AGENCY_4)

You can use this business function to implement new business models for agency business processes, support allocation of any types of expenses, improve cost transparency, and increase process flexibility and efficiency. Furthermore, a new B2B outbound service allows customers and partners to leverage enterprise service-oriented architecture for the exchange of invoices. The following further enhancements in agency business processes increase usability in the modeling of business processes through a unified reporting architecture that enables greater flexibility for end users.

Incoterms

Partner Determination Within Energy Business

ALE Monitor for IDocs from the Agency Business Application

Enterprise Services

Settle Invoice Requests for Energy Business without SD Processing

Deviating Exchange Rate in Customer Company Code

Integration

The new features of this business function are enhancements of the Agency Business component. Agency Business is integrated in SAP’s core application SAP ERP Central Component 6.0 (SAP ECC 6.0) and can be implemented in conjunction with other SAP Industry Add-ons, such as SAP Retail.

Prerequisites



Software Component SAP_APPL 606

SAP Enterprise Services

SAP APPL 606

EA_RETAIL

EA_GLTRADE

Single Settlement Request

Vendor Billing Documents

Expense Settlement



http://sap.com/xi/APPL/Global2

Customer Settlement

To use Incoterms in agency documents, you must do the following:

o Maintain condition records for condition types, for example, in SAP Menu Logistics Materials Management Purchasing Master Data Conditions .

o Activate Incoterms by selecting the Incoterms Active checkbox under Incoterms in Customizing for Logistics – General Agency Business

Billing Billing Document Types .

To use partner determination within energy business, you define settings in Customizing for Logistics - General Agency Business Basic Settings

Determine Partner Determination .

To use Enterprise Services, you have activated the SAP_APPL and EA_RETAIL components. In the case of the specific chargeback process, where invoices are sent out as compensation requests towards the supplier, the EA_GLTRADE component also has to be activated.

To settle invoice requests for energy business without SD processing, you have defined settings in Customizing for Logistics - General in the following locations:

o Agency Business Basic Settings Copy Control

o Agency Business Payment Payment Types


To use this new feature, you must make settings in Customizing for Agency Business Payment Payment Types .

Features

The following features are available within the Trade, Agency Business 5 business function:

Incoterms

Incoterms are automatically copied from the trading contract or its follow-on documents to agency documents, which are created as expense documents. A manual entry or change of Incoterms in the agency documents is also supported.

Partner Determination Within Energy Business

Based on a new Customizing setting, Agency Business applications provide a new feature to maintain partner data on header and on item level of a document. If this new feature is activated for a certain billing type, the partner data can be copied from the vendor and customer master data automatically if defined in Customizing, and you can maintain the partner data manually. The partner data can be copied to the follow-on documents.

ALE Monitor for IDocs from the Agency Business Application

The ALE Monitor enhances the SAP Standard IDoc transaction for Agency Business IDocs for better monitoring, selection, filtering, comparison and testing of IDocs - either in a productive or non-productive environment.


Enterprise Services

These services are targeted to enable the exchange of supplier and customer invoices of B2B and A2A processes.

Settle Invoice Requests for Energy Business without SD Processing

With Contract Settlement for Energy Business, you can run an integrated commodity management scenario to trade power, gas, and similar energy products that do not require dedicated logistics follow-on processing. In addition, you can use a third-party application optimized for front- and mid-office activities to handle contracts and related settlement data, while using Global Trade Management for contract settlement and invoicing. SOA A2A services are used for the communication between the applications within a company. This enables streamlined contract settlement of invoice requests in energy business without the need for dedicated logistics follow-on processing.


In cross-company business, it is possible that the currency of the customer company code deviates from the currency of the vendor company code. In the single settlement request document, you can use the Deviating Exchange Rate in Customer Company Code field on header level to specify an exchange rate for the deviating currencies

On item detail level, a new tab screen is provided to maintain customer account assignment. It is possible to assign separate profit center, and cost elements to the customer instead of using the ones from the vendor side. This works only in combination with the class-based accounting interface that can be set in the billing type and has been available since EhP4.


Trade, Invoice Forecasting

Technical Data

Technical Name of Business Function ISR_GLT_IFW




Application Component Logistics - Agency Business - Invoice Forecasting Worklist (LO-AB-IFW)

Required Business Function Not relevant

You can use this business function to activate IFW (Invoice Forecasting Worklist). This is a new application that you can use to simulate and then track any invoices (both inbound and outbound). It is used by an invoice clerk or accountant working in a commodities trading company.

Invoices can be sent out as soon as a provisional price is known. Incoming invoices can be verified as early as possible and you can simulate expected invoices (due date, amount). Now you have one central application to view all deals that need to be invoiced.

IFW allows the following

Real-time handling of simulated and real invoices

Integration into Commodity Pricing Engine (CPE) for market curves, quotations

Support of third party front-office trades (partner based CPE pricing mode)

The standard delivery of IFW assumes a GTM trading contract (TC) as a source document.

The A2A and A2X SOA services for the business object Trading Order allows a third party to set the IFW relevancy indicator on item level, dependent on Customizing settings.

Prerequisites


Type of Component Component Required for the

Following Features Only

Software Component EA-GLTRADE 606, SAP_APPL 606

XI/ESR Content EA-GLTRADE 606 with namespace http://sap.com/XI/EA-GLTRADE/Global

There is no strong dependency of ISR_GLT_IFW (Trade, Invoice Forecasting) on other business functions. However, all IFW functionality for differential invoicing requires at least one of the two business functions LOG_SD_COMMODITY (Contract-to-Cash for Commodities) and LOG_MM_COMMODITY (Procure-to-Pay for Commodities) ) to be switched on. Those two business functions again depend on business function


LOG_CPE_FA_FE (Logistics, Commodity Pricing Engine in SD and MM). If the integration into PPE (Pricing and Payment Events) is to be used as well, business function ISR_GLT_COMMODITY_5 (Trade, Commodity Management 5) has to be switched on in addition.

After activating this business function, you make Customizing settings under:

Logistics - General Global Trade Management Invoice Forecasting.

Logistics - General Global Trade Management Position Management Portfolio Management.

Materials Management Purchasing Commodity Pricing (only if LOG_CPE_FA_FE is switched on).

Sales and Distribution Basic Functions Commodity Pricing (only if LOG_CPE_FA_FE is switched on).

Logistics - General Global Trade Management Trading Contract Pricing and Payment Events (PPE) (only if ISR_GLT_COMMODITY_5 is switched on).

For more information about activating the individual functions in Customizing, see the relevant detailed release notes for the main release note.

Features

Report: Any Selection of Deals and Related Invoices

New UI: Report shows any simulated invoices and real invoices for a given selection, with the possibility to react to given statuses and with navigation to related transaction (invoices, payments). Report shows any selection of deals and related invoices (both SD and MM).

You now have one central application fully integrated in SAP ERP to view all deals that need to be invoiced.

Simulation of Invoices

IFW simulates invoices both on sales and purchase side, based on available pricing and payment data. The user knows the earliest and latest dates for creating invoices.

Navigation to Invoice Creation

The user can navigate from simulated invoices directly to the SAP invoice creation and invoice verification transaction screens. All required and known data is defaulted from the IFW report. Invoice creation and invoice verification screens were separate transactions. They are now accessed easily from one single screen.

Flexible Status Management of (simulated) Invoices

Dates for future invoices and the possibility of creating an invoice are transformed into a set of statuses displayed in the IFW report. For this, the SAP BRFplus application, which is fully flexible and configurable, is used in the background.

Integration into Commodity Pricing Engine (CPE) and new Events for Pricing

Commodity Pricing is often determined by certain events. Pricing and Payment Events (PPE) feeds data into Commodity Pricing Engine (CPE), and CPE gives back dates, status, and amount of future invoices.

With PPE and CPE, IFW is fully integrated in a framework of logistical and pricing data. Pricing engine is fully integrated.


Retail, Connectivity to F&R 5.2

Technical Data

Technical Name of Business Function ISR_APPL_SCM_2



Technical Usage Retail

Application Component Logistics Basic Data (LO-MD)

Required Business Functions

Retail, Planning and Master Data (EA-RETAIL) (ISR_EARET_PLANNING)

Retail, Supply Chain (EA-RETAIL) (ISR_EARETAIL_SCM)

Retail, Planning and Master Data (ISR_RETAIL_PLANNING)

Retail, Supply Chain (ISR_RETAIL_SCM)

This business function provides new features and usability enhancements for improved connectivity between the SAP ERP and SAP Forecasting and Replenishment (SAP F&R) systems. The features provided offer the following business and technical benefits in the areas replenishment and optimization in SAP F&R:

Transfer of source list data from SAP ERP to SAP F&R, for use in source determination in SAP F&R

Enhancements in the area of time-dependent promotion data maintenance

Consideration of transit stock

Prerequisites


Type of Component Component Required for the Following Features

Only

Software Component

EA-RETAIL 606, SAP_APPL 606

You have activated the following business functions:

o Retail, Planning ans Master Data (ISR_EARET_PLANNING)

o Retail, Supply Chain (ISR_EARETAIL_SCM)

o Retail, Planning and Master Data (ISR_RETAIL_PLANNING)

o Retail, Supply Chain (ISR_RETAIL_SCM)


Features

Source List

You can transfer source list data from SAP ERP to SAP F&R. The source list, an existing component of the source of supply network in SAP ERP, contains the preferred sources of supply defined for combinations of materials and receiving plants, as well as the periods during which procurement from these sources is possible. The standard interfaces from SAP ERP to SAP F&R have been enhanced to allow users to consider source lists during source determination in SAP F&R. The system evaluates the source list entries in SAP ERP to determine whether they are relevant for SAP F&R. If relevant, they are transferred to SAP F&R to be taken into consideration during source determination.

Time-Dependent Promotion Data

You can maintain promotions with time-dependent replenishment data, meaning you can adapt replenishment parameters during active promotions. Based on the existing maintenance transaction for time-dependent promotion data, you can create default values for minimum and maximum stock levels, planning and delivery cycles, and planned delivery times. You can create the default values manually or you can create them automatically using a mass import of default values from customer sources. The system transfers these values as time-dependent data for transportation lanes to SAP F&R

Consideration of Transit Stock

The standard order interface from SAP ERP Retail to SAP F&R has been enhanced to allow for the consideration of transit stock.

When performing a requirements calculation for a combination of material and plant, SAP F&R by default considers open orders in the receiving plant. This means that when calculating the net demand for a combination of material and plant, the system also takes into account any goods receipts expected by the delivery date for the calculated required quantity. However, if an exceptional stock transfer is triggered in the supplying plant (for example, to another distribution center), it is necessary that SAP F&R also considers open stock transfer orders at the supplying plant so that this extra demand is taken into consideration. The following enhancements to the transfer of order data have therefore been made:

Goods issue information (quantity, unit, and completion status) is transferred from SAP ERP to SAP F&R. SAP F&R can therefore consider completed goods issues in the requirements calculation of the supplying plant.

It is now possible to send from SAP ERP to SAP F&R stock transfer order items in which the combination of material and supplying plant is F&R-relevant but not the combination of material and receiving plant.

You can specify whether stock transfer orders are relevant for the requirements calculation of the supplying plant (as goods issues), for the receiving plant (as goods receipts) or both. Replenishment relevance is set at the level of order document type.


Retail, Inbound Promotions 2

Technical Data

Technical Name of Business Function ISR_RETAIL_PROMO_2

Type of Business Function Industry Business Function

Available As Of SAP ERP 6.0 EHP6

Technical Usage Retail

Application Component LO-MD-PR, LO-MD-RDM

Directly Dependent Business Function Requiring Activation in Addition

Retail (EA-RET)

Retail, Bonus Buy (ISR_RETAIL_BONUS_BUY)

Retail, Import of Promotional Data and Funct. Enhancements (ISR_RETAIL_PROMO)

You can use this business function to enhance promotions in SAP ERP with subsequent processing for bonus buy articles and to add display articles to promotions.

Prerequisites


Type of Component Component Is Needed Only for the Following Features

Software Component EA-RETAIL 606

SAP_APPL 606

Features

Bonus Buy Enhancements

Articles that are associated with bonus buys can now be synchronized to the corresponding promotion as line items. This enhancement triggers subsequent processing in SAP ERP.

Display Articles

Display articles can now be added to promotions created in SAP PMR. This enhancement allows retailers to procure display articles containing component articles that are planned into promotions. It also makes the articles available for subsequent processing, such as allocation or promotional announcements.

Switches

This business function uses the following technical switches:

ISR_APPL_PROMO_2 (SAP_APPL)

ISR_RETAIL_PROMO_2 (EA-RETAIL)

Business Functions

Documents

Transcript of Business Functions