Invoice posting error in Dynamics Ax2009 '1.00 cannot be picked because only -100.00 is/are available from the inventory.'

This question has suggested answer(s)

I have an item with stock 25 On Hand quantity, but when I post the invoice the system threw an error "1.00 cannot be picked because only -100.00 is/are available from the inventory." Stock -100 calculated from Purchase order less Sales order, quantity adjusted from Movement journal is not calculated on it. And one more thing I have to mention that according to me this error occurred after inventory closing recalculation process. I had tested it on my test machine. Would have any solution to resolve this issue? Thanks in advance!

All Replies
  • I'll simulate your scenario here, but if the inventory transaction happened within the same time frame your inventory closing were executed, then you're gonna have some issues, because when you run inventory closing, Dynamics Ax closes the selected period for any transaction.

    Plus, is it PO or SO? Is it Batch controlled? You may have 25 on hand on your entire warehouse, but if it is batch controlled, you need to have the whole amount (considering you've already posted the picking list) on the same batch as you are trying to post.

  • Error occurred during sales order posting, we do not configure the batch dimension. Furthermore, find the transaction of an item below.

    Site

    Warehouse

    Serial number

    Physical date

    Financial date

    Reference

    Number

    Receipt

    Issue

    Quantity

    Item number

    Dimension No.

    Value open

    Lot ID

    Adjustment

    Financially closed

    Settled quantity

    Type

    10

    1010

    9813020334

    Sales order

    SO-00010725

    On order

    -50

    PSN_0027809

    00013037_075

    Yes

    Customer

    10

    1010

    9813020334

    01-Jul-11

    01-Jul-11

    Transaction

    000191_076

    Purchased

    203

    PSN_0027809

    00013038_075

    No

    30-Jun-12

    203

    Inventory

    10

    1010

    9813020334

    01-Jul-11

    01-Jul-11

    Transaction

    000391_076

    Purchased

    1

    PSN_0027809

    00013037_075

    No

    30-Jun-12

    1

    Inventory

    10

    1010

    9813020334

    17-Sep-11

    17-Sep-11

    Sales order

    SO-00000972

    Sold

    -10

    PSN_0027809

    00013037_075

    No

    -263.02

    30-Jun-12

    -10

    Customer

    10

    1010

    9813020334

    14-Feb-12

    14-Feb-12

    Sales order

    SO-00004056

    Sold

    -25

    PSN_0027809

    00013037_075

    No

    -657.57

    30-Jun-12

    -25

    Customer

    10

    1010

    9813020334

    29-Feb-12

    29-Feb-12

    Purchase order

    PO-00000714

    Purchased

    150

    PSN_0027809

    00013037_075

    No

    30-Jun-12

    150

    Vendor

    10

    1010

    9813020334

    03-Mar-12

    03-Mar-12

    Sales order

    SO-00004470

    Sold

    -25

    PSN_0027809

    00013037_075

    No

    -95.95

    30-Jun-12

    -25

    Customer

    10

    1010

    9813020334

    08-Mar-12

    08-Mar-12

    Sales order

    SO-00004605

    Sold

    -40

    PSN_0027809

    00013037_075

    No

    -153.51

    30-Jun-12

    -40

    Customer

    10

    1010

    9813020334

    15-Mar-12

    15-Mar-12

    Sales order

    SO-00004776

    Sold

    -42

    PSN_0027809

    00013037_075

    No

    -161.19

    30-Jun-12

    -42

    Customer

    10

    1010

    9813020334

    20-Mar-12

    20-Mar-12

    Sales order

    SO-00004847

    Sold

    -1

    PSN_0027809

    00082064_075

    No

    -3.83

    30-Jun-12

    -1

    Customer

    10

    1010

    9813020334

    24-Mar-12

    06-Apr-12

    Sales order

    SO-00004999

    Sold

    -1

    PSN_0027809

    00013037_075

    No

    24-Mar-12

    Customer

    10

    1010

    9813020334

    27-Mar-12

    27-Mar-12

    Sales order

    SO-00005102

    Sold

    -86

    PSN_0027809

    00013037_075

    No

    -330.08

    30-Jun-12

    -86

    Customer

    10

    1010

    9813020334

    06-Apr-12

    06-Apr-12

    Sales order

    SO-00004999

    Purchased

    1

    PSN_0027809

    00013037_075

    No

    06-Apr-12

    Customer

    10

    1010

    9813020334

    10-Apr-12

    10-Apr-12

    Purchase order

    PO-00000939

    Purchased

    100

    PSN_0027809

    00013037_075

    No

    30-Jun-12

    100

    Vendor

    10

    1010

    9813020334

    21-Apr-12

    21-Apr-12

    Sales order

    SO-00005902

    Sold

    -12

    PSN_0027809

    00013037_075

    No

    88.94

    30-Jun-12

    -12

    Customer

    10

    1010

    9813020334

    03-May-12

    03-May-12

    Sales order

    SO-00006201

    Sold

    -15

    PSN_0027809

    00013037_075

    No

    111.17

    30-Jun-12

    -15

    Customer

    10

    1010

    9813020334

    07-May-12

    08-Aug-12

    Sales order

    SO-00006281

    Sold

    -1

    PSN_0027809

    00013037_075

    No

    07-May-12

    Customer

    10

    1010

    9813020334

    10-May-12

    14-May-12

    Sales order

    SO-00006399

    Sold

    -1

    PSN_0027809

    00013037_075

    No

    10-May-12

    Customer

    10

    1010

    9813020334

    14-May-12

    14-May-12

    Sales order

    SO-00006399

    Purchased

    1

    PSN_0027809

    00013037_075

    No

    14-May-12

    Customer

    10

    1010

    9813020334

    22-May-12

    22-May-12

    Sales order

    SO-00006684

    Sold

    -5

    PSN_0027809

    00013037_075

    No

    37.06

    30-Jun-12

    -5

    Customer

    10

    30-Jun-12

    30-Jun-12

    Weighted average   inventory closing

    Purchased

    471

    PSN_0027809

    00023687_075

    Yes

    00300667_074

    62.96

    278

    Inventory

    10

    30-Jun-12

    30-Jun-12

    Weighted average   inventory closing

    Sold

    -471

    PSN_0027809

    00023687_075

    No

    00300667_074

    -62.96

    30-Jun-12

    -471

    Inventory

    10

    1010

    9813020334

    08-Aug-12

    08-Aug-12

    Sales order

    SO-00006281

    Purchased

    1

    PSN_0027809

    00013037_075

    No

    08-Aug-12

    Customer

    10

    1010

    9813020334

    17-Aug-12

    17-Aug-12

    Sales order

    SO-00008041

    Sold

    -50

    PSN_0027809

    00013037_075

    Yes

    370.52

    Customer

    10

    1010

    9813020334

    20-Nov-12

    Sales order

    SO-00009659

    Deducted

    -1

    PSN_0027809

    00013037_075

    Yes

    Customer

    10

    1010

    9813020334

    12-Jan-13

    Sales order

    SO-00010391

    Deducted

    -1

    PSN_0027809

    00013037_075

    Yes

    Customer

    10

    1010

    9813020334

    12-Jan-13

    Sales order

    SO-00010392

    Deducted

    -1

    PSN_0027809

    00013037_075

    Yes

    Customer

    10

    1010

    9813020334

    21-Jan-13

    Sales order

    SO-00010537

    Deducted

    -1

    PSN_0027809

    00013037_075

    Yes

    Customer

    89

     

     

  • Kindly paste the transaction into excel to check the error.

     

  • Run again inventory closing recalculation process, may be your Item number was block. If you cant run again this process you'll have to research by code.

    Regards.

    ANTONIO GILABERT
    AX3.ES
  • I had run again inventory closing process including recalculation, but the problem is still exist.

  • I checked your inventory transactions by copy and paste into excel. You are using as inventory dimensions at least site, warehouse and serial numbers. The inventory is separated for serial numbers per dimension number (inventdimid). The current stock seems to be 139 items. When I counted the purchased and sold transactions for the dimension number that is used on the open sales transaction you have a current stock on this dimension number of -63.

    You have to check the used site, warehouse and serial number values on all transactions to see which values were used. These values are not visible in the table you attached in this thread. When you know these values, you might use an inventory journal for having some corrections.

    kind regards,

    André Arnaud de Calavon  |  Microsoft Dynamics AX Solution architect  |  My blog  |  My company

    This post is my own opinion and does not necessarily reflect the opinion or view of my company, Microsoft, both its employees, or other MVPs.

  • All the site and serial number were same, there were a few transfer transactions of warehouse(wh1010 to wh1020 / wh1020 to wh1010 etc.). The effect of these transfers was null. Therefore, all the transactions values were same except warehouse. Hope you got my point.

  • Hi Muhammed,

     

    Look at your table in another view:

    Dimension   No. Quantity Status Number Reference
    00013037_075 -50 On order SO-00010725 Sales order
    00013037_075 1 Purchased 000391_076 Transaction
    00013037_075 -10 Sold SO-00000972 Sales order
    00013037_075 -25 Sold SO-00004056 Sales order
    00013037_075 150 Purchased PO-00000714 Purchase order
    00013037_075 -25 Sold SO-00004470 Sales order
    00013037_075 -40 Sold SO-00004605 Sales order
    00013037_075 -42 Sold SO-00004776 Sales order
    00013037_075 -1 Sold SO-00004999 Sales order
    00013037_075 -86 Sold SO-00005102 Sales order
    00013037_075 1 Purchased SO-00004999 Sales order
    00013037_075 100 Purchased PO-00000939 Purchase order
    00013037_075 -12 Sold SO-00005902 Sales order
    00013037_075 -15 Sold SO-00006201 Sales order
    00013037_075 -1 Sold SO-00006281 Sales order
    00013037_075 -1 Sold SO-00006399 Sales order
    00013037_075 1 Purchased SO-00006399 Sales order
    00013037_075 -5 Sold SO-00006684 Sales order
    00013037_075 1 Purchased SO-00006281 Sales order
    00013037_075 -50 Sold SO-00008041 Sales order
    00013037_075 -1 Deducted SO-00009659 Sales order
    00013037_075 -1 Deducted SO-00010391 Sales order
    00013037_075 -1 Deducted SO-00010392 Sales order
    00013037_075 -1 Deducted SO-00010537 Sales order
    subtotal -63
    00013038_075 203 Purchased 000191_076 Transaction
    subotal 203
    00023687_075 471 Purchased Weighted avg. inv. closing
    00023687_075 -471 Sold Weighted avg. inv. closing
    subtotal 0
    00082064_075 -1 Sold SO-00004847 Sales order
    subtotal -1

     

    As the Dimension No is a unique combination of your inventory dimensions, a difference should be in site, warehouse, serial number or another dimension.

    So AX thinks there is a difference and you don't have sufficient inventory...

    Please check if all transfers are posted correctly. I can't see which dimension no is what combination of dimensions.

    kind regards,

    André Arnaud de Calavon  |  Microsoft Dynamics AX Solution architect  |  My blog  |  My company

    This post is my own opinion and does not necessarily reflect the opinion or view of my company, Microsoft, both its employees, or other MVPs.

  • Hi Mr. Andre,

    As you said that the combination of inventory dimensions should be difference in site, warehouse and serial number respectively, which is clearly shown in the given figure. But the highlighted entries has same combination whereas the dimension number is not unique. I am asking this to our consultants that why this happened? Your calculation was absolutely perfect, you got the right point that according to dimension item don't have sufficient inventory. But how can AX ignore the dimension number when posting the sales order?

     

    Dimension No. Configuration Size Color Site Warehouse Batch number Location Serial number
    00013035_075 9813020334
    00013036_075 00013035_075 (On Hand in AX) 9813020334
    00013037_075 10 1010 -64 9813020334
    00013038_075 10 1010 203 9813020334
    00043371_075 1010 9813020334
    00081545_075 10 1010-Transit 9813020334
    00081546_075 10 LBF02 9813020334
    00082064_075 10 LBF03 9813020334
    00098803_075 10

    9813020334

    use rich text formatting to view the table

    Kind Regards,

    Muhammed Ali

  • Hi Muhammed,

    AX cannot ignore the dimension no. on postings. This could be caused by manual changes in this table. I saw this once when we had to add the batch number in an implementation where we first did not have this dimension. All records in InventDim table were converted, but one user did not wait for the release of the conversion and created already some transactions. In that time after conversion we had "double" records as well. We corrected it with an script to change all related transactions and purchase lines to have only one dimension number.

    Sounds easy, but we did some testing in another environment to be sure nothing else could go wrong.

    In your case you have to be careful as well with the inventory closing. If you have used it for this item, check the related postings if this was correct.

    Good luck!

    kind regards,

    André Arnaud de Calavon  |  Microsoft Dynamics AX Solution architect  |  My blog  |  My company

    This post is my own opinion and does not necessarily reflect the opinion or view of my company, Microsoft, both its employees, or other MVPs.

  • Hi AndrĂ©,

    Thanks for your consideration regarding this matter. I have discussed it with our consultant and they will be find some solution soon. If I need your more assistance I will contact you again. Thanks a lot!

    Regards,

    Muhammed Ali

  • Hi guys

    I have also this problem , please see below picture. Who could slove this problem