Location Error Codes

The following errors are specific to the Location module.

The %s in error messages are placeholders used to indicate where a specific value, such as a Location ID, will be inserted when the actual error message is displayed.

For example, let’s assume the error is “Overlapping Outage exist for this locationNum. Outage Id : %s”. This error occurs when a user tries to schedule a new maintenance outage for a specific warehouse (Location Number 123), but there’s already an existing outage, OUTAGE-A-123, scheduled for the same period. This means the error would display “Overlapping Outage exist for this locationNum. Outage Id : OUTAGE-A-123.”

Module	Error Code	Message
Location	LOCATION-2001	End Date should be after Start Date.
Location	LOCATION-2002	Overlapping Outage exist for this locationNum. Outage Id : %s.
Location	LOCATION-2003	Fulfillment methods are not defined for this tenant.
Location	LOCATION-2004	Not applicable for modification in this stage.
Location	LOCATION-2005	Outage is already cancelled!
Location	LOCATION-2006	Outage couldn’t be cancelled due to an error.
Location	LOCATION-2007	Location capacity can not be infinite with maxAllocation limit.
Location	LOCATION-2008	Location current allocation can not be more than maxAllocation limit.
Location	LOCATION-2009	Maximum allocations is null or negative.
Location	LOCATION-2010	Maximum allocations cannot be less than current allocation.
Location	LOCATION-2011	Current allocation can’t be updated using this API.
Location	LOCATION-2012	CapacityOverride cannot be cancelled—it has already ended or been cancelled.