Oracle Enterprise Performance Management Cloud …...1 Overview This guide contains information...

Oracle® CloudOracle Enterprise Performance ManagementCloud Tables and Views for AccountReconciliation

F31282-03

Oracle Cloud Oracle Enterprise Performance Management Cloud Tables and Views for AccountReconciliation,

F31282-03

Copyright © 2020, Oracle and/or its affiliates.

Primary Author: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Governmentend users are "commercial computer software" or “commercial computer software documentation” pursuantto the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Documentation Accessibility

Documentation Feedback

1 Overview

2 Common Tables

FCM_ATTRIBUTES 2-1

FCM_ORG_UNITS 2-7

FCM_SCHEDULER_JOBS 2-9

FCM_TEAMS 2-13

FCM_TEAM_USERS 2-16

FCM_USERS 2-17

3 Reconciliation Compliance Tables and Views

Tables 3-1

ARM_ACCESS 3-2

ARM_ACCOUNT_TYPES 3-4

ARM_ACTION_PLAN 3-5

ARM_AMORTIZATIONS 3-6

ARM_AMORTIZATION_SCHEDULE 3-8

ARM_ANSWERS 3-10

ARM_ATTRIBUTE_VALUES 3-11

ARM_COMMENTS 3-13

ARM_CURRENCY_RATES 3-15

ARM_FORMATS 3-17

ARM_FREQUENCIES 3-19

ARM_HISTORY 3-20

ARM_INSTRUCTIONS 3-22

iii

ARM_PERIODS 3-24

ARM_QUESTIONS 3-25

ARM_QUESTION_LIST_VALUES 3-28

ARM_RATE_TYPES 3-29

ARM_RECONCILIATIONS 3-30

ARM_RECONCILIATION_BUCKETS 3-35

ARM_RECON_ATTRIBUTES_1 3-36

ARM_REFERENCES 3-37

ARM_SUMMARY_AMOUNTS 3-39

ARM_SUMMARY_BALANCES 3-40

ARM_SUMMARY_REC_CHILDREN 3-42

ARM_TRANSACTIONS 3-43

ARM_TRANSACTION_AMOUNTS 3-46

ARM_TRANSACTION_SUMMARIES 3-48

ARM_TRANS_ATTRIBUTES_1 3-50

ARM_WORKFLOW_ACTIONS 3-50

Views 3-52

ARM_BALANCE_DETAIL_SUMMARY (VIEW) 3-52

ARM_BALANCE_SUMMARIES (VIEW) 3-54

4 Transaction Matching Tables

Tables 4-1

TM_ADJUSTMENT 4-1

TM_ATTRIBUTE_VALUE 4-4

TM_BALANCE_SUMMARY 4-6

TM_DATA_SOURCE 4-9

TM_DATA_SOURCE_ATTRIB 4-11

TM_MATCH 4-15

TM_MATCH_PROC 4-17

TM_MATCH_PROC_BKT_ATTRIB_MAP 4-19

TM_MATCH_PROC_DEF_ATTRIB_MAP 4-21

TM_MATCH_RULE 4-26

TM_MATCH_RULE_ADJ_DET 4-29

TM_MATCH_RULE_ADJ_DET_ATTRIB 4-32

TM_MATCH_RULE_COND 4-35

TM_MATCH_TRANS 4-39

iv

5 Transaction Matching Dynamic Tables

TM_TRANS_<DATA_SOURCE_ID> 5-1

v


For information about Oracle's commitment to accessibility, visit theOracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.


vi

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

Documentation Feedback

To provide feedback on this documentation, send email to [email protected],or, in an Oracle Help Center topic, click the Feedback button located beneath theTable of Contents (you may need to scroll down to see the button).

Follow EPM Information Development on these social media sites:

LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051

Twitter - http://twitter.com/hyperionepminfo

Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

YouTube - https://www.youtube.com/oracleepminthecloud

vii

http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051

http://twitter.com/hyperionepminfo

http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

https://www.youtube.com/oracleepminthecloud

1Overview

This guide contains information about tables within Oracle Account Reconciliation andtheir columns, primary keys, indexes, and foreign keys, if applicable. The guide alsoincludes information about views within Oracle Account Reconciliation along with thecolumns and queries associated with each view.

Basic terminology that may be helpful:

• Tables are the basic unit of data storage in Oracle Account Reconciliation, wheredata is stored in rows and columns. For example, the FCM_USERS table is acommon table and stores information about the users such as first name, lastname, time zone preference, user interface skin preference.

Note:

In Transaction Matching, there are also dynamically created tablesthat are created for each datasource once a match type is approvedsuccessfully. See TM_TRANS_<DATA_SOURCE_ID>

• A view is a logical representation of a table or combination of tables. A viewis a stored query that derives its data from the tables on which it is based.For example, the ARM_BALANCE_DETAIL_SUMMARY view is a ReconciliationCompliance view that shows the Source and Sub-system balances that are shownon the Detail Balances list.

How This Guide is Structured

This guide is divided into four sections:

• Common Tables - these tables start with FCM

• Reconciliation Compliance Tables and Views - these tables and views start withARM

• Transaction Matching Tables - these tables start with TM

• Transaction Matching Dynamically Created Tables - these tables start withTM_TRANS

1-1

2Common Tables

Related Topics

• FCM_ATTRIBUTES

• FCM_ORG_UNITS

• FCM_SCHEDULER_JOBS

• FCM_TEAMS

• FCM_TEAM_USERS

• FCM_USERS

FCM_ATTRIBUTESThis table stores the custom attributes defined by the administrator.

Details

• Schema: PBCS_REG

• Object owner: FCM

• Object type: TABLE

• Tablespace: DEFAULT

Primary Key

Name Columns

FCM_ATTRIBUTES_PK ATTRIBUTE_ID

Columns

Name Data Type Length Precision Scale NullAllowed

Comments

ATTRIBUTE_ID NUMBER 18 0 No Unique ID

APP_ID NUMBER 1 0 No TheApplicationID

DELETED VARCHAR2

1 No Y=YesN=No

ATTRIBUTE_NAME

VARCHAR2

765 No Attributedisplayname

2-1


Comments

ATTRIBUTE_TYPE

VARCHAR2

25 No Possiblevalues areBOOLEAN,DATE,NUMBER,LIST,TEXT.

ORDER_SEQ NUMBER 0 Yes The orderof theattributesin accountsegmentsandcomponentsegments.

USED_FOR VARCHAR2

10 No Denoteswhich viewtype anattribute isused forUser,AccountSegmentorSegments.Possiblevalues areUSER,ACCTSEG,SEGMENTorSYSTEM.

NEGATIVE_NUMBER_FORMAT

VARCHAR2

15 Yes If theCustomAttribute isNUMBERtype, this isthe displayformat tobe used fornegativenumbers.

SCALE VARCHAR2

15 Yes If theCustomAttribute isNUMBERtype, this isthe SCALEfor thedisplayformat.

Chapter 2FCM_ATTRIBUTES

2-2


Comments

THOUSANDS_SEPARATOR_FLAG

VARCHAR2

1 Yes If theCustomAttribute isNUMBERtype, this isthecharacterto be usedforthousandsseparator

DECIMAL_PLACES

NUMBER 2 0 Yes If theCustomAttribute isNUMBERtype, this isthe # ofdecimalplacesused forthe displayformat.

CURRENCY_SYMBOL

VARCHAR2

255 Yes If theCustomAttribute isNUMBERtype, this isthecurrencysymbolused forthe displayformat.

PERCENTAGE VARCHAR2

1 No Denoteswhetherattribute isto bedisplayedas apercentage.

TEXT_LINES NUMBER 0 Yes Number oflines for amulti-linetextattribute.

INCLUDE_ATTACHMENTS

VARCHAR2

1 No Y=Yes toincludeattachments (usedonly formulti-linetextattributes).


2-3


Comments

IS_CALCULATION

VARCHAR2

1 Yes Y=Yes,N=No toindicatewhethertheattribute isacalculation

CALCULATION_ID

NUMBER 18 0 Yes The ID ofthecalculationinFCM_CALCULATIONS table.

ATTRIBUTE_SOURCE

VARCHAR2

30 Yes The sourceof thecalculation,forinstance, Rforreconciliation, T fortransaction.

DISPLAY_TO_USER

VARCHAR2

1 Yes Y=Yes,N=No toindicatewhethertheattributeshould bedisplayedto user ofhidden.


2-4


Comments

OBJECT_VERSION_NUMBER

NUMBER No Used toimplementoptimisticlocking.Thisnumber isincremented everytime therow isupdated.Thenumber iscomparedat the startand end ofatransactionto detectwhetheranothersessionhasupdatedthe rowsince itwasqueried.

LAST_UPDATE_LOGIN

NUMBER Yes Whocolumn.Stores theID of theuser wholastupdatedthis row.

LAST_UPDATE_DATE

DATE No Whocolumn.Stores thedate whenthis rowwas lastupdated.

LAST_UPDATED_BY

VARCHAR2

255 No Whocolumn.Stores theID of theuser wholastupdatedthis row.


2-5


Comments

CREATION_DATE DATE No Whocolumn.Stores thedate whenthis rowwascreated inthedatabase.

CREATED_BY VARCHAR2

255 No Whocolumn.Stores theID of theuser whocreatedthis row.

SUB_SEGMENT VARCHAR2

1 Yes Whethertheattribute isa subsegmentprofilesegment.

TARGET_DIM VARCHAR2

5 Yes The targetdimensionin DM

HAS_DND_ACCESS

VARCHAR2

1 Yes Whetherattribute isused in DoNot Displayaccess.

TOTALING_METHOD

VARCHAR2

20 Yes Thetotalingmethod oftheattribute, ifnumeric

RECON_DASHBOARD_TABLE

VARCHAR2

32 Yes The tablename oftheattributewherereconciliation valuesare stored,forinstanceARM_RECON_ATTRIBUTES_1.


2-6


Comments

TRANS_DASHBOARD_TABLE

VARCHAR2

32 Yes The tablename oftheattributewheretransactionvalues arestored, forinstanceARM_TRANS_ATTRIBUTES_1.

DASHBOARD_COLUMN

VARCHAR2

32 Yes Thecolumnname inthe recon/transactiontable fortheattribute

Indexes

Index Uniqueness Columns

FCM_ATTRIBUTES_N1 NONUNIQUE APP_ID, USED_FOR

FCM_ATTRIBUTES_PK UNIQUE ATTRIBUTE_ID

FCM_ORG_UNITSThis table stores the organizational unit information.

Details





Primary Key

Name Columns

FCM_ORG_UNITS_PK ORG_ID

Chapter 2FCM_ORG_UNITS

2-7

Columns

Name Data Type Length

Precision

Scale NullAllowed

Comments

ORG_ID NUMBER 18 0 No Organization Unit ID(Unique key)

ORG_NAME VARCHAR2

255 No Organization UnitName

PARENT_ORG_ID

NUMBER 18 0 Yes Parent OrganizationUnit ID

DESCRIPTION VARCHAR2

4000 Yes Description

HOLIDAY_RULE_ID

NUMBER 18 0 Yes Holiday rule ID

ARM_CALENDAR_ID

NUMBER 18 0 Yes ARM calendar ID

ARM_WORK_DAYS

VARCHAR2

30 Yes Stores string offormat 1-2-3-4-5-6-7for workdays. 1-Sunday and 7 -Saturday.

ORDER_SEQ NUMBER 3 0 Yes The relative order

ORG_CODE VARCHAR2

255 No The org unit uniquecode

DELETED VARCHAR2

1 Yes Whether the org unithas been logicallydeleted.


NUMBER 9 0 No Used to implementoptimistic locking.This number isincremented everytime the row isupdated. The numberis compared atthe start and endof a transactionto detect whetheranother session hasupdated the row sinceit was queried.

LAST_UPDATE_LOGIN

NUMBER Yes Who column. Storesthe login/session IDof the user who lastupdated this row.

LAST_UPDATED_BY

VARCHAR2

255 No Who column. Storesthe ID of the user wholast updated this row.

LAST_UPDATE_DATE

DATE No Who column. Storesthe date when this rowwas last updated.

Chapter 2FCM_ORG_UNITS

2-8


Precision

Scale NullAllowed

Comments

CREATED_BY VARCHAR2

255 No Who column. Storesthe ID of the user whocreated this row.

CREATION_DATE DATE No Who column. Storesthe date when thisrow was created in thedatabase.

Indexes


FCM_ORG_UNITS_N1 NONUNIQUE PARENT_ORG_ID

FCM_ORG_UNITS_PK UNIQUE ORG_ID

FCM_SCHEDULER_JOBSThis table stores the jobs being run by the scheduler.

Details





Primary Key

Name Columns

FCM_SCHEDULER_JOBS_PK JOB_ID

Columns


Comments

JOB_ID NUMBER 18 0 No Job ID,primarykey

APP_ID NUMBER 3 0 No ApplicationID

JOB_CODE VARCHAR2

60 No Theinternalcode of thejob

JOB_NAME VARCHAR2

256 No The jobname

Chapter 2FCM_SCHEDULER_JOBS

2-9


Comments

SERVER VARCHAR2

256 Yes The servername thejob isscheduledto runagainst

START_DATE DATE No Thescheduledstart dateof the job

RECURRING VARCHAR2

1 No Whetherthe job isrecurringor not

INTERVAL NUMBER Yes For arecurringjob, theintervalbetweenexecutions

CLASS_NAME VARCHAR2

255 No The classname tocall

METHOD VARCHAR2

255 No Themethodname tocall

STATUS_ID NUMBER 3 0 No The statusof the job:32=pending,6=running,1=closed,#=error

MESSAGE VARCHAR2

4000 Yes Anymessagespassed onby the job

ACTUAL_START_DATE

DATE Yes The actualstart dateof the job

ACTUAL_END_DATE

DATE Yes The actualend date ofthe job


2-10


Comments


