Microsoft Dynamics AX 2009 System architecture

The following post has been copied from - http://technet.microsoft.com/en-us/library/dd362112(AX.50).aspx

Microsoft Dynamics AX 2009 - Sytem architecture

Understanding the internal architecture of Microsoft Dynamics AX can help you make decisions when planning, customizing, and deploying a system. This topic provides a high-level overview of the system architecture of Microsoft Dynamics AX.

The diagram below provides a high-level overview of Microsoft Dynamics AX system architecture. This diagram does not depict the system topology or physical infrastructure required for the deployment.

Your infrastructure can consist of many Microsoft Dynamics AX components on a single physical server or on multiple physical servers. For considerations in planning your deployment infrastructure, see Planning system topology.

For details on Microsoft Dynamics AX components, see Component architecture. For up-to-date hardware and software requirements for Microsoft Dynamics AX, see the system requirements Web page.

Create Axapta Payment Journal

The following code creates a payment journal in AX.

public void PaymentJournalLineCreation()

{

    boolean                     ret;

    CustTable                   custTable;

    LedgerJournalName           LedgerJournalName;

    LedgerJournalTable          ledgerJournalTable;

    LedgerJournalTrans          ledgerJournalTrans;

    LedgerJournalCheckPost      ledgerJournalCheckPost;

    NumberSeq numberseq;

    ;

    //Get customer account

    this.getCustomerAccount();

    //Get currency

    this.setCurrency();

    //Set JournalNameId

    this.setJournalNameId(LedgerJournalACType::Bank);

    //Get table buffer

    custTable = CustTable::find(customerAccount, false);

    // Find a ledgerJournalName record

    select firstonly LedgerJournalName

    where LedgerJournalName.JournalName == journalNameId;

    //Get next available voucher number

    numberseq = NumberSeq::newGetVoucherFromCode(LedgerJournalName.VoucherSeries);

    ledgerJournalTrans.Voucher = numberseq.voucher();

    //Generate the transaction line

    ledgerJournalTrans.JournalNum = ledgerJournalId;

    ledgerJournalTrans.CurrencyCode = currencyCode;

    ledgerJournalTrans.ExchRate = Currency::exchRate(ledgerJournalTrans.CurrencyCode);

    ledgerJournalTrans.AccountNum = customerAccount;

    ledgerJournalTrans.accountName();

    ledgerJournalTrans.AccountType = LedgerJournalACType::Cust;

    ledgerJournalTrans.Dimension[1] = custTable.Dimension[1];

    LedgerJournalTrans.KUMTeamDescription();

    ledgerJournalTrans.Dimension[2] = custTable.Dimension[2];

    ledgerJournalTrans.KUMDetailDescription();

    ledgerJournalTrans.Dimension[3] = custTable.Dimension[3];

    ledgerJournalTrans.KUMEventDescription();

    ledgerJournalTrans.AmountCurCredit = paymentAmount;

    ledgerJournalTrans.TransDate = PaymentDate;

    ledgerJournalTrans.Txt = '@COL1576'; //Payment, Thank you

    ledgerJournalTrans.PaymMode = custTable.PaymMode;

    ledgerJournalTrans.PostingProfile = 'DFLT';

    ledgerJournalTrans.BankTransType = 'Chck-rcpt';

    ledgerJournalTrans.Payment = custTable.PaymTermId;

    ledgerJournalTrans.CustVendBankAccountId = this.GetCustomerBankAccountID(customerAccount);

    ledgerJournalTrans.SettleVoucher = SettlementType::OpenTransact;

    ledgerJournalTrans.TransactionType = LedgerTransType::Payment;

    ledgerJournalTrans.Approved = NoYes::Yes;

    ledgerJournalTrans.ApprovedBy = curUserId();

    ledgerJournalTrans.Due = systemdateget();

    ledgerJournalTrans.TaxGroup = 'DFLT';

    ledgerJournalTrans.OffsetAccount = bankAccount;

    ledgerJournalTrans.OffsetAccountType = LedgerJournalACType::Bank;

    ledgerJournalTrans.offsetAccountName();

    ledgerJournalTrans.PaymentStatus = CustVendPaymStatus::None;

    ledgerJournalTrans.insert();

}

There are some methods calls in the previous code. These are the following:

//Find customer account based on Customer Reference Number

public CustAccount getCustomerAccount()

{

    CustAccount     custAccount;

    CustBankAccount custBankAccount;

    int             countRecords = 0;

    ;

    switch (JournalFormatType)

    {

        case KMN_CustPaymentJournalFormatType::Mexico:

            select * from custBankAccount where custBankAccount.MsgToBank == customerReference;

            custAccount = custBankAccount.CustAccount;

            this.parmCustAccount(custAccount);

            break;

    }

    return custAccount;

}

//Sets the currency value to the property

public void setCurrency()

{

    ;

    //Set property

    this.parmCurrencyCode(CompanyInfo::standardCurrency());

}

public void setJournalNameId(LedgerJournalACType _journalType)

{

    LedgerJournalNameId _journalNameId;

    ;

    switch(_journalType)

    {

        case LedgerJournalACType::Bank:

            _journalNameId = 'CR';

            break;

    }

    this.parmLedgerJournalNameId(_journalNameId);

}

NOTE: I'm using accessory methods for most of the variables in this code (this is a class), so remember to declare them in the classDeclaration and create your own properties.

Get Employee email with X++ - Microsoft Dynamics AX

The new way Microsoft Dynamics AX handles employee records is very different from the prior versions. For example, in AX 3.0 or 4.0 the employee table will have an email for a specific record, so you could just do something like this to retrieve an employee email:

EmplTable::find(emplId).email;

I needed to get the Employee ID for a custom functionality that sends a sales status confirmation email to a contact with copy to the employee that is handling that Sales Order.

In Microsot Dynamics AX 2009, however, the employee's information is handled diferently. For example, the Employee contact information is stored in a table called DirECommunicationAddress, and the Employee's address is stored in the Address table.