Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Enable POS extensibility for Norway in Microsoft Dynamics AX 2012 R2 for Retail


Introduction

This binary update enables additional extensibility options required to implement the localization functionality for Norway for Microsoft Dynamics AX 2012 R2 for Retail. This article provides an overview of the steps required to enable and implement the localization, as well as an overview of the components of the update.

↑ Back to the top


Overview

The localization for Norway is implemented in Microsoft Dynamics AX 2012 R3 for Retail. It consists of:

  • A Retail Headquarters update that is required to set up the localization features and to generate the mandatory periodic reporting. See KB 4462498 to review and download the update;
  • A Retail Channel update that includes additional extensibility options and corresponding extensions that implement the localization features. See KB 4462547 to review and download the update.

The KB articles referenced above describe all the configuration and setup steps needed to enable the localization.

In order to enable the Retail localization for Norway in Microsoft Dynamics AX 2012 R2 for Retail, you need to:

  1. Apply this update to POS to add the extensibility options;
  2. Manually port the Retail Headquarters update KB 4462498 to Microsoft Dynamics AX 2012 R2 for Retail Headquarters;
  3. Manually port the Retail Channel SDK extensions from the update KB 4462547 to Microsoft Dynamics AX 2012 R2 Enterprise POS SDK;
  4. Perform configuration and setup steps described in the articles KB 4462498 and KB 4462547.

↑ Back to the top


SDK overview

The below sections provide an overview of the extensibility options required to implement the Retail localization solution for Norway.

The solution consists of a new project, new interfaces and a new service. Besides that, several existing interfaces are extended with new methods.

  • The ReceiptTransactionTypeService project is located under the Retail SDK\POS Plug-ins\Services folder and is part of the Services solutions.
  • The new interface of ITaxOverrideTrigger is part of the Contracts assembly.
  • The existing interface of IBatchOperationTrigger is extended with three new methods:
    • PreSaveCloseBatch is called before saving a closed batch data;
    • PreBuildReport is called before building a daily report;
    • PostBuildReport is called after building a daily report with possibility to extend it.
  • The existing interface of IItemTrigger is extended with new method:
    • PostPriceCheck is called after checking the item price.

These new interfaces should be implemented and used in the Norway trigger localization project.

Receipt transaction type service

The new ReceiptTransactionTypeService service is added to enable the customization of logic determining the type of receipt for a POS transaction. This service works the same way as other services and is loaded by MEF. It provides the GetReceiptTransType method, which could be called from localization triggers to determine the type of receipt for a POS transaction, for example in order to resolve the receipt title field.

Tax override trigger

The new TaxOverride trigger is added to enable the customization of the tax override process. This trigger works the same way as other triggers and is loaded by MEF. It provides the following four methods: PreOverrideTaxLine, PostOverrideTaxLine, PreOverrideTaxTransaction and PostOverrideTaxTransaction; the methods are called before and after overriding tax for a sales line and a sales transaction, respectively.

The new ITaxOverrideTrigger interface was added to the Contracts library. This interface describes the PreOverrideTaxLine, PostOverrideTaxLine, PreOverrideTaxTransaction and PostOverrideTaxTransaction methods.

The PreOverrideTaxLine and PreOverrideTaxTransaction methods can interrupt the tax overriding process and show messages via the standard PreTriggerResult object. To use the TaxOverride trigger, a new class needs to be created. This class should implement the ITaxOverrideTrigger interface. In this case, MEF will load the class during the application startup.

Norway triggers

To complete the Norway localization the NorwayTriggers project should be implemented as standard POS triggers that are loaded if the ISO code field of the functionality profile of POS is set to NO.

  • NorwayApplicationTrigger should implement the IApplicationTrigger interface and overrides the ApplicationStart method in order to initialize the registration state.
  • NorwayBatchOperationTrigger should implement the IBatchOperationTrigger interface and overrides the SaveCloseBatch, PreSaveCloseBatch and PreBuildReport methods:
    • The SaveCloseBatch method updates shift grand total counters;
    • The PreSaveCloseBatch method calculates Norway-specific shift date and saves in order to transmit it to HQ;
    • The PreBuildReport method overrides X and Z reports build logic.
  • NorwayPrintingTrigger should implement the IPrintingTrigger interface and overrides the GetReceiptFieldInfo method. The method receives the IReceiptField and the IReceiptPrintingContext objects and calculates the value of the receipt field being printed.
  • NorwayTransactionTrigger should implement the ITransactionTrigger interface and overrides the PreEndTransaction and SaveTransaction methods:
    • The PreEndTransaction method receives the IPosTransaction object and performs the registration of the retail transaction;
    • The SaveTransaction method receives the IPosTransaction object and finalizes the registration of the retail transaction by saving the fiscal registration information.

↑ Back to the top


Update information

If you are encountering an issue downloading, installing this update, 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.

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:

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.

How to obtain the updates

The updates are available for manual download and installation from Microsoft Download Center.

Prerequisites

You must have one of the following products installed to apply this update:

  • Microsoft Dynamics AX 2012 R2

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the update.

↑ Back to the top


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Keywords: kbAutoHotfix, kbQFE, kbnoloc, kbsurveynew, kbMBSQuickPub, kbMBSPartner, kbExpertiseAdvanced, kbExpertiseBeginner, kbExpertiseInter

↑ Back to the top

Article Info
Article ID : 4462550
Revision : 8
Created on : 9/14/2018
Published on : 9/14/2018
Exists online : False
Views : 255