NUMBER 9 0 No Used toimplementoptimisticlocking.Thisnumber isincremented everytime thatthe row isupdated.Thenumber iscomparedat the startand end ofatransactionto detectwhetheranothersessionhasupdatedthe rowsince itwasqueried.

LAST_UPDATE_LOGIN

NUMBER Yes Whocolumn.Stores theID of theuser wholastupdatedthis row.

LAST_UPDATED_BY

VARCHAR2

255 No Whocolumn.Stores theID of theuser wholastupdatedthis row.

LAST_UPDATE_DATE

DATE No Whocolumn.Stores thedate whenthis rowwas lastupdated.


2-11


Comments

CREATED_BY VARCHAR2

255 No Whocolumn.Stores theID of theuser whocreatedthis row.

CREATION_DATE DATE No Whocolumn.Stores thedate whenthis rowwascreated inthedatabase.

APP_KEY VARCHAR2

100 Yes Theapplicationkey of thejob

NAME_TOKENS VARCHAR2

1000 Yes The nametokens, ifany, fortranslatingthe jobname

CREATOR_USER_ROLE

NUMBER 9 0 Yes The userrole of thecreator ofthe job

USER_CREATED VARCHAR2

1 No Whetherthe job wassubmittedby a useror asystem job

RESULTS_TASK_FLOW

VARCHAR2

255 Yes The taskflow of theresults ofthe dialog

RESULTS CLOB Yes The resultsof the job

PERCENT_COMPLETE

NUMBER 3 0 Yes Percentcompleteof the job,if the jobsupports it

PARAMETERS CLOB Yes Theparametersof the job


2-12

Indexes


FCM_SCHEDULER_JOBS_N1

NONUNIQUE APP_ID, STATUS_ID

FCM_SCHEDULER_JOBS_N2

NONUNIQUE APP_ID, JOB_CODE,STATUS_ID

FCM_SCHEDULER_JOBS_PK

UNIQUE JOB_ID

FCM_TEAMSThis table stores the team information.

Details





Primary Key

Name Columns

FCM_TEAMS_PK TEAM_ID

Columns


Comments

TEAM_ID VARCHAR2

38 No Team ID,PrimaryKey

TEAM_NAME VARCHAR2

80 No Name ofteam

TEAM_DESCRIPTION

VARCHAR2

255 Yes Descriptionof team

HAS_PREPARER VARCHAR2

1 Yes Flagindicatingteam haspreparerrole

HAS_REVIEWER VARCHAR2

1 Yes Flagindicatingteam hasreviewerrole

Chapter 2FCM_TEAMS

2-13


Comments

HAS_VIEWER VARCHAR2

1 Yes Flagindicatingteam hasviewer role

HAS_COMMENTATOR

VARCHAR2

1 Yes Flagindicatingteam hascommentator role

PRIMARY_USER_ID

VARCHAR2

255 Yes The userID of theprimaryuser of theteam

DELETED VARCHAR2

1 Yes Whetherthe teamhas beenlogicallydeleted


NUMBER 9 0 Yes Used toimplementoptimisticlocking.Thisnumber isincremented everytime thatthe row isupdated.Thenumber iscomparedat the startand end ofatransactionto detectwhetheranothersessionhasupdatedthe rowsince itwasqueried.

Chapter 2FCM_TEAMS

2-14


Comments

LAST_UPDATE_LOGIN

NUMBER Yes Whocolumn.Stores thelogin/session IDof the userwho lastupdatedthis row.

LAST_UPDATED_BY

VARCHAR2

255 Yes Whocolumn.Stores theID of theuser wholastupdatedthis row.

LAST_UPDATE_DATE

DATE Yes Whocolumn.Stores thedate whenthis rowwas lastupdated.

CREATED_BY VARCHAR2

255 Yes Whocolumn.Stores theID of theuser whocreatedthis row.

CREATION_DATE DATE Yes Whocolumn.Stores thedate whenthis rowwascreated inthedatabase.

HAS_SDM_USER VARCHAR2

1 Yes Flagindicatingteam hasSDM Userrole

HAS_TSS_USER VARCHAR2

1 Yes Flagindicatingteam hasTSS Userrole

Chapter 2FCM_TEAMS

2-15


Comments

HAS_FCC_VIEWER

VARCHAR2

1 Yes Flagindicatingteam hasCM viewerrole

Indexes


FCM_TEAMS_PK UNIQUE TEAM_ID

FCM_TEAM_USERSThis table stores the team user membership.

Details





Primary Key

Name Columns

FCM_TEAM_USERS_PK TEAM_ID

FCM_TEAM_USERS_PK USER_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

TEAM_ID VARCHAR2

255 No Team ID, Primary Key

USER_ID VARCHAR2

255 No User ID, Primary Key

LAST_UPDATE_LOGIN

NUMBER

Yes Who column. Stores thelogin/session ID of the userwho last updated this row.

LAST_UPDATED_BY

VARCHAR2

255 Yes Who column. Stores theID of the user who lastupdated this row.

LAST_UPDATED_DATE

DATE Yes Who column. Stores thedate when this row was lastupdated.

Chapter 2FCM_TEAM_USERS

2-16

Name DataType

Length

Precision

Scale NullAllowed

Comments

CREATED_BY VARCHAR2

255 Yes Who column. Stores the IDof the user who created thisrow.

CREATION_DATE

DATE Yes Who column. Stores thedate when this row wascreated in the database.


NUMBER

9 0 Yes Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whether anothersession has updated therow since it was queried.

Indexes


FCM_TEAM_USERS_N1 NONUNIQUE TEAM_ID

FCM_TEAM_USERS_PK UNIQUE TEAM_ID, USER_ID

FCM_USER_TEAMS_N1 NONUNIQUE USER_ID

FCM_USERSThis table stores user information.

Details





Primary Key

Name Columns

FCM_USERS_PK USER_ID

Chapter 2FCM_USERS

2-17

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

FIRST_NAME VARCHAR2

300 Yes First name of user

LAST_NAME VARCHAR2

300 Yes Last name of user

EXTERNAL_USER

VARCHAR2

1 Yes Whether user is external

USER_TIMEZONE

VARCHAR2

255 Yes User''s time zone preference

USER_SKIN VARCHAR2

255 Yes User''s skin preference

USER_AVATAR BLOB Yes User''s avatar image


NUMBER 9 0 Yes Used to implement optimisticlocking. This number isincremented every time thatthe row is updated. Thenumber is compared atthe start and end of atransaction to detect whetheranother session has updatedthe row since it was queried.

LAST_UPDATE_LOGIN

NUMBER Yes Who column. Stores thelogin/session ID of the userwho last updated this row.

LAST_UPDATED_BY

VARCHAR2

255 Yes Who column. Stores the IDof the user who last updatedthis row.

LAST_UPDATE_DATE

DATE Yes Who column. Stores thedate when this row was lastupdated.

CREATED_BY VARCHAR2

255 Yes Who column. Stores the IDof the user who created thisrow.

CREATION_DATE

DATE Yes Who column. Stores the datewhen this row was created inthe database.

Indexes


FCM_USERS_PK UNIQUE USER_ID

Chapter 2FCM_USERS

2-18

3Reconciliation Compliance Tables andViews

Related Topics

• Tables

• Views

TablesRelated Topics

• ARM_ACCESS

• ARM_ACCOUNT_TYPES

• ARM_ACTION_PLAN

• ARM_AMORTIZATIONS

• ARM_AMORTIZATION_SCHEDULE

• ARM_ANSWERS

• ARM_ATTRIBUTE_VALUES

• ARM_COMMENTS

• ARM_CURRENCY_RATES

• ARM_FORMATS

• ARM_FREQUENCIES

• ARM_HISTORY

• ARM_INSTRUCTIONS

• ARM_PERIODS

• ARM_QUESTIONS

• ARM_QUESTION_LIST_VALUES

• ARM_RATE_TYPES

• ARM_RECONCILIATIONS

• ARM_RECONCILIATION_BUCKETS

• ARM_RECON_ATTRIBUTES_1

• ARM_REFERENCES

• ARM_SUMMARY_AMOUNTS

• ARM_SUMMARY_BALANCES

• ARM_SUMMARY_REC_CHILDREN

3-1

• ARM_TRANSACTIONS

• ARM_TRANSACTION_AMOUNTS

• ARM_TRANSACTION_SUMMARIES

• ARM_TRANS_ATTRIBUTES_1

• ARM_WORKFLOW_ACTIONS

ARM_ACCESSThis table stores the access of users and groups to objects inside accountreconciliation.

Details


• Object owner: ARM



Primary Key

Name Columns

ARM_ACCESS_PK ACCESS_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

ACCESS_ID NUMBER

18 0 No Unique ID, Primary Key

OBJECT_ID NUMBER

18 0 No The object this access is beingassociated with

USER_TYPE VARCHAR2

1 Yes The user type: G=group, U=user,T=team

USER_ID VARCHAR2

255 Yes The user or group ID

ACCESS_TYPE VARCHAR2

2 No The Access type: V=Viewer,P=Preparer, R=Reviewer,C=Commentator

ACCESS_ORDER

NUMBER

3 0 Yes The relative order. Applicable toreviewers

FREQUENCY_ID

NUMBER

18 0 Yes The Frequency ID, when the object isa Profile.

START_DATE DATE Yes The start date of the preparer orreviewer for reconciliation instances.

START_OFFSET NUMBER

9 0 Yes The start offset of the preparer orreviewer for profiles.

Chapter 3Tables

3-2

Name DataType

Length

Precision

Scale

NullAllowed

Comments

END_OFFSET NUMBER

9 0 Yes The end offset of the preparer orreviewer for profiles.

END_DATE DATE Yes The end date for preparer or reviewerof instances.

DURATION NUMBER

9 0 Yes The duration of the preparer orreviewer for profiles.

EVER_BEEN_LATE

VARCHAR2

1 Yes Whether this user has ever been lateperforming their role at any point.

REJECTS NUMBER

9 0 Yes The number of rejects

REQUIRE_ALL VARCHAR2

1 Yes Whether the team assignmentrequires all users to sign off or justone.


NUMBER

9 0 No Used to implement optimistic locking.This number is incremented everytime that the row is updated. Thenumber is compared at the start andend of a transaction to detect whetheranother session has updated the rowsince it was queried.

LAST_UPDATE_LOGIN

NUMBER

Yes Who column. Stores the login/sessionID of the user who last updated thisrow.

LAST_UPDATED_BY

VARCHAR2

255 No Who column. Stores the ID of the userwho last updated this row.

LAST_UPDATE_DATE

DATE No Who column. Stores the date whenthis row was last updated.

CREATED_BY VARCHAR2

255 No Who column. Stores the ID of the userwho created this row.

CREATION_DATE

DATE No Who column. Stores the date whenthis row was created in the database.

BACKUP_USER_ID

VARCHAR2

255 Yes ID of backup user

ACTIVE_USER_ID

VARCHAR2

255 Yes ID of user that is currently assigned

ACTUAL_END_DATE

DATE Yes Actual date of completion ofassignment.

Indexes


ARM_ACCESS_N1 NONUNIQUE USER_ID

ARM_ACCESS_N2 NONUNIQUE OBJECT_ID, ACCESS_TYPE, USER_ID

ARM_ACCESS_N3 NONUNIQUE OBJECT_ID, ACCESS_TYPE,ACCESS_ORDER

ARM_ACCESS_N4 NONUNIQUE OBJECT_ID, ACCESS_ORDER

Chapter 3Tables

3-3


ARM_ACCESS_N5 NONUNIQUE ACTIVE_USER_ID

ARM_ACCESS_N6 NONUNIQUE BACKUP_USER_ID

ARM_ACCESS_PK UNIQUE ACCESS_ID

ARM_ACCOUNT_TYPESThis table stores the Account Types.

Details





Primary Key

Name Columns

ARM_ACCOUNT_TYPES_PK ACCOUNT_TYPE_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

ACCOUNT_TYPE_ID

NUMBER

18 0 No Unique account type ID, primary key.

ACCOUNT_TYPE_ORDER

NUMBER

No Relative order of the account types

ACCOUNT_TYPE_NAME

VARCHAR2

765 No Unique account type name.

PARENT_TYPE_ID

NUMBER

18 0 Yes Parent Account Type ID.


NUMBER

No Used to implement optimistic locking.This number is incremented everytime that the row is updated. Thenumber is compared at the start andend of a transaction to detect whetheranother session has updated the rowsince it was queried.

LAST_UPDATE_LOGIN

NUMBER

Yes Who column. Stores the login/sessionID of the user who last updated thisrow.

LAST_UPDATED_BY

VARCHAR2

255 No Who column. Stores the ID of the userwho last updated this row.

LAST_UPDATE_DATE


Chapter 3Tables

3-4

Name DataType

Length

Precision

Scale

NullAllowed

Comments

CREATED_BY VARCHAR2

255 No Who column. Stores the ID of the userwho created this row.

CREATION_DATE


Indexes


ARM_ACCOUNT_TYPES_PK

UNIQUE ACCOUNT_TYPE_ID

ARM_ACTION_PLANThis table stores the Action Plans.

Details





Primary Key

Name Columns

ARM_ACTION_PLAN_PK ACTION_PLAN_ID

Columns


Precision

Scale NullAllowed

Comments

ACTION_PLAN_ID

NUMBER 18 0 No Unique ID, Primary Key

OBJECT_ID NUMBER 18 0 Yes The object this access isbeing associated with

ACTION_PLAN_NAME

VARCHAR2

4000 Yes Action Plan Details

CLOSE_DATE DATE Yes Action Plan Close Date

CLOSED VARCHAR2

1 Yes Whether action plan isclosed or open

Chapter 3Tables

3-5


Precision

Scale NullAllowed

Comments


NUMBER No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whether anothersession has updated therow since it was queried.

LAST_UPDATE_LOGIN

NUMBER Yes Who column. Stores thelogin/session ID of theuser who last updatedthis row.

LAST_UPDATED_BY

VARCHAR2

255 No Who column. Stores theID of the user who lastupdated this row.

LAST_UPDATE_DATE

