FTR_POSTINGSTATUS_GET_TEXT SAP Function module - Texts for Posting Status of a Flow

FTR_POSTINGSTATUS_GET_TEXT 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 FTR_POSTINGSTATUS_GET_TEXT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM FTR_POSTINGSTATUS_GET_TEXT - FTR POSTINGSTATUS GET TEXT

CALL FUNCTION 'FTR_POSTINGSTATUS_GET_TEXT' "Texts for Posting Status of a Flow
  EXPORTING
    pi_sbewebe =                " tb_sbewebe    Posting Status of Flow
    pi_ssprgrd =                " tb_ssprgrd    Reason Why Flow Is Blocked for Posting
    pi_sbfrei =                 " tb_sbfrei     Release Given for Flow to Be Posted?
*   pi_posting_info =           " tracs_tm_query  Posting Information (from Posit.Mgmt)
*   pi_payment_info =           " trprs_tm_query  Payment Information (from Posit.Mgmt)
  IMPORTING
    pe_xbewebe =                " tb_xbewebe2   FTR: Posting Status of a Flow (Name)
    .  "  FTR_POSTINGSTATUS_GET_TEXT

ABAP code example for Function Module FTR_POSTINGSTATUS_GET_TEXT

The ABAP code below is a full code listing to execute function module FTR_POSTINGSTATUS_GET_TEXT 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:
ld_pe_xbewebe  
 
 TYPE TB_XBEWEBE2
.


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

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

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

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

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

CALL FUNCTION 'FTR_POSTINGSTATUS_GET_TEXT'
  EXPORTING
    pi_sbewebe =                 ld_pi_sbewebe
    pi_ssprgrd =                 ld_pi_ssprgrd
    pi_sbfrei =                  ld_pi_sbfrei
*   pi_posting_info =            ld_pi_posting_info
*   pi_payment_info =            ld_pi_payment_info
  IMPORTING
    pe_xbewebe =                 ld_pe_xbewebe
    .  "  FTR_POSTINGSTATUS_GET_TEXT

IF SY-SUBRC EQ 0.
  "All OK
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_pe_xbewebe
 
 TYPE TB_XBEWEBE2 ,
ld_pi_sbewebe
 
 TYPE TB_SBEWEBE ,
ld_pi_ssprgrd
 
 TYPE TB_SSPRGRD ,
ld_pi_sbfrei
 
 TYPE TB_SBFREI ,
ld_pi_posting_info
 
 TYPE TRACS_TM_QUERY ,
ld_pi_payment_info
 
 TYPE TRPRS_TM_QUERY .


ld_pi_sbewebe = 'Check type of data required'.
ld_pi_ssprgrd = 'Check type of data required'.
ld_pi_sbfrei = 'Check type of data required'.
ld_pi_posting_info = 'Check type of data required'.
ld_pi_payment_info = 'Check type of data required'.