SAP ISH_SSF_SIGN_DATA Function Module for









ISH_SSF_SIGN_DATA is a standard ish ssf sign data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish ssf sign data FM, simply by entering the name ISH_SSF_SIGN_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_SSF_SIGN_DATA 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 'ISH_SSF_SIGN_DATA'"
EXPORTING
I_APPL = "
I_STYPE = "

IMPORTING
E_SIGID = "

EXCEPTIONS
USER_ABORT = 1 ERROR = 2
.



IMPORTING Parameters details for ISH_SSF_SIGN_DATA

I_APPL -

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

I_STYPE -

Data type: NSIGH-STYPE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISH_SSF_SIGN_DATA

E_SIGID -

Data type: NSIGH-SIGID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

USER_ABORT -

Data type:
Optional: No
Call by Reference: Yes

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_SSF_SIGN_DATA 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_i_appl  TYPE IF_ISH_SSF_SIGNATURE, "   
lv_e_sigid  TYPE NSIGH-SIGID, "   
lv_user_abort  TYPE NSIGH, "   
lv_error  TYPE NSIGH, "   
lv_i_stype  TYPE NSIGH-STYPE. "   

  CALL FUNCTION 'ISH_SSF_SIGN_DATA'  "
    EXPORTING
         I_APPL = lv_i_appl
         I_STYPE = lv_i_stype
    IMPORTING
         E_SIGID = lv_e_sigid
    EXCEPTIONS
        USER_ABORT = 1
        ERROR = 2
. " ISH_SSF_SIGN_DATA




ABAP code using 7.40 inline data declarations to call FM ISH_SSF_SIGN_DATA

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 SIGID FROM NSIGH INTO @DATA(ld_e_sigid).
 
 
 
"SELECT single STYPE FROM NSIGH INTO @DATA(ld_i_stype).
 


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!