1 Using This Recipe
Use this recipe to create purchase requisitions and purchase orders in Oracle Fusion Cloud SCM (SCM) when Purchase Orders are booked in Oracle MICROS Inventory Management (IM). Upon successful creation of Purchase Requisitions in SCM, an Order Acknowledgement is sent back.
Note:
This recipe is available as Oracle MICROS Inventory Management — Oracle Fusion Cloud SCM | Order Processing in the Integration Store. Oracle provides this recipe as a sample only. The recipe is meant only for guidance and is not warranted to be error-free. No support is provided for this recipe.Overview
This recipe integrates Inventory Management with SCM Procurement.
It enables customers to centralize orders across all locations. Consolidated Purchase Orders provide greater purchasing power to the Organization during supplier negotiations.
To use the recipe, you must install the recipe package and configure the connections and other resources within the package.
Every booked Order in IM generates a Purchase Order Flat file in the configured File Server location. This schedule driven recipe reads each file, creates a consolidated Purchase Requisition Import file, and imports the file into SCM using the service integration APIs. It also executes an Enterprise Scheduler (ESS) job to generate a consolidated purchase order in SCM for the imported requisitions.
This recipe listens to the Requisition Import event, processes the response generated by SCM against the previous requisition request, and generates an acknowledgement file based on success/failure of IM Orders.
-
Oracle MICROS IM Orders to SCM Requisitions: The scheduled integration connects to the configured FTP server and downloads the order files created by IM.
The integration then creates a requisition header interface file, a requisition line file along, and a properties file based on the downloaded files. Then it invokes the Requisitions bulk data import process with these files using the ERP adapter.
It then invokes the Oracle ERP Launch ESS Job integration.
-
Oracle SCM Order Status to Oracle MICROS IM: This flow processes the requisition import and creates acknowledgement files based on the headers of successfully processed requisitions. It then uploads the Acknowledgement file to the configured IM FTP Server.
-
Oracle ERP Launch ESS Job: This is an application-driven integration which gets triggered by the Oracle MICROS IM Orders to SCM Requisitions. It launches the Generate Purchase Order ESS job in SCM based on the job parameters received as the input payload.
Parent topic: Using This Recipe
System and Access Requirements
-
Oracle Integration Cloud, Version 22.1.3.0.0 or higher
An account in Oracle Integration Cloud with the Service Invoker role to configure the recipe
-
Oracle Fusion Cloud SCM, Version 21D or higher
-
Oracle MICROS Inventory Management, Version 9.1
Parent topic: Using This Recipe
Assumptions
-
Master data configurations such as procurement business units, inventory locations, organizations, Items, Categories, UOMs, Suppliers are already performed in SCM
-
Relevant Master data is synchronized to IM and the respective OIC Lookups containing information such as Suppliers, Items etc are updated with the cross references
Note:
As a pre-requisite, the recipe Oracle Fusion Cloud SCM — Oracle MICROS Inventory Management | Master Data Synchronization for synchronizing Supplier and Item Master data from SCM to IM should be installed. -
Oracle MICROS Inventory Management
-
One MICROS Purchase Order represents one Purchase Requisition in SCM. Hence one header per Order file is created in the File-Based Data Import (FBDI) import file
-
SCM Purchase Requisition Number is NOT auto generated. It is populated with the IM Purchase Order Number
-
Supplier acknowledgement, ASDN, Receipt are beyond the scope of this recipe, however below important points should be addressed while implementing the same due to the recipe design considerations.
-
“Customer Number” data send as Location Reference in the MICROS Order export file is send to the supplier via “Notes to the Supplier” field in Fusion Cloud SCM Requisition Line. This is important to facilitate a smooth delivery location identification recognized by the supplier
-
Supplier ASDN/delivery note/B2B Invoice delivered along with the shipment at the receiving center should have the Purchase Order Number field generated with SCM Purchase Requisition Number and not SCM Purchase Order Number. This is due to the fact that Purchase Order receipt is done at the IM application and that would need the IM generated Purchase Order Number
-
-
One Deliver-to-Location in SCM is mapped against the combination of one or more IM provided “Customer Number” and the respective vendor/supplier. This is incorporated as the OIC lookup cross reference.
-
Current design considers Purchase Requisitions having a single Requisitioning Business Unit (BU), Approver, Entered By, and Procurement BU. Hence these values are stored in the lookup table. Integrations and lookups could be modified based on additional requirements such as multiple BU’s or dynamic invokes.
-
All the OIC cross references are updated based on SCM and IM configurations
-
Recipe integration includes the minimal data mapping required to generate the SCM Purchase Requisition. Recipe consumers can have additional mappings based on their requirements
The recipe includes an example implementation of validations which can be modified as required
-
OIC lookups are used to store environment specific values/configurations and cross references. Recipe consumers can choose to either retrieve the values using additional invokes or continue to use the lookups as per the requirements
-
Recipe integration includes sample error handling and notifications. A robust error handling based on customer needs has to be implemented by the recipe consumer
Parent topic: Using This Recipe