Assumptions

• Master data configurations such as procurement business units, inventory locations, organizations, Items, Categories, UOMs, and Suppliers are already performed in SCM.

• The Relevant Master data is synchronized to IM and the respective OIC Lookups containing information such as Suppliers, Items, and so on are updated with the cross references.

  Note:

  As a prerequisite, install the recipe Oracle Fusion Cloud SCM — Oracle MICROS Inventory Management | Master Data Synchronization for synchronizing Supplier and Item Master data from SCM to IM.

• Oracle MICROS Inventory Management

  • The Order file format must be exactly as specified in Appendix A: MICROS Inventory Management Order Export.

  • The Order acknowledgement file format must be exactly as specified in Appendix B: MICROS Inventory Management Order Acknowledgement.

• 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.

• The SCM Purchase Requisition Number is not auto generated. It is populated with the IM Purchase Order Number.

• Supplier acknowledgement, ASDN, and Receipt are beyond the scope of this recipe. However, the following important points need to be addressed while implementing the same due to the recipe design considerations.

  • Customer Number data sent as Location Reference in the MICROS Order export file is sent to the supplier via the 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.

  • The Supplier ASDN/delivery note/B2B Invoice delivered along with the shipment at the receiving center should have the Purchase Order Number field generated with the SCM Purchase Requisition Number and not the SCM Purchase Order Number. This is due to the fact that the Purchase Order receipt is done at the IM application, and needs 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.

• The current design considers Purchase Requisitions as 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 can be modified based on additional requirements such as multiple BU’s or dynamic invokes.

• All 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 must be implemented by the recipe consumer.