Release Workbench 

Use

After you have drawn up the final version of a plan or subplan you can release it. This triggers the creation of outbound messages with relevant data. Data can be distributed as XML files with the SAP Exchange Infrastructure (SAP XI) and for some messages you can choose to send it directly by RFC to the SAP R/3 System. In the SAP XI environment, MAP message types MAP are defined under application component “BI CONT 3.51 ® http://sap.com/xi/SEM”.

In the Release Workbench use appropriate selection criteria (for example, product ID, category, sales organization and distribution channel) to specify the exact data that you want to release. You can simultaneously release data for several message types (for example, all message types that relate to a particular category).

Prerequisites

To use the functions of the Release Workbench you must have the appropriate authorization:

●     Authorization for specific selection criteria

●     Authorization for repeated release of data

Process Flow

The following diagram depicts the release process flow:

...

       1.      From the SAP Easy Access screen, choose Business Planning and Simulation ® Planning Content ® Retail Analytics ® Release Workbench ® Start Release Workbench to start the Release Workbench.

       2.      On the initial screen in the Release Workbench you choose message types using the relevant selection fields.

You can also choose Release Associated Messages.

For more information, see Message Types and Their Dependencies.

In the screen area General Selection Criteria you can store general restrictions for the data to be released.

       3.      After you have entered data on the initial screen a tab page is displayed for each selected message type. You then enter additional data there that is specific to the message type.

It is not possible to release data here straight from the planning layout.

Following a release, XML files are created that can be distributed with the SAP Exchange Infrastructure. Alternatively, data for specific message types can be transferred directly with Remote Function Call (RFC) to an SAP R/3 Retail System. For more information on RRC-enabled message types, see SAP Note 682377.

Data can be released immediately or it can be scheduled as a job for later. Alternatively you can simulate the release. Checks are performed here without triggering a release.

Every release transaction is retained in an application log that you can call at the touch of a button. This contains information about the selection conditions and resulting data objects and about error messages if the release was not completed successfully.

Most message types are based on master data and can only be released once. Other message types, such as OTB, allocations tables and purchase orders are composed of planning data and can be released more than once. The related control is performed with a release status that is available for master data but not for planning data.

To be able to send markdown proposals you do not need to release the proposals manually beforehand. The system creates these at periodic intervals - usually once a week - and transfers them to the retailing system.