Updates for i. SAF are available for the Lithuanian version of Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, and Microsoft Dynamics AX 2009 SP1

The changes in the hotfix enable the updates for the Standard Audit File in the Lithuanian version of Microsoft Dynamics AX 2012 R3.
In order to meet the new requirements, there is a need to implement a new functionality in Microsoft Dynamics AX program, which allows the required data of issued and received invoices to be exported. The name of this function will be „i.SAF register”.
The decree is effective from 1st of October 2016. The date when the registers should be provided for the tax authority is till 20 November 2016.
All relevant information can be found: http://www.vmi.lt/cms/en/pvm-saskaitu-fakturu-registru-duomenu-tvarkymo-ir-pateikimo-taisykliu-projektas

Setup

1. Open AOT, export XSLT file from the applicable resource into a folder (say, C:\TMP\XSL).

   HU Invoice exporting 2016	AifOutboundPortReportInvoiceList2016_HU
   PL SAF Accounting books	AifOutboundPortReportSAFAccountBooks_PL
   PL SAF Bank statement	AifOutboundPortReportSAFBankStatement_PL
   PL SAF Inventory	AifOutboundPortReportSAFInvent_PL
   PL SAF VAT invoices	AifOutboundPortReportSAFVATInvoice_PL
   PL SAV VAT register	AifOutboundPortReportSAFVATSalesPurch_PL
   LT i.VAZ transportation documents	AifOutboundPortReportIVAZTransportDoc_LT
   LT I.SAF	AifOutboundPortReportISAF_LT
   -	AifOutboundPortValueMapping

2. System administration >> Setup >> Services and Application Integration Framework >> Outbound ports for electronic audit reports.
   1. Click "Create / Update ports". This will populate the list of default ports. SOFTWARE UPDATE DETAILS \ This software update is scheduled to ship in the following service pack(s).

      HU Invoice exporting 2016	"Invoice list 2016 (Hungary)"	InvoiceList2016Hungary	InvoiceList2016Hungary
      PL SAF Accounting books	"SAF Accounting books (Poland)"	SAFAccountingBooksPoland	SAFAccountingBooksPoland
      PL SAF Bank statement	"SAF Bank statement (Poland)"	SAFBankStatementPoland	SAFBankStatementPoland
      PL SAF Inventory	"SAF Inventory (Poland)"	SAFInventoryPoland	SAFInventoryPoland
      PL SAF VAT invoices	"SAF VAT invoices (Poland)"	SAFVATInvoicesPoland	SAFVATInvoicesPoland
      PL SAF VAT register	"SAF VAT sales and purchase register (Poland)"	SAFVATSalesAndPurchaseReg	SAFVATSalesAndPurchaseReg
      LT i.VAZ transportation documents	"i.VAZ transportation documents (Lithuania)"	iVAZTransportationDocuments	iVAZTransportationDocuments
      LT i.SAF	"i.SAF (Lithuania)"	iSAFLithuania	iSAFLithuania

   2. Set "Import XSLT" equal to the path from step 1 (C:\TMP\XSL).
   3. Set "Default export path" to the path you expect the reports to be saved to. (say, C:\TMP\OUT\InvoiceList2016Hungary)
   4. Click "Create / Update ports".
   5. The XSL is imported into Dynamics AX with the default ID.
   6. The "XSLT ID" field is st to reference the XSL transformation.
   7. The outbound AIF port is created and initialized with a list of needed services.

Notes and recommendations

1. For better performance please make sure the parameter "Execute business operations in IL" is enabled (Tools >> Options >> Development >> General). Please note that global compilation and rebuilding IL is a mandatory step after the hotfix installation.
2. The folder where the XSL was exported to (step 1) is used only for editing the XSL (if needed) and uploading it back to Dynamics AX. The transformation does not use the file in the folder after the step 2.d.
3. For debugging purpose, you may want to get the non-transformed XML. To achieve that clear the field " XSLT ID".

Exporting the report file

