Hi @mlewis1 

To create a Move Transaction you have to make sure the production order is In Process and it has still quantities to complete. I tested a call and seems to be working using MoveEntry endpoint:

You can test it on a 23.200.001 version.

The payload:

{    
    "Date": {
        "value": "2023-11-13"
    },
    "Description": {
        "value": "API TEST"
    },
    "Details":  
        {            
            "LineNbr": {
                "value": 1
            },
            "Location": {
                "value": "LOCATION"
            },
            "LotSerialNbr": {},
            "OperationNbr": {
                "value": "0010"
            },
            "OrderType": {
                "value": "RO"
            },
            "ProductionNbr": {
                "value": "0038689"
            },
            "Quantity": {
                "value": 1.000000
            },            
            "UOM": {
                "value": "EA"
            },
            "Warehouse": {
                "value": "WAREHOUSE"
            }            
        }
    ]
}

The response:

Would an update be done using the same endpoint? I have a situation where I am attempting to modify the transaction attributes and it fails with an error "Line 2 of Move Transaction  requires Attribute placeholder for attribute]" even though my attributes are in the correct order. The JSON payload is in the same order as the initial creation.

Hi @rwiscott 

Same principle. You need to manage the collections available in the endpoint

I recommend to do the update in 2 steps:

• Get the specific move transaction and specific production order line you want to update (Attributes)

• Then get the specific ids to point to the specific record to update and build your payload accordingly:

{   
    "BatchNbr": {
        "value": "0106123"
    },
    "Details": :
        {            
            "LineNbr": {
                "value": 1
            },
            "OrderType": {
                "value": "RO"
            },
            "ProductionNbr": {
                "value": "0038689"
            },
            "InventoryID": {
                "value": "PK26G2-02"
            },
             "Quantity": {
                "value": 1.000000  <-- "Important, keep the original quantity" 
            },
            "TransactionAttributes": :
                {
                    "id": "081ff52a-5060-49d9-ac3c-216bdde377cd",                                        
                    "AttributeID": {
                        "value": "ARFY15"
                    },         
                    "TranLineNbr": {
                        "value": 1
                    },           
                    "Value": {
                        "value": "5" <-- "New Value"
                    }                    
                }
            ]            
        }
    ]
}

Response

In Acumatica

It is worth to mention that attributes linked to Move Transactions are kept in a different table. The original attribute value in the production order won’t be updated.

Enjoy!