Previous Next JavaScript must be enabled to correctly display this content

## 4 Supported Archival Usecases

This topic explains intraday tasks that operate throughout the day according to the set frequency.

Oracle Banking Virtual Account Management comes with various audit archival settings. You can review these configurations in the Oracle Banking Microservices Platform Foundation User Guide, and they can be scheduled through the Jobs listed below.

Note:

Every job mentioned is linked to a subdomain that handles all configured and pre-installed Task Flows. One scheduling setup is enough for each job.

1. ArchivalJobVAM

Archival control name - plato_event_control

This archival flow is used to archive events generated by obvam-account-service along with their associated sub-records. Records become eligible for archiving when their creation date is older than the specified retention period.

Archival control name - obvam_uncollected_control

This archival flow is used to archive uncollected transactions along with their associated sub-records. Records become eligible for archiving when the actual release date of the transaction is older than the specified retention period.

Archival control name - obvam_account_control

This archival flow is used to archive virtual account records along with their associated sub-records. Records become eligible for archiving when the virtual account is closed and its last checked date is older than the specified retention period.

2. ArchivalJobVAS

Archival control name - dashboard_event_control

This archival flow is used to archive events received by obvam-statement-service and obvam-projection-service along with their associated sub-records. Records become eligible for archiving when the date of receiving the event is older than the specified retention period.

Archival control name - obvam_statement_control

This archival flow is used to archive statement details after generation along with their associated sub-records. Records become eligible for archiving when the current branch date is older than the specified retention period.

3. ArchivalJobVAT

Archival control name - transaction_jrn_control

This archival flow is used to archive transaction journal records along with their associated sub-records. Records become eligible for archiving when the booking date of the transaction is older than the specified retention period.

4. ArchivalJobVAN

Archival control name - internal_transfer_control

This archival flow is used to archive internal transfer records along with their associated sub-records. Records become eligible for archiving when the booking date of the transaction is older than the specified retention period.

5. ArchivalJobEIE

Archival control name - obvam_interestliq_control

This archival flow is used to archive interest liquidation transactions along with their associated sub-records. Records become eligible for archiving when the interest is liquidated and its last checked date is older than the specified retention period.

6. ArchivalJobVAE

Archival control name - obvam_entity_control

This archival flow is used to archive virtual entity records along with their associated sub-records. Records become eligible for archiving when the virtual entity is closed and its last checked date is older than the specified retention period.

7. ArchivalJobVAC

Archival control name - obvam_facility_control

This archival flow is used to archive customer account product records along with their associated sub-records. Records become eligible for archiving when the customer account product is closed and its last checked date is older than the specified retention period.

8. ArchivalJobVAI

Archival control name - obvam_remit_details_control

This archival flow is used to archive remittance details records along with their associated sub- records. Records become eligible for archiving when the remittance detail is closed and its last checked date is older than the specified retention period.

Archival control name - obvam_remit_list_controll

This archival flow is used to archive remittance list records along with their associated sub- records. Records become eligible for archiving when the remittance list is closed and its last checked date is older than the specified retention period.

Archival control name - obvam_idmap_control

This archival flow is used to archive multi-currency identifier mapping records along with their associated sub- records. Records become eligible for archiving when the identifier mapping is closed and its last checked date is older than the specified retention period.

Archival control name - obvam_corp_rule_control

This archival flow is used to archive corporate specific rule records along with their associated sub- records. Records become eligible for archiving when the corporate specific rule is closed and its last checked date is older than the specified retention period.