SAP CACS03_LOSA_RESP_INT_RFC Function Module for NOTRANSL: Haftung(LOS): Ende einer Haftungsunterbrechung (RFC)

Search SAP Function Modules

CACS03_LOSA_RESP_INT_RFC is a standard cacs03 losa resp int rfc 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: Haftung(LOS): Ende einer Haftungsunterbrechung (RFC) 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 cacs03 losa resp int rfc FM, simply by entering the name CACS03_LOSA_RESP_INT_RFC into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS03_LOSA_RESP_INT_RFC 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 'CACS03_LOSA_RESP_INT_RFC'"NOTRANSL: Haftung(LOS): Ende einer Haftungsunterbrechung (RFC)
  EXPORTING
   I_CACSAPPL =  "Commission Application (ICM)
   I_OBJ_TYPE =  "Object Type Class (OTC) for Logical Service
   I_OBJ_ID =  "Calculating Object Identification
   I_OBJ_METHOD =  "Assigned Method for Object Type Class for Logical Service
   I_TECH_TIME =  "Technically Valid From
   I_BUSI_TIME =  "Effective from

 IMPORTING
   E_B_ERROR_OCCURED =  "Boolean Variable (X=True, -=False, Space=Unknown)
   E_STRUC_RESP =  "Comn.: Liability Types

EXCEPTIONS
   PROCESS_ERROR = 1 

.

IMPORTING Parameters details for CACS03_LOSA_RESP_INT_RFC

I_CACSAPPL - Commission Application (ICM)

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

I_OBJ_TYPE - Object Type Class (OTC) for Logical Service

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

I_OBJ_ID - Calculating Object Identification

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

I_OBJ_METHOD - Assigned Method for Object Type Class for Logical Service

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

I_TECH_TIME - Technically Valid From

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

I_BUSI_TIME - Effective from

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

EXPORTING Parameters details for CACS03_LOSA_RESP_INT_RFC

E_B_ERROR_OCCURED - Boolean Variable (X=True, -=False, Space=Unknown)

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

E_STRUC_RESP - Comn.: Liability Types

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

EXCEPTIONS details

PROCESS_ERROR - An error has occurred during the execution

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS03_LOSA_RESP_INT_RFC 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.

ABAP code using 7.40 inline data declarations to call FM CACS03_LOSA_RESP_INT_RFC

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