1. By default, report menu items are added to General ledger >> Reports >> External >> Services and Application Integration Framework. For example, the below is applicable to Invoice list 2016 (Hungary).
   1. Select the invoice date and/or invoice ID ranges (fields Invoice date / "From", "To", Invoice ID / "From", "To").
   2. Selected dates / invoice IDs affect the query anges, not vice versa. To use advanced filtering please use "Select" button.
   3. Select the "Format" value (by default the format created on Setup, step 2.a is used)
   4. Select the "Filename" value (by default the "Default export path" from Setup, step 2.c is used)
2. Click OK. The report is exported to the specified path.

Appendix I

Shared setup

This section contains settings that are used by multiple reports.Setting up the Sales tax reporting codesSales tax reporting codes is a standard feature, extended for the purpose of electronic reporting in XML format. The below example illustrates how the feature should be used in case of SAF VAT invoices and SAF VAT sales and purchase register reports; you need to setup tax reporting codes and map them to elements of XML schema. The below examples refer to the VAT sales and purchase registers report.

1. Save the schema file (for example, Schemat_JPK_VAT(1)_v1-0.xsd) into a folder (say, C:\TMP\XSD).
2. Open the Sales tax reporting XML codes form (General Ledger >> Setup >> Sales tax >> External >> Sales tax reporting XML codes)
3. Click the Import button. Select the schema file with and click "OK".
4. New record in XML schemas list will be created. Choose Type of schema (for example, "SAF VAT sales and purchase register (Poland)").
5. Open the Reporting codes form (General Ledger >> Setup >> Sales tax >> External >> Sales tax reporting codes). Map reporting codes to xml schema elements that refer to VAT (for example, ones that start from "K_", like "K_10").
   
   Notes
   
   • Amounts on these reporting codes will be exported to selected tags.
   • If tax transaction contains reporting codes which are mapped both to sales and purchase sides, it will be present both in sales and purchase parts of resulting xml file.
   • You can use arithmetic operations during the mapping, effectively allowing mapping multiple tax reporting codes to one schema element (see below: element P_13_1 refers to the reporting code "1001" which is a sum of reporting code "1" and (-) reporting code "2").

Value mapping (value replacement)

In some cases, the reporting data should be transformed in a uniform way throughout the whole report (or multiple reports), especially to support data that does not exist in AX.

Example: Lithuanian i.SAF report should display special tax codes according to the VAT classification approved by Lithuanian tax authority (further mentioned as "PVM codes") instead of AX tax codes (further mentioned as "TAX codes"); it is not a problem if TAX codes exactly match PVM codes, but that is not always possible.

In that case value mapping / replacement should occur in the XSLT. There are several ways of doing that:

• Implementing the mapping in the original XSLT
• Implementing the in a separate XSLT and applying it before the original XSLT

The second approach is more scalable; please find the example below.

1. Export the AifOutboundPortValueMapping.xslt from the resource into a folder (say, C:\TMP\XSL). If needed – rename to match the beahavior (say, ReplaceTaxCodeLTiSAF.xslt).
2. Edit the XSLT (any text editor – from Notepad to Visual Studio).
   1. See the "Add replacement pattern(s)" area; it contains replacement patterns (one or multiple) (in the example - one pattern called TaxCodeLTiSAF); pattern is a list of replacement pairs 'from - to'; hope the semantics is quite self-explanatory.

      <ReplacementPattern name="TaxCodeLTiSAF">
      <Replace>
      
              <From>VAT19</From>
      
              <To>PVM19</To>
      
            </Replace>
      
            <Replace>
      
              <From>VAT18</From>
      
              <To>PVM18</To>
      
            </Replace>
      
          </ReplacementPattern>

   2. Edit (add/remove) replacement rules (and patterns, if more than one is needed).
   3. See the "Add XPath(s) to transform here" area; here XPath(s) that should be updated should be listed with what replacement pattern should be applied to each.

      <xsl:template match="//TaxTrans/TaxTransactionView/TaxCode">
      <xsl:call-template name="Replace">
      
            <xsl:with-param name="ReplacementPattern" select="'TaxCodeLTiSAF'"/>
      
            <xsl:with-param name="IfFromNotFoundUseOriginal" select="true()"/>
      
          </xsl:call-template>  
      
        </xsl:template>

   4. By default, if the replacement pattern does not contain the applicable rule, no substitution is performed. In the example above TAX code "VAT0" will remain as "VAT0" in the report. To replace all non-set up TAX codes with blank values use the parameter IfFromNotFoundUseOriginal set to ‘false()’ (<xsl:with-param name="IfFromNotFoundUseOriginal" select="false()"/>)