DATE No Who column. Stores thedate when this row waslast updated.

CREATED_BY VARCHAR2

255 No Who column. Stores theID of the user whocreated this row.

CREATION_DATE DATE No Who column. Stores thedate when this row wascreated in the database.

PRIOR_ACTION_PLAN_ID

NUMBER 18 0 Yes ID of prior actionplan, for copied-forwardtransactions

Indexes


ARM_ACTION_PLAN_PK

UNIQUE ACTION_PLAN_ID

ARM_ACTION_PLAN_U1

UNIQUE OBJECT_ID

ARM_AMORTIZATIONSThis table stores the amortization information for transactions.

Details




Chapter 3Tables

3-6


Primary Key

Name Columns

ARM_AMORTIZATIONS_PK TRANSACTION_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

TRANSACTION_ID NUMBER

18 0 No Foreign key toARM_TRANSACTIONS

METHOD VARCHAR2

1 No A=Actual, S=Straight-line or C=custom

START_PERIOD NUMBER

18 0 Yes Starting period forStraight-line or Custom

NUM_PERIODS NUMBER

Yes Number of periods forthe amortization

ORIGINAL_AMOUNT_BUCKET1

NUMBER

29 12 Yes Original amount enteredby the user in bucket 1


NUMBER



NUMBER


START_DATE DATE Yes Start date used for theActual method

END_DATE DATE Yes End date used for theActual method

HALF_MONTH_CONVENTION

VARCHAR2

1 No Y for using half-monthconvention


NUMBER

9 0 No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whetheranother session hasupdated the row since itwas queried.

LAST_UPDATE_LOGIN

NUMBER

Yes Who column. Stores thelogin/session ID of theuser who last updatedthis row.

LAST_UPDATED_BY VARCHAR2


Chapter 3Tables

3-7

Name DataType

Length

Precision

Scale NullAllowed

Comments

LAST_UPDATE_DATE DATE No Who column. Stores thedate when this row waslast updated.

CREATED_BY VARCHAR2



Indexes


ARM_AMORTIZATIONS_PK

UNIQUE TRANSACTION_ID

ARM_AMORTIZATION_SCHEDULEThis table stores the amortization schedule for transactions.

Details





Primary Key

Name Columns

ARM_AMORTIZATION_SCHEDULE_PK AMORT_SCHEDULE_ENTRY_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

AMORT_SCHEDULE_ENTRY_ID

NUMBER

18 0 No Unique key

TRANSACTION_ID NUMBER

18 0 No Foreign key toARM_AMORTIZATIONSandARM_TRANSACTIONS

Chapter 3Tables

3-8

Name DataType

Length

Precision

Scale NullAllowed

Comments

CURRENCY_BUCKET_ID

NUMBER

18 0 No Currency Bucket ID, FKtoARM_CURRENCY_BUCKETS

CURRENCY VARCHAR2

80 No Currency of theamortization

PERIOD_NUM NUMBER

No Number identifying theperiod (1-based)

AMOUNT NUMBER

29 12 No Amount of amortization


NUMBER


LAST_UPDATE_LOGIN

NUMBER





CREATED_BY VARCHAR2



PERIOD_ID NUMBER

18 0 Yes Period of theamortization

Indexes


ARM_AMORTIZATION_SCHEDULE_PK

UNIQUE AMORT_SCHEDULE_ENTRY_ID

ARM_AMORTIZATION_SCHEDULE_UK

UNIQUE TRANSACTION_ID, PERIOD_NUM,CURRENCY_BUCKET_ID

Chapter 3Tables

3-9

ARM_ANSWERSThis table stores the answers for the questions.

Details





Primary Key

Name Columns

ARM_ANSWERS_PK ANSWER_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

ANSWER_ID NUMBER

18 0 No Unique ID

QUESTION_ID NUMBER

18 0 No Question that isanswered

OBJECT_ID NUMBER

18 0 No Object this question/answer applies

VALUE_TEXT VARCHAR2

4000 Yes Text value(used for TEXT,MULTILINE_TEXT andBOOLEAN types)

VALUE_DATE DATE Yes Date value (used forDATE and DATETIMEtypes)

VALUE_NUMBER NUMBER

Yes Number type (used forNUMBER type)

VALUE_CHOICE_LIST_ID

NUMBER

18 0 Yes Used for the case wherethe user chooses listvalue


NUMBER


Chapter 3Tables

3-10

Name DataType

Length

Precision

Scale NullAllowed

Comments

LAST_UPDATE_LOGIN

NUMBER






CREATED_BY VARCHAR2


Indexes


ARM_ANSWERS_N1 NONUNIQUE OBJECT_ID

ARM_ANSWERS_PK UNIQUE ANSWER_ID

ARM_ANSWERS_U1 NONUNIQUE OBJECT_ID, QUESTION_ID

ARM_ATTRIBUTE_VALUESThis table stores the relationship between an object and the attributes that areassigned to it including the value that the user assigned to the attribute.

Details





Primary Key

Name Columns

ARM_ATTRIBUTE_VALUES_PK ATTRIBUTE_VALUE_ID

Chapter 3Tables

3-11

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

ATTRIBUTE_VALUE_ID

NUMBER

18 0 No Unique identifier

ATTRIBUTE_ID NUMBER

18 0 No Foreign Key toARM_ATTRIBUTES

OBJECT_ID NUMBER

18 0 No The ID of the objectthis attribute value isassociated with

ORDER_SEQ NUMBER

9 0 Yes The order of theattribute with respectto the other attributesapplied to the sameobject.

REQUIRED VARCHAR2

1 Yes Flag to indicate ifthe attribute value isrequired or not. Possiblevalues are Y/N.

UPDATABLE_BY VARCHAR2

1 Yes Flag to indicate whocan update the attributevalue. P=Preparer, R=Reviewer, B= BothPreparer and Reviewer,N=None. If null, itmeans None.

VALUE_TEXT VARCHAR2

4000 Yes Only used if the typeof attribute is TEXT orBOOLEAN

VALUE_NUMBER NUMBER

Yes Only used if the type ofattribute is NUMBER

VALUE_DATE DATE Yes Only used if the type ofattribute is DATE

VALUE_LIST_CHOICE_ID

NUMBER

18 0 Yes Only used if the type ofattribute is LIST

HISTORY_ATTRIBUTE_TYPE

VARCHAR2

3 Yes The attribute type, usedby history to determinehow to handle changes


NUMBER

No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whetheranother session hasupdated the row since itwas queried.

Chapter 3Tables

3-12

Name DataType

Length

Precision

Scale NullAllowed

Comments

LAST_UPDATE_LOGIN

NUMBER






CREATED_BY VARCHAR2


FDMEE_UDX_NAME VARCHAR2

5 Yes Name of attribute inFDMEE

COPY_TO_PROFILE VARCHAR2

1 Yes Whether the attributeshould be copied to theprofile on submission

PRIOR_ATTRIBUTE_VALUE_ID

NUMBER

18 0 Yes Prior attribute valueID, for copied-forwardtransactions

Indexes


ARM_ATTRIBUTE_VALUES_N1

NONUNIQUE OBJECT_ID

ARM_ATTRIBUTE_VALUES_N2

NONUNIQUE ATTRIBUTE_ID, HISTORY_ATTRIBUTE_TYPE

ARM_ATTRIBUTE_VALUES_PK

UNIQUE ATTRIBUTE_VALUE_ID

ARM_ATTRIBUTE_VALUES_U1

UNIQUE ATTRIBUTE_ID, OBJECT_ID

ARM_ATTRIBUTE_VALUES_U2

UNIQUE OBJECT_ID, ATTRIBUTE_ID

ARM_COMMENTSThis table stores the relation between the object and the text record that stores thecomment.

Details


Chapter 3Tables

3-13




Primary Key

Name Columns

ARM_COMMENTS_PK COMMENT_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

COMMENT_ID NUMBER

18 0 No Unique identifier

OBJECT_ID NUMBER

18 0 Yes ID of the object theComment is tied to.Currently restricted toprofile instances only.

COMMENT_TEXT CLOB Yes The text of thecomment.

CREATOR_ID VARCHAR2

255 No The user ID of theperson who created this.

USER_CREATION_DATE

DATE No Date when thiscomment was created.


NUMBER


LAST_UPDATE_LOGIN

NUMBER






Chapter 3Tables

3-14

Name DataType

Length

Precision

Scale NullAllowed

Comments

CREATED_BY VARCHAR2


CREATOR_ROLE VARCHAR2

3 Yes The ownerrole: P=Preparer,R=Reviewer,C=Commentator,V=Viewer

PRIOR_COMMENT_ID NUMBER

18 0 Yes Prior comment IDfor copied-forwardtransactions.

Indexes


ARM_COMMENTS_N1

NONUNIQUE OBJECT_ID

ARM_COMMENTS_PK

UNIQUE COMMENT_ID

ARM_CURRENCY_RATESThis table stores the currency conversion rates.

Details





Primary Key

Name Columns

ARM_CURRENCY_RATES_PK FROM_CURRENCY

ARM_CURRENCY_RATES_PK TO_CURRENCY

ARM_CURRENCY_RATES_PK PERIOD_ID

ARM_CURRENCY_RATES_PK RATE_TYPE_ID

Chapter 3Tables

3-15

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

FROM_CURRENCY VARCHAR2

80 No From currency

TO_CURRENCY VARCHAR2

80 No To currency

PERIOD_ID NUMBER

18 0 No Period ID for the Periodmapping.

RATE_TYPE_ID NUMBER

18 0 No Rate Type ID forthe ARM RATE TYPEmapping

RATE NUMBER

No Currency ConversionRate




LAST_UPDATE_LOGIN

NUMBER


CREATED_BY VARCHAR2




NUMBER


FROM_SOURCE_SYSTEM

VARCHAR2

1 Yes Whether rates wereloaded from the sourcesystem.

Chapter 3Tables

3-16

Indexes


ARM_CURRENCY_RATES_N1

NONUNIQUE PERIOD_ID

ARM_CURRENCY_RATES_PK

UNIQUE FROM_CURRENCY, TO_CURRENCY,PERIOD_ID, RATE_TYPE_ID

ARM_CURRENCY_RATES_UI

UNIQUE PERIOD_ID, RATE_TYPE_ID,FROM_CURRENCY, TO_CURRENCY

ARM_FORMATSThis table stores the formats.

Details





Primary Key

Name Columns

ARM_FORMATS_PK FORMAT_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

FORMAT_ID NUMBER

18 0 No Unique ID

SOURCE_FORMAT_ID NUMBER

18 0 Yes Source Format ID. Only setfor format snapshots used byinstances.

FORMAT_NAME VARCHAR2

765 No The format name

FORMAT_DESCRIPTION

VARCHAR2

4000

Yes The format description

RECONCILIATION_METHOD

VARCHAR2

1 No The reconciliation methodfor this format: A=AccountAnalysis and B=BalanceComparison.

ZERO_UNEXPLAINED_DIFF_REQUIRED

VARCHAR2

1 Yes The flag to indicate whether0 unexplained difference ismandatory or not. Possiblevalues Y=Yes or N=No.

Chapter 3Tables

3-17

Name DataType

Length

Precision

Scale

NullAllowed

Comments


NUMBER

9 0 No Used to implement optimisticlocking. This number isincremented every time therow is updated. The numberis compared at the start andend of a transaction to detectwhether another session hasupdated the row since it wasqueried.

LAST_UPDATE_LOGIN

NUMBER

Yes Who column. Stores the login/session ID of the user who lastupdated this row.

LAST_UPDATE_DATE DATE No Who column. Stores the datewhen this row was lastupdated.


255 No Who column. Stores the ID ofthe user who last updated thisrow.

CREATION_DATE DATE No Who column. Stores the datewhen this row was created inthe database.

CREATED_BY VARCHAR2

255 No Who column. Stores the ID ofthe user who created this row.

DISPLAY_ACCOUNT_ID_AS

VARCHAR2

1 Yes Whether to display the accountID as individual segments (''S'')or one concatenated string(''C'')

SHOW_ACTION_PLAN_BEX

VARCHAR2

1 Yes Whether to show the actionplan for balance explanations

SHOW_ACTION_PLAN_SRC

VARCHAR2

1 Yes Whether to show the actionplan for source systemtransactions

SHOW_ACTION_PLAN_SUB

VARCHAR2

1 Yes Whether to show theaction plan for subsystemtransactions

VARIANCE_PERIOD_FREQUENCY_ID

NUMBER

18 0 Yes The frequency of the varianceperiod

SHOW_ACTION_PLAN_VEX

VARCHAR2

1 Yes Whether to show the actionplan for variance explanations

MATCH_TYPE_ID NUMBER

18 0 Yes The TM match type ID

SUBSEGMENT_DETAIL

VARCHAR2

1 Yes Whether to enable subsegment details fortransactions

DISABLE_AMORT_BEX

VARCHAR2

1 Yes Whether to disableamortizations for the BalanceExplanation (BEX).

Chapter 3Tables

3-18

Name DataType

Length

Precision

Scale

NullAllowed

Comments

DISABLE_AMORT_SRC

VARCHAR2

1 Yes Whether to disableamortizations for the SourceSystem (SRC).

DISABLE_AMORT_SUB

VARCHAR2

1 Yes Whether to disableamortizations for the SubSystem (SUB) transactions.

Indexes


ARM_FORMATS_N1 NONUNIQUE SOURCE_FORMAT_ID

ARM_FORMATS_PK UNIQUE FORMAT_ID

ARM_FREQUENCIESThis table stores the frequencies defined by the user.

Details





Primary Key

Name Columns

ARM_FREQUENCIES_PK FREQUENCY_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

FREQUENCY_ID NUMBER

18 0 No The unique ID of thefrequency

FREQUENCY_NAME VARCHAR2

180 No The name of thefrequency

FREQUENCY_ORDER NUMBER

18 0 Yes Order of frequency

Chapter 3Tables

3-19

Name DataType

Length

Precision

Scale NullAllowed

