Microsoft KB Archive Search

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.

  1. Home
  2. A duplicate error occurs when you upgrade the data for purchase orders by using the Microsoft Dynamics AX 2012 upgrade scripts

A duplicate error occurs when you upgrade the data for purchase orders by using the Microsoft Dynamics AX 2012 upgrade scripts

This article applies to Microsoft Dynamics AX for all regions.

↑ Back to the top

Symptoms

Assume that you have a purchase order that has several Misc. charges codes used in Microsoft Dynamics AX 2012. When you upgrade the data for the purchase order by using the Microsoft Dynamics AX 2012 upgrade scripts, a duplicate error occurs. This problem occurs when the updateVendPurchOrderJour method creates MarkupTrans records.

↑ Back to the top

Resolution

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/support/
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.

↑ Back to the top

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:
  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.


For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Microsoft Dynamics AX 2012 installed to apply this hotfix.

Restart requirement

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

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Axupgar.aldNot applicable349,3385-Jun-1218:51Not applicable
Axupgcs.aldNot applicable272,04411-May-126:42Not applicable
Axupgda.aldNot applicable277,72831-May-1216:20Not applicable
Axupgde-at.aldNot applicable304,31931-May-1216:20Not applicable
Axupgde-ch.aldNot applicable304,24031-May-1216:20Not applicable
Axupgde.aldNot applicable304,31931-May-1216:20Not applicable
Axupgen-au.aldNot applicable272,03811-May-126:42Not applicable
Axupgen-ca.aldNot applicable272,32411-May-126:42Not applicable
Axupgen-gb.aldNot applicable271,70511-May-126:42Not applicable
Axupgen-ie.aldNot applicable271,73411-May-126:42Not applicable
Axupgen-in.aldNot applicable272,04411-May-126:42Not applicable
Axupgen-my.aldNot applicable272,09111-May-126:42Not applicable
Axupgen-nz.aldNot applicable272,04111-May-126:42Not applicable
Axupgen-sg.aldNot applicable272,13711-May-126:42Not applicable
Axupgen-us.aldNot applicable272,04610-May-129:49Not applicable
Axupgen-za.aldNot applicable271,72411-May-126:42Not applicable
Axupges-mx.aldNot applicable304,37431-May-1216:20Not applicable
Axupges.aldNot applicable303,22831-May-1216:20Not applicable
Axupget.aldNot applicable272,04411-May-126:42Not applicable
Axupgfi.aldNot applicable283,05331-May-1216:20Not applicable
Axupgfr-be.aldNot applicable309,70231-May-1216:20Not applicable
Axupgfr-ca.aldNot applicable310,80631-May-1216:20Not applicable
Axupgfr-ch.aldNot applicable310,80631-May-1216:20Not applicable
Axupgfr.aldNot applicable309,70231-May-1216:20Not applicable
Axupghe.aldNot applicable406,7105-Jun-1218:51Not applicable
Axupghu.aldNot applicable272,04411-May-126:42Not applicable
Axupgis.aldNot applicable282,84931-May-1216:21Not applicable
Axupgit-ch.aldNot applicable295,64831-May-1216:21Not applicable
Axupgit.aldNot applicable295,64831-May-1216:21Not applicable
Axupgja.aldNot applicable272,04411-May-126:43Not applicable
Axupglt.aldNot applicable272,04411-May-126:43Not applicable
Axupglv.aldNot applicable272,04411-May-126:43Not applicable
Axupgnb-no.aldNot applicable274,77631-May-1216:21Not applicable
Axupgnl-be.aldNot applicable288,33831-May-1216:21Not applicable
Axupgnl.aldNot applicable288,49531-May-1216:21Not applicable
Axupgpl.aldNot applicable272,04411-May-126:43Not applicable
Axupgpt-br.aldNot applicable272,04411-May-126:43Not applicable
Axupgru.aldNot applicable272,04411-May-126:43Not applicable
Axupgsv.aldNot applicable278,93831-May-1216:21Not applicable
Axupgth.aldNot applicable501,96431-May-1216:21Not applicable
Axupgtr.aldNot applicable272,04411-May-126:43Not applicable
Axupgzh-hans.aldNot applicable347,01211-May-126:43Not applicable
Performance_updatestatistics.sqlNot applicable7409-Jun-115:42Not applicable
Pi_upgradeax4.xpoNot applicable10,099,3915-Jun-1219:03Not applicable
Pi_upgradeax5.xpoNot applicable10,297,2415-Jun-1219:03Not applicable
Privateproject_ax40preprocessing_si.xpoNot applicable1,5709-Jun-115:42Not applicable
Privateproject_ax40preupgradeframework_batch.xpoNot applicable55,97013-Apr-117:23Not applicable
Privateproject_ax50preupgradeframework_batch.xpoNot applicable109,85413-Apr-117:23Not applicable
Sharedproject_ax50preupgrade_lean.xpoNot applicable2,013,2829-Jun-115:42Not applicable
Sharedproject_ax50preupgrade_retail.xpoNot applicable836,74810-May-129:49Not applicable
Sharedproject_ax50preupgrade_si.xpoNot applicable7,1839-Jun-115:42Not applicable
Upgradeax4.xpoNot applicable10,018,5685-Jun-1219:03Not applicable
Upgradeax5.xpoNot applicable10,203,6485-Jun-1219:03Not applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein 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: kbsurveynew, kbnoloc, kbmbsquickpub, kbmbsmigrate, kbexpertiseinter, kbqfe, kbexpertiseadvanced, kb, kbautohotfix, kbhotfixserver, kbexpertisebeginner

↑ Back to the top

Article Info
Article ID : 2721117
Revision : 2
Created on : 2/17/2017
Published on : 2/17/2017
Exists online : False
Views : 82