My Oracle Support Banner

ECM: DEIU - Parse Statement Addenda Populating Addenda With Value Even Though it Does Not Match Pattern Specified in Map ID (Doc ID 2745499.1)

Last updated on JANUARY 20, 2021

Applies to:

PeopleSoft Enterprise FIN Cash Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Parse Statement Addenda process is populating an Addenda with an output value even though it does not match the Pattern specified in the Data Export Import Utility (DEIU) Map ID.

STEPS
1. Navigate to Set Up Financials/Supply Chain > Common Definitions > Data Export Import Utility > Map Definition
2. Add a new Map ID = CM_PARSE_TEST by copying it from Map ID = BANK_RECON_PD_MAP
3. Save the Map ID
4. On the Detail – Step 4 of 6 train, delete Lines 6 – 9
5. For line 5, click the Edit button
6. On the Edit Transform Property page, for Group Criteria, check the Always True box
7. Delete Line 2
8. For Line 1, select Transform = Pattern
9. In the Pattern field, enter the following: USREMARK=/BNF/@@@@@@@@@@@@
10. On the Summary – Step 6 of 6 train, Click the Validate button then click the Submit button
11. Navigate to Banking > Administer Reconciliation > Assign Addenda Parse ID
12. Associated Bank information to Map ID = CM_PARSE_TEST
13. Navigate to Banking > Bank Statements > Import Bank Statements
14. Load a BAI2 file
15. Navigate to Banking > Bank Statements > Enter Bank Statements
16. Display the loaded Bank Statement
17. On the Bank Transaction Entry page, access the Addenda Information tab
18. Add Addenda’s to the 1st three lines by clicking the Expanded Addenda hyperlink
19. Addenda for the 1st line:
YOUR REF=O/B CITIBANK NYCREC FROM=CITIBANK N.A.NEW YORK NY 10043-0001 USREMARK=/BNF/CM0000000174 DEBIT REF

20. Addenda for the 2nd line
YOUR REF=O/B BK OF NYCREC FROM=THE BANK OF NEW YORK MELLON NEW YORK NY 10005-2901

21. Addenda for the 3rd line
12345678901234 Parsing test with an addenda

22. Save the Bank Statement
23. Navigate to Banking > Reconcile Statements > Parse Statement Addenda
24. Run the Parse Statement Addenda process specifying the above Statement
25. SQL output of the Addenda parsed for the 1st 3 lines

RECON_REF_ID_01

CM0000000174
BK OF NYCREC
4 Parsing te

26. 1st Addenda is parsed correctly since it matches the pattern from Step 9
27. 2nd and 3rd Addenda do not match the pattern and should not have an output value


NOTE: In the Steps above, user details / customer name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Product name test environment).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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.