SAP H99B_OUTPUT_LFORM Function Module for Prints a logical form









H99B_OUTPUT_LFORM is a standard h99b output lform SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prints a logical form processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for h99b output lform FM, simply by entering the name H99B_OUTPUT_LFORM into the relevant SAP transaction such as SE37 or SE38.

Function Group: HR99B00_FORMS
Program Name: SAPLHR99B00_FORMS
Main Program: SAPLHR99B00_FORMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function H99B_OUTPUT_LFORM pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'H99B_OUTPUT_LFORM'"Prints a logical form
  EXPORTING
   I_MOLGA =  "Country Grouping
*  I_MAIL_APPL_OBJECT =  "Structure for Object ID
*  I_FUNCTION =  "
   I_FOGROUP =  "Output Form Group
   I_FOLNAME =  "Logical Form Name
*  I_FOVARIANT =  "Output Form Variant
*  I_FOTYPE =  "Output Form Type
*  I_DATE = SY-DATUM "Date
   I_DATA_STRUC =  "
*  I_LANGUAGE =  "Language Key
*  I_PROGRAM =  "ABAP Program Name

CHANGING
*  I_WA_TABLE =  "

EXCEPTIONS
   ERROR = 1    FOTYPE_INVALID = 2
.



IMPORTING Parameters details for H99B_OUTPUT_LFORM

I_MOLGA - Country Grouping

Data type: MOLGA
Optional: No
Call by Reference: Yes

I_MAIL_APPL_OBJECT - Structure for Object ID

Data type: SWOTOBJID
Optional: Yes
Call by Reference: Yes

I_FUNCTION -

Data type: STRING
Optional: Yes
Call by Reference: Yes

I_FOGROUP - Output Form Group

Data type: P_99B_FOGROUP
Optional: No
Call by Reference: Yes

I_FOLNAME - Logical Form Name

Data type: P_99B_FORMLOGC
Optional: No
Call by Reference: Yes

I_FOVARIANT - Output Form Variant

Data type: P_99B_FOVARIANT
Optional: Yes
Call by Reference: Yes

I_FOTYPE - Output Form Type

Data type: P_99B_FOTYPE
Optional: Yes
Call by Reference: Yes

I_DATE - Date

Data type: DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_DATA_STRUC -

Data type: ANY
Optional: No
Call by Reference: Yes

I_LANGUAGE - Language Key

Data type: SPRAS
Optional: Yes
Call by Reference: Yes

I_PROGRAM - ABAP Program Name

Data type: REPID
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for H99B_OUTPUT_LFORM

I_WA_TABLE -

Data type: ANY
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

FOTYPE_INVALID - Invalid output form type

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for H99B_OUTPUT_LFORM Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_error  TYPE STRING, "   
lv_i_molga  TYPE MOLGA, "   
lv_i_wa_table  TYPE ANY, "   
lv_i_mail_appl_object  TYPE SWOTOBJID, "   
lv_i_function  TYPE STRING, "   
lv_i_fogroup  TYPE P_99B_FOGROUP, "   
lv_fotype_invalid  TYPE P_99B_FOGROUP, "   
lv_i_folname  TYPE P_99B_FORMLOGC, "   
lv_i_fovariant  TYPE P_99B_FOVARIANT, "   
lv_i_fotype  TYPE P_99B_FOTYPE, "   
lv_i_date  TYPE DATUM, "   SY-DATUM
lv_i_data_struc  TYPE ANY, "   
lv_i_language  TYPE SPRAS, "   
lv_i_program  TYPE REPID. "   

  CALL FUNCTION 'H99B_OUTPUT_LFORM'  "Prints a logical form
    EXPORTING
         I_MOLGA = lv_i_molga
         I_MAIL_APPL_OBJECT = lv_i_mail_appl_object
         I_FUNCTION = lv_i_function
         I_FOGROUP = lv_i_fogroup
         I_FOLNAME = lv_i_folname
         I_FOVARIANT = lv_i_fovariant
         I_FOTYPE = lv_i_fotype
         I_DATE = lv_i_date
         I_DATA_STRUC = lv_i_data_struc
         I_LANGUAGE = lv_i_language
         I_PROGRAM = lv_i_program
    CHANGING
         I_WA_TABLE = lv_i_wa_table
    EXCEPTIONS
        ERROR = 1
        FOTYPE_INVALID = 2
. " H99B_OUTPUT_LFORM




ABAP code using 7.40 inline data declarations to call FM H99B_OUTPUT_LFORM

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
DATA(ld_i_date) = SY-DATUM.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!