We’re attempting to import asset lifecycle updates using FBDI templates for our annual asset revaluation process. The import consistently fails with foreign key constraint violations during the validation phase. The error messages indicate that category mappings and location references cannot be resolved, even though we’ve verified the values exist in the system.
Our FBDI template includes asset numbers, category codes, and location identifiers that we exported from a previous successful import. The foreign key validation is rejecting approximately 40% of our 5000+ asset records.
Error: FA_INVALID_CATEGORY_ID
Asset: A-00234 - Category 'COMPUTER-EQUIP' not found
Error: FA_INVALID_LOCATION_CODE
Asset: A-00891 - Location 'BLDG-3-FL2' invalid
We’ve checked that categories and locations exist in their respective value sets, but the FBDI import process isn’t finding them. Is there a specific format or value set alignment requirement for foreign key references in FBDI asset templates that we’re missing?
Good point about the dependent value sets. Our category flexfield does have dependent segments. I’ll check the parent-child relationships. Is there a SQL query or report I can run to extract the exact values that FBDI expects for categories and locations, including any parent segment dependencies?
Yes, you can query the value set tables directly to get the validated values. For categories, query FND_VS_VALUES_B and FND_VS_VALUES_TL filtered by your category value set name. For locations, check FA_LOCATIONS table. The key is to match the exact string format including any leading zeros, spacing, or special characters that the value set validation expects.
I encountered similar issues last year. The problem is often in how the value sets are configured for validation. Check if your category and location value sets have ‘Validation Type’ set to ‘Independent’ or ‘Dependent’. If they’re dependent value sets, the parent values must also be correctly specified in your FBDI template. Also verify that the value set security and data access sets aren’t filtering out certain values that exist but aren’t accessible to the user running the import.