As its promise towards continuous innovation, Oracle rolls out quarterly updates for its enterprise applications — HCM, Financials, SCM, & ERP. Oracle quarterly updates include the following:
· Bug fixes and data fixes
· Security alerts and enhancements
· New tax, legal, and regulatory updates
· Upgraded scripts
· Certification with new third-party products and versions
· Certification with new Oracle products
The latest in this series is Oracle 24B release. If you’re wondering what new features and enhancements come along with this update, this blog is for you. Here, we’ll highlight what new technical and functional updates come along with Oracle 24B release.
Supply Chain Management Functional Updates
These functional updates are concerned with the Supply Chain Management (SCM) module.
Supply Chain Orchestration
· Supply requests can now be searched with the help of supply request reference, supply order, supply document, or item. Users can also create and save their own default searches.
Collaboration Messaging Framework
· AVALARA and TIE KINETIX users can now connect with their trading partners and exchange messages with greater ease.
· Users can now send a PO as an uncompressed PDF file by email to their suppliers using “Transmit the PO PDF”.
Procurement
Procurement Checklists
· Procurement agent can now view compliance checklists. They can now drill down to the checklist from Oracle Analytics Publisher reports or external applications.
· User can also create a compliance checklist and can also become the owner. If user manages compliance checklists for a single procurement BU, that BU is defaulted as the procurement BU of the checklist. To manage compliance checklists for multiple procurement BUs, the BU set in the Default Procurement Business Unit profile option can be defaulted.
Purchasing
· Users can now create requisitions and purchase orders with special handling. In special handling, users can capture special handling descriptive on the document header and lines.
· The Bill Only special handling type can be created for purchases that don’t follow the standard procurement process.
· If contacts are no longer applicable, these can be replaced with additional contact email IDs on approved purchase orders.
· If only some of the quantity on the order line is currently available on the requested date, then your drop ship supplier might ship that quantity, and Order Management will split the order line for the remaining quantity.
Redwood Experience
· A new task is now available under Purchase Agreements and Purchase Orders work area to access the new Purchase Agreements page.
Self Service Procurement
· For requisitioning usage, users can now secure local catalogs, punch out catalogs, smart forms, and public shopping lists by internal deliver-to locations.
· Users can create requisition lines with multiple distributions to allocate costs to multiple charge accounts and projects.
· Procurement Requester can now view lifecycle information for requisitions in the Responsive Self Service Procurement application.
· Procurement Requester can now review the summarized fulfillment information for each line in the requisition and drill down into downstream documents such as negotiations, purchase orders, shipments, receipts, and invoices.
· With this, procurement requester will have access to relevant information of the preferred supplier source or internal source to make an informed buying decision.
Inventory Management
· The lot uniqueness parameter can default to “Unique across items,” ensuring that users do not overlook changing the setting, which could lead to additional work later on to correct.
· Users can now view recently completed counts for their PAR locations. They can also drill into the details to see the replenishment status of a specific count.
Since Oracle Cloud updates have the potential to negatively impact your customizations, integrations, and custom reports, it is recommended that you should test them before applying to production. The updates are first applied in the test environment and customers are given two weeks’ time to perform regression testing. During this window, any anomalies can be highlighted to Oracle support team.
