As title stated , this post is about "What is AME "
AME is a web application providing following services to calling applications
1. A centralized repository for defining and sharing rules.
2. An execution engine to evaluate rules based on transaction specific data.
3. List management capabilities
4. History of approval Status.
In this post I will show a small demo ( Screen Shots) about Master Detail BPEL Flow with Human task flow activity .For this demo , I have created a Master Detail flow , Order Header (Master) and Order Lines (Detail).Below are the details about validation and data flow for the complete Process - Complete Flow - Master Detail with Human Task Flow.
How to design Approval Workflow based on Approval List generated in Oracle Approval Management (AME).
Recently I was working on requirement to design custom approval workflow based approval list generated by Oracle Approval Management (AME) module.
Approval List was based on
To fulfill the requirement, I have designed a workflow Approval Sub-process to send notification to the approvers, generated by Oracle Approval Management (AME) module and then plug that sub-process in the existing customer’s workflow process.
Below is sample workflow to implement AME (Oracle Approval Management) based approval list
1.Please make sure that you have required setup in approval management before you start working on your workflow (please refer my previous post on how to do the setup).Make sure that AME is integrated with calling Application ( application where you have your workflow).
2.Design your workflow Process and call AME APIs
There are many other APIS available to generate approval list , above 2 works well for me , you can pick any of those based on your requirement.
In my Workflow I have activity
·Start – to start the workflow.
·Initial Approval – this activity will determine
if approval is required or not .If it is required it then it call api Ame_Api2.Getnextapprovers1
to get the approval list from AME based on our setup and send the Approval
Notification to the First approver in the list by calling Notify approver.
·Notify Approver - if approver approve the
Notification , this process send a FYI type of notification to the Requestor
and execute the next activity ‘Get Next Approval’.
·Get Next Approval - this activity on execution first update the status of the Approver (whom we
send the notification) by mean of API AME_API.updateApprovalStatus2
(please note that this status will be updated in the AME and not in your
calling applications) and then call Ame_Api2.Getnextapprovers1 to get the next
approver .If Ame_Api2.Getnextapprovers1 return any further approver , then as
shown in workflow we loop back to
notification activity and perform same action , but in case there are no more
approver , execute the End activity and
complete the sub process.
This post is about how to transact an item that is defined in dual UOM in Order to cash Flow.
1. Define an Item with Dual Control
Primary UOM - Ea
Secondary UON - DZ (Dozen)
Conversion - 12Ea - 1DZ.
2. Create Sales Order
Line 3.1 in Primary UOMQty = 24 Ea
Line 4.1 in Secondary UOM Qty =3 DZ
3. Perform the Pick release and Ship confirm. Please Note that irrespective of Ordered UOM , Shipping will Shipped the item in Primary UOM only.
Once Ship Confirm executed ,Source requested Quantity(Ordered Qty) for Delivery details associated with line 4.1 was in Secondary UOM (3DZ) , but shipping still shipped in Primary UOM (ie 36 each).
4. Similarly Invoice Qty for Line 3.1 will be 24 ea and that for 4.1 will be 3 DZ.
In case your business requirement is to perform Invoicing in Secondary UOM , Order Should be created in Secondary UOM.Other solution is you can still placed Order in UOM and then customized your Invoicing report and display the Qty in Secondary UOM (Complex workaround).
This post is about how to transact an item that is defined
in dual UOM in Order to cash Flow.
1. Define an Item with Dual Control
UOM - Ea
UON - DZ (Dozen)
- 12Ea - 1DZ.
2. Create Sales Order
3.1 in Primary UOMQty = 24 Ea
4.1 in Secondary UOM Qty =3 DZ
3. Perform the Pick release and Ship confirm. Please Note
that irrespective of Ordered UOM , Shipping will Shipped the item in Primary UOM only.
Once Ship Confirm executed ,Source requested Quantity(Ordered Qty) for Delivery details associated with
line 4.1 was in Secondary UOM (3DZ) , but shipping still shipped in Primary UOM (ie
4. Similarly Invoice Qty for Line 3.1 will be 24 ea and that
for 4.1 will be 3 DZ.
In case your business requirement is to perform Invoicing in
Secondary UOM , Order Should be created in Secondary UOM.Other solution is you
can still placed Order in UOM and then customized your Invoicing report and
display the Qty in Secondary UOM (Complex workaround).
In 3rd post we will talk about Quoting Approval workflow processes.Oracle Quoting Approval Workflow has 4 Subprocess.
Start Approval (Main Process)
Start Approval (Main Process) -This Workflow process initiated in Oracle Quoting by calling workflow API wf_engine.createprocess .As explained in below slide show , Submit_Approval workflow activity in this work inturns calls child workflow process "Individual Approver" and after Initiating call to "Individual Approver", it progress to "Wait for flow " activity and wait for response from child sub-process"Individual Approver".
Once It receive Response from child process "Individual Approver" , it will process Further to "Check rejected" activity .If approver has rejected the notification ,"Check rejected" activity return "True" and Close the workflow , if it returns "False" , workflow further progress to activity "Submit Next Batch".
Submit Next Batch - This activity will check if all the requested approver has approved the Quote , if Yes It will move to next activity , else It will loop back to activity "Submit Approval"
Individual Approver - On execution, this subprocess calls the subprocess "Approver Process" Workflow , Once APPROVAL PROCESS subprocess executed successfully , it progress to next activity "Continue Flow " which in turns signal parent activity "Start Approval" to proceed further
Approver Process - This subprocess after validating few attribute call the subprocess "Notify approver" and based on the outcome of that it send Approve/Reject /Time out Notification.
Notify Approver - This Workflow Subrocess Record the Response of Approver.
For any further question , feel free to send me email/or leave comments.
This is Part -1 of 3 part blog post about Oracle Quoting and Approval Management.
Part-1 is about - How to Create and Approve Quote in Oracle Quoting.
Part-2 is about - Analysis of AME (Oracle Approval management ) approval process and how to create Attribute Conditions Action Types Rules to generate list of Approver to approve Quotes in Oracle Sales QQuoting
Part-3 is short discussion about the Workflow in Oracle Sales Quoting.
This is a very short demo about how to design graphs in BI/XML publisher Report. To build BI/XML publisher reports we should have a at least sample XML document, but in case your XML feed in not yet ready we can build a dummy XML document manually or use XSQL to build XML document , If found latter very easy , so will take later approach to build XML document.
Since focus here is how to build graphs in BI/XML publisher, I will not talk about how to integrate this with the Oracle Applications, for that you can refer my in depth posts on same subject
In this blog in will explain in brief about the New feature Item Orderability offered by Oracle Order management in R12.1.
Item Orderability - This is new feature introduced in Oracle R12.1.1.This is rule that user can define to restrict the items that can be ordered from the Sales Order form.
Because of the complex business scenario in the Modern time organization want to control which customer are allowed to order which product.
Now Order management Provide a new UI in R12.1.1 to define the rule to restrict the Item order, this UI is name as Item Orderability Rules.It allow user to Order the Item to customer based on the Rules.
As of Now Oracle has provided rules to control only the 11 attributes - like you can ally the restriction based on Customer Customer class Order types, Customer category etc.