The SCN wiki will not be available for new content submission starting September 4th 6PM CET until September 7th 6PM CET. Please plan your SCN wiki tasks accordingly.
The In-Store Food Production Integration ES bundle, developed for the retail grocery industry, connects an external In-Store Food Production (ISFP) software solution to SAP ERP Retail for management of all processes involving a store's fresh items, with provision for the seamless integration of end-to-end business process support.
Note: The Term "In-Store Food Production" is equal to "Fresh Item Management".
This ES bundle will shorten the implementation time required to integrate ISFP data into SAP ERP Retail. An In-Store Food Production solution manages the full lifecycle of all perishable items in a store across all applicable departments (Meat, Seafood, Deli, Bakery, Produce, Food Service, Grocery and Floral) from the time of receipt of ingredients and primals through recipe, to construction or cutting plan to deconstruction. Comprehensive fresh item data management is a valuable tool to improve productivity, which reduces shrink of slow-moving and date-sensitive products that otherwise have to be thrown away. It can increase profitability for stores, which is important because of the thin margins in the grocery business. The In-Store Food Production Integration ES bundle leverages SOA by enabling stores to integrate their fresh item management solutions with SAP ERP using enterprise services.
This ES bundle will be of value to retail grocery enterprises using fresh item management systems to maintain and manage a store's perishable products.
How To Use This ES Bundle
Perishables, as their name suggests, require special care and handling. At a minimum, retailers need to know how much product to stock and to incorporate in in-store prepared foods, to avoid losses from spoilage. Because grocery margins are already thin, any reduction in perishables waste means more bottom-line profit.
- A master data exchange process is necessary to create a consolidated base for both involved systems (SAP ERP Retail and external ISFP) for all "fresh" items (ingredients, primals and sellable products). The master data created and maintained within SAP ERP Retail must be replicated to the external ISFP system.
- An inventory exchange process enables synchronization of inventory data between SAP ERP Retail and the external ISFP system. Besides inventory synchronization, physical inventory adjustments in form of complete counts of "fresh" items are sending back to the SAP ERP system.
- A price/cost exchange process between both systems will obtain the final sales price at SAP ERP Retail out of the calculated unit cost of a "finished" product sent from the external ISFP system.
The basic processes / data exchanges are:
- Transfer of master data from SAP ERP system to ISFP system
- Transfer of supplier data
- Transfer of merchandise category data (incl. Hierarchy)
- Transfer of store data
- Transfer of store group data
- Transfer of product data inclusive purchase and sales price data
- Transfer of master data from ISFP system to SAP ERP system
- Transfer of cost data
- Exchange of goods movement data
- Transfer of goods movement data (from SAP ERP system to ISFP system)
- Transfer of goods movement data (from ISFP system to SAP ERP system)
- Transfer of inventory data
- Request to execute physical inventory count (from SAP ERP system to ISFP system)
- Transfer of inventory data as creation (from ISFP system to SAP ERP system)
- Transfer of inventory data as confirmation (from ISFP system to SAP ERP system)
The following series of use cases for the In-Store Food Production Integration ES bundle shows how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate a few of the ways that this ES bundle could be used, the intention is to show the flexibility and reusability of these business objects and enterprise service operations so that you will have a clearer understanding of how to best deploy them in your own environment. This wiki is also a space for you to share knowledge and collaborate with others who are implementing the In-Store Food Production Integration ES bundle.
Use Case 1: Replication of Master Data from SAP ERP Retail to the external ISFP System
Master data within a retail organization need to be transferred from SAP ERP Retail to the external ISFP system. Master data are: Product data (including prices), merchandise category data (including hierarchies), store data, store group data and supplier data. Please refer to the Connectivity Kit to see details about all 5 Master data replication services.
An example for this use case is the replication of Stores: Stores can be grouped and flagged based on desired parameters, such as whether or not individual stores offer in-store food production. Once the desired stores are selected, store data can be replicated from SAP ERP to the external ISFP system.
Master Data replication enterprise services used within this case are:
Use Case 2: Execution of Physical Inventory
Request to exceute Physical Inventory count from the SAP ERP system to the ISFP system
REQUEST: This process step sends a request to execute a physical inventory count from the SAP ERP system to to the ISFP system. The message contains all items that have to be counted. This service is only relevant in connection with the (CONFIRMATION) Service that sends the results of the inventory count back to SAP ERP.The reponsible enterprise Services is: PhysicalInventoryCountERPRequest_Out
Transfer of physical inventory count data from the ISFP system to the SAP ERP system
This process consists of sending physical inventory count data from the ISFP system to the SAP ERP system. There are two options to send the physical inventory count data:
- CREATE: The physical inventory count data are sent without a reference to an existing physical inventory document (CREATE). In this scenario the ISFP decides which products are counted.
The responsible enterprise Service is: PhysicalInventoryCountERPCreateRequest_In
- CONFIRMATION: The physical inventory count data are sent as a confirmation to an existing physical inventory document. The confirmation is only relevant in connection with the above mentioned service which sends the (REQUEST) for counting. In this scenario the SAP ERP system decides which products has to be be counted.
The reponsible enterprise Service is: PhysicalInventoryCountERPConfirmation_In
Use Case 3: Transfer of Cost Data
Transfer of Cost Data from the ISFP System to the SAP ERP System
This process step consists of sending cost data from the ISFP system to the SAP ERP system. In the SAP ERP system the received data is used to create purchasing conditions.
For details about the element structure of the messages mentioned, see: ProcurementPriceSpecificationERPCreateRequest_In
Use Case 4: Transfer of Goods Movement Data between the ISFP System and the SAP ERP System.
Transfer of Goods Movement Data from the ISFP System to the SAP ERP System.
This process step consists of sending goods movement data from the ISFP system using a bulk message (for example, the message can include data for several goods movements procedures) to the SAP ERP system. In the SAP ERP system the received data is used to create corresponding goods movement documents.
For details about the element structure of the messages mentioned, see: GoodsMovementERPCreateRequest_In
Transfer of Goods Movement Data from the SAP ERP System to the ISFP System.
This process step contains of reading a single goods movement document (just at the booking time) within the SAP ERP system and sending this data using a message (for example, the message includes one header and several items) to the ISFP system.
For details about the element structure of the messages mentioned, see: GoodsMovementERPNotification_Out
If you want to implement the integration scenario, please refer to the connectivity kit for the integration scenario also available in SDN.
Certified Partner Applications implementing this ES Bundle
Additional services, for Example Enterprise Services that move the price data, are planned for development for this ES bundle.
- Installed your SAP ERP system with release version ERP 6.0 and Retail Add-On EA-Retail. The software component versions SAP APPL 604, ESA ECC-SE 604 and EA-RETAIL 604 must be installed.
Note: The ES that are necessary to implement this integration scenario are contained in the following software component versions: SAP APPL 604, ESA ECC-SE 604, and EA-RETAIL 604.
- Configured your SAP ERP for SAP Retail. This includes activating the corresponding SAP Retail business function set (for example, settings made using transaction SFW5). For more information, see Configuration as SAP Retail.
- It is necessary to install SAP XI/PI if this is not yet available in the retailer's landscape. The minimum version is XI/PI based on SAP NetWeaver 7.0. You can download XI/PI from SAP Service Marketplace. For more information, see SAP Exchange Infrastructure or SAP NetWeaver 7.0.
Note: During the initial XI/PI installation you should import SAP products and SAP software components to the System Landscape Directory (SLD). For further information, see #1.3. Configuring Integration Scenario and Maintaining Master Data.
SDN and SAP Links
Fresh Item Management solution provider for SAP: