Sep 11, 2009

DynamicsZone: DataLoad software also works with AX

DataLoad V4 - Classic & Professional

"If you have hundreds of records, then DataLoad Classic is a good way of loading the records that you need; if you have thousands of records then DataLoad Professional is the tool to use. Good thing is that this tool is made by oracle and Flexibiulity of AX being windows platform is such that this tool works on it as well.
And it’s FREE Implementing or supporting any application requires significant effort to configure and load master and transaction data, for example from legacy systems, an expensive and time-consuming activity.
DataLoad reduces the time and costs associated with data migration. Its easy-to-use interface means that it can be used by non-technical employees, giving end-users an active role in the implementation and support of any system. With 8,000 downloads a month and customers in over 30 countries, DataLoad is the world's most popular data entry tool for end users, consultants and developers.
Why Use DataLoad?
· Non-technical users can easily configure and load data into any system
· Recommended by Oracle, DataLoad contains specific additional features to load large volumes of data in Oracle E-Business Suite
· DataLoad is sponsored by leading UK systems integrator Edenbrook, which has committed to support and improve the tool
· DataLoad is available in Classic and Professional editions, catering to all types of application implementation from the simple to the vastly complex
· DataLoad Classic is available to download free of charge and is not a time limited trial version
· DataLoad has a proven track record with over 10 years of production use and is still actively developed to meet today's needs
DataLoad Functionality
A summary of DataLoad functionality is provided below,
DataLoad provides a spreadsheet style interface and the data contained within that spreadsheet can be loaded into any system using a Macro load, or into Oracle Applications using Forms Playback. Either way, data or setup is loaded through the application's forms and that provides many advantages. Users have a choice between the free DataLoad Classic or more feature rich DataLoad Professional,
Macro Loads
All versions of DataLoad provide the Macro load functionality and this is the load technology of choice in DataLoad Classic, the freeware version.
The easiest way to load data into a form is using a keyboard and mouse and this is what DataLoad does with Macro loads. You configure the data, keystrokes and mouse clicks in DataLoad that you want loaded into your form(s). When you run the load DataLoad presses the keys and clicks the mouse as you specified. Any keys on your keyboard can be used by DataLoad, in any combination, and the left and right mouse buttons can also be used. And because DataLoad calls the same low-level Windows code that is called when you actually press a key or use your mouse, the application you are loading data into cannot tell the difference between data entered by you at the keyboard or DataLoad.
To build a DataLoad load write down what keys and mouse clicks you use to enter one record in your application. Now enter that into a DataLoad row and copy the instructions down into as many rows as the number of records you are going to load. Finally, paste your data into cells in DataLoad that correspond to the fields in your form. Your load is now built!
To load data as quickly as possible DataLoad uses Windows copy & paste to copy data into form fields. Where the actual keystrokes should be sent instead the data just needs to be preceded with a backslash, '\'. To send mouse clicks use the *ML or *MR commands to send left or right mouse click respectively. Please read the User Guide for more information about keystrokes, DataLoad commands and mouse clicks.
Controlling the Load
DataLoad can send data, key strokes and mouse clicks far faster than applications can handle them. To slow down DataLoad there is a comprehensive set of Delay options, using both the Delays form and the *SL (Sleep) command which cause DataLoad to wait at key points.
For the fastest, most reliable copy & paste loads use the Load Control functionality in DataLoad Professional. Load Control enables DataLoad to monitor a log file written by the application you are loading data into. Having configured DataLoad to use the log file your load will not run faster than the application is processing the data. No delays are required and DataLoad will run as fast as possible without overloading the target application. Another great benefit of Load Control is that if an error occurs in the application DataLoad will stop sending data. Therefore loads can be run unsupervised.
To download visit http://www.dataload.net

Posted by Ali Jawad     at 4:09 AM

DynamicsZone: DataLoad software also works with AX

Sep 9, 2009

ERP & Management E-Books - Home

PMP, ITIL and Dynamics AX , CRM & GP (Oracle & SAP 2 Come Soon)

