Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Ashok
    BCEA Enabled Requisitions: How are they processed if created...
    Topic posted June 23, 2019 by AshokBlack Diamond: 60,000+ Points, tagged Budget/Encumbrance, Requisition Import, Requisition Processing, Requisition Web Services 
    58 Views, 1 Comment
    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.

     

    Comment