Comments


NUMBER


LAST_UPDATE_LOGIN

NUMBER





CREATED_BY VARCHAR2



Indexes


ARM_FREQUENCIES_PK

UNIQUE FREQUENCY_ID

ARM_HISTORYThis table stores the history of a task, template, schedule, or task type.

Details





Chapter 3Tables

3-20

Primary Key

Name Columns

ARM_HISTORY_PK HISTORY_FIELD_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

HISTORY_FIELD_ID NUMBER

18 0 No The history field uniqueidentifier

OBJECT_ID NUMBER

18 0 No The object ID of thishistory entry

OBJECT_TYPE VARCHAR2

8 Yes The object type of thishistory entry

OBJECT_NAME VARCHAR2

256 Yes The object name of thishistory entry

SUPPORTING_OBJECT_ID

NUMBER

18 0 Yes An ID to the objectreferenced by thisentry. For instance, theAttribute ID for thechange in an attributevalue

SUPPORTING_OBJECT

VARCHAR2

765 Yes A supporting objectfield. A general use fieldin case the other fieldsare not enough to storethe history

FIELD_ID NUMBER

9 0 No The field ID whichstates what field (suchas task name, startdate, end date, etc.)changed. Refer toHistoryManager.java forthe full enumeration

CHANGE_TYPE_ID NUMBER

9 0 No The ID of thechange type, suchas Added, Removed,and Modified. Refer toHistoryManager.java forthe full enumeration.

OLD_VALUE VARCHAR2

4000 Yes The prior value of thefield

NEW_VALUE VARCHAR2

4000 Yes The new value of thefield

CHANGED_BY VARCHAR2

255 No The person who madethe modification

CHANGED_ON TIMESTAMP(6)

No The date of themodification

Chapter 3Tables

3-21

Name DataType

Length

Precision

Scale NullAllowed

Comments


NUMBER


LAST_UPDATE_LOGIN

NUMBER






CREATED_BY VARCHAR2


Indexes


ARM_HISTORY_N1 NONUNIQUE OBJECT_ID

ARM_HISTORY_N2 NONUNIQUE FIELD_ID

ARM_HISTORY_N3 NONUNIQUE CHANGED_ON

ARM_HISTORY_PK UNIQUE HISTORY_FIELD_ID

ARM_INSTRUCTIONSThis table stores the instructions.

Details





Chapter 3Tables

3-22

Primary Key

Name Columns

ARM_INSTRUCTIONS_PK INSTRUCTION_ID

Columns


Precision

Scale NullAllowed

Comments

INSTRUCTION_ID NUMBER 18 0 No Primary Key

OBJECT_ID NUMBER 18 0 No The associated object ID

INSTRUCTION_TEXT

CLOB Yes The text of theinstructions


NUMBER 9 0 No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The numberis compared at thestart and end of atransaction to detectwhether another sessionhas updated the rowsince it was queried.

LAST_UPDATE_LOGIN


LAST_UPDATE_DATE


LAST_UPDATED_BY

VARCHAR2



CREATED_BY VARCHAR2


Indexes


ARM_INSTRUCTIONS_PK

UNIQUE INSTRUCTION_ID

ARM_INSTRUCTIONS_U1

UNIQUE OBJECT_ID

Chapter 3Tables

3-23

ARM_PERIODSThis table stores the periods.

Details





Primary Key

Name Columns

ARM_PERIODS_PK PERIOD_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

PERIOD_ID NUMBER

18 0 No The unique ID of the period

FREQUENCY_ORDER

NUMBER

2 0 Yes The relative order of the period

PERIOD_NAME VARCHAR2

180 No The name of the period

START_DATE DATE Yes The start date of the period

END_DATE DATE Yes The end date of the period

SKIP_WEEKENDS

VARCHAR2

Yes Flag to indicate if weekendsshould be skipped while scheduling.Possible values Y or N.


NUMBER

9 0 No Used to implement optimisticlocking. This number is incrementedevery time the row is updated.The number is compared at thestart and end of a transactionto detect whether another sessionhas updated the row since it wasqueried.

LAST_UPDATE_LOGIN

NUMBER


LAST_UPDATED_BY

VARCHAR2

255 No Who column. Stores the ID of theuser who last updated this row.

LAST_UPDATE_DATE


CREATED_BY VARCHAR2

255 No Who column. Stores the ID of theuser who created this row.

Chapter 3Tables

3-24

Name DataType

Length

Precision

Scale

NullAllowed

Comments

CREATION_DATE

DATE No Who column. Stores the datewhen this row was created in thedatabase.

FREQUENCY_ID NUMBER

18 0 Yes Frequency ID

STATUS_ID NUMBER

2 0 Yes The status of the period:51=Pending, 52=Open, 53=Closed,54=Locked

CLOSE_DATE DATE Yes The close date of the period

PROCESS_ID NUMBER

18 0 Yes The unique ID of the process

IS_AUTOREC_RUNNING

VARCHAR2

1 Yes Whether auto reconciliation processis running currently for the period

LAST_RECONCILED

TIMESTAMP(6)

Yes When the period was last reconciled

LAST_ARCHIVED

DATE Yes When the period was last archived

PURGED DATE Yes When the period was last purged

LAST_RESTORED

DATE Yes When the period was last restored

ARCHIVE_LOCATION

VARCHAR2

500 Yes The archive location

PRIOR_PERIOD_ID

NUMBER

18 0 Yes The period ID of this period's priorperiod

Indexes


ARM_PERIODS_N2 NONUNIQUE STATUS_ID

ARM_PERIODS_PK UNIQUE PERIOD_ID

ARM_PERIODS_U1 UNIQUE PRIOR_PERIOD_ID

ARM_QUESTIONSThis table stores the questions for a format instance.

Details





Chapter 3Tables

3-25

Primary Key

Name Columns

ARM_QUESTIONS_PK QUESTION_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

QUESTION_ID NUMBER 18 0 No Unique ID identifier

OBJECT_ID NUMBER 18 0 No ID of the object thisquestion applies to

QUESTION_TEXT VARCHAR2

4000 No The text of the question

QUESTION_TYPE VARCHAR2

25 No Type of question (TEXT,NUMBER, LIST, DATE,DATETIME, YESNO,TRUEFALSE)

REQUIRED VARCHAR2

1 No Is the question requiredto be answered (Y or N)

ORDER_SEQ NUMBER Yes The order ofappearance for thequestion within theformat instance

NEGATIVE_NUMBER_FORMAT

VARCHAR2

15 Yes Number format touse for negativenumbers (NUMBERtype question only).

SCALE VARCHAR2

15 Yes Scale used for numberformatting (NUMBERtype question only).

THOUSANDS_SEPARATOR_FLAG

VARCHAR2

1 Yes Whether or not touse the thousandsseparator (NUMBERtype question only).

DECIMAL_PLACES NUMBER Yes The number of decimalplaces (NUMBER typequestion only).

CURRENCY_SYMBOL

VARCHAR2

255 Yes The currency symbol,if any (NUMBER typequestion only).

Chapter 3Tables

3-26

Name DataType

Length

Precision

Scale NullAllowed

Comments


NUMBER 9 0 No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whetheranother session hasupdated the row since itwas queried.

LAST_UPDATE_LOGIN


LAST_UPDATE_DATE





CREATED_BY VARCHAR2


TEXT_LINES NUMBER Yes Number of lines for amulti-line text attribute

INCLUDE_ATTACHMENTS

VARCHAR2

1 No For multiline textquestions: Y=Yes,N=No.

PERCENTAGE VARCHAR2

1 No Whether the questionshould be formatted asa percentage

Indexes


ARM_QUESTIONS_N1

NONUNIQUE OBJECT_ID

ARM_QUESTIONS_PK

UNIQUE QUESTION_ID

ARM_QUESTIONS_U1

NONUNIQUE OBJECT_ID, QUESTION_ID

Chapter 3Tables

3-27

ARM_QUESTION_LIST_VALUESThis table stores the values for a list-type question.

Details





Primary Key

Name Columns

ARM_QUESTION_LIST_VALUES_PK QUESTION_LIST_VALUE_ID

Columns


Precision

Scale NullAllowed

Comments

QUESTION_LIST_VALUE_ID

NUMBER 18 0 No Unique ID

QUESTION_ID NUMBER 18 0 No Question the list value isassociated with.

LIST_VALUE VARCHAR2

765 No The value

LIST_ORDER NUMBER 0 No The list value orderwithin the "Question ID"



LAST_UPDATE_LOGIN


LAST_UPDATE_DATE


LAST_UPDATED_BY

VARCHAR2


Chapter 3Tables

3-28


Precision

Scale NullAllowed

Comments


CREATED_BY VARCHAR2


Indexes


ARM_QUESTION_LIST_VALUE_N1

NONUNIQUE QUESTION_ID

ARM_QUESTION_LIST_VALUES_PK

UNIQUE QUESTION_LIST_VALUE_ID

ARM_QUESTION_LIST_VALUES_U1

UNIQUE QUESTION_ID, LIST_VALUE

ARM_RATE_TYPESThis table stores the rate type definitions.

Details





Primary Key

Name Columns

ARM_RATE_TYPES_PK RATE_TYPE_ID

Columns


Precision

Scale NullAllowed

Comments

RATE_TYPE_ID NUMBER 18 0 No The Unique ID identifier

RATE_TYPE_NAME

VARCHAR2

765 No ARM Rate Type Name

SOURCE_SYSTEM_ID

NUMBER 18 0 Yes Source system identifier

Chapter 3Tables

3-29


Precision

Scale NullAllowed

Comments

SOURCE_SYSTEM_RATE_TYPE

VARCHAR2

765 Yes Source System RateType

CREATED_BY VARCHAR2


CREATION_DATE DATE Yes Who column. Stores thedate when this row wascreated in the database.

LAST_UPDATE_DATE


LAST_UPDATE_LOGIN



NUMBER No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The numberis compared at thestart and end of atransaction to detectwhether another sessionhas updated the rowsince it was queried.

Indexes


ARM_RATE_TYPES_PK

UNIQUE RATE_TYPE_ID

ARM_RECONCILIATIONSThis table stores the reconciliation and reconciliation instances of the system.The reconciliation and reconciliation instances share the same columns except:START_DATE (instance) vs START_DATE_OFFSET (reconciliation), END_DATE(instance) vs END_DATE_OFFSET (reconciliation) SCHEDULE_ID (instance), null forreconciliations.

Details





Chapter 3Tables

3-30

Primary Key

Name Columns

ARM_RECONCILIATIONS_PK RECONCILIATION_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

RECONCILIATION_ID NUMBER

18 0 No The Reconciliation unique ID

RECONCILIATION_ACCOUNT_ID

VARCHAR2

4000

No The concatenated accountsegment values.

RECONCILIATION_NAME

VARCHAR2

765 No The reconciliation name

RECONCILIATION_DESCRIPTION

VARCHAR2

4000

Yes The reconciliation description

PERIOD_ID NUMBER

18 0 Yes The period ID of thereconciliation instance. -2 forprofiles.

STATUS_ID NUMBER

2 0 Yes The status of the reconciliation:Null = Profiles, 32 = Pending,6 = Open with Preparer, 10= Open with Reviewer, 1 =Closed.

RESPONSIBILITY_LEVEL

NUMBER

9 0 Yes The current responsibility levelof the reconciliation instance.NULL for reconciliations.

PROCESS_ID NUMBER

18 0 Yes The process associatedwith the reconciliation. FKto ARM_PROCESSES. Theprocess determine how theCompleteness Check is verified

FORMAT_ID NUMBER

18 0 Yes The Format associated withthe reconciliation. FK toARM_FORMATS. This willdetermine the ReconciliationMethod as well as the layoutof the reconciliation as shownto the reconciler (preparer,approver, viewer, commentator).

RECONCILIATION_ACTIONS_ID

NUMBER

18 0 Yes The ID used for reconciliationactions/summary as analternate ID to differentiateprofile objects from actionobjects. Used to differentiatebalance summary attributesfrom profile attributes, andattachments from references

ACCOUNT_TYPE_ID NUMBER

18 0 Yes The account type ID, FK toARM_ACCOUNT_TYPES

Chapter 3Tables

3-31

Name DataType

Length

Precision

Scale

NullAllowed

Comments

NORMAL_BALANCE VARCHAR2

1 Yes D = Debit, C = Credit, U =Unassigned, E = Either Debit orCredit

HISTORICAL_RATE VARCHAR2

1 Yes This flag determines isthe object contains historicalaccounts and so no currencyconversion is done using Fxrates

RATE_TYPE_ID NUMBER

18 0 Yes Rate Type ID, FK toARM_RATE_TYPES table

AUTOREC_THRESHOLD_PERCENT

NUMBER

3 0 Yes Percent threshold value for Autoreconciliation method Balancematch (% tolerance). Valueshould be between 0 and 100

AUTO_RECONCILED VARCHAR2

1 Yes Whether the reconciliation wasauto-reconciled

MAX_AGE_ADJUSTMENTS

NUMBER

9 0 Yes This is the maximum agethat an Adjustment Transactionshould be for this ReconciliationAccount.

MAX_AGE_EXPLANATIONS

NUMBER

9 0 Yes This is the maximum agethat a Balance ExplanationTransaction should be for thisReconciliation Account.

AGING_VIOLATION VARCHAR2

1 Yes Whether or not there is an agingviolation in the reconciliation.

EVER_BEEN_LATE VARCHAR2

1 Yes Whether the reconciliation hasever been late with any person.

ENTER_SYSTEM_BALANCES

VARCHAR2

1 Yes Flag to indicate if source systembalances are manually enteredby preparer or not. Values: ''Y''or ''N''.

ENTER_SUBSYSTEM_BALANCES

VARCHAR2

1 Yes Flag to indicate if subsystembalances are manually enteredby preparer or not. Values: ''Y''or ''N''.

NORMAL_BALANCE_VIOLATION

VARCHAR2

1 Yes Whether or not there is aviolation in the reconciliation'snormal balance.

