SAP API_RE_CN_PERIOD_GET_DETAIL Function Module for
API_RE_CN_PERIOD_GET_DETAIL is a standard api re cn period get detail 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 api re cn period get detail FM, simply by entering the name API_RE_CN_PERIOD_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RECN_API_CONTRACT
Program Name: SAPLRECN_API_CONTRACT
Main Program: SAPLRECN_API_CONTRACT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function API_RE_CN_PERIOD_GET_DETAIL 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 'API_RE_CN_PERIOD_GET_DETAIL'".
EXPORTING
* ID_BUKRS = "Company Code
* ID_RECNNR = "Contract Number
* ID_OBJNR = "Object Number
* ID_INTRENO = "Internal Key of Real Estate Object
* IO_OBJECT = "
IMPORTING
ES_PERIOD = "
ES_ACTIVE_NOTICE = "Active Notice
ET_NOTICE = "Active and Inactive Contract and Object Notices
ET_RENEWAL = "Renewal Options or Automatic Renewals
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for API_RE_CN_PERIOD_GET_DETAIL
ID_BUKRS - Company Code
Data type: BAPI_RE_CONTRACT_INTK-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_RECNNR - Contract Number
Data type: BAPI_RE_CONTRACT_INTK-RECNNROptional: Yes
Call by Reference: No ( called with pass by value option)
ID_OBJNR - Object Number
Data type: RECAOBJNROptional: Yes
Call by Reference: No ( called with pass by value option)
ID_INTRENO - Internal Key of Real Estate Object
Data type: RECAINTRENOOptional: Yes
Call by Reference: No ( called with pass by value option)
IO_OBJECT -
Data type: OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for API_RE_CN_PERIOD_GET_DETAIL
ES_PERIOD -
Data type: BAPI_RE_CN_PERIOD_INTOptional: No
Call by Reference: Yes
ES_ACTIVE_NOTICE - Active Notice
Data type: BAPI_RE_CN_NOTICE_INTOptional: No
Call by Reference: Yes
ET_NOTICE - Active and Inactive Contract and Object Notices
Data type: BAPI_RE_T_CN_NOTICE_INTOptional: No
Call by Reference: Yes
ET_RENEWAL - Renewal Options or Automatic Renewals
Data type: BAPI_RE_T_CN_RENEWAL_INTOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error Occurred While Determining the Data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for API_RE_CN_PERIOD_GET_DETAIL 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_error | TYPE STRING, " | |||
lv_id_bukrs | TYPE BAPI_RE_CONTRACT_INTK-BUKRS, " | |||
lv_es_period | TYPE BAPI_RE_CN_PERIOD_INT, " | |||
lv_id_recnnr | TYPE BAPI_RE_CONTRACT_INTK-RECNNR, " | |||
lv_es_active_notice | TYPE BAPI_RE_CN_NOTICE_INT, " | |||
lv_id_objnr | TYPE RECAOBJNR, " | |||
lv_et_notice | TYPE BAPI_RE_T_CN_NOTICE_INT, " | |||
lv_et_renewal | TYPE BAPI_RE_T_CN_RENEWAL_INT, " | |||
lv_id_intreno | TYPE RECAINTRENO, " | |||
lv_io_object | TYPE OBJECT. " |
  CALL FUNCTION 'API_RE_CN_PERIOD_GET_DETAIL' " |
EXPORTING | ||
ID_BUKRS | = lv_id_bukrs | |
ID_RECNNR | = lv_id_recnnr | |
ID_OBJNR | = lv_id_objnr | |
ID_INTRENO | = lv_id_intreno | |
IO_OBJECT | = lv_io_object | |
IMPORTING | ||
ES_PERIOD | = lv_es_period | |
ES_ACTIVE_NOTICE | = lv_es_active_notice | |
ET_NOTICE | = lv_et_notice | |
ET_RENEWAL | = lv_et_renewal | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " API_RE_CN_PERIOD_GET_DETAIL |
ABAP code using 7.40 inline data declarations to call FM API_RE_CN_PERIOD_GET_DETAIL
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 BAPI_RE_CONTRACT_INTK INTO @DATA(ld_id_bukrs). | ||||
"SELECT single RECNNR FROM BAPI_RE_CONTRACT_INTK INTO @DATA(ld_id_recnnr). | ||||
Search for further information about these or an SAP related objects