For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Customers / Support
I thought this article would serve two purposes:
a) Quick primer on functionality that exists in this regard prior to Update 19B
b) Feature as introduced in Update 19B.
Business Problem:
Customers have provided us business use cases where a standard agreement captures the price for a product or service at the outset of a negotiation but later, these prices may be re-negotiated by specific requesters. You could look at this problem in two dimensions:
a) Quantity based products or services
b) Amount based products or services
Solution:
As I assume many of you are aware, Fusion Self Service Procurement already allows requesters the ability to update the price in cases of an amount based requisition. In Update 19B, this functionality has been extended to include quantity based requisitions as well.
Here is a solution summary:
A. What is supported:
Requesters can modify the price on a requisition for both quantity and amount based lines.
B. Pre-requisites:
To avail of the feature introduced in Update 19B, we have introduced an Opt-in entitled: Override Agreement Price on Requisitions.
C. Who can update price:
Any requester with the job role: Procurement Requester can edit the price on a requisition provided the agreement allows it.
D. What flows are supported for these features:
You can update the price through the following flows:
1. Shopping flows through the UI
2. Enter Requisition Line flow through the UI
3. Using the FBDI template to import requisitions
4. Using the Purchase Request Web Service to create a requisition
5. Approver editing a requisition during the approval process
NOTE: The Purchase Requisition REST service does not support this feature at this time.
E. How does this feature work?
Once opted in, you can create an agreement (a blanket purchase agreement using Fusion Purchasing). You must ensure that the attribute Allow price override must be enabled for the agreement line that you create. Additionally, you can set a value for the attribute Price Limit. The value you set here is the maximum value up to which the requester may edit the price on the requisition line.
Once this configuration is complete, the next time a requester shops for the item or service, the system will enable the Price attribute for edit (See Screenshot 1 below). This screenshot describes how price is edited in a regular UI flow.
If you wish to enable this feature when using an FBDI template or the Purchase Request Web Service payload, you must provide a valid BPA reference in the template or the payload. If you don't and the system auto-sources an agreement, then the agreement price will prevail. This is important to remember.
F. Additional considerations:
1. The system will display an error message if you enter a price that is over the Price Limit value set in the agreement
2. You cannot enter Null or Blank as the price on the requisition line but you can enter 0
3. If the agreement is in a different currency than the functional currency, remember the price is updateable in that currency. So if the agreement is in EUR and the functional currency is USD, the requester changes the EUR price. This is current behavior but worth remembering.
4. The Opt-in for this feature expires in Update 19D. This means that the feature is automatically turned on and available to all requesters after the expiration.
Let us know if this article is helpful and if you have any questions or clarifications.
Hello,
How can I set up or define a sequence for my shipment documents based on the business unit?
Thank you.
Support / Customers
I am writing this article based on a recent customer issue that surfaced a need to communicate this behavior.
Business Problem:
The customer uses work order sub types to create work orders. In the recent 19A integration of Work Orders with Procurement, the customer creates a requisition using a work order destination type. The customer had also defined charge account derivation mapping sets using the work order sub type. However, the charge account on the requisition was not derived using the mapping set definition.
Analysis:
Work order sub type is used in TAB derivation rules to derive charge account. But the value for the sub type has to be captured in the transaction in question. In other words, when creating the requisition, there must be a value passed for this attribute for the application to then derive the charge account.
Conclusion:
1. Currently, the attribute Work Order sub type is only used in deriving charge account as part of our Purchase Requisitions Web Service when creating an externally managed requisition for an OSP (Outside Service Processing) item
2. When the user creates a work order based requisition through Self Service Procurement UIs, the work order sub type is not captured either explicitly or defaulted and so nothing is passed for charge account derivation. In other words, in the manual flows, sub type will not be used for charge account derivations
3. Even in the OSP scenario outlined in 1. above, please note that you must pass the value of the CODE for the sub type and not the sub type name. (See attached screenshot). This is another thing to take note of that will help you derive the charge account based on this mapping set.
4. There is an enhancement recorded for the scenario outlined in 2. above, but there are no timelines or plans at this point to design and implement this. If you require this to be supported, please log an idea in the Idea forum as per the process we follow for any enhancements that you wish to bring to our notice.
Recently, some customers could not upload attachments to requisition due to the error:
"User do not have access to upload attachment for Entity: POR_REQUISITION_HEADERS".
In order to have access to the upload attachment service operation, and to the requisition entities, the user that can perform the operation should be granted the following duty roles:
Role Name: ORA_FUN_FSCM_LOAD_INTERFACE_ADMIN_DUTY, FSCM Load Interface Administration
Role Description: Manages load interface file for import.
Role Name: ORA_POR_REQUISITION_SELF_SERVICE_USER_DUTY, Requisition Self Service User
Role Description: Manages requisitions including creating, searching, and viewing requisitions, creating Non Catalog requests,
creating requisitions with one-time locations, and changing deliver-to locations on requisition lines.
NOTE: Our white paper Uploading Attachments to Requisitions Using ERP Object Attachment Service was fixed accordingly, and it is uploaded with this article for your reference.
Context:
In a drop ship flow, there were some changes made on the sales order configuration that caused a requisition that was already in process for that order to go on hold. This happens because the DOO team blocks changes to order lines that have a status of Requisition Created. However, due to some exception use cases, the changes on the order line could not be blocked and consequently, the requisition lines went on hold.
Now, when this happens, a purchase order, as is obvious, cannot be created for that requisition line. This means the flow is essentially blocked. Prior to the solution discussed in this article, for such unforeseen cases data fix was being implemented. These are not recommended or suitable for recurring scenarios.
Solution:
This article provides Support and Customers an easy way to release the hold on the requisition line. This frees up the requisition for further processing and the corresponding order orchestration flow to continue as deemed necessary. The attached word document provides you a detailed step by step description of how this needs to be achieved.
Please take a read.
NOTE:
Please note that Support has also published a KM Note on this topic. Here is the link:
How To Use Purchase Request Web Service To Release Hold On Drop Ship Purchase Requisition Line (Doc ID 2503692.1)
Customer / Support
There is recent fix in 19A that I wished to communicate through this article.
Issue:
Planning system (Planned order releases from Planning Central for instance) tend to have thousands of lines on a requisition. Up until this fix, the system would only process the first 500 lines through approval while the remainder of the lines would stay in Pending Approval.
Fix:
With this fix, such external requisitions containing up to 10000 lines can be processed successfully. The limit has been changed from 500 to 10000.
We get asked this question quite often from support for customers. Even as recently as yesterday, this was discussed on a customer post. I thought it fit to provide this information for support to share the next time this comes up as a customer query.
Url added on smartform setup. however, no preview is displayed. See attached.
url used: https://goo.gl/images/8EPno8
On the requisition page, no image displayed rather the smartform text link is displayed twice (Recent Purchase and Recently Viewed')
Shouldn't it display image under 'Request Forms' section?
Dear,
Our client is Hospital, and they don't to allow to the user to change the location and requester name in the purchase requisition preference screen.
How the user will be restricted to select the specific locations on PR preference and he cannot change requster name.
Hi,
We are planning to use purchase request web service for inbound integration with an upstream application. While it meets most of our requirements, we are not able to use it for creating requisitions with a one time address. We found that the 'address type' attribute (one time/internal) and the address attributes are not part of the web service payload. Is this not supported yet? If not, it is planned for a future release ?
Thanks & Regards,
Mohanish
Hi All,
Please help me on this
What is the difference between Oracle ERP Cloud and EBS tables in Procurement?
Thanks,
Dev Thota.