EXP_BALANCE_AGING_VIOLATION

VARCHAR2

1 Yes Whether or not there is aviolation in the reconciliation'sexpected balance.

SOURCE_SYSTEM_AGING_VIOLATION

VARCHAR2

1 Yes Whether or not there is aviolation in the reconciliation'ssource system.

SUBSYSTEM_AGING_VIOLATION

VARCHAR2

1 Yes Whether or not there is aviolation in the reconciliation'ssubsystem balance.

REJECTS NUMBER

9 0 Yes The number of rejectsperformed

Chapter 3Tables

3-32

Name DataType

Length

Precision

Scale

NullAllowed

Comments

EMAIL_SENT VARCHAR2

3 Yes ''Y'' for sent and ''N'' foremail not sent. Needed fororchestrating BPEL flow.

EMAIL_SENT_DATE DATE Yes The date when email wassent to the user. Used forconstructing email notificationcontent.

START_DATE DATE Yes Start Date of the reconciliationinstance. Same as the StartDate for the preparer.

END_DATE DATE Yes End Date of the reconciliationinstance. Same date as the EndDate for the last reviewer.

ACTUAL_END_DATE DATE Yes The date that the reconciliationwas completed

START_OFFSET NUMBER

9 0 Yes Start offset of the profile. Sameas the start offset for thepreparer.

SCHEDULE_FROM VARCHAR2

1 Yes Indicates how reconciliationstart date is calculated by perioddates, C - Close Date and E -End Date.

END_OFFSET NUMBER

9 0 Yes End offset of the profile. Sameas the end offset for the lastreviewer.


NUMBER

9 0 No Used to implement optimisticlocking. This number isincremented every time therow is updated. The numberis compared at the start andend of a transaction to detectwhether another session hasupdated the row since it wasqueried.

LAST_UPDATE_LOGIN

NUMBER



255 No Who column. Stores the ID ofthe user who last updated thisrow.

LAST_UPDATE_DATE DATE No Who column. Stores the datewhen this row was last updated.

CREATED_BY VARCHAR2

255 No Who column. Stores the ID ofthe user who created this row.

CREATION_DATE DATE No Who column. Stores the datewhen this row was created inthe database.

SUMMARY_RECONCILIATION

VARCHAR2

1 Yes Whether the profile/reconciliation is a summaryprofile or not.

Chapter 3Tables

3-33

Name DataType

Length

Precision

Scale

NullAllowed

Comments

SUMMARY_REC_TYPE

VARCHAR2

1 Yes Whether the child accounts arefilter or list type. Possible valuesare F - Filter, L - List.

SUMMARY_REC_FILTER_ID

NUMBER

18 0 Yes The filter ID stores the filtercriteria for child accounts, usedwhen summary reconciliationtype is Filter.

PREPARER_UPDATE_DATE

DATE Yes Last time the preparer updatedthe reconciliation

AUTO_RECONCILIATION_METHOD

VARCHAR2

50 Yes Auto Reconciliation method(code) name

AUTOREC_BALANCE_LOW

NUMBER

29 12 Yes Lower limit for balance forAuto reconciliation methods withbalance range

AUTOREC_BALANCE_HIGH

NUMBER

29 12 Yes Upper limit for balance forAuto reconciliation methods withbalance range

AUTOREC_THRESHOLD_NUMBER

NUMBER

29 12 Yes Number threshold value for Autoreconciliation method Balancematch (# tolerance)

ORG_ID NUMBER

18 0 Yes The organization ID, FK toFCM_ORG_UNITS

CALENDAR_ID NUMBER

18 0 Yes Calendar used when duringcopy to period. Always null forprofile, but not null for recon

ACTIVE VARCHAR2

1 No Whether the profile is marked asactive

VARIANCE_PERIOD_ID

NUMBER

18 0 Yes The variance period ID

Indexes


ARM_RECONCILIATIONS_N1

NONUNIQUE PERIOD_ID, RECONCILIATION_ACCOUNT_ID


NONUNIQUE PERIOD_ID


NONUNIQUE RECONCILIATION_ACCOUNT_ID


NONUNIQUE SUMMARY_RECONCILIATION,RECONCILIATION_ID


NONUNIQUE PERIOD_ID, STATUS_ID

ARM_RECONCILIATIONS_PK

UNIQUE RECONCILIATION_ID

ARM_RECONCILIATIONS_U1

UNIQUE PERIOD_ID, RECONCILIATION_ID

Chapter 3Tables

3-34


ARM_RECONCILIATIONS_U2

UNIQUE RECONCILIATION_ACTIONS_ID

ARM_RECONCILIATIONS_N1U

NONUNIQUE PERIOD_ID, SYS_NC00056$

ARM_RECONCILIATION_BUCKETSThis table stores the enabled currency buckets for reconciliations.

Details





Primary Key

Name Columns

ARM_PROFILE_BUCKETS_PK BUCKET_ID

ARM_PROFILE_BUCKETS_PK RECONCILIATION_ID

Columns


Precision

Scale NullAllowed

Comments

BUCKET_ID NUMBER 18 0 No Currency Bucket ID, FKtoARM_CURRENCY_BUCKETS

RECONCILIATION_ID

NUMBER 18 0 No Associated reconciliationID, FK toARM_RECONCILIATIONS

ENABLED VARCHAR2

1 Yes Is this bucket enabled ornot: Y=Yes, N=No.

DEFAULT_CURRENCY_ID

VARCHAR2

80 Yes Default Currency ID

Chapter 3Tables

3-35


Precision

Scale NullAllowed

Comments



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2



Indexes


ARM_PROFILE_BUCKETS_N1

NONUNIQUE RECONCILIATION_ID

ARM_PROFILE_BUCKETS_PK

UNIQUE BUCKET_ID, RECONCILIATION_ID

ARM_PROFILE_BUCKETS_U1

UNIQUE RECONCILIATION_ID, ENABLED, BUCKET_ID

ARM_RECON_ATTRIBUTES_1This table stores the attribute value assignments of the reconciliations. The columnsare dynamically created using the name C_<Attribute ID>.

Details




Chapter 3Tables

3-36


Primary Key

Name Columns

ARM_RECON_ATTRIBUTES_1_PK OBJECT_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

OBJECT_ID

NUMBER

18 0 No The Reconciliation ID for this row'sreconciliation.

C_<AttributeID>

These are the user defined columns,FCM_ATTRIBUTES.ATTRIBUTE_ID is usedto form the name of the column.Column name follows the formatc_<ATTRIBUTE_ID> (For Example, C_100000000056159).

Indexes


ARM_RECON_ATTRIBUTES_1_PK

UNIQUE OBJECT_ID

ARM_REFERENCESThis table stores the references and attachments.

Details





Primary Key

Name Columns

ARM_REFERENCES_PK REFERENCE_ID

Chapter 3Tables

3-37

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

REFERENCE_ID NUMBER

18 0 No Primary Key

OBJECT_ID NUMBER

18 0 No The object ID that this reference/attachment belongs to

REFERENCE_TYPE

VARCHAR2

4 No The reference type: ''URL'' or ''FILE'""

REFERENCE_NAME

VARCHAR2

765 Yes The reference name

URL VARCHAR2

4000 Yes The URL of the reference

FILE_ID NUMBER

Yes The File ID, FK toARM_REFERENCE_FILES

FILE_NAME VARCHAR2

765 Yes The file name

FILE_MIMETYPE VARCHAR2

128 Yes The file mime type


NUMBER

9 0 No Used to implement optimistic locking.This number is incremented everytime the row is updated. The numberis compared at the start and end of atransaction to detect whether anothersession has updated the row since itwas queried.

LAST_UPDATE_LOGIN

NUMBER


LAST_UPDATED_BY

VARCHAR2

255 No Who column. Stores the ID of theuser who last updated this row.

LAST_UPDATE_DATE


CREATED_BY VARCHAR2

255 No Who column. Stores the ID of theuser who created this row.

CREATION_DATE


CREATOR_ROLE VARCHAR2

3 Yes The role of the creator of thereference/attachment.

CREATOR_ID VARCHAR2

255 No The user ID of the person whocreated this.

USER_CREATION_DATE

DATE No The date of creation.

CARRY_FORWARD

VARCHAR2

1 Yes Whether to carry the attachmentforward.

Chapter 3Tables

3-38

Indexes


ARM_REFERENCES_N1

NONUNIQUE OBJECT_ID, REFERENCE_TYPE

ARM_REFERENCES_PK

UNIQUE REFERENCE_ID

ARM_SUMMARY_AMOUNTSThis table stores the display values for various balance and transaction summaries.Needed for performance reasons.

Details





Primary Key

Name Columns

ARM_SUMMARY_AMOUNTS_PK SUMMARY_AMOUNT_ID

Columns


Precision

Scale NullAllowed

Comments

SUMMARY_AMOUNT_ID

NUMBER 18 0 No Primary Key


VARCHAR2

4000 No The Account ID

PERIOD_ID NUMBER 18 0 No The Period ID

BUCKET_ID NUMBER 18 0 No The Bucket ID

SUMMARY_TYPE VARCHAR2

4 No Types: BSRC=BalanceSource System,BSUB=BalanceSub System,SRC=Adjustment toSource System,SUB=Adjustment to SubSystem, BEX=BalanceExplanation

AMOUNTS VARCHAR2

4000 Yes The amounts broken upby currencies.

Chapter 3Tables

3-39


Precision

Scale NullAllowed

Comments



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2



Indexes


ARM_SUMMARY_AMOUNTS_N1

NONUNIQUE PERIOD_ID

ARM_SUMMARY_AMOUNTS_PK

UNIQUE SUMMARY_AMOUNT_ID

ARM_SUMMARY_AMOUNTS_U1

UNIQUE PERIOD_ID, RECONCILIATION_ACCOUNT_ID,BUCKET_ID, SUMMARY_TYPE

ARM_SUMMARY_BALANCESThis table stores the child balance amount information for a summary reconciliation.

Details




Chapter 3Tables

3-40


Primary Key

Name Columns

ARM_SUMMARY_BALANCES_PK RECONCILIATION_ID

ARM_SUMMARY_BALANCES_PK CHILD_RECON_ACCOUNT_ID

ARM_SUMMARY_BALANCES_PK BALANCE_TYPE

Columns


Precision

Scale NullAllowed

Comments

RECONCILIATION_ID

NUMBER 18 0 No ID of the summaryprofile/reconciliation

CHILD_RECON_ACCOUNT_ID

VARCHAR2

4000 No Account ID of the childprofile/reconciliation

BALANCE_TYPE VARCHAR2

4 No The balance type:BEX SRC=Adjustmentsto source system,SUB=Adjustmentsto subsystem,BSRC=Sourcesystem balance,BSUB=Subsystembalance.

AMOUNT NUMBER 29 12 No The amount



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2


Chapter 3Tables

3-41


Precision

Scale NullAllowed

Comments


Indexes


ARM_SUMMARY_BALANCES_N1

NONUNIQUE RECONCILIATION_ID, BALANCE_TYPE

ARM_SUMMARY_BALANCES_PK

UNIQUE RECONCILIATION_ID,CHILD_RECON_ACCOUNT_ID,BALANCE_TYPE

ARM_SUMMARY_REC_CHILDRENThis table stores the parent-child relationships for a summary reconciliation.

Details





Primary Key

Name Columns

ARM_SUMMARY_REC_CHILDREN_PK RECONCILIATION_ID

ARM_SUMMARY_REC_CHILDREN_PK CHILD_ACCOUNT_ID

Columns


Precision

Scale NullAllowed

Comments

RECONCILIATION_ID

NUMBER 18 0 No Reconciliation ID ofthe summary profile/reconciliation

CHILD_ACCOUNT_ID

VARCHAR2

4000 No Account ID of the childaccount

Chapter 3Tables

3-42


Precision

Scale NullAllowed

Comments



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


LAST_GENERATED_DATE

DATE Yes Date the child accountwas last successfullygenerated into thesummary reconciliation.

CREATED_BY VARCHAR2



Indexes


ARM_SUMMARY_REC_CHILDREN_N1


ARM_SUMMARY_REC_CHILDREN_PK

UNIQUE RECONCILIATION_ID, CHILD_ACCOUNT_ID

ARM_TRANSACTIONSThis table stores the reconciliation compliance transactions for reconciliations.

Details



Chapter 3Tables

3-43



Primary Key

Name Columns

ARM_TRANSACTIONS_PK TRANSACTION_ID

Columns


Precision

Scale NullAllowed

Comments

TRANSACTION_ID NUMBER 18 0 No Unique ID, primary key

TRANSACTION_CODE

VARCHAR2

150 Yes Code to identifytransaction

TRANSACTION_DESCRIPTION

VARCHAR2

4000 Yes Simple description

TRANSACTION_TYPE

VARCHAR2

3 No The type of transaction:BEX=BalanceExplanation,SRC=Adjustment toSource System,SUB=Adjustment toSubsystem

RECONCILIATION_ID

NUMBER 18 0 No Reconciliation that thetransaction belongs to

OPEN_DATE DATE Yes Date the transactionopened

CLOSE_DATE DATE Yes Date the transactionclosed

AGING_VIOLATION

VARCHAR2

1 Yes Whether or not there isan aging violation in thetransaction.

AGE NUMBER 0 Yes Age of the transaction indays (Period End Dateminus Transaction OpenDate)

STATUS_FLAG VARCHAR2

1 No Stores the status:N=none, O=ok, X=needsattention



Chapter 3Tables

3-44


Precision

Scale NullAllowed

Comments

LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2



ACCOUNT_ID VARCHAR2

4000 Yes The associated accountID, for transactionscopied from childaccount

UPDATED VARCHAR2

1 Yes Whether or not thetransaction was updatedafter being copied to thesummary

SUMMARY_CREATED

VARCHAR2

1 No Y=yes, this ttransactionwas created in thesummary recon, N=No,it was not created insummary recon.

AMORT_ACCRETE

VARCHAR2

1 No N=no, A=amortizing,C=accreting

FROM_FDMEE VARCHAR2

1 No Whether loaded fromDM/FDMEE

PRIOR_TRANSACTION_ID

NUMBER 18 0 Yes The ID of the priortransaction, if carriedforward.

PERIOD_ID NUMBER 18 0 Yes The Period ID


VARCHAR2

4000 Yes The ReconciliationAccount ID

FROM_FLAG VARCHAR2

1 Yes Where transactioncame from: M=Manuallyentered by user,I=Imported fromRecon Actiondialog,P=Imported withPre-mapped account ID,F=FDMEE data load

Chapter 3Tables

3-45


Precision

Scale NullAllowed

Comments

SUB_PROFILE_ID VARCHAR2

4000 Yes The sub segment profileID, if sub segments areenabled

Indexes


ARM_TRANSACTIONS_N1


ARM_TRANSACTIONS_N2

NONUNIQUE ACCOUNT_ID

ARM_TRANSACTIONS_N3

NONUNIQUE RECONCILIATION_ACCOUNT_ID, PERIOD_ID

ARM_TRANSACTIONS_N4

NONUNIQUE PRIOR_TRANSACTION_ID,RECONCILIATION_ID

ARM_TRANSACTIONS_N5


ARM_TRANSACTIONS_N6

UNIQUE PERIOD_ID, RECONCILIATION_ID,TRANSACTION_ID

ARM_TRANSACTIONS_N7

UNIQUE PERIOD_ID, RECONCILIATION_ACCOUNT_ID,TRANSACTION_ID

ARM_TRANSACTIONS_N8

NONUNIQUE PERIOD_ID, PRIOR_TRANSACTION_ID

ARM_TRANSACTIONS_PK

UNIQUE TRANSACTION_ID

ARM_TRANSACTIONS_U2

NONUNIQUE PRIOR_TRANSACTION_ID

ARM_TRANSACTIONS_N1U

NONUNIQUE PERIOD_ID, SYS_NC00027$

ARM_TRANSACTION_AMOUNTSThis table stores the mapping between the reconciliation transaction amount and whatbucket these fit into.

Details





Chapter 3Tables

3-46

Primary Key

Name Columns

ARM_TRANSACTION_AMOUNTS_PK TRANS_AMOUNT_ID

Columns


Precision

Scale NullAllowed

Comments

TRANS_AMOUNT_ID

NUMBER 18 0 No Unique ID

OBJECT_ID NUMBER 18 0 No The object thistransaction is associatedwith

CURRENCY_BUCKET_ID

NUMBER 18 0 No ID of the bucket thatamount corresponds with

AMOUNT NUMBER No The currency amount ofthe transaction

CURRENCY VARCHAR2

80 Yes The currency used forthe transaction

OVERRIDE VARCHAR2

1 No Whether or not theuser has overridden theamount: Y=Yes, N=No.



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2



Chapter 3Tables

3-47

Indexes


ARM_TRANSACTION_AMOUNTS_PK

UNIQUE TRANS_AMOUNT_ID

ARM_TRANSACTION_AMOUNTS_U1

UNIQUE OBJECT_ID, CURRENCY_BUCKET_ID

ARM_TRANSACTION_SUMMARIESThis table stores the total amounts for a reconciliation's transaction by transactiontype.

Details





Primary Key

Name Columns

ARM_TRANSACTION_SUMMARIES_PK TRANSACTION_SUMMARY_ID

Columns

Name DataType

Length

Precision

Scale NullAllowed

Comments

TRANSACTION_SUMMARY_ID

NUMBER 18 0 No The Primary Key

RECONCILIATION_ID NUMBER 18 0 No ID of the summary profile/reconciliation

TRANSACTION_TYPE

VARCHAR2

3 No The transaction type. Samevalues asARM_TRANSACTIONS.TRANSACTION_TYPE

CURRENCY_BUCKET_ID

NUMBER 18 0 No The currency bucket ID

CURRENCY VARCHAR2

80 No The 3 character currencycode

AMOUNT NUMBER Yes The amount

Chapter 3Tables

3-48

Name DataType

Length

Precision

Scale NullAllowed

Comments


NUMBER 9 0 No Used to implementoptimistic locking. Thisnumber is incrementedevery time the row isupdated. The number iscompared at the startand end of a transactionto detect whether anothersession has updated therow since it was queried.

LAST_UPDATE_LOGIN

NUMBER Yes Who column. Stores thelogin/session ID of the userwho last updated this row.



LAST_UPDATE_DATE

DATE No Who column. Stores thedate when this row was lastupdated.

CREATED_BY VARCHAR2

255 No Who column. Stores the IDof the user who created thisrow.


PERIOD_ID NUMBER 18 0 Yes The Period ID


VARCHAR2

4000 Yes The Reconciliation AccountID

Indexes


ARM_TRANSACTION_SUMMARIES_N1



NONUNIQUE PERIOD_ID, RECONCILIATION_ID


NONUNIQUE PERIOD_ID, RECONCILIATION_ACCOUNT_ID,TRANSACTION_TYPE

ARM_TRANSACTION_SUMMARIES_PK

UNIQUE TRANSACTION_SUMMARY_ID

ARM_TRANSACTION_SUMMARIES_U1

NONUNIQUE PERIOD_ID, RECONCILIATION_ACCOUNT_ID,TRANSACTION_TYPE,CURRENCY_BUCKET_ID, CURRENCY

ARM_TRANSACTION_SUMMARIES_U2

UNIQUE RECONCILIATION_ID, TRANSACTION_TYPE,CURRENCY_BUCKET_ID, CURRENCY

Chapter 3Tables

3-49

ARM_TRANS_ATTRIBUTES_1This table stores the attribute value assignments of the transactions and action plans.The columns are dynamically created using the name C_<Attribute ID>.

Details





Primary Key

Name Columns

ARM_TRANS_ATTRIBUTES_1_PK OBJECT_ID

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

OBJECT_ID NUMBER

18 0 No The Transaction or Action Plan ID for therow.

C_<AttributeID>

These are the user defined columns,FCM_ATTRIBUTES.ATTRIBUTE_ID isused to form the name of the column.Column name follows the formatc_<ATTRIBUTE_ID> ( For Example, C_100000000056159).

Indexes


ARM_TRANS_ATTRIBUTES_1_PK

UNIQUE OBJECT_ID

ARM_WORKFLOW_ACTIONSThis table stores the workflow actions (submit and approve) for a profile instance.Does not store rejection actions.

Details





Chapter 3Tables

3-50

Primary Key

Name Columns

ARM_WORKFLOW_ACTIONS_PK ACTION_ID

Columns


Precision

Scale NullAllowed

Comments

ACTION_ID NUMBER 18 0 No Unique ID

OBJECT_ID NUMBER 18 0 No The object (profileinstance) of this action.

ACTION_TYPE VARCHAR2

1 No The action type:S=submit, A=approve

ACTION_DATE DATE No When the action tookplace

ACTION_LEVEL NUMBER 9 0 Yes Approval only. Theapproval level ofthis approval. Matchesaccess order_seqcolumn.

ACTION_BY_USER_ID

VARCHAR2

255 No Which user performedthis action

ACTION_BY_RULE_ID

NUMBER 18 0 Yes The rule ID thatperformed the action ifauto run by a rule.



LAST_UPDATE_LOGIN


LAST_UPDATED_BY

VARCHAR2


LAST_UPDATE_DATE


CREATED_BY VARCHAR2


Chapter 3Tables

3-51


Precision

Scale NullAllowed

Comments


Indexes


ARM_WORKFLOW_ACTIONS_N1

NONUNIQUE OBJECT_ID, ACTION_LEVEL

ARM_WORKFLOW_ACTIONS_PK

UNIQUE ACTION_ID

ViewsRelated Topics

• ARM_BALANCE_DETAIL_SUMMARY (VIEW)

• ARM_BALANCE_SUMMARIES (VIEW)

ARM_BALANCE_DETAIL_SUMMARY (VIEW)This view stores the Source and Sub-system balances that are shown on the DetailBalances list.

Details



• Object type: VIEW

Columns


Precision

Scale

NullAllowed

Comments

BALANCE_ID NUMBER Yes ID of the currency bucket

PERIOD_ID NUMBER 18 0 No The ARM period ID

PROFILE_ID VARCHAR2

4000 No The profile segment ID (it is fromARM_Reconciliations.RECONCILIATION_ACCOUNT_ID)

BALANCE_TYPE

NUMBER 1 0 No The ARM balance types: 1=-Source system or 2=Sub-system)

