Axapta Dynamics

Wednesday, March 01, 2006

Fusion is it a treat to Axapta?

I had a chance of going through the details of proposed fusion for Oracle Applications and was suprised to see that the fusion architecture is nothing but a marketing hype and is a middle layer architecture. The proposed architecture is based on SOA and the communication between systems is by using WSDL and SOAP protocols. The proposed middleware is only for E-Business applications which means for web based UI which makes it a formidable competietor for our Hub and Spoke model. But we can say that its nothing but the proposed biztalk integration with capabilities to integrate with all the applications easily and please see the fusion architecture below.

# posted by Sri Ram : 3:17 PM 0 comments links to this post

Monday, January 09, 2006

Porting Ax Application between Instances

In usual implementation scenario/update scenario we have to work on a test application and then transfer all the content to the live environment. The following steps are to be followed if an application is to be moved from one Environment to other i.e. Test, Development, Live.

Close down all connections for

Clients
AOS
Business Connector

Copy the following files to the new application folder

.aod
.ald
.ahd
.add

Remove the application object index file (.aoi) from the application folder
Start the new application in 2-tier mode, compile entire application and then synchronize the entire database

# posted by Sri Ram : 7:26 PM 0 comments links to this post

Thursday, January 05, 2006

Security in Axapta

This gives one on how security features are inbuilt in Axapta. Its a block diagram explaining how security features can be configured in Axapta for a manufacturing / production industry

# posted by Sri Ram : 7:17 PM 0 comments links to this post

Tuesday, December 27, 2005

Our Team

# posted by Sri Ram : 9:11 AM 1 comments links to this post

Friday, November 04, 2005

Important Inventory Tables

I just thought of sharing this basic info. As I think this will be of utmost important to those who wanted to know what are the tables that will be affected in the back end for an item created
InventTable
InventtableModule
InventLocation
InventDim
InventSum

ItemID the for the item is stored in InventTable
DimensionID with all the inventory dimensions are stored in the InventDim table. A new dimensionID will be created when there is a change in any of the eight inventrory dimensions.
InventOnhand will be present in the InventSum table. Onhand quantity will be for combination of DimensionId and ItemID.

Hope it gives some basic input on the same.

# posted by Sri Ram : 6:45 PM 0 comments links to this post

Thursday, November 03, 2005

Automatic Number Sequence Attach Code

I find this very great in case if any one wants to attach a number sequence manually created to a particular column in Axapta. We have to write the code in create, write, delete override methods in the table we wanted to have a number sequence to be attached. Here the table is name is Test_Table and the column name for which number sequence to be attached is Test_Num

public void create(boolean _append = false)
{
super(_append);
numberSeq = NumberSeq::newGetNumFromCode("Test_001", true,true);
if (numberSeq)
{
Test_Table.Test_Num = numberSeq.num();
numAllocated = Test_Table.Test_Num;
}
}

public void write()
{
;
ttsbegin;
if (numberSeq && Test_Table.Test_Num == numAllocated)
numberSeq.used();
else
{
if (numberSeq)
numberSeq.abort();
}
super();
ttscommit;
}

public void delete()
{
ttsbegin;
if (!Test_Table.RecId && numberSeq)
numberSeq.abort();
super();
ttscommit;
}