Requried table and API permissions for Qbyte integration
Aucerna Execute includes out-of-the-box integration with Qbyte FM.
- Manual push of AFE header information into Qbyte (usually after the AFE release for approval, or when it becomes internally approved)
- Manual or scheduled import of actual costs from Qbyte
- (optional) Export of calculated accruals from Aucerna Execute for import into Qbyte
Writes to Qbyte are performed using the Qbyte Connect API (which must be purchased separately from P2). Reads take place against the Qbyte tables directly.
Typically, users will create a separate integration user account in Qbyte and grant the following privileges to that user. Aucerna Execute would then be configured to connect to the Qbyte Oracle database using this integration user account.
Aucerna Execute requires EXECUTE privileges on the following Qbyte Connect API packages:
- AFES_API
- REPORTING_ENTITIES_API
- CAPITAL_OVERHEAD_API
- JOINT_OVERHEAD_AGREEMENTS_API
Aucerna Execute also requires SELECT permissions on the following Qbyte tables:
- AUTHORIZATIONS_FOR_EXPENDITURE
- AFE_DESCRIPTIONS
- OPERATOR_AFES
- AFE_LEGALS
- COST_ESTIMATE_ITEMS
- AFE_APPROVALS
- AFE_SUPPLEMENTS
- AFE_REVISIONS
- AFE_PROJECT_JUSTIFICATIONS
- REPORTING_ENTITIES
- CAPITAL_OVERHEAD_LINKS
- JOINT_OVERHEAD_AGR_PROPERTIES
- AFE_ACTUALS
- MAJOR_ACCOUNTS
If you receive an error message when logging into Data Navigator please double check the API privileges and permissions for your Qbyte integration user and contact P2 to grant the missing privileges.