SAP RETM_API_TERM_PY_GET Function Module for









RETM_API_TERM_PY_GET is a standard retm api term py get 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 retm api term py get FM, simply by entering the name RETM_API_TERM_PY_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function RETM_API_TERM_PY_GET 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 'RETM_API_TERM_PY_GET'"
EXPORTING
IO_HAS_TERM = "

IMPORTING
ET_TERM_PY = "
ET_TERM_PYSPLIT = "Split for Posting Rules of RE Object - Internal
.



IMPORTING Parameters details for RETM_API_TERM_PY_GET

IO_HAS_TERM -

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

EXPORTING Parameters details for RETM_API_TERM_PY_GET

ET_TERM_PY -

Data type: BAPI_RE_T_TERM_PY_INT
Optional: No
Call by Reference: Yes

ET_TERM_PYSPLIT - Split for Posting Rules of RE Object - Internal

Data type: BAPI_RE_T_TERM_PYSPLIT_INT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RETM_API_TERM_PY_GET 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_et_term_py  TYPE BAPI_RE_T_TERM_PY_INT, "   
lv_io_has_term  TYPE IF_RETM_HAS_TERM, "   
lv_et_term_pysplit  TYPE BAPI_RE_T_TERM_PYSPLIT_INT. "   

  CALL FUNCTION 'RETM_API_TERM_PY_GET'  "
    EXPORTING
         IO_HAS_TERM = lv_io_has_term
    IMPORTING
         ET_TERM_PY = lv_et_term_py
         ET_TERM_PYSPLIT = lv_et_term_pysplit
. " RETM_API_TERM_PY_GET




ABAP code using 7.40 inline data declarations to call FM RETM_API_TERM_PY_GET

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



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!