SAP QSS7_READ_SIGN_REMARK Function Module for NOTRANSL: Auslesen der Tabelle der Bemerkung zur Signatur

Search SAP Function Modules

QSS7_READ_SIGN_REMARK is a standard qss7 read sign remark 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: Auslesen der Tabelle der Bemerkung zur Signatur 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 qss7 read sign remark FM, simply by entering the name QSS7_READ_SIGN_REMARK into the relevant SAP transaction such as SE37 or SE38.

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

Function QSS7_READ_SIGN_REMARK 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 'QSS7_READ_SIGN_REMARK'"NOTRANSL: Auslesen der Tabelle der Bemerkung zur  Signatur
  EXPORTING
   IV_DS_APPLICATION =  "Application of the Digital Signature
*  IV_VORGANG =  "Business Transaction
*  IV_QMNUM =  "Notification Number
*  IV_MANUM =  "Sequential Activity Number
   IV_DS_SIGNOBJECT =  "Digital Signature Object
   IV_SIGN_STATE =  "Status of Signature Process
*  IV_SIGNSTRAT =  "Signature Strategy
*  IV_PRUEFLOS =  "Inspection Lot Number
*  IV_PHYNR =  "Number of the physical sample
*  IV_VORNR =  "Operation Number
*  IV_PROBENR =  "Sample Number (Based on an Inspection Point)
*  IV_PRNR =  "Sample-Drawing Number

CHANGING
*  LT_SIGN_REMARK =  "Record of Remarks from the Application for Digital Signature
*  LV_DEFAULT_REMARK_ID =  "Component of Version Number

.

IMPORTING Parameters details for QSS7_READ_SIGN_REMARK

IV_DS_APPLICATION - Application of the Digital Signature

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

IV_VORGANG - Business Transaction

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

IV_QMNUM - Notification Number

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

IV_MANUM - Sequential Activity Number

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

IV_DS_SIGNOBJECT - Digital Signature Object

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

IV_SIGN_STATE - Status of Signature Process

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

IV_SIGNSTRAT - Signature Strategy

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

IV_PRUEFLOS - Inspection Lot Number

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

IV_PHYNR - Number of the physical sample

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

IV_VORNR - Operation Number

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

IV_PROBENR - Sample Number (Based on an Inspection Point)

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

IV_PRNR - Sample-Drawing Number

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

CHANGING Parameters details for QSS7_READ_SIGN_REMARK

LT_SIGN_REMARK - Record of Remarks from the Application for Digital Signature

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

LV_DEFAULT_REMARK_ID - Component of Version Number

Data type: SIGN_REMARK_STRUC-ID
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for QSS7_READ_SIGN_REMARK 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.

ABAP code using 7.40 inline data declarations to call FM QSS7_READ_SIGN_REMARK

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.

Search for further information about these or an SAP related objects