Search 800 + Posts
Oct 30, 2010
Reference Sales Order for RMA
This post is about the status of Sales order that we want to refer in RMA.
If we want to refer an outgoing sales order line in an RMA, then the line of the outgoing order should be at least booked. Logically speaking the outgoing line should be ship confirmed/Closed at the time of RMA,otherwise why we want to create RMA for outgoing order line that is not shipped.In oracle Applications system will not let you reference an outgoing order line in RMA unless outgoing line is atleast Booked .
- Posted using BlogPress
What if we lost reservation on a line
Once in a while I have noticed that Order Line lost reservation on a booked order line even when delivery details has released_status = staged.
Now because of lost of reservation , reserved qty column is null in sales order form as well as when I check the data in table mtl_reservation there is no data with
demand_source_line_id = order_line_id.
Due to lost reservation on order line, stock that was earlier reserved for this particular line now picked up by another sales orde line , that results in confusion and delay .
NOW one quick fix for such issue is Navigate to order >> order lines >> TOOLS
select SCHEDULING >> RESERVATIONS DETAILS and populate the qty that you have lost in the quantity field ( in am assuming we have stock , with out stock we will not be able to RESERVE quantity ) , Once done we are ready for ship confirm.
Hope that helps.
How to Enter Serial No. for RMA Order from Sales Order UI
In R12i Oracle has Introduced a New feature to Enter the Serial Numbers for the Serial Control Items on RMA Order from the Sales Order UI( user Interface).
This is Short Post (Supported with Presentation) about this feature and explain Navigation streps about How to Enter the Serial number for Serial Control Items for Return Sales Order(RMA) for the Serial Control Items.
For additional info on How to Define Serial Control Items , please refer How to define Serial Control Items
Hope that Helps. Don't forget to leave your feedback. Your feedback is very important.
This is Short Post (Supported with Presentation) about this feature and explain Navigation streps about How to Enter the Serial number for Serial Control Items for Return Sales Order(RMA) for the Serial Control Items.
For additional info on How to Define Serial Control Items , please refer How to define Serial Control Items
Serial numforreturnorder
View more presentations from eoracleapps.
Hope that Helps. Don't forget to leave your feedback. Your feedback is very important.
Oct 28, 2010
Sales Order and RMA with Serial Control Items
This is a short Power Point Presentation in SharePoints , about how to define Serial Control Items in Oracle Inventory Module and then how to use Serial Number while Creating Sales Order and RMA Orders.
I have explained everything in Power Point Presentation,Any feedback will be highly appreciated.
Serial controlitem
View more presentations from eoracleapps.
I have explained everything in Power Point Presentation,Any feedback will be highly appreciated.
Oct 27, 2010
Order Header is in Closed Status , even when all the Order lines are cancelled
Many a times we have notice that Order Header has value FLOW_STATUS_CODE = 'Closed', open_flag ='N', where as all the lines associated with the Order Header in status Cancelled. FLOW_STATUS_CODE ='Cancelled', Open_flag = 'N' and Cancelled_flag ='Y', well that's what we expect from the system. Though that is the expectations , but many a time user debate that since all the orders lines are cancelled , order header should be in Cancelled status and NOT in Closed status.
Please Note that if we cancelled the order header , in that case cancellation process will cancel all the open lines and then cancel the order header and set the Header flow status code = cancelled and cancelled flag = Y and open_flag = N.
But the case that we are discussing here is not the cancel order process, here we have not cancelled the Order Header rather we have cancel all the line.Please note that when we cancel a order line , it cancels(if possible) the order line and associated delivery details (if possible) and then execute the "CLOSE LINE" workflow process to set the cancel flag = Y and flow_status_code = Y, and at the same time it let the Order header workflow knows that this line is cancelled and open_flag = N.
Thus the moment last order line got cancelled and inform order header that openflag for it is N , order header workflow evaluate that if there are no more open lines , it progress towards the Close Order process and close the Order ( if you have setup close the order header when all the lines has open_flag = N) .That is the reason when you query such order you can see the Order STATUS as CLOSED and NOT the CANCELLED. Please note that cancelling all lines are different from the Cancel Order .
In Cancel order we explicitly tell the system to cancel the order , but if you cancel all the order lines individually , system will not considered that action same as that of Close Header.
Hope that helps
Please Note that if we cancelled the order header , in that case cancellation process will cancel all the open lines and then cancel the order header and set the Header flow status code = cancelled and cancelled flag = Y and open_flag = N.
But the case that we are discussing here is not the cancel order process, here we have not cancelled the Order Header rather we have cancel all the line.Please note that when we cancel a order line , it cancels(if possible) the order line and associated delivery details (if possible) and then execute the "CLOSE LINE" workflow process to set the cancel flag = Y and flow_status_code = Y, and at the same time it let the Order header workflow knows that this line is cancelled and open_flag = N.
Thus the moment last order line got cancelled and inform order header that openflag for it is N , order header workflow evaluate that if there are no more open lines , it progress towards the Close Order process and close the Order ( if you have setup close the order header when all the lines has open_flag = N) .That is the reason when you query such order you can see the Order STATUS as CLOSED and NOT the CANCELLED. Please note that cancelling all lines are different from the Cancel Order .
In Cancel order we explicitly tell the system to cancel the order , but if you cancel all the order lines individually , system will not considered that action same as that of Close Header.
Hope that helps
Oct 21, 2010
Oracle Sales Order Line Workflow – Fulfill Activity (Internal name – FULFILL_LINE) Errors
Most of the workflow for Sales Order line has this activity, this activity is just before the Invoicing Sub process and indicate that the line is ready for fulfillment, PL/SQL API OE_FULFILL_WF.START_FULFILLMENT for this activity perform various validation and then populate the fulfill Quantity and fulfill flag on the sales Order line.
Fig 1-1
But another important feature of this activity is, this activity has 4 Attributes associated with it, Go to Node Attribute tab and you will see
Fig 1-1
But another important feature of this activity is, this activity has 4 Attributes associated with it, Go to Node Attribute tab and you will see
Oct 20, 2010
Drop Ship Order Stuck with Awaiting Receipt Status
In this post I will discuss about Drop Ship Order stuck with 'Awaiting Receipt' Status.There could be 100s of reason for order line stuck at this status,But here I will discuss the case where
With PO is received , our expectations are that Order line workflow should progress to Deferred Fulfill Status, same was mine , but when I learnt from user that Order Line is not moving , I Start digging around and notice some very intyeresting fact.
As per user , they have deleted /canceled the PO Shipment Created from the drop ship sales order and Created a New Shipment and Received the Quantity against the Newly created Shipment . Well with above scenario NOWAY order line will progress from AWAITING RECEIPT satatus and it will stuck there for ever.
let me explain -
As soon as user deleted the PO shipment , link between OM and PO broken ( PO data in the oe_drop-ship_sources got nullified) , though data of requisition still there in this table.
After that when user created the New Shipment , it was no more a dropship Shipment, rather is is just a normal Shipment Created for PO , that was the reason when user received this shipment it fails to progress the Order line.
Solution - First of all don't do like this , if you have some issue with the Quantity , then update the Order line, and if you are in R12.1.1 this change will automatically reflect in PO , but if you are in 11i you need to make this change manually.
Now to fix this issue ,create the PO with auto create ( as data for requisition is still in oe_drop_ship-sources_all) ,Once PO created , approve and receive the PO , receiving(RTP) will automatically push the Order line from SHIP_LINE -Notified status to Defer fulfill and Order line status will change from AWAITING-RECEPIT to RETURNED.
Hope that helps
- Order Line is at Status = Awaiting Receipt
- Order line workflow is at SHIP_LINE - NOTIFIED
- Requisition is Created and Approved.
- Purchase Order is Created /Approved.
- Receipt is Already Created.
With PO is received , our expectations are that Order line workflow should progress to Deferred Fulfill Status, same was mine , but when I learnt from user that Order Line is not moving , I Start digging around and notice some very intyeresting fact.
As per user , they have deleted /canceled the PO Shipment Created from the drop ship sales order and Created a New Shipment and Received the Quantity against the Newly created Shipment . Well with above scenario NOWAY order line will progress from AWAITING RECEIPT satatus and it will stuck there for ever.
let me explain -
As soon as user deleted the PO shipment , link between OM and PO broken ( PO data in the oe_drop-ship_sources got nullified) , though data of requisition still there in this table.
After that when user created the New Shipment , it was no more a dropship Shipment, rather is is just a normal Shipment Created for PO , that was the reason when user received this shipment it fails to progress the Order line.
Solution - First of all don't do like this , if you have some issue with the Quantity , then update the Order line, and if you are in R12.1.1 this change will automatically reflect in PO , but if you are in 11i you need to make this change manually.
Now to fix this issue ,create the PO with auto create ( as data for requisition is still in oe_drop_ship-sources_all) ,Once PO created , approve and receive the PO , receiving(RTP) will automatically push the Order line from SHIP_LINE -Notified status to Defer fulfill and Order line status will change from AWAITING-RECEPIT to RETURNED.
Hope that helps
Oct 1, 2010
How to Create WSDL Web Services with Oracle AS Adapter for Oracle Applications.
This is a shot presentation about How to design/Deploy Web Services with Oracle AS Adapter for Oracle applications.Here I will cover ONLY , how to Create web Service with Interface type as PL/SQL type Inter. These Adapter are very useful for Integrating Oracle Applications with Oracle / Non-Oracle Systems and they made the Integration process very easy and simple.
Demo- Demo in the Post is about How to Delete the Sales Order line from Oracle Order Management System using Web-Service designed by means of Oracle AS Adapter.
OracleAS Adapter for Oracle Applications provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications. The Adapter supports Release 12 and Release 11i of E-business Suite.
OracleAS Adapter for Oracle Applications enables you to orchestrate discrete data into a meaningful business process and creates WSDL Web services for various interface types within Oracle E-Business Suite. It plays the role of service provider for Oracle E-Business Suite to allow seamless integration between business partners, processes, applications, and end users in heterogeneous environment.
Demo- Demo in the Post is about How to Delete the Sales Order line from Oracle Order Management System using Web-Service designed by means of Oracle AS Adapter.
OracleAS Adapter for Oracle Applications provides comprehensive, bidirectional, multimodal, synchronous, and asynchronous connectivity to Oracle Applications. The Adapter supports Release 12 and Release 11i of E-business Suite.
OracleAS Adapter for Oracle Applications enables you to orchestrate discrete data into a meaningful business process and creates WSDL Web services for various interface types within Oracle E-Business Suite. It plays the role of service provider for Oracle E-Business Suite to allow seamless integration between business partners, processes, applications, and end users in heterogeneous environment.
Subscribe to:
Posts (Atom)