BUCKET_ID NUMBER 18 0 No ID of the currency bucket

CURRENCY VARCHAR2

15 No The currency key such as USD,CAD, or Yen.

Chapter 3Views

3-52


Precision

Scale

NullAllowed

Comments

AMOUNT NUMBER Yes The component account'saggregated balance

UD2X VARCHAR2

300 Yes Sub-segment value that maps toUD2 dimension

UD3X VARCHAR2


UD4X VARCHAR2


UD5X VARCHAR2


UD6X VARCHAR2


UD7X VARCHAR2


UD8X VARCHAR2


UD9X VARCHAR2


UD10X VARCHAR2


UD11X VARCHAR2


UD12X VARCHAR2


UD13X VARCHAR2


UD14X VARCHAR2


UD15X VARCHAR2


UD16X VARCHAR2


UD17X VARCHAR2


UD18X VARCHAR2


UD19X VARCHAR2


UD20X VARCHAR2


CREATION_DATE

DATE Yes Who column. Stores the datewhen this row was created in thedatabase.

LAST_UPDATE_DATE

DATE Yes Who column. Stores the date whenthis row was last updated.

Chapter 3Views

3-53

ARM_BALANCE_SUMMARIES (VIEW)This view stores the Source and Sub-system balances that are shown on theReconciliation Balances list.

Details



• Object type: VIEW

Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

PERIOD_ID NUMBER

18 0 No The ARM period ID.

PROFILE_ID VARCHAR2

4000 No The profile segment ID (it is fromARM_Reconciliations.RECONCILIATION_ACCOUNT_ID)

BALANCE_TYPE

NUMBER

1 0 No The ARM balance types: 1=Sourcesystem or 2=Sub-system)

BUCKET_ID NUMBER

18 0 No ID of the currency bucket

CURRENCY VARCHAR2

80 No The currency key such as USD, CAD,or Yen.

AMOUNT NUMBER

Yes The component account's aggregatedbalance.

LAST_UPDATE_DATE

DATE Yes Who column. Stores the date whenthis row was last updated.

CREATION_DATE

DATE Yes Who column. Stores the date whenthis row was created in the database.

Chapter 3Views

3-54

4Transaction Matching Tables

Related Topics

• Tables

TablesRelated Topics

• TM_ADJUSTMENT

• TM_ATTRIBUTE_VALUE

• TM_BALANCE_SUMMARY

• TM_DATA_SOURCE

• TM_DATA_SOURCE_ATTRIB

• TM_MATCH

• TM_MATCH_PROC

• TM_MATCH_PROC_BKT_ATTRIB_MAP

• TM_MATCH_PROC_DEF_ATTRIB_MAP

• TM_MATCH_RULE

• TM_MATCH_RULE_ADJ_DET

• TM_MATCH_RULE_ADJ_DET_ATTRIB

• TM_MATCH_RULE_COND

• TM_MATCH_TRANS

TM_ADJUSTMENTThis table stores Transaction Matching adjustment information.

Details


• Object owner: TM



Primary Key

Name Columns

ADJTRANSDETAILS_PK ADJUSTMENT_ID

4-1

Columns


Comments

RECON_ID NUMBER 18 0 No Foreign keytoTM_RECON

MATCH_PROC_ID

NUMBER 18 0 No Foreign KeytoTM_MATCH_PROC

MATCH_ID NUMBER 18 0 No Foreign KeytoTM_MATCH

ADJUSTMENT_ID

NUMBER 18 0 No Primary key

STATUS NUMBER 1 0 Yes AdjustmentStatus -1=OPEN,2=CLOSE

TRANS_TYPE_ID

NUMBER 18 0 No TM_TRANS_TYPEforeign key.Thetransactiontypeassociatedwith theadjustment

CHANGED_DATA_SOURCE_ID

NUMBER 18 0 No TM_DATA_SOURCEforeign key.The sourceto which theadjustmentis posted

BAL_ATTRIB_VALUE_1

NUMBER 18 2 Yes Adjustmentamount

Chapter 4Tables

4-2


Comments


NUMBER 9 0 Yes Used toimplementoptimisticlocking. Thisnumber isincrementedevery timethat the rowis updated.The numberis comparedat the startand end ofatransactionto detectwhetheranothersession hasupdated therow since itwasqueried.

CREATED_BY

NVARCHAR2

255 No Whocolumn.Stores theID of theuser whocreated thisrow.

UPDATED_BY

NVARCHAR2

255 Yes Whocolumn.Stores theID of theuser wholast updatedthis row.

CREATE_DATE

TIMESTAMP(6)

No Whocolumn.Stores thedate whenthis row wascreated inthedatabase.

UPDATE_DATE

TIMESTAMP(6)

Yes Whocolumn.Stores thedate whenthis row waslastupdated.

Chapter 4Tables

4-3


Comments

ACCOUNTING_DATE

DATE Yes AccountingDate of theadjustment

EXPORT_JOURNAL_JOB_ID

NUMBER 18 0 Yes Job IDassociatedwith journalexport

Indexes


ADJTRANSDETAILS_PK UNIQUE ADJUSTMENT_ID

TM_ADJUSTMENT_MATCH NONUNIQUE MATCH_ID

Foreign Keys

Table Foreign Table Foreign Key Column

TM_ADJUSTMENT TM_MATCH_PROC MATCH_PROC_ID

TM_ADJUSTMENT TM_RECON RECON_ID

TM_ADJUSTMENT TM_MATCH MATCH_ID

TM_ADJUSTMENT TM_TRANS_TYPE TRANS_TYPE_ID

