Electronic Accounting- Mexico

Table of Contents
Configuration Settings for Auxiliary Accounting (Mexico)......................................................................... 2
Configuration Settings for Electronic Accounting (Mexico) ....................................................................... 4
Configuration Settings for Journal Entries (Mexico) ................................................................................. 6
Customizing for Company Code Data..................................................................................................... 12
Configuration Settings for Auxiliary Accounting (Mexico)

Before you use the auxiliary accounting solution for Mexico that consists of generating XML files for
primary chart of accounts and country chart of accounts you must perform the below-mentioned
activities:

1. Create a Financial Statement Version (FSV)

First, execute transaction OB13 to define chart of accounts. Then, execute transaction OB58 to
create an FSV based on the primary chart of accounts and country chart of accounts.
While creating the FSV, make the following settings:
a. Do not select the Item keys auto. checkbox as the system automatically assigns an item
key to the FSV item.
b. In the Item field, enter the SAT code by double-clicking on the item in FSE2.
Enter NA in the case of non-assigned nodes.
c. To identify the nature of G/L accounts, ensure that the item text starts with either D (for
debit) or A (for credit).
In the event there is a node in the FSV that incudes accounts of different nature, ensure
that you define a second level. Enter the SAT code in the Item field in the first level and
define the nature in the Item Text field in the second level.
2. Validate the File
Execute the FILE transaction to create a logical file path and logical file name to validate physical
file names.
a. On the Change View “Logical File Path Definition: Overview” screen, create the
FI_RPFIMXEACCT_PATH logical file path.
b. Under Dialog Structure, double-click on Logical File Name Definition, Cross-Client to
create the FI_RPFIMXEACCT_FILE logical name.
For additional information and instructions, refer SAP Note 1497003.

3. Generate XML File

Use the RPFIGLMX_AUXACCOUNTING report (transaction code: FIGLMX_AUXACCT) to generate
XML files. To access this report, on the SAP Easy Access screen, choose Accounting -> Financial
Accounting -> General Ledger -> Reporting -> Tax Reports -> Mexico -> Generate XML Files for
Auxiliary Accounting.
On the report selection screen, enter the following values:
 Company code, reporting year, and reporting period
 Financial statement version
 Requirement type, order number, and process number
For detailed information, refer to the report documentation by choosing the i button.

In addition to the XML file, the report also generates a corresponding tree output that contains
the total credit/debit details of all G/L accounts.

4. Once the XML file has been generated, you can download the file on to your presentation
server.
 From the report output screen, choose the Back (F3) button. The system automatically calls the
RFASLDPC program, that you use to download the file.
On the RFASLDPC program selection screen, in the Character Set Conversion group box, choose
one of the following radio buttons:
 No Character Set Conversion
Choose this button if your system is Unicode active.
 Manual Entry of Code Page
Choose this button if your system is not Unicode. Also, enter 4110 in the Target Code
Page field.

To check if your system is Unicode or not, from the menu bar, choose System -> Status. The field
Unicode System will indicate the status.
5. The following Business Add-Ins (BAdIs) are used in the XML file processing:
a. FIGLMX_ACC_BAL
You use this BAdI to direct the account balances to the RPFIGLMX_AUXACCOUNTING
report’s ALV output and XML output.
This BAdI is called internally in the RPFIGLMX_AUXACCOUNTING report.
This BAdI contains the GET_ACCOUNT_BALANCES method that determines the account
balances for special ledgers. In the event the fiscal year is not a calendar year, the
special ledgers’ account balances are stored in a temporary table. This method returns
the account balances using the CT_BALANCES changing parameter to the report output.
b. FIGLMX_EXIT
You use this BAdI to direct special ledger documents to the
RPFIGLMX_AUXACCOUNTING report’s ALV output and the XML output.
This BAdI is called when internally in the RPFIGLMX_AUXACCOUNTING report.
This BAdI contains the ADD_DOCUMENT_DETAILS method that fetches the special
ledger documents. In the event the fiscal year is not a calendar year, these documents
are stored in a temporary table. This method returns the documents using the
FIGLMX_AUX_HEADER and FIGLMX_AUX_ITEMS changing parameters to the report
output.

You must implement both these BAdIs and activate the mentioned methods to get the
respective code.
Configuration Settings for Electronic Accounting (Mexico)

Prior to using the electronic accounting solution for Mexico, ensure that you perform the below-
mentioned activities:

1. Create a Financial Statement Version (FSV)

