Presentation

MONETARY DATA FLOW

© 2003 Kanbay Incorporated - All rights reserved

 AGENDA

 What is monetary transaction ? Brief overview.

 Concept of Batches.
 Monetary Data Flow.
 Questions ??
 Feedback.
Monetary Transaction – Brief Overview.
Monetary Transaction
▲ Affect the balance of CMS accounts.
▲ These transactions do not affect the balance until a batch
processing run is completed.

Any transaction that affects an account balance needs a transaction

code and corresponding logic module .
The system uses logic modules to provide the effect of monetary
transactions. (use to identify which all fields needs to be updated
with the transaction specified).
Monetary Transaction – Brief Overview.
There are two types of monetary transactions:
▲ Generated transactions
# created by the system eg. Late or finance charge ,
Membership fee charged etc.
▲ User-assigned transactions
# Generated by the user eg. Payment transaction,
Purchase transaction etc.
Monetary Data Flow

ATTD - User Input.

AMT1 - Online Monetary transaction file.
AMJ1 - Reject Reentry items from online system.
AMXT - Today’s Transfer Transaction.
AMWT - Warehoused transaction.
Concept of Batches
Any monetary transaction enter the CMS system is AMT1RL
format.

The AMT1 file contains 4 different record types as follows :-

▲ FILE HEADER RECORD .
▲ BATCH HEADER RECORDS.
▲ TICKET HEADER RECORDS.
▲ DETAIL TRANSACTIONS RECORDS.
Concept of Batches CONTD……
A group of monetary transaction is called BATCH.
Batch Header record and transaction records consist a single BATCH.
A Batch is defined as a unit of work with following thumb rules
▲ Control Totals indicate the number of items, amount of debits and amount of
credits which should be in the batch.
▲ Calculated Totals reflect the actual number of items, amount of debits, and
amount of credits which are in the batch.
▲ The account numbers on all transactions within a batch must belong to the
same Organization.
▲ The batch must consist of no more than 999 transactions.
 Concept of Batches CONTD……
▲ Each transaction within the batch must have a sequence number. The
sequence numbers must start at 001 for each transaction in the batch
and increment consecutively by 1 for subsequent transaction in the
batch. The number of transaction in the batch must equal the greatest
sequence number assigned in the batch.
▲ The Calculated Total should match the Control Total on the batch
header. If they are matching the then the batch is said to be balanced
and complete otherwise it is referred as incomplete and unbalanced.
Only monetary transactions in balanced batches are passed to
posting. Batches which are not in balance are passed to the Reject
Re-entry for correction and will be delayed from processing
▲ Each Batch entered in the system must be unique.
Concept of Batches CONTD……
The uniqueness of batches in CMS is based on the key structure for
monetary transactions and batches. Each record in a batch, both batch
headers and transactions, has a common key. The key consists of four
fields, which are:
Batch Date: This is the date assigned by Reject Re-entry in the event the batch
rejects. For all other batches entering CMS first time, this date must be equal
to zero. If it is not zero, it will be forced to zero by the system.
Batch Source: This is a 4 digit numeric field. The batch source may not be equal
to 0000 or 9999. These two values are reserved by CMS.
Batch Number: This is an assigned number which indicates the specific batch.
This field is a 5 digit numeric field which must be greater than zero (00001
through 99999 are valid).
 Concept of Batches CONTD……

Sequence Number: This is a 5 digit numeric field which

uniquely identifies each item within the batch.

Batch Number Sequence Number Type of Record

00000 00 000 File Header.

00001-99999 00 000 Batch Header.

00001-99999 00 001-999 Transaction in Non-Ticket Batch.

00001-99999 01-99 000 Ticket Header ( if Ticket Batch ).

00001-99999 01-99 001-999 Transaction record in Ticket Batch.

 Monetary Data Flow
ARD020
AMJ1 AMT1 ATJ1 AMWT ATNS ATVT
AMXT Online Extract ATT1 ATXT

ARD080 ARD100

MONETARY TXN SORT

ATTT MERGE TRANSACTIONS

ATTD Coming
as input to
CMS from
TRAMS ATTD ARU080
ATBB
USER MONETARY ATTI
ATIB
EDIT

ATPT

ATTD Coming ATNS

as input to ATVT
CMS as ATE1
user input AMCP
AMCR
AMMC
AMSD
Monetary Data Flow
ATTD - User Input.
AMT1 - ATT1 - Online Monetary transaction file - extract.
AMJ1 - ATJ1 - Reject Reentry file - extract.
AMXT - ATWT - Today’s Transfer Transaction file - extract.
AMWT- Warehoused transaction.
ATTI - Transaction Input File ( ATTD + ATTT ).
ATBB - Balance Batches
ATIB - Incomplete Batches.
ATNS - New Sales.
ATVT - Variable Transaction.
ATE1 - Rejected Transaction.
ATPT - Posted Transaction.
Monetary Data Flow

AMBI AMBS ATTA1-C ,

ATPT ATGT AMCR AMDI AMWT1-C,
AMOA AMPS ATM1-C
AMRT

ARD180
ARD185 Delete AMWT. ATM1 ARU760
TXN ATTA
UPDATE MULTIPLE REJECT Delete / Define AMXT Merge Segmented
AND BACKUP PROCESSING AMJ1 & AMT1 Temporary Files.

ATTA1-C ATTA
AMWT1-C ATM11-C
AMWT
ATTA1-C
ATST ATM1
AMOS, ABAO
Monetary Data Flow

ATM1
ATE1 , ATTA

ARD190
ARD200
Build AMM1 File
Multiple Reject Build Reject
Transaction Reentry file AMJ1

AMM1 AMJ1
Monetary Data Flow.
Monetary Data Flow.
Monetary Data Flow.

Abhishek Taori.
aztaori@kanbay.com
Extn : 2308