Sample Intercompany Transactions Task Flow

Before you can work with transactions, the administrator must open the periods for the transactions. Administrators can also set matching requirements, specify intercompany matching tolerance values, and define reason codes to indicate the reason for mismatched transactions. See the Oracle Hyperion Financial Management Administrator's Guide.

Table 10-1 Sample Intercompany Transactions Task Flow

Task	Description
Manage reason codes	The administrator defines reason codes in the application to be used for the intercompany matching process. Users can select from this list when processing intercompany transactions.
Open period for intercompany transactions	Before you can perform any action on intercompany transactions, the administrator must open the transaction periods. During this process, the administrator also defines the Match/Validate Before Posting requirement and the matching tolerance to be used for the matching process.
Load transactions	You can load transactions into the system from external ASCII files. You can also enter transactions manually.
Manage transactions	You can view the list of transactions, change the entity and partner selections, and select other filtering criteria to view transactions.
Edit transaction	You can make changes to a transaction, such as adding comments to the transaction.
Run transaction report	You can run a transaction report to view a list of transactions based on the filter criteria.
Run matching report by transaction ID	Before performing the matching process, you can run the matching report to see which transactions are to be matched.
Auto-match by transaction ID	You can match transactions using the transaction ID or the reference ID. The system updates the transactions with a matched status and matched code. You can also save the matching settings to a matching template to be used later.
Run matching report by account	This is another option to view the matching transactions report where the transactions are matched based on the accounts instead of a transaction or invoice.
Auto-match by account	This option is useful to match transactions when the application does not have an exact match of transaction ID and detail. To avoid a possible mismatch, you can perform auto-matching by ID first, then auto-matching by account.
Perform manual match of transactions	After you perform the auto-match process, you might find some transactions that should be matched even though they do not fit the matching criteria for the process. You can select certain transactions and manually match the transactions. The matching process updates the matched status and assigns a matched code.
Perform unmatch of transactions	During the matching process, you might need to unmatch certain groups of transactions manually. When you select a transaction, the system displays the group of transactions that have the same matched code. You can then unmatch all transactions within the same matched group.
Post transactions	After all transactions have been matched and you are ready to post the transactions to the system, you can select the transactions to post.
Run transaction report	After you post transactions, you can create a transaction report to view the status of each transaction. This report contains information on the posting status, and posting user, date and time. This can be used as a summary report so that you can quickly view the posting information.
Lock entities	The administrator can lock entities to prevent users from adding new transactions or making changes to specific entities. When the entity is locked, no more matching can done for that entity, and no additional transactions can be posted for the entity.
Drill down to transaction details from the Intercompany Matching System Report	After you post transactions and the intercompany accounts reflect the account balance of these transactions, you can run the Intercompany Matching System Report to view the matching at the account level for individual transactions.
Drill through to transaction details from data grids or data forms	When you are in a data grid or data form, you can view the corresponding intercompany transactions. You cannot modify transactions from data grids or forms.
Close period	At the end of the closing cycle after you finish processing intercompany transactions, the Intercompany Administrator closes the period to prevent additional modifications to the transactions for the period. If the Match/Validate Before Post option is selected for the period, all matched transactions or mismatched transactions with a reason code must be posted before the period can be closed. When you close a period, the period is locked for future transactions, however, you can continue to view transactions or run reports on transactions from the period.