Ansicht
Dokumentation
/DSD/BF: Electronic Signature in the DSD Process (New) ( RELN/DSD/603_DSDBF_ELSIG )
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Short text
/DSD/BF: Electronic Signature in the DSD Process (New)
Use
As of SAP ECC 6.0, Enterprise Extension SCM, Enhancement Package 3(EA-SCM 603), business function Enhancement of the DSD Process(/DSD/BF), you can supply selected document types with a simple electronic signature, that is, store a signature electronically on the mobile device, to be used in the subsequent processes in the DSD backend. You can use the electronic signature so that the relevant roles can check selected documents in the DSD process to make sure they are correct and complete, then confirm the documents with their signature.
You can provide a signature for the following document types:
- Order
- Invoice
- Delivery
- Check-in/check-out document
- Reload check-in/check-out document
You can display the document types order, delivery, and invoice together with the signatures in the standard applications. You can also display the signatures for the check-in/check-out documents and the reload check-in/check-out documents in the settlement cockpit. You can print backend documents that have been settled with the signature (invoices, deliveries, and orders).
You make the settings for the electronic signature in backend Customizing for the DSD connector. You can activate or deactivate the ready for input status for the signature for each document type. If the ready for input status is activated, the document must be supplied with a signature. You can decide if a document type should be signed by the driver, controller, or customer. Alternatively, you can specify that the system should accept manual entry of a password instead of a signature.
After the tour or reload, you can transfer the signatures that have been entered electronically on the mobile device to the backend (upload). The system saves the signatures in the backend in separate tables and can archive the signatures together with the corresponding documents. In the final settlement run, the system changes or creates the settled backend documents such as invoice, order, and delivery. The system allocates the signatures
Prerequisites
If you want to use the electronic signature function, you must use the mobile DSD process.
Restrictions
The electronic signature function does not fulfill legal obligations.
The reason is that there is not a 1:1 relationship after the final settlement run in the mobile DSD process between the documents created or changed on the mobile device, and the documents created or changed in the backend.
If you change a delivery on the mobile device, for example, the backend system creates an additional delivery for the changed data. A delivery signed on the mobile device refers to two backend deliveries and two corresponding forms in this case. The backend system treats the two backend deliveries and forms as a unit that corresponds to the relevant mobile deliveries. The same applies for orders and invoices.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
You make the settings for this function in the following sections in Customizing for Direct Store Delivery:
- Electronic Signature-> Signature Repository
- Electronic Signature-> Signature Text ID
- Handheld Connectivity -> DSD Connector Settings-> Mobile Device Settings-> Define General Settings-> Determine Cancellation/Change for Signature
- Handheld Connectivity -> DSD Connector Settings-> Mobile Device Settings -> Determine Signature Mapping Document - Signer Role
Further Information
For more information, see the central Release Note for the business function Enhancement of the DSD Process.
BAL_S_LOG - Application Log: Log header data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5412 Date: 20240425 Time: 041402 sap01-206 ( 98 ms )
