topic Re: No processing log exists in Application Development and Automation Discussions

No processing log exists

Former Member — Tue, 15 Apr 2014 12:48:35 GMT

Hello All, In ME23N for a PO for perticular output type in messgae processing log not exsiting. But i have check for other Output type log is showing. So please help me out why the log is not showing for here. Thanks and Regards Sankil

Re: No processing log exists

vikas_mulay2 — Tue, 15 Apr 2014 12:56:37 GMT

Hi,

If the output type is process sucessfully(i.e Green in Colour) you will get the message 'No Processing Log exists'.

If the Output type has error in it(i.e Red in colour) you will get the Processing Log.

Hope this solves your query

Regards,

Vikas

Re: No processing log exists

Former Member — Tue, 15 Apr 2014 13:16:09 GMT

Hi Vikas, Thanks for your response. But i have seen some other PO also with different output type with green colour showing log. But in my case its not happening for (ZALL output type)Means not getting log, which my client want to see. Thanks Sankil

Re: No processing log exists

Former Member — Tue, 15 Apr 2014 13:17:57 GMT

I've got the message below when I click "Processing log" in ME22n. How should I do? No processing log exists Message no. VN052 Diagnosis A processing log could not be found for the selected output. Procedure Possible reasons are as follows: The selected output has not yet been processed The processing program did not write a log System logging has been de-activated for the selected output type (use settings in Customizing for current application for the selected output type) I want to see the log as i have ssen with some other output type but i dont know ahy its showing with (ZALL). Thanks sankil

Re: No processing log exists

Former Member — Tue, 15 Apr 2014 13:19:14 GMT

Well your problem seems to be that your update of the PO is successful. You should not be looking for problems once they are not present .

Re: No processing log exists

vikas_mulay2 — Tue, 15 Apr 2014 13:44:09 GMT

Right...Agreed with Jozef...:)

You will not get a log if things are processed.Infact i never get a log if my Output type trigerred in Green(Processed Sucessfully)...

You will get a log if The selected output has not yet been processed or processed with error(Red in colour).

We can try if u can share the log that you get for processed entries(Green in colour)

REgards,

Vikas

Re: No processing log exists

Former Member — Tue, 15 Apr 2014 15:26:28 GMT

Hi Sankil,

To answer your question, I need the following information -

Does the same print program cater to all PO output types ?

Is it a custom print program.

For analysis, first check the dispatch time of the output type in tcode NACE. If it is '4', it is processed immediately when PO document is saved. If it is '3', then output will get triggered through tcode ME9F. For '1' & '2' , through program RSNAST00.

If the output is successfully processed and dispatch time is '4', you will see green light.

If the output is waiting to be processed, you will see yellow light. This happens when dispatch time is '3' ( '1' OR '2' is also possible ).

If there is error and it is your custom print program, we generally set RETCODE variable <> 0 in FORM ENTRY of our print program.

The processing log messages are updated by FM 'NAST_PROTOCOL_UPDATE' .

If your print program is a custom one, check whether the program contains call to FM 'NAST_PROTOCOL_UPDATE'. If the FM is not there in your program, log will not get updated. So you need to add it after processing the output ( copy the code from the standard one ). If FM exists, put a breakpoint in CALL FUNCTION 'NAST_PROTOCOL_UPDATE' and see why the log is not getting updated. You can also add custom messages using 'NAST_PROTOCOL_UPDATE'.

Regards,

DPM

Re: No processing log exists

Former Member — Mon, 09 Nov 2015 13:46:53 GMT

FM 'NAST_PROTOCOL_UPDATE' should be called two times.

1, First time SAP calls this FM always in program RSNAST00 in routine ' PROGRAMM_AUFRUFEN'

2, When you are calling this FM second time message id and message number should not be VN, 056.

I hope this is a little confusing.

SAP trying to update one information message which is not so important, since SAP kept restriction not to update NAST "if no other message exists in the remaining program".

To achieve the above scenario, SAP kept a counter for messages.