Functional Requirements for the RRM Interface 

To ensure that data exports in the Retail Revenue Management interface are performed correctly, you must make various settings in Customizing and observe certain mandatory and optional implementations of Business Add-Ins (BAdIs). 

Settings in Customizing

·        RRM Profile

The RRM profile is a higher-level control parameter for controlling data exports. It is used to summarize several different control parameters for the program flow and for reading data. You maintain the RRM profile in Customizing for pricing. If you perform the data export using the report RWRP_RRM_OUTBOUND, you have to specify an RRM profile on the selection screen.

Maintain the following parameters in the RRM profile:

¡        Filter value for the Business Add-In (BAdI) RP_RRM_OUTBOUND

¡        Indicator that determines whether an application log should be created for the data export

¡        Purchase price determination type for procedure when defining the purchase prices

¡        Price point type for determining price point groups

¡        Various parameters for determining historical sales data

Specify the source from which the data should be determined. If you use the Retail Information System (RIS) as the source, you must enter a selection variant with an application area. If you use SAP BW as the source, you must enter a method from an analytical application. In both cases you must define table fields for the business volume value and quantity.

RRM profile 0001 is supplied as an example in the standard system.

·        Selection Variants

To be able to read historical sales data from another info structure, you must create a selection variant for an existing application area. Maintain selection variants in Customizing for pricing. In the standard system, the application area 09 is supplied for the RRM interface (Retail Pricing: RRM Interface).

In the selection variants for the RRM interface you must explicitly specify entries that contain the field names for the business volume quantity, the corresponding reference field of the unit of measure, the business volume value, and the corresponding reference field of the currency and select value return as the field use. The field names should be specified in the RRM profile used.

·        Analytical Application Methods

To be able to read historical sales data from SAP BW, you must create a method for an analytical application. You maintain methods, together with the source query data, using transaction MCW_AA. In the standard system, the analytical application 009 “Retail Pricing – Retail Revenue Management” is supplied for the RRM interface.   

In the query components for the RRM interface you must explicitly specify entries that contain the field names for the business volume quantity, the corresponding reference field of the unit of measure, the business volume value, and the corresponding reference field of the currency and select value return as the field use. The field names should be specified in the RRM profile used.

Business Add-Ins

You can maintain various Business Add-Ins (BAdIs) to extend the functions of the RRM interface in Customizing for retail pricing.

The following BAdIs are available:

·        RP_RRM_OUTBOUND

This BAdI provides the actual link between SAP Retail and external RRM systems when you use the RRM interface to export data. Instead of direct communication with the RRM system, you can also use an RRM system specific exchange program to perform and monitor the data transfer.

Create an implementation for this BAdI so that you can perform the data export. The BAdI has an extendable filter type, which enables you to define different implementations for different RRM systems or for data export subtasks. In the RRM profile used, specify the filter type value (filter value) that was issued when you created an implementation.

The filter values MSEXCEL and FILEPROG are supplied as examples of possible implementations in the standard system.  The examples show how the articles and store data that were selected for the data export in the report RWRP_RRM_OUTBOUND can be transferred to Microsoft Excel or to an ASCII file.

·        RP_RRM_MDSEL_CONTROL

You will often want to limit the selection of articles and stores in data exports using the RRM interface, for example, when not enough historical sales data for newly created articles exists for optimization in an RRM system. You can filter the selection using this BAdI. Implementations are optional for this BAdI.

·        RP_RRM_BAPI_PP_READ

You can use this BAdI to monitor purchase price determination in the SAP Business Object BUS6060 “Retail Revenue Management Interface“. You can define purchase prices for specific customers, using a different method in each case, or you can check and filter the purchase prices defined using standard methods. For customer-specific definitions in the RRM profile used, set value 99 “Determination using BAdI” for the parameter PP Determination Type. Implementations are optional for this BAdI. However, they are required if you intend to define the purchase prices for specific customers.

·        RP_RRM_BAPI_SD_CHECK

You can use this BAdI to monitor the determination of historical sales data (sales history) in the SAP Business Object BUS6060 “Retail Revenue Management Interface“. Implementations are optional for this BAdI.