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.
View products that this article applies to.
Description | File name |
Microsoft SQL Server name and instance | ResultReport.xml |
SQL database name | ResultReport.xml |
Microsoft Dynamics AX company name | ResultReport.xml |
Description | File name |
Application hotfixes that are installed on the system | ComputerName_AX_Layer_Hotfix_Info.htm |
Application hotfixes that are installed on the system | ComputerName_SysHotfixManifestVersionInfo.xml |
Description | File name |
Model layer metadata and hotfix information | ComputerName_AX2012ModelMetaDataAndHotFixInfo.htm |
Model layer metadata and hotfix information | ComputerName_AX2012ModelMetaDataAndHotFixInfo.xml |
Description | File name |
Virtualization information output | ComputerName_Virtualization.txt ComputerName_Virtualization.html |
Rule ID | Title | Description | ||
RC_OpenTransfers | Open transfers were detected. Message Type: Informational | |||
RC_ItemTypeSwitchServiceToNonService | Items that were switched from a Service Type item to a Stocked Inventory Type item were detected. Message Type: Informational | Switching from a service to a stocked item can cause reconciliation issues because of the changed posting accounts when you process the two item types. The potential conflicts inventory value report can help in pointing out these reconciliation differences. | ||
RC_WeightedAverage | One or more Weighted Average Summary transactions are tied to the canceled inventory closing voucher. Message Type: Error | |||
RC_ItemTypeSwitch_ItemTOService | Items that were switched from Stocked Type to a Service Type were detected. Message Type: Informational | Items that were switched from stocked to non-stocked can cause reconciliation issues because of the changed posting accounts when you process transactions. Run the Potential Conflicts by inventory and general ledger report to determine whether you are affected by this change. | ||
RC_Unfinished_InventClosings | Check for unfinished InventClosings Message Type: Informational | This is an uncompleted state that can cause problems if you use production and are trying to end a production order. Investigate the Inventory Closing form to complete any unfinished closings. | ||
RC_CheckInventSumDateTrans | InventSumDateTrans Table not cleared. Message Type: Informational | Check the InventSumDateTrans table for any records, because this table should be cleared when the Physical Inventory by Item Dimension report is complete. This is known to cause performance issues. If there are no reports in process, the table can be cleared. | ||
RC_CheckForInvalidSidedMarking | Single-sided record marking in inventtrans was detected. Message Type: Error | When you use inventory marking, it is expected that one issue or receipt transaction is marked to a valid offsetting issue or receipt. By not having this offset, a transaction cannot be adjusted or closed by the inventory-closing process. Contact Support for additional help in investigating the transactions in detail and to determine whether the marking can be removed. | ||
RC_BadQuantities | Invalid quantities were detected on issue type transactions in the Inventtrans table. Message Type: Error | Issue transactions cannot have a quantity that is greater than zero. Such a transaction can cause processing errors and adversely affect on-hand quantities for an item. Contact Support for help in determining whether this data is causing your environment a problem. | ||
RC_ReceiptTransaction | Invalid receipt transaction Message Type: Error | You cannot have a receipt transaction that contains a quantity less than zero. Such a transaction can cause processing errors and adversely affect on-hand quantities for an item. Contact Support for help in determining whether this data is causing your environment a problem. | ||
RC_UnderSettlementsOnClosedTrans | Undersettled quantities were detected on closed issue transactions Message Type: Error | Closed issue transactions with a settled quantity that does not match the actual quantity can affect an item's average cost price. To correct this issue, click Basic, expand Periodic, click Consistency check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_OverSettlementsOnClosedTrans | Receipt transactions with oversettled quantities were detected Message Type: Error | Receipt transaction should not contain a settled quantity that is greater than the actual quantity. To correct this, run a consistency check. To do this, click Basic, expand Periodic, click Consistency check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_OverOrUnderSettled | Closed Inventory transactions were found that do not match the original posted cost. Message Type: Error | The settled cost amount should match the original posted amount plus any adjustments. To correct this, run a consistency check. Click Basic, click Periodic, click Consistency Check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_IncorrectClosingOrRecalcs | Inventory Closings or Recalculations were found that did not post to ledger. This could cause reconciliation issues. Message Type: Informational | If an inventory close or recalculation contains adjustments to entries and was not posted to ledger, it can cause reconciliation issues. On the inventory closing form's general tab there is a Ledger option, and if this option is not marked, the transactions are not posted to ledger. If you are troubleshooting a reconciliation, issue run the inventory potential conflicts report to determine the significance of this closing. | ||
RC_ClosingVouchersMarkedPosted | Closing vouchers that are marked as posted but did not exist in LedgerTrans found. Message Type: Informational | Inventory closings or recalculations were found that were marked to post to ledger but did not. This can cause reconciliation issues. | ||
RC_OpenInventTransWithFullySettledQtys | Open inventory transactions with fully settled quantities were detected. Message Type: Error | If the quantity settled matches the actual transaction quantity, the record should be closed. To correct this issue, click Basic, click Periodic, click Consistency Check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_BadCosts | Issue transaction that has a cost greater than zero. Message Type: Error | You cannot have an issue transaction with a cost greater than zero, because this can affect the average cost price of an item. Contact Support for help in correcting this issue. | ||
RC_BadCostsReceiptTrans | You cannot have a receipt transaction that has a cost less than zero. Message Type: Error | Receipt transactions cannot contain a cost that is less than zero, because this can affect the average cost price of an item. Contact Support for help in correcting this issue. | ||
RC_InvalidInventSumsQty | Inventory On Hand records that did not match the underlying transactions exist. Message Type: Error | The inventory On Hand summary table should match the underlying inventory transaction quantities. If this is out of sync, it can cause posting issues. To correct this issue, click Basic, click Periodic, click Consistency Check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_InvalidIventPostingAccounts | Ledger entries were detected that do not map to a current inventory posting account. Message Type: Informational | Ledger postings that relate to inventory transactions were detected in the last year on an account that is currently not set up in inventory management. This can cause reconciliation differences. Print the Potential Conflicts - Inventory report and the General Ledger report. To do this, click Inventory Management, click Reports, click Status, and then click Inventory Value to help in reconciling this difference. | ||
RC_OldInventTransRecordsNotClosed | Inventory transactions were detected that are open for more than three years. Message Type: Informational | Inventory transactions with a financial date greater than three years ago and still open could indicate that an inventory close has not been run in some time, on-hand stock has a long shelf life, or on-hand stock is in a negative inventory state. If closes are run frequently and stock levels are expected to be closed, we recommend that you review the individual transactions to determine why they are not picked up by an inventory close. If closes were not run, we suggest that you run a close. This will settle these transactions. The benefit from this is the prevention of accidental backdating of transactions and the improvement of reporting and inquiry performance. | ||
RC_BadProductionOrders | Non-financially updated inventory transactions that relate to an ended production order were found Message Type: Error | Inventory transactions that relate to an ended production order should always be financially updated. Contact Support for help in analyzing the data. | ||
RC_InvalidInventSumsCost | Records in the inventory summary table do not match the historical transactions cost or quantity value. Message Type: Error | One or more records in the inventory summary table (InventSum) do not match the summarized quantity and value of the historical transactions for the item. To correct this issue, click Basic, click Periodic, click Consistency Check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. | ||
RC_InvalidInventTrans | Inventory transactions were found that do not relate to an active item in inventory. Message Type: Error | Transactions without an active item in the system would indicate a data inconsistency that could adversely affect reporting or performance because it is an unexpected scenario. Contact Support for help in resolving this issue. | ||
RC_BackDatedTransactions | Back-date production orders were detected. Message Type: Informational | Production orders with a financial date that is earlier than the report as finished can cause temporary reconciliation issues if you use the finished items in a process report and execute the report between the physical and financial dates. | ||
RC_DuplicateInventDimCombinations | Duplicate inventory dimension combinations were found that are known to cause performance issues. Message Type: Error | Check the DimIdx index on the InventDim table to make sure that it is set to unique. Having duplicate inventory dimension combinations is known to cause performance issues in certain environments. | ||
RC_FullySettledNotClosed | Inventory transactions were detected that are open. But the quantity and costs are fully settled. Summary table does not match the historical transactions cost or quantity value. Message Type: Error | Fully settled transactions should be marked as closed in inventory and can cause performance issues when you run inventory-based reports and the inventory-closing process. To correct this issue, click Basic, click Periodic, click Consistency Check, click the Inventory Management module, and then click the Check/Fix option. Expand the Item node, and then click Transactions. |
Keywords: kbmbspartner, kbmbsmigrate, kbsurveynew, kb