cancel
Showing results for 
Search instead for 
Did you mean: 

Pur Rqs hopping over to next bucket at creation

Private_Member_738444
Participant
0 Kudos

Hi Folks,

I am trying to manually create a Purchase Requisition in APO.

For this I enter the required quantity in the "Distribution Receipts (Planned)" field in the Planning book.

Under ideal circumstances this should create an order in the same bucket, as the one I entered & the order gets assigned to the External Vendor (it picks the lane from 'External Procurement Relationship' maintained for this Vendor.

Unfortunately it's not behaving the standard way

Instead it is creating an order, but in the immediate next bucket!! Why?

Why is the order hopping to the next bucket?

Any hint to this peculiar behavior would be deeply appreciated.

I have tried & checked the master-data, external procurement relationships & t-lanes, but failed to nail any suspect.

This behaviour is currently being observed only in the Production systems.

The simulation systems created a Pur.Rqs for similar exercise, without any bucket hopping.


Regards

Kumar


Accepted Solutions (0)

Answers (1)

Answers (1)

Private_Member_738444
Participant
0 Kudos

Hi folks,

Please share some pointers to this long pending issue

Thanks

Kumar

former_member187488
Active Contributor
0 Kudos

Hello Kumar,

Without checking the system, it would be hard to know the exact reason.

Basicly it should because of scheduling. Maybe you can follow the below logic and check your system setting.

1)Set the end date/time of STO

  - End date is set according to period factor in product master

  - End time is set to 12:00:00

2)Backward scheduling, on the GI/GR time and transportation duration, to determine the start date/time.

  - GR Start (Shipping End) = STO End - GR duration

    This considers receiving calendar of the target location

  - Shipping Start (GI End) = Shipping End - Transportation duration

    This considers transpt. calendar for the transportation lane

  - GI Start = Shipping Start - GI duration

    This considers shipping calendar of the source location

3)If start date/time is not working time, find the most recent working date/time (backwards) to be the final start date/time.

4)If start time is not 12;00:00, it will get adjusted to the most recent 12:00:00 backwards.

5)Forward scheduling from the final start date/time, calculating the final delivery end date/time.

  - This is the reverse of backward scheduling

  - The result of final delivery date/time may be different than 1).

Besides, the system will also consider resource calendar. For GR/GI activity, it will consider handling-in/ handling-out resource assigned to the target/source location.. For transportation activity, it will consider transportation resource assigned to transportation lane. (Only resource calendar is considered, reource availability will not be considered.)

Best Regards,

Ada