adobe captivate - oracle · web vieworacle fusion middleware provides infrastructure for soa...

Adobe Captivate Thursday, May 25, 2023

Slide 3 - Oracle Procurement Cloud Release 11

Slide notes

Hello, my name is Kim. Welcome to training for Release 11. In this session we will talk what’s coming in Oracle Procurement Cloud for Supply Chain Integration with Fusion Procurement.

Notes

of 19


Slide 4 - Agenda

Slide notesFor the enhancements covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Next, we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

of 19


Slide 5 - Enhancements Overview

Slide notesWe begin with an overview. At a high level, this solution provides organizations the ability to manage their supply chain integrations to Fusion Procurement more easily and efficiently.

The new Purchase Request web service, provides the ability for external applications to send requests to Fusion Procurement in the form of create, change, control , and get operations. This service is a wrapper for both the requisition and purchase order documents. The purpose of this web services is to eliminate the need for external systems such as order fulfillment or supply execution from having to determine which procurement object, requisition or purchase order, needs to be accessed. The web service will internally determine if action is needed on a requisition or purchase order. The Purchase Request web service supports both fusion to fusion and 3rd Party to fusion integration.

Procurement is leveraging the Service Oriented Architecture (or SOA) and the business events model for supply chain integration. SOA s a well recognized industry term and approach to application development characterized by encapsulation of individual product components and support for standards-based integration protocols. Oracle Fusion Middleware provides infrastructure for SOA development through the Fusion SOA Suite.

Business events are typically a one-way, fire-and-forget, asynchronous way to send a notification of a business occurrence. Other systems within the infrastructure can listen for these events and take action. For example, when a purchase order is implemented, Procurement will raise a Purchase Request business event.

Procurement is planning to publish the following web services for fusion to fusion and 3rd party to fusion integration:

• Create Purchase Request (Create, Populate Submit Operations)

• Change Purchase Request (Change, Cancel, Split Actions)

• Control Purchase Request (Hold, Freeze, Firm Actions)

• And Get Purchase Request

of 19


Procurement is planning to publish the following business events for fusion to fusion integration:

• Purchase Order Implemented

• Purchase Order Change Order Implemented

• Purchase order Change Order Rescinded

• Requisition Line Canceled

• Finally, Requisition Line Split

Notes

of 19


Slide 6 - Create Purchase Request

Slide notesNext, we will go into the details of the creation flow using the purchase request web service. The Purchase Request web service supports two different create options:

• Populate and Submit

• And Create

The Populate operation is for when integrating applications, like planning, have a high volume of supply requests which may have as many as 10K requests for a single batch. The caller can call the purchase request web service with this operation multiple times to populate the interface table with the data to create requisitions. Once the interface table is fully loaded, the calling application must call the Purchase Request web service with the Submit operation.

The Submit operation kicks off the requisition import process to complete the creation of the requisition with the data from the interface table. Calling applications should first load the interface table using the Populate operation and then call the Purchase Request web service with the Submit operation.

The Create operation combines 1 and 2. It will write the attributes into the requisition interface tables, and then kick off the Requisition Import process to complete the creation of requisitions. The Requisition Import process will then perform the necessary derivation and validation logic on the requisition.

Procurement is introducing a new indicator identifying if a requisition is externally or internally managed in Procurement. This indicator is specified by the originating party during requisition creation process through the create purchase request web service. All requisitions created within Self-Service Procurement will be internally managed.

Included is a high level summary of the Self-Service Procurement impacts with the new externally managed flag:

• Externally managed requisitions can be created through the purchase request web service or requisition import.

• Internally managed requisitions can be created through the Self-Service Procurement UI, purchase request web service, or requisition import.

• Externally managed requisitions will be created with an approval status of ‘Approved’.

of 19


• Externally managed requisitions are not viewable in Self-Service Procurement.

• Internally managed requisitions are viewable in Self-Service Procurement.

• Finally, internally and externally managed requisitions are viewable in the Purchasing Process Requisitions UI.

Notes

of 19


Slide 7 - Change Purchase Request

Slide notesNext, we will talk about the Change Purchase Request Operation.

To change, cancel, or split a previously raised purchase request, Integrating applications should call the ‘Purchase Request Service Change Operation’. The purchase request service will receive requests for changes and determine whether the request should be applied to the requisition or purchase order.

• Requisitions will support the action: Cancel.

• And Purchase Orders will support the actions: Change, Cancel, and Split.

The web service call can perform a mix and match of the different action types in one operation (ex: cancel and change) and therefore one change order similar to what is possible from the UI.

For changes to a purchase order it will be all or none per purchase order. Changed schedules are being grouped into a change order for the purchase order and they all must pass for the change order to be successful. For cancellations to a requisition it will be per requisition line. If the requisition line passes, the cancellation will be processed regardless if other requisition lines for the same requisition fail.

The change action for the purchase order schedule includes increasing or decreasing Quantity Ordered, moving in our out Requested Delivery Dates, changing Ship-to Locations, changing Attachments, and changing other additional attributes.

The split action will be accomplished by using the split action, specifying a parent schedule, and specifying the data for the new schedule in the input payload. The service will copy the parent schedule and then update the new schedule with the updated data from the input schema. In order to update the original or parent schedule, the integrating application should also call the change operation with the change action to update the original schedule. The integrating application might want to update the original schedule reducing the quantity and specifying a different Requested Ship Date.

