Oracle Retail Decoupling

Oracle Retail systems are aging, highly customized applications that are not scalable solutions for our growth and expansion plans for Retail business. The existing systems are not supported in their current state and will either require customizations to scale and upgrade or replace.
SIM: Maintance of Store Inventory is currently updated behind 1-2 hours, not real time. This delay causes disruptions to the user journey, minimizes the effectiveness of our OMNI capabilities and creates disconnected experiences for the consumer. Additional challenges: label printing is unstable, we have no offline support in SIM, limiting offsite/events support and requiring manual updates, retail inventory operations are managed in two applications causing inefficient user experiences.
RMS Product Data: RMS data is incomplete and limited, missing product details and images which leads poor consumer experiences in stores. This leads us to stitch data with ecomm data sources complicating the architecture. Product uploads are managed manually (excel) which leads to missing product in the system.
RPM Pricing: Pricing is currently one of the biggest drivers of issues within the Retail space. The system is complicated and currently drives roughly 70% of ticket submitted. All promotions within stores are managed manually through price adjustments, creating human error and prohibiting the use of complex promotions needed to support Membership programs and other commercial activities. Current tools are inadequate to support pricing management within the business, processes are manual and require uploads which are hard to validate and test and create products with missing/incorrect pricing leading to price overrides, creating audit risk.
RMA: Retail data visualazation, connected to Oracle Retail data warehouse. Disconnected from the Data team's strategy and pulling data from two sources creates disparity in reporting. Overall strategy to align with one shared source of truth. Reporting is limited (inventory is lacking, no planning reporting, phased out by Oracle and not supported)
RPAS Planning: MFP=Merchandise Fiscal Plan, AP=Assortment Plan. RPAS has not been updated for several years, used for system repository. Does not support the use case needed within planning. To be managed and owned by Shelby in E2E Planning.
RMS Accounting/ReSA: Align with Core Apps (Siva) and Finance - align on solution TBD
RMS Store Set ups: Workflows in setting up stores and cost centers that need to be migrated to a new system in order to decouple Oracle Retail modules
Allocation/Replen: Syrup is only used in the NA, need to rollout to EMEA/JP/China.
RIB/UC4 Shutdown: Once all of the above modules are shut down and moved to new solutions, these will no longer be needed and will shut down.