Microsoft Dynamics Axapta Technical,Functional Coverage

InventTrans  The InventTrans table contains information about inventory transactions. When order lines such as sales order lines or purchase order lines are created they generate related records in the inventTrans table. These records represent the flow of material that goes in and out of the inventory. InventTable The InventTable table contains information about items. InventSum The InventSum table contains information about the present and expected on-hand stock of items. Expected on-hand is calculated by looking at the present on-hand and adding whatever is on-order (has been purchased but not arrived yet). InventDim The InventDim table contains values for inventory dimensions. VendTable The VendTable table contains vendors for accounts payable. CustTable The CustTable table contains the list of customers for accounts receivable and customer relationship management.

InventTable entity schema tables description of axapta InventTable The InventTable table contains information about items. InventItemGroup  The InventItemGroup table contains information about item groups. InventDimGroup The InventDimGroup table contains information about a dimension group. InventTableModule The InventTableModule table contains information about purchase, sales, and inventory specific settings for items. InventModelGroup The InventModelGroup table contains information about inventory model groups. InventItemSalesSetup  The InventItemSalesSetup table contains default settings for items such as Site and Warehouse. The values are related to sales settings. InventItemPurchSetup  The InventItemPurchSetup table contains default settings for items such as Site and Warehouse. The values are related to purchase settings. InventItemInventSetup The InventItemInventSetup table contains default settings for items such as Site and Warehouse. The values are r

1. Open the delete actions tab under the TestTable. 2. Right-click and select New | Delete Action. 3. Open the Properties window (Alt + Enter). 4. Change the table that it should point to. In our case the RelatedlTable. 5. Decide which action should take place when a record in the TestTable is deleted..

Macros in axapta Macros are constants, or pieces of code, that are being taken care of by the compiler before the rest of the code to replace the code where the macro is used with the content of the macro. There are three different types of macros: stand alone macros, local macros, and macro libraries. Macros are typically constant values that are only changed by developers. They are used so that developers don't have to hardcode these kind of values in the X++ code, but rather refer to the macro. The macro libraries can be found in the AOT under Macros. Each of them can contain multiple macros that can be used throughout the rest of AX. To use the macros from a macro library in AX, simply include them in the scope that you would like to use them. The next example shows how to use two different macros from the same macro library in a Job. First we create a macro library that consists of two macros: #define.Text('This is a test of macros') #define.Number(200)

Inheritance in axapta One of the central concepts of object-oriented programming is the possibility to inherit functionality defined at a higher level in the system. This can be done by having a class hierarchy where a method in a subclass overrides a method in the super class (higher level). The method in the subclass can still use the functionality in the same method in the super class by using the super function as in this example: public void sellCar() { ; super(); } This method implies that the class that the method belongs to, extends another class where the functionality in the method sellCar is already written or that the sellCar method is defined at a higher level in the class hierarchy in which this class belong. In our example, we have a super class called Car that extends Object, and then we have we have Car_Economy, Car_Compact, Car_MidSize and Car_Luxury who all extend the class Car. Also, they override the toString method for all of these classes as shown in

Static methods in Axapta In AX, you will see that some methods have a method modifier named static. Actually, all the Jobs we have looked at so far have been using the static modifier. This means that the method can be called directly without creating an object. This also off course means that the static classes can't access the protected data defined in the classDeclaration of the class. The modifier is used at the beginning of the method definition right after the method access modifier and before the return value as in the next example: public static void main(Args args) { } To call a static method you use double colon instead of period as you do in object methods: SomeClass::staticMethod()

The code in AX can run on either the client or the server. The server here will be the Application Object Server (AOS). There are two ways of controlling where objects of a certain class should execute. When developing static methods you can select to use the client or server modifier in the method header like in the example: // This method will execute on the client. static client void clientMethod() { } // This method will execute on the server. static server void serverMethod() { } You can also set the RunOn property on a certain class to make all objects of that class run on either the client or the server. You can also set the RunOn property on the class to CalledFrom. This will make objects of that class execute on the same layer as the method that created the object.