SAP CACS_DBC_GET_YEARS_OF_TABLE Function Module for NOTRANSL: Lesen der Jahre in den Belegtabellen
CACS_DBC_GET_YEARS_OF_TABLE is a standard cacs dbc get years of table 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: Lesen der Jahre in den Belegtabellen 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 cacs dbc get years of table FM, simply by entering the name CACS_DBC_GET_YEARS_OF_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_DB_CONVERSION_TOOLS
Program Name: SAPLCACS_DB_CONVERSION_TOOLS
Main Program: SAPLCACS_DB_CONVERSION_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CACS_DBC_GET_YEARS_OF_TABLE 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 'CACS_DBC_GET_YEARS_OF_TABLE'"NOTRANSL: Lesen der Jahre in den Belegtabellen.
EXPORTING
IV_TABNAME = "Table Name
IV_FIELD = "Field Name
IMPORTING
EV_MAX_YEAR = "Year of Commission Case/Commission Document
EV_MIN_YEAR = "Year of Commission Case/Commission Document
EXCEPTIONS
NOTHING_TO_CONVERT = 1 FIELDS_DO_NOT_EXIST = 2 NO_SUCH_FIELD = 3
IMPORTING Parameters details for CACS_DBC_GET_YEARS_OF_TABLE
IV_TABNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
IV_FIELD - Field Name
Data type: FIELDNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CACS_DBC_GET_YEARS_OF_TABLE
EV_MAX_YEAR - Year of Commission Case/Commission Document
Data type: CACSYEAROptional: No
Call by Reference: Yes
EV_MIN_YEAR - Year of Commission Case/Commission Document
Data type: CACSYEAROptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_TO_CONVERT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
FIELDS_DO_NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NO_SUCH_FIELD - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_DBC_GET_YEARS_OF_TABLE 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_iv_tabname | TYPE TABNAME, " | |||
lv_ev_max_year | TYPE CACSYEAR, " | |||
lv_nothing_to_convert | TYPE CACSYEAR, " | |||
lv_iv_field | TYPE FIELDNAME, " | |||
lv_ev_min_year | TYPE CACSYEAR, " | |||
lv_fields_do_not_exist | TYPE CACSYEAR, " | |||
lv_no_such_field | TYPE CACSYEAR. " |
  CALL FUNCTION 'CACS_DBC_GET_YEARS_OF_TABLE' "NOTRANSL: Lesen der Jahre in den Belegtabellen |
EXPORTING | ||
IV_TABNAME | = lv_iv_tabname | |
IV_FIELD | = lv_iv_field | |
IMPORTING | ||
EV_MAX_YEAR | = lv_ev_max_year | |
EV_MIN_YEAR | = lv_ev_min_year | |
EXCEPTIONS | ||
NOTHING_TO_CONVERT = 1 | ||
FIELDS_DO_NOT_EXIST = 2 | ||
NO_SUCH_FIELD = 3 | ||
. " CACS_DBC_GET_YEARS_OF_TABLE |
ABAP code using 7.40 inline data declarations to call FM CACS_DBC_GET_YEARS_OF_TABLE
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.Search for further information about these or an SAP related objects