Getting processing log for our custom output triggering FM?

[former_member194142]

Hello,

VA02 > Extras>Header>Output>Edit --- Triggering an custom IDOC

Stadnard SAP output programs shows IDOC number on output processing log. But, our custom programs/FMs the one we use to trigger on order IDOC, don't show the processing log. How to get this processing log for custom FMs just like standard SAP?

Thank you

[brad_bohn]

What processing program and routine are you using? Both ALE_PROCESSING and EDI_PROCESSING have a call to record the IDOC number in the log. See FILL_NAST_PROTOCOL_IDOC in RSNASTED. If you aren't using the standard program for some reason, you can perform the same logic in your processing program to populate the log with NAST_PROTOCOL_UPDATE.

[former_member194142]

Thank you.

We are using ALE model.

[former_member194142]

Hello

I am sending my custom IDOC by using FM 'MASTER_IDOC_DISTRIBUTE', if it went well (sending successfully - status is '03') in next step am using PERFORM FILL_NAST_PROTOCOL(ROIKCALE) routine.

But, when i checked the PROCESSING LOG of the associated green latest item in VA02/03>Extras>OP>Header>Edit....am getting a message that "No processing log exists"

How to get/see my IDOC #?

when i saw the F1, it says, "System logging has been de-activated for the selected output type (use settings in Customizing for current application for the selected output type)"

When i checked the settings in NACE (and then clicking lense), they are fine.

Am i seeing correctly to get/know the generated IDOC #?

Thank you

[brad_bohn]

MASTER_IDOC_DISTRIBUTE has the IDOC number in the control record among other places. Since you're not using RSNASTED and form ALE_PROCESSING for some reason, you need to capture the IDOC number in your code and log it yourself. As I said before, RSNASTED handles this for you and the only thing you need to do is write the process code. I don't know why you would call to ROIKCALE for the log update routine if you wrote your own Z-program. You should just call the logging functions directly - you can record any number of messages with custom code.

[former_member194142]

Thank you

Yes, i got the IDOC # as importing param from MSATER_IDOC_DISTRIBUTE FM....Actuualy, now i can not develop/test this requirement because am out from work. If you get a chance pls. eloborate that do i need to call the same FM NAST_PROTOCAL_UPDATE in my custom FM explicitly, which sends custom IDOC thru MASTER_IDOC_DISTRIBUTE FM? and what others i need to do?

Thank you

[former_member194142]

Hello

I did not get the statement

 
 write the process code  

from Brad Bohn reply, pls. eloborate/explain briefly.

Thank you

[former_member194142]

Any help pls. that how can implement code in my custom FM (which has MASTER_IDOC_DISTRIBUTE to trigger OB IDOC) in order to get processing log in VA02/03 transactions? Pls. explain below, (what are logging functions here?)

 You should just call the logging functions directly 

Thank you

[former_member194142]

Any help pls.

Thank you

[brad_bohn]

Writing the process code refers to the function for creating the IDOC itself - when you use RSNASTED, that's all you have to do other than configuration and development of the IDOC definition. The messaging/logging is handled for you as I've said before. Since you're not following that model, you need to perform the logging yourself as I've already said as well. Follow the model in ROIKCALE but call the functions in your own code. The process in ROIKCALE is very simple - take the time to analyze it.