We have previously explored simple layouts and tables individually. In “SAP Adobe Interactive Form Tutorial. Part III. Date Time and Floating Fields, we will delve into essential elements like Date, Time, and various system fields, including Floating Fields (dynamic/changing). While these concepts are fundamental, they remain somewhat elusive until explicitly explained. Let’s embark on this brief journey to uncover these crucial aspects of Interactive Adobe Forms.

Exchange Code: SFP. Trust at this point you have embraced this t-code very much like SAPScript and Smartforms ( and can recall it even in your fantasies).

Make sure to create the interface (which is essential for Adobe forms). Although the tutorial is titled “SAP Adobe Interactive Form Tutorial. Part II. Date Time and Floating Fields,” the interface is the backbone of any interactive Adobe form. The integration of Date Time and Floating Fields is covered extensively in this part to ensure a comprehensive understanding.

Enter the short description and Save.

Enter the Package name and Save.

Let us add our own custom Parameter Name. Select the Import option under Form Interface (left side) and press the Create button (right side) to add an Importing Parameter.

NAME is of type NAME1 (Data Element). Save, Check, Activate the Interface.

Go to back SFP Transaction main screen. Now is the time to create the Form.

Hit Make and give the short depiction and Interface name which you have made previously.

Enter the Package name and Save.

Drag NAME from Connection point to the Context area. Trust you recall that, we made sense of the term Setting in past posts. Basically recollect it as the Worldwide/Top Incorporate whose factors are apparent/accessible to the entire application. If we have any desire to show a few fields in the Adobe from the Connection point, then, at that point, the field must be there in the Setting region.

Intuitive the DATE and TIME fields to Setting. These are framework created factors.

Presently the time has come to play in our Format Region. You can plan your format as perfectly as could be expected and as intricate you need. Be that as it may, for our learning, we will Keep It Basic and Sweet(KISS).

i. A practical example of “How to use a Floating Field in Adobe?”.

Go to Layout

Insert a Standard text field.

Grow/Stretch (as you do in ms paint) the message field limits with the goal that you can compose a sentence in it.

Enter the underneath text or any line you need. In any case, pick single word which you need to keep as drifting field. Drifting means, it very well may be printed anything according to the limiting. It relies upon the runtime worth of the bound variable.

For our model, we maintain that NAME should be dynamic. Select the text (NAME), Right-click on it and pick it as Drifting Field. The word NAME changes to {TextField}.

Do I have to let you that know if you see anything in wavy supports in Adobe Structure, they are Drifting Field?

Bind the drifting field with NAME field which we hauled to the Setting region.

The Field {Text Field} will have dynamic length (most extreme up to bound NAME field from setting). It would extend and gather in size as per your feedback. Name “Smash” is just 3 person, yet name “Wolfeschlegelsteinhausenbergerdorff” has in excess of 30 characters, however your {TextField} would in any case acknowledge it. All things considered, that is the utilization of a Drifting Field.

ii. How to work with Date and Time in Adobe?

Go to Data view:

Intuitive Date and Time fields to Design.

—————————————————————————————–

Ram’s Tip 1: Choosing the right Date/Time Pattern (format).

Select the Date Field and Press on Examples.

You can change the date design, By Choosing the Date Example under the select sort.

You can choose the example in view of country, under Area, by choosing the expected country.

We can likewise organize the Time utilizing similar advances referenced above for the Date field.

Ram’s Tip 2: Know the standard system fields in Adobe.

In Adobe Forms, the beneath are the framework fields accessible.

—————————————————————————————–

Check, Save and Activate.

Stand Alone Test of Adobe Form in T-code SFP:

Press F8 or raise a ruckus around town button on the highest point of your Adobe Structure. Pass your worth to NAME Field.

Press F8 (Execute). Give you neighborhood printer name and hit Print See

You will get your Date, Time and Floater Fields (dynamic runtime esteem) printed.

Allow us to call the Structure from our Driver Program.

Do we need to show the output again? Trust us, it would be precisely as above in the independent test. 

Ideally, at this point, you know how to compose a driver program to call your Adobe structure. Do you actually require it? Alright. Check the functioning driver program underneath. Try to appropriately deal with the special cases.

*&---------------------------------------------------------------------*
*======================================================================*
* YRAM_ADOBE_FORM_PROGRAM3 *
*======================================================================*
* Project : SAP Adobe Forms Tutorial *
* Author : Varad (www.elearningsolutions.co.in) *
* Description : Driver Program for Printing Floating Field, Date & Time *
*======================================================================*
REPORT yram_adobe_form_program3.

