Quantcast
Viewing all articles
Browse latest Browse all 9760

Re: Print program name for the dunning form F150_FR_DUNN_01 in sapscript

Hi,

 

Yes, you should be able to assign F150_FR_DUNN_01 in Dunning Forms customizing:

Image may be NSFW.
Clik here to view.
dunnforms.jpg

and yes, I too would absolutely try to go for either a Smartform or even a PDF Form (if i'd have all the necessary setup for them, like Adobe Document Services, in the system already). I have Basis 702 SP  0011and FINBASIS 600 SP 0021, so all the following technicalities refer to those releases:

 

The corresponding SAP sample Forms are:

- F150_DUNN_SF for Smartform; and

- F150_DUNN_SF for pdf Form (don't let the name confuse you Image may be NSFW.
Clik here to view.
)

 

I'm not entirely sure if it's a good idea to try to convert/migrate Sapscript to Smartform and the Smartform to PDF Form - have never done that  myself and don't know how good/usable the migration result is. I just take the interface of Smartform from SAP and do the rest from scratch or by copying over the common parts of our existing custom forms.

 

There are the SAP Standard wrapper FMs for SF and PDF forms already in the System:

- FI_PRINT_DUNNING_NOTICE_SMARTF calling PRINT_DUNNING_NOTICE_SF and

- FI_PRINT_DUNNING_NOTICE_PDF calling PRINT_DUNNING_NOTICE_PDF.

 

So, theoretically, all you had to do to replace SapScripts (or even to enable all three form types) is to assign a custom BTE Event handler FM to event 1720 (for correct Application), which could detect, what type of form is assigned in Customizing and call the corresponding wrapper FM.

 

As a sample for coding PDF form wrapper call one could takeFI_PSO_EVENT_00001720_PDF (if you have IS-PS) in the system. I'd take out the IS-PS specific "business logic" like posting dunning charges (if it does not apply to my solution) and add the logic to decide, which wrapper to call.

 

The confusing part about the customizing (Table T047E) to me is that there seems to be no form type defined anywhere in there... just the FORNR field for form name, which should apparently take the names of all three form types... I'd  try to extend that table with custom Form type field and try to regenerate Table Maintenance dialog for  view Cluster VC_T047_F... That would save the whole effort to try to detect the type for  form assigned...

 

Another tip, in case you didn't know it already: you should be able to see all the Customizing paths, where T047E is involved, when you enter table name in SM30 and press "Customizing" and then "Continue w/o Specifying Project":

Image may be NSFW.
Clik here to view.
dunnforms1.jpg

The selected entry is the one you are looking for to assing your custom forms, I believe.

 

cheers

Janis


Viewing all articles
Browse latest Browse all 9760

Trending Articles