SAP FPCOMP_CONDITION_END Function Module for









FPCOMP_CONDITION_END is a standard fpcomp condition end 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 fpcomp condition end FM, simply by entering the name FPCOMP_CONDITION_END into the relevant SAP transaction such as SE37 or SE38.

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



Function FPCOMP_CONDITION_END 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 'FPCOMP_CONDITION_END'"
EXCEPTIONS
USAGE_ERROR = 1 SYSTEM_ERROR = 2 INTERNAL_ERROR = 3
.



EXCEPTIONS details

USAGE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR - System Error

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPCOMP_CONDITION_END 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_usage_error  TYPE STRING, "   
lv_system_error  TYPE STRING, "   
lv_internal_error  TYPE STRING. "   

  CALL FUNCTION 'FPCOMP_CONDITION_END'  "
    EXCEPTIONS
        USAGE_ERROR = 1
        SYSTEM_ERROR = 2
        INTERNAL_ERROR = 3
. " FPCOMP_CONDITION_END




ABAP code using 7.40 inline data declarations to call FM FPCOMP_CONDITION_END

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



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!