TM_ATTRIBUTE_VALUEThis table stores Transaction Matching transaction type attribute values for theadjustment.

Details





Columns


Comments

ATTRIB_VALUE_ID

NUMBER 18 0 Yes Primary key

ATTRIB_ID NUMBER 18 0 Yes Primary keyof theattribute

Chapter 4Tables

4-4


Comments

OBJECT_ID NUMBER 18 0 Yes AdjustmentID orSupport ID

ATTRIBUTE_SOURCE_TYPE

NUMBER 1 0 Yes Type of theattribute -1=Adjustment or0=Support

VALUE_TEXT

NVARCHAR2

2000 Yes Value of theattribute iftype is Text

VALUE_NUMBER

NUMBER Yes Value of theattribute iftype isNumber

VALUE_LIST_CHOICE_ID

NUMBER 18 0 Yes Value of theattribute iftype is List


NUMBER 9 0 Yes Used toimplementoptimisticlocking.Thisnumber isincremented every timethat the rowis updated.The numberis comparedat the startand end ofatransactionto detectwhetheranothersession hasupdated therow since itwasqueried.

LAST_UPDATE_LOGIN

NUMBER Yes Whocolumn.Stores theID of theuser wholast updatedthis row.

Chapter 4Tables

4-5


Comments

UPDATED_BY

NVARCHAR2


CREATED_BY

NVARCHAR2

255 Yes Whocolumn.Stores theID of theuser whocreated thisrow.

VALUE_DATE

TIMESTAMP(6)

Yes Value of theattribute iftype is Date

UPDATE_DATE

TIMESTAMP(6)


CREATE_DATE

TIMESTAMP(6)

Yes Whocolumn.Stores thedate whenthis row wascreated inthedatabase.

TM_BALANCE_SUMMARYThis table stores the Transaction Matching pre-calculated balance summary for eachperiod.

Details





Primary Key

Name Columns

TM_BALANCE_SUMMARY_PK PROFILE_ID

Chapter 4Tables

4-6

Name Columns

TM_BALANCE_SUMMARY_PK PERIOD_ID

TM_BALANCE_SUMMARY_PK BALANCE_TYPE

TM_BALANCE_SUMMARY_PK BUCKET_ID

TM_BALANCE_SUMMARY_PK CURRENCY

Columns


Comments

PROFILE_ID

VARCHAR2 4000 No Account ID ofthe profile/reconciliation

PERIOD_ID NUMBER 18 0 No Period ID

BUCKET_ID

NUMBER 18 0 No Currencybucket ID

BALANCE_TYPE

NUMBER 1 0 No BalanceType:1=Unmatched Total(SourceSystem),2=Unmatched Supported(SourceSystem),3=In TransitTotal (SourceSystem),4=Unmatched Total (SubSystem),5=Unmatched Supported(SubSystem),6=In TransitTotal (SubSystem)

CURRENCY

VARCHAR2 80 No Currency

AMOUNT NUMBER 29 12 No BalanceAmount

Chapter 4Tables

4-7


Comments


NUMBER 9 0 No Used toimplementoptimisticlocking. Thisnumber isincrementedevery timethat the rowis updated.The numberis comparedat the startand end of atransaction todetectwhetheranothersession hasupdated therow since itwas queried.

LAST_UPDATED_BY

VARCHAR2 255 No Who column.Stores the IDof the userwho lastupdated thisrow.

LAST_UPDATE_DATE

TIMESTAMP(6)

No Who column.Stores thedate whenthis row waslast updated.

CREATED_BY

VARCHAR2 255 No Who column.Stores the IDof the userwho createdthis row.

CREATION_DATE

TIMESTAMP(6)

No Who column.Stores thedate whenthis row wascreated in thedatabase.

Indexes


TM_BALANCE_SUMMARY_N1 NONUNIQUE PERIOD_ID

TM_BALANCE_SUMMARY_PK UNIQUE PROFILE_ID, PERIOD_ID,BALANCE_TYPE,BUCKET_ID, CURRENCY

Chapter 4Tables

4-8

TM_DATA_SOURCEThis tables stores Transaction Matching data sources.

Details





Primary Key

Name Column

DATASOURCE_PK DATA_SOURCE_ID

Columns


Comments

RECON_TYPE_ID

NUMBER 18 0 No Foreign KeytoTM_RECON_TYPPE

DATA_SOURCE_ID

NUMBER 18 0 No DatasourceID, PrimaryKey

TEXT_ID NVARCHAR2

100 No Text ID for thematch type

NAME NVARCHAR2

100 No Name of thematch type

DYNAMIC_TABLE_NAME

NVARCHAR2

50 Yes For eachdatasource,one table iscreateddynamically tostore thedata. Thisfield indicatesthe databasetable name.Will beavailable onlyif the matchtype isapprovedsuccessfully

Chapter 4Tables

4-9


Comments


NUMBER 9 0 Yes Used toimplementoptimisticlocking. Thisnumber isincrementedevery timethat the row isupdated. Thenumber iscompared atthe start andend of atransaction todetectwhetheranothersession hasupdated therow since itwas queried.

CREATED_BY

NVARCHAR2

255 No Who column.Stores the IDof the userwho createdthis row.

UPDATED_BY

NVARCHAR2

255 Yes Who column.Stores the IDof the userwho lastupdated thisrow.

CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)

Yes Who column.Stores thedate whenthis row waslast updated.

SOURCE_TYPE_ENUM

NUMBER 2 0 Yes Two types ofData sources:-0=SourceSystem and1=SubSystem

Chapter 4Tables

4-10


Comments

ENABLE_TRANS_DELETE

NUMBER 1 0 Yes DeleteTransactionsfor the Datasource can be1=Enabled or0=Disabled

Indexes


DATASOURCE_PK UNIQUE DATA_SOURCE_ID

UNIQUE_DATASOURCE_IDX001

UNIQUE RECON_TYPE_ID,SYS_NC00010$

Foreign Keys


TM_DATA_SOURCE TM_RECON_TYPE RECON_TYPE_ID

TM_DATA_SOURCE_ATTRIBThis table stores Transaction Matching data source attributes.

Details





Primary Key

Name Columns

DATASOURCEATTRIB_PK DATA_SOURCE_ATTRIB_ID

Columns


Comments

CALC_ID NUMBER 18 0 Yes Internal UseOnly.Calculationassociatedwith theattribute

Chapter 4Tables

4-11


Comments

DATA_SOURCE_ID

NUMBER 18 0 No Foreign KeytoTM_DATA_SOURCE

DATA_SOURCE_ATTRIB_ID


TEXT_ID NVARCHAR2

100 No Text ID ofthe attribute

NAME NVARCHAR2

50 No Name of theattribute

DATA_TYPE

NVARCHAR2

20 No Data Typeof theattribute.1=Date,3=Integer,4=List,6=Number,8=Text,10=Yes/No

COLUMN_TYPE

NVARCHAR2

25 No Type of theattribute, todistinguishbetweenuser inputorcalculatedcolumn (i.e.Input,Calculated,Reference)

IS_REQUIRED

NUMBER 1 0 No 1=True.indicatesthis attributeismandatoryduring dataentry, or0=Falseindicatesattribute notmandatoryduring dataentry.

IS_KEY NUMBER 1 0 No 1=True,indicateswhether thisattribute is akey, or0=False,attribute nota key.

Chapter 4Tables

4-12


Comments

DEFAULT_VALUE

NVARCHAR2

1000 Yes Use DefaultValue is 1(True) thenthecorresponding defaultvalue isstored here.

TOTALING_METHOD

NVARCHAR2

40 Yes Indicatestotalingmethod forInteger andNumbertype ofattributes.e.g. Sum,Average,Count,None



CREATED_BY

NVARCHAR2


Chapter 4Tables

4-13


Comments

UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


IS_BALANCING_ATTRIB

NUMBER 1 0 Yes 1=If theattribute is abalancingattribute,0=attributenot thebalancingattribute

IS_ACCOUNTING_DATE

NUMBER 1 0 Yes 1=If theattribute isselected asAccountingdate,0=attributenot selectedasAccountingdate

IS_ALLOWED_TO_EDIT

NUMBER 1 0 Yes 1=Indicatesthe attributeis editableduringtransactionedit, 0=noteditableduringtransactionedit

Chapter 4Tables

4-14

Indexes


DATASOURCEATTRIB_PK UNIQUE DATA_SOURCE_ATTRIB_ID

UNIQUE_DATASOURCEATTRIB_IDX001

UNIQUE DATA_SOURCE_ID,SYS_NC00021$

Foreign Keys


TM_DATA_SOURCE_ATTRIB TM_DATA_SOURCE DATA_SOURCE_ID

TM_MATCHThis table stores Transaction Matching matches and match status.

Details





Primary Key

Name Column

MATCH_PK MATCH_ID

Columns


Comments

RECON_ID NUMBER 18 0 No Foreign KeytoTM_RECON

MATCH_PROC_ID


MATCH_RULE_ID

NUMBER 18 0 Yes Foreign keytoTM_MATCH_RULE

MATCH_ID NUMBER 18 0 No Primary key

Chapter 4Tables

4-15


Comments

MATCH_STATUS_ENUM

NUMBER 2 0 No Match status:1=SUGGESTED_MATCH,2=CONFIRMED_MATCH,3=CONFIRMED_ADJUST,4=SUGGESTED_ADJUST,6=SUPPORTED, 7=BOTH

ADJUSTMENT

NUMBER 2 0 No Adjustmentexists ornot:1=NOTAPPLICABLE,2=ADJUST,3=SUPPORT


NUMBER 9 0 Yes Used toimplementoptimisticlocking. Thisnumber isincrementedevery timethat the rowis updated.The numberis comparedat the startand end of atransaction todetectwhetheranothersession hasupdated therow since itwas queried.

CREATED_BY

NVARCHAR2

255 No Who column.Stores the IDof the userwho createdthis row.

UPDATED_BY

NVARCHAR2

255 Yes Who column.Stores the IDof the userwho lastupdated thisrow.

Chapter 4Tables

4-16


Comments

CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)

Yes Who column.Stores thedate whenthis row waslast updated.

Indexes


MATCH_PK UNIQUE MATCH_ID

TM_MATCH_RECON NONUNIQUE RECON_ID

TM_MATCH_STATUS NONUNIQUE MATCH_STATUS_ENUM

TM_MATCH_SUMMARIES_U1

NONUNIQUE RECON_ID,MATCH_STATUS_ENUM

Foreign Keys

Name Foreign Table Foreign Key Column

TM_MATCH TM_RECON RECON_ID

TM_MATCH TM_MATCH_RULE MATCH_RULE_ID

TM_MATCH TM_MATCH_PROC MATCH_PROC_ID

TM_MATCH_PROCThis table stores match processes.

Details





Primary Key

Name Columns

MATCHPROC_PK MATCH_PROC_ID

Chapter 4Tables

4-17

Columns


Comments

RECON_TYPE_ID

NUMBER 18 0 No Foreign KeytoTM_RECON_TYPE

MATCH_PROC_ID


TEXT_ID NVARCHAR2

100 No Text ID ofthe matchprocess

NAME NVARCHAR2

100 No Name of thematchprocess

FROM_DATA_SOURCE_ID

NUMBER 18 0 Yes SourceSystemdata source

TO_DATA_SOURCE_ID

NUMBER 18 0 Yes Sub systemdata source



CREATED_BY

NVARCHAR2


Chapter 4Tables

4-18


Comments

UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


ADJ_ACCOUNTING_DATE_TYPE

NUMBER 1 0 Yes 0=MatchDate,1=LatestAccountingDate in theMatchGroup

POSITION NUMBER 4 0 Yes Order ofauto matchexecution

Indexes


MATCHPROC_PK UNIQUE MATCH_PROC_ID

UNIQUE_MATCHPROC_IDX001

UNIQUE RECON_TYPE_ID,SYS_NC00012$

Foreign Keys


TM_MATCH_PROC TM_RECON_TYPE RECON_TYPE_ID

TM_MATCH_PROC_BKT_ATTRIB_MAPThis table stores bucketing attributes defined for each match process.

Chapter 4Tables

4-19

Details





Primary Key

Name Columns

TMMATCHPROCBKTATTRIBMAP_PK BUCKET_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


BUCKET_ID


BUCKET_NAME

NVARCHAR2

100 No Name of thebucket

FROM_DATA_SOURCE_ID

NUMBER 18 0 No Foreign KeytoTM_DATA_SOURCE.SourceSystemdata sourceID.

TO_DATA_SOURCE_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE.Sub Systemdata sourceID.

FROM_ATTRIB_ID

NUMBER 18 0 No Foreign KeytoTM_DATA_SOURCE_ATTRIB.SourceSystemdata sourceattribute ID.

Chapter 4Tables

4-20


Comments

TO_ATTRIB_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE_ATTRIB. SubSystemdata sourceattribute ID.

BUCKET_ORDER

NUMBER 3 0 No Bucketingorder

Indexes


TMMATCHPROCBKTATTRIBMAP_PK

UNIQUE BUCKET_ID

Foreign Keys


TM_MATCH_PROC_BKT_ATTRIB_MAP

TM_DATA_SOURCE_ATTRIB TO_ATTRIB_ID


TM_DATA_SOURCE TO_DATA_SOURCE_ID


TM_DATA_SOURCE_ATTRIB FROM_ATTRIB_ID


TM_DATA_SOURCE FROM_DATA_SOURCE_ID


TM_MATCH_PROC MATCH_PROC_ID


TM_RECON_TYPE RECON_TYPE_ID

TM_MATCH_PROC_DEF_ATTRIB_MAPThis table stores default attribute mapping defined for each match process.

Details





Chapter 4Tables

4-21

Primary Key

Name Columns

MATCHPROCDEFATTRIBMAP_PK MATCH_PROC_DEF_ATTRIB_MAP_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


BUCKET_ID


BUCKET_NAME

NVARCHAR2

100 No Name of thebucket

FROM_DATA_SOURCE_ID


TO_DATA_SOURCE_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE.Sub Systemdata sourceIDz

