Contract PO's

[Former Member]

Hi all,

I'm a Abaper need to know something about Contract P.O's.I've got a requirement were in some sales order wont be having P.O's.The general Sales order are fetched from vbak table and based on this sales doc. we'll be fetching Documents for P.O's, Delivery & Invoices by giving VBTYP_N as 'V', 'J', 'M' and the status of each is varified like how many have been invoiced or GR or G.I we'll find this individually in the logic

But i've been told that we some times have no P.O's and we need to get contract P.O's.....For this we can just give VBTYP_N = 'G'. By this we can simply get contract po right.....and we can also check in T.code VA43.....for contract S.O's.....but i just want to know how this contract P.O are different form general P.O's in business terms......and most important thing is do this contract P.O have different status compare to the general P.O's......Please let me know this for going further in changing the logic......

Functionally i'm very poor please let me know what this is all about with an example........Pointe wud be surely rewarded.............

[Former Member · Accepted solution]

Hi

PO is purchase order and in VBFA doc type = V where in contract it is G.

Contract are the obligation to customer to give some units in specific time duration.

Generally flow will be like this for contracts:

Contracts --> SO for X units --> PO for X units --> Delivery for X units --> Invoice for X units.

Contract qty decreased by X units.

But in normal sales where in customer is not a regular purchaser it wil be

SO for X units --> PO for X units --> Delivery for X units --> Invoice for X units.

Hope this helps to understand better. Reward pts accordingly.

Kind Regards

Sandeep