* Selection Screen
PARAMETERS: p_name TYPE name1.

**&&~~ Data Objects
DATA: gv_fm_name TYPE rs38l_fnam, " FM Name
gs_fp_docparams TYPE sfpdocparams,
gs_fp_outputparams TYPE sfpoutputparams.

CONSTANTS : gv_form_name TYPE fpname VALUE 'YRAM_ADOBE_FORM3'.

*======================================================================*
* START of Calling the Form
*======================================================================*
*&---------------------------------------------------------------------*
**&&~~ Form Processing: Call Form - Open
*
CALL FUNCTION 'FP_JOB_OPEN'
CHANGING
ie_outputparams = gs_fp_outputparams
EXCEPTIONS
cancel = 1
usage_error = 2
system_error = 3
internal_error = 4
OTHERS = 5.
IF sy-subrc <> 0.
" Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Get the Function module name based on Form Name
*
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
EXPORTING
i_name = gv_form_name
IMPORTING
e_funcname = gv_fm_name.
IF sy-subrc <> 0.
" Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Take the FM name by execuing the form - by using Pattern-
**&&~~ call that FM and replace the FM Name by gv_fm_name
**&&~~ Call the Generated FM
CALL FUNCTION gv_fm_name "'/1BCDWB/SM00000176'
EXPORTING
/1bcdwb/docparams = gs_fp_docparams
name = p_name
EXCEPTIONS
usage_error = 1
system_error = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
*&---------------------------------------------------------------------*

*&---------------------------------------------------------------------*
*&---- Close the spool job
CALL FUNCTION 'FP_JOB_CLOSE'
EXCEPTIONS
usage_error = 1
system_error = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
* <error handling>
ENDIF.

This post might seem straightforward, but trust us, if there’s no one to guide you in your team, even finding the Floating Field option in Adobe can be time-consuming. Not to mention configuring the date and time according to the end user’s preferences. Someone needs to show you for the first time, and then you can do it on your own. In “SAP Adobe Interactive Form Tutorial. Part III. Date Time and Floating Fields,“ we’ll cover these aspects in detail.

Thank you kindly for your time!!

YOU MAY BE INTERESTED IN

How to SPLIT Data in FOR LOOP Using Modern ABAP Syntax?

ABAP Evolution: From Monolithic Masterpieces to Agile Architects

Calculator in SAP using New ABAP Syntax

In SAP Adobe Interactive Form Tutorial. Part I, we demonstrated the steps to create our basic form and the driver program. One of our readers requested the configuration steps for the driver program and Adobe form. In SAP Adobe Interactive Form Tutorial. Part II. Tables in Adobe Form, we will cover how to set up tables within the Adobe form and configure the driver program accordingly.

Question from our peruser: Might u at any point if it’s not too much trouble, make sense of where we will arrange the driver program and related adobe structure name, to set off in any exchange?
Reply: Go to t-code NACE==>Select any application. For instance : V3 ==> Proceed “Result type” button ==> Select any result type. For Instance : RD00 ==> Go ahead “Handling Schedules” ==> here we can arrange Medium/Program/Structure Routine/Structure/PDF-SmartForm Structure.

Under PDF-Smartform Structure, we can arrange the adobe structure.

In PP Module – we can arrange in OPK8 Exchange.

In the previous part of the “SAP Adobe Interactive Form Tutorial. Part I,“ we explored how to display a variable. In real-world scenarios, it’s rare to have a requirement where only a single field needs to be displayed. Today, in “SAP Adobe Interactive Form Tutorial. Part II. Tables in Adobe Form,” we will learn how to create tables in Adobe Forms. Generally, there are two methods for creating tables in Adobe Forms.

1. Normal Table Method using Table Object
2. Create Table using Sub Forms in Adobe

Table Object Method:
Benefits:
It is basic and simple. At the point when we have not many fields which can squeeze into the single line in the design, we can utilize this
The originator realizes that you are working with tables. Creator permits choosing lines or segments, to resize a section at the same time.
We have a really look at box to rehash the table header on each page

Hindrances:
On the off chance that we deactivate the fields in the specific circumstance, it will be hard to utilize if necessary in the structure anyplace. For instance in Content manager ( to have some contingent printing and so on)
Challenging to deal with when we need to print the settled tables
Restriction when we need to print non-standard tables