FROM_ATTRIB_ID

NUMBER 18 0 No Foreign KeytoTM_DATA_SOURCE_ATTRIB.SourceSystemdata sourceattribute ID.

TO_ATTRIB_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE_ATTRIB.Sub Systemdata sourceattribute ID.

Chapter 4Tables

4-22


Comments

BUCKET_ORDER

NUMBER 3 0 No Bucketingorder

RECON_TYPE_ID


MATCH_PROC_ID


MATCH_PROC_DEF_ATTRIB_MAP_ID


FROM_DATA_SOURCE_ID


FROM_ATTRIB_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE_ATTRIB.SourceSystemdata sourceattribute ID.

TO_DATA_SOURCE_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE.Sub Systemdata sourceID.

TO_ATTRIB_ID

NUMBER 18 0 Yes Foreign KeytoTM_DATA_SOURCE_ATTRIB.Sub Systemdata sourceattribute ID.

USED_FOR_BALANCING

NUMBER 1 0 No Identifies ifthis is abalancingattributemapping ornot: 0=No,1=Yes.

Chapter 4Tables

4-23


Comments


NUMBER 9 0 Yes Used toimplementoptimisticlocking.Thisnumber isincremented every timethat the rowis updated.The numberis comparedat the startand end ofatransactionto detectwhetheranothersession hasupdated therow since itwasqueried.

CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


Chapter 4Tables

4-24


Comments

TOLERANCE_TYPE

NUMBER 2 0 Yes -"ABSOLUTE","PERCENTAGE" etc.ENUM -"ABSOLUTE" is thedefaultvalue.

TOLERANCE_LOW_UPTO

NUMBER 16 2 Yes - UPTO isonlyapplicable ifDEFAULT_TOLER_LIMIT_LOW_TYPE isPercentage

TOLERANCE_HIGH_UPTO

NUMBER 16 2 Yes - UPTO isonlyapplicable ifDEFAULT_TOLER_LIMIT_HIGH_TYPE isPercentage

DEFAULT_TOLER_LIMIT_LOW

NUMBER 16 2 Yes DefaultFromtolerancelimit. Matchoperationsuse thisvalue ifdefault ischosen inrule

DEFAULT_TOLER_LIMIT_HIGH

NUMBER 16 2 Yes Default Totolerancelimit. Matchoperationsuse thisvalue ifdefault ischosen inrule

Indexes


MATCHPROCDEFATTRIBMAP_PK

UNIQUE MATCH_PROC_DEF_ATTRIB_MAP_ID

Chapter 4Tables

4-25

Foreign Keys


TM_MATCH_PROC_DEF_ATTRIB_MAP


TM_MATCH_PROC_DEF_ATTRIB_MAP


TM_MATCH_RULEThis tables stores matching rules.

Details





Primary Key

Name Columns

MATCHRULE_PK MATCH_RULE_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


MATCH_RULE_ID


TEXT_ID NVARCHAR2

100 No Text ID ofthe matchrule

NAME NVARCHAR2

100 No Name of thematch rule

DESCRIPTION

NVARCHAR2

2000 Yes Descriptionof the matchrule

Chapter 4Tables

4-26


Comments

MATCH_STATUS_ENUM

NUMBER 2 0 No 0=UNUSED,1=SUGGESTED,2=CONFIRMED,3=SUGGESTED_NO_AMBIGUOUS,4=CONFIRMED_NO_AMBIGUOUS/

MATCH_RULE_TYPE_ENUM

NUMBER 2 0 No 0=ONE_TO_ONE,1=ONE_TO_MANY,2=MANY_TO_ONE,3=MANY_TO_MANY,4=ADJUSTMENT,5=SUPPORT,6=ONE_TO_MANY_SUBSET,7=MANY_TO_ONE_SUBSET.

MATCH_RULE_EXEC_TYPE_ENUM

NUMBER 2 0 No 0=Auto,1=Manual

Chapter 4Tables

4-27


Comments



CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


RULE_ORDER

NUMBER 4 0 No RuleexecutionOrder

CREATE_DATE

TIMESTAMP(6)


Chapter 4Tables

4-28


Comments

UPDATE_DATE

TIMESTAMP(6)


FROM_DS_FILTER_ID

NUMBER 18 0 Yes SourceSystem filterused formatching

TO_DS_FILTER_ID

NUMBER 18 0 Yes Sub systemfilter usedfor matching

SOURCE_TO_ADJUST

NUMBER 18 0 Yes The sourceto adjust ifthe rule hasat least oneruleconditionwith "MatchWithadjustment"

Indexes


MATCHRULE_PK UNIQUE MATCH_RULE_ID

UNIQUE_MATCHRULE_IDX001

UNIQUE MATCH_PROC_ID,SYS_NC00015$

Foreign Keys


TM_MATCH_RULE TM_RECON_TYPE RECON_TYPE_ID

TM_MATCH_RULE TM_MATCH_PROC MATCH_PROC_ID

TM_MATCH_RULE_ADJ_DETThis table stores the adjustment detail definition for match rules

Details





Chapter 4Tables

4-29

Primary Key

Name Columns

MATCHRULEADJDET_PK MATCH_RULE_ADJ_DET_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


MATCH_RULE_ID

NUMBER 18 0 No Foreign keytoTM_MATCH_RULE

MATCH_RULE_ADJ_DET_ID

NUMBER 18 0 No Foreign keytoTM_MATCH_RULE_Adj_DET

ADJ_DATA_SOURCE_ID

NUMBER 18 0 Yes Source toadjust whenadjustmentis createdby automatch

TRANS_TYPE_ID

NUMBER 18 0 No TransactionType to beused byauto matchwhenadjustmentis created

Chapter 4Tables

4-30


Comments



CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


Chapter 4Tables

4-31

Indexes


MATCHRULEADJDET_PK UNIQUE MATCH_RULE_ADJ_DET_ID

Foreign Keys


TM_MATCH_RULE_ADJ_DET TM_MATCH_PROC MATCH_PROC_ID

TM_MATCH_RULE_ADJ_DET TM_RECON_TYPE RECON_TYPE_ID

TM_MATCH_RULE_ADJ_DET TM_TRANS_TYPE TRANS_TYPE_ID

TM_MATCH_RULE_ADJ_DET TM_MATCH_RULE MATCH_RULE_ID

TM_MATCH_RULE_ADJ_DET_ATTRIBThis table stores one row for each match rule adjustment attribute.

Details





Primary Key

Name Columns

MATCHRULEADJDETATTRIB_PK MATCH_RULE_ADJ_DET_ATTRIB_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


MATCH_RULE_ID


Chapter 4Tables

4-32


Comments

MATCH_RULE_ADJ_DET_ID


MATCH_RULE_ADJ_DET_ATTRIB_ID

NUMBER 18 0 No Foreign keytoTM_MATCH_RULE_ADJ_DET_ATTRIB

ATTRIB_ID NUMBER 18 0 No TransactionTypeattribute ID

MATCH_RULE_DEF_VAL_TYPE

NUMBER 18 0 Yes TransactionTypeattribute ID

DEF_VALUE_ATTRIB_ID

NUMBER 18 0 Yes Data sourceattribute idfrom whichthe value tobe picked.

DEF_VALUE_TEXT

NVARCHAR2

500 Yes Defaultvalue to beused iftransactiontypeattribute isText

DEF_VALUE_NUMBER

NUMBER 18 0 Yes Defaultvalue to beused iftransactiontypeattribute isNumber

DEF_VALUE_DATE

DATE Yes Defaultvalue to beused iftransactiontypeattribute isDate

DEF_VALUE_LIST_CHOICE_ID

NUMBER 18 0 Yes Defaultvalue to beused iftransactiontypeattribute isList

Chapter 4Tables

4-33


Comments



CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


Chapter 4Tables

4-34

Indexes


MATCHRULEADJDETATTRIB_PK

UNIQUE MATCH_RULE_ADJ_DET_ATTRIB_ID

Foreign Keys


TM_MATCH_RULE_ADJ_DET_ATTRIB



TM_MATCH_RULE_ADJ_DET MATCH_RULE_ADJ_DET_ID


TM_MATCH_RULE MATCH_RULE_ID



TM_MATCH_RULE_CONDThis table stores match rule conditions.

Details





Primary Key

Name Columns

MATCHRULECOND_PK MATCH_RULE_COND_ID

Columns


Comments

RECON_TYPE_ID


MATCH_PROC_ID


Chapter 4Tables

4-35


Comments

MATCH_RULE_ID


MATCH_RULE_COND_ID


IS_BALANCING_ATTRIB

NUMBER 1 0 No Needs torefer codefor actualvalues -YES/NO

COMP_DATA_SOURCE_ID

NUMBER 18 0 No SourceSystemdata source

COMP_ATTRIB_ID

NUMBER 18 0 Yes SourceSystemattribute ID

MATCH_TYPE_ENUM

NUMBER 2 0 No 0=ONE_TO_ONE,1=ONE_TO_MANY,2=MANY_TO_ONE, 3=MANY_TO_MANY,4=ADJUSTMENT,5=SUPPORT,6=ONE_TO_MANY_SUBSET,7=MANY_TO_ONE_SUBSET.

COMP_TO_DATA_SOURCE_ID

NUMBER 18 0 Yes Sub systemdata source.When ruleType isAdjust orSupport,this columnvalue isNULL

Chapter 4Tables

4-36


Comments

COMP_TO_ATTRIB_ID

NUMBER 18 0 Yes Sub systemdata sourceattribute ID.when ruleType isAdjust orSupport,this columnis NULL

TOLER_LIMITS_TYPE_ENUM

NUMBER 2 0 No "CustomLimits","MatchProcessLimits"



CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


Chapter 4Tables

4-37


Comments

CREATE_DATE

TIMESTAMP(6)


UPDATE_DATE

TIMESTAMP(6)


TOLERANCE_TYPE

NUMBER 2 0 Yes -"ABSOLUTE","PERCENTAGE" etc.ENUM - nullis thedefaultvalue.

TOLERANCE_LOW_UPTO


TOLERANCE_HIGH_UPTO


TOLERANCE_LOW

NUMBER 16 2 Yes FromTolerance

TOLERANCE_HIGH

NUMBER 16 2 Yes ToTolerance

Indexes


MATCHRULECOND_PK UNIQUE MATCH_RULE_COND_ID

Chapter 4Tables

4-38

Foreign Keys


TM_MATCH_RULE_COND TM_RECON_TYPE RECON_TYPE_ID

TM_MATCH_RULE_COND TM_MATCH_RULE MATCH_RULE_ID

TM_MATCH_RULE_COND TM_MATCH_PROC MATCH_PROC_ID

TM_MATCH_TRANSThis table stores supported transactions and is retained even after the transaction ismatched.

Details





Primary Key

Name Columns

MATCHTRANS_PK MATCH_TRANS_ID

Columns


Comments

RECON_ID NUMBER 18 0 No Foreign KeytoTM_RECON

MATCH_PROC_ID


MATCH_ID NUMBER 18 0 Yes Foreign KeytoTM_MATCH

MATCH_TRANS_ID


COMP_TRANS_ID

NUMBER 18 0 Yes TransactionID fromsourcesystem datasource ofthis matchprocess

Chapter 4Tables

4-39


Comments

COMP_TO_TRANS_ID

NUMBER 18 0 Yes TransactionID from subsystem datasource ofthis matchprocess



CREATED_BY

NVARCHAR2


UPDATED_BY

NVARCHAR2


CREATE_DATE

TIMESTAMP(6)


Chapter 4Tables

4-40


Comments

UPDATE_DATE

TIMESTAMP(6)


Indexes


MATCHTRANS_PK UNIQUE MATCH_TRANS_ID

Foreign Keys


TM_MATCH_TRANS TM_RECON RECON_ID

TM_MATCH_TRANS TM_MATCH MATCH_ID

TM_MATCH_TRANS TM_MATCH_PROC MATCH_PROC_ID

Chapter 4Tables

4-41

5Transaction Matching Dynamic Tables

Related Topics

• TM_TRANS_<DATA_SOURCE_ID>

TM_TRANS_<DATA_SOURCE_ID>For each data source, one table is created dynamically to store thedata. TM_DATA_SOURCE.DYNAMIC_TABLE_NAME indicates the name ofthe table for the given datasource. The table name follows the formatTM_TRANS_<DATA_SOURCE_ID> (for example, TM_TRANS_1024). The table willbe available only if the match type is approved successfully.

Details





Columns

Name DataType

Length

Precision

Scale

NullAllowed

Comments

TRANS_ID NUMBER 18 0 No Unique transaction ID.

RECON_ID NUMBER 18 0 Yes Primary key to TM_RECON

JOB_ID NUMBER 18 0 Yes Import Job ID

MATCH_ID NUMBER 18 0 Yes Match Id

MATCH_STATUS_ENUM NUMBER 2 0 Yes Match status (sameas TM_MATCHMATCH_STATUS_ENUM)

EXPORT_JOURNAL_STATUS

NUMBER 18 0 Yes Export journal status: 0=closed, Null=open

EXPORT_JOURNAL_JOB_ID

NUMBER 18 0 Yes Export Journal Job ID

IS_EDITED_TRANS NUMBER 1 0 Yes Is transaction edited: 1=Yes

5-1

Name DataType

Length

Precision

Scale

NullAllowed

Comments

C_<DATA_SOURCE_ATTRIBUTE_ID>

Other user defined attributesin the data source.TM_DATA_SOURCE_ATTRIB.DATA_SOURCE_ATTRIB_ID is used to form the name ofthis column. Column namefollows the formatC_<DATA_SOURCE_ATTRIBUTE_ID> (for example,C_20512. Will be availableonly if the match type isapproved successfully.

Chapter 5TM_TRANS_<DATA_SOURCE_ID>

5-2

Oracle Enterprise Performance Management Cloud …...1 Overview This guide contains information...

Documents

Transcript of Oracle Enterprise Performance Management Cloud …...1 Overview This guide contains information...