SAP HR_BR_LER_FILIAL_RAIS Function Module for









HR_BR_LER_FILIAL_RAIS is a standard hr br ler filial rais 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 hr br ler filial rais FM, simply by entering the name HR_BR_LER_FILIAL_RAIS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_BR_LER_FILIAL_RAIS 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 'HR_BR_LER_FILIAL_RAIS'"
EXPORTING
COMPANY_CODE = "
BRANCH = "
DATE = "
* BRANCH_DETAIL = PBR99_OFF "

IMPORTING
NROWN = "
CDNAI = "
CGC_NUMBER = "
ADDRESS = "
NAME = "
MDN01 = "
MUPM1 = "

EXCEPTIONS
BRANCH_NOT_FOUND = 1 ADDRESS_NOT_FOUND = 2 COMPANY_NOT_FOUND = 3 RAIS_DATA_NOT_FOUND = 4 CURRENCY_ERROR = 5
.



IMPORTING Parameters details for HR_BR_LER_FILIAL_RAIS

COMPANY_CODE -

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

BRANCH -

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

DATE -

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

BRANCH_DETAIL -

Data type: PBR99_FLAG
Default: PBR99_OFF
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HR_BR_LER_FILIAL_RAIS

NROWN -

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

CDNAI -

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

CGC_NUMBER -

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

ADDRESS -

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

NAME -

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

MDN01 -

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

MUPM1 -

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

EXCEPTIONS details

BRANCH_NOT_FOUND -

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

ADDRESS_NOT_FOUND -

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

COMPANY_NOT_FOUND -

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

RAIS_DATA_NOT_FOUND -

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

CURRENCY_ERROR -

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

Copy and paste ABAP code example for HR_BR_LER_FILIAL_RAIS 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_nrown  TYPE T7BRB3-NROWN, "   
lv_company_code  TYPE BAPIBRANCH-BUKRS, "   
lv_branch_not_found  TYPE BAPIBRANCH, "   
lv_cdnai  TYPE T7BRNJ-CDNAI, "   
lv_branch  TYPE BAPIBRANCH-BRANCH, "   
lv_address_not_found  TYPE BAPIBRANCH, "   
lv_date  TYPE SY-DATUM, "   
lv_cgc_number  TYPE SY, "   
lv_company_not_found  TYPE SY, "   
lv_address  TYPE ADDR1_VAL, "   
lv_branch_detail  TYPE PBR99_FLAG, "   PBR99_OFF
lv_rais_data_not_found  TYPE PBR99_FLAG, "   
lv_name  TYPE BAPIBRANCH-NAME, "   
lv_currency_error  TYPE BAPIBRANCH, "   
lv_mdn01  TYPE T7BRB3-MDN01, "   
lv_mupm1  TYPE T7BRB3-MUPM1. "   

  CALL FUNCTION 'HR_BR_LER_FILIAL_RAIS'  "
    EXPORTING
         COMPANY_CODE = lv_company_code
         BRANCH = lv_branch
         DATE = lv_date
         BRANCH_DETAIL = lv_branch_detail
    IMPORTING
         NROWN = lv_nrown
         CDNAI = lv_cdnai
         CGC_NUMBER = lv_cgc_number
         ADDRESS = lv_address
         NAME = lv_name
         MDN01 = lv_mdn01
         MUPM1 = lv_mupm1
    EXCEPTIONS
        BRANCH_NOT_FOUND = 1
        ADDRESS_NOT_FOUND = 2
        COMPANY_NOT_FOUND = 3
        RAIS_DATA_NOT_FOUND = 4
        CURRENCY_ERROR = 5
. " HR_BR_LER_FILIAL_RAIS




ABAP code using 7.40 inline data declarations to call FM HR_BR_LER_FILIAL_RAIS

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.

"SELECT single NROWN FROM T7BRB3 INTO @DATA(ld_nrown).
 
"SELECT single BUKRS FROM BAPIBRANCH INTO @DATA(ld_company_code).
 
 
"SELECT single CDNAI FROM T7BRNJ INTO @DATA(ld_cdnai).
 
"SELECT single BRANCH FROM BAPIBRANCH INTO @DATA(ld_branch).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date).
 
 
 
 
DATA(ld_branch_detail) = PBR99_OFF.
 
 
"SELECT single NAME FROM BAPIBRANCH INTO @DATA(ld_name).
 
 
"SELECT single MDN01 FROM T7BRB3 INTO @DATA(ld_mdn01).
 
"SELECT single MUPM1 FROM T7BRB3 INTO @DATA(ld_mupm1).
 


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!