SAP IST_COPA_DATA_CHECK Function Module for INTERNAL: Global Checks for CO-PA Update









IST_COPA_DATA_CHECK is a standard ist copa data check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Global Checks for CO-PA Update 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 ist copa data check FM, simply by entering the name IST_COPA_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function IST_COPA_DATA_CHECK 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 'IST_COPA_DATA_CHECK'"INTERNAL: Global Checks for CO-PA Update
EXPORTING
X_BUKRS = "Company Code
* X_DATE = SY-DATUM "Date for Activation Check

IMPORTING
Y_ERKRS = "Operating Concern
Y_KOKRS = "Controlling Area

TABLES
* TY_IST_EBS_TOI_COPA = "Table Content IST_EBS_TOI_COPA per Operating Concern

EXCEPTIONS
NO_ERKRS = 1 NO_ATTRIBUTE_CORRELATION = 2 NOT_ERKRS_ACTIVE = 3
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLIST_EBS_BILLPOST_001 Customer Exit to Change Documents Before Posting
EXIT_SAPLIST_EBS_BILLPOST_002 Customer Exit for Converting Contract Account ID

IMPORTING Parameters details for IST_COPA_DATA_CHECK

X_BUKRS - Company Code

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

X_DATE - Date for Activation Check

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for IST_COPA_DATA_CHECK

Y_ERKRS - Operating Concern

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

Y_KOKRS - Controlling Area

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

TABLES Parameters details for IST_COPA_DATA_CHECK

TY_IST_EBS_TOI_COPA - Table Content IST_EBS_TOI_COPA per Operating Concern

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

EXCEPTIONS details

NO_ERKRS - Error Determining the Operating Concern

Data type:
Optional: No
Call by Reference: Yes

NO_ATTRIBUTE_CORRELATION - No Characteristic Allocation Found

Data type:
Optional: No
Call by Reference: Yes

NOT_ERKRS_ACTIVE - Profitability Analysis is not Active

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IST_COPA_DATA_CHECK 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_x_bukrs  TYPE T001-BUKRS, "   
lv_y_erkrs  TYPE TKEB-ERKRS, "   
lv_no_erkrs  TYPE TKEB, "   
lt_ty_ist_ebs_toi_copa  TYPE STANDARD TABLE OF IST_EBS_TOI_COPA, "   
lv_x_date  TYPE SY-DATUM, "   SY-DATUM
lv_y_kokrs  TYPE TKA01-KOKRS, "   
lv_no_attribute_correlation  TYPE TKA01, "   
lv_not_erkrs_active  TYPE TKA01. "   

  CALL FUNCTION 'IST_COPA_DATA_CHECK'  "INTERNAL: Global Checks for CO-PA Update
    EXPORTING
         X_BUKRS = lv_x_bukrs
         X_DATE = lv_x_date
    IMPORTING
         Y_ERKRS = lv_y_erkrs
         Y_KOKRS = lv_y_kokrs
    TABLES
         TY_IST_EBS_TOI_COPA = lt_ty_ist_ebs_toi_copa
    EXCEPTIONS
        NO_ERKRS = 1
        NO_ATTRIBUTE_CORRELATION = 2
        NOT_ERKRS_ACTIVE = 3
. " IST_COPA_DATA_CHECK




ABAP code using 7.40 inline data declarations to call FM IST_COPA_DATA_CHECK

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.

"SELECT single BUKRS FROM T001 INTO @DATA(ld_x_bukrs).
 
"SELECT single ERKRS FROM TKEB INTO @DATA(ld_y_erkrs).
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_x_date).
DATA(ld_x_date) = SY-DATUM.
 
"SELECT single KOKRS FROM TKA01 INTO @DATA(ld_y_kokrs).
 
 
 


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!