FA Outbound Communication Send Details Populates Wrong SA ID For Disable Service
(Doc ID 2944051.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.8.0.0.0 and laterOracle Utilities Meter Data Management - Version 2.4.0.0.0 to 2.5.0.0.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.8.0.0.0 version, Framework
FA Outbound Communication Send Details Populates Wrong SA ID for Disable Service
A recent SR, SR 3-32200139371, was created for PGW where D2-ProMDMDtl would populate the wrong SA ID than the Service Agreement linked to the Field Activity's parent Activity Orchestration.
This fix resolved the issue for Start Service Events/Enable Service Orchestrators, but the issue is still seen with Stop Service Events/Disable Service Orchestrators.
The expectation was that Disable Service Orchestrators would link to an Active US, where the D2-RETACTUS script would be used.
While this is true, the Active SA (which has an end date due to Pending Stop) is not being selected by the D2-ProMDMDtl script.
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 |