1.- 0002042663 informativa

4
7/21/2019 1.- 0002042663 INFORMATIVA http://slidepdf.com/reader/full/1-0002042663-informativa 1/4

Upload: javier-andrade

Post on 04-Mar-2016

230 views

Category:

Documents


0 download

DESCRIPTION

nota sap ce

TRANSCRIPT

Page 1: 1.- 0002042663 INFORMATIVA

7/21/2019 1.- 0002042663 INFORMATIVA

http://slidepdf.com/reader/full/1-0002042663-informativa 1/4

Page 2: 1.- 0002042663 INFORMATIVA

7/21/2019 1.- 0002042663 INFORMATIVA

http://slidepdf.com/reader/full/1-0002042663-informativa 2/4

The solution is planned for releases from 600 onwards.

Chart of Accounts:

The classification of the Chart of Account by the government ’s grouping code is planned to be done via a FSV: Financial Statement Version(trans.FSE2).

The structure of the Grouping Code shall be defined in the FSV and the GL accounts of the company assigned to the corresponding code.

Because in the chart of accounts of SAP only main G/L Accounts exists (no sub -accounts can be defined), an according to what the governmentexplained, only the first level of the Grouping Code shall be used. This is:

1. Cash

2. Banks3. Investments4. Customers5. …

With the use of the FSV, there is no need to enhance GL master data to enter SAT code. FSV would be a one time activity and makes easy toadd/modify FSV items. Besides, all the relevant GL accounts required for the Balances reporting are already defined in the FSV.

15.08.2014

To be able to map the Chart of Accounts to the Grouping Code and Nature, a new Financial Statement Version has to be defined. Please refer tothe document "Customizing Activities for Electronic Accounting" where are defined the steps to create the new Financial Statement Version, theGrouping Codes and Nature, and how to assign the accounts.

On August 6th, the Tax Authorities informed that the XML file for the balances of the accounts is now only needed in January 2015. Then, inOctober only the Chart of Accounts is required, the other two XML files, Balances and Journal Entries are required in 2015. SAP will still releasethe XML files for the Chart of Accounts and for the Balances by the end of September.

19.08.2014

Today the government published that also the chart of accounts is now required in January 2015.

With this, all three files have now to be provided in January 2015.

29.09.2014

Chart of Accounts and Accounts Balances XML files:

The report to generate the XML files for the chart of accounts and for the accounts balances is in the pilot tests phase. The report will be releasedfor all customers on October 8 th via OSS notes:

- 2066631 - Mexico Electronic Accounting - DDIC Note

- 2050349 - Mexico Electronic Accounting - Chart of Accounts/Account Balances

Please note that a few header tags in the XML files definition in the Annex24 are still expected to be defined by the government. Once the missingheader tags are published, a correction for the code to generate the right format will be released.

Journal Entries XML files:

The report to generate the XML file for the Journal Entries is being developed. The release of this report is planned by the second week ofDecember.

Part of the data needed for this XML file, in case of income or expense Journal Entries, is the CFDI information: "UUID" (e-invoice number), the"RFC" (Tax Number of the issuer of the e-invoice) and the amount.

- The UUID* is a 36 char data. To be able to enter this information, header texts need to be defined:

1) In Sales&Distributions and in FI Accounts Receivables and Payables: If the CFDI standard functionality is used, the UUID field already exists. Ifthe functionality is not used, there is no need to setup the CFDI solution, only the field has to be defined.

2) In Material Management (transaction MIRO), an analysis is being done to determine the corresponding field

3) In Travel Management (transaction PR05), an analysis is being done to determine the corresponding field

- The RFC* will normally be taken from the vendor/customer master data.

In some cases such as “factoraje ” or imports via customs agents, the RFC could be different than the business partner for which the invoice iscreated. For those cases, to be able to get the right RFC, it has to be provided:

1) In Sales&Distributions and in FI Accounts Receivables and Payables: As for the UUID, the RFC will be stored in a Header Text.

2) In Material Management (MIRO), an analysis is being done to determine the corresponding field

