Bulk Create Location-Level Cycle Count Tasks Directly
This API is used to create location-driven cycle count tasks directly in bulk, bypassing the need to execute a cycle count task creation template.
Note: This API supports creation of only location-based cycle count
tasks and does not support bulk creation of item-driven cycle count tasks.
URL
POST .../wms/lgfapi/v10/entity/location/cc_loc_task/bulk_create
Request Parameters
| Category | Parameter/Field Name | Type | Required | Description |
| parameters | facility_id | Integer | Conditional | Facility context by id. |
| parameters | facility_id__code | String | Conditional | Facility context by code. |
| parameters | id__in | Array (Integer) | Yes | Valid active or reserve location IDs to create location-driven
count tasks. You can pass a single or multiple location IDs. You can pass only a single location id in the payload. |
| options | priority | Integer | Yes | Task Priority. |
| options | description | String | Yes | Valid CC task type description to create location-driven count tasks. You can pass only CC task type. |
| options | commit_frequency | Integer | No |
Frequency at which the changes are applied to each resource or group of resources being processed. Supported values:
|
Note:
- Either facility_id or facility_id__code should be sent. If you send both, the API fails.
- If you send a location for which the count is in pending status, the system creates a new CC task in Held status for the location.
Request Body (with id__in)
{
"parameters": {
"id__in": [132440,130200,132888],
"facility_id__code": "Facility01"
},
"options": {
"priority":2,
"description": "CC_LOCATION_DTL",
"commit_frequency": 10
}
}
Sample Response
{
"record_count": 3,
"success_count": 3,
"failure_count": 0,
"data": null,
"details": null
}
You can also send a single location id in the payload.
Request Body (with id)
{
"parameters": {
"id": 132440,
"facility_id__code": "Facility01"
},
"options": {
"priority":2,
"description": "CC_LOCATION_DTL",
"commit_frequency": 10
}
}
Sample Response
{
"record_count": 1,
"success_count": 1,
"failure_count": 0,
"data": null,
"details": null
}