Return Po Quantity is more than actual Po quantity

[Former Member]

Hi All,

While creating Return STO PO the quantity is allowing more then normal STO Po quantity.

Example :

1.Sto PO qty : 10, obd :10 qty, pgi :10 qty, migo :10 qty, miro :10 qty...

Return Sto PO :

1. Return sto po : 15 qty ( system allowing to create more quantity). obd : 15 qty. pgi : 15 qty and migo : 15 qty ( If the material is having stock, we can create GR, if the material don't have stock its giving general error like don't have stock in plant)..

Please help on this..

Thanks

[former_member183424]

Yes, the scenario is fine. There are no relation between normal STO PO and return STO PO (quite same like normal PO and return PO), both are different process, different document and they are not linked to each other.

[Former Member]

Hi dibyendu,

Thanks for your quick reply, Please suggest me how to control this...is there any configuration settings or any other way.

Thanks 

[former_member183424]

There are no standard configuration as I have said there are no between these two documents.

You may can check flexible development. You need to link up the old STO PO at the time return STO PO creation. Use a Z field in PO screen and enter the old STO PO number during return STO PO creation and use badi ME_PROCESS_PO_CUST to compare the quantity (all others as per your requirement) with regards to the old STO PO. Then show a message as per your requirement. You need to consult with your ABAP team to do the same.

[BijayKumarBarik]

Hi,

How Return PO Quantity is more than actual PO quantity which is Logically incorrect and Prohibited by any business unit

If vendor supply 10 quantities with all purchasing conditions and you receive it. Later you find all 10 quantities not upto marks- you can go for return delivery or if the same 10 quantities stored long time- you can go for Return PO with 10 quantities only not with 15 quantities.

Refer on return process with movement types

Regards,

Biju K

[madhava_hn]

Hi Kishore,

What is the business necessity for return PO over return delivery?

Why you are not crating return delivery for the STO with 122  and why you are going for return PO(161)?

If you are OK with return delivery, then go ahead with movement type 122, where you can refer the standard (previous) PO.

Otherwise you may have go for new development, what you are facing is the normal behavior.

[Former Member]

most likely, a business process in which the trigger of return purchase order/delivery must be initiated at the procurement level or a gap between the actual delivery versus the current situation.

Regards,

[Former Member]

Hi Kishore,

As you mentioned you are taking the sales order number in collective number field which is at header level but the quantity is captured against the line item level, So you may need to add Z field in EKPO and update the actual po with line item in field and validate the before save.

Rgds,

Nayeem.

[PollyGan]

Hi,

There's no relationship between PO and return PO. Considering:
1. PO with 10
2. PO2 with 10
3. return with 15

This is totally reasonable.

Best regards,
Polly

[Former Member]

Hi polly,

Thanks for reply..When we are creating a return po, we are taking original sales invoice number as reference in return po screen (collective number field)..if this is the case, how can we go on this..pls suggest.

Thanks

[PollyGan]

Hi, I don't see the function in standard. The BAdI mentioned by Diyendu might be feasible approach. Best regards, Polly