VL02N - Processing Program missing for output

[Former Member]

I'm trying to set up a control type for VL02N, in wich to call a smartform I've developed but VL02N says the processing program is missing for that output type. I've done all the steps in NACE, setting the processing routines for the output type.

Has anyone had this problem?

[Former Member]

Have you set the Output  Medium correctly ?

Are you using a Custom Outype , if so Plz  check whether the condition records are maintained appropriately

[Former Member]

What do you mean by output medim?

The setting to print immediatly?

[Former Member]

I meant the Message Transmission Medium in Processing Routines (Print Output, Fax ,etc ) ...

Also have u set the value in "Form Entry" usually the value in it is "ENTRY"   , the RSNAST00

Program  will call your Z Program via this Form Routine only

[Former Member]

Everything is set... I have no idea why this is happening!

[Former Member]

Are you checking in the same client in which you have configured , or if not have you made a client copy of the config from one  client another (testing client) via SCC1 .

I hope you would have taken care of this , if not please check

[Former Member]

One thing I've noticed is that i'm only getting this error message for a certain type of documents.

If i use the output type with other document types, I don't get the error message and the smartform is called correctly.

[Former Member]

Can u check ur access sequences ?

[Former Member]

Yes , I can check them. How are the access sequences related to the document types?

Sorry for all these questions, the problem is that I've never had this kind of error related to output types.

[Former Member]

Fernando

No issues , neither me ... Acess equence and condition records are some of the pre requisites that go into the output determination processing... So as you said it works for certain condition types the Particular Output type needs to be assigned in a key combination say for a Doc Type/Salesorg/Division . So check the Condition records and access sequence which have been maintained for the Document type which is working ....(SD Functional guy should be able to help you)

i believe the  Condition record would be more closer to the issue ...