topic SMARTFORM ISSUE ? in Application Development and Automation Discussions

SMARTFORM ISSUE ?

Former Member — Mon, 30 Jun 2008 14:02:50 GMT

I have did one smartform and wrote driver program for that but when i have implemented that in NACE tcode it is not reflecting in the ME22N tcode.

In processing routines i have given my smartform name in SMARTFORM column and under program nmae i have given my DRIVER program name.

When i am executeing the driver program though se38 then it is excecuting perfectly. What changes that i have to do to implement my SMARTFORM in ME22N. Waiting for your valuable replies.

Thks in Advance.

Re: SMARTFORM ISSUE ?

Former Member — Mon, 30 Jun 2008 14:12:14 GMT

Hello venkateshwar reddy ,

You need to follow certail rules inside driver print program of the SMARTFORMS. Take a sample print ptogram and try to follow the stems that they had given there. For example you have to take the document number from the NAST-OBJKEY inside the print program and then you need to pass this to the SMARTFORMS Function module.

Hope this answers your question.

Thanks,

Greetson

Re: SMARTFORM ISSUE ?

Former Member — Mon, 30 Jun 2008 14:43:43 GMT

Hello venkateshwar reddy ,

Check the standard print program "/SMB40/FM06P" for your code example.

As I mentioned you earlier they are passing the NAST structure to the form routine. In the Transaction run time NAST will have values .

*PERFORM processing_po USING nast ls_xfz*
                     *CHANGING ent_retco ent_screen l_druvo.*

Hope this answers your question.

Thanks,

Greetson

Re: SMARTFORM ISSUE ?

Former Member — Tue, 01 Jul 2008 12:11:32 GMT

Hello Reddy,

Looks like in the smartforms driver program you have maintained the Selection screen parameter pointing to a Po number field reference and

in your data retrieval logic is based on this selection field reference field and not the NAST-OBJKEY. This is wrong.

Do the following corrections in your driver program:

1) Change the form routine name from "SUB_GET_DATA " to "ENTRY" (because you had mentioned "ENTRY" in the NACE Output type configurations.

2) Make your retrieval logic to make use of NAST_OBJKEy and not the P_EBELN.

For detailed reference check the sample print program that I had mentioned in my previous posting on the same thread.

Hope this solves your problem.

Thanks,