SAP CATS_MY_CHECK_PUSH Function Module for NOTRANSL: Entscheidung, ob Synchronisation notwendig ist









CATS_MY_CHECK_PUSH is a standard cats my check push 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: Entscheidung, ob Synchronisation notwendig ist 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 cats my check push FM, simply by entering the name CATS_MY_CHECK_PUSH into the relevant SAP transaction such as SE37 or SE38.

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



Function CATS_MY_CHECK_PUSH 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 'CATS_MY_CHECK_PUSH'"NOTRANSL: Entscheidung, ob Synchronisation notwendig ist
EXPORTING
IM_DATE = "Date
IM_TIME = "Time of Entry
IM_OBJECT = "

IMPORTING
SUBRC = "Return Value, Return Value after ABAP Statements
.




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_SAPLCATS_MY_003 Supplement Offline Time Data
EXIT_SAPLCATS_MY_004 Influence Messages from Synchronization

IMPORTING Parameters details for CATS_MY_CHECK_PUSH

IM_DATE - Date

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

IM_TIME - Time of Entry

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

IM_OBJECT -

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

EXPORTING Parameters details for CATS_MY_CHECK_PUSH

SUBRC - Return Value, Return Value after ABAP Statements

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

Copy and paste ABAP code example for CATS_MY_CHECK_PUSH 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_subrc  TYPE SY-SUBRC, "   
lv_im_date  TYPE CATSDATE, "   
lv_im_time  TYPE CATS_CPUTM, "   
lv_im_object  TYPE CATS_MY_PUSH-OBJECT. "   

  CALL FUNCTION 'CATS_MY_CHECK_PUSH'  "NOTRANSL: Entscheidung, ob Synchronisation notwendig ist
    EXPORTING
         IM_DATE = lv_im_date
         IM_TIME = lv_im_time
         IM_OBJECT = lv_im_object
    IMPORTING
         SUBRC = lv_subrc
. " CATS_MY_CHECK_PUSH




ABAP code using 7.40 inline data declarations to call FM CATS_MY_CHECK_PUSH

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 SUBRC FROM SY INTO @DATA(ld_subrc).
 
 
 
"SELECT single OBJECT FROM CATS_MY_PUSH INTO @DATA(ld_im_object).
 


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!