Reject/Recount a Cycle Count Adjustment Record

This API is used to reject/recount a pending Cycle Count (CC) adjustment record.

URL

POST .../wms/lgfapi/v10/entity/cc_adjustment_hdr/reject/

Request Parameters

Category	Parameter/Field Name	Type	Required	Description
parameters	facility_id	Integer	No	Facility context by id.
parameters	facility_id__code	String	No	Facility context by code.
parameters	company_id	Integer	No	Company context by id.
parameters	company_id__code	String	No	Company context by code.
parameters	location_barcode	String	Conditional	Location barcode subjected to CC adjustment record.
parameters	group_nbr	String	Conditional	Group number of a specific CC adjustment record.
options	cc_task_type	String	No	Valid item-driven cycle task type description to create item-driven count tasks. You can pass only item-driven cycle count task type description in the payload.
options	priority	Integer	Conditional	Task Priority. If cc_task_type value is passed, then you must pass a value in the priority field.
options	comment	String	No	CC adjustment rejection comments. This field supports a maximum of 250 characters. If you pass a value longer than the 250 characters, the API fails with an error message.

Note:

• This API is supported only in the synchronous mode.
• If facility or company context isn’t provided, the API will use your default facility/company.
• You must pass either one or both “location_barcode” and “group_nbr” fields.
• If the “location_barcode” is provided without “group_nbr” and multiple pending CC adjustment records are found for the specified location, the API returns an error message “Multiple pending CC adjustment records found for the location %LOCATION_BARCODE. Please provide group_nbr”. This validation prevents unintended bulk rejection of pending CC records when you perform item driven cycle count for a location.
• When rejecting location-driven cc adjustment records, if reject/recount cc trigger is enabled, the system creates location level cycle count task. For more details on validations, refer “Create Item Driven Cycle Count Tasks for Rejected Counts” section in Online Help.
• When an MHE-driven cycle count adjustment populated with an MHE system is rejected through this API and a task is created, the system sends Cycle Count Task Info to that specific MHE system.

Request Body

{ 
    "parameters":
     {   
         "facility_id": 648,
         "company_id": 369,
         "location_barcode": "ACTR000107",
         "group_nbr": 33457
     },
    "options":
    {
             "cc_task_type": "CC By Item",
		"priority": 20,
		"comment": "CC rejected due to conflict"
     }

}

Sample Response

204 No Content