In the case of the cancel action, if the requisition line has yet to be placed onto a purchase order, the requisition line will be canceled. If the requisition line has been placed onto a draft purchase order, the draft purchase order schedule will be cancelled or deleted and then the requisition line will be canceled. If the requisition line has been placed on an implemented purchase order, the purchase order schedule and backing requisition line will be canceled.

of 19


Slide 8 - Control Purchase Request

Slide notesNext, we will discuss the Purchase Request Control Operation.

To hold/freeze, release hold/unfreeze, firm, or undo a firm on a previous raised purchase request, Integrating applications should call the ‘Purchase Request Service Control Operation’. The Purchase Request Service will receive requests for performing the control action and determine whether the request should be applied to the requisition or purchase order.

For the hold/freeze request:

• Requisition lines will be removed from the requisition pool.

• Draft purchase orders will be deleted/cancelled and backing requisition lines will be removed from the requisition pool.

• Finally, implemented purchase order will be placed on hold and frozen (a change order is not created). This will prevent changes to the purchase order, invoicing, and receiving.

For the release hold/unfreeze request:

• Requisition lines will be placed back in the requisition pool.

• And implemented purchase orders will be released from hold and unfrozen. This will allow changes to the purchase order, invoicing, and receiving.

For the firm/undo firm request:

• This action is not supported for requisition lines.

• And the purchase order schedule will be firmed or the firm will be undone. Firm prevents Planning from suggesting reschedules or cancellations to the firmed purchase order.

Please note that both Hold/Freeze and the Firm/Undo Firm actions are supported through the change operation as well. This allows integrating applications to make a single call to the change operation if they need to perform a control and change action at the same time.

of 19


Notes

of 19


Slide 9 - Get Purchase Request

Slide notesThe last operation we will discuss is the Purchase Request Get Operation.

The integrating applications should call the ‘Purchase Request Service Get Operation’ to get the latest purchase request details. This service will return a flattened view of the purchase order header, line, and schedule which contains all of the information relevant to integrating applications.

Included are some key points about this operation:

• The Requisition Header ID must be passed in.

• If a PO Header ID is passed in, this operation will return all Purchase Order Schedules for the PO Header ID and Requisition Header ID.

• If a PO Schedule ID is passed in, this operation will return a single Purchase Order Schedule.

• Finally, If a Change Order Sequence is passed in, we return only Purchase Order Schedules that have changed between the Change Order Sequence that is passed in and the latest Purchase Order Change Order.

Notes

of 19


Slide 10 - Purchase Request Events

Slide notesNext, we will talk about the Purchase Request Event.

Business events are typically a one-way, fire-and-forget, asynchronous way to send a notification of a business occurrence. Other systems within the infrastructure can listen for these events and take action. After Procurement publishes a business event that an integrating application subscribes to, the integration application can call the Purchase Request Service Get Operation to obtain additional information about this business event that is not in the event payload.

The integrating Fusion applications listen to Purchase Request events for the following functionality:

• Purchase Order Implemented

• Purchase Order CO Implemented

• Purchase Order CO Rescinded

• Requisition Line Canceled

• Finally, Requisition Line Split

Notes

of 19


Slide 11 - Purchase Request Web Service and Events

Slide notesNow, let us talk about the business values that these enhancements bring.

The Purchase Request Web Service and Events model provides organizations the ability to manage their Supply Chain Integration to Fusion Procurement easily and more efficiently.

Supply Chain Integrations which are optimized include drop shipments, back to back orders, inventory replenishment, planned orders, contract manufacturing, and configure to order.

Notes

of 19


Slide 12 - Summary of Enhancement Capabilities

Slide notesHere is the summary of the features I have talked about today:

• The create purchase request web service allows integrating applications to create approved requisition lines.

• The change purchase request web service allows integrating applications to change, split, and cancel purchase order schedules and cancel approved requisition lines.

• The control purchase request web service allows integrating applications to firm purchase order schedule, hold an freeze purchase order schedules and lines.

• The get purchase request web service allows integrating applications to get all or only changed purchase order schedules.

• Finally, the purchase request events allow integrating applications to be notified of business events of interest.

Notes

of 19


Slide 13 - Implementation Advice

Slide notesIn this implementation advice section we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

of 19


Slide 14 - Feature Impact Guidelines

Slide notesHere you can see the key upgrade information for the new features covered in this training. It details:

• If a feature is automatically available after the upgrade

• Finally if a feature can be accessed using the shipped job roles – the exact job roles are detailed later in this section

Notes

of 19


Slide 15 - Job Roles

Slide notesHere you can see the shipped job roles that will access the new capabilities covered in this training.

Notes

of 19


Slide 16 - Additional Information

Slide notesOracle Enterprise Repository is used by technical integrators for services or for project planning for integrating with services. It accessible inside and outside the firewall at the above location.

Notes

of 19


Slide 17 - Business Process Model Information

Slide notesThe business processes associated with the new capabilities covered in this training are detailed here.

The high level business process is Procurement with activities Create Requisition, Amend Requisition, Create Purchase Order, Amend Purchase Order, and Manage Purchase Order Lifecycle.

Notes

of 19


Slide 18 - Associated Release Training

Slide notesThe other training module that is related to these new capabilities and are recommended viewing is Service Events Enhancements.

This concludes this presentation. Thank you for listening. You can pause and rewind any of these slides if you require additional time to take in the detail.

Notes

of 19

adobe captivate - oracle · web vieworacle fusion middleware provides infrastructure for soa...

Documents