MIT FI/CO Validations

Introduction: SAP FI/CO Validations
FI/CO Validations are procedures that can assess the validity of FI/CO documents before they are posted. These procedures run during the transactions of creating or changing an FI/CO document. According to the configuration, they issue messages to the user. The result of these messages is either just information or warnings that the user can override, or a hard error that will block the transaction from being completed before the data are corrected. The transactions where FI validations may apply encompass all transactions that generate accounting documents, i.e., the standard FI transactions (General Ledger, Accounts Payable, Accounts Receivable), as well as others such as material movements, cost settlements, etc. The transactions where CO validations may apply encompass all transactions that generate costing documents, i.e., pure CO transactions (e.g. ,cost assessment, distribution, reposting) as well as all other transactions that do secondary CO posting (e.g. sales, purchasing, FI transactions). In both FI and CO, validations are distinguished into three kinds: (a) Header validations: check data in the document header, e.g. document type, document date, posting date/period, user name, transaction type etc. (b) Line item validations: check data in each document line-item, e.g. GL account number, cost object, possibly in conjunction with header data (see above). (c) Document validations: check data in the whole document, e.g. GL account combination between two or more line items.
FI/CO Validations for MIT
Requirements for validating FI/CO documents were gathered during multiple CAO meetings in June 1997. Requirements primarily relate to the following processes: Journal vouchers; preliminary posting and actual posting Monthly period closing, fiscal-year end closing Payroll Travel Cashier Accounts receivable transactions Accounts payable transactions Department of Facilities Procurement Sponsor Billing The result of these meetings was a set of rules, which has been implemented in SAP as FI/CO validations. *Notes:* A preliminary document can be saved without any validation, if the user saves the document with the menu option park . If the user selects the menu option check (before saving the document), then only the CO validations are triggered. (Note: If validation is passed the system puts in the profit center and fund center of the cost object(s) that where validated.) If the user selects to save the document using the menu-option complete, both the CO and FI validations are triggered (Note: standard SAP does not trigger FI validations; this is achieved through an MIT modification). SAP Application Area Cost Accounting Financial Accounting

Introduction: SAP FI/CO Validations

FI/CO Validations are procedures that can assess the validity of FI/CO documents before they are posted. These procedures run during the transactions of creating or changing an FI/CO document. According to the configuration, they issue messages to the user. The result of these messages is either just information or warnings that the user can override, or a hard error that will block the transaction from being completed before the data are corrected.

The transactions where FI validations may apply encompass all transactions that generate accounting documents, i.e., the standard FI transactions (General Ledger, Accounts Payable, Accounts Receivable), as well as others such as material movements, cost settlements, etc.

The transactions where CO validations may apply encompass all transactions that generate costing documents, i.e., pure CO transactions (e.g. ,cost assessment, distribution, reposting) as well as all other transactions that do secondary CO posting (e.g. sales, purchasing, FI transactions).

In both FI and CO, validations are distinguished into three kinds:
(a) Header validations: check data in the document header, e.g. document type, document date, posting date/period, user name, transaction type etc.
(b) Line item validations: check data in each document line-item, e.g. GL account number, cost object, possibly in conjunction with header data (see above).
(c) Document validations: check data in the whole document, e.g. GL account combination between two or more line items.

FI/CO Validations for MIT

Requirements for validating FI/CO documents were gathered during multiple CAO meetings in June 1997. Requirements primarily relate to the following processes:

Journal vouchers; preliminary posting and actual posting
Monthly period closing, fiscal-year end closing
Payroll
Travel
Cashier
Accounts receivable transactions
Accounts payable transactions
Department of Facilities
Procurement
Sponsor Billing

The result of these meetings was a set of rules, which has been implemented in SAP as FI/CO validations.

Notes:

A preliminary document can be saved without any validation, if the user saves the document with the menu option park .
If the user selects the menu option check (before saving the document), then only the CO validations are triggered. (Note: If validation is passed the system puts in the profit center and fund center of the cost object(s) that where validated.)
If the user selects to save the document using the menu-option complete, both the CO and FI validations are triggered (Note: standard SAP does not trigger FI validations; this is achieved through an MIT modification).

SAP Application Area