Concolidation with RBATTP

[Former Member]

Hi

I am working on RBATP consolidation scenario. The output of the scenario is that Purch Reqs are generated to move the stock between supplying plants to a consolidation location from where it is sent to the end custoemer. The issue is with the scope of check. The client is against using Purch Reqs and Purchase Orders in the scope of check. This is because apart from GATP generated Purch Reqs and Purch Orders, there are external Purchase Reqs and Purchase Orders which are not reliable from ATP point of view. Is there any way to handle this situation. I could not find a way where in one could differentiate between the receipt elements generated due to GATP check and the ones which are externally created.

Thank You

Rajiv

[Former Member · Accepted solution]

Hi Rajiv,

Though the requisitions in PPDS, SNP and GATP are Preqs, the applications are different. Try to explore on this.

Also, for external Purchase Requisitions, you can use different document type and block these Preqs from coming to APO using CIF user exits.

If even this is not possible one more feasible solution can be use of direct delivery from supplying location. In this case, no purchase requisition will be created between original enquiry location and supplying location triggered thru RBATP.

Regards,

Bipin