HR_GB_OC_CHECK_PAYMENT_DATA SAP Function module - Prüfen, ob Daten für Zahlungen aus Off-Cycle korrekt

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

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

Pattern for FM HR_GB_OC_CHECK_PAYMENT_DATA - HR GB OC CHECK PAYMENT DATA

CALL FUNCTION 'HR_GB_OC_CHECK_PAYMENT_DATA' "Prüfen, ob Daten für Zahlungen aus Off-Cycle korrekt
  EXPORTING
    infotype_0009_record =      " p0009
    country_group =             " t500l-molga
    country =                   " psyst-land
    v0433_bsr_no =              " p0434-bsrno   HR-GB: Building Society Roll Number
  IMPORTING
    bank_detail =               " bnka_bf
    payment_method_detail =     " t042z_bf
    payment_method_text =       " t042z_l_bf-text1
    .  "  HR_GB_OC_CHECK_PAYMENT_DATA

ABAP code example for Function Module HR_GB_OC_CHECK_PAYMENT_DATA

The ABAP code below is a full code listing to execute function module HR_GB_OC_CHECK_PAYMENT_DATA 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_bank_detail  
 
 TYPE BNKA_BF
,
ld_payment_method_detail  
 
 TYPE T042Z_BF
,
ld_payment_method_text  
 
 TYPE T042Z_L_BF-TEXT1
.


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

SELECT single MOLGA 
  FROM T500L 
  INTO @DATA(ld_country_group).



DATA(ld_country) = some text here


DATA(ld_v0433_bsr_no) = some text here
.

CALL FUNCTION 'HR_GB_OC_CHECK_PAYMENT_DATA'
  EXPORTING
    infotype_0009_record =       ld_infotype_0009_record
    country_group =              ld_country_group
    country =                    ld_country
    v0433_bsr_no =               ld_v0433_bsr_no
  IMPORTING
    bank_detail =                ld_bank_detail
    payment_method_detail =      ld_payment_method_detail
    payment_method_text =        ld_payment_method_text
    .  "  HR_GB_OC_CHECK_PAYMENT_DATA

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_bank_detail
 
 TYPE BNKA_BF ,
ld_infotype_0009_record
 
 TYPE P0009 ,
ld_payment_method_detail
 
 TYPE T042Z_BF ,
ld_country_group
 
 TYPE T500L-MOLGA ,
ld_payment_method_text
 
 TYPE T042Z_L_BF-TEXT1 ,
ld_country
 
 TYPE PSYST-LAND ,
ld_v0433_bsr_no
 
 TYPE P0434-BSRNO .


ld_infotype_0009_record = 'Check type of data required'.

SELECT single MOLGA 
  FROM T500L 
  INTO ld_country_group.


ld_country = some text here

ld_v0433_bsr_no = some text here