CLASSES AND TABLES WHILE CREATING SALESORDER

CLASSES , TABLES ,FORMS AND METHODS WHILE CREATING SALES ORDER AX X++

CLASSES AND TABLES WHILE CREATING SALES 

ORDER 

Below are the list of tables and classes being executed in a sales order cycle.
Similar is the case for purchase order

Sales Order (Confirmation, Picking list, Packing slip, Invoice )

Creating Sales Order
-------------------------

Classes :- SalesTableType and SaleslineType classes  will get called while creating the orders.
Tables  :- Sales Table, Logistics Postal Address, CustTable, MCRPrimaryAddressCust,SalesLine.

Confirmation
--------------------
Classes :- SalesFormLetter class

Tables  :- SalesParmTable, SalesParmLine Table
CustConfirmJour Table, CustConfirmTrans Table- when a sales order gets confirmed.


SalesFormLetter classes will be used to post the sales order at various document status like picking,packing, invoice etc.

Picking List
---------------
Classes :- SalesFormLetter_PickingList class

 Tables :- SalesTable, SalesParm Tables

Packing List
---------------
Classes :-SalesFormLetter_PackingSlip class

Tables  :-SalesTable, Salesparm Tables

CustPackingSlipJour, CustPackingSlipTrans  when a packing slip is posted.

Invoice
---------
Classes :- SalesFormLetter_Invoice class

CustInvoiceTable, CustInvoiceTrans when invoice is posted.

SalesOrder Classes and Tables:

SalesTableType and SaleslineType classes will get called while creating the SalesOrders.
SalesFormLetter_Confirm
SalesFormLetter_Invoice
SalesFormLetter_PackingSlip
SalesFormLetter_PickingLlst
classes will be used to post the sales order at various document status (packing, invoice etc).
Tables:
SalesTable contains all SalesOrder headers regardless whether they have been posted or not.
The SalesParmTable and SalesParmLine contains detailed information regarding posting sales headers and Lines.
CustConfirmJour and CustConfirmTrans tables contains all Sales Confirmation headers and Lines posted in Dynamic Ax originating from Sales Orders and Lines.
CustPackingSlipJour and CustPackingSlipTrans tables contains all sales PackingSlip headers and Lines posted in Dynamic Ax originating from Sales Orders and Lines.
CustInvoiceJour and CustInvoiceTrans tables contains all sales all Sales Invoice headers and Lines posted in Dynamic Ax originating from Sales Orders and Lines.

Purchase Order classes and Tables:

PurchTableType and PurchTableLine classes will get called while creating the PurchaseOrders.
PurchFormLetter_PurchOrder
PurchFormLetter_ApproveJournal
PurchFormLetter_Invoice
PurchFormLetter_PackingSlip
PurchFormLetter_ReceiptsList
classes will be used to post the PurchaseOrder at various document status (packing, invoice etc).
Tables:
PurchTable contains all purchase order headers regardless whether they have been posted or not.
PurchParmTable and PurchParmLine contains detailed information regarding posting Purchase headers and Lines.
VendPackingSlipJour and VendPackingSlipTrans tables contains posted packingslip headers and lines.
VendInvoiceJour and VendInvoiceTrans tables contains all invoiced purchase order headers and Lines.
VendReceiptsJour and VendReceiptsTrans tables contains posted receipt header and lines.
VendPurchOrderJour and VendPurchOrderTrans tables contains Purchase requisition headers and lines.

Classes, Tables, Forms and Methods used to post the sales orders 


SalesTableType and SaleslineType classes will get called while creating the orders.
SalesFormLetter* classes will be used to post the sales order at various document status(packing, invoice etc).
SalesParm* tables are used to prepare the data for posting
CustConfirmJour, CustConfirmTrans - when a sales order gets confirmed
CustPackingSlipJour, CustPackingSlipTrans - when a packing slip is posted.
CustInvoiceTable,CustInvoiceTrans - when an invoice is posted.
Posted by at  

Comments

Post a Comment

Popular posts from this blog

We will follow the following steps in the AX development.

We will follow the following steps in the AX development. 1. Follow the naming convention: - All new objects will start with a prefix ‘INC_ModuleNameofObject’ - Adding a new field to an existing table should be prefixed with ‘INC_ModuleNameofObject’ - Created Extended Data Types for any new fields you create. - Follow the rest of the standard processes for methods, relations, indexes, delete actions. 2. Label file: - Create a new label file or use an existing for your customization. - Label file will have the 1st 3 digits of the Customer Name (Functional consultant can help         to identify the names.) 3. Please maintain a XPO for the customization, we will use it for the deployment.         Please maintain a backup and forward it to me end of the day. 4. The customization will be done on the test environment. It will be tested by the functional consultant         and then by the end user. ...
Read more

Need to provide “ItemId lookup” based on "ItemType" field, which selected while creating SalesOrder

In SalesTable form – Need to provide “ItemId lookup” based on "ItemType" field,  which selected while creating SalesOrder In SalesTable Form -> Datasource -> Salesines -> Fields -> ItemID -> Lookup( )     SysTableLookup          sysTableLookup = SysTableLookup::newParameters(tableNum(InventTable),_formControl);     Query                   query = new Query();     QueryBuildDataSource    queryBuildDataSource = query.addDataSource(tableNum(InventTable));         queryBuildDataSource.addRange(fieldNum(InventTable, ItemType)).value(queryValue(salesTable.ItemType));     sysTableLookup.addLookupfield(fieldNum(InventTable,ItemId));     sysTableLookup.addLookupMethod(tableMethodStr(InventTable,defaultProductName));     sysTableLookup.addLookupMethod(tableMethodStr(InventTable,itemGroupId));   ...
Read more

How to retrieve multiple selected records from Grid using X++

Image
How to retrieve multiple selected records from Grid using X++: In this post, we discuss how we can retrieve all selected(marked) records of a datasource or retrieve marked records form Grid. For this purpose follow the steps listed below. Create a new table named " Student " that contains two string fields i.e. Name & ID. Create a new form and add the newly created "Student" table in the datasource node. Next create a new button on the form, set its multiselect property to " Yes " . Now override the clicked method of the button and add the following code. Code snippet     int             recordsCount;     Student     studentLocal;     super();          recordsCount = student_ds.recordsMarked().lastIndex();  // Total number of marked records.     studentLocal = student_ds.getFirst(1);          while (studentLocal)     {   ...
Read more