Dynamics AX 2009 Demo Data

The Demo Data set for Microsoft Dynamics® AX 2009 is no longer based on the Global Trade and Manufacturing Company. Based on market feedback we have created a new Contoso Entertainment systems group of companies. It comes with 2 fiscal years of transactional data that enable us to demo our stronger Business Intelligence story and Role Center pages, while allowing us to easily expand the demo data story in future releases as we expand Microsoft Dynamics® AX’s functionality footprint.

Contoso Entertainment Systems (CES) is a home electronics manufacturing, distribution and retail company that includes a Professional Services department. Its headquarters are in the USA with a key distribution subsidiary based in Germany and it works with the relevant currencies. CES distributes televisions, projectors, Digital Video Recorders and Players, and audio receivers. It manufactures speakers and assembles home theatre systems. CES’s customers are primarily based in North America and Europe and include Major Accounts (such as hotel chains), Wholesalers (of differing sizes), Retail stores (that are self-owned and operated), as well an internet storefront.

The legal and physical structure of CES is setup as follows:

• CEC – Contoso Entertainment Consolidation, based in USA
  

  CEU – Contoso Entertainment USA, Headquarters based in USA Site 1: Production of all speakers Site 2: Assembly of home theatre systems and Services Site 3: Production of Standard speakers CEE – Contoso Entertainment Europe, Distribution subsidiary company based in Germany Site 4: Distribution, Assembly and Service of all products

• CVC – Virtual company that includes table collections from CEU and CEE.

The Contoso Entertainment Systems Demo Data for Microsoft Dynamics® AX 2009 documentation with more information is under development and will be posted on this page soon.

The downloads for Contoso Entertainment Systems demo data offers transactional data for Basic, Administration, General Ledger, Bank, Fixed Assets, Accounts Payable, Accounts and Receivable, Inventory Management, Intercompany, Production, Master Planning, CRM, Project, Expense Management, and Human Resources modules, and is intended to demonstrate these modules’ functionality. It also offers base data (i.e. no transactions) for the Product Builder modules.

[Download here] – need login to Partner Source

AX: Create Journal Movement via x++

/*
Code below is x++ code for Create Journal Movement via x++,
change “[XXXXXXXX]” to your value.
*/

Boolean CreateJournalMovement()
{

InventJournalTable journalTable;
InventJournalTrans journalTrans;
JournalTableData journalTableData;

InventJournalId journalId;
InventJournalName journalName;

AX: Posting Sales Order via x++

/*
Code below is x++ code for Posting Sales Order via x++,
change “[SALES ID]” to your Sales Id.
change DocumentStatus for posting Confirmation or Picking List or Packing Slip or Invoice
change SalesUpdate for Spec Quantity, ex: DeliverNow
*/
SalesFormLetter SalesFormLetter = SalesFormLetter::construct(DocumentStatus::PackingSlip,true);
SalesTable salesTable;
;
salesTable= SalesTable::Find(“[SALES ID]“);

SalesFormLetter.update(salesTable, systemDateGet(), SalesUpdate::DeliverNow, AccountOrder::None, false, false);

AX: Posting Production Journal BOM via x++

/*
Code below is x++ code for Posting Production Journal BOM via x++,
of course you must change “[JOURNAL ID]” to your Journal Id.
second parameter, “true” for “show info result”, “false” for “hide info resut”
*/
ProdJournalCheckPostBOM prodJournalCheckPostBOM;
;
ttsbegin;
prodJournalCheckPostBOM  = ProdJournalCheckPostBOM::newPostJournal(“[JOURNAL ID]“,true);
prodJournalCheckPostBOM.run();
ttscommit;

Upgrade from AX 4.0 to AX 2009

The steps below provide a high-level overview of the tasks that you must complete to upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009.

1. Back up your existing database and application files.
2. (Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 4.0. For example, clean up the SysDatabaseLog table.
3. (Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.
4. (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.
5. Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
6. Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select your existing Microsoft Dynamics AX database.
7. Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.
8. Complete the steps in the Upgrade checklist to finish upgrading.

Upgrade from AX 3.0 to AX 2009

This topic lists the high-level steps involved in upgrading from Microsoft Dynamics AX 3.0 to Microsoft Dynamics AX 2009.

1. Back up your existing database and application files.
2. Import two .xpo files from the installation media to assist with data upgrade.
   • UpgradeColumnList.xpo, for 32-bit to 64-bit RecId field conversion.
   • LeftJustified.xpo, for removing any trailing spaces from fields.
     • Note: To help improve performance, you can apply the LeftJustified.xpo on the database that you create in step 4 after you’ve used the Microsoft Dynamics AX DB Upgrade Preparation tool but before you start the Microsoft Dynamics AX 2009 AOS. See step 8.
3. (Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 3.0. For example, clean up the SysDatabaseLog table.
4. Create an empty database for Microsoft Dynamics AX 2009 in SQL Server 2005.
5. (Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.
6. (Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.
7. Run AXDBUpgrade.exe (The Microsoft Dynamics AX DB Upgrade Preparation tool). Note: To help improve performance, you can run this tool in Multithreaded mode. For example, to run this tool in 10 threads, enter AxDbUpgrade.exe P/10 at a command prompt.
8. (Optional) Apply the LeftJustify file imported in step 2 to the Microsoft Dynamics AX 2009 database created in step 4.
9. Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
10. Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select the database that you created in step 4.
11. Copy your upgraded customized file into the correct application directory.
12. Start the AOS.
13. Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.
14. Complete the steps in the Upgrade checklist to finish upgrading.

Horee berhasil..install ax 2009 on Windows XP SP3 without domain.

“…bangun pagi ku terus install…”

Alhamdulillah, akhirnya bisa juga juga install ax 2009 di windows xp sp3 dengan lepas domain.

Setelah 10 jam lamanya download Installation DVD nya yang sebesar 1,7Gb.

Interfacing ERP Application to 3rd Party to ERP Application

Setiap aplikasi memiliki karakteristik sendiri-sendiri, ada aplikasi ERP yang mengatasnamakan “build in” application, “customable” application ataupun benar-benar tailor made application.

Pada dasarnya aplikasi build in, memaksa suatu company untuk mengikuti business process yang sudah ada secara standard di aplikasi tersebut, dengan sedikit sentuhan customisasi.

Ada juga aplikasi customable, contoh dynamics AX, yang bisa dicustom dalam skala besar, bahkan kita bisa buat modul baru dan berinteraksi dengan modul standard. bahkan business process standardpun bisa di “belok”-kan menjadi

Dynamics AX: Looping tablename_ds

ReqTrans rt;
;
rt = ReqTrans_ds.getFirst();
while (rt)
{
rt = ReqTrans_ds.getNext();
}

AX so tau, Invoice dari Packing Slip dan Serial yang ngaco.

SO Invoice dari Packing Slip tertentu dan serial no tertentu.

Yah benar itulah yang terjadi, memang kadang aplikasi yang sudah jadi kadang tidak sesuai dengan keinginan suatu company.

Kenyataannya adalah dimana kita buat SO kemudian di reserve dan di keluarkan dengan 2 kali packing slip misal:

Packing 1 Item A serial C qty 5 KG

Packing 2 Item A serial D qty 5 KG

Nah pada saat invoice qty 8, yang terjadi adalah AX akan mengambil qty 5 dari packing 1 dan qty 3 dari Packing 2, padahal yang diinginkan user adalah 4 dari packing 1 dan 4 dari packing 2, untuk itu saya coba buatkan untuk solusi tersebut.

Bisa dilihat codenya di