Class diagram

under construction below this line ---------------------------

ARAP Facility - List of object interfaces, with proposed mapping to arapXML: 

struct TransactionInfo {

TransactionId trans_id;

wstring voucher_ref;

Date voucher_date;

Date act_trans_date;

PeriodId period_id;

};

typedef sequence <TransactionInfo> TransactionInfoList;

The data type TransactionInfo specifies summary information about a single, specific GL Transaction. The data type TransactionInfoList is a collection type for multiple TransactionInfo data types

• The member trans_id specifies a unique GL Transaction reference for a single, specific GL Transaction.
  
• The member voucher_ref refers to any external (e.g. physical) documentation which may be related to (or associated with) a single GL Transaction such as a cheque, purchase order or invoice number, for example. Many National statutory regulations require that each GL Transaction in the accounting books must correspond to a "real" business transaction (usually represented by a paper voucher) and that it must also be easy to trace a specific GL Entry in the books to a corresponding voucher. This information may also be required for internal auditing purposes.
  
• The member voucher_date refers to the date of the "real" business transaction that caused the GL Transaction to be created and posted to the General Ledger, for example; a date on some external documentation (e.g. voucher) that a GL Transaction is to be (or was) associated with. Please see the TransactionInfo member voucher_ref as mentioned previously.
  
• The member act_trans_date refers to the "physical" or actual calendar date that the GL Transaction was (or is to be) posted to the currently selected General Ledger, and may be used for general purpose GL Transaction retrieval.
  
• The member period_id refers to an implementation defined accounting period for the logical posting of this GL Transaction. The data type PeriodId is of type wstring.

Generally, financial accounting is done within "accounting periods". An accounting period is defined as a period of time (of arbitrary length), whose only constraint is that a given accounting period is shorter than a full financial year. This applies not only to General Ledger accounting, but also to other often related accounting functions such as Accounts Receivable and Accounts Payable, for example. The set up of accounting periods is typically performed only once a year and is the subject of organisational policy. This submission makes no prescriptive statements about the rules that may be applied when using accounting periods.

As of this writing, both Period Management as well as Closing and Reconciliation Facilities are being considered as potential candidates for future OMG FDTF RFPs.

Each GL Transaction is composed of at least two (or more) GL Entries. Every GL Entry in the GL Facility corresponds to either a debit or a credit. Each GL Entry contains the details of an amount (debited or credited) in a foreign currency, as well that same amount in the nominated reporting currency of a specific General Ledger. In combination with the historical exchange rate information provided by an instance of the OMG Currency Facility, this provides sufficient information to generate multi-currency general purpose financial statements, should this be required.

struct Entry {

TransactionId trans_id;

EntryId entry_id;

Date entry_date;

EntryType entry_type;

AccountId acc_id;

Money orig_amount

Money amount;

DebitOrCredit dr_cr;

wstring description;

wstring voucher_ref;

};

typedef sequence<Entry> EntryList;

The data type EntryList specifies a collection type for multiple GL Entries. The data type Entry specifies information about a single GL Entry.

• The member trans_id specifies the parent GL Transaction that a single GL Entry is associated with and is synonymous with the TransactionId data type of the TransactionInfo data type mentioned previously.
  
• The member entry_id specifies the "audit trail" number of a GL Entry, while the members entry_date and data type entry_type (respectively) specify the "logical" date that a GL Entry was (or is to be) posted and the GL Entry type identifying the type of a single GL Entry.
  
• The member acc_id specifies the GL Account associated with a single GL Entry.
  
• The member orig_amount specifies the original amount of money of a foreign currency business transaction. A "foreign currency" is defined as a currency other than the reporting currency of an enterprise. Please see Profile::get_ledger_currency() for more information.
  
• The member Amount specifies the monetary amount of a GL Entry in a General Ledger’s reporting currency, while the member dr_cr indicates whether the GL Account involved was (or is to be) debited or credited.
  
• The GL Entry members description and voucher_ref hold user defined annotation which describes the GL Entry and a voucher reference to any relevant documentation associated with the GL Entry.

The data type EntryTypeInfo refers to a single, specific GL Entry type and an associated high level description such as "Journal Debit" or "Journal Credit", for example. The data type EntryTypeInfoList is a collection type of EntryTypeInfo.

• The member type refers to a single GL Entry type which represents the type of financial accounting transaction associated with a single, specific GL Entry.

The member description refers to a high level, human-readable description such as "Journal Credit" or "Journal Debit", for example.

copyright notice:

Used with the permission of the Object Management Group. For information on joining the OMG or additional information, please contact OMG headquarters by phone at +1-781-444 0404, by fax at +1-781-444 0320, or by email at info@omg.org. The OMG provides current information and services for distributed enterprise computing on the World Wide Web at www.omg.org and www.corba.org. Information about OMG Japan can be found at www.omgj.org.

The Object Management Group is an international non-profit standards organization that promotes a full-lifecycle approach to enterprise integration. OMG's standards cover application design and implementation.

CORBA®, The Information Brokerage®, CORBA Academy®, IIOP® and the Object Management Group logo® are registered trademarks of the Object Management Group. OMG(tm), Object Management Group(tm), the CORBA Logo(tm), "The Middleware That's Everywhere(tm)" , the CORBA Academy logo(tm), XMI(tm), MOF(tm), CWM(tm), OMG Interface Definition Language(tm), IDL(tm), CORBAservices(tm), CORBAfacilities(tm), CORBAmed(tm), CORBAnet(tm), UML(tm), the UML Cube Logo, "We're Known By The Companies We Connect(tm)", Model Driven Architecture(tm), MDA(tm), OMG Model Driven Architecture(tm), OMG MDA(tm), "The Architecture of Choice for a Changing World(tm)", and Unified Modeling Language(tm) are trademarks of the Object Management Group.