Oracle SCM Cloud is the next generation Cloud solution for a multi-sourced Order to Cash Management system. The application now supports multiple order capture sources including Oracle CPQ Cloud, Oracle Commerce Cloud, EDI or other legacy systems and provide easy to configure Interfaces between these systems.

Capture, configure, and price orders where your business users set up all the product constraints and pricing rules. You can also automate, monitor, and manage the process from order capture to settlement to post-sales care all under a single Order Management Cloud System

Some of the key features offered by Order Management Cloud:

• Multi-Sourced OM System
• Order Promising and Supply Allocation (Global Order Promising System)
• Order Orchestration
• Exception Resolution
• Analytics based Reporting capabilities

Click on the link below to get an insight of how the Oracle Order Management cloud works:

http://www.ibizsoftinc.com/Demo/Oracle-ERP-Cloud/

Following image shows the entire workflow process in BPM which handles these different scenarios:

Leave Management BPM Workflow

Scenario A: If the Requestor is a General Secretary / Assistant of the General Secretary then the Leave gets approved without any request for Permission
Step1: First, the employee logins into the BPM workspace with the employee username and has access to the Leave Form to raise a Leave Request. Here the user enters the following details i.e. Request Type & Person Type. Once the details are entered click on Submit

Leave Form

The process tracking Audit Trail shows the process flow details

Audit Trail

In this scenario, since the Person Type is General Secretary no additional approvals are required and the Leave is created in Oracle eBS in the “Create record in EBS” process.

Step2: Next, user gets a Confirmation message stating his Leave has been created

Approval Status

The same can be verified in Oracle using the Employee Self-Service responsibility

Absence record created in EBS

Scenario B: If the Person Type is other than General Secretary and Request Type is Personal then the Leave Request should be forwarded to the Reporting Manager for Approval/Rejection
Step1: User requests for Leave with the appropriate details in the Leave Form

Leave form – Scenario B

Step2: The request is sent for Reporting Managers approval. The RM will get an Approval request. RM can choose to either Approve or Reject the request. Once the RM clicks on Approve the Leave record is created in eBS and confirmation is sent to the Requestor

Reporting Manager Approval

Step3: Leave record is successfully created in eBS

Absence record created in EBS – Scenario B

Step4: Once the Leave record is created the user is provide with a Confirmation message

Confirmation message

Step5: During Step2 the RM Approver can Reject the request as well. If he/she Rejects the request then no Leave record is created in eBS and the user gets a message stating the Request was Rejected.

Leave request Reject – Scenario B

Step6: User gets the status of the Request as REJECT

Rejection Message

Scenario C: If the Person Type is other than General Secretary and Request Type is Offical then the Leave Request should be forwarded to the Reporting Manager for Approval and then this request needs to be passed onto Department Manager for second level of Approval
Step1: User requests for Leave using Leave Form with Request Type as Official

Leave Request (Official) – Scenario C

Step2: Next, the RM will get a request to Approve/Reject. If RM chooses to Approve then this request will be forwarded to the Department Manager for his/her Approval/Rejection

RM Approval

Step3: Once RM approves the Request, this Leave Request is forwarded to Department Manager.

Department Manager Approval – Scenario C

Step4: Use gets a confirmation stating the Leave has been Approved

DM Approval Status