ECM: Parsing Property "PATTERNS" Is Behaving Differently Then Documented In PeopleBooks
(Doc ID 2346804.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise FIN Cash Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
How Parsing property "PATTERNS" is behaving in PeopleSoft?
As per Peoplebooks, the PATTERN property should do following:
Use this transformation type to match a substring with a pattern that you want to replace in the output. Add the wildcard character “@” to the pattern to identify the length of the entire string to include in the output.
For example, when you enter abc@@@"in the Pattern field, you want to find substrings with “abc” and include three trailing characters in the output. If the entered source string is dfabc123kkyabc456, DEIU processing identifies the pattern “abc” and inserts “abc123” in the target field.
However if the following PATTERN is setting up: AP@@@@@@@@@, then the expectation would be for example to see in the BANK_ADDEND_TBL the value of AP000037978 in one of the RECON_REF_ID fields. However application engine BNK_RCN_ADDN does not populate RECON_REF_ID with the value AP000037978 instead this field is populated with 000037978 so it excludes the prefix of AP.
According to example in PeopleBooks however the populated value should be AP000037978.
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