FITP_CREATE_FOP_ELEMENT SAP Function module

FITP_CREATE_FOP_ELEMENT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FITP_CREATE_FOP_ELEMENT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FITP_TRPL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FITP_CREATE_FOP_ELEMENT - FITP CREATE FOP ELEMENT

CALL FUNCTION 'FITP_CREATE_FOP_ELEMENT' "
  EXPORTING
    variant =                   " ftpt_variant-variant
*   sw_portal =                 " char1         Single-Character Indicator
  TABLES
    pnr_fop =                   " ta23pf        Payment Method
  EXCEPTIONS
    FOP_NOT_CREATED = 1         "
    APPLICATION_API_ERROR = 2   "
    GENERAL_API_ERROR = 3       "
    NO_DESTINATION_FOUND = 4    "               No RFC destination found
    NO_VALID_VARIANT = 5        "
    CONNECTION_ERROR = 6        "               Error when setting up connection
    .  "  FITP_CREATE_FOP_ELEMENT

ABAP code example for Function Module FITP_CREATE_FOP_ELEMENT

The ABAP code below is a full code listing to execute function module FITP_CREATE_FOP_ELEMENT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_pnr_fop  
 
 TYPE STANDARD TABLE OF TA23PF,"TABLES PARAM
wa_pnr_fop
 
 LIKE LINE OF it_pnr_fop
.

 

SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO @DATA(ld_variant).


DATA(ld_sw_portal) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_pnr_fop to it_pnr_fop.
.

CALL FUNCTION 'FITP_CREATE_FOP_ELEMENT'
  EXPORTING
    variant =                    ld_variant
*   sw_portal =                  ld_sw_portal
  TABLES
    pnr_fop =                    it_pnr_fop
  EXCEPTIONS
    FOP_NOT_CREATED =            1
    APPLICATION_API_ERROR =      2
    GENERAL_API_ERROR =          3
    NO_DESTINATION_FOUND =       4
    NO_VALID_VARIANT =           5
    CONNECTION_ERROR =           6
    .  "  FITP_CREATE_FOP_ELEMENT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_variant
 
 TYPE FTPT_VARIANT-VARIANT ,
it_pnr_fop
 
 TYPE STANDARD TABLE OF TA23PF ,
wa_pnr_fop
 
 LIKE LINE OF it_pnr_fop,
ld_sw_portal
 
 TYPE CHAR1 .



SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO ld_variant.
 

"populate fields of struture and append to itab
append wa_pnr_fop to it_pnr_fop.
ld_sw_portal = 'Check type of data required'.