Purchasing

Get Involved. Join the Conversation.

Topic

    Nagaraj VinayakaRao
    PO CLOSE SCHEDULE has a limitation of 5000 schedules (or...
    Topic posted October 31, 2019 by Nagaraj VinayakaRaoGreen Ribbon: 100+ Points, tagged Orders 
    68 Views, 13 Comments
    Title:
    PO CLOSE SCHEDULE has a limitation of 5000 schedules (or lines) in the spreadsheet.
    Summary:
    PO CLOSE SCHEDULE has a limitation of only 5000 schedules (or lines) in the spreadsheet. Clients in Retail industry have more than 5000 PO schedules to action on. Why this restriction?
    Content:

    Ability to close/Final close POs  through a spreadsheet is available in Fusion R13. CLOSE SCHEDULE SPREADSHEET has a limitation of 5000 schedules (or lines)  to action on in the spreadsheet. Clients in Retail industry have more than 5000 PO schedules to download and action on them.  Want to know WHY oracle has limited it to only 5000 lines? Why this restriction?

    As per Oracle help, there are options to create smaller batches of less than 5000 lines by selecting different criteria. However, downloading POs at one go and then action on them in the same spreadsheet would be easier to manage than to create multiple batches.

    Comment

     

    • Nitin Katare

      ADFDi itself has no additional limitations than what Excel has (1 million rows), but the different product implementations of ADFDi have its own certified limit. The "Close Purchase Order Schedules Using a Spreadsheet" feature (using ADFDi) in purchasing is certified for 5000 rows. Many products certify up to 5000 rows, but there is no 1 limit for all products - certified limits are based on performance due to the complexity of the business logic and is dependent on the product.

      • Nagaraj VinayakaRao

        Thanks Nitin. ER 27843777 logged to provide additional filters for this program. At status 22. Any idea when this fix will be released?

        • Nitin Katare

          Don't have a further update as of this time, will update once we have more information.

          • Pawan Gadade

            Hi Nitin,

            Good Day!

            We are facing this issue for longer time. At current stage this task is not able to proceed 1 day records (which is much less then the current capacity i.e. 5000 records)
            Could you please let us know if 20 A patch will resolve the issue and will work on at least 1 day records so we can run this task multiple times.

            Regards,
            Pawan

      • Alan Rowland

        Nitin, is this information readily available in one place or at least by product group (e,.g. SCM, ERP, etc.)?  This is a common question.  My organization and other spend too much time using the trial-and-error approach then logging SR's.

    • Pawan Gadade

      Hi Nitin,

      Good Day!

      For SR Number "SR 3-20656148211", could you please provide any update on this enhancement request.

      Regards,

      Pawan

      • Nitin Katare

        Hi Pawan

        Is the ask to process 300,000 PO schedules from closed to finally closed?

        If yes, I don't think this will be something that is supported. ADFDi is certified for up to 5000 PO schedules to be processed at a time. Are you having trouble with processing 5000 PO schedules?

        I am checking with development on the fix being referenced in the SR meanwhile.

        Regards

        Nitin

         

      • Swati Gupta

        Hi Pawan,

        Please confirm that you are talking about patch for bug fix 29368899 (which is not an enhancement request) to be released in 20A.

        Thanks,

        Swati

        • Pawan Gadade

          Hi Swati & Nitin,
          Good Day!

          At current stage this task is not able to proceed 1 day records (which is much less than the current capacity i.e. 5000 records). We tried to run this task for multiple times for single day duration but every time we received error stating "Unable run Close Schedule in Spreadsheet error- ORA-56720: I/O data limit exceeded - call abort"

          Please let us know if this bug/error will get resolved by release 20A. Even if it is working for 1 day we can run this task multiple time.

          Regards,

          Pawan