This appendix covers the following topics:
Oracle Project Manufacturing uses Oracle Workflow technology to provide guided walk-throughs of all steps required to define project manufacturing contract and indirect projects and to generate notifications for scheduling exceptions.
Oracle Workflow is a complete workflow management system that supports business process definition and automation. Its technology enables automation and continuous improvement to business processes, routing information of any type according to user-defined business rules. Oracle Workflow contains a graphical user interface that enables you to modify workflow processes to suit your business needs.
Oracle Project Manufacturing comes with the following workflows:
Project Manufacturing Project Definition [Contract] workflow guides you through the setup steps required to define a project manufacturing contract project. This workflow is seeded with one process, the PJM Contract Type Project Definition process.
Project Manufacturing Project Definition [Indirect/Capital] workflow guides you through the setup steps required to define a project manufacturing indirect or capital project. This workflow is seeded with one process, the PJM Indirect Type Project Definition process.
Project Manufacturing Project Schedule Exception Notification workflow allows you to define the notifications sent for schedule exceptions. This workflow is seeded with one process, the Project Manufacturing Integration Exception Process.
The PJM Contract Type Project Definition process provides a workflow-based approach to organize and launch the application forms needed to setup a project manufacturing contract project. The process provides sequential access to the needed windows from Oracle Projects, Oracle Master Scheduling, Oracle Work in Process, Oracle Cost Management, and Oracle Project Manufacturing.
The PJM Contract Type Project Definition process can be accessed through Oracle applications and through Workflow Builder. Use the Workflow Builder to customize the process.
Choose the Process tab on the navigator. The processes you can access are displayed on the upper left.
Select the PJM Contract Type Project Definition Process.
Processes can be customized using the Oracle Workflow Builder. When you customize the PJM Contract Type Project Definition process, only projects defined after you customize it are affected.
Choose Open from the File menu, and connect to the database.
Select Project Manufacturing Project Definition [Contract] to open it.
Expand the data source, then expand the item type Project Manufacturing Project Definition [Contract].
Expand the Processes branch within the item type.
Double-click on the PJM Contract Type Project Definition Process to the display the diagram in a process window.
There are no required modifications for this workflow process.
You can customize the PJM Contract Type Project Definition process by adding or deleting steps to the process, by changing process names and descriptions, and by changing step icons. For example, you might choose to remove Task Auto Assignment (step 16) from this process if your organization is at a project control level of task.
Each type of customization is supported for the PJM Contract Type Project Definition. However, the order of steps must take prerequisites for each form opened into account for the process to operate smoothly.
You can use the PJM Contract Type Project Definition process as a basis for developing your own project definition processes.
The PJM Contract Type Project Definition process is associated with an item type called Project Manufacturing Project Definition [Contract]. All the available processes associated with an item type are listed under that item type in the Workflow Builder. Currently, the only available process for this item type is the PJM Contract Type Project Definition process.
The Project Manufacturing Project Definition [Contract] item type has two attributes associated with it. These attributes reference information in the demonstration application tables. The attributes are used and maintained by function activities throughout the process.
| Display Name | Description | Type | Length/Format/ Lookup Type |
|---|---|---|---|
| User Name | Name of user defining project | Text | |
| Project Number | Number of project being defined | Text |
To view the properties of the PJM Contract Type Project Definition process, select the process in the navigation tree and choose Properties from the Edit menu. This process has a result type of None, indicating that when the process completes, it does not end with any particular result, such as End (Approved) or End (Rejected). Instead, its subprocesses end with specific results.
This process is runnable, indicating that it can be initiated as a top level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs.
The PJM Contract Type Project Definition process is designed to provide maximum flexibility for you. Hence, no step in the process is required in order to complete additional steps. You can select a project for which prerequisite steps have been completed before going on to the next step.
In order to provide this flexibility, the PJM Contract Type Project Definition process does not send message attributes from one step to the next.
The following is a description of each activity listed by the activity's display name.
This is a standard activity that marks the start of the process.
Function - WF_STANDARD.NOOP
Result Type - None
Prerequisite activities - None
Item Attributes Set by Function - None
This step opens the Oracle Project forms required to define a project.
Message - Define Project
Respond Message Attributes - Form PA_PAXPREPR_PROJECT
This step opens the Oracle Project forms required to define a project agreement.
Prerequisite Activities - Previous step
Message - Define Project Agreement
Respond Message Attributes -Form PA_PAXINEAG_AGREEMENT
This step opens the Oracle Project forms required to define a revenue budget.
Message - Define Project Revenue Budget
Respond Message Attributes - Form PA_PAXBUEBU
This step opens the Oracle Project forms required to review budget status for a project.
Message - Review Budget Status
Respond Message Attributes- Form PA_PAXBUEBU
This step opens the Oracle Project forms required to define cost budget for a project.
Message - Define Project Cost Budget
Respond Message Attributes -Form PA_PAXBUEBU
This step opens the Oracle Project forms required to review project approval.
Message - Review Project Status
Respond Message Attributes -Form PA_PAXPREPR_PROJECT
This step opens the Oracle Master Scheduling/MRP forms required to define a planning group.
Message - Define Planning Group
Respond Message Attributes -Form MRP_FNDLVMUL_PLANNING_GROUP
This step opens the Oracle Master Scheduling/MRP forms required to change the Inventory organization.
Message - Change Organization
Respond Message Attributes - Form MRPCHORG
This step opens the Oracle Work in Process forms required to define the WIP accounting class.
Message - Define WIP Accounting Class
Respond Message Attributes -Form WIP_WIPSUMCL
This step opens the Oracle Cost Management forms required to define the cost group.
Message - Define Cost Group
Respond Message Attributes - Form CST_CSTFDCGA
This step opens the Oracle Project Manufacturing form required to define the project parameters.
Message - Define Project Parameters
Respond Message Attributes -Form PJMFDPJP
This step refers you to Node 11 if additional organizations are desired for the project.
Message - Continue Setup in Another Inventory Org?
This step opens the Oracle Project Manufacturing form required to define the task auto assignment rules.
Message - Define Task Auto Assignment Rules
Respond Message Attributes -Form PJMFTAAR
The PJM Indirect Type Project Definition process provides a workflow-based approach to organize and launch the application forms needed to setup a project manufacturing contract project. The process provides sequential access to the needed forms from Oracle Projects, Oracle Master Scheduling/MRP, Oracle Work in Process, Oracle Cost Management, and Oracle Project Manufacturing.
The PJM Indirect Type Project Definition process can be accessed through Oracle applications and through Workflow Builder. Use the Workflow Builder to customize the process.
Choose the Process tab on the navigator. The processes you can access are displayed on the upper left.
Select the PJM Indirect Type Project Definition Process.
Processes can be customized using the Oracle Workflow Builder. When you customize the PJM Contract Type Project Definition process, only projects defined after you customize it are affected.
Choose Open from the File menu, and connect to the database.
Select Project Manufacturing Project Definition [Indirect/Capital] to open it.
Expand the data source, then expand the item type Project Manufacturing Project Definition [Indirect/Capital].
Expand the Processes branch within the item type.
Double-click on the PJM Indirect Type Project Definition Process to display the diagram in a process window.
There are no required modifications for this workflow process.
Customization Example
You can customize the PJM Indirect Type Project Definition process by adding or deleting steps to the process, by changing process names and descriptions, and by changing step icons. For example, you might choose to remove Task Auto Assignment, Node 12, from this process if your organization is at a project control level of task.
Each type of customization is supported for the PJM Indirect Type Project Definition. However, the order of steps must take prerequisites for each form opened into account for the process to operate smoothly.
You can use the PJM Indirect Type Project Definition process as a basis for developing your own project definition processes.
The PJM Indirect Type Project Definition process is associated with an item type called Project Manufacturing Project Definition [Indirect/Capital]. All the available processes associated with an item type are listed under that item type in the Workflow Builder. Currently, the only available process for this item type is the PJM Indirect Type Project Definition process.
The Project Manufacturing Project Definition [Indirect/Capital] item type has two attributes associated with it. These attributes reference information in the demonstration application tables. The attributes are used and maintained by function activities throughout the process.
| Display Name | Description | Type |
|---|---|---|
| User Name | Name of user defining project | Text |
| Project Number | Number of project being defined | Text |
To view the properties of the PJM Indirect Type Project Definition Process, you select the process in the navigation tree and choose Properties from the Edit menu. This process has a result type of None, indicating that when the process completes, it does not end with any particular result, such as End (Approved) or End (Rejected). Instead, its subprocesses end with specific results.
This process can be performed, which indicates it can be initiated as a top level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs. The PJM Contract Type Project Definition process is designed to provide maximum flexibility for you. Hence, no step in the process is required in order to complete additional steps. You can select a project for which prerequisite steps have been completed to go on to further steps. In order to provide this flexibility, the PJM Contract Type Project Definition process does not send message attributes from one step to the next.
The following is a description of each activity listed by the activity's display name:
This is a standard function activity that mars the start of the process.
Function - WF_STANDARD.NOOP
Result Type - None
Required - Yes
Prerequisite activities - None
Item Attributes Set by Function - None
Item Attributes Retrieved by Function - None
This step opens the Oracle Project forms required to define a project.
Message- Define Project
Respond Message Attributes- form PA_PAXPREPR_PROJECT
Send Messages Attributes
This step opens the Oracle Project forms required to define the cost budget.
Message- Define Cost Budget
Respond Message Attributes- Form PA_PAXIBUEBU
This step opens the Oracle Project forms required to review budget status for a project.
Message- Review Budget Status
Respond Message Attributes - Form PA_PAXIBUEBU
This step opens the Oracle Project forms required to review project approval.
message- Review Project Status
Respond Message Attributes- Form PA_PAXPREPR_PROJECT
This step opens the Oracle Master Scheduling/MRP forms required to define a planning group.
Message - Define Planning Group
Respond Message Attributes - Form MRP_FNDLVMUL_PLANNING_GROUP
This step opens the Oracle Master scheduling/MRP forms required to change the inventory organization.
Message - Change Organization
Respond Message Attributes - Form MRPCHORG
This step opens the Oracle Work in Process forms required to define the WIP accounting class.
Message - Define WIP Accounting Class
Respond Message Attributes - Form WIP_WIPSUMCL
This step opens the Oracle Cost Management forms required to define the cost group.
Message - Define Cost Group
Respond Message Attributes - Form CST_CSTFDCGA
This step opens the Oracle Project Manufacturing form required to define the project parameters
Message - Define Project Parameters
Respond Message Attributes - Form PJMFDPJP
This step refers you to Node 11 if additional organizations are desired for the project.
Message - Continue Setup in Another Inventory Org?
This step opens the Oracle Project Manufacturing form required to fined the task auto assignment rules.
Message - Define Task Auto Assignment Rules
Respond Message Attributes - Form PJMFTAAR
When you submit a Project Schedule Exception Notification request, Oracle Project Manufacturing uses Oracle Workflow technology in the background to handle the notification process. Oracle Workflow defines the approval notification options hierarchy available in the request parameters. You can use the Workflow Builder interface to modify your notification process.
The project manufacturing project schedule exception notification workflow consists of a single process, which is viewable in the Workflow Builder as a diagram. You can modify the objects and properties.
Processes can be customized using the Oracle Workflow Builder. When you customize the Project Manufacturing Project Schedule Exception Notification workflow, only those schedule exception notification requests that are submitted after you have customized it are affected. You can add or remove document types or alter the responsibilities to be notified for a given document type.
Choose Open from the File menu, and connect to the database.
Select PJM Project Schedule Exception Notification to open it.
Expand the data source, then expand the item type PJM Project Schedule Exception Notification.
Expand the Processes branch within the item type.
Double-click on the PJM Integration Exception Process to the display the diagram in a process window.
There are no required modifications for this workflow process.
You can customize the PJM Integration Exception process by adding or deleting steps to the process, by changing process names and descriptions, and by changing step icons.
Customization Example
You might choose to customize this process by adding planners or buyers to the notification cycle.
Each type of customization is supported for the PJM Integration Exception Process, however, the order of steps must take prerequisites for each form opened into account for the process to operate smoothly.
You can use the PJM Integration Exception Process as a basis for developing your own project definition processes.
The Project Manufacturing Integration Exception process is associated with an item type called Project Manufacturing Project Schedule Notifications. All the available processes associated with the item type are listed under that item type in the Workflow Builder. Currently, the only available process for this item type is the Project Manufacturing Integration Exception process.
The Project Manufacturing Project Schedule Notifications item type also has numerous attributes associated with it. These attributes reference information in the demonstration application tables. The attributes are used and maintained by function activities and notification activities throughout the process.
| Display Name | Type |
|---|---|
| Organization Name | Text |
| Document Type | Text |
| Date Type | Text |
| Tolerance Days | Number |
| Project Start Date | Date |
| Project End Date | Date |
| Task Start Date | Date |
| Task End Date | Date |
| Project Name | Text |
| Task Name | Text |
| WIP Job Name | Text |
| Job Start Date | Date |
| Job End Date | Date |
| Item Number | Text |
| Requestor | Text |
| Exception Subject | Text |
| Exception Body | Text |
| SO Number | Text |
| SO Requested Date | Date |
| SO Promised Date | Date |
| Forecast Name | Text |
| Forecast Start Date | Date |
| Forecast End Date | Date |
| Requisition Number | Text |
| Need by Date | Date |
| RFQ Number | Text |
| Due Date | Date |
| Quotation Number | Text |
| Effectivity Start Date | Date |
| Effectivity End Date | Date |
| MDS Name | Text |
| PO Number | Text |
| Requested Date | Date |
| Promised Date | Date |
| Release Date | Date |
| Project Number | Text |
| Task Number | Text |
| Status | Text |
| Quantity | Number |
| Job Type | Text |
| Start Quantity | Number |
| Quantity Completed | Number |
| Warehouse | Text |
| Ship to Location | Text |
| Ordered Quantity | Number |
| Delivered Quantity | Number |
| Forecast Set | Text |
| Project Manager | Role |
| Task Manager | Role |
| Open Form | Form |
| Item Description | Text |
| Line Number | Text |
To view the properties of the Project Manufacturing Integration Exception Process, select the process in the navigation tree and choose Properties from the Edit menu. This process has a result type of None, indicating that when the process completes, it does not end with any particular result, such as End (Approved) or End (Rejected). Instead, its subprocesses end with specific results.
This process is runnable, indicating that it can be initiated as a top level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs. The workflow begins at node 1. At node 2, this workflow branches depending on whether the document is a WIP, SO, Forecast, PR, RFQ, quotation, MDS, MPS, purchase order, or blanket release exception notification. If a choice is not made, the process is initiated for all options. At nodes 3, 9, 15, 21, 27, 33, 39, 45, 51, and 57 the workflow notifies the requestor and locates the appropriate project manager for notification. At nodes 4, 10, 16, 22, 28, 34, 40, 46, 52, and 58 the workflow locates the appropriate project manager for notification. At nodes 5, 11, 17, 23, 29, 35, 41, 47, 53, and 59 the workflow sends notification to the appropriate project manager. At nodes 6, 12, 17, 24, 30, 36, 42, 48, 54, and 60 the workflow locates the appropriate task manager for notification. At nodes 7, 13, 18, 25, 31, 37, 43, 49, 55, and 61 the workflow sends notification to the appropriate task manager.
The following is a description of each activity listed by the activity's display name. You can create all the components for an activity in the graphical Workflow Builder except for the PL/SQL stored procedures that the function activities call. All function activities execute PL/SQL stored procedures which you must create and store in the Oracle RDBMS. The naming convention for the PL/SQL stored procedures is:
<PACKAGE>.<PROCEDURE>
<PACKAGE> is the name of the package that groups all of the procedures.
<PROCEDURE> represents the name of the procedure.
To view the package and procedure names used by the Project Manufacturing Integration Exception process, view the Properties page for each function activity. For example, the function activity Set Document Type uses the <PACKAGE.<PROCEDURE> name PO_APPROVAL_REMINDER_SV.SET_DOC_TYPE
This is a Standard function activity that simply marks the start of the process.
This function activity determines the document type: WIP, SO, Forecast, PR, RFQ, quotation, MDS, MPS, purchase order, or blanket release exception notification.
Nodes: 3, 9, 15, 21, 27, 33, 39, 45, 51, and 57. This activity sends schedule exception notification to the requestor.
Nodes: 4, 10, 16, 22, 28, 34, 40, 46, 52, and 58. This activity locates the appropriate project manager(s) for notification.
Nodes: 5, 11, 17, 23, 29, 35, 41, 47, 53, and 59. This activity sends schedule exception notification to the project manager(s).
Nodes: 6, 12, 17, 24, 30, 36, 42, 48, 54, and 60. This activity locates the appropriate task manager(s) for notification.
Nodes: 7, 13, 18, 25, 31, 37, 43, 49, 55, and 61. This activity sends schedule exception notification to the task manager(s).