First, execute transaction OB13 to define chart of accounts. Then, execute transaction OB58 to
create an FSV based on the primary chart of accounts and country chart of accounts.
While creating the FSV, make the following settings:
a. Do not select the Item keys auto. checkbox as the system automatically assigns an item
key to the FSV item.
b. In the Item field, enter the SAT code by double-clicking on the item in FSE2.
Enter NA in the case of non-assigned nodes.
c. To identify the nature of G/L accounts, ensure that the item text starts with either D (for
debit) or A (for credit).
In the event there is a node in the FSV that incudes accounts of different nature, ensure
that you define a second level. Enter the SAT code in the Item field in the first level and
define the nature in the Item Text field in the second level.
2. Validate the File
Execute the FILE transaction to create a logical file path and logical file name to validate physical
file names.
a. On the Change View “Logical File Path Definition: Overview” screen, create the
FI_RPFIMXEACCT_PATH logical file path.
b. Under Dialog Structure, double-click on Logical File Name Definition, Cross-Client to
create the FI_RPFIMXEACCT_FILE logical name.

For additional information and instructions, refer SAP Note 1497003.

3. Generate XML File
Use the RPFIGLMX_EACCOUNTING report (transaction code: FIGLMX_EACCT) to generate XML
files. To access this report, on the SAP Easy Access screen, choose Accounting -> Financial
Accounting -> General Ledger -> Reporting -> Tax Reports -> Mexico -> Generate XML Files.
For detailed information, refer to the report documentation by choosing the i button.

In addition to the XML file, the report also generates a corresponding tree that contains the
total credit/debit details of all G/L accounts.

4. Once the XML file has been generated, you can download the file on to your presentation
server.
From the report output screen, choose the Back (F3) button. The system automatically calls the
RFASLDPC program, that you use to download the file.
On the RFASLDPC program selection screen, in the Character Set Conversion group box, choose
one of the following radio buttons:
 No Character Set Conversion
Choose this button if your system is Unicode active.
  Manual Entry of Code Page
Choose this button if your system is not Unicode. Also, enter 4110 in the Target Code
Page field.

To check if your system is Unicode or not, from the menu bar, choose System -> Status. The field
Unicode System will indicate the status.
5. The following Business Add-Ins (BAdIs) are used in the XML file processing:
a. FIGLMX_ACC_BAL
You use this BAdI to direct the account balances to the RPFIGLMX_EACCOUNTING
report’s ALV output and XML output.
This BAdI is called internally in the RPFIGLMX_EACCOUNTING report.
This BAdI contains the GET_ACCOUNT_BALANCES method that determines the account
balances for special ledgers. In the event the fiscal year is not a calendar year, the
special ledgers’ account balances are stored in a temporary table. This method returns
the account balances using the CT_BALANCES changing parameter to the report output.
b. FIGLMX_EXIT
This BAdI is called internally in the RPFIGLMX_EACCOUNTING report.
The CHANGE_FILE_NAME and CREATE_TRIGGER_FILE methods allow you to change the
file name path and create a trigger file respectively.
c. FIGLMX_NEWGL
You use this BAdI to maintain uniform debit and credit values between the
RPFIGLMX_EACCOUNTING and the RPFIGLMX_AUXACCOUNTING reports.
This BAdI contains the GET_CREDIT_DEBIT_NEWGL method that fetches the debit and
credit values in the event the new General Ledger (GL) solution has been activated in
your system. For additional information, refer SAP note 2361008.
You must implement this BAdI and activate the above method to get the respective
code.
Configuration Settings for Journal Entries (Mexico)

Before you generate an XML file for all posted journal entries, ensure that you perform the below-
mentioned activities:

1. Validate the File

Execute the FILE transaction to create a logical file path and logical file name to validate physical
file names.
a. On the Change View “Logical File Path Definition: Overview” screen, create the
FI_RPFIMXEACCT_PATH logical file path.
b. Under Dialog Structure, double-click on Logical File Name Definition, Cross-Client to
create the FI_RPFIMXEACCT_FILE logical name.

For additional information and instructions, refer SAP Note 1497003.

2. Generate XML File

Use the RPFIGLMX_JE_DETAILS report (transaction code: FIGLMX_JE) to generate XML files. To
access this report, on the SAP Easy Access screen, choose Accounting -> Financial Accounting ->
General Ledger -> Reporting -> Tax Reports -> Mexico -> Journal Entry.
For detailed information, refer to the report documentation by choosing the i button.

