Show TOC

 Retail, MAP Interface 2

 

Technical Data

Technical Name of Business Function

BF_ISR_RETAIL_MAP_IF2

Type of Business Function

Enterprise Business Function

Available As Of

SAP Enhancement Package 5, SAP ERP 6.0

Technical Usage

Retail

Application Component

EA-RETAIL

Directly Dependent Business Function Requiring Activation in Addition

ISR_RETAIL_MAP_IF

You can use this business function:

  • To assign rollout groups to categories

    This is relevant for fashion retailers or other retailers who use purchasing list in SAP ERP.

    This business function also allows you to activate consistency checks when creating a purchasing list or adding articles to it.

    The new feature now uses restrictions to ensure that the rollout assignments are correct depending on the types of rollouts you can use for the different categories or hierarchy nodes.

  • To maintain labels in the layout workbench

    This is relevant for nonfashion retailers using the layout workbench. You can now maintain label information manually if the retailer does not use an external shelf optimization program, or if the data needs to be changed in SAP ERP.

Prerequisites

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

Type of Component

Component

Is Needed Only for the Following Features

Software Component

EA-RETAIL 605

For optional Customizing activities, check the Features section below.

For more information about the assortment planning interface, see Retail, SAP Merchandise and Assortment Planning Interface.

Features

This business function:

  • Introduces rollout groups to aggregate existing rollouts

  • Includes a new transaction to assign rollout groups to categories

  • Offers input help on the entry screen of Operational Assortment Planning and Control (purchasing list) to find valid rollouts

  • Includes consistency checks, for example, between rollout assignment of purchasing lists and valid rollouts of the corresponding category, or between rollout assignment of the purchasing list and articles added to the purchasing list

  • Performs data extraction of new rollout definitions from SAP ERP to SAP NetWeaver BW for Merchandise and Assortment Planning

Rollout Groups

You can define rollout groups that have a technical key and a language-dependent description. A new Customizing activity allows you to assign rollouts to rollout groups.

Assigning Rollout Groups to Categories

You assign rollout groups to categories and by leaving the category in this assignment blank, you have a rollout group for all categories with no specific categories assigned.

However, if you have a large number of categories you can maintain one rollout group as the main (default) rollout group, which is valid for all categories where no rollout group is assigned. You can do this by assigning the rollout group to an empty category. You can then define specific rollout groups for specific categories.

Note Note

One rollout group can be assigned to several categories whereas one category can have at most one rollout group assigned to it.

End of the note.

You can maintain exceptions for the main rollout group for specific categories.

Season, Season Year and Rollout Information

When you release a planned article to a purchasing list, the system hands over the season/season year/ rollout assignment information of the purchasing list the article is assigned to. If the planned article is assigned to several purchasing lists, the season/season year/rollout combination with the earliest valid-from date is handed over to the basic data of the article. The system ignores season/season year/rollout assignments where the valid-to date is in the past.

Consistency Checks When Creating or Changing Purchasing Lists

You can make settings for system messages so the system can warn you in case a rollout is not assigned to a valid rollout group. When you try to create a purchasing list for a season/season year/rollout combination where the rollout is not assigned to the rollout group valid for the category of your purchasing list, the system displays an error message. It can prevent you from creating such a purchasing list. The corresponding message is WRF_APC 380: Rollout &1 is not valid for purchasing list &2.

You can make settings for system messages so the system can also warn you in case of a contradiction in rollout assignment when you try to add a material to a purchasing list. If the rollout assignment contradicts the rollout assignment of the purchasing list, that is, the rollouts belong to different rollout groups, the system displays an error message. It can prevent you from adding such materials to a purchasing list. The corresponding message is WRF_APC 381: Rollout &1 of material &2 is not consistent with rollout &3 of PL &4.

When you create an existing material from a planned material, the system checks the planned material and your settings for system messages described below. If the planned material is contained in multiple purchasing lists assigned to different rollouts, it fetches information of the rollout with the earliest valid-from date.

  • If this rollout assignment contradicts one of the purchasing list rollout assignments, the system issues a warning or stops the creation, depending on your settings for system messages. The corresponding message is WRF_APC 381: Rollout &1 of material &2 is not consistent with rollout &3 of PL &4.

  • If this rollout is not assigned to the rollout group valid for the category of the material, the system issues a warning or stops the creation process depending on your settings for system messages. The corresponding message is WRF_APC 387: Rollout &1 is not valid for material &2.

Data Extraction from SAP ERP to SAP NetWeaver BW

Each category can have its own rollout definition. This information is provided by an extractor that returns rollouts in the format of the structure WRF_S_ROLLOUT. The structure refers to the tables TWSAI (annual seasons), WRFT_ROASGN (the rollout assignment to rollout groups) and WRF_ROCAT (the assignment of categories to rollout groups).

For categories with no rollout groups assigned to them, the system takes the default rollout group as a fallback strategy. The default rollout group is the rollout group assigned to a blank category.

Example

Rollout Groups

Rollout group 1 is Months and comprises rollouts 01 to 12 where 01 = January, 02 = February, 03 = March, and so on

  • Rollout group Two-Month Periods and comprises rollouts 21 to 26, where 21 = January, February, 22 = March, April, 23 = May, June, and so on

  • Rollout group Quarters and comprises rollouts Q1 to Q4 where Q1 = first quarter, Q2 = second quarter, and so on

Note Note

You can only assign a single rollout to a rollout group.

End of the note.
Assigning Rollout Groups to Categories

If you have 100 categories, out of which 96 are planned by month and four by quarters, you can set up rollout group Months as the default (you do this by assigning it to a blank category. This saves you the trouble of assigning this rollout group to the 96 categories over and over again.