Sunday, November 28, 2010
Oracle apps Form Personalisation Debugging Steps
Then we end up wasting most of the time checking and testing why it is not working.
In this article i will be covering how to debug the form personalisation .
WHY FORM PERSONALISATION IS NOT WORKING?
A rule or action may not run for a variety of reasons:
a.The Rule or Action is not enabled
b.The Condition has evaluated to FALSE
c.The Trigger Event and/or Trigger Object were not what you expected
The scope of the rule only consists of Responsibility, Industry and/or User, and none is true for the current context
d.An action is executing the Builtin 'RAISE FORM_TRIGGER_FAILURE' . That will abort all further processing for that event.
e.The Language of the Action, if not ‘All’, is different than what you are currently running
f.You have set Custom Code to ‘Off’ or ‘Core code only’ in the pulldown menu.
g.Rules are created for a Function. You might be running the same form, but as a different function.
h.You need to re-open the form so that the new personalization get applied.
To test whether its running or not
There can be a case that form personalisation is running but it is not working. So to test that Create a message type of 'SHOW' and add some useful test after the interested action.
Now re-run the form and you will be able to see the message when that event occurs.
Form Personalisation is running and action is getting fired but personalization is not getting applied.
Often an Action may execute, but by the time control returns to the user the property you set has been overridden. What can you do?
Try performing the action at a ‘lower’ event.
Properties that affect all records of a block: set at WHEN-NEW-BLOCK-INSTANCE or WHEN-NEW-RECORD-INSTANCE
Properties that affect a specific item in a block: set at WHEN-NEW-ITEM-INSTANCE
The downside of the ‘lower’ events is that they fire more frequently
Another Method of Debugging the Form Personalisation is to set teh debug to step-by-step .
This help in knowing the exact condition getting processed and the result after evaluation of the conditions
Now It will pop up the message every time a trigger or its condition is getting evaluated.
This way you can easily debug the form personalisation .It will be also helpful in getting more insight on how a personalisation is getting fired and why it is nt getting fired.
Please leave a comment in case you like this or need more details .
I will get back to you
Friday, November 26, 2010
BACK TO BACK FLOW in Order Management -Oracle apps
I have researched across the various site and have compiled the Back to Back Order Management Flow.
Why Back to Back ?
1.Data Integration
2.Lower Inventory
3.Lower inventory cycle
4.Can offer a variety of products
5.Link supply to Specific demands -pegging -hard reservations
6.Focus on Product Design
Customer orders product that one do not stock as well as do not even manufacture. So in this case one want to purchase the item that customer orders and then Supplier ship it to you, and you send it it to the customer. This process is called "back-to-back" or "procure-to-order".
SET UP
1.Define Back-t0-Back(b2b) Item
Use the Inventory Master Items to define the b2b items
a) In the Order Management tab , item must be marked as Customer Orderable , Assemble to Order.
b)In the Purchasing Tab , item must be marked as purchasable and value is provided in the List price field.
c)Item must be marked as ‘Build in WIP’ on the WIP tab
d)In the General Planning tab, set the Make or Buy flag to Buy
2.Assign the item to the pricelist..
Processing of Order
1.Enter the b2b item , keep the source type as Internal and book the Order.
2.Line will go to supply Eligible Status.
3.Place cursor on the line and go to Actions > Progress Order. Select Create Supply Order - Eligible to progress the workflow of the line
This takes info from the Sales Order line and loads the Requisition Import interface tables. The line status will show as PO Req requested.Purchasing Flow
If you want to see the Requisition number or Purchase Order number created by your Sales Order line, you must go to the Reservations Details form to find that information
1.Now Requisition Import is run to create the purchase requisition tied to the sales order line. This can be done by either manually submitting the Requisition Import concurrent program or scheduling it to run automatically.Requisitions created by this process have an interface source type of ‘CTO’ .
The Line status of sales order lien will show PO-ReqCreated.
2.Go to Purchasing > Requisitions > Requisition Summary.
In the Find Requisitions window, enter requisition number and click on Find.
Verify that the status is Approved Requisition must have status APPROVED as we ran Req. Import with Requisition approval initiation= Yes
3. Go to Purchasing > Autocreate.
From Edit > Clear > Record, clear any query criteria that may be defaulted.
Enter requisition number and click Find
Check the checkbox to the left of the line, and click on Automatic.
Enter the Supplier and Supplier site and click on Create
4. The Purchase Order form will automatically open with the PO that got created.
Click on the Approve button.
Click on the OK button in the Approval Documents window to approve the PO
Note down the PO number, and verify that the status is Approved. .
once the PO or release is received, the items are recorded in inventory and a reservation is automatically made to the sales order line
5 Go to Purchasing > Receiving > Receipts.
Enter Purchase Order number and click on Find.
In the Receipts window, check the checkbox to the left of the line and enter
Destination Type : Inventory
Subinventory : FGI
Save the receipt.
6.Go to Purchasing > Receiving > Receiving Transactions Summary
Enter the Purchase Order number and click on Find.
Click on the Transactions button.
Verify a Receive and Delivery transaction. This means that the B2B item has been received into Inventory.
The line status of the sales order line will now show Awaiting Shipping .
The Sales Order can now be pick released, shipped and invoiced just like other stocked items
RESERVATIONS
Reservation happens automatically, and can be traced from the sales order form by using Tools->Scheduling->Reservation Details.
When Req Import processes, the purchase requisition is reserved to the sales order line. In Inventory Reservations form, under supply tab, reservation is linked to a requisition, requisition number and line number.
When the requisition becomes a PO the Reservations form, under supply tab, then it shows the reservation is linked to a PO and the PO number as well as the line number.
When the PO is received into inventory, the reservation is automatically transferred into Inventory, and it now looks like any other reservation from a sales order to on-hand stock.
What happen in case of Cancellation and changes?
Sales order line is cancelled or the quantity is reduced --> reservation is reduced and a notification is automatically sent to the buyer explaining that there is now a PO for a higher quantity than what is needed for the sales order. The buyer can then decide whether to cancel the PO line, or to buy the product anyway and put it into inventory.
Schedule date on the order line is changed -> notification to the buyer, who can then decide to either change the date on the PO or cancel it or do nothing. If the buyer decides to cancel the PO-> new requisition will be created the next time AutoCreate Requisition is run.
PO is cancelled or a partial quantity is cancelled--> reservation is cancelled or reduced appropriately. The next time AutoCreate Requisition is run, it will create another requisition for the unreserved amount on the sales order.
This is the Whole back-to-back flow.
In case of any doubt or anything is missing pls put the comments
