SAP COPI_CHECK_SIGN_TO_SIGN_MS Function Module for NOTRANSL: Überprüft die Bearbeitung der vorangegangenen data get specs









COPI_CHECK_SIGN_TO_SIGN_MS is a standard copi check sign to sign ms 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: Überprüft die Bearbeitung der vorangegangenen data get specs 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 copi check sign to sign ms FM, simply by entering the name COPI_CHECK_SIGN_TO_SIGN_MS into the relevant SAP transaction such as SE37 or SE38.

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



Function COPI_CHECK_SIGN_TO_SIGN_MS 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 'COPI_CHECK_SIGN_TO_SIGN_MS'"NOTRANSL: Überprüft die Bearbeitung der vorangegangenen data get specs
  EXPORTING
   CR_ID =  "Control recipe identifier
   FT_NO =  "Process instruction number
*  DGS_LINE =  "
*  STEP_SIGNED =  "

 IMPORTING
   ALL_OK =  "All data get specs processed
   SIGN_MS_FOUND =  "

TABLES
   ICOFMA =  "Message allocation table
   SCOFT =  "Table with process instructions
   SCOFV =  "Table with process instruction characteristics
   TCOMH =  "

EXCEPTIONS
   DGS_NOT_FOUND = 1
.



IMPORTING Parameters details for COPI_CHECK_SIGN_TO_SIGN_MS

CR_ID - Control recipe identifier

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

FT_NO - Process instruction number

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

DGS_LINE -

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

STEP_SIGNED -

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

EXPORTING Parameters details for COPI_CHECK_SIGN_TO_SIGN_MS

ALL_OK - All data get specs processed

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

SIGN_MS_FOUND -

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

TABLES Parameters details for COPI_CHECK_SIGN_TO_SIGN_MS

ICOFMA - Message allocation table

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

SCOFT - Table with process instructions

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

SCOFV - Table with process instruction characteristics

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

TCOMH -

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

EXCEPTIONS details

DGS_NOT_FOUND -

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

Copy and paste ABAP code example for COPI_CHECK_SIGN_TO_SIGN_MS 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_cr_id  TYPE COFV-CRID, "   
lv_all_ok  TYPE FLAG, "   
lt_icofma  TYPE STANDARD TABLE OF RCOFMA, "   
lv_dgs_not_found  TYPE RCOFMA, "   
lv_ft_no  TYPE COFV-FTNO, "   
lt_scoft  TYPE STANDARD TABLE OF RCOFTP, "   
lv_sign_ms_found  TYPE FLAG, "   
lt_scofv  TYPE STANDARD TABLE OF RCOFVP, "   
lv_dgs_line  TYPE I, "   
lt_tcomh  TYPE STANDARD TABLE OF RCOMHP, "   
lv_step_signed  TYPE C. "   

  CALL FUNCTION 'COPI_CHECK_SIGN_TO_SIGN_MS'  "NOTRANSL: Überprüft die Bearbeitung der vorangegangenen data get specs
    EXPORTING
         CR_ID = lv_cr_id
         FT_NO = lv_ft_no
         DGS_LINE = lv_dgs_line
         STEP_SIGNED = lv_step_signed
    IMPORTING
         ALL_OK = lv_all_ok
         SIGN_MS_FOUND = lv_sign_ms_found
    TABLES
         ICOFMA = lt_icofma
         SCOFT = lt_scoft
         SCOFV = lt_scofv
         TCOMH = lt_tcomh
    EXCEPTIONS
        DGS_NOT_FOUND = 1
. " COPI_CHECK_SIGN_TO_SIGN_MS




ABAP code using 7.40 inline data declarations to call FM COPI_CHECK_SIGN_TO_SIGN_MS

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 CRID FROM COFV INTO @DATA(ld_cr_id).
 
 
 
 
"SELECT single FTNO FROM COFV INTO @DATA(ld_ft_no).
 
 
 
 
 
 
 


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!