If the POS system disconnected from the back end AX system (e.g: network disrupt, router hardware issues, etc) then it may display following error when you try to login to your POS system:
This error is not refer to multiple logon issue. I guess the POS system try to validate the staff profile with store number, and verify against "AllowMultipleLogins" value which only exists in AX back end DB. It will failed due to AOS/RTS are not reachable.
Solution:
Marked the “Continue on TS errors” at HQ > Setup > Staff > General tab
Wednesday, September 14, 2011
Wednesday, June 15, 2011
Method 'send' in COM object of class 'CDO.Message' returned error code 0x8004020D ()
Wednesday, October 31, 2007
Financial Statement - Stack trace error
I have stack trace error in standard financial statement report @@
Follow the steps to reproduce the error:
Updated:
Obviously map.empty() doesn't work as it do. Probably following code can solve the bug on our standard financial report.
//empty statement was added to be 100% sure that not critical error being thrown. but it's still redundant.
ledgerBalColumnsDim = ledgerBalColListPrinted.empty() ? ledgerBalColList.lookup(actualColumn) : ledgerBalColListPrinted.lookup(actualColumn);
Change to:
//empty statement was added to be 100% sure that not critical error being thrown. but it's still redundant.
ledgerBalColumnsDim = !ledgerBalColListPrinted ? ledgerBalColList.lookup(actualColumn) : ledgerBalColListPrinted.lookup(actualColumn);
Follow the steps to reproduce the error:
- Go to General Ledger > Reports > Transactions > Periodic > Financial statement
- Choose INC_01 Income statement for Financial statement.
- Choose Account for Main focus.
- Choose P&L for Row definition.
- Click OK button to run the report.
Updated:
Obviously map.empty() doesn't work as it do. Probably following code can solve the bug on our standard financial report.
//empty statement was added to be 100% sure that not critical error being thrown. but it's still redundant.
ledgerBalColumnsDim = ledgerBalColListPrinted.empty() ? ledgerBalColList.lookup(actualColumn) : ledgerBalColListPrinted.lookup(actualColumn);
Change to:
//empty statement was added to be 100% sure that not critical error being thrown. but it's still redundant.
ledgerBalColumnsDim = !ledgerBalColListPrinted ? ledgerBalColList.lookup(actualColumn) : ledgerBalColListPrinted.lookup(actualColumn);
Transfer Orders - Missing Remaining Shipping Quantity
Once again transfer order module gives me trouble. I'm still thinking it is considered as "features" or it just another bug for MS.
Here are the steps to reproduce it:
1) By using demo company, create a transfer order from GW warehouse to MW warehouse.
2) Choose any item (e.g: B-R14) and input 10 quantities.
3) We going to post 3 picking list by the following sequence:
6) Now we do the shipment. It only shows 9 quantities on the screen.
7) Confirmed the shipment and return back to transfer order form. We look at the Lines\Ship Now tab, it is show us still have 1 remaining ship quantity.
It applied to AX4 SP1 & Sp2.
Here are the steps to reproduce it:
1) By using demo company, create a transfer order from GW warehouse to MW warehouse.
2) Choose any item (e.g: B-R14) and input 10 quantities.
3) We going to post 3 picking list by the following sequence:
- 3
- 3
- 4
- 3, same quantities
- 4, increase 1 quantity
- 2, reduced 2 quantities
6) Now we do the shipment. It only shows 9 quantities on the screen.
7) Confirmed the shipment and return back to transfer order form. We look at the Lines\Ship Now tab, it is show us still have 1 remaining ship quantity.
It applied to AX4 SP1 & Sp2.
Wednesday, October 17, 2007
Tips: Enable company/user template when created new form with new table
It is pretty simple. Go and check your new table, look at TableGroup property, and set the value to Group/Main.
There is some info in Dev Guide 4.0 (grabbed from internet):
Table groups constitute a way to categorize tables according to the types of data they hold. Determining group membership, though, is not an exact science but more of a conceptual definition. But when determining group membership for your own tables, follow the standards in the Microsoft Axapta application.
Parameter
The table holds data primarily used as parameters or setup information for one of the Main tables. The table typically holds only one record.
CustParameters, VendParameters
Group
The table holds data primarily used to categorize one of the Main tables. There is a one-to-many relationship between Group and Main.
CustGroup, VendGroup
Main
The table is one of the principal tables in the application and holds data for a central business object. The table typically holds static, base information.
There is a one-to-many relationship between Main and Transaction.
CustTable, VendTable
Transaction
The table holds transaction data. Typically the table is not used for data entry directly.
CustTrans, VendTrans
WorksheetHeader
The table typically categorizes information in the WorkSheetLine tables.
There is a one-to-many relationship between WorkSheetHeader and WorkSheetLine.
SalesTable
WorksheetLine
The table holds information to be validated and made into transactions. Compared to the information in Transaction tables, the information in WorkSheetLine tables is temporary and may be deleted without affecting system stability.
SalesLine
Miscellaneous
The table does not fit in any of the other categories.
There is some info in Dev Guide 4.0 (grabbed from internet):
Table groups constitute a way to categorize tables according to the types of data they hold. Determining group membership, though, is not an exact science but more of a conceptual definition. But when determining group membership for your own tables, follow the standards in the Microsoft Axapta application.
Parameter
The table holds data primarily used as parameters or setup information for one of the Main tables. The table typically holds only one record.
CustParameters, VendParameters
Group
The table holds data primarily used to categorize one of the Main tables. There is a one-to-many relationship between Group and Main.
CustGroup, VendGroup
Main
The table is one of the principal tables in the application and holds data for a central business object. The table typically holds static, base information.
There is a one-to-many relationship between Main and Transaction.
CustTable, VendTable
Transaction
The table holds transaction data. Typically the table is not used for data entry directly.
CustTrans, VendTrans
WorksheetHeader
The table typically categorizes information in the WorkSheetLine tables.
There is a one-to-many relationship between WorkSheetHeader and WorkSheetLine.
SalesTable
WorksheetLine
The table holds information to be validated and made into transactions. Compared to the information in Transaction tables, the information in WorkSheetLine tables is temporary and may be deleted without affecting system stability.
SalesLine
Miscellaneous
The table does not fit in any of the other categories.
Monday, September 10, 2007
Transfer Orders - "Receive Remain" show weird value after multiple shipments and received (2)
Just debugged and found it was caused by following code under InventPickingListJournalRegistrate class - updatePickingListJournal method.
It seem like used to handle over-delivery but I'm wonder how to get the calculation method.
//handle potential overdelivery for transfer orders
if (inventPickingListJournalLine.InventPickRequesterType ==
InventPickRequesterType::Transfer)
{
inventTransferLine = inventMovement.buffer();
if (inventTransferLine)
{
if (inventTransferLine.QtyRemainReceive < abs(inventTransferLine.QtyShipped - inventTransferLine.QtyRemainShip))
{
inventTransferLine.QtyRemainReceive = abs(inventTransferLine.QtyShipped - inventTransferLine.QtyRemainShip);
inventTransferLine.updateEstimatedReceipt();
}
}
}
For me, over-delivery should be:
Over-delivery quantity = total received quantity - total transfer quantity
//handle potential overdelivery for transfer orders
if (inventPickingListJournalLine.InventPickRequesterType ==
InventPickRequesterType::Transfer)
{
inventTransferLine = inventMovement.buffer();
if (inventTransferLine)
{
if (inventTransferLine.QtyTransfer < abs(inventTransferLine.QtyShipped + inventTransferLine.QtyRemainShip))
{
inventTransferLine.QtyRemainReceive = abs(inventTransferLine.QtyShipped + inventTransferLine.QtyRemainShip - inventTransferLine.QtyReceived);
inventTransferLine.updateEstimatedReceipt();
}
}
}
Note:
It seem like used to handle over-delivery but I'm wonder how to get the calculation method.
//handle potential overdelivery for transfer orders
if (inventPickingListJournalLine.InventPickRequesterType ==
InventPickRequesterType::Transfer)
{
inventTransferLine = inventMovement.buffer();
if (inventTransferLine)
{
if (inventTransferLine.QtyRemainReceive < abs(inventTransferLine.QtyShipped - inventTransferLine.QtyRemainShip))
{
inventTransferLine.QtyRemainReceive = abs(inventTransferLine.QtyShipped - inventTransferLine.QtyRemainShip);
inventTransferLine.updateEstimatedReceipt();
}
}
}
For me, over-delivery should be:
Over-delivery quantity = total received quantity - total transfer quantity
//handle potential overdelivery for transfer orders
if (inventPickingListJournalLine.InventPickRequesterType ==
InventPickRequesterType::Transfer)
{
inventTransferLine = inventMovement.buffer();
if (inventTransferLine)
{
if (inventTransferLine.QtyTransfer < abs(inventTransferLine.QtyShipped + inventTransferLine.QtyRemainShip))
{
inventTransferLine.QtyRemainReceive = abs(inventTransferLine.QtyShipped + inventTransferLine.QtyRemainShip - inventTransferLine.QtyReceived);
inventTransferLine.updateEstimatedReceipt();
}
}
}
Note:
- I have tried to use the over-delivery function and configured TO Line\Setup tab. It seems like not working. Probably someone can enlighten to me how to activate the function.
Wednesday, September 5, 2007
Transfer Orders - "Receive Remain" show weird value after multiple shipments and received
I was come across the standard bug in TO that will increase "Receive Remain" value when user tried to do multiple shipments and receive posting.
Let said we try to transfer item A 200 pcs from Warehouse GW to MW.
By using partial transfer, we are going to ship 8 times (each time 25 pcs) through Picking List, Picking List registration, Shipment, and Receive Posting.
We have encountered the "Receive Remain" value increased in the 7th times when we update picking list registration.
Below is the simulation chart (Refer to TO Line\Receive Now tab) after update picking list registration process:
It was applicable to AX4.0 SP1 and SP2.
To be continue... for solution...
Let said we try to transfer item A 200 pcs from Warehouse GW to MW.
By using partial transfer, we are going to ship 8 times (each time 25 pcs) through Picking List, Picking List registration, Shipment, and Receive Posting.
We have encountered the "Receive Remain" value increased in the 7th times when we update picking list registration.
Below is the simulation chart (Refer to TO Line\Receive Now tab) after update picking list registration process:
No | Shipped quantity | Received quantity | Receive remain |
1 | 0 | 0 | 200 |
2 | 25 | 25 | 175 |
3 | 50 | 50 | 150 |
4 | 75 | 75 | 125 |
5 | 100 | 100 | 100 |
6 | 125 | 125 | 75 |
7 | 150 | 150 | 100 (shoule be 50) |
8 | 175 | 175 | 150 (should be 25) |
It was applicable to AX4.0 SP1 and SP2.
To be continue... for solution...
Subscribe to:
Posts (Atom)