Release Notes 6.3.1000.0008.01

 

 

 

Image result for bedrock shinola image 

  

Release Notes 

 6.3.1000.0008.01/Microsoft Dynamics AX

 

 

   

       Table of Contents

Enhancements

Enhancement #1 Allow the ability to filter on Variant Dimension values in the Variant Suggestions form

Enhancement #2 BOM Lines by BOM version report

Enhancement #3 Statement posting errors batch job

Fixes

Fix #1 Pending Invoice Workflow stopped: “Function InventCostTransCostList::newPlannedCostList has been used incorrectly.”

Fix #2 Pending Invoice: Delete Pending Invoices where there are no workflow options.

Fix #3 Pending Invoice Workflow stopped: Stopped (error): Insufficient inventory transactions with status Received.

Fix #4 Default Order Settings are not editable

Fix #5 Item cannot be entered on Inventory Journals: “No parameters for inventory”

Fix #6 Outbound Requests: additional sequence Send requests not created

Known Issues and Problems

Issue #1 Retail Hierarchy: Populated Default warehouses in Basic product properties cannot be deleted 

Workaround

Issue #2 Retail Hierarchy: Populated Default warehouses in Basic product properties does not update Default and Site specific order settings

Workaround

Revision History

 

 

 

Enhancements

 

 

Enhancement #1 Allow the ability to filter on Variant Dimension values in the Variant Suggestions form

Ticket 10896

 

In Variant suggestions, the Variant Dimensions can be filtered to specify variants that should be created.

  • Filters can be applied to the Variant Dimensions Configuration, Size, Color and Style or any combination within.
  • The Select check box can be used to select specific variants to create.

Note: The Select all feature will select all variants regardless of filters applied.

 

 

Enhancement #2 BOM Lines by BOM version report

Ticket 22251

 

A custom report has been created to populate information per one BOM Version.

  • A new menu item has been added to the Report section on the Area page in Inventory Management
  • Menu item is Lines by BOM Version
  • Path is: Inventory Management>Reports>Bill of Materials>Lines by BOM Version
  • Parameter to run is one BOM Version
  • Report includes specified Header and Line information per one BOM Version

 

 

Enhancement #3 Statement posting errors batch job

Ticket 21969

 

Sunrise Technologies wrote a batch job which will search the batch jobs Post statement and Post statement – FCO for Company FCO.  This new batch job identifies any errors that prevented retail sales orders from automatically invoicing.

The name of the new batch job is BMC_4725_FindErrorBatchJob.

Up until now, this new batch job could only be run from AOT by an admin user.  The enhancement is that the new batch job has been mapped to Retail module menu so that any user with access to the Retail module can run the new batch job.

To run BMC_4725_FindErrorBatchJob, follow this path:

FCO > Retail > Periodic > POS posting > Statement posting errors.

 

 

 

Fixes

Fix #1 Pending Invoice Workflow stopped: “Function InventCostTransCostList::newPlannedCostList has been used incorrectly.”

Ticket 21621

 

Problem: A pending vendor invoice stops in workflow due to the error message “Function InventCostTransCostList::newPlannedCostList has been used incorrectly”.

 

Fix: A job has been created that corrects the issue and allows workflow to be resumed.  When this error occurs, a ticket should be submitted to have IT run the job that resolves this issue.  Once the job is run, resume workflow on the Pending invoice.

 

Fix #2 Pending Invoice: Delete Pending Invoices where there are no workflow options

Ticket 22735

 

Problem: A pending invoice cannot be approved, rejected or deleted.

 

Fix: A job has been created that allows the Pending Invoice to be deleted and then a new pending invoice can be created if needed.  When this problem occurs, a ticket should be submitted to have IT run the job that resolves this issue.  Once the job is run, delete the Pending Invoice and then create a new

 

Fix #3 Pending Invoice Workflow stopped: Stopped (error): Insufficient inventory transactions with status Received

Ticket 22768

 

Problem: A pending vendor invoice stops in workflow due to the error message “Insufficient inventory transactions status Received.”  The root cause of this is that a space or tab is entered after the Packing slip number in Inventory transactions.  While a tab cannot be manually keyed in to the Packing slip number, it can be pasted in.

 

Fix: A job has been created to fix the data issue in the Packing slip number in Inventory transactions.  When this problem occurs, a ticket should be submitted to have IT run the job that resolves the issue. 

 

Fix #4 Default Order Settings are not editable

Ticket 18645 & 22741

 

Problem: When default warehouse values are added to the Retail Hierarchy Category and the Item is assigned to that category, the Default Order Settings and Site Specific Order settings are not editable.

 

Fix: A job has been created that allows the default and site specific order settings to be edited.  When this problem occurs, a ticket should be submitted to have IT run the job that resolves the issue.  Once the job is run, the Default & Site specific order settings can be edited.

 

Fix #5 Item cannot be entered on Inventory Journals: “No parameters for inventory”

Ticket 22741

 

Problem: When attempting to add an item to a Transfer Journal that is in the state of Fix #4, the error message will populate as “No parameters for inventory” and the item cannot be placed on the journal.

 

Fix: A job has been created that allows the default and site specific order settings to be edited.  When this problem occurs, a ticket should be submitted to have IT run the job that resolves the issue.  Once the job is run, the Item can be entered on a Transfer Journal.

 

 

 

Fix #6 Outbound Requests: additional sequence Send requests not created

Ticket 22602

 

Problem: When Production Orders attached to an MPO have the statuses reset and then re-released or re-started, additional sequence Outbound Send Requests are not being created.

 

Fix: A check has been added to the Outbound Request logic that ensures additional sequence Outbound Send Requests are created.

 

 


Known Issues and Problems

Issue #1 Retail Hierarchy: Populated Default warehouses in Basic product properties cannot be deleted

Ticket 18645

 

Issue: When default warehouses are added to the Retail Hierarchy Category, the values cannot be deleted.

 

Workaround

  • Do not add default warehouses to the Retail Hierarchy Category.
  • For items assigned to categories in this state, the job for Fix #4/#5 can be run to correct the item’s settings.

 

There is a hotfix for this issue that will be included in the CU12 upgrade.

 

Issue #2 Retail Hierarchy: Populated Default warehouses in Basic product properties does not update Default and Site specific order settings

Ticket 18645

 

Issue: When default warehouses are added to the Retail Hierarchy Category, the default order settings and site specific order settings are not populated and cannot be edited.

 

Workaround

  • Do not add default warehouses to the Retail Hierarchy Category.
  • For items assigned to categories in this state, the job for Fix #4/#5 can be run to correct the item’s settings.

 

This process will be tested as part of the CU12 upgrade project to see if there is a potential fix within the update.  If not, this will be re-visited after.

 

 

 

 

 

  

 

 

Revision History

Version

Date

Summary of Changes

Author

Revision Marks
(Yes/No)

1.0

03/16/2017

Initial draft.

Elise Chapman

No

1.0

03/17/2017

Revision (Enhancement #4).

Greg Matson

No

1.0

3/20/2017

Completed draft

Elise Chapman

No

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Article is closed for comments.