If the checkbox in the Sales and Marketing Parameter, transaction log tab is checked, AX stores the log in smmtranslog table. This table stores the changes across Sales and Marketing and Accounts receivable masters.
Cleaning the log would help in saving a lot of database space.
Sales and Marketing > Setup > Sales and Marketing Parameter > Transaction log
Though there are option available in the parameter to automatically clean the log, user can go to the table and clean the log manually.
2.19.1.1 Result
DRAFT
2.19.1.2 Suggested frequency
DRAFT
3
SUMMARY
Perhaps there are number of clean-ups available in AX 2012, the usage depends on the requirement .Below is the comprehensive list of activities that were used in AX 2009.
Module Clean up Usage in AX 2009
Account
Receivable Clean up Back Order HTH is already using this cleanup in AX 2009 Sale Confirm Journal
Cleanup HTH is already using this cleanup in AX 2009 Delete Empty Sale Order HTH is already using this cleanup in AX 2009 Delete Empty Return
Authorization
HTH is already using this cleanup in AX 2009 General Journal Clean up Ledger Journals HTH is not using this cleanup in AX 2009. Procurement and
Sourcing Purchase update historyclean up HTH is not using this activity as for now. But it issuggested to clean up the history. Delete Request for quotation HTH is not using this functionality and hence not
using this clean-up too. Inventory
Management Summation of Loadadjustment This is a new enhancement in AX 2012. Inventory Journal Settlement HTH is not using this clean up in AX 2009. Inventory Settlement clean
up
HTH is not using this clean up in AX 2009. Inventory Dimension clean
up HTH is not using this clean up in AX 2009. Dimension inconsistency
clean up This is a new enhancement in AX 2012. On hand entries clean up This is a new enhancement in AX 2012. InventsumTTSlog HTH is not using this clean up in AX 2009. Production
Control Clean up registration HTH is not using Production and hence not using thisclean up. Achieve Future Registration HTH is not using Production and hence not using this
clean up.
Production Journal clean up HTH is not using Production and hence not using this clean up.
Production orders clean up HTH is not using Production and hence not using this clean up.
DRAFT
Sales Update History HTH is not using this clean up in AX 2009, but it is suggested to use it.
Call Centre Delete orders This is a new module introduced in AX 2012 R3 and so HTH is not using this AX 2009.
Delete quotation This is a new module introduced in AX 2012 R3 and so HTH is not using this AX 2009.
Delete Return Orders This is a new module introduced in AX 2012 R3 and so HTH is not using this AX 2009.
Sales Update history Clean
up This is a new module introduced in AX 2012 R3 andso HTH is not using this AX 2009. Sales order purge This is a new module introduced in AX 2012 R3 and
so HTH is not using this AX 2009. Sysdatabaselog
table
Batchjob history clean up
HTH is already using this functionality in AX 2009. TIS History HTH is already using this functionality in AX 2009. Alerts HTH is not using this, though it is recommended to
use. Clean up closed
TA HTH is not using this in AX 2009.
DRS cleanup HTH is already using this in Ax 2009. Smmtranslog
DRAFT
4
TEST CASES
Activity Scenario Sample data Expected Results
DRAFT
5
CLIENT ACCEPTANCE
The foregoing clearly states our understanding of our engagement with MicroChannel, and we hereby agree to the project scope, objectives, assumptions, task assignments and deadlines described herein. We understand that changes to the engagement details, as described in this document, will require a formal change order.
We accept our responsibility to ensure that scope; resources and time are kept constant through the life cycle of the project, and our responsibility to ensure that our staff meets all the task deadlines. We understand that our failure to meet these responsibilities could result in an out of scope condition and adjustment of the overall project plan and deliverables, including the possibility of change orders or an entirely new project budget and timeline.
HTH Programme Manager Rebecca Hicks
Agrees that all key areas/personnel were consulted from the relevant departments for this functional area and that requirements are in line with the solution scope.
Date:
HTH Project Manager James Merrill
Agrees that all key areas/personnel were consulted from the relevant departments for this functional area and that requirements are in line with the solution scope.
Date:
HTH Functional Owner
Agrees that all that the identified Gaps are mandatory and aligned to the business strategy.
Date:
HTH Key User
Agrees that all operational requirements for the functional area are stated within the document.
Date:
HTH Business Analyst Matthew Baines
Agrees that all operational requirements for the functional area are stated within the document and that the test cases .
Date:
MCS Programme Manager
Agrees that the document is in adherence of TSF and the solution within the agreed project scope.
Date:
MCS Project Manager Shekhar Diptiman
Agrees that the document is in adherence of TSF and the solution within the agreed project scope.
Date:
MCS Consultant Mansi Kashyap
Agrees that any conflicting requirements are highlighted and
resolved. Date: Exhibit 1: Acceptance