SAP CACS_DET_GET_STD_CONTRACT Function Module for NOTRANSL: Findung: Eintrag des Standardvertrags hohlen









CACS_DET_GET_STD_CONTRACT is a standard cacs det get std contract 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: Findung: Eintrag des Standardvertrags hohlen 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 det get std contract FM, simply by entering the name CACS_DET_GET_STD_CONTRACT into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS_DET_GET_STD_CONTRACT 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_DET_GET_STD_CONTRACT'"NOTRANSL: Findung: Eintrag des Standardvertrags hohlen
EXPORTING
IV_APPL = "Commission Application Identification
IV_CTRTST_ID = "Number of Standard Commission Contract
IV_BUSI = "Effective Validity
IV_TECH = "Technical Validity

IMPORTING
ES_CTRTST = "Structure for Table CACS_STDCTR

EXCEPTIONS
ERROR = 1 NOT_FOUND = 2
.



IMPORTING Parameters details for CACS_DET_GET_STD_CONTRACT

IV_APPL - Commission Application Identification

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

IV_CTRTST_ID - Number of Standard Commission Contract

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

IV_BUSI - Effective Validity

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

IV_TECH - Technical Validity

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

EXPORTING Parameters details for CACS_DET_GET_STD_CONTRACT

ES_CTRTST - Structure for Table CACS_STDCTR

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

EXCEPTIONS details

ERROR -

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

NOT_FOUND -

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

Copy and paste ABAP code example for CACS_DET_GET_STD_CONTRACT 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_iv_appl  TYPE CACSAPPL, "   
lv_es_ctrtst  TYPE CACS_S_STDCTR, "   
lv_not_found  TYPE CACS_S_STDCTR, "   
lv_iv_ctrtst_id  TYPE CACS_CTRTST_ID, "   
lv_iv_busi  TYPE CACSBUSITIME, "   
lv_iv_tech  TYPE CACSTECHTIME. "   

  CALL FUNCTION 'CACS_DET_GET_STD_CONTRACT'  "NOTRANSL: Findung: Eintrag des Standardvertrags hohlen
    EXPORTING
         IV_APPL = lv_iv_appl
         IV_CTRTST_ID = lv_iv_ctrtst_id
         IV_BUSI = lv_iv_busi
         IV_TECH = lv_iv_tech
    IMPORTING
         ES_CTRTST = lv_es_ctrtst
    EXCEPTIONS
        ERROR = 1
        NOT_FOUND = 2
. " CACS_DET_GET_STD_CONTRACT




ABAP code using 7.40 inline data declarations to call FM CACS_DET_GET_STD_CONTRACT

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!