Posts

Posts

  • Ashok
    Default of the Supplier Site Agreement in Purchase...15.0
    Topic posted Yesterday by AshokGold Crown: 30,000+ Points, tagged FAQ, How-To, Requisition Web Services, Setup in Procurement > Self Service Procurement public
    Title:
    Default of the Supplier Site Agreement in Purchase Requisitions
    Summary:
    How does the supplier site default to requisition lines
    Content:

    Business Context:

    We have recently seen a few customers observe that even though they change the supplier site on a blanket agreement, the new site is not defaulted to the requisition line.

    Analysis:

    Procurement agents create supplier purchase agreements and they can specify the client requisitioning business units that can purchase using the supplier agreement. Now, the agreement has several regions and tabs. In the main tab, the purpose of providing a supplier site is to determine certain default options such as currency, communication method, supplier acknowledgement, etc. It will default as the purchasing site in the control tab, if the procurement BU of the agreement is also a requisitioning BU. 

    Important: The supplier site in the main tab is not the site that defaults to the requisition in Self Service Procurement.

    Then where?

    On the Controls tab of the agreement, in the Business Unit Access region, you specify the client requisitioning BU and provide the supplier site, ship-to location, and bill-to location for requisitions and purchase orders created for these client business units.

    When you create requisitions in a requisitioning BU and use an agreement, the supplier and supplier site default from the agreement. The supplier site used in requisitions is the one defined in the Controls tab of the agreement for the client requisitioning BU that is active in the  Requisition's user's preferences.

    Important: When you do a change order in the agreement to change the site in the main tab, the site in the controls tab will not automatically change based on the site of the main tab. This is probably why these customers don't see their change reflected on their requisitions. So, if you want the new site to apply to your requisitions, you must make the same change in the Controls tab of the agreement as well.

    NOTE: 

    When the supplier has multiple sites, you can check the option Allow ordering from unassigned sites on the Controls tab of the agreement. This option will allow requesters to choose any valid supplier site in the requisitioning Business Unit when creating requisitions. This capability is enabled when ordering using a smart form with a CPA, or through the Enter Requisition Line page.

  • Kunal Dave
    Browsing Catalogs missing from Requisitions page: Shop by...3
    Topic posted July 2, 2019 by Kunal Dave, tagged Create Requisition, How-To, Manage Procurement Catalog, Requisition Processing, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    Browsing Catalogs missing from Requisitions page: Shop by Category - Top Categories,
    Summary:
    Not able to add catalogs to Requisitions Home Page
    Content:

    Not able to add catalogs to Requisitions Home Page using the Shop by Category or Top Categories section. Setup same as another environment where functionality is working. Please advise.

     

    Thanks,

    Kunal

  • Anas Marikkkar
    Purchase Requisition budget check for CAPEX purchases2
    Topic posted June 27, 2019 by Anas MarikkkarBronze Crown: 15,000+ 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
    Critical Bug Fix 19C: Requisitions can source Agreements...5.0
    Topic posted June 23, 2019 by AshokGold Crown: 30,000+ Points, tagged Requisition Web Services, Tip in Procurement > Self Service Procurement public
    Title:
    Critical Bug Fix 19C: Requisitions can source Agreements expiring on system date
    Summary:
    Allowing Agreements expiring on system date to be sourced on Requisitions
    Content:

    Customers / Support

    This has been a requirement that had previously caused issues for a few customers. This bug fix resolves the issues of disallowing agreements that are still valid as of the system date to be sourced onto requisitions.

    Business Problem:

    This customer used the shopping home page to search for a BPA backed item. In the search results, the system displayed the item and the relevant agreement reference. However, on adding to cart, the auto sourcing process removed the agreement. 

    Why? 

    The design did not consider agreements expiring the same day (end of day). It excluded the current day that resulted in the agreement not being sourced.

    Fix:

    The bug has been resolved. Now, if the user were to use the Enter Requisition Line flow or the Shopping flow, the system will source the agreement that expires on the same day (system date). An agreement is considered valid even if it expires on the system date as it is valid until the end of that date.

  • 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.

     

  • 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

  • MANISH KUMAR
    Mass Update for Requisition if lines are created from...1
    Topic posted May 21, 2019 by MANISH KUMARBlue Ribbon: 750+ Points, tagged Create Requisition, Requisition Processing, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    Mass Update for Requisition if lines are created from shopping cart and Requisition lines
    Summary:
    Mass Update for Requisition if lines are created from shopping cart and Requisition lines
    Content:

    I am unable to Mass update the suggested buyer if the requisition lines have come from Requisition line entry and catalog. In case lines only come form either shopping cart or requisition line entry then it works.

    How can we enable this functionality.

    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:
  • 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
  • Ashok
    Work Order Subtype usage in TAB Derivation for Requisitions3
    Topic posted February 28, 2019 by AshokGold Crown: 30,000+ Points, tagged How-To, Requisition Processing, Requisition Web Services in Procurement > Self Service Procurement public
    Title:
    Work Order Subtype usage in TAB Derivation for Requisitions
    Summary:
    How to use Work Order Subtype in TAB derivation for Requistions
    Content:

    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.