Skip navigation

Have you gone to a program, performed an inquiry only to be presented with the P00IO - I/O Limit Exceeded window?


The P00IO is related to the number of records that can be read at one time during an inquiry and this can be user defined …with limits.


UDC Table 00/IO holds program numbers and a value for the number of records that can be “read” during the inquiry.  So you may think that making this number as big a value as the field will hold would be a good, one time solution to prevent the P00IO from disrupting your future inquiries.  Well, it is not that simple.  Each program has coding to set the maximum usable digits that can be set in the UDC and if exceeded, the value you enter could be seen by the system as zero.


Here is an example. If you update UDC 00/IO with a value of 100,000 for a program that has a maximum usable digits value of 5, 100,000 will actually be seen as zero.  This is due to truncating 100,000 from the LEFT to reduce the number of digits to the number defined in the program.  In this example, the 6 digit ‘100,000’ value will be reduced by dropping the 1, resulting in ‘00,000’ so the P00IO will be presented for any inquiry in that program. In contrast, if you used 999,999 for the same program, this 6 digit value would drop the left most “9” resulting in a value of 99,999 so the inquiry should produce better results.


So prior to adding new programs to or adjusting existing values in UDC 00/IO, you need to know the maximum usable digits for that program. IO Limit Exceeded Due to Excessive Amount of Records F5 F6 (Doc ID 827483.1) provides details related to how you can search the program code to find the maximum usable digits for the program you are using. Having this information so the program can be properly defined will help you to avoid the P00IO window from popping up in your future inquiries.

Did you know you can automate the processing of transfer orders from beginning to end? Over the years, the World applications have been enhanced to accommodate the transfer order process to flow seamlessly, with little or no manual intervention required.


A transfer order is typically created to accommodate the transfer of stock items from one branch to another. The process begins at creation of the transfer order, which results in two separate orders, as follows:

  • A sales order, on which the customer reflects the demand branch (typically defined with an ‘ST’ order type)
  • A related purchase order, on which the supplier reflects the supply branch (typically defined with an ‘OT’ order type)


The ST and OT orders are processed individually, using the same applications you would typically use to process a standard sales or purchase order.


Listed below are the programs that have been enhanced to accommodate an automated process:

  • Batch Sales Order Creation (P40211Z). This program was enhanced as of the A9.3 release to allow for the batch creation of the sales transfer order (ST) AND the related purchase order (OT). Prior to this enhancement, you were required to create transfer orders using the interactive Transfer Order Entry program (P4242).
  • Shipment Confirmation (P4205). This program was enhanced in the A8.1 release to invoke the receipt routing process for the OT when you ship confirm the ST.
  • Batch Shipment Confirmation (P42051). This program was created in the A9.2 release to ship confirm quantities on existing sales order lines, in their entirety. You can use the program to ship confirm transfer orders in batch mode, and simultaneously initiate the receipt routing process for the related OTs.
  • The interactive and batch Voucher Match programs (P4314 and P470412). These programs were enhanced in the A9.3 release to recognize the AP Interface flag (P4314) designated for each line type in the Order Line Type Set Up program (P40205). The primary intent of the enhancement is to accommodate the transfer order process by closing out the OT without creating a voucher, as a voucher is typically unwarranted for the transfer order process.


You can fully automate the OT process, as follows

  1. Set up a one-step receipt route that serves to put items on the OT directly into stock when the ST ships.
  2. Set up a version of the interactive or batch ship confirm program (P4205 or P42051) to invoke the receipt route defined in step 1 for transfer orders.
  3. Set up and use a line type specifically for transfer orders, such that vouchers will not be created for the order line type.
  4. Utilize the Evaluated Receipts program (P43800, which calls P470412) to automatically close out OTs after they are received, with no resulting voucher.


For more information about the processes noted above, please see the following documents:


Transfer Orders (P4242/P42011z) - Document 626657.1     

FAQ: Transfer Orders - Document 1538476.1

Troubleshooting Transfer Orders and Direct Ship Orders - Document 1539701.1

EDI Inbound 850 Inbound Purchase Orders - Document 626765.1


Otherwise, if you need further assistance, please log a service request.

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.