Skip to main content

Cumulative update 2 vs. Feature pack [AX 2012]

It was a little confusing at first what the Feature pack contained. This was release recently on in 1st February 2012. This release is targeted at the five key industries: Manufacturing, Distribution, Services Industries, Public Sector, and Retail. This release also incorporates Microsoft Dynamics ERP RapidStart Services.
One major thing you will notice when you install the Feature pack it is the same build as Cumulative update 2.

Below are two screenshots. The first is Cumulative update 2 and the second is the Feature pack. Notice a few things here:
  1. Build is the same. 6.0.947.280
  2. Feature pack I installed the Extensions model (Build 6.0.1108.0). This installs into the FPK layer and is meant to put you in a good position to install the industry specific models (which I have not installed on this scenario).
DAX2012CU2_2012-03-28_0744

DAX2012FeaturePack_2012-03-28_0745
In this blog entry I haven’t gone into the installation disk. In brief the install disk for the Feature Pack is the latest and it comes bundled with all these in there. Including the Retail component installation which is now part of the install wizard.

Correction update:
Feature pack kernel is actually 6.0.947.862

Just an additional note regarding the Extensions model. It is not option, it must be installed.
http://technet.microsoft.com/en-us/library/ee355075.aspx
Extensions
Microsoft Dynamics AX extensions for the following industries:
  • Process Manufacturing - Process manufacturing production and logistics for Microsoft Dynamics AX. Allows you to manage production, inventory, and costs in a process-controlled environment, such as in the food, chemical, and pharmaceutical industries.
  • Public Sector - Addresses the special controls, rules, and regulations of Public Sector organizations.
  • Project Management – Allows you to invoice customers for various billing scenarios, such as billing per unit of delivery and billing when a milestone is completed. You can also create customer and vendor retentions, and manage workers on projects.
  • Retail - Provides mid-market and large retailers a complete head office and point of sale (POS) solution.
ImportantImportant
This model is required when you install Microsoft Dynamics AX 2012 Feature Pack. If the model includes functionality that you do not plan to use, turn off the appropriate license codes and configuration keys. Do not uninstall this model to remove unwanted functionality. Uninstalling models that are released by Microsoft will place your system in an unsupported state. If you have uninstalled this model, you must reinstall it using the instructions found in How to: Export and Import a Model.



As Brandon mentions in his blog. Microsoft strong recommendation is you to update any clients on previous versions of AX 2012 to the feature pack. Here is the link to Microsoft page on this
The Microsoft Dynamics AX 2012 Feature Pack—Why You Should Adopt it Moving Forward 

Additional links:
List of build numbers
http://blogs.msdn.com/b/axsupport/archive/2012/03/29/overview-of-ax-build-numbers.aspx
Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more