Full questions with full answers — no sign-in required.
mediumEquipment
1. Shortly after migrating IoT-enabled equipment master data during hypercare, technicians using the Fiori mobile app report receiving duplicate sensor-triggered alerts for the same piece of equipment. What areas would you investigate to isolate the cause?
First check whether the equipment migration created duplicate equipment master records or duplicate IoT device-to-equipment mappings, since duplicate keys often cause the IoT platform to fire alerts against multiple equipment IDs. Review the integration middleware's deduplication logic and confirm the equipment ID mapping table wasn't populated twice during migration. Also verify Fiori app caching isn't re-displaying resolved alerts, and check if the notification creation logic lacks idempotency checks on the IoT payload.
mediumMobile Maintenance
2. During a refurbishment cycle, technicians using a mobile app report that they cannot see the refurbishment order in their release queue even though planning confirmed it was released in the backend. What are the likely causes and how would you troubleshoot?
Likely causes include a mismatch in the mobile app's filter criteria (e.g., work center, planning plant, or order type not included in sync scope), a delay in the sync job/replication cycle, or the technician's user assignment not matching the order's responsible work center or personnel number. I would first verify the order status in IW32 confirms REL, check the mobile integration monitoring (sync logs/queue) for errors, and confirm the app's work center/plant filter configuration includes the refurbishment order type used.
easyFunctional Locations
3. What is the purpose of a structure indicator when defining functional locations, and how does it affect the technical object hierarchy?
A structure indicator defines the coding template and hierarchy level logic for functional location identifiers, controlling whether the structure is edge-based (derives parent from string) or hierarchy-based (independent of naming). It sets the length, allowed characters, and level breakdown per segment. Once assigned and functional locations exist, changing it is restrictive since it directly affects how location numbers are parsed and linked to superior locations.
mediumMobile Maintenance
4. During a global template rollout, regional maintenance technicians report that the mobile Fiori app for notifications is missing required custom fields visible in the desktop transaction. How would you resolve this while maintaining a consistent global template?
I'd verify whether the custom fields were added through key user extensibility and check if they were explicitly enabled for the mobile Fiori app's UI, since not all custom fields auto-propagate to mobile launchpad tiles. I'd review the app's extensibility scope, adjust the Fiori launchpad role/catalog assignment for the region, and test on the actual mobile device rendering, ensuring the global template's UI configuration is replicated consistently rather than locally patched per region.
mediumEquipment
5. How do equipment categories influence field control and integration behavior, and what should be considered when defining custom equipment categories?
Equipment categories (e.g., M-Machine, E-Electronic, S-Series) drive field selection, screen layout, and which reference/classification data is relevant. They also affect integration, such as whether an equipment can be linked to a fixed asset, a PS network, or serial number profiles. When defining custom categories, consultants must configure number ranges, field selection groups, and partner determination procedures consistently, and consider downstream reporting and interface impacts.
mediumMaintenance Orders
6. How does an external service performed on a maintenance order (via service PO) flow into order costs and eventually financial accounting, and where do production issues typically arise?
A service line on the maintenance order operation creates a PR then PO with account assignment to the order; goods receipt for services (ML81N/MIGO) posts a GR/IR accrual debiting the order and crediting GR/IR clearing; vendor invoice (MIRO) clears GR/IR and posts to AP, hitting FI/CO simultaneously. Issues typically arise from mismatched service entry sheet quantities/values versus PO, GR/IR account not clearing due to price variance, or order account assignment missing causing PO creation failure.
