Agent 'Actions' And 'Change History' Data Integrity Issues With Automation Agent After Importing Migration Project.
(Doc ID 2593731.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Global Trade Management Cloud Service - Version 6.3.4 and laterOracle Transportation Management Cloud Service - Version 6.3.4 and later
Oracle Transportation Management - Version 4.0 and later
Information in this document applies to any platform.
Symptoms
The Migration Project for importing agent into a target system does not override the agent actions (the Transaction Code is RC), means it does not delete all action in the target system and insert only actions from the source system.
Also, OTM does not update the agent 'Change History'.
Example:
-------------
Target System (2 Actions):
---------------------------
Agent ID: AGENT MIGRATION PROJECT
Agent Type:CONTACT
Agent Event: CONTACT - MODIFIED: USER
Agent Actions:
AD HOC NOTIFY CONTACT: CON01
AD HOC NOTIFY CONTACT: CON02
Change History
2019-07-26 20:21:37 <Domain_NAME>.
2019-07-26 20:13:21 <Domain_NAME>.
Source System (1 Actions):
---------------------------
Agent ID: AGENT MIGRATION PROJECT
Agent Type:CONTACT
Agent Event: CONTACT - MODIFIED: USER
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
- Migration Project: AGENT MIGRATION PROJECT
- Export he Migration Project from Source
- Import the Migration Project in the Target.
Migration Project ID: 20190726-0003
Status: IMPORTED
- Now check view the Agent in the Target instance.
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
AD HOC NOTIFY CONTACT: CON02
Issue#1:
The expectation is to find the following action.
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
OTM is just updating the actions based on the migrated agent action sequence, but not deleting the rest of the actions.
Issue#2:
The updates data is not reflected in the agent 'Change History'
2019-07-26 20:21:37 <Domain_NAME>.
2019-07-26 20:13:21 <Domain_NAME>.
select * from AGENT_ACTION_DETAILS where agent_gid='<Domain_NAME>.AGENT MIGRATION PROJECT'
ACTION_SEQUENCE AGENT_ACTION_GID INSERT_DATE UPDATE_DATE
1 AD HOC NOTIFY CONTACT - CONTACT 2019-07-26 20:21:37.0 2019-07-26 20:22:07.0
2 AD HOC NOTIFY CONTACT - CONTACT 2019-07-26 20:21:37.0
-------------
Target System (2 Actions):
---------------------------
Agent ID: AGENT MIGRATION PROJECT
Agent Type:CONTACT
Agent Event: CONTACT - MODIFIED: USER
Agent Actions:
AD HOC NOTIFY CONTACT: CON01
AD HOC NOTIFY CONTACT: CON02
Change History
2019-07-26 20:21:37 <Domain_NAME>.
2019-07-26 20:13:21 <Domain_NAME>.
Source System (1 Actions):
---------------------------
Agent ID: AGENT MIGRATION PROJECT
Agent Type:CONTACT
Agent Event: CONTACT - MODIFIED: USER
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
- Migration Project: AGENT MIGRATION PROJECT
- Export he Migration Project from Source
- Import the Migration Project in the Target.
Migration Project ID: 20190726-0003
Status: IMPORTED
- Now check view the Agent in the Target instance.
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
AD HOC NOTIFY CONTACT: CON02
Issue#1:
The expectation is to find the following action.
Agent Actions:
AD HOC NOTIFY CONTACT: CON03
OTM is just updating the actions based on the migrated agent action sequence, but not deleting the rest of the actions.
Issue#2:
The updates data is not reflected in the agent 'Change History'
2019-07-26 20:21:37 <Domain_NAME>.
2019-07-26 20:13:21 <Domain_NAME>.
select * from AGENT_ACTION_DETAILS where agent_gid='<Domain_NAME>.AGENT MIGRATION PROJECT'
ACTION_SEQUENCE AGENT_ACTION_GID INSERT_DATE UPDATE_DATE
1 AD HOC NOTIFY CONTACT - CONTACT 2019-07-26 20:21:37.0 2019-07-26 20:22:07.0
2 AD HOC NOTIFY CONTACT - CONTACT 2019-07-26 20:21:37.0
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 |