This site is dedicated for all what you need to learn ITIL, SAP, Oracle MS Dynamics AX, CRM, GP and PMP which includes, xls, pdf, doc files, simulators, article and other helping tools.
All download links are from rapidshare.
If you want any tool, books or article related to PMP and AXAPTA not listed here, just write to http://ax-pmp.weebly.com/
we will try to upload on priority basis.
Good Luck
Last Updated: Sep 07, 09 Reason: Material Added in Dynamics AX BI, WM and others

ERP & Management E-Books - Home

Sep 8, 2009

Changes in Sales and Transfer Order Picking from Microsoft Dynamics AX 4.0 to Dynamics AX 2009

Overview
The purpose of this post is to present the major changes and new functionality that was introduced for sales and transfer order picking in AX 2009.
The aim and the idea behind these changes is to move towards a single system for picking that can be shared in order to simplify and unify future extensions.
The post contains information about:
· User Interface changes
· Changes to tables and classes
· Upgrade scripts
· New functionality for order picking
· New enhancements for advanced WMS outbound processes
Differences in terminology
Picking registration, as known in AX 4.0, is referred to as order picking. Picking with output orders and advanced WMS, as applied in AX 2009, is referred to as consolidated picking.
Differences from a UI perspective
The parameter Set inventory transactions to picked in AX 4.0 is now obsolete, and it has been replaced by the Picking route status parameter.





The following conversion rules apply:
Dynamics AX 4.0

Set inventory transactions to picked = selected
Set inventory transactions to picked = not selected

Dynamics AX 2009

Picking route status = Complete
Picking route status = Active

When you post a picking list, and the picking route status is Active, the reference for inventory transactions is set to Output order instead of Invent-picking list registration:








When you click Posting/Picking list registration from a sales order or a transfer order, a new registration form opens:



The Picking list registration form is used to register what was picked and it is quite similar to the picking registration form in AX 4.0. You can either update the entire picking route or update individual lines, and you can view and pick both consolidated lines and order picking lines in this form.
Additional functionality available from this form:

· Barcode identification
· Split of picking lines
· Unpick of picking lines with the option to put items on another location
· Cancellation of picking lines
A new inventory parameter, End output inventory order, is introduced:







The End output inventory order parameter controls whether or not the reference between an output order and inventory transactions is removed when you delete or decrease the quantity of a picking registration line.
If the End output inventory order parameter is selected, the behavior is similar to the behavior in AX 4.0, and that is to say that after posting, the inventory transactions do not reference an output order.
It the End output inventory order parameter is not selected, the reference between the output order and inventory transactions is not removed and a new picking route can be created from the Open output orders form.
When the picking list is posted, the status of the picking lines and the inventory transactions changes.
In AX 2009, there are no separate tables to store picking list journal and picking list registration data.
Differences from a code perspective
In AX 2009, picking is handled using the WMS module and several classes and tables prefixed with WMS are used. This means that several tables are controlled by the LogisticsAdvanced configuration key rather than by the WMSAdvanced configuration key as in AX 4.0.
The figure below shows how the tables in AX 4.0 map to the tables used in AX 2009:


Sep 6, 2009

Microsoft Dynamics Sure Step

Success Factors in ERP Implementation

Executive Commitment

Please see this video;

http://www.microsoft.com/dynamics/support/implementation/success.aspx

Sep 4, 2009

Dynamics Ax - Task Recorder

This is a free add-on for Ax that allows you to record whatever you're doing in Ax (forms that open, user input and screenshots) and automatically create documentation for you.
Its a LOT easier than taking hundreds of screenshots and cutting/pasting them into a word documentIt's by no means perfect though, and there is still a fair amount of editing required before the document that it spews out is presentable enough to be of any use to an end-user, but it does make life easierYou can download it from here (requires partnersource login)There's a brief but succinct description here at the axaptapedia too

Sep 1, 2009

Posting Accounts in Dynamics AX2009

