SAP TP_1A_CREATE_FOP_ELEMENT Function Module for

Search SAP Function Modules

TP_1A_CREATE_FOP_ELEMENT is a standard tp 1a create fop element SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 tp 1a create fop element FM, simply by entering the name TP_1A_CREATE_FOP_ELEMENT into the relevant SAP transaction such as SE37 or SE38.

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

Function TP_1A_CREATE_FOP_ELEMENT 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 'TP_1A_CREATE_FOP_ELEMENT'"
  EXPORTING
   VARIANT =  "Plan Variant Number (Sequential Number)

TABLES
   PNR_FOP_IN =  "'Form of Payment' in PNR
   PNR_FOP_OUT =  "Output of 'Form of Payments' in PNR

EXCEPTIONS
   FOP_CREATION_ERROR = 1    FOP_NOT_CREATED = 2    NO_DESTINATION = 3    INVALID_VARIANT = 4    CONNECTION_ERROR = 5    RFC_ERROR = 6    GENERAL_API_ERROR = 7 

.

IMPORTING Parameters details for TP_1A_CREATE_FOP_ELEMENT

VARIANT - Plan Variant Number (Sequential Number)

Data type: FTPT_VARIANT-VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TP_1A_CREATE_FOP_ELEMENT

PNR_FOP_IN - 'Form of Payment' in PNR

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

PNR_FOP_OUT - Output of 'Form of Payments' in PNR

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

EXCEPTIONS details

FOP_CREATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

FOP_NOT_CREATED -

Data type:
Optional: No
Call by Reference: Yes

NO_DESTINATION -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_VARIANT - Invalid context

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CONNECTION_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RFC_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

GENERAL_API_ERROR - General API error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TP_1A_CREATE_FOP_ELEMENT 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.

ABAP code using 7.40 inline data declarations to call FM TP_1A_CREATE_FOP_ELEMENT

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.

Search for further information about these or an SAP related objects