Copy Node (STTP) Will not Properly Build a Target Data when "Treat Target as Prefix" is ticked
(Doc ID 1545904.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
COPY (STTP) Node is used to copy "string" / "numeric string" data from one data field to another and aim to append a source data field to a target data field by ticking "Treat Target as Prefix" check box, as shown by this following example:
- Assuming that you have "IteratorString1" profile data & "IteratorString2" profile data and their value are "AAA" and "BBB" respectively
Image 1 - Setting up a profile tags values
- You aim to combine those data to be "AAABBB" by using STTP node by selecting the "IteratorString2" (BBB) as a source profile and the "IteratorString1" (AAA) as a target profile and tick "Treat Target as Prefix" check box
Image 2 - Configure Copy Profile with "Treat Target as Prefix" ticked
However, when control plan is saved/compiled and used in the runtime, the STTP node with "Treat Target as Prefix" ticked does not copy the data as it should. The data is copied as "BBBAAA" which means it treats a source as prefix instead.
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