About sales order posting
Use the Inventory posting form to control the following sales order posting accounts:
· Packing slip
· Packing slip offset
· Issue
· Consumption
· Revenue
· Discount
· Commission
· Commission offset
· Packing slip revenue
· Packing slip revenue - offset
· Packing slip tax
When you create an order line (On order status), an inventory transaction is generated with the quantity specified, but without any financial value.
When you update the packing slip for the item (Deducted status), transactions based on the items cost at the time the packing slip is updated are generated in the packing slip account, and the packing slip offset account, in connection with the packing slip update.
In order for the posting to occur, you must select two setup check boxes:
1. Post physical inventory (Inventory management > Setup > Inventory > Inventory model groups > Setup tab).
2. Post packing slip in ledger (Accounts receivable > Setup > Parameters > Updates tab).
When you invoice-update (Sold status) the item, the two packing slip transactions are reversed. The items cost is credited to the account for inventory issues, and the account for item consumption is debited.
The item sale, excluding any taxes, such as sales tax, is credited to the revenue account. Tax is credits to the tax codes account. The sale, including any taxes such as sales tax, is debited from the customer summary account as set up in the customer's posting profile.
· For Discount, the sales order is posted before the line discount is deducted, and the line discount is debited in the account for discounts. If no account is specified for discounts, the revenue is posted after the line discount is deducted, and the latter is not recorded directly in a ledger account.
· For Commission, a commission account, and a commission offset account are created. These accounts provide an overview of the ledger-posting of commissions. When you invoice-update a sales order, the commission on the posted amount is debited from the commission account and credited to the commission offset account.

About purchase order posting
By using the Inventory posting form, you can control the following purchase order posting accounts:
· Packing slip
· Packing slip offset
· Receipt
· Consumption
· Discount
· Fixed receipt price profit
· Fixed receipt price loss
· Fixed receipt price offset
· Charge
· Stock variation
· Packing slip purchase
· Packing slip purchase offset
· Packing slip tax
· Fixed asset receipt
When you create a purchase line (Ordered status), an inventory transaction is generated with the quantity specified, but without any financial value.
When the item is received (Received status), transactions based on the items' cost as recorded in the purchase line are generated in the packing slip account, and the same transactions are reflected in the packing slip offset account for the packing slip update.
For the posting to occur, you must select two setup check boxes:
1. Post physical inventory (Inventory management > Setup, Inventory > Inventory model groups > Setup tab).
2. Post packing slip in ledger (Accounts receivable > Setup > Parameters > Updates tab).
When you update the invoice for the item (Purchased status), the two packing slip transactions are reversed. For an item not using standard cost, the item's true cost is debited from the inventory receipt account. Any tax is debited in the tax code account, and item purchases, including tax, are credited to the vendor summary account according to the setup in the supplier's posting profile.
For items with a standard cost, transactions are made based on the standard cost specified in the Price field on the Price/Discount tab on the Inventory table. The difference between the real cost and the standard cost is posted in the standard accounts for gains and losses.
If an account for discounts is indicated, the purchase posts before the line discount is deducted, and the line discount will be credited in the separate account for discounts. If you do not specify an account for the line discount, the inventory receipt is posted after the line discount is deducted, and the latter is not recorded directly in a ledger account.
To specify that a purchase is for the internal use of a fixed asset, use the Fixed asset receipt option.


About inventory posting
Microsoft Dynamics AX provides control over the following inventory posting accounts:
· Fixed receipt price profit
· Fixed receipt price loss
· Issue
· Loss
· Receipt
· Profit
· Fixed asset issue
You can generate transactions for inventory profits and losses when you record transactions in the inventory, for example, in a profit/loss journal. For inventory profits, the receipts account is debited, and the account for inventory gains is credited. For inventory losses, the issues account is credited and the account for inventory gains is debited.


