SAP BPAR_R_ORG_BUSINESS_YEAR Function Module for NOTRANSL: Geschäftspartner: Lesen der Geschäftsjahres-Daten einer Organisa
BPAR_R_ORG_BUSINESS_YEAR is a standard bpar r org business year SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Geschäftspartner: Lesen der Geschäftsjahres-Daten einer Organisa 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 bpar r org business year FM, simply by entering the name BPAR_R_ORG_BUSINESS_YEAR into the relevant SAP transaction such as SE37 or SE38.
Function Group: BPR0
Program Name: SAPLBPR0
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BPAR_R_ORG_BUSINESS_YEAR 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 'BPAR_R_ORG_BUSINESS_YEAR'"NOTRANSL: Geschäftspartner: Lesen der Geschäftsjahres-Daten einer Organisa.
EXPORTING
PARTNER = "Partner
* I_YEAR = "Fiscal Year
* ZGP = ' ' "Single-Character Indicator
IMPORTING
E_BP000 = "Partner master
E_BUS000 = "BP: General Data I (Read)
E_BUS001 = "BP: General Data II (Read)
E_BP001 = "FS-Specific Attributes; Organization
E_BP021_SINGLE = "Fiscal Year Information
E_CUSTOMER = "Customer Number
TABLES
E_BP021 = "Fiscal Year Information
EXCEPTIONS
PARTNER = 1 NO_ORG_DATA = 2
IMPORTING Parameters details for BPAR_R_ORG_BUSINESS_YEAR
PARTNER - Partner
Data type: BP000-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
I_YEAR - Fiscal Year
Data type: BP_BUSIN_YOptional: Yes
Call by Reference: No ( called with pass by value option)
ZGP - Single-Character Indicator
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BPAR_R_ORG_BUSINESS_YEAR
E_BP000 - Partner master
Data type: BP000Optional: No
Call by Reference: No ( called with pass by value option)
E_BUS000 - BP: General Data I (Read)
Data type: BUS000Optional: No
Call by Reference: No ( called with pass by value option)
E_BUS001 - BP: General Data II (Read)
Data type: BUS001Optional: No
Call by Reference: No ( called with pass by value option)
E_BP001 - FS-Specific Attributes; Organization
Data type: BP001Optional: No
Call by Reference: No ( called with pass by value option)
E_BP021_SINGLE - Fiscal Year Information
Data type: BP021Optional: No
Call by Reference: No ( called with pass by value option)
E_CUSTOMER - Customer Number
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BPAR_R_ORG_BUSINESS_YEAR
E_BP021 - Fiscal Year Information
Data type: BP021Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARTNER - Partner
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ORG_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BPAR_R_ORG_BUSINESS_YEAR 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_e_bp000 | TYPE BP000, " | |||
lt_e_bp021 | TYPE STANDARD TABLE OF BP021, " | |||
lv_partner | TYPE BP000-PARTNR, " | |||
lv_partner | TYPE BP000, " | |||
lv_i_year | TYPE BP_BUSIN_Y, " | |||
lv_e_bus000 | TYPE BUS000, " | |||
lv_no_org_data | TYPE BUS000, " | |||
lv_zgp | TYPE CHAR1, " SPACE | |||
lv_e_bus001 | TYPE BUS001, " | |||
lv_e_bp001 | TYPE BP001, " | |||
lv_e_bp021_single | TYPE BP021, " | |||
lv_e_customer | TYPE KNA1-KUNNR. " |
  CALL FUNCTION 'BPAR_R_ORG_BUSINESS_YEAR' "NOTRANSL: Geschäftspartner: Lesen der Geschäftsjahres-Daten einer Organisa |
EXPORTING | ||
PARTNER | = lv_partner | |
I_YEAR | = lv_i_year | |
ZGP | = lv_zgp | |
IMPORTING | ||
E_BP000 | = lv_e_bp000 | |
E_BUS000 | = lv_e_bus000 | |
E_BUS001 | = lv_e_bus001 | |
E_BP001 | = lv_e_bp001 | |
E_BP021_SINGLE | = lv_e_bp021_single | |
E_CUSTOMER | = lv_e_customer | |
TABLES | ||
E_BP021 | = lt_e_bp021 | |
EXCEPTIONS | ||
PARTNER = 1 | ||
NO_ORG_DATA = 2 | ||
. " BPAR_R_ORG_BUSINESS_YEAR |
ABAP code using 7.40 inline data declarations to call FM BPAR_R_ORG_BUSINESS_YEAR
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 PARTNR FROM BP000 INTO @DATA(ld_partner). | ||||
DATA(ld_zgp) | = ' '. | |||
"SELECT single KUNNR FROM KNA1 INTO @DATA(ld_e_customer). | ||||
Search for further information about these or an SAP related objects