SAP FMCA_FPF_STATUS_TEXT_READ Function Module for FPF: Reads Form Bundle Status Text

Search SAP Function Modules

FMCA_FPF_STATUS_TEXT_READ is a standard fmca fpf status text read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FPF: Reads Form Bundle Status Text 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 fmca fpf status text read FM, simply by entering the name FMCA_FPF_STATUS_TEXT_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function FMCA_FPF_STATUS_TEXT_READ 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 'FMCA_FPF_STATUS_TEXT_READ'"FPF: Reads Form Bundle Status Text
  EXPORTING
*  CLIENT = SY-MANDT "
*  LANGUAGE = SY-LANGU "
*  OBJNR = ' ' "
   STATUS_NUMBER =  "
*  STSMA = ' ' "

 IMPORTING
   LANGUAGE_FOUND =  "
   TXT04 =  "
   TXT30 =  "

EXCEPTIONS
   INSUFFICIENT_INPUT = 1    OBJECT_NOT_FOUND = 2    STATUS_NOT_FOUND = 3    STSMA_NOT_FOUND = 4    FAILED = 5 

.

IMPORTING Parameters details for FMCA_FPF_STATUS_TEXT_READ

CLIENT -

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJNR -

Data type: CRM_JSTO-OBJNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

STATUS_NUMBER -

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

STSMA -

Data type: CRM_JSTO-STSMA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FMCA_FPF_STATUS_TEXT_READ

LANGUAGE_FOUND -

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

TXT04 -

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

TXT30 -

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

EXCEPTIONS details

INSUFFICIENT_INPUT -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

STATUS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

STSMA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

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

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