Posts

Posts

  • Ashok
    Requisition Import: Understanding how the parameter Error...24.8
    Topic posted April 12, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Requisition Import, Tip in Procurement > Self Service Procurement public
    Title:
    Requisition Import: Understanding how the parameter Error Processing works
    Summary:
    Requisition Import: What is the significance of the import parameter Error Processing?
    Content:

    Customers / Support

    This one is rather interesting. You would think obvious but I was answering a couple of forum posts / bugs on this recently. I thought it would not be a bad reminder on explaining an important feature in importing requisitions.

    Context:

    The customer in this case came to us with an issue that the system was disobeying their command on creating requisitions even when they had set Error Processing to All.

    Functionality:

    What does the import parameter Error Processing do?

    It determines how to create or not create requisitions when the system encounters any validation issues while processing requisition lines.

    What are the supported values for this parameter?

    The supported values are: All or Partial. 

    All indicates that the system will only create requisitions only if all the lines from the interface header pass validation

    Partial indicates that the system will create requisitions even if some lines from the interface header pass validation.

    Subtext:

    What customers and support  need to know are the following guiding principles:

    1. The import parameter Group By has a role to play in how this works

    2. If the Group By parameter is applied, then the system creates 'batches' of requisition headers under which to group requisition lines and then applies the value All or Partial.

    Let us discuss this with an example:

    When creating an import batch, let's say the customer provided a requisition header reference of 1 as the header interface id for example.

    Now using this reference, the customer has provided several lines all pointing to this id

    Let's assume (as was in the customer case I dealt with) that the import parameter Group By was set to Location (Deliver-to Location). This means the system will group all requisition lines with the same location and process them under one requisition header.

    Now imagine the batch imported contained multiple locations. Stands to reason multiple requisition header batches will be created, right?

    The customer in this case actually provided one location for ALL requisition lines but did not provide Location for ONE record.

    Customer expectation: It should fail all the lines and hence no requisitions ought to be imported

    Designed actual behavior: If the group by attribute does not contain a value, now that is not part of the set of requisition lines to be processed. So the system cannot possibly know the intent of the customer was to group it using the same location as all others.

    So the system processed all other lines into one header even though Error Processing was set to All and rejected this one line.

    We explained this to the customer and it was understood.

    Take away:

    Remember the correlation between Group By and Error Processing and when you find that the number of requisition headers created were less or more than you expected, this is one of the first things you can review to see how it might have done what it did.

    Let me know if this article helps / clearly understood. Would be happy to receive and implement feedback on this.

  • Ashok
    19A Bug Fix: Tax not calculated in certain cases when...15.0
    Topic posted January 20, 2019 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Requisition Import, Requisition Processing in Procurement > Self Service Procurement public
    Title:
    19A Bug Fix: Tax not calculated in certain cases when requisitions are created via FBDI
    Summary:
    Import requisitions in certain cases were not calculating taxes correctly. Now fixed.
    Content:

    Issue:

    Customer in this case was importing requisitions via FBDI. The customer provides values for some tax attributes. Note that the requisitions in these cases were imported in status 'Incomplete'. The user then opens the requisition from the UI. At this time, the bug is triggered. The issue is that the user provided tax attribute values are overridden by system defaulted values.

    NOTE: The customer provided Tax Classification Code in this specific use case.

    Resolution:

    Any attributes that are user provided in the FBDI template ought to be retained and tax computations ought to use those values. The fix achieves this requirement.

  • Ashok
    User Preferences not a source of Charge Account defaulting...25.0
    Topic posted December 8, 2018 by AshokBlack Diamond: 60,000+ Points, tagged FAQ, Requisition Import, Requisition Web Services, Tip in Procurement > Self Service Procurement public
    Title:
    User Preferences not a source of Charge Account defaulting during Requisition Import
    Summary:
    User Preferences not a source of Charge Account defaulting during Requisition Import
    Content:

    Customers and Support

    This has come up twice recently on forum posts. It might merit a reminder. As you know Charge Account derivation uses various sources. User Preferences is one of them. Note that if you are importing requisitions (either using FBDI Templates or the Web Service), the charge account defined on User Preferences will not be considered for defaulting purposes.

    We get asked this question as to why the charge account derivation either fails or ignores the charge account on user preferences.

    User preferences by definition and design is applicable for UI based charge account defaulting, not for backend services such as Web Service or Import Requisitions.

  • Ashok
    BCEA Enabled Requisitions: How are they processed if created...15.0
    Topic posted June 23, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Budget/Encumbrance, Requisition Import, Requisition Processing, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    BCEA Enabled Requisitions: How are they processed if created via Web Services
    Summary:
    How are BCEA enabled requisitions processed when created via Web Services
    Content:

    Customers / Support

    I am posting this article in the hopes that this will help triage some basic behavior related queries on Budgetary Control enabled requisitions created by the Purchase Requisitions Web Service (PRWS).

    Context:

    Recently, a customer had a flow where they were attempting to create a requisition through PRWS and were observing behavior on which they wanted more clarifications. Here is a summary of what they were attempting:

    a) Creating a requisition through PRWS

    b) DocumentStatusCode = Approved passed in the payload. In other words, creating requisitions in Status 'Approved'

    c) Requisition was BCEA enabled

    d) Some of these requisitions were Canceled after import due to Funds Reservation failure (In this case the customer had not opened the encumbrance period causing the failure)

    e) This was causing a reconciliation issue for them between the legacy system and Fusion (they would not be able to use the same Requisition Number)

    f) They expected the requisition to go into Status 'Rejected'. This was their requirement

    Analysis and Resolution:

    My colleague Mara provided very helpful details that I thought would be worth posting here as a reminder or primer to you as well.

    Summary:

    1. Some reasons for Funds Reservation failure to be aware of prior to invoking such processes: Budget period closed, Accounting period closed, Not enough funds available to reserve

    2. When importing legacy requisitions, customers need to remember that BCEA validations will be triggered during import without which you cannot import a requisition that is BCEA enabled

    3. If you want control in reprocessing a requisition in the event of a failure, import the requisition in Status 'Incomplete'. That way if approvals are then triggered, you can view the status of the approval and the failure reasons on the UI. You can even write an approval rule to autoapprove requisitions based on the attribute 'Interface Source Code'

    4. If you have ensured that all check points for BCEA enablement are fine, then and only then import a requisition in Status 'Approved'. This is because, the implication of importing it in such a status is that if BCEA fails, then the requisition is automatically set to Status 'Canceled', not rejected. As you can imagine, if you have suggested that these requisitions have been approved in the legacy system there is not a mechanism to override that choice as that would be confusing

    5. When a requisition is imported as mentioned in 4. and the requisition is canceled due to BCEA failures, 

    6. To analyze BCEA errors on such approved requisitions, you will need to run the following XCC reports in the order stated below:

    a) Budgetary Control Results for Batch Report 
    b) Budgetary Control Exception Analysis Report 

    Here is a link that explains these reports in more detail: https://docs.oracle.com/en/cloud/saas/financials/19b/ocuar/oracle-fusion-budgetary-control-reports.html#OCUAR1569886

    7. If the requisition is imported in status 'Incomplete' and then submitted for approval and is rejected due to BCEA failures, note that the Document History section of the requisition will display an error message with details on what failed in the requisition details

    8, Note that the customer also wanted to know if they can in  such cases disable budgetary control and import the requisitions and then turn them on. The guidance here is to be aware that this can be potentially risky. It is not advisable to do this if transactions have already been created with BCEA. Also note that if you turn the feature off, it only impacts new requisitions created. Existing ones that are using BCEA will continue to do so even if the feature is disabled.

    I would ask support and customers to review the information provided here carefully. Do let us know whether you found this useful and also share your own experiences and insights.

     

  • Lokeswara Raju Chamarti
    FBDI import for Requisitions - Preparer and Requester Email25.0
    Topic posted August 6, 2019 by Lokeswara Raju ChamartiBlue Ribbon: 750+ Points, tagged Create Requisition, Requisition Import in Procurement > Self Service Procurement public
    Title:
    FBDI import for Requisitions - Preparer and Requester Email
    Summary:
    Case sensitivity of email address for Preparer / Requester / Buyer in Requisition Import FBDI
    Content:

    The FBDI import for requisition import expect the email address to exactly match with the email address of employee with case. Expectation is that this should not be validated and matching has to happen case insensitive. Email address are not case sensitive and if the email address is sent with upper case / lower case, both will work in any email server. So the email address field should not be considered with case. 

    We have multiple systems and the user accounts don't have the exact same email address in all the systems. Our Cloud ERP has user address as First.Last@Company.com. The external system that send the Requisition information to Oracle Cloud has email address as first.last@company.com. This is causing the FBDI import of requisition to fail as the email address in the Preparer / Requester is not matching with ERP value.

    The email address match should not be case sensitive for any comparisions.

  • Ashok
    Update 19B: How to override agreement price on a Requisition75.0
    Topic posted April 21, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, How-To, Requisition Import, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    Update 19B: How to override agreement price on a Requisition
    Summary:
    How do you override the price from an agreement on a Purchase Requisition
    Content:

    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.

    Image:
  • Dev Thota
    What is the difference between Oracle ERP Cloud and EBS...55.0
    Topic posted December 13, 2018 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Budget/Encumbrance, Business Intelligence - BI, Create Requisition, FAQ, How-To, Internal Material Transfer, Inventory Cloud, Manage Procurement Catalog, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Requisition Web Services, Setup, Tip, Update Preparer and Requester, White Paper in Procurement > Self Service Procurement public
    Title:
    What is the difference between Oracle ERP Cloud and EBS tables in Procurement?
    Summary:
    What is the difference between Oracle ERP Cloud and EBS tables in Procurement?
    Content:

    Hi All,

    Please help me on this

    What is the difference between Oracle ERP Cloud and EBS tables in Procurement?

    Thanks,

    Dev Thota.

    Version:
    18 C
  • Dev Thota
    Auto Create Receipt in Fusion Oracle Procurement?45.0
    Topic posted September 26, 2018 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Budget/Encumbrance, Business Intelligence - BI, Create Requisition, FAQ, How-To, Internal Material Transfer, Inventory Cloud, Manage Procurement Catalog, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Requisition Web Services, Setup, Tip, Update Preparer and Requester, White Paper in Inventory and Logistics > Inventory public
    Title:
    Auto Create Receipt in Fusion Oracle Procurement?
    Summary:
    Auto Create Receipt in Fusion Oracle Procurement?
    Content:

    Hi,

    We have 100POs we don't need to create 100 receipts manually.

    Is there any option like run scheduled job to create automatically.

    Thanks,

    Dev Thota.

  • Ashok
    Oracle Self Service Procurement Cloud: Why can't I find...5.0
    Topic posted May 9, 2018 by AshokBlack Diamond: 60,000+ Points, tagged Create Requisition, FAQ, Requisition Import, Requisition Web Services, Tip in Procurement > Self Service Procurement public
    Title:
    Oracle Self Service Procurement Cloud: Why can't I find my Requisitions in the Process Requisitions page
    Summary:
    Why can't I find my Requisitions in the Process Requisitions page?
    Content:

    After submitting a requisition for approval, users expect it to be auto-approved and available for buyers in the Process Requisitions page. But sometimes this is not the case and buyers cannot find the requisition lines submitted by requesters.

    This article will help you identify the possible reasons why buyers cannot find requisition lines in the Process Requisitions page.

    A. The requisition could be rejected or canceled during the approval process. Only approved requisition lines are displayed in the Process Requisitions page.

    • For internally managed requisitions, you can verify the status of the requisition in the Manage Requisitions page
    • For externally managed requisitions, the output of the Purchase Request Web Service or the ESS program PDF error report should indicate whether your requisition was created successfully.

    NOTE: Externally managed requisitions are created as approved requisitions.

    B. The import process could have ended with errors. If you are using FBDI to import requisitions, then verify that there is no PDF report in the output of the requisition import ESS program. The PDF report contains the errors found during the import process. If the import process ended successfully, there should be a text file in the ESS output with the numbers of the requisitions that were created.

    C. The requisition line could have been placed on purchase order automatically. Use the View Requisitions or the Manage Orders page in Oracle Purchasing work area to verify whether the requisition line is on a purchase order. A requisition line placed on a purchase order will not be displayed in Process Requisitions page.

    D. The generate orders program is not set to run automatically after requisitions are created via FBDI or Purchase Request Web Service. In Fusion Setup and Maintenance, open the Configure Requisitioning Business Function for the requisitioning BU of your requisitions. Check the option "Create orders immediately after requisition import" to make sure that the Generate Orders program is executed after you create requisitions using FBDI or Purchase Request Web Service.

    NOTE: After setting up this option you might need to run the Generate Orders program from the Purchasing work area for requisitions previously created.

    E. The requisition line could be assigned to another buyer or not assigned to any buyer.

    A buyer that has full access to manage requisitions should be able to search for requisitions by Requisitioning BU in the Process Requisitions page. Leave the buyer search criteria blank in the search region to search for requisitions with any buyer and without a buyer assignment. Sort the page by Buyer descending to see the requisitions without a buyer on the top of the list.

    NOTE: For a buyer to have full access to manage requisitions, make sure the buyer has been granted the privilege Create Purchase Order from Requisitions.

    In addition, go to the Manage Procurement Agents page from the Purchasing work area and define the buyer as an agent for the Procurement BU you desire. In the Agent Access region, give full access to the Manage Requisitions action.

    F. In order to prevent requisitions from being created without a buyer and Procurement BU assignment, you can:

    • Define buyer assignment rules. From the Manage Buyer Assignment Rules in Oracle Purchasing work area, define buyer assignment rules for your business. If you define the rules after requisitions were created, you might need to run the Generate Orders program to see the requisition lines in the Process Requisitions page.
    • Enter a default buyer in the item definition for the deliver-to organization.
    • Enter a default buyer in the Configure Procurement Business Function page for the Procurement BU.

    For requisitions created via FBDI or Purchase Request Web Service, the Procurement BU can be either provided or derived. It is derived either from the supplier site, or from the buyer assignment rules, if not provided

  • Dev Thota
    Unable to create a receipt in my receipts?75.0
    Topic posted July 8, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Internal Material Transfer, Inventory Cloud, OTBI, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Tip in Inventory and Logistics > Inventory public
    Title:
    Unable to create a receipt in my receipts?
    Summary:
    Unable to create a receipt in my receipts?
    Content:

    Hi all,

    Unable to create a receipt in my receipts?

    PO created through work order(WO).

    Thanks,

    Dev Thota.

    Version:
    19B
    Image: