SAP CACS_PS_GET_PARTNERSHIPS Function Module for NOTRANSL: Partnerschaften zu Vertrag finden

Search SAP Function Modules

CACS_PS_GET_PARTNERSHIPS is a standard cacs ps get partnerships 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: Partnerschaften zu Vertrag finden 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 ps get partnerships FM, simply by entering the name CACS_PS_GET_PARTNERSHIPS into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_PS_GET_PARTNERSHIPS 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_PS_GET_PARTNERSHIPS'"NOTRANSL: Partnerschaften zu Vertrag finden
  EXPORTING
*  IV_BUSI_TIME =  "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
*  IV_TECH_TIME =  "Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
   IV_APPL =  "Commission Application Identification
   IV_CTRTBU_ID =  "Commission Contract Number
*  IV_BUFFER_REFRESH = ' ' "Boolean Variables (X=true, space=false)

 IMPORTING
   ET_PS_ID =  "Pair: Contract Bundle - Group Contract

EXCEPTIONS
   INVALID_SETTINGS = 1 

.

IMPORTING Parameters details for CACS_PS_GET_PARTNERSHIPS

IV_BUSI_TIME - Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)

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

IV_TECH_TIME - Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)

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

IV_APPL - Commission Application Identification

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

IV_CTRTBU_ID - Commission Contract Number

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

IV_BUFFER_REFRESH - Boolean Variables (X=true, space=false)

Data type: BOOLEAN_FLG
Default: ' '
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CACS_PS_GET_PARTNERSHIPS

ET_PS_ID - Pair: Contract Bundle - Group Contract

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

EXCEPTIONS details

INVALID_SETTINGS -

Data type:
Optional: No
Call by Reference: Yes

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

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