sexta-feira, 13 de janeiro de 2017

Digital Invoicing configuration for Mexico configuration in SAP SD

Go to start of metadata

1.1 Purpose of the Document

This document outlines the customization settings that are to be done pertaining to SD to implement Digital Invoicing for Mexico. The Mexican tax regulations have made the implementation of electronic invoices by domestic business entities, mandatory. A digital/electronic invoice (Factura Electrónica), also called a digital tax receipt, e-invoice or efactura is an electronic document that meets the legal and statutory requirements similar to that of pre-printed invoices. The Electronic invoicing process requires digital certificates and a series of folio numbers obtained from the government in order to generate the electronic invoice in the SAP system. The various settings with respect to SD configuration that SAP recommends in order to set up the electronic invoicing process is outlined in this document. The complete setup of the Digital Invoicing process in SAP however is a combination of various tasks to be performed such as implementation of recommended notes, development activities involving creation of smartforms, BADI changes; storing of Digital certificates etc.

1.2 Scope of the document

 This document describes only the configuration steps with respect to SD that need to be completed in order to setup the Digital Invoice functionality for Mexico.

1.3 Prerequisites

SAP recommends the implementation of the following Notes before the customization for SD is done as these are dependent activities. The below table gives the list of Notes to be implemented.
 The latest Support Package needs to be implemented in order that the following nodes of the customizing activities become available as per the screenshot below.
 The Digital Signature Settings node will reveal the following Customizing activities:
If the latest support package has not been implemented, the following configuration settings can be maintained by calling up the corresponding views manually in transaction SM30.

1.4  Configuration Settings

Official Document No. Configuration

1.4.1 Maintain document class
        View : V_DOCCLS
 Document classes are used to distinguish among the different types of official documents as prescribed by the authorities, for example, invoices, debit memos, credit memos, or delivery notes.
Go to SM30 and enter the view name V_DOCCLS.
1.4.2 Assign document classes to document types
         View: V_T003_B_I.
In this step the document classes defined in the previous step are assigned to the accounting document types that are being used in the current business scenario.
 1.4.3 Maintain Number Groups for Folio Numbers
         View : V_1ANUMGR1
Each business entity needs to get the Folio numbers (no. range) from the Mexican government. A no. group needs to be created at first in order to assign the folio number range to it. Different number ranges can exist for different type of documents such as Credit memos, Debit Memos, Invoices etc.
1.4.4 Maintain number ranges for Folio Numbers.
         T-code : SNRO, Object : J_1AOFFDOC
The number range of the Folio numbers got from the government is maintained in this step.
1.4.5 Assign number ranges
          View : V_OFNUM_MX
 The number ranges for the Folio numbers defined in the previous step are assigned to the various Document Classes (such as Credit memos. Debit memos) defined earlier. This step helps to determine different Number ranges (through No. range groups defined) for the different type of documents.

Generation of Digital Signature

1.4.6 Assign Legal Tax Abbreviations to Account Keys
         View : IDMX_DI_VTAXES
In this step the abbreviation for the various taxes used in the business scenario are defined.
Example
Assume that you record the special tax on goods and services (Impuesto Especial sobre Producción y Servicios in Spanish, IEPS) in an account represented by the account key IEP, and value-added tax (Impuesto al Valor Agregado in Spanish, IVA) in an account represented by the account key MWS. You enter the following combination of account keys and tax abbreviations:
 1.4.7 Definition & Assignment of text IDs to store the data for the Digital Signature
           Tcode- VOTXN
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 billing document 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 billing documents 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 that some companies must provide at header level in billing documents.
  • Line item supplement (complemento)
    • Supplemental data that some companies must provide at line item level in billing documents.
  • 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 billing document and derived data required by Mexican law for signing billing documents digitally. The original input message is stored as a character string.
  • Addendum (addenda)
  • Contains additional data that customers can choose to include in their billing documents.
1.4.8 Determine Text IDs to Store Billing Document Data
          View - IDMX_DI_VTXTID

Creation of Output type for triggering the Digital Invoice

1.4.9 Create Output Type
      T-code – NACE
A new output type (ZMDI) is created and the program that generates the digital invoice in pdf & xml formats and smartform are assigned to this output type.
Both ‘print output’ and ‘external send’ are configured so that the output can be printed as well as sent as an email to the email ids that are maintained in the customer master.
1.4.10 Assignment of output type to Output Determination procedure
           T-code – NACZ
1.4.11 Maintain Output condition records
            T-code – VV31
This step is done in order to determine the output type automatically during billing. Based on the conditions (access sequence) during which the o/p  needs to get triggered – Eg: Based on Sales org / Billing type , maintain the condition records and save.

1.5 Additional Notes

For further Information the following Notes can be referred
  • 1280467 FAQ Digital Invoice Mexico
  • 1301160 ODN enabled in SD and FI for Mexico for digital invoicing
  • 1300880 Digital Invoice Mexico: Import Certificates
  • 1303712 Mexico: Enable Creation of Digital Signature in SD
  • 1296042 XML file Digital Invoice Mexico
Fonte: https://wiki.scn.sap.com/wiki/display/Found/Digital+Invoicing+configuration+for+Mexico+configuration+in+SAP+SD

5 comentários:

  1. Very nice Blog. This blog is very informative and very useful for me to know about the benefits of digital signatures.
    Bulk PDF Signer
    PDF Signer
    Digital Signature Software

    ResponderExcluir
  2. I simply want to say I’m very new to blogs and actually loved you’re blog site. Almost certainly I’m going to bookmark your blog post . You absolutely come with great well written articles.
    Document Management Software
    Document Management Software Dubai
    Document Management Software UAE
    Electronic Document Management System

    ResponderExcluir
  3. Thanks for this useful article. keep it up. we are dealing in Digital Signature Software at minimum prices if anyone wants pls contact.

    ResponderExcluir