People and compliance on Oracle Fusion

Health, safety and environment incident on Oracle Fusion Cloud

Takes a safety or environmental incident from a report on a phone through classification, investigation and corrective actions to closure, with the regulator report where the rules require one.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 ReportS02 ClassificationS03 InvestigationS04 ActionsS05 Regulator reportS06 HSE boarddh_employeeEmployeeHCM REST: workers · assignmentsdh_equipmentEquipmentMaintenance REST: maintenanceAssetsdh_maintenance_orderMaintenance orderMaintenance REST: maintenanceWorkOrdersdh_cost_centerCost centerGeneral Ledger: chart of accountssegment values (REST: valueSets)dh_supplier_masterSupplier masterProcurement REST: suppliers ·supplierSitesWRITE BACK TO ORACLE FUSIONMaintenance order → POST/PATCH maintenanceWorkOrdersEquipment → PATCH maintenanceAssetsrows stay in Oracle Fusion · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Oracle Fusion object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Oracle Fusion objects behind each handler

Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.

ObjectRead fromFields the app usesFreshness
EmployeeHCM REST: workers · assignmentsPersonNumber (id) · DisplayName (name) · DepartmentName (org unit) · PositionCode (position)live through the API
EquipmentMaintenance REST: maintenanceAssetsAssetNumber (id) · AssetDescription (desc) · LocationCode (location) · SerialNumber (serial)live through the API
Maintenance orderMaintenance REST: maintenanceWorkOrdersWorkOrderNumber (number) · AssetNumber (equipment) · WorkOrderType (type) · Priority (priority)live through the API
Cost centerGeneral Ledger: chart of accounts segment values (REST: valueSets)Value (id) · Description (name) · Attribute (owner) (owner) · Ledger / legal entity (company)live through the API
Supplier masterProcurement REST: suppliers · supplierSitesSupplierNumber (id) · Supplier (name) · Country (country) · Status (block)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: Anyone on site submits S01 on the mobile screen, for an incident or a near miss.

This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.

Start

Anyone on site submits S01 on the mobile screen, for an incident or a near miss. The instance then reads its rows from Oracle Fusion through the handlers above.

What the app writes back

Through released interfaces

Writes use the same released REST resources (POST and PATCH) with the integration user's data-security profile. Each call returns the document identifier or an error message, and the app records both beside the decision.

ObjectWhat changesInterface
Maintenance ordermaintenance order created for a corrective action on the equipment, with the incident number as referencePOST/PATCH maintenanceWorkOrders
Equipmentequipment set to out of service when the site manager takes it off linePATCH maintenanceAssets
Acknowledged and logged

Each write stores the identifier Oracle Fusion returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

Oracle roles and data-security policies are mapped to Lima access policies once. A buyer scoped to a business unit in Oracle sees the same rows in the app.

  • An integration user with the REST resource roles for the objects the app reads and writes
  • BI Cloud Connector offerings enabled for the objects that need history at scale
  • Allowed IP or private connectivity to the pod
  • Business-unit and inventory-organisation scopes agreed with the process owner
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on Oracle E-Business Suite

The same app on Oracle E-Business Suite

On Oracle E-Business Suite the same objects live in the tables named beside each row and are read in place through JDBC with a read-only user; writes go through the open interface tables and public APIs, run by a concurrent program.

ObjectOn Oracle FusionOn Oracle E-Business Suite
EmployeeHCM REST: workers · assignmentsPER_ALL_PEOPLE_F · PER_ALL_ASSIGNMENTS_F
EquipmentMaintenance REST: maintenanceAssetsEAM: MTL_SERIAL_NUMBERS · EAM_ASSET_ATTRIBUTES
Maintenance orderMaintenance REST: maintenanceWorkOrdersWIP_DISCRETE_JOBS (EAM work orders)
Cost centerGeneral Ledger: chart of accounts segment values (REST: valueSets)GL_CODE_COMBINATIONS · FND_FLEX_VALUES
Supplier masterProcurement REST: suppliers · supplierSitesAP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT)
Nearby

This app on other systems, and other apps on Oracle Fusion

Health, safety and environment incident on

Other apps on Oracle Fusion

Terms on this page

Near missAn event that could have caused injury or damage; reported and investigated like an incident.
Lost-time injuryAn injury that keeps the person away from work for at least 1 full shift; it usually requires a regulator report.
Read in placeThe rows stay in Oracle Fusion; the handler sends the filter and the columns and Oracle Fusion returns the matching rows.
Questions

Does this app copy data out of Oracle Fusion?

The screens read through handlers that leave the rows in Oracle Fusion. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does Oracle Fusion need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on Oracle E-Business Suite as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.