Technician's Primary Address Is Not Picked Up By Mobile Field Service Multiplatform When Creating Parts Requirement
(Doc ID 2681849.1)
Last updated on JUNE 21, 2023
Applies to:
Oracle Mobile Field Service - Version 12.2.8 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
Technician's Primary Address Is Not Picked Up By Mobile Field Service Multiplatform When Creating Parts Requirement. When PR is created from [Mobile Field Service Multi platform] and it does not pick up primary address and picks up random address by default. This causes the part to be delivered to wrong/previous address.
EXPECTED BEHAVIOR
Primary address should be the defaulted that could be selected when technician is selected in MFS MP [Mobile Field Service Multi platform]
STEPS
-----------------------
1. Login to Mobile Field Service Multi platform
2. Create a part requirement for the technician and save. Perform the Sync.
3. Once PUML [Process upload mobile Data] runs, the PR gets synced to EBS and when the same is opened find that the Technician address is not defaulted to the Primary address, but a secondary address of the resource is selected randomly.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |