End Job Activity with REST and set custom lot number

Does anyone know how to end activity with REST using a custom lot number and custom lot attributes?

I tried a payload against this PATCH labor service: /api/v1/Erp.BO.LaborSvc/LaborDtls

{
    "Company": "SD",
    "EmployeeNum": "4444",
    "SubmittedBy": "smason",
    "LaborHedSeq": 111184,
    "LaborDtlSeq": 1314482,
    "SysRowID": "8FA12519-8CEC-43B5-828B-6763FCAA69A0",
    "LaborType": "P",
    "LaborTypePseudo": "P",
    "LaborCollection": true,
    "JobNum": "620026",
    "AssemblySeq": 0,
    "OprSeq": 10,
    "ResourceGrpID": "",
    "OpCode": "BUNS",
    "OpComplete": true,
    "JCDept": "306",
    "ActiveTrans": false,
    "ExpenseCode": "NONPROD",
    "ClockInDate": "2024-09-19",
    "ClockinTime": "16.13",
    "ClockOutTime": "16.20",
    "EnableLot": true,
    "LotNum": "374678",
    "LaborQty": "1.00",
    "LaborHrs": "0.08",
    "LaborRate": ".000000",
    "BurdenHrs": "0.08",
    "BurdenRate": "55.000000",
    "OutputBin": "SHEET-FLR",
    "OutputWarehouse": "MAIN",
    "IndirectCode": "",
    "RowMod": "U",
    "TimeStatus": "A",
    "ApprovedDate": "2024-09-19"
}

Epicor just ignores the lot number I input and uses the job number instead.

2 things:

  • 1 β†’ don’t use the ODATA endpoints, use the custom methods
  • 2 β†’ Verify this works in the client or on the web, and trace when you do it to make sure you are sending the right data.
2 Likes