SubForm Strategy:
What is Subform?
The subform is essential for the structure which is utilized for sorting out the various components like info fields, tables, messages present body pages and seldom ace pages.
At the end of the day, Subform is only a gathering of components. To bunch specific components on the design we can utilize subform and wrap them into it.

Benefits:
Utilizing subforms gives us greater adaptability while spreading out tables.
At the point when we need to print different columns of table, subform is more valuable
We can revise cells in subform (Print any place we need )
It is extremely helpful when we are printing settled tables in the structure.

There are no much impediments, in light of the fact that inside, tables are dealt with as subform structures. We can undoubtedly take a look at this on the off chance that we take a gander at the XML wellspring of the format in Planner.
In the event that we believe that the header should be rehashed in the event of page breaks we need to utilize “Flood Pioneers” (rather than the advantageous really take a look at box in the event that we are utilizing tables). We want to set them on the “Pagination” tab of the article range).

So contingent upon what we need to accomplish we could need to utilize subforms rather than a table. Yet, for standard tables, the suggestion is to straightforwardly utilize the table item. Follow the KIS procedure. Keep It Straightforward (KIS).

I’m certain in the event that you have not worked in Tables previously, the above benefits and weaknesses could have most certainly befuddled you. Sit back and relax. Disregard the above correlation. We will complete an involved with bit by bit guide and when you wrap up making the tables utilizing both the strategies referenced, the image would be clear.

In this instructional exercise, our point is to show Client Information from Client Expert Table KNA1 utilizing both the techniques. We should Adobe.

Building the Interface which would be common for both methods.

Transaction Code: SFP.

Enter the Interface name and Create (Interface is mandatory for Adobe form).

the short description and Save.

the Package name and Save.

Allow us to add our own custom Boundary Name. Select the Import choice under Structure Connection point (left side) and press the Make button (right side) to add a Bringing in Boundary

Bringing in Boundary IT_KNA1 is of type CCRCTT_KNA1. CCRCTT_KNA1 is a table sort of KNA1. In Adobe structure interface/Capability module you want to utilize Table Sort Boundaries to pass table information to the structure from your program. (In Capability module, Tables boundary is old).

Save, Check, Actuate the Connection point.

Go to back SFP Exchange fundamental screen. Make the structure.

Press on create button

Give the short portrayal and Connection point name which you have made before.

Enter the Bundle name and Save.

Drag IT_KNA1 from Connection point which we made before to the Specific situation.

Method 1: Create Table in Adobe Form using Table Object

You ought to deactivate the fields from the Table which are not expected to print since there are many fields in the table, it won’t fit in the structure.

Select the fields which are not expected to be shown.

Right click and select deactivate.

Then it looks like below.

We have only 6 active fields.

Go to layout tab

Embed a text variable to make them head on the structure.

Change the text as required.

You can change the text style and size of the text in the obvious area above.————————————————————————————————
Ram’s Tip 1: In the event that you don’t find Text style toolbar naturally, you can enact it as displayed underneath.

Go to Palettes -> Press on Font.

————————————————————————————————

Now go to Data view.

Select IT_KNA1, Drag and drop it into the layout.

You can change the section level or width, by intuitive choice. If you have any desire to be exceptionally exact, you can likewise go to the properties in the right hand side and change the width and level.

Save, Check, Activate the form.

Kindly note: On the off chance that you have information in the IT_KNA1 table more than 1-page size, it wouldn’t stream to the following page. You need to do the accompanying two exercises to see all information.

The subform must be Flowed.

Select IT_KNA1 And check the check box ‘Allow Page Breaks within Content’.

————————————————————————————————————————

Begin of Update on 27th February 2017

A few clients in certain nations would like the table to have the line Design from Right to Left.

As a matter of course, correcting Rows is Left.

Be that as it may, in the event that you need your columns from Right to Left, pick the format from the Table properties.

---

————————————————————————————————————————

Execute the Driver program: YRAM_ADOBE_FORM_PROGRAM2. The code scrap is given toward the end.

The result would show the table with the Client Expert information.

Method 2: Create Table using Sub Forms

By utilizing this strategy, we can show the fields in any request and the fields in numerous columns of lines.

Go to layout

Each structure will have Expert page and Body page as a matter of course (Untitled Subform) (page1).

In Straightforward definition, we can utilize Expert page to print the header information and Body page for printing the thing information.

The substance region is utilized for printing the information in Body page. We can change the length or width of the substance region in Expert page.

