Business Processes
When you deploy a BP design to Gateway, the system maps to the BP design, in Gateway, in two ways:
- Mapping to the existing, predefined, objects in Gateway.
- Mapping to a newly created object in Gateway, under Unifier Provider.
Mapping to a newly created object in Gateway requires that you:
- Use the dynamic object mapping, in Gateway, to map the newly created objects from Unifier Provider to an existing object in Gateway.
- or
- Create a new object in Gateway and map the Unifier Provider object to newly created object in Gateway.
The new objects created in Unifier Provider contain the following default information:
- Object name.
- Description that is added in the Unifier.
- Fields (including respective properties) associated with the design
Before you can use the object, you must configure the remaining information for the newly created object:
- Data related to Flow Type
- Cross-reference to the Gateway object
Once you complete mapping the object in Gateway, you can use the object for creating business flows in Gateway and use the data.
Configuring Unifier Objects on Gateway
By default, the mapping of data involves the following applications in order:
- Unifier
- Unifier Provider on Gateway
- Gateway Provider on Gateway
Mapping to a newly created object in Gateway requires that you match the information of that object in Gateway to the information of the object that you deployed from Unifier. In Gateway, once you find and select an object that you can use (i.e., an object that has matching information), you can proceed by cross-referencing the object in Unifier to the selected object in Gateway.
Default Gateway Objects
The following table lists the object names that are available for mapping in Gateway, by default, and provides a description:
Item | Object Name | Description |
|---|---|---|
1 |
| A company level purchase order, which enables agreements with vendors to provide services across multiple projects, released on a per-project/per-period basis with work authorizations against a previously determined maximum. |
2 |
| Line Items for Blanket Purchase Orders |
3 |
| Base Commit for EPC Activities (SOV = Payment Application) |
4 |
| Line Items for Contracts |
5 |
| To track money committed to be spent (General Spends type Base Commit) |
6 |
| Line Items for Purchase Orders |
7 |
| Process that is connected to Blanket Purchase Order Business Process that is deployed at company level. This process can be used to write against the blanket purchase order |
8 |
| Line Items for Work Releases |
9 |
| A formal commit change to the contract. |
10 |
| Line Items for Change Orders |
11 |
| Approval process for purchase order changes. |
12 |
| Line Items for PO Amendments |
13 |
| A general process for requesting and approving payments against commitments (invoice at the CBS or breakdown level, do not calculate retainage or stored materials) |
14 |
| Line Items for Invoices |
15 |
| A process to track your payment information using a standard payment application method (for example, tracking retainage, stored materials, past payments, etc.) |
16 |
| Line Items for Payment Applications |
17 |
| Used to create multiple project estimates and identify the preferred scenario. |
18 |
| Line Items for Estimates |
19 |
| Used to approve project budget |
20 |
| Line Items for Budget Approval |
21 |
| For requesting additional (or reduced) budget beyond the existing budget. |
22 |
| Line Items for Budget Changes |
23 |
| For transferring budget from one CBS code to another. Most typically used to release budget contingency to other cost items. |
24 |
| Line Items for Budget Transfers |
25 |
| Contractor initiated potential change order. |
26 |
| Line Items for Potential Change Orders |
27 |
| A process for adjusting spends line items. Most commonly used to reassign costs to alternate cost centers or GL codes; Generic spend to transfer across cost codes |
28 |
| Line Items for Journal Entries |
29 |
| BP to hold Checks Processed Information from Financial System. |
30 |
| Line Items for Payments |
31 |
| A log for documenting, tracking, and estimating impacts of open issues and risks; Log of items that may impact schedule/scope/cost |
32 |
| Line Items for Risks & Issues |
33 |
| Fund accounts as assigned to projects |
34 |
| Line Items for Fund Appropriations |
35 |
| Project attribute information |
36 |
| Document vendor performance for consideration for future work (Simple) |
37 |
| Company vendor directory |
38 |
| Line Items for Vendors |
39 |
| Used to capture Employee Timesheets (project / non-project hrs) |
40 |
| Line Items for Timesheets |
41 |
| A change of identical material or equipment |
42 |
| Line Items for Request for Substitution |
43 |
| A change to a budget that is typically created for a contractor that is based on changes to a contract between the contractor and owner. |
44 |
| Line Items for Budget Change Orders |
45 |
| A budget that is typically created for a contractor that is based on a contract they have with an owner for a project. |
46 |
| Line Items for Budget Items |
47 |
| A payment application that is raised by a contractor to the owner in order for the contractor to receive payment. |
48 |
| Line Items for Payment Applications to Owner |
49 |
| A record of the actual payments a contractor will have received from the owner based on the payment application they presented to the owner. |
50 |
| Line Items for Payments From Owner |
User-Defined Report (UDR)
Unifier displays a project-level/company-level UDR that is enabled for integration in the log page of the Business Objects node (Company Workspace > Admin mode > Gateway > Business Objects).
You can export data, generated out of a project-level/company-level UDR that is enabled for integration, to an Oracle/external application Provider through Gateway.
To export, you can select the listed UDR and click Deploy to send the data in the UDR to Gateway and use the data for integration with an Oracle/external application Provider.