About production posting
Production posting activities follow the production process.
· As items are consumed during production they are recorded in the production order. This process generates issue transactions to make up for the missing raw materials.
· As the materials are consumed, they are posted to both the Picking list issue account and the Picking list offset account.
When the production is reported as finished, a receipt transaction is posted to the finished item. The cost calculated for the finished item is then posted to both the Report as finished receipt account and the Reported as finished offset account.
Finally, when production is complete, all accounts are updated with the final calculations. The raw materials that were actually consumed are credited to the account tracking inventory issues and debited from the account tracking item consumption. The overall cost of the finished item is debited from the inventory Receipt account and credited to the inventory Issues account.
Summation of accounts the transactions are posted to during production
· Picking list issue
· Picking list offset account
· Report as finished receipt
· Reported as finished offset account
· Issue
· Issue offset account
· Receipt
· Receipt offset account

Aug 24, 2009

Aug 20, 2009

7 Key Benefits of Microsoft Dynamics Ax 2009

1-- Increased flexibility. Microsoft Dynamics AX 2009 will give business the ability to make changes to core procedures plus perform other adjustments on the fly, helping business to be more agile and opportunistic in the fast moving economic climate.

2-- Integration with existing IT investments. Microsoft Dynamics AX 2009 built on Microsoft windows architecture enhances interoperability with Microsoft products, including Microsoft Office and Project Server 2007.

3-- Major new components of Dynamics AX 2009 include a centralized "compliance centre" that Microsoft has characterized as a "one-stop shop" for compliance-related information, and "self-service" BI (business intelligence), which enables users to access KPIs (key performance indicators) directly from the client.

4-- Simplified IT management. Microsoft Dynamics AX 2009 gives IT staff easy-to-administer system, thus reducing management overheads.

5-- Enhanced forward planning. Microsoft Dynamics AX 2009's budgeting and financial forecasting tools will automate tasks your staffs have had to perform manually, improving your staff’s ability to plan for the future based on robust, sound data analysis.

6-- Improved order processing. Microsoft Dynamics AX 2009 will enable your sales staff to put through orders in a more timely fashion from out in the field, accelerating order fulfillment and improving customer satisfaction.

7-- Streamlined processes through integrated technology. Integrated e-commerce capabilities within Microsoft Dynamics AX 2009 will eliminate the manual and duplicative data entry if it existed.

Aug 19, 2009

Basic steps to up gradation from AX 4.0 to AX 2009(Test Environment)

1. Create an Empty Database (Test_AX2009)
2. Restore AX 4.0 Backup in “Test_AX2009”
3. Copy all Existing AX 4.0 Layers to any other folder. These can be copied from (C:\Program Files\Microsoft Dynamics\40\Applications\App\Standard)
4. Install AX 2009 application (Installation is simple)
a. Database (Select Existing Database and point to “Test_AX2009”)
b. AOS (Do not run AOS Service)
c. Client
5. Delete SysSetupLog Table Entries – (This is main Problem I was facing – which does not let AOS to start in coming steps)
6. Copy back the Application Layer Files to AX 2009 Application Directory (C:\Program Files\Microsoft Dynamics\50\Applications\App\{Instance Name})
7. Delete Index file from C:\Program Files\Microsoft Dynamics\50\Applications\App\{Instance Name}\axapd.aoi)
8. Execute the Attached Script file in the SQL Studio
9. Start AOS Service
10. Run Client
11. Upgrade Check list will open.
12. Go through by all simple checklist.
13. Take Back up DB “Test_AX2009” after Executing Pre-Synchronize Step in CheckList.
14. If you DB has some errors, you will face them in Post-Synchronize Step. Like I faced the following:

Unit Conversion Does not Exist
Record already exist in EPWEBSITE Table
To resolve the errors, you can access Tables through AOT and add missing records.
You have to remove all errors, otherwise Post-Synchronize step will not complete.


15. Pre Synchronize, Synchronize and Post- Synchronize is for entire database, not only for your company. If any error in Contoso Company, you have to remove them as well. Even I got 3 errors in DAT Company.
16. Finish with Checklist
17. Restart Client.