We are keeping the header in Expert page

————————————————————————————————
Ram’s Tip 3: Anytime of your turn of events, to see the fundamental result of your structure, you simply have to tap on See PDF Tab.
————————————————————————————————

Go to configuration view

To print the Table information the Subform must be FLOWED.

This is a vital stage. We want to embed the SubForm.

You can change the level or width of the window in Design tab. You can likewise drag and change.

This Subform can be utilized as the header. If it’s not too much trouble, note Untitled SubForm has been renamed as Header in the left hand side.

Change the header structure content to Streamed, and Stream course to Western text, so that fields will be shown next to each other.

Select your header Subform go to insert -> 0 – Standard -> Text field.

You want to change the properties of the text field for better presentation and appearance.

Select the TextField1. Change the appearance from Indented box – > Strong box.

Change the position from left -> none.

Value entered from user entered from -> Read-only.

Select the Border as the solid color.

Presently, you can reuse this TextField1.

Reorder the TextField1 in Header sub from. (For this situation glue multiple times since we want 5 fields to show)

You can Change the name of the field.

You can pass hard coded text to these fields.

You can change the depiction and An incentive for every one of the excess fields.

We have made the Header column. Presently, the time has come to print the thing information of the table.

Create one more Subform and name it as Items.

Change the thing Subform content to Streamed, and Stream course to Western text, so that fields will be shown next to each other.

Duplicate the five fields Client No, Nation, Name, Road, and Phone and glue under things subform.

Eliminate the default values for every one of the fields.

Tie the information table, i.e IT_KNA1 to the Things Subform.

Restricting is a vital piece of Adobe. Ensure you tie the information accurately.

Bind the fields as:
CustomerNo to KUNNR,
Country to LAND1,
Name to NAME1
Street to STRAS
Telephone to TELF1

You should check the checkbox Rehash Subform for every information thing.

Run the Driver Program: YRAM_ADOBE_FORM_PROGRAM2

The result ought to be same.

In both the Techniques above, we utilized the underneath driver program to call the Adobe Structure. Snap it in your advancement SAP framework and test your recently made tables in the Adobe.

*&---------------------------------------------------------------------*
*======================================================================*
* YRAM_ADOBE_FORM_PROGRAM2 *
*======================================================================*
* Project : SAP Adobe Forms Tutorial *
* Author : Varad (www.elearningsolutions.co.in) *
* Description : Driver Program for Printing the Customer data *
*======================================================================*
REPORT yram_adobe_form_program2.

**&&~~ Data Objects
DATA: gv_fm_name TYPE rs38l_fnam, " FM Name
gs_fp_docparams TYPE sfpdocparams,
gs_fp_outputparams TYPE sfpoutputparams,
gt_kna1 TYPE STANDARD TABLE OF kna1.

CONSTANTS : gv_form_name TYPE fpname VALUE 'YRAM_ADOBE_FORM2'.

*======================================================================*
* START of TREATMENT *
*======================================================================*
START-OF-SELECTION.
SELECT * FROM kna1 INTO TABLE gt_kna1 UP TO 50 ROWS.
*&---------------------------------------------------------------------*
**&&~~ Form Processing: Call Form - Open
*
CALL FUNCTION 'FP_JOB_OPEN'
CHANGING
ie_outputparams = gs_fp_outputparams
EXCEPTIONS
cancel = 1
usage_error = 2
system_error = 3
internal_error = 4
OTHERS = 5.
IF sy-subrc <> 0.
" Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Get the Function module name based on Form Name
*
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
EXPORTING
i_name = gv_form_name
IMPORTING
e_funcname = gv_fm_name.
IF sy-subrc <> 0.
" Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Take the FM name by execuing the form - by using Pattern-
**&&~~ call that FM and replace the FM Name by gv_fm_name
*
**&&~~ Call the Generated FM
CALL FUNCTION gv_fm_name "'/1BCDWB/SM00000176'
EXPORTING
/1bcdwb/docparams = gs_fp_docparams
it_kna1 = gt_kna1
EXCEPTIONS
usage_error = 1
system_error = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Form Processing: Call Form - Open
*
CALL FUNCTION 'FP_JOB_CLOSE'.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
*&---------------------------------------------------------------------*
*&---- Close the spool job
CALL FUNCTION 'FP_JOB_CLOSE'
EXCEPTIONS
usage_error = 1
system_error = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
* <error handling>
ENDIF.
*&---------------------------------------------------------------------*

