SAP CACS_CHECK_BP_CTRT Function Module for Checks of Partner Type and Contract Type

Search SAP Function Modules

CACS_CHECK_BP_CTRT is a standard cacs check bp ctrt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks of Partner Type and Contract Type 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 check bp ctrt FM, simply by entering the name CACS_CHECK_BP_CTRT into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_CHECK_BP_CTRT 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_CHECK_BP_CTRT'"Checks of Partner Type and Contract Type
  EXPORTING
*  I_APPL =  "Commission Application Identification
   I_GP_NR =  "Business Partner Number
   I_BUSI_BEGIN =  "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
   I_BUSI_END =  "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
   I_CTRTST_ID =  "Commission Contract

EXCEPTIONS
   FAILED = 1 

.

IMPORTING Parameters details for CACS_CHECK_BP_CTRT

I_APPL - Commission Application Identification

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

I_GP_NR - Business Partner Number

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

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

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

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

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

I_CTRTST_ID - Commission Contract

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

EXCEPTIONS details

FAILED - Requirements not fulfilled

Data type:
Optional: No
Call by Reference: Yes

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

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