@mikebar98 

If you are able to perform this transaction with the same data in UI, I dont see why it would error out in API. If thats the case, could be a bug how API is handling the transaction, and I would suggest opening a DEV support ticket for further review and bug fix if required.

However, have you looked up the error message. I found following community discussion that might be helpful:

ERROR: One or more lines have unassigned Location and/or Lot/Serial Number | Community (acumatica.com)

Hi @mikebar98,

You can try following payload structure to include the Lot/Serial Number in the request. This will allow you to specify LotSerialNbr for each InventoryID/detail line you add.

{
    "Description": {
        "value": "From API"
    },
    "Details": [
        {
            "InventoryID": {
                "value": "AAPOWERAID"
            },
            "Allocations": [
                {
                    "Location": {
                        "value": "R1S1"
                    },
                    "LotSerialNbr": {
                        "value": "LREX15026"
                    },
                    "Qty": {
                        "value": 20.000000
                    }
                }
            ]
        }
    ]
}

Hope that helps.! Feel free to post if you have any questions. Good Luck.!

I believe what @Vignesh Ponnusamy created should help you solve your issue.

Thank you @Vignesh Ponnusamy, this was it!

Is there some API doc that I’m missing? I thought I looked everywhere for inventory issue pushing, didn’t see this allocation key. 

Hi @mikebar98,

Glad that helps.! 

It is possible that we don’t have example for all the endpoint entity but you should be able to locate documentation similar to this screen/functionality. For example, below are a two example of creating allocations from the API,

• https://help-2021r1.acumatica.com/Help?ScreenId=ShowWiki&pageid=918995d9-45ce-4cf7-a271-608abf967ae8
• https://help-2021r1.acumatica.com/Help?ScreenId=ShowWiki&pageid=f8ef40fd-5a93-4e39-a52b-e827355cb5b8

Cheers.!

Hi team, following up here
 

it seems that the UOM i specify during the allocation (which matches the UOM i specify on the top level) is being ignored. The default UOM is being assumed (which is incorrectly converting the qty i specify in the allocation).

Is that expected? I believe im passing the UOM correctly. Here’s a sample payload 

payload = {
  'Note': {
    'value': 'Vendor Order Items 255989'
  },
  'Details': a
    {
      'InventoryID': {
        'value': 'GEN-10062'
      },
      'Note': {
        'value': 'VO 226581, VOI 255989'
      },
      'TranType': {
        'value': 'Issue'
      },
      'UnitPrice': {
        'value': 0.1245
      },
      'UOM': {
        'value': 'ML'
      },
      'WarehouseID': {
        'value': 'TP-NY'
      },
      'Location': {
        'value': 'TP-NY'
      },
      'Qty': {
        'value': '1'
      },
      'ReasonCode': {
        'value': 'TPISSUE'
      },
      'Allocations': i
        {
          'InventoryID': {
            'value': 'GEN-10062'
          },
          'LotSerialNbr': {
            'value': '54838052340'
          },
          'UOM': {
            'value': 'ML'
          },
          'Qty': {
            'value': '1'
          },
          'Location': {
            'value': 'TP-NY'
          }
        }
      ]
    }
  ],
  'PostPeriod': {
    'value': '10-2023'
  },
  'Date': {
    'value': '2023-10-23'
  }
}

worth to note that the base unit is in bottles, and im trying to push in ML. I see a UOM field so id think that i should be able to push an issue with whatever UOM i desire, is that not the case?

Hi @mikebar98,

Request payload looks good to me. I tried the following and able to set the UOM to the Detail Line and to its allocation,

{
    "Description": {
        "value": "From API"
    },
    "Details": [
        {
            "InventoryID": {
                "value": "AAPOWERAID"
            },
            "UOM": {
                "value": "PALLET"
            },
            "Allocations": [
                {
                    "Location": {
                        "value": "R1S1"
                    },
                    "LotSerialNbr": {
                        "value": "LREX15026"
                    },
                    "Qty": {
                        "value": 20.000000
                    },
                     "UOM": {
                        "value": "EA"
                    }
                }
            ]
        }
    ]
}

Are you able to set the required UOM values from the UI?

Also, it would be worth checking the Units of Measure screen to setup the right conversion rate. 

here’s what i see after i PUT that payload i shared

it thinks i sent 1 bottle, when i sent 1 ML 

here is the conversion table

I can put whatever value i want in the allocation UOM, and the API will not yell at me. It feels that the system ignored the allocated UOM & goes with the base unit

Hi @mikebar98,

Yes, I see the behavior.

UOM is being bought from the Allocation Details, which defaults the Base unit from the Stock Item. 

I would suggest you check with the Product Support team, they should be able to suggest a configuration/setup that might allow you use different UOMs for a allocation. Thanks,