CNV_TDMS_09_DROP_SYNC_STATUSES SAP Function module - Synchronization of status from substate and job table

CNV_TDMS_09_DROP_SYNC_STATUSES is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CNV_TDMS_09_DROP_SYNC_STATUSES into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CNV_TDMS_09_DROP_SOL_CHECK
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CNV_TDMS_09_DROP_SYNC_STATUSES - CNV TDMS 09 DROP SYNC STATUSES

CALL FUNCTION 'CNV_TDMS_09_DROP_SYNC_STATUSES' "Synchronization of status from substate and job table
  EXPORTING
    ip_packid =                 " cnvmbtpack-packid  Package Number to Specify CMIS and TDMS Packages
    ip_phase =                  " cnvmbtstate-phase  Phase of the Migration Project
    ip_act_id =                 " cnvmbtstate-activity_id  Unique ID for all activities to be executed
  EXCEPTIONS
    NO_STATE_ENTRY_FOUND = 1    "               For the transfered import parameter no entry in table cnvmbtstate found
    NO_SESSION_ID_FOUND = 2     "               Could not found the session id in the status table
    NO_SUBSTATE_ENTRIES = 3     "               Could not found substate entries for the given session id
    ERROR_GET_JOB_STATUS = 4    "               Error trying to read job status from receiver system
    .  "  CNV_TDMS_09_DROP_SYNC_STATUSES

ABAP code example for Function Module CNV_TDMS_09_DROP_SYNC_STATUSES

The ABAP code below is a full code listing to execute function module CNV_TDMS_09_DROP_SYNC_STATUSES including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

 

SELECT single PACKID 
  FROM CNVMBTPACK 
  INTO @DATA(ld_ip_packid).

 

SELECT single PHASE 
  FROM CNVMBTSTATE 
  INTO @DATA(ld_ip_phase).

 

SELECT single ACTIVITY_ID 
  FROM CNVMBTSTATE 
  INTO @DATA(ld_ip_act_id).

.

CALL FUNCTION 'CNV_TDMS_09_DROP_SYNC_STATUSES'
  EXPORTING
    ip_packid =                  ld_ip_packid
    ip_phase =                   ld_ip_phase
    ip_act_id =                  ld_ip_act_id
  EXCEPTIONS
    NO_STATE_ENTRY_FOUND =       1
    NO_SESSION_ID_FOUND =        2
    NO_SUBSTATE_ENTRIES =        3
    ERROR_GET_JOB_STATUS =       4
    .  "  CNV_TDMS_09_DROP_SYNC_STATUSES

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ip_packid
 
 TYPE CNVMBTPACK-PACKID ,
ld_ip_phase
 
 TYPE CNVMBTSTATE-PHASE ,
ld_ip_act_id
 
 TYPE CNVMBTSTATE-ACTIVITY_ID .



SELECT single PACKID 
  FROM CNVMBTPACK 
  INTO ld_ip_packid.


SELECT single PHASE 
  FROM CNVMBTSTATE 
  INTO ld_ip_phase.


SELECT single ACTIVITY_ID 
  FROM CNVMBTSTATE 
  INTO ld_ip_act_id.