Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

how do we test the sap script

Former Member
0 Likes
2,775

Hi All,

Any one tell me processor for testing a SAP SCRIPT.Its so urgent.

Regards,

Rajesh.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,891

Hi.

To test a SAP SCRIPT, you need to do the Configuratin first, for this gotto NACE and do the confog.

let me tell you a example for MEDRUCK. for this goto NACE and select the application type and and press the processing routines there the output type is NEU and give the Form name and the Driver program name. then save it. then goto ME23N and press the Print Preview button, then you will get the print Preview, for this one select the Local Printer name.this will ask when you press the print Preview button.

so, for config, inform your functional person to do, and for testing process. if yo are working for Sales order, then goto Va03, give the sales order, and in the menu you have option issue output in the initial screen and press screen.output will come to screen

7 REPLIES 7
Read only

Former Member
0 Likes
1,891

Hi,

For debugging the script..

Utilities-> Activate debugger..

For testing it : Check if the windows are not overlapping, the data passed in to the windows do not exceed the window size... , check if a footer window is properly maintained..., check if NEXT PAGE option is properly defined..

Award if useful

Thanks

Rajiv

Read only

Former Member
0 Likes
1,891

If you haven't, set up the output determination using transaction NACE. (output types->processing routines)

Assuming that this is for a billing document, you can then use vf02 to open up an existing billing document, use the menu goto->header->output and configure the document for the new output type you set up in NACE. Now you should be able to print this billing document using vf03, using the billing document menu (output to screen).

Read only

0 Likes
1,891

testing is nothing but checking the output for different test cases.

Suppose u want test PO,then we do it in ME23 or me22 whar ever may be.We dont do it from driver progrm.(for perticular transaction u have to configure output type in NACE transaction)

In most case the out put will be checked from that particular tcodes.

Read only

Former Member
0 Likes
1,892

Hi.

To test a SAP SCRIPT, you need to do the Configuratin first, for this gotto NACE and do the confog.

let me tell you a example for MEDRUCK. for this goto NACE and select the application type and and press the processing routines there the output type is NEU and give the Form name and the Driver program name. then save it. then goto ME23N and press the Print Preview button, then you will get the print Preview, for this one select the Local Printer name.this will ask when you press the print Preview button.

so, for config, inform your functional person to do, and for testing process. if yo are working for Sales order, then goto Va03, give the sales order, and in the menu you have option issue output in the initial screen and press screen.output will come to screen

Read only

0 Likes
1,891

Thanks sudheer,

But i have one doubt in the example MEDDRUCK AND VA01 Applications have different processors for testing. Please clarify my doubt.

Regards,

Rajesh

Read only

0 Likes
1,891

Medruck for PO and u can test ur Scripts from SE71 itself without data or ME9F for PO with data.

regards

Prabhu

Read only

Former Member
0 Likes
1,891

Hi ,

If output type or driver program, being defined and created respectively .

Before trigerring or executing ur script, ACTIVATE debugger from SE&! initial screen with script name . THROUGH UTILITIES->ACTIVATE DEBUGGER..

Control will come directly to the , script..now u can check using F5/F6 , script behaviour..on the top screen u cas see ..details like..which Window and text element currently being processed ..

Thanks .