After transporting our warehouse management configuration from DEV to QA environment (SI-2302), several location resources are missing in the target system. The transport package shows successful completion, but when I open the planning area, about 30% of warehouse locations don’t appear in the location master data.
I verified the transport package included all configuration objects and master data dependencies. The planning area activation in QA completed without errors, but the missing locations are causing our inventory optimization operators to fail. The error log shows ‘Location resource not found’ for these missing entries.
Is there a specific sequence for transporting location resources, or could this be a master data dependency issue that’s not captured in the transport package?
I reviewed the transport log and found warnings about ‘Referenced master data not available’ for several location attributes. It seems the location resources reference specific storage type attributes that weren’t included in the package. However, I’m not sure how to identify all these dependencies before creating the transport package.
I encountered this exact issue last month. The problem is that location resources in warehouse management have implicit dependencies on planning area configuration that aren’t always captured automatically. When you transport just the planning area, the location master data might reference attributes or hierarchies that don’t exist yet in QA. You need to transport in sequence: first master data structures, then location resources, then planning area configuration. Also check if your QA system has the same organizational structure as DEV.
Check if the location master data was included in the transport package content. Sometimes location resources have dependencies on other master data entities like organizational units or storage types that need to be transported first. Look at the transport log for any warnings about missing dependencies.
Use the Transport Tool’s dependency analysis feature before creating the package. Select your planning area and choose ‘Analyze Dependencies’ - this will show all related master data objects. Make sure to include not just location resources but also any attribute hierarchies, planning level definitions, and key figure assignments that reference locations. The tool should flag missing dependencies, but you need to run the analysis first.
The root cause of missing location resources after transport is incomplete transport package completeness due to master data dependencies that aren’t automatically detected. Here’s the comprehensive solution:
1. Transport Package Completeness Analysis:
Before creating any transport package, perform a complete dependency analysis:
Open Transport Tool and select your planning area
Click ‘Analyze Dependencies’ and wait for full scan
Review ALL flagged dependencies: master data attributes, hierarchies, calculation views, key figures
Create a checklist of required objects in dependency order
2. Master Data Dependencies Resolution:
Location resources in warehouse management depend on multiple master data layers:
First Transport (Foundation):
Storage type attributes and hierarchies
Organizational unit definitions
Location attribute master data (capacity, type, zone attributes)
Planning level definitions that include location dimension
Second Transport (Configuration):
Planning area configuration with location planning levels
Key figure definitions that use location attributes
Calculation views that reference locations
Third Transport (Resources):
Location resources themselves
Location-specific key figure assignments
Planning operator configurations
3. Planning Area Activation Sequence:
After transport to QA, follow this activation sequence:
Verify all master data dependencies are present in target system
Activate planning area (this creates database structures)
Run ‘Initialize Master Data’ job from Jobs and Scheduling app
Check master data consistency report for missing references
If locations still missing, manually export/import location master data using Excel templates
4. Missing Location Recovery Process:
For the 30% missing locations in your case:
// Export from DEV:
Export -> Master Data -> Location Resources
Filter: Status = Active, Modified After = [transport date]
Format: Excel template
// Import to QA:
Import -> Master Data -> Location Resources
Validation: Check for duplicate IDs
Mode: Add Missing Only
5. Verification Steps:
After transport and recovery:
Open planning area in QA and verify location count matches DEV
Run test planning operator to confirm location resources are accessible
Check key figure data can be created at location level
Review system log for any remaining ‘Location resource not found’ errors
6. Prevention for Future Transports:
Create a transport checklist template:
Run dependency analysis and document all required objects
Group objects by dependency layer (foundation → config → resources)
Create separate transport packages for each layer
Test each package in sandbox environment before QA transport
Document the sequence and timing between transports
The key issue is that IBP’s transport tool treats location resources as configuration, but they have runtime dependencies on master data that must exist first. Always transport master data structures before the objects that reference them, and use the Initialize Master Data job after planning area activation to rebuild the location resource index.
Another aspect to consider - are these location resources created through data integration jobs or manually? If they’re created via integration, the transport won’t include them because they’re treated as transactional data, not configuration. You’d need to either manually create them in QA or set up the same integration job to populate them after transport.