User exits in smartforms ?

[Former Member]

hi,

does anybody know if there are common user exits (Badis, etc....)  in smartforms ? I mean a user exit which is called from every form which is created in the system via smartforms ?

br, Martin

[Former Member]

hi,

does anybody know if there are common user exits (Badis, etc....)  in smartforms ? I mean a user exit which is called from every form which is created in the system via smartforms ?

br, Martin

[former_member201285]

As far as I know there aren't any user exits. As you can implement your own ABAP coding at all points of the form processing logic, there's no need for this.

Regards,

Ulrich

[Former Member]

Since it's specific code, I guess you can implement your own exits when you want.

I think you should detail your question. Why would you need to add ome code to all smartforms on your system?

[Former Member]

well, I will go into detail:

I have about 7 different HR standard(!) forms. I have to archive this smartforms into our archive. there is NO customizing for doing that in HR for this forms. so I have to do it somewhere in the coding....I don't want to do it in the form directly, as these are standard smartform forms. so this may not be a modification. so that's why I asked the question about common user exits in smartforms.

what do you mean by 'specific code' anyway ?

br, Martin

[Former Member]

I guess you might be doing this with implicite enhancement points in the printing program of your smartforms.

For me, "specific code" is the opposite of "standard code"

[Former Member]

you mean the function module which is created in smartforms ?

[Former Member]

No, I mean the program which calls the module function which is created in smartforms.

Modifying the function module might work but I think it's dangerous since the function module are auto generated from the smrtforms

[Former Member]

this could be a problem since in the HR environment "everything" is changing so often, especially those programs.

[nabheetscn]

Hi Martin

If you look at the smartform parameters carefully you will see we can directly pass the archive details and form will be archived. In HR i dont have much knowledge but in normal scenarios like sales/purchase order etc we normally create an output type and what will happen to this output type and other confirguration in NACE. You can simply fill those variables in some enhancement/exit etc before form is called and it will automatically do the work where is the issue???

Nabheet

[Former Member]

Hi Nabheet,

I am doing also archiving for sales orders etc.... with config in NACE. so I know what you are

talking about.

but its a completely other situation with HR. so I still don't get the point where I can do this without(!) modification.

br, Martin

[Former Member]

Then enhancing the printing program can still be a solution, they do not change as FM

[Private_Member_7726]

Hi,

You are right, of course, not to want to put the archiving logic in a form... But what would you have achieved, had you found a generic user exit for all the smartforms in the system and implemented it there..? Simply obscured part of the business logic, I believe... Technically it would not be "part" of smartform, yet it would still be called during processing of layout. It would probably be nasty logic, relaying on smartform names or something like it. Business logic concerning archiving belongs in the application + the customizing of application - not even in the driver programs really, much less in some obscure generic user exit.

I'm no specialist in HR, but if the "driver programs" are standard ones, could you give the name of one, so we can try to get a idea how the forms are called and how the control flows during HR printing?

cheers

Jānis

[Former Member]

well, as I mentioned I have about 6 or 7 smartforms, with 6 or 7 different printing programs. so I would have to enhance 6 or 7 programs. that's why I asked for a "central user exit".

br, Martin