SAP CY_GET_BUKRS_PERIV Function Module for Determines company code and posting period
CY_GET_BUKRS_PERIV is a standard cy get bukrs periv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines company code and posting period 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 cy get bukrs periv FM, simply by entering the name CY_GET_BUKRS_PERIV into the relevant SAP transaction such as SE37 or SE38.
Function Group: CYTA
Program Name: SAPLCYTA
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CY_GET_BUKRS_PERIV 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 'CY_GET_BUKRS_PERIV'"Determines company code and posting period.
EXPORTING
IWERKS = "Plant
IMPORTING
EBUKRS = "Company Code
EPERIV = "Fiscal Year Variant
IMPORTING Parameters details for CY_GET_BUKRS_PERIV
IWERKS - Plant
Data type: T001W-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CY_GET_BUKRS_PERIV
EBUKRS - Company Code
Data type: T001K-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EPERIV - Fiscal Year Variant
Data type: T001-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CY_GET_BUKRS_PERIV 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_ebukrs | TYPE T001K-BUKRS, " | |||
| lv_iwerks | TYPE T001W-WERKS, " | |||
| lv_eperiv | TYPE T001-PERIV. " |
|   CALL FUNCTION 'CY_GET_BUKRS_PERIV' "Determines company code and posting period |
| EXPORTING | ||
| IWERKS | = lv_iwerks | |
| IMPORTING | ||
| EBUKRS | = lv_ebukrs | |
| EPERIV | = lv_eperiv | |
| . " CY_GET_BUKRS_PERIV | ||
ABAP code using 7.40 inline data declarations to call FM CY_GET_BUKRS_PERIV
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 BUKRS FROM T001K INTO @DATA(ld_ebukrs). | ||||
| "SELECT single WERKS FROM T001W INTO @DATA(ld_iwerks). | ||||
| "SELECT single PERIV FROM T001 INTO @DATA(ld_eperiv). | ||||
Search for further information about these or an SAP related objects