Show TOC

Retail, Global Data Synchronization Locate this document in the navigation structure

 

Technical Data

Technical Name of Business Function

ISR_RETAIL_GDS

Type of Business Function

Industry Business Function

Enterprise Business Function

Available As Of

SAP ERP 6.0 Enhancement Package 3

Technical Usage

Retail

Application Component

IS-R

Directly Dependent Business Function Requiring Activation in Addition

Retail, Planning and Master Data and Retail, Planning and Master Data, EA (ISR_RETAIL_PLANNING, ISR_EARET_PLANNING)

As of SAP ECC 6.0, Enterprise Extension Retail, Enhancement Package 3 (EA-RET 603), the business function Retail, Global Data Synchronization (ISR_RETAIL_GDS) is available. With this business function you can use various new functions in the GDS area: Enhanced Price-Catalog Inbound-Processing, Workflow for Work with Inbound Price Catalogs, Validation and Enrichment Processor, Sample implementation Agentrics data pool.

Prerequisites

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

Type of Component

Component

Is Needed Only for the Following Features

Software Component

EA-RETAIL 603

Enterprise Service Bundle

ES Bundle Global Data Synchronization

In order to be able to use this business function, you must also activate the business functions ISR_RETAIL_PLANNING and ISR_EARET_PLANNING.

You make the Customizing settings under

  Logistics General   Material Master   Global Data Synchronization   Inbound   General  

  Process Data Pool  

  Process Classification Level  

  Process Class System  

  Process Classification Code  

Additionally under

  Logistics General   Material Master   Global Data Synchronization   Inbound   Subscription   Create Default Values for New Subscription (recommended)  

And under

  Logistics General   Material Master   Global Data Synchronization   Inbound   Data Transfer  

  Preassignment and Saving Options at Client Level  

  Configure Automatic Transfer (if automatic transfer is to be used)  

  Convert Condition Types (if purchase price or sales price is used)  

  Define Purchase Price and Sales Price (if purchase price or sales price is used)  

  Control Posting of Purchase Price (if purchase price is used)  

  Control Posting of Sales Price (if sales price is used)  

  Control Reading of Prices (if purchase price or sales price is used)  

Features

Price Catalog - Inbound Processing

Price catalog inbound processing has been supplemented with a new selection screen with an intuitive user interface. This transaction offers the preselected worklist directly on call-up (for example, the new entries in the catalogs). The preselection is the last manual selection or - if not available - the default selection. The selection also takes into account workflow items (for task GDS_IN) so that a user can automatically display the catalog entries that he or his catalog group must process.

The transaction can also be used for a free selection. Here you can select precisely which catalogs are to be displayed in the enhanced price catalog processing. After this selection you go directly to price catalog processing. This catalog selection provides an overview of the selected catalogs and a preview of the relevant catalog items. Using various default setting options, you can control, for example, which catalog groups (and thus employees) are assigned to process which catalogs.

New workflow (GDS_IN)

A new workflow is available. It optimizes the work with inbound price catalogs: In the case of automatic creation or changing of price catalogs, the system informs the responsible employee of a work item and immediately provides him with the assigned catalogs for processing.

VE-Processor

The Validation and Enrichment Processor (VE Processor, VEP) is a generic tool for validating and enriching data. The VE Processor enables the user to apply rules to mass data. Its functionality has been improved in important aspects: You can now form worklists and create where-used lists for each element.

Example Implementation

SAP delivers an example implementation for the Agentrics data pool. The following GDS messages are supported: Subscription, Notification und Confirmation. The processing functions for Subscription and Notification have been improved so that the active use of GDS has been further simplified.