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

Standard script and code for output control ticket in IW32

Former Member
0 Likes
1,853

Hi,

I am working on a output control ticket which gets printed using transaction IW32.

I have to create Z driver program and z form and attach it to shop paper.

I just wanted to make sure that RIPRCT00 and PM_COMMON are the standard program and form for this output control ticket.

Because even though if I keep a break point in the program RIPRCT00 to see the data its fetching, when I do the print preview after going in IW32 I don't go inside the standard program RIPRCT00.

So I am wondering if RIPRCT00 and PM_COMMON are the standard prohgram and form attcahed with output control ticket ?

1 ACCEPTED SOLUTION
Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
1,175

PM_COMMON is the standard sapscript form. I had to work on a simular project last year. I copied PM_COMMON to ZPM_COMMON and did the modifications there. I also copied RIPRCT00 to ZRIPRCT00 and modified it. I'm not sure why you breakpoint is not working for you. Check the configuration to make sure that the output type is setup and it is pointing to print program and the form.

Regards,

Rich Heilman

Hi,

I am working on a output control ticket which gets printed using transaction IW32.

I have to create Z driver program and z form and attach it to shop paper.

I just wanted to make sure that RIPRCT00 and PM_COMMON are the standard program and form for this output control ticket.

Because even though if I keep a break point in the program RIPRCT00 to see the data its fetching, when I do the print preview after going in IW32 I don't go inside the standard program RIPRCT00.

So I am wondering if RIPRCT00 and PM_COMMON are the standard prohgram and form attcahed with output control ticket ?

5 REPLIES 5
Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
1,176

PM_COMMON is the standard sapscript form. I had to work on a simular project last year. I copied PM_COMMON to ZPM_COMMON and did the modifications there. I also copied RIPRCT00 to ZRIPRCT00 and modified it. I'm not sure why you breakpoint is not working for you. Check the configuration to make sure that the output type is setup and it is pointing to print program and the form.

Regards,

Rich Heilman

Read only

0 Likes
1,175

I've just tested it in my system, it stops at my break-point in ZRIPRCT00. Again please check config, also check you break point location and make sure that the program will actually go there, maybe set your break point in the PRINT_PAPER form.

Please remember to award points for helpful answers. THanks.

Regards,

Rich Heilman

Read only

0 Likes
1,175

Yes,

It works only if I set break point point in PRINT_PAPER in my Zprogram but not if I set it anywhere else.

When I try to configure it in SPRO, where I attach my new program and layout name it forces me to enter something in the form routine.

what if I am making a completely new Zcode and don't use print_paper in it ? How do I avoid including any name in form routine ?

Read only

0 Likes
1,175

You must enter something in the form. The reason for this is because in the program when it is going to execute the print of the papers, it is call the subroutine(form) of the print program. It gets these values from your configuration in SPRO. It is doing something like this.

perform print_paper in program zriprct00.

Of course, "print_paper" and "zriprct00" are variables retrieved from the configuration.

So, in summary, In SPRO, configure the output type to use the PRINT_PAPER form of program "ZRIPRCT00" and the sapscript form ZPM_COMMON.

If you are developing a completely new "Z" print program, you must have an entry point in which the program is executed. You will have to have a subroutine(form) very simular to PRINT_PAPER, or you can just copy and paste that code into your new program.

Make sense?

Regards,

Rich Heilman

Read only

Former Member
0 Likes
1,175

Goto OIDF transaction code and give the Driver program name your Zprogram name this way you can get the break poing in your program.