VA13 & VA12-Output Type is not the same when viewing the same SI#

[Former Member]

Hi All,

1st, I'm not a SD functional consultant but rather an ABAPer, so kindly pardon my terms.

Currently,

When I open a Sales Inquiry number via VA12 > Header > Extras > Output > Edit : I can see the output types table maintained

but

When I go to VA13 > Header > Extras > Output > Edit, I dont see output types maintained.

Given this, the users are confused how come that they cannot Issue an Output to in VA13 even if they see an output types maintained in VA12.

So I debug the SAP standard transaction code itself and prove that there's no User Exits or enhancements that has something to do with the weird scenario.

Anyone who have encountered this issue in terms of configuration?

Moreover, I already double check the following:

NACE - output type assigned properly to the form and print program

V/43 - Output type is properly maintained as well

Thanks all.

[Jelena · Accepted solution]

Jaime, there already was exactly the same question not so long ago, only it was VA03 vs. VA02 transaction. As it's been already correctly pointed out, you see different output in Change and Display transaction because in Change transaction the output determination takes place. Plain put, what you see in VA12, has not been saved yet.

I have a feeling that the output is not being saved actually. Try setting Further Data to 'Send immediately...' and also check 'Print immediately' in the Communication options. After saving and going back into VA12 the output should turn either green or red color. If it truns red, you should see an error message.

Other items to check:

1) Make sure that you have checked 'Allow manual' (or something like that) in the output type configuration, if you're planning to issue this output manually.

2) Output determination runs in its own LUW, check for the update termination.

3) Authorizations

4) Output is stored in NAST table (OBJKY = VBELN with all leading zeroes). You can check if record is actually being created there.

If all 4 items pass, then send a message to SAP.

[Former Member · Accepted solution]

SNavaneetha & Jelena & All,

Thanks with the guideline, but it just so happen that someone run SAP standard program RSCLNAST as a batch job, in such that it keeps on deleting the entries in table NAST, so even after saving the output type, after some type, the output type assigned to SO# / Billing Doc # / Inquiry # disappear.

Hi SNavaneetha,

I know that you've been a SD veteran consultant, but I'll appreciate it alot if you can provide a SAP standard source basis on what you just said, so that next time if ABAPers like us encountered such scenario with our co-functional, we can provide them a SAP standard source.

Thanks.

JQC

[Jelena · Accepted solution]

Jaime, well, if you delete NAST records what else did you expect? If the users need the output records to be stored longer, change the parameters in the above mentioned program.

There is SAP documentation available on the Output Determination:

http://help.sap.com/saphelp_47x200/helpdata/en/93/745017546011d1a7020000e829fd11/frameset.htm

It's not a rocket science. A document gets created, output determination takes place, NAST record gets created. If the record has not been processed, you'll see the same thing in change and display transaction. If the record was processed and the output is configured as repeated, you'll see the processed record (green/red) and the new record (yellow) in Change mode, but only the processed one in Display mode. Not sure how much clearer this could be explained...

The SD specialist most likely already knows all this, but is not aware of the deletion program being run.

[Former Member · Accepted solution]

Well said, thanks.

Thread closed.

[former_member183879]

Hi Jamie,

This behaviour is expected.

When the document is in change mode the output determination takes place. So in change mode, whatever the outputs are going to be triggered will be available with a yellow mark. YOU HAVE TO SAVE THE DOCUMENT NOW. If you dont save it, the output types wont be updated for the documents. I think thats were you are doing the mistake. If it is not saved, then in display mode, the output will only show the view before the change mode because there is no change done actually.

Hence Open the document in change mode and SAVE IT. Now see the document in VA13, you can see the output type record there.

Hope this helps, If you have any more query, pls lemme know.

[Former Member]

Hi Krishnan,

Thanks with the prompt and fast reply.

Yes I did that also, please see my actual screen shot [VA12->Save->VA13->Display|http://img829.imageshack.us/img829/2914/sdnva13tracking.jpg]

Thanks.

[Former Member]

Jaime

I am unable to check your documentation because of some restrictions at my client site.

1) Firstly are you saving the document after going into it in change mode (VA12)?

2) What does the Output Determination Analysis say when you are in Display mode- using menu path 'Go to/ Determin analysis'?

Revert with your findings.

[Former Member]

Hi Chand,

Here's the screenshot of my VA13 and VA12 instead:

[VA13 and VA12|http://img185.imageshack.us/img185/1194/vascreenshot.jpg]

The determination analysis says " No analysis log exist "

[Former Member]

Hi All,

I already disabled all the routine program, user exits, and enhancements, but I'm still encountering the issue mentioned about. At this point, I'm very sure that it has nothing to do with my ABAP.

My assumption is that it's either SD configuration or somewhere in Basis side.. Please give some light on this.

thanks

[Former Member]

For further details, the documentation of my investigation analysis is in [SD-Issue Output To Issue|http://www.megaupload.com/?d=5DULEDI2]

thanks