cancel
Showing results for 
Search instead for 
Did you mean: 

Deleted PO still print out

fisher_li
Participant
0 Kudos

Hey, PO gurus,

If I create a single line item PO in our Dev environment and put it on hold immediately without saving it.

Go back and delete the line item and then save it, the PO will not print (the print will failed in message screen) which is what we want.

But when I do the same steps in our QA, the deleted PO will print automatically.

Is there any program/config that I need to check to see why the PO print function acts differently?

Thanks in advance!

Fisher Li

Accepted Solutions (0)

Answers (2)

Answers (2)

fisher_li
Participant
0 Kudos

It turned out that we had a "commit work" statement in user EXIT to cause this problem.

Fisher

maruti1
Explorer
0 Kudos

Hello ,

In my case i need to get o/p of a deleted PO ( PO deleted with all line items) . can you let me know what were the setting with which you were able to print o/p of deleted PO in QA.

Thnaks,

Maruti

brad_bohn
Active Contributor
0 Kudos

Check your determination analysis (Goto -> Determination Analysis) and view the analysis difference for your output type in both environments. Most likely you have a different requirement assigned or the code in the same requirement is different. You can also check the output config in transaction NACE for application 'EF'.

Former Member
0 Kudos

Hi,

I think u can have the condtion

EKKO-LOEKZ NE 'L' to get only existing po

ekpo-loekz NE 'L' to get only existing line items in po

Try this

Regards

Edited by: Rasheed salman on Jan 5, 2010 6:05 AM

fisher_li
Participant
0 Kudos

Brad,

Thank you for your help!

I checked the "Go to -> Determin, analysis" and there was no analysis available in our system.

I also checked the config in T code NACE and the config are the same in both Dev and QA.

There must be something that I overlooked, so the PO print out acted differently between Dev and QA.

Fisher

fisher_li
Participant
0 Kudos

Rasheed,

Thank you for replying my question.

Since the system do exactly what we want in our Dev environment but not in our QA environment, so I prefered find out what made the difference before I make any program change.

Fisher