BiLog: Got Game? Got Audit Requirements? And want to run reports?
PamDenny 270000BXV7 Comments (2) Visits (6053)
Got Game – Holiday Game? Game
from cheering on the Packers, maximizing your consumption of apple or pumpkin
pie, or Game from braving the crowds on Black Friday? My game came into play last week in a
Lasertron Match with over 40 family members after an incredible Thanksgiving
Day Feast. While my phaser accuracy would cause teammates
to cry for trades, our family had an amazing time in our annual, Buffalo tradition.
As we turn from holidays back to the work week, we change from Got Game to Got Audit Requirements. Many clients have internal and regulatory tracking requirements on their data, and to comply with the requirements, reports are often used.
One of the 150 plus reports delivered with the Version 7 products is the eAudit report. This report details the eAudit Transactions within a given time period for the selected database objects and attributes. However, what makes this report unique is that its sql is dynamic as the user selects any 'Auditable' Version 7 objects and attributes at run time. You can find more details on this report and other Version 7 reports by accessing the Version 7 Report booklets detailed here.
If this delivered report does not meet your unique business
needs for audit compliance, you could quickly create an ad hoc report. To highlight how you can quickly do this,
we’ll imagine you have to deliver a report with audit data in the Asset
application. To recap, when you create an ad hoc report using multiple database objects, you must have a corresponding report object structure (ROS). You can find these described in more detail here.
Since we will be including data from both the base Asset object and its corresponding audit object, A_ASSET, we first need to create an ROS for those two database objects. ROS join database objects together via maxrelationships - so before we create the ROS - we need to confirm a relationship between the parent ASSET object and the child A_ASSET object exists.
1. To do this, go to the Database Configuration application and filter on the asset application. In the relationships tab, filter to see if there is a relationship to A_ASSET. In this case, a relationship wasn’t available out of the box, so one was created as shown below.
2. Next, navigate to the Object Structure application to add a new ROS. This ROS will enable you to create audit ad hoc reports from the Asset application, so its parent is ASSET, and the child is A_ASSET. It uses the new relationship created above to join the ASSET and A_ASSET objects together.
3. Then, grant security access to the new Asset Audit report object structure in the Report Administration application. You can enable this by selecting the 'Set Report Object Structure Security' from the Action menu.
4. Now, you can begin building your custom ad hoc report using the new Asset Audit ROS you have created as shown below. You can then save this report, share it with others and also schedule it to execute on a regular basis.
You can find additional details on this example here
The delivered eAudit report and Ad hoc reporting audit capability give you a variety of options to meet your audit requirements.
Got Game? Got Audit Requirements? With Version 7.....multiple report options give you multiple tools to master those requirements.