3) In Travel Management (transaction PR05), an analysis is being done to determine the corresponding field

- The Amount will be taken from the total amount of the corresponding invoices journal entries.

Page 3: 1.- 0002042663 INFORMATIVA

7/21/2019 1.- 0002042663 INFORMATIVA

http://slidepdf.com/reader/full/1-0002042663-informativa 3/4

* To define fields of UUID and RFC in In Sales&Distributions and in FI Accounts Receivables and Payables, please refer to version 2 of theconfiguration document attached in this note.

The report will look for the UUID, RFC and amounts in the fields defined above. In case those fields are not used, there will be a BAdI, that will allowto get the information from a different place.

08.10.2014

OSS notes:

- 2066631 - Mexico Electronic Accounting - DDIC Note

- 2050349 - Mexico Electronic Accounting - Chart of Accounts/Account Balances

Is now planned to be released by Friday October 17th.

Some adjustments are being done based on the pilot tests and presentations comments, and a probable change of the code will be also needed,due to adjusted files formats that will be published by the government in the incomming weeks.

16.10.2014

The release of the notes will be delayed because the government hasn't published the changes to the XML files definition yet.

The current codes will require to be adjusted, then tested. Once the changes are published, it is estimated to take around one week for theadjustments and the tests, before releasing the notes.

04.11.2014

OSS notes:

- 2066631 - Mexico Electronic Accounting - DDIC Note

- 2050349 - Mexico Electronic Accounting - Chart of Accounts/Account Balance

have been released.

These notes contain the codes and objects for the report that generates the XML files for the Chart of Accounts and the Account Balancesaccording to the definition in Annex24 published on July 1st.

When the government publishes the changes, adjustments to the current code will be done accordingly and a new version of the note will becreated.

The report has the following execution parameters:

- Company Code: the report can be excuted to generate an XML file for one Company Code or a consolidated XML file for many companies, onlyif all these companies are part of the same Legal Entity (same Tax Number or "RFC") and share the same Chart od Accounts.

- FSV - Financial Statement Version: classifies the accounts according to the Grouping Code of the government and the nature.

- Account Group: allows to limit the accounts selection for one or many account groups

- Period: for which the data has to be selected.

According to the law the data has to be in Spanish. The report will select the long text of the account in language Spanish, if the long text does notexists in Spanish, the English long text will be used instead.

Because the government's validation tool for the XML files is not available yet, one option is to generate the XML file and attend one of thegovernment's offices (SAT), to check that the file generated is correct.

24.12.2014

The adjustments for the last changes to the XML files for the Chart of Accounts and the Account Balances, published on December 2014, areavailable in OSS notes:

2096590 - RPFIGLMX_EACCOUNTING General correction N1 (New SAP Note)

2104844 - Electronic Accounting DDIC Note D1 (New SAP Note)

Disclaimer

This message outlines our general product direction and should not be relied on in making a purchase decision. This message is not subject to

your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this message or todevelop or release any functionality mentioned in this message. This message and SAP's strategy and possible future developments are subjectto change and may be changed by SAP at any time for any reason without notice. The information in this message is provided without a warranty ofany kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this message, except if such damages were caused by SAP intentionally orthrough gross negligence.

Page 4: 1.- 0002042663 INFORMATIVA

7/21/2019 1.- 0002042663 INFORMATIVA

http://slidepdf.com/reader/full/1-0002042663-informativa 4/4

Other Attributes

Validity

References

This document is referenced by:

SAP Notes (2)

Attachments

16.12.2014

Software Component From Rel. To Rel. And SubsequentSAP_APPL 600 600

602 602

603 603

604 604

605 605

606 606

616 616

617 617

2096590 RPFIGLMX_EACCOUNTING: General correction (N1) 2050349 Mexico Electronic Accounting - Chart of Accounts/Account Balances

File Name File Size (KB) Mime TypeCustomizing Activities for Electronic Accounting(4).pdf 645 application/pdf

Accounts Grouping Code Nature V3.xlsx 92 application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

Planned delivery date for Legal Change