Do you have anything to add to this article? Have you encountered any issues while using Adobe Forms? Would you like to share any real-world project requirements or solutions? Feel free to share your thoughts. Please leave your comments in the section below and let us know how “SAP Adobe Interactive Form Tutorial. Part II. Tables in Adobe Form“ has helped you or if you have additional insights to offer.

Many thanks for your time!!

YOU MAY BE INTERESTED IN

Applying Enterprise Integration Patterns in SAP ABAP

Objects of Data Dictionary in SAP ABAP

SAP LUW in ABAP Cloud

Spice of this part: Many of us ABAPers may not realize that Adobe Forms can be tested independently in transaction SE37, much like Smart Forms. This tip might not be found in every “SAP Adobe Interactive Form Tutorial. Part I. First Adobe Forms“ you come across.

So clasp your safety belts and prepare for this delightful excursion on SAP Adobe Structure with our experience Pilot, Slam Daruru.

Tutorial 1: Our First Adobe Form

Pre-requisites: Adobe life cycle designer in your system and it should be configured in the Sever as well.

Transaction code: SFP. In the previous article, we told a trick to remember this. Smart Form PDF. 

Enter the Point of interaction and Make (Point of interaction is required for Adobe structure).

What are the uses of Form Interface?

1. In the structure interface, you determine the information that is traded with the application program (like tables, structures, workspaces).
2. Under Worldwide Definitions, you characterize your own fields, factors and so on.
3. The framework fields contain information with a predefined meaning (like the date).

Give the Depiction and Press on Save.

Give the Bundle name and Save.

Really look at the Connection point properties. Examine the left side and the right half of the board. Check the Boundary Name which was created consequently.

Allow us to add our own custom Boundary Name. Select the Import choice under Structure Point of interaction (left side) and press the Make button (right side) to add a Bringing in Boundary IV_TEXT.

For this instructional exercise, IV_TEXT is of type CHAR30 and actually look at the discretionary Banner.

Check, Save and Initiate the Structure Point of interaction.

Return or go to t-code SFP once more. This time we want to make the Structure.

Ideally, we don’t have to educate you again to Press on Make button.

Give the Portrayal of the Structure and the Point of interaction name which we made before.

Enter the Bundle name and Save.

This is the main look of our Structure. Left side we have the Connection point and right side the Specific situation.

Extend the Import Boundary and Simplified the expected variable to Setting

What is the significance of the Context in Form Builder?

In the unique circumstance (otherwise called the structure setting), you determine which information is replicated from the connection point to the structure. You can likewise remember this information as a hub for a pecking order structure. In this pecking order, you can likewise conclude the structure rationale by determining conditions for handling the hubs.

The setting capability in Structure Developer is the connection that ties the point of interaction to the design. You develop the structure setting from the current connection point.

In the event that the above clarification is excessively unclear for you. Disregard it.

Essentially recollect Setting as information announcement at the Worldwide Region, might be very much like TOP Incorporate program.

To put it plainly, assuming you need your boundaries i.e inner tables, workspaces or variable and so forth to be passed from your driver program to Connect and afterward to the Structure then you want to characterize that interior table, workspaces or factors at the Setting of the Structure. Does it appear to be legit? Or on the other hand did I befuddle you more?

Anything characterized in Setting of the Structure is accessible in the Structure to be shown or controlled. Assuming you characterized a variable in the Structure Connection point yet didn’t make it in the Unique situation, then that Point of interaction variable could never be accessible in the Structure.

Basic simplified the boundaries from Connection point to the Structure Setting (as displayed in the figure underneath). All the limiting between Connection point boundaries and Structure setting would happen naturally.

On the off chance that you could do without alternate routes (simplified) or on the other hand assuming you need the setting boundary name to be not quite the same as that in Structure Connection point, then, at that point, you really want to determine the Information Field in the properties of the Setting component without help from anyone else. For instance, if you need to make a setting P_TEXT however you need to tie it with IV_TEXT, then, at that point, the Information Field ought to be IV_TEXT as displayed underneath.

Tip: Simplified from Connection point to the Unique circumstance and afterward change the name/portrayal of the Setting component. This will save your time and you don’t have to unequivocally keep up with the properties.

Allow us to actually look at the Format Tab.

Left side we have Progressive system, Tab Request, Information View and so on and Right side we have Plan, Mater and PDF Review choices.