In addition to the XML file, the report also generates a corresponding tree output that contains
the total credit/debit details of all G/L accounts.
The ALV output consists of documents that are posted for the date you enter on the report
selection screen.

3. On the RPFIGLMX_JE_DETAILS report selection screen, enter the following mandatory

parameters:
a. Company Code
b. Fiscal Year
c. Posting Date
d. Requirement Type
The requirement type classfies the reason for the file generation. The reasons could be
one of the following:
i. Requirement of the government
This is indicated by the codes AF (audit of the company) and FC (crosscheck a
vendor/customer audit )
ii. Tax refung purposes
This is indicated by the codes DE (tax refund) and CO (tax compensation for
future tax declarations).
e. Order number and process number
f. Down payment indicator
The system, by default, displays A as the down payment indicator. If you add additional
indicators (for example, K), the report then considers both A and K as indicators, and
processes documents belonging to these indicators as down payment documents.
 If you remove A and enter another value (for example, M), the report only considers
relevant documents as down payment documents. In this case, documents with down
payment indicator A are considered as regular invoices.
g. File path
4. Once the XML file has been generated, you can download the file on to your presentation
server.
From the report output screen, choose the Download File (F9) button. The system automatically
calls the RFASLDPC program, that you use to download the file.
On the RFASLDPC program selection screen, in the Character Set Conversion group box, choose
one of the following radio buttons:
 No Character Set Conversion
Choose this button if your system is Unicode active.
 Manual Entry of Code Page
Choose this button if your system is not Unicode. Also, enter 4110 in the Target Code
Page field.
To check if your system is Unicode or not, from the menu bar, choose System -> Status. The field
Unicode System will indicate the status.

5. The RPFIGLMX_JE_DETAILS report must also include the electronic invoicing data. This includes
the CFDI number (UUID), tax ID of the issuer (RFC), and the CFDI amount. Note that the
electronic invoicing data is included only in the vendor and customer documents (such as
invoices, credit memos, payments)
UUID is 36 characters long and is available in both FI and SD if you have already implemented
the CFDI solution.
RFC is normally fetched from the vendor master data or the customer master data.

The UUID and RFC data are stored in the individual fields. You can get these details as follows:
a. If these data are not available or are not maintained in the travel module, use the
FIGLMX_TVEX BAdI to get the details.
b. If these data are not available or are not maintained in the CFDI table for FI and SD
documents, use the FIGLMX_CFDI BAdI to get the details.
c. If these data are not available or are not maintained in the header text of FI documents,
the RPFIGLMX_JE_DETAILS report will get the details.
d. If these data are stored in a Z-table, the GET_UUID_DETAILS method of the
FIGLMX_EDIT BAdI gets the details based on the logic that you implement.
e. If you are using the CFD_CBB solution and these data are stored in a Z-table, the
GET_CFD_CBB_DETAILS method of the FIGLMX_EDIT BAdI gets the details based on the
logic that you implement.

The graphic below depicts the digital signature process for electronic invoicing data:
Additionally, the RPFIGLMX_JE_DETAILS report includes the payment method data. This data is
broadly classified into the following sections:
 Check
This section consists of the following fields/details:
o Check number
o Source bank code, source bank name (if it is a foreign bank), and source bank
account
o Date, beneficiary, and RFC
o Amount, currency, and exchange rate
 Bank transfer
This section contains the following fields/details:
o Source bank account, source bank code, and source bank name (if it is a foreign
bank)
o Target bank account, target bank code, and target bank name (if it is a foreign
bank)
o Date, beneficiary, and RFC
o Amount, currency, and exchange rate
 Other payment method
This section contains the following fields/details:
o Payment method code
o Date, beneficiary, and RFC
o Amount, currency, and exchange rate

If the vendors’ checks or bank transfers are done via the automatic payment program
(transaction F110), the RPFIGLMX_JE_DETAILS report will receive the data automatically. In the
 event the vendors’ checks or bank transfers are not done via automatic payment program, then
use the FIGLMX_EXIT BAdI to get the data. The CHANGE_DOCUMENT_DETAILS method in the
BAdI enables you to do this.
For vendors’ manual payments and for all customers’ payment types, use the following BAdIs to
include the data in the XML file:
 FIGLMX_BANK
You use this BAdI to map SAP bank number to CLAVE numbers defined by the SAT. This
BAdI contains the MAP_BANK_NUMBER_TO_CLAVE method that you must implement
and also use it maintain your logic, as per your business requirements.
 FIGLMX_EXIT
