cancel
Showing results for 
Search instead for 
Did you mean: 

POD not working as expected

Former Member
0 Kudos

Hello Everyone,

We have set up the POD process in our system as follows:

a) POD indicator for an item category, say NXX. We have also not set the automatic POD indicator for this item category.

b) POD indicator ticked in shipping tab of the customer master.

We are supposed to invoice the delivery only after we confirm POD using transaction VLPOD.

However, the system allows us to create the invoice without any check on the POD confirmation.

Could any of you help us with what could be the possible reason for this strange behavior ?

Cheers,

MR

Accepted Solutions (1)

Accepted Solutions (1)

eduardo_hinojosa
Active Contributor
0 Kudos

Hi

First, check if the value for VBUK-PDSTK (status POD) for this delivery is right.

If it's right, check in your copy rules from delivery to invoice if you are using a customer VOFM. If the answer is yes, compare with other VOFM (for instance 003, ie include LV60A003) and check if it is checking the value of PDSTK, for instance:

if vbuk-pdstk na ' C'.
     perform vbfs_hinzufuegen using '000000' '197' space space space.
.....

I hope this helps you

Regards

Eduardo

siva_vasireddy2
Active Contributor
0 Kudos

Hi,

   Edurado is right you need to check the routine-003 whether the coding related to POD is Commented  or you might be using difererent routine other than 003.

sivavasireddy

Former Member
0 Kudos

Hello Eduardo n Siva ,

We do not have any coding which checks for the VBUK status.  And even if it was coded, how can we explain the fact that it works for the same data under one user, whereas it does not work with another user id ?

Cheers,

Mr

eduardo_hinojosa
Active Contributor
0 Kudos

Hi

What routine are you using for the copy rules? Perhaps you are using a customer routine (see Note 327220 - VOFM function and its objects, part 2.2 Namespaces). If it's true, check the ABAP code.

Regards

Eduardo

Answers (1)

Answers (1)

Former Member
0 Kudos

Thank you Eduardo, but it seems to be one of those one-off glitches in the system.