We’re attempting to load warehouse item organization data using FBDI templates for a new distribution center. The FBDI job completes but all 2,847 rows fail validation with error “Locator not found for subinventory RECV-ZONE-A”. I’ve verified the subinventory exists and is locator-controlled in the UI.
Our FBDI template mapping includes ItemNumber, OrganizationCode, SubinventoryCode, and LocatorName columns. The subinventory-locator relationship appears correct when I manually check setup, but the import process doesn’t recognize the association. We’re running this for initial warehouse setup and blocking go-live.
Has anyone encountered FBDI validation issues where the template doesn’t properly resolve the subinventory-locator hierarchy? The import documentation mentions template sequence but doesn’t clarify dependencies.
You’ll need to update your FBDI mapping to include the segment columns. The standard template for warehouse item organizations should have these columns when locators are involved:
ItemNumber, OrganizationCode, SubinventoryCode,
LocatorSegment1, LocatorSegment2, LocatorSegment3
Make sure you’re using the correct template version for 23c. There were changes to the locator handling in the warehouse management FBDI templates between 23b and 23c. Download the latest template from the Import Objects task and compare your column headers.
Another thing - if you created custom locator flexfield segments, you need to ensure they’re registered properly in both the Warehouse Management and Inventory modules. Data import validation checks both registrations.
That’s interesting about the segment columns. Our locators are indeed three-segment (Aisle-Row-Bin). I was using a single LocatorName column with values like “A-01-01”. Let me rebuild the template with separate segment columns and retest. The subinventory is definitely set to Prespecified locator control.
Do I need to change anything in the import map definition, or will FBDI automatically recognize the segment columns?
Check if your locators were imported in a separate FBDI load. The validation engine requires locators to exist AND be associated with the subinventory before item org data can reference them. If you created locators manually or in a different batch, there might be a timing issue with the validation cache.
Also verify the LocatorName format matches exactly - including any segment separators if you’re using multi-segment locators. Case sensitivity matters in FBDI validation.
I ran into this last quarter. The issue is usually that FBDI validates the complete hierarchy path during import. Your template needs to include the full locator context, not just the locator name. For warehouse item orgs, the validation looks for:
OrganizationCode -> SubinventoryCode -> LocatorSegments
If you’re using structured locators (row-aisle-bin), you need separate columns for each segment in the template. A single LocatorName column won’t work for the validation engine when the locator structure has multiple segments defined. Check your locator flexfield configuration - if it’s three segments, your FBDI template needs LocatorSegment1, LocatorSegment2, LocatorSegment3 columns instead of a combined LocatorName.
Also verify that the subinventory’s locator control is set to ‘Prespecified’ not ‘Dynamic’. FBDI won’t validate against dynamic locators.