Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Ashok
    ESS Resiliency for Long Running Jobs - Import Requisitions
    Topic posted May 15, 2018 by AshokBlack Diamond: 60,000+ Points, last edited July 17, 2018, tagged How-To, Requisition Import 
    116 Views
    Title:
    ESS Resiliency for Long Running Jobs - Import Requisitions
    Summary:
    Fusion POR Cloud R13: ESS Resiliency for Long Running Jobs - Import Requisitions
    Content:

    ESS Resiliency for long running ESS Jobs

    Business Problem:

    There are critical ESS jobs (Import Requisitions for example), that run in a customer organization, which by their nature run for long periods of time. If such jobs were to encounter critical failures or system errors (either due to database issues or server related stoppages etc.), currently the process starts from the beginning rather than from where it last left off. This causes a lot of wastage in terms of time and infrastructure redundancies.

    Resolution: 

    In Release 13, Update 18B, as part of an Oracle-wide technical mandated improvement, the Import Requisitions ESS job has been enhanced. The enhancements are as follows:

    a) The restart will occur from the point of failure without having to reprocess the entire set of records
    b) Records previously processed are not processed again

    This is not a process change that is obvious to the user but rather a process improvement that is intrinsic to the ESS job itself. The system will start from the last stoppage point and continue instead of starting over. How this is achieved is by enabling processing records in groups we call chunks. Records are processed and committed in chunks so that those records do not then need to be processed again if there are system failures

    Implementation Considerations:

    With the introduction of this feature enhancement, the customer can also select the size of number of records to be considered for processing. The parameter Maximum Batch Size in the Import Requisitions process, which is set to 2500 out of the box, will be used as the default chunk size. However, the customer can modify this depending on their business requirements. What they modify this value to depends on how many records they process in a batch, and the time it takes to process those records in their environments.

    NOTE:
    This feature enhancement is applicable to the requisitions import process using the file based data import (FBDI) process. It does not apply to the Purchase Request Web Service feature.