debugging routine for output type in purchase order

[Former Member]

HI all,

I am unable to get breakpoint to stop at a custom requirement routine for a custom output type (ZSND) for purchase order.

I created routine 901 and explicitly add 'break userid' . In ME21N, it stops at the routine. In ME22N, it did not stop at the routine.

I like to it stop during ME22N. I tried adding the custom output in ME22N in Messages details, then save. It still did not stop at the custom routine. Can anyone pls shed lights how i can make it stop ? Or could it be that no output is generated during the ME22N changes, thus it would stop at that routine in ME22N ?

thanks

Joyce

[Former Member]

No, you can't manually add an output and expect the requirement to trigger. Requirements are ONLY triggered during automatic processing. When you add an output manually, you are effectively saying 'I don't care what the config says - process this output type'.

[uwe_schieferstein]

Hello Joyce

The first output ZSND creates the ORDERS IDoc (ME21N). For this output type you obviously have assigned the VOFM condition (somewhere in the NACE transaction).

Changing the purchase order (ME22N) should create a different output type (-> ORDCHG IDoc). The first output ZSND must not be repeated (or it is defined to be set automatically only once).

Thus, there are two explanations for your observation:

(1) The output ZSND is not created a second time using ME22N

(2) The new output (-> ORDCHG) has not been assigned to the VOFM condition 901.

(1) you can test quite easily by adding the ZSND output manually in transaction ME22N.

(2) you need to check the output customizing.

Regards

Uwe

[Former Member]

Hi Uwe,

If i add the ZSND output manually in ME22n, the email will be send. I don;t use IDOC for the purchase order. Do you mean i have to create another output for ME22N and assign 901 to it ?

thanks

Joyce

[uwe_schieferstein]

Hello Joyce

Whether you send a newly created purchase order via IDoc or e-mail to your supplier does not matter yet this (EDI) output should be generated only once. Otherwise the supplier will receive the same purchase order twice.

Thus, when you change you PO (ME22N) you should have a different output (for PO change). It is important that the supplier must be able to distinguish between a new PO and a changed PO.

Finally, for this second output you have to assign you VOFM condition 901 like you did for the first output.

Regards

Uwe

[Former Member]

Hi Uwe,

Thanks for the info. I did not create another output for change.

Joyce

[brad_bohn]

No, you can't manually add an output and expect the requirement to trigger. Requirements are ONLY triggered during automatic processing. When you add an output manually, you are effectively saying 'I don't care what the config says - process this output type'.

[Former Member]

HI Brad,

Thanks for your helpful explaination. Is there a way for my program to add the output automatically ?

[Former Member]

Thank you to everyone who replied.