Driver program is not getting triggered

[Former Member]

Hi Experts ,

I have assigned driver program and form under the application ME to the output type WE01 and WE02 and WE03 .But my program is not getting triggered.

How to check whether the Form entry is getting or not ?

i have also tried putting the break point in the program.

Please suggest .

Thanks

[Former Member]

just check in TNAPR table for the output type you have the same program name or not.

[Former Member]

ask ur functional to check the config in nace.

program will only get triggered when ur config is complete in tcode NACE

Edited by: kartik tarla on Feb 1, 2009 1:19 PM

[Former Member]

Hi Kartik ,

I have checked the NACE transaction . With std prog and form the output was coming properly.

I just changed the prog name and form with mine ,but output is not coming.

I tried to debug the transaction MIGO from where the print needs to come but no use.

[Former Member]

just changing the program name and form name wont do.

where u have assigned ur program name double click in it, the u check if entry routine has been specified or not.

[Former Member]

In Form entry i put one message and now it is giving me express document error with the write stmt.That means my prog is getting triggered.

Below is my Form entry

form entry using OBJKY " ".

NAST_KEY = OBJKY.

select single werks from t001w into t001w-werks where werks = NAST_KEY-p_werks.

if sy-subrc ne 0.

message ' TESTING FORM ENTRY ' type 'E'.

endif.

perform check_input.

perform fetch_data.

perform print_control.

if not wa_mkpf is initial.

perform call_sf.

endif.

endform. "ENTRY

Please suggest me how should the form entry be coded.

I want to fetch the OBJKEY ,but i think there is some problem with the code .

Please suggest .

Thanks

[Former Member]

Its better u refer some standard program on how to write an entry routine. generally entry routine call an processing routine and all ur code is written in processing routine so check that.

For the code u hv written, specify nast as tables parameter.

and use as nast-objky.

nast_key = nast-objky.

I am not on sap system right now, so i can give u code by evening meanwhile u refer to some standard on how to use entry and how to refer nast entries inside ur program.

кu03B1ятu03B9к

Edited by: kartik tarla on Feb 1, 2009 2:00 PM

[Former Member]

Hi Kartik,

Thanks a lot !

Update for you ......

By refereing std prog i have written the form routine like below.

FORM entry USING ent_retco ent_screen.

xscreen = ent_screen.

CLEAR ent_retco.

PERFORM check_input USING nast-objky.

ent_retco = retco.

perform fetch_data.

perform print_control.

ENDFORM.

form check_input using objky.

nast_key = objky.

select single werks from t001w into t001w-werks where werks = NAST_KEY-p_werks.

if sy-subrc ne 0.

• message 'ENTER VALID PLANT' type 'E'.

endif.

endform. "check_input

But i am not able to debug the code...

Break point is not triggering the code.

[Former Member]

Above u said ur program is getting triggered.

so is ur problem that program is getting triggered but not stopping at break point right?

Assuming u hv hardcoded ur breakpoint.

try debugging using update debugging, though not sure if this is gonna work in this case but generally if an task is called in update mode and has a breakpoint then it doesnot stop at it unless update debuging is switched on.

кu03B1ятu03B9к

Edited by: kartik tarla on Feb 1, 2009 9:33 PM

[Former Member]

The output is triggered in background, so it will never catch your break point.

Follow this technique:

Goto the output edit page on your transaction MIGO. Select the output type and click on "Further data", there in "Dispatch time" select "1 Send with periodically scheduled job" and save your goods receipt. Doing this will not issue the output immediately and you have trigger it manually as detailed below.

This setting will allow you to run your output type manually via program RSNAST00. Unlike "send immediately" which runs in background, running with RSNAST00 runs your output type in foreground, so all your break points will be caught.

While running RSNAST00, you may need to format OBJECT KEY field with correct number of leading zeros, otherwise it won't select the output type.

[Former Member]

Hi Sonal,

Just debugg and check if the program name and entry form is passed correctly..

Regards,

Pramod