3. Save the XSLT.
4. Import the XSLT into AX.
   1. On the "Outbound ports for electronic audit reports" form select the "i.SAF (Lithuania)" port, create new XSLT transformation reference, right-click on "XSLT ID", "View details".
   2. On the "XSLT repository" create new record, "XSLT ID" = "ReplaceTaxCodeLTiSAF", save.
      • Click "Import", select the XSLT (e.g. C:\TMP\XSL\ReplaceTaxCodeLTiSAF.xslt), "Open".
   3. On the "Outbound ports for electronic audit reports" form select the "ReplaceTaxCodeLTiSAF" XSLT; if needed, use button "Up" to place the "ReplaceTaxCodeLTiSAF" XSLT higher ("before") the "iSAFLithuania" XSLT.
5. Run the report, see tax codes are replaced.
   
   Note If multiple replacements are needed, multiple patterns can be created in one XSLT or multiple XSLTs (each containing one pattern) can be chained as in 4.c above.

Appendix II: Country/region-specific reports

Poland

SAF VAT invoices and VAT sales and purchase register:

Please refer to the Setting up the sales tax reporting codes chapter for examples.

Lithuaniai.VAZ

The periodic procedure for generating i.VAZ file is available at General Ledger\Reports\External\Services and Application Integration Framework\i.VAZ transportation documents (Lithuania):

User can select the documents according to the condition defined in the dialog window i.VAZ transportation documents (Lithuania).
Ledger\Reports\External\Services and Application Integration Framework\i.VAZ transportation documents (Lithuania):

The User should setup the transportation details required in i.VAZ format using the form Transportation details accessible from the form.

• Sales order
• Sales packing slip journal
• Sales invoice journal
• Free text invoice
• Project invoice proposal
• Project invoice journal
• Purchase order
• Vendor invoice creation
• Vendor invoice journal
• Inventory transfer order
• Inventory transfer order history

New fields groups are added in the form Packing slip:

i.VAS

• Send to i.VAS should be marked for documents, which should be exported to i.VAZ.
• Document type - New transport document, Amendment; Splitting of cargo; Cancellation.
• Sending status –None or Sent

Delivery address allows to change the address after export to i.VAZ and repeat the document export with a new address as Amendment.

Splitting of cargo is the type for documents, when a part of goods from New document is returned.

Cancelation

• Reason code
• Reason comments

After the doc is exported to i.VAZ the Sending status becomes the value Sent. Using the button Transportation details user can change the transportations details.

i.SAF

1. The periodic procedure for generating i.SAF file is available at GeneralLedger\Reports\External\Services and Application Integration Framework\i.SAF (Lithuania). User can select the documents according to the condition defined in the dialog window i.VAZ transportation documents (Lithuania).
2. Schema and file size limitations can be supported by setting maximum number of counteragents and invoices in the report. Set Error tolerance to Error to abort report execution if data volume exceeds the expected value; set Error tolerance to Warning to truncate the report if data volume exceeds the expected value.
3. After the data is exported to i.SAF, the Sending status changes to Sent. Invoice type (SF, DS, KS, AN, VS, VD, VK) and the Sending status can be edited in customer, vendor and project invoice journals.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx

You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+Contacts

Customers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm

In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.