Posts

Posts

  • Dev Thota
    Unable to create a receipt in my receipts?45.0
    Topic posted July 8, 2019 by Dev ThotaSilver Trophy: 7,500+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Internal Material Transfer, Inventory Cloud, OTBI, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Tip in 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:
  • Anas Marikkkar
    Purchase Requisition budget check for CAPEX purchases2
    Topic posted June 27, 2019 by Anas MarikkkarGold Medal: 3,500+ Points, tagged Budget/Encumbrance, Create Requisition, How-To, Requisition Import, Requisition Processing, Requisition Web Services, White Paper in Procurement > Self Service Procurement public
    Title:
    Purchase Requisition budget check for CAPEX purchases
    Summary:
    Budget needs to be checked for CAPEX Purchase
    Content:

    The client has a budget for every Capital Expenditure (CAPEX) . They track based on certain categories. For example vehicle budget. At the time of the request , amount  needs to be checked against the budget.

    When raising a purchase requisition the user normally enters the asset clearing account for the charge account. This is to ensure the FA clearing account selected in the process of asset addition.

    How to check the budget against the relevant account at the time of purchase requisition.

    Version:
    19B
  • Ashok
    BCEA Enabled Requisitions: How are they processed if created...15.0
    Topic posted June 23, 2019 by AshokGold Crown: 30,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.

     

  • Anil Nair
    Automate Catalog Administration in Procurement CatalogsAnswered3
    Topic posted May 23, 2019 by Anil NairBlue Ribbon: 750+ Points, tagged Agreement Loader, Create Requisition, FAQ, How-To, Manage Procurement Catalog, Requisition Import, Requisition Processing, Setup, Tip, White Paper in Procurement > Self Service Procurement public
    Title:
    Automate Catalog Administration in Procurement Catalogs
    Summary:
    Automate Catalog Administration in Procurement Catalogs
    Content:

    We have 1200+ contracts which will be imported as Contract Purchase Agreements and Blanket Purchase Agreements in Oracle.

    These contracts will further require to be setup as part of the catalog administration tasks i.e catalog (with exclusion rules) , smart forms and content zone with security (assigned to each user/group in content security). Since we have a high volume of contracts (CPA/BPA) we dont want to perform the catalog administration task setup manually as it will be take days to complete.

    Does the system provide any option to import these catalog setup tasks (e.g. FBDI, Adfdi template,etc)?

  • MANISH KUMAR
    Requisition Import from 3rd party Field service system1
    Topic posted May 21, 2019 by MANISH KUMARBlue Ribbon: 750+ Points, tagged Create Requisition, Requisition Import, Requisition Processing, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    Requisition Import from 3rd party Field service system
    Summary:
    Requisition Import from 3rd party Field service system
    Content:

    I need to understand the Requisition Import functionality and how can we import requisition from 3rd party field service system. These are the high level requirements:

    1. The Requisition should be created in incomplete status so that Controller has ability to modify it before it creates Purchase Order

    2. The Requisition should get appropriate BPA based on various condition e.g. need to have some custom logic to apply BPA ( because one BPA for Min-Max and other for manual requisition)

    3. The Buyer assignment should happen based on buyer assignment rule or org-item rule

     

    Regards,

    Manish

  • Ashok
    Update 19B: How to override agreement price on a Requisition75.0
    Topic posted April 21, 2019 by AshokGold Crown: 30,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:
  • Ashok
    Requisition Import: Understanding how the parameter Error...24.8
    Topic posted April 12, 2019 by AshokGold Crown: 30,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.

  • Mohammad Alhindawi
    Shipments Document Sequence1
    Topic posted March 11, 2019 by Mohammad AlhindawiRed Ribbon: 250+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, BI Publisher Reports, Budget/Encumbrance, Business Intelligence, Business Intelligence - BI, Create Requisition, FAQ, How-To, Internal Material Transfer, Intrastat, Inventory & Cost Management Analytics Cloud, Inventory Cloud, Manage Procurement Catalog, Public Sector, Requisition Import, Requisition Mobile, Requisition Processing, Requisition Web Services, SCM, Setup, Supply Chain Financial Orchestration, Supply Chain Orchestration, Tip, Update Preparer and Requester, White Paper in Logistics > Inventory public
    Title:
    Shipments Document Sequence
    Summary:
    Shipments Document Sequence
    Content:

    Hello,

     

    How can I set up or define a sequence for my shipment documents based on the business unit?

     

    Thank you.

    Version:
    Oracle Fusion Inventory Management Cloud Service
  • Dev Thota
    Is it possible to create dependency between DFF and category...35.0
    Topic posted January 31, 2019 by Dev ThotaSilver Trophy: 7,500+ Points, tagged Agreement Loader, Approvals, Approvals/Notification, Budget/Encumbrance, Business Intelligence - BI, Create Requisition, Internal Material Transfer, Requisition Import, Requisition Mobile, Requisition Processing in Procurement > Self Service Procurement public
    Title:
    Is it possible to create dependency between DFF and category name?
    Summary:
    Is it possible to create dependency between DFF and category name?
    Content:

    Hi all,

    Is it possible to create dependency between DFF and category name?

    Version:
    18 D
  • Ashok
    19A Bug Fix: Tax not calculated in certain cases when...15.0
    Topic posted January 20, 2019 by AshokGold Crown: 30,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.