Kontakt

Ansicht
Dokumentation

IDMX_DI_VTXTIDFI - Determine Text IDs to Store Invoice Data

IDMX_DI_VTXTIDFI - Determine Text IDs to Store Invoice Data

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you set up the system so that it can save, and later retrieve the results of the digital signature process.
Since not every piece of data required for the digital signature process is stored in a field in the system, the system uses text fields in the billing document, for example, at header level, to store the derived results of the digital signature process.

Note: Since the text fields contain data related to the digital signature and any manipulation of the data would render the recipient's view of the digital invoice useless, the text fields are not visible in the invoice. The language of the text fields in which the system stores data is the language of your company code in the system. In some text fields, to comply with legal regulations in Mexico, the system always enters texts in Spanish, for example, the document type for payment flow, regardless of the language of the company code.

The derived results of the digital signature process that the system stores in text fields are grouped in categories:

  • Encrypted character string
    The result of applying the signer's private key to the hashed character string. The result represents a unique fingerprint of the character string, which contains the legally-defined data.
    The encrypted character string is stored in Base 64 encoded format.
  • Document type for payment flow
    Shows whether the document is of type income (ingreso), expense (egreso), or transfer (traslado). The system always enters the text in Spanish, for example, ingreso.
  • Approval year for official document number
  • Approval number for official document number
  • Serial number of certificate
    The serial number of the certificate that you receive from the authorities to sign electronic invoices digitally.
  • Payment installment texts
    Contains the number of installments in which a payment is divided and the corresponding legally-defined text in Spanish. The installments data is stored in the Customizing activity Define Terms of Payment.
  • Document header supplement (complemento)
    Supplemental data at header level that some companies must provide at header level in invoices.
  • Line item supplement (complemento)
    Supplemental data at header level that some companies must provide at line item level in invoices.
  • MD5 hashed character string
    The result of applying the hash algorithm, MD5, to the original input message.
    The hashed character string is stored in hexadecimal encoded format.
  • Original input message
    The complete set of data in the invoice and derived data required by Mexican law for signing invoices digitally.
    The original input message is stored as a character string.
  • Addendum (addenda)
    Contains additional data that customers can choose to include in their invoices.
  • Special Document Header Supplement in XML File
    Special supplemental data that some companies must provide at header level in invoices.
  • Special Line Item Supplement in XML File
    Special supplemental data that some companies must provide at line item level in invoices.
  • Customs Data for Reporting
    Customs data if the invoice includes Special Document Header Supplement in XML File imported goods.
  • Certificate Base64 Coded in XML File
    The certificate stored in Base 64 encoded format.
  • UUID
Unique identifier assigned to by the SAT to the invoice when the invoice is approved.
  • SAT digital signature
SAT's encrypted character chain in base64 (SAT digital signature).
  • Certificate issuer name
Certificate issuer name that is sent for a cancellation request.
  • Digest value
Digest value that is sent for a cancellation request.
  • Serial number
Serial number of the certificate that is sent for a cancellation request.
  • Signed info
Signed info that is sent for a cancellation request.
  • Final chain
Final chain in base64 that is sent for a cancellation request (XML with the cancellation request)

The categories, which are represented by data IDs in this Customizing activity, correspond to specific, predefined qualifiers in child segments of standard IDoc types. The qualifiers use specific, fixed values so that other systems can read the required data in the IDoc segments.
To create a digital invoice, subsequent systems generate an XML file. To generate the XML file, the subsequent systems need to access the derived data from the digital signature process. Since the SAP system stores the data in specific, defined IDoc segments, even if different senders transmit IDocs, the required data is always stored in the same IDoc segments.
The fact that the derived data is always stored in the same IDoc segments also enables the system to access the data required to print digital invoices.
You use this Customizing activity to ensure that the SAP system stores the data that it derives from the digital signature process in the correct IDoc segments. To do this, you map the text fields that store the derived data to the qualifiers (represented by data IDs) of the required IDoc segments.

You have created new text IDs for the text types in which you want to store the derived data from the digital signature process.
Ensure that the namespace you use for each of the text IDs is unique and not already in use.

You create the text IDs as follows:

Since the text fields must not be visible, and therefore not changeable, in the invoice header in the productive system, do not select the checkboxes that make the texts visible in the above Customizing activities.

Note: If you change the ID of a text type after you have digitally signed an electronic invoice, the system will not be able to process that digital invoice correctly, because the system will not be able to access the data in the invoice.

You have performed the Customizing activity Assign Legal Tax Abbreviations to Account Keys.

For each entry in the dropdown box in the Data ID column, perform the following steps:

  1. In the Text Object field, choose the corresponding text field (for example, BELEG for header texts) in which you want the system to store the derived data from the digital signature process.
  2. Choose the text ID of the text type in which you want to store each category of derived data from the digital signature process.

You have created text types with the IDs ZECC, ZDTP, ZAPY, ZAPN, ZSNC, ZPMI, ZCDD, ZHCC, ZOIM, ZADD, ZXCH, ZCUS, ZXBC, ZUDD, ZSAT, ZISN, ZDIV, ZSEN, ZSIV, and ZFIN as header texts (text object BELEG) and ZCGD and ZXCL as a line item text (text object DOC_ITEM) as described under Prerequisites.

You assign the text IDs of the text types that you created to the data IDs as follows:

Data ID Text Object Text ID
Encrypted Character String BELEG ZECC
Document Type for Payment Flow BELEG ZDTP
Approval Year for Official Document Number BELEG ZAPY
Approval Number for Official Document Number BELEG ZAPN
Serial Number of Certificate BELEG ZSNC
Payment Method Installments BELEG ZPMI
Document Header Supplement BELEG ZCDD
Line Item Supplement DOC_ITEM ZCGD
MD5 Hashed Character String BELEG ZHCC
Original Input Message BELEG ZOIM
Addendum BELEG ZADD
Special Document Header Supplement in XML File BELEG ZXCH
Special Line Item Supplement in XML File DOC_ITEM ZXCL
Customs Data for Reporting BELEG ZCUS
Certificate Base64 Coded in XML BELEG ZXBC
Unique Identifier BELEG ZUUD
SAT Digital Signature BELEG ZSAT
Certificate Issuer Name BELEG ZISN
Digest Value BELEG ZDIV
Serial Number BELEG ZSEN
Signed Info BELEG ZSIV
Final Chain BELEG ZFIN

BELEG

BELEG

BELEG

BELEG






BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 12133 Date: 20240523 Time: 203832     sap01-206 ( 134 ms )