Overview of Parse Rule Sets

Oracle Fusion Cash Management supports parse rule sets to transform data during the bank statement import process. 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: Determines the order in which to process the rules.

  • Transaction Code: The code used to determine the statement line type.

  • Source Field: The interface table field that contains the data to be parsed.

  • Target Field: The statement line field that the data is to be parsed to.

  • Rule: Contains the syntax for determining the data within the source field to be parsed.

  • Overwrite: Used to control whether to overwrite existing data in a target field or skip parsing the data.

The parse rule syntax is described in the following:

[LITERAL](<[MATCHING TOKEN],[START-END]>)[LITERAL]

Where

LITERAL represents a string or character value represented by an identifier that should match the source data exactly.

MATCHING TOKEN represents a token (or set of tokens) which describes the data to extract. The following table lists the valid tokens with their descriptions:

Token

Description

N

Extract a valid number

.

Decimal position

X

Extract an alphanumeric

~

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.

The following table lists some examples:

Description

Source Data

Rule

Target Data

Extract numeric rate data from a source field

EST/TRX RTE 3.76 USD/LIBOR CPTY: PRU

RTE (N.NN)

3.76

Extract value date from a source field

Dt.01/01/2011?Receipt

Dt.(1-10)?Receipt

01/01/2011

Extract check number from a source field

Account Number 1005

Account Number.(X~)

1005

Extract currency from a source field

$^EUR:Dt

$^(1-3):Dt.

EUR

Extract the counterparty of an unknown string length from the same source field

EST/TRX RTE 3.76 USD/LIBOR CPTY:PRU

CPTY: (X~)

PRU

Extract the currency from the same source field using positional matching

PRU EST/TRX RTE 3.76 USD/LIBOR CPTY: PRU

RTE(7-9)

USD

Extract Contract ID from Additional Entry Information

TXT:AR:Receipt Num:CEF-1:For:2010$^USD:Dt.01/01/2011?Receipt Method:CE-Foreign:Receipt Type:Standard:BU:Vision Operations:Customer:World of Business:Account No.1001

Account Number(NNNN)

1001

Extract Transaction ID from Customer Reference

CustRef # A.23@orlc.com

CustRef (X~).com

# A.23@orlc