This BAdI is called internally in the RPFIGLMX_JE_DETAILS report. Implement this BAdI,
activate the CHANGE_DOCUMENT_DETAILS method, and also maintain your logic as per
your business requirements.

The graphic below represents the payment method flow and usage of the respective BAdIs:

6. If you have not implemented the standard CFDI solution, make the following configurations to
the document text field:
For UUID in FI
a. Execute transaction OBT8 and choose the Create button
b. Enter YUUD in the Text ID field and provide an appropriate description
c. Save your entries
For UUID in SD
a. Execute transaction VOTXN
b. Select the Header button against Billing Doc. and choose Change.
c. First, create the dialog structure if it does not exist
 d. Then under Dialog Structure, select Text ID's in Textprocedure and choose New Entries
e. Enter YUUD in the TxPrc field and provide an appropriate description
f. Assign the text procedure to the document type used. You do this by selecting Text
procedure assignment under Dialog Structure.

For RFC in FI

a. Execute transaction OBT8 and choose the Create button

b. Enter RFC in the Text ID field and provide an appropriate description
c. Save your entries

For RFC in SD
a. Execute transaction VOTXN
b. Select the Header button against Billing Doc. and choose Change.
c. First, create the dialog structure if it does not exist
d. Then under Dialog Structure, select Text ID's in Textprocedure and choose New Entries
e. Enter RFC in the TxPrc field and provide an appropriate description
f. Assign the text procedure to the document type used. You do this by selecting Text
procedure assignment under Dialog Structure.

7. The following Business Add-Ins (BAdIs) are used in the XML file processing:
a. FIGLMX_BANK
You use this BAdI to map SAP bank number to CLAVE numbers defined by the SAT. This
BAdI contains the MAP_BANK_NUMBER_TO_CLAVE method that you must implement
and also use it maintain your logic, as per your business requirements.
b. FIGLMX_CFDI
You use this BAdI to get the CFDI details of invoices.
This BAdI is called internally in the RPFIGLMX_JE_DETAILS report.
This BAdI contains the GET_CFDI_DETAILS method that reads the FI and SD documents’
CFDI details from the CFDI database table. Note that this method is internally
implemented at SAP. You just need to implement and activate this method to get the
respective code.
c. FIGLMX_EXIT
This BAdI is called internally in the RPFIGLMX_JE_DETAILS report. You must implement
this BAdI and activate the below-mentioned methods to get the respective code.
This BAdI contains the following methods:
i. GET_UUID_DETAILS
This method fetches the UUID (that is, the CFDI number)
ii. CHANGE_FILE_NAME
This method enables you to change the file name in the file system.
iii. ADD_DOCUMENT_DETAILS
This method fetches the special ledger documents and returns them using the
JE_HEADER and JE_ITEMS changing parameters to the report output.
iv. GET_CFD_CBB_DETAILS
This method fetches the CFD details.
 v. CREATE_TRIGGER_FILE
This method allows you to create a trigger file.
vi. CHANGE_DOCUMENT_DETAILS
This method enables you to change the document details.
d. FIGLMX_TVEX
You use this BAdI to display the travel expenses incurred from using SAP Travel
Management (FI-TV). Due to the integration with Financial Accounting and Sales and
Distribution, the data from travel expenses (consisting of vouchers and invoices) is
transferred to these components. This data must be included in the XML file generated
by the RPFIGLMX_JE_DETAILS report.
This BAdI contains the following GET_TVEX_DETAILS method that enables you to modify
the travel expense details.
Customizing for Company Code Data

To customize company code data for use in Mexico, make settings as described below. For more
information on company codes, see Company Code.

Procedure

1. Create a parameter in the company code master data to store the new GL indicator. To do so,
execute transaction SM30 and enter V_T001I in the Table/View field.
2. In the following screen, choose the New Entries button.
3. Make the following entries:
a. Par. type = MX_NGL
b. Description = Mexico new GL indicator
c. Length = 1
d. ISO code = MX
4. In Customizing for Financial Accounting (New), choose Financial Accounting Global Settings
(New) -> Global Parameters for Company Code -> Enter Global Parameters.
5. Double-click the relevant company code.
6. On the subsequent screen, choose the Additional Data pushbutton.
7. In the Mexico new GL indicator field, enter X if you have activated the new GL functionality.
Leave the field empty if you have not activated the new GL functionality.