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