Ansicht
Dokumentation

J_2G0067 - Digital Sign Device Parameters

J_2G0067 - Digital Sign Device Parameters

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

The key field Device ID S/N (DEVID) holds the DSD's registry number or serial number (S/N), which is an 11-character string formed by 3 Latin characters and 8 digits. This information must be real because it is needed when we have to print on the document the DSD that was out of order.

Field Additional Category (ADDCA) is a 30-character field that can be defined freely. It should be used when we want to categorize DSDs belonging to companies defined in SAP under the same company code. Its maintenance is not obligatory. Wildcards can be used. For example let 's say we have two companies (I and II) and the only way to distinguish their postings is the Plant. If all the plants of Company I start with '10' and all the plants of Company II start with '20', then we could set ADDCA = '10*' for all DSDs of Company I, and ADDCA = '20*' for all DSDs of Company II.

If column ADDCA is used, the printing programs must be slightly adjusted in order to set an appropriate value to a corresponding ADDCA variable (search in the printing program for string EAFA01 to find where).

The content of Valid Series (SERIES) field defines the valid print series of the documents that can be processed from the specific DSD. A set of values can be defined with the use of commas and wildcards. The maintenance of this field is mandatory, and if we want to enable a DSD for all print series we must set its SERIES field to '*'.

Note that when a company applies the purchase order papers for the DSDs to the ministry, the print series that is going to be used for every DSD must be declared also. In order to be more flexible and not constrain the use of the DSDs, especially when the centralized model is going to be applied, we propose that all DSDs should be enabled for all series.

Field Dev. Usage (DEVUS) has to do with the way every DSD is going to be used. It can take the following values:

  • ' ' The device is inactive (equivalent to not existent)

  • 'X' The device is in use

  • 'A' This device is used exclusively as an alternative (last) choice

If all DSDs for the same combination of fields BUKRS - ADDCA - SERIES, are set as inactive, then all documents that satisfy the selection criteria set by these three fields, will be printed without being signed (i.e. with the old way).

Field Device off (ISOFF) is a flag, which if set, determines that the specific DSD is out of order.

If all DSDs for the same combination of fields BUKRS - ADDCA - SERIES, are set as being out of order, then all documents that satisfy the selection criteria set by these three fields, will be printed with an indication about the problematic DSD in place of the PAIPS (§ 1.1).

In field Destination (RFCDE ) the RFC destination (transaction SM59) of the corresponding DSD must be defined.






ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3232 Date: 20240523 Time: 185329     sap01-206 ( 75 ms )