D1-SETTRANDT takes customElements from initialSnapshot instead of finalSnapshot (Doc ID 1377453.1)

Last updated on NOVEMBER 15, 2011

Applies to:

Oracle Utilities Meter Data Management - Version: 2.0.1 and later   [Release: 2.0 and later ]
Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management - Version: 3.1 and later ]
Information in this document applies to any platform.

Symptoms

The Service Point ongoing sync request BO (D1-OngoingSyncRequestSP) defines Script D1-SETTRANDT on the Data Transformed lifecycle status. This Script is moving the customElements from the initialSnapshot stanza to the target BO. This is not correct as the initialSnapshot data is not used to create the final object in MDM. The final object in MDM is based on the data in the finalSnapshot stanza.

Prior to MDM v2.0.1 SP5, D1-SETTRANDT had the following code in Step 20:


20: edit data
declareBO "bo_schema/targetBo" as 'targetBo_schema';

move "bo_schema/syncRequestDetails/original/finalSnapshot/formattedElements" to "targetBo_schema";
move "bo_schema/syncRequestDetails/original/finalSnapshot" to "targetBo_schema";
move "bo_schema/syncRequestDetails/original/initialSnapshot/customElements" to "targetBo_schema";
move "bo_schema/targetBo" to "targetBo_schema/bo";

move "targetBo_schema" to "bo_schema/syncRequestDetails/transformed";

invokeBO "parm/hard/businessObject/id" using "bo_schema" for update;
end-edit;

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms