My Oracle Support Banner

Integration Object Field Is Not Reflecting In The Target Env After Full Repository Migration (Doc ID 2466647.1)

Last updated on JULY 16, 2020

Applies to:

Siebel CRM - Version 18.8 and later
Information in this document applies to any platform.

Symptoms

On : 18.8 version, Upgrade

ACTUAL BEHAVIOR
---------------
While doing full repository migration from Dev to Test able to see the I/O in the XMl format in the table "S_RR_INT_OBJ" but new fields are not available for mapping.

EXPECTED BEHAVIOR
-----------------------
After the full repository migration from Dev to Test new added fields should be available for mapping.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Add a new field in the development to any integration object.
2) Deliver the workspace.
3) Deploy the integration object
4) Confirm the changes are reflecting on Dev UI and new field is available
for use.
5) Perform full runtime repository migration from Dev to Test.
6) Log into siebel application runnign at test environment.
7) The new field is not available for mapping in Administration -
Integration.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.