Let us picked Information View and Simplified the Field which we need to print on the structure to Configuration view. You can put this recorded anyplace in the design. For our model, we have only one component IV_TEXT. The explanation being basic. We made only one component in the Unique circumstance. You can add several additional background information components and they would be accessible here to be passed to the design. In next posts, we will add greater intricacy to our necessity and you would have the option to perceive how we can deal with numerous components.

You can change the Inscription from IV_TEXT to required subtitle. For instance: Text. Click on the component and change the properties of the Article on the right hand side.

Check, Save and Initiate the Structure.

Stand Alone Testing of Adobe Form by using Interface:

To see yield for test reason even before your calling project or driver program is prepared, you can press F8 and again F8 and input a worth to the Connection point and really take a look at the result.

note: Ideally, at this point you have understood that like Smartform, Adobe structure additionally produces a capability module in the back end.

Execute (F8)

Press on Print review button. Check the info boundary is effectively passed from connection point to the design.

Like SAP Script and Smartform, Adobe Form also need a Driver Program. Forms have no utility if they are alone. They need a partner to be complete.  Let us take a look at the other side of the coin.

If you have worked in Smartform earlier, you would find no difference. We just need to pass the data to the Form using the Interface parameters. And debugging is also similar as Smartform.

*&---------------------------------------------------------------------*
*======================================================================*
*                     YRAM_ADOBE_FORM_PROGRAM1                           *
*======================================================================*
* Project     : SAP Adobe Forms Tutorial                               *
* Author      : Varad                                *
* Description : Driver Program to Print Adobe form                     *
*======================================================================*
REPORT yram_adobe_form_program1.

TABLES : apb_lpd_otr_keys.

**&&~~ Data Objects
DATA: gv_fm_name         TYPE rs38l_fnam,      " FM Name
      gs_fp_docparams    TYPE sfpdocparams,
      gs_fp_outputparams TYPE sfpoutputparams.

CONSTANTS : gv_form_name TYPE fpname VALUE 'YRAM_ADOBE_FORM1'.

**&&~~ Selection Screen
*
PARAMETERS : p_text TYPE char30.
*&---------------------------------------------------------------------*
**&&~~ Form Processing: Call Form - Open
*
CALL FUNCTION 'FP_JOB_OPEN'
  CHANGING
    ie_outputparams = gs_fp_outputparams
  EXCEPTIONS
    cancel          = 1
    usage_error     = 2
    system_error    = 3
    internal_error  = 4
    OTHERS          = 5.
IF sy-subrc <> 0.
  " Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Get the Function module name based on Form Name
*
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
  EXPORTING
    i_name     = gv_form_name
  IMPORTING
    e_funcname = gv_fm_name.
IF sy-subrc <> 0.
  " Suitable Error Handling
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Take the FM name by executing the form - by using Pattern-
**&&~~ call that FM and replace the FM Name by gv_fm_name
*
**&&~~ Call the Generated FM
CALL FUNCTION gv_fm_name   "'/1BCDWB/SM00000176'
  EXPORTING
    /1bcdwb/docparams = gs_fp_docparams
    iv_text           = p_text
* IMPORTING
*   /1BCDWB/FORMOUTPUT       =
  EXCEPTIONS
    usage_error       = 1
    system_error      = 2
    internal_error    = 3
    OTHERS            = 4.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
*&---------------------------------------------------------------------*
**&&~~ Form Processing: Call Form - Open
*
CALL FUNCTION 'FP_JOB_CLOSE'
* IMPORTING
*   E_RESULT             =
* EXCEPTIONS
*   USAGE_ERROR          = 1
*   SYSTEM_ERROR         = 2
*   INTERNAL_ERROR       = 3
*   OTHERS               = 4
  .
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
*&---------------------------------END----------------------------------*

Let us test the Output using the Driver Program:

Execute the Driver Program and picked the Print Review choice. The info field is accurately shown in the Structure Format.

Do you have anything to add to this article? Have you faced any issues while using Adobe Forms? Would you like to share any real project requirements or solutions? If so, please feel free to share your thoughts. For more detailed guidance, refer to our “SAP Adobe Interactive Form Tutorial. Part I. First Adobe Forms“. Kindly leave your comments in the section below.

Much thanks for your time!!

YOU MAY BE INTERESTED IN

Just 3 Changes to Improve the SAP ABAP Performance by 95 Percent

Transport ABAP Report Variants into a Work Bench Request

Use of data elements in SAP ABAP