Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
B
Appendix: RMFCS Integration
Assortment Planning Cloud Service supports integration with Oracle Retail Merchandising Foundation Cloud Service (RMFCS). If a retailer has RMFCS as the source system for inventory and transactional data, they can readily integrate to get foundation hierarchy data, inventory, and transactional data from RMF Cloud Service using RAP integration. This appendix provides more details specific to the integration with Oracle Retail Merchandising Foundation Cloud Service.
New Placeholder Item Integration
New Placeholder Items (Style/Color or Styles) created in APCS can be integrated with RMFCS. It involves multiple levels of process which are detailed below:
-
First, the RMFCS Server should be connected with APCS during deployment, after mapping the dimensions (style/color, style) to item in RMFCS. New Placeholder items created in APCS will directly use the reserved item numbers from RMFCS. A Service Request (SR) can be created to request to connect the RMFCS server with the Planning Servers. This is needed only if the customer already has RMFCS as the master source for defining new items. New Placeholder Items created in APCS will directly use the reserved item numbers from RMFCS. For more details, refer to the RPASCE-RMS Integration for Item Management - Slow Item Build section in the Oracle Retail Predictive Application Server Cloud Edition Administration Guide . The customer should ensure that max_item_resv_qty and max_item_expiry_days are set on the RMFCS DB side to allow reserving of items from the RMFCS side.
-
The customer can then create new placeholder items within APCS and assign attributes to them. RMFCS does not contain style/color as a separate level, so an attribute should be selected as the RMFCS Color attribute in the Product Setup view in Planning Administration. All new style/colors created should be assigned with a unique color attribute. The customer should then select the style/color ready for Export to RMFCS. The process only allows for creating new placeholder items and assigning initial attributes. Any further updates/maintenance of the item or RMFCS specific item attributes should be managed in the RMFCS side.
-
The customer can run the Export to RMF CS custom menu which exports all items marked for Export to RMFCS in real time to the RMFCS Item Induction process. It exports new item details, and its assigned attributes (UDA).
-
In batch, the customer needs to run Rename Style/Color that renames the style/color positions created as style concatenated with a color attribute as it will be identified in the RMFCS product hierarchy file. This process is scheduled to run as part of weekly batch before the hierarchy load process.
-
Once RMFCS approves the newly interfaced items, the same items will be coming in the product hierarchy file as regular items. Since it will use the same position names for Item and Style/Color, the standard hierarchy load process in the APCS side will then formalize those informal placeholder Item and Style/Color.
July 1, 2026 Appendix B-1 of B-2
Appendix B New Product Attribute/Product Attribute Value Integration
New Product Attribute/Product Attribute Value Integration
New Placeholder Product Attributes or Product Attribute values can be created in AP during planning process. However, newly created Product Attributes and values will not be available in RMFCS if those are assigned to items; it will not be integrated to RMF CS during placeholder item process. So before using new product attributes, the first user needs to create the Product attributes/Product Attribute values, which can use the standard Placeholder Attribute export process and create the same in RMFCS UDA. The UDA id/value can be different than the product attribute id/product attribute value created in AP side. So it needs to be renamed first before formalizing the same.
The customer can upload the rename file for Product Attribute/Attribute values or use the Planning Admin workbook to enter the actual Rename Product Attribute and Rename Product Attribute value measures. If those measures are populated and if the attribute is a place holder attribute, the Rename Product Attribute batch process renames the place holder attributes and then the regular product attribute import process will formalize the Product Attribute if the same product attribute created in RMFCS is interfaced using RAP Interfaces.
Batch Tasks Specific to RMFCS Integration
The following sets of Online Administration Tools tasks are pre-configured in Configured Batch Tasks to support RMFCS integration. For more details about running the tasks, see the Oracle Retail Assortment Planning Cloud Service Administration Guide .
- Run Batch Task Group > Set RMF CS Dimension Mapping
RMFCS can be linked with the APCS domain in real time to get the reserved item numbers for new placeholder items created. In order to do that, connections between the RMFCS servers and RPAS server needs to be set up during installation time. For more details about those setups, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide . Once those are set, running this task will map the sku (Item) and skup (style/color) dimensions to Item in RMFCS. Once this mapping is done, any new place holder sku or skup created will use the reserved RMFCS item numbers directly from RMFCS.
- Run Batch Task Group > Rename RMF CS Style/Color
This task renames the Style/Color DPM positions which are exported to RMFCS, with Style concatenated with the Color Attribute Id, as it comes in the Product Hierarchy Interface.
July 1, 2026 Appendix B-2 of B-2