cancel
Showing results for 
Search instead for 
Did you mean: 

Output type not automatically triggered in billing

saolin
Explorer
0 Kudos
646

Dear expert,

I have an issue with billing output not triggered automatically in billing document but it allows to maintain manually. I don't tick manually in output dermimination I have done config as attached not sure which part is missing. Could you pls advise me ... Thank you.

ABAPER1
Explorer
0 Kudos
Hey did you get the solution of output type not automatically triggered in billing document? I'm too facing the same problem. Please suggest..

Accepted Solutions (0)

Answers (1)

Answers (1)

DominikTylczyn
Active Contributor
0 Kudos

Hello saolin

Detailed output determination analysis might help. Go to VF02 for a billing document, choose the menu Goto -> Header -> Output and then from the output screen choose the menu Goto -> Determin. analysis. That will display a screen as in your fist screenshot. You need to expand output determination nodes on the left hand side of the screen. This will show you the values of the billing document that were used to find output determination conditions.

You may want to share detailed screenshot of the output determination analysis.

What seems odd in your setup is the output determination procedure. It is ZRT000 on your first screenshot and V10000 on the last one.

Best regards

Dominik Tylczynski

saolin
Explorer

Thank you very much sir for advice. I could see the value in the note and it error with output not found I'm not sure which part i miss configuration. Could you please advise more sir? Thank you.

DominikTylczyn
Active Contributor
0 Kudos

saolin Looks like the billing type ZRSR is missing in the output determination conditions (your 2nd screenshot - VV31).

The analysis says that output is determined with sales organization CMSM and billing type ZRSR. Those values are coming from the billing document. You need to maintain an output determination condition in VV31 with the same values.

Ryan-Crosby
Active Contributor

saolin You will also want to check your timing configuration of 3, which is sending with application own transaction instead of 4 (immediate). You would also want to review the specifics of requirement 62 that exists in the configuration of your output procedure.

DominikTylczyn
Active Contributor

ryan.crosby2 Timing settings, 3 vs 4 don't affect output determination. They do affect output processing. The other comment is perfectly valid - requirement 62 should be examined as it impact the output determination.

Ryan-Crosby
Active Contributor

3a9e4ce873a94034b33dc62b0ce600ee Yes, I'm aware of that but I would consider the "automatic" portion of the question to include the processing of the output as well, and not only the determination piece. With timing 3 one must setup another action in the system to execute the output instead of having it occur immediately upon a save event.