Parse rules

1. Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.
How to Define Parse Ruleset in Fusion Cash Management? (Doc ID 2271373.1)
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Fusion Cash Management - Version 11.1.9.2.0 and later
Oracle Fusion Cash Management Cloud Service - Version 11.1.9.2.0 to 11.12.1.0.0 [Release 1.0]
Information in this document applies to any platform.
GOAL
What are the steps in Oracle Fusion Cash Management to create parse rule sets to transform data during the bank
statement import process to populate key fields?
SOLUTION
Parse rules are used to move data from one field to another. The parse rule set is associated to a bank account in the
bank account setup. The parse rule set is most commonly used to parse data from the statement line addenda field into
more specific statement line fields. Each parse rule within a parse rule set consists of the following fields:
Sequence : Sequence determines the order in which to process the rules.
TransactionCode : Transaction Code is the code used to determine the statement line type.

2. Didn't find what you are looking for?
Source : Source is the interface table field that contains the data to be parsed.
Target: Target is the statement line field that the data is to be parsed to.
Rule: Rule contains the syntax for determining the data within the source field to be parsed.
Overwrite : Overwrite is used to control whether to overwrite existing data in a target field or skip parsing the data.
The parse rule syntax is described below:
[LITERAL](<[MATCHING TOKEN],[START-END]>)[LITERAL]
Where:
LITERAL = A string or character value represented by an identifier that should match the source data exactly.
MATCHING TOKEN = A token (or set of tokens) which describes the data to extract. Valid tokens are:
N = Extract a valid number
. = Decimal position
X = Extract an alpha numeric
~ = Extract everything in the source field from the parse position to either the end of the data or up to the next literal.
START = A position to begin extracting data, offset by the parse position. It must be a valid numeric.
END = A position to stop extracting data. END can be either a valid numeric or the ~ token.
Please review training document which includes setups related to Auto Reconciliation.
REFERENCES
NOTE:2393632.1 - Parsing Rule To Remove Leading Zeros