Skip to Content
avatar image
Former Member

planned order range

Dear Experts

when  i  am generating planned order from apo it is not matching with my current number .

In T-code : /n/SAPAPO/RRPC1 and it is also not matching from ECC number range OMI3 or OMI2 .

is there any other setting to mantain number range in APO.

Regards

jaisree

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 24, 2015 at 11:47 AM

    Hi Jaisree,

    Could you please explain your issue in detail. Some screenshots will help a lot.

    Do you expect your PO number should followed by the previous PO ? There could be some other process running in parallel which may also create orders, please have a check

    PO which are created in APO holds the Temp number, when it transfered to ECC (CIF) a real PO number will be created and same will be sent to APO (CIF) again which replaces the Temp PO number.

    Regards

    Vinoth

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Jaisree,

      As i said earlier, your system must be using main memory buffering for number ranges.

      Main memory buffering

      You may only set the main memory buffering if no legal requirement applies to the number assignment. You can display the buffer contents of the main memory using transaction SM56.

      Only use this for financial accounting documents after consulting the user department.

      Advantages:

      - A lock is temporarily set on the NRIV table when a new buffer is requested. (see Note 920234).

      - Avoiding performance problems

      Disadvantages:

      - Gaps may still exist

      - Gaps cannot be documented

      - The numbers are not assigned chronologically.

      You should deactivate the Number range Buffering.

      No buffering

      No buffering should only be set if required for legal reasons.

      Advantages:

      - The number assignment does not contain any gaps.

      - The numbers are assigned chronologically.

      Disadvantages:

      - Performance problems may occur, since a number is assigned in each case and the table remains locked until the next COMMIT or ROLLBACK.

      - You cannot request numbers in parallel.

      Check with your Basis Team on this.

      Its standard behavior of the system to created orders without continued numbers. Whats the business need for PO numbers to be continuous.

      - Vinoth

  • Aug 25, 2015 at 09:15 AM

    Hello,

    IN /SAPAPO/RRPCUST1 Number Range Number is same as /SAPAPO/RRPC1

    Also check Use number range   = X set there.

    For the global parameters and default values (Transaction /SAPAPO/RRPCUST1) you must make a setting that number ranges should be used. Furthermore, a number range number must be set there.

    The number range itself must then be set in the section 'Maintain number ranges' (Transaction /SAPAPO/RRPC1)

    Best Regards,

    R.Brahmankar

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member R Brahmankar

      Dear all

      Do we can have difference in number of digits in planned order no in ECC vs APO.

      Because we have 6 digit planned order in ecc where as in apo it is 8 digit number .

      But my planned order is 8 digit in product view .so how can i confirm that my planned order is transffering to ecc

      Regards

      Jaisree