Po Print output Type is generating Print output type for version and non version fields

[Former Member]

Hi Gurus

I am facing an issue, We have release startergy and version management. Which is working as per our requirement. All the condition records are maintained as per the requirement. The multiple issue has been ticked in the message type configuration of the PO. Now the problem is:

1. when we make a change in the PO, which is version relevant field, the output is triggered and after release it is processed succesfully with green ikon.

2. When we make a changein the PO for a non version relevant field , again when i check the messages it is triggering a new output type but when saving it it is turning into red"No print relevant changes to Document exists for XXXXX".

Note: I have maintained the logica printer destination and kept the 4- print immediately option.

Long time back when i was checking the PO's it was working perfectly where the output type is only triggered when version relevant field is there and wont generateoutput type when non version relevant field is changed.Any information on this will be highly appreciated.

[BijayKumarBarik]

Hi,

Find your PDF/Smartform for your purchase order output type(message type) by using  t.code: NACE, Application EF -> Output types  > select your PO message type and find PDF/Smartform assign to it.

Now discuss with ABAPer and find logic designed " Purchase Order Print" with your PDF/Smartform in t.code: SMARTFORMS.

Regards,

Biju K

[Former Member]

Hi Bijay

The Version and Release Stratergy are working fine.The configuration for Version Management, Release Strategy and the PO Print Output Configuration are perfect.The assigning of the Z Purchase Order Form is also done. As i stated earlier the issue is with the Print Output,

Before: When a Version relevant field is changed it is trigger output of NEU --> After release of PO it used to turn green--> Spool is generated succesfully.

Before: When a Non -Version relevant field is changed it never triggred output.(This used to work correctly as per our requirement)

Present: When a Version relevant field is changed it is triggering output of NEU --> After release of PO it used to turn green--> Spool is generated succesfully.

Present: When a Non -Version relevant field is changed it is triggering output of NEU (Which is in Yellow colour) when saving the PO this output type NEU is turning into red When clicking on the Processing Log an error message appears"No print relevant changes to Document exists for XXXXX".

Why is this new behaviour occuring and what is the root cause for it...? Thank you in advance..

[BijayKumarBarik]

Hi,

Check any text causing your concern!

As I already mentioned and you want to find root cause, better discuss with ABAPer to find logic designed for Purchase Order Print" with your PDF/Smartform( check with  in t.code: SMARTFORMS)

Regards,

Biju K

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[Former Member]

Hi All

After much exploration,I have found the reply in one of the older conversation in our forums stating that it is a standard behaviour.

http://scn.sap.com/thread/3181808

The relevant SAP note is:

OSS Note 28869 - Printout of changes although field not print-relevant

Previously when i used to do the changes for non version relevant fields in PO before, It never used to trigger the new out put type while saving it turns into "red" When checking messages in the PO "No print-relevant changes to document XXXXXXXXXX exist" message appears.

As per the mentioned thread, "if you want it different, then you have to go for a modification"

how can i do the modification, where exactly is the modification required and how to restrict the functionality of not creating new output type when a non version field is changed.Kindly advise on this issue.

[Former Member]

Let the output be triggered & failed . Is there any issue if the output is getting failed ?

If you read the OSS note than you can clearly see that there could be some performance issue ,If we want to restrict the output triggered to block. As I can't copy paste the content of the OSS(Violation of rule). Pls have a look a the the OSS 28869