Showing posts with label Sales Order. Show all posts
Showing posts with label Sales Order. Show all posts

Monday, 28 March 2016

Sales Order --> Rules --> Processing Constraints

Depending on the business requirements we can be required to check for some conditions and based on their applicability restrict some operations to be performed on the Sales Order.
These restrictions can be applied via the Processing Constraints. There are number of Seeded Oracle Constraints which prevent certain operations in orders to maintain Data Integrity .
E.g. We cannot split an Order line After it is shipped , thus Seeded Oracle Processing Constraint will ensure that this action cannot be performed by the user.


Apart from these we can have custom constraints defined too. Once the constraints have been defined we need to apply it i.e. map it to the responsibilities to specify which responsibilities will be bound by the constraint or can override the constraint.


This can be done by the Applicable to Option :


Oracle provides 3 options which work as below :


All Responsibilities : This means this constraint will be applicable to all responsibilities.
Authorized Responsibility : When any responsibility is mentioned here, then the processing constraint will NOT BE applicable to that responsibility
Constrained Responsibility : When any responsibility is mentioned here, then the processing constraint will BE applicable ONLY to that responsibility


For Seeded constraints the Applicability is All Responsibilities and cannot be updated

Tuesday, 12 January 2016

Pick Release Order with Container Item

In this article we will discuss on the Pick Release process and changes happening in the system when we do a pick release for a line attached to a container item.

Scenario : Suppose we are in a business where we sell LED lamps , since the end product is small generally the shipping units will be in hundreds or thousands. In the actual shipping
These small lights will be packed into large boxes/cartons/containers which will be shipped to the customer. Suppose we have a container with a capacity of 1000.
We create a sales order with a ordered quantity of 5000.
In this scenario when we do a shipping although we will be shipping 5000 units of product but in 5 containers as the business will pack them in 5 containers and ship those records.

If we have such a scenario first of all we need to do a setup of a container item and associate with the Actual inventory item. Here we will define how many units one container will hold which will be used in the stage of picking.

1.       It is assumed that a container item is already created in the system and we have defined a relationship between the actual item and the container item. This information is available in the table wsh_container_items

2.       In the Pick Release rule setup if Auto Pack is set to Yes : then the Pick release process will take care of packing the goods into the containers as per the setup in Step 1

Changes during Pick Release :

The Goods will be moved from the source sub inventory to the staging sub inventory

In wsh_delivery_details the delivery details will be split up in multiples of 1000 and balance quantity if it exists to match the container mapping and new lines will be created with source code ‘WSH’ to signify a container which has been associated to each line.
Below SQL can be used to get the details.
select lpn_id,source_code,split_from_delivery_detail_id,SRC_REQUESTED_QUANTITY,requested_quantity,wdd.cancelled_quantity,wdd.*
from wsh_delivery_Assignments wda,wsh_delivery_details wdd--,oe_order_lines_all ool
where 1=1--
and delivery_id = :delivery id 
and wda.DELIVERY_DETAIL_ID = wdd.DELIVERY_DETAIL_ID
order by wdd.DELIVERY_DETAIL_ID

here source code : OE is the actual order line and the source code ’WSH’ is for each container delivery details which has been created during the pick release process .Here the WSH records signify the number of cartons which have been packed the LPN ID for which the information can be found in table : WMS_LICENSE_PLATE_NUMBERS

The material transactions are created as below to track the transfer of goods from Source to Staging sub-invenotry
·         2  entries are created in mtl_material_transactions just like any other picking tracking the movement of goods from the source sub-inv to staging sub-inv
·         When the shipping is done then we will have 5 entries in mtl_material_transactions signifying the movement of goods outside the staging warehouse each with quantity 1000 reason being in physical shipment 5 cartons moved out of the warehouse




Monday, 22 December 2014

Released_status in wsh_delivery_details (wsh_delivery_details.released_status)

When a Sales Order line is booked , for Shippable item lines have an entry in the table wsh_delivery_Details. The column released status has status values which provide information of the Sales Order shipment status

B: Backordered- Line failed to be allocated in Inventory
C: Shipped -Line has been shipped
D: Cancelled -Line is Cancelled
N: Not Ready for Release -Line is not ready to be released
R: Ready to Release: Line is ready to be released
S: Released to Warehouse: Line has been released to Inventory for processing
X: Not Applicable- Line is not applicable for Pick Release
Y: Staged- Line has been picked and staged by Inventory 

Detailed Explanation : 

B : Backordered : when we try to pick release a Sales Order but On-hand is not available for the order line , in such scenarios the order line is back ordered and the released status  = 'B'

C: Shipped :Once the Order line is shipped the associated delivery details Released Status is changed to 'C' .OM interface and Inventory interface have processed and the trip is closed.

D: Cancelled : When the Order line is cancelled the released status = 'D'

N: Not Ready for Release -Line is not ready to be released . this can happen when the information is available in wsh_delivery_details but order line has not reached the Awaiting Shipping status , might be due to some workflow customization's

R: Ready to Release: The Order line has been booked and the line is ready to be pick released . Line status is Awaiting Shipping under such scenarios

S: Released to Warehouse : Depending on the Pick release process in the business it moght be that Pick release is performed with Auto Pick confirm Set to No.
In such scenarios when we do pick release the Move Order will be created
Move Order allocation is done , but since Auto Pick Confirm is set to No the Mover Order will not be transacted.
The Delivery Detail will be in state : Pick Wave

X: Not Applicable- Line is not applicable for Pick Release , for the non-shippable item lines eg : Warranty orders


Y: Staged- Line has been picked and staged by Inventory .In this Case the line has been pick released. the Move Order Creation,Allocation and transaction is completed . Goods have be transferred from the Source Sub-invenotry to Staging area of the warehouse and the line is ready to be shipped


Monday, 17 November 2014

Item Validation During Order Import

During Order Import many of us face Errors related to Item Validation on the Sales Order Line. This leads to  checks on the item master Setup. Listing down below some of the basic checks that should be done once any Item Related validation error is reported

  1. Is the item assigned to the Warehouse specified on order line / the Warehouse defaulting via the defaulting rules
  2. Is the Item assigned to the Item Validation Org , Item Master Org 
  3. In case the Shipping OU and Selling OU are different the item should be assigned to the IVO of both the Operating Units
  4. Order Enabled Flag , Customer Order Enabled Flag . this flag needs to setup for all the warehouses mentioned in Step 1,2,3
  5. Item status needs to be checked for all the warehouses for steps 1,2,3
If the issue still persists check for all other item attributes which might be Impacting . For internal Sales Orders the Internal Order Enabled Flag needs to be set

Thursday, 2 October 2014

BILL Only order , Item Flag Shippable

When Creating sales orders , we have many instances where we need to create a BILL Only Sales Order . There are situations when the company is creating an Order for invoicing but there will not be any shipments for this order ,
Eg : If you buy a Warranty for a product in this case there is not physical shipment needed
        If you have requested for a service of any product , in this case you are requesting the visit of a           technician to come and service , no physical shipments might be involved

In such scenarios when the order line is created it is in Entered Status
On booking the Order the line status changes to BOOKED Please make not that line does not go into Awaiting Shipping status
Once workflow background process runs the Order line is Closed

when entering the sales order for a BILL Only line , the item selected on the Sales order also needs to be setup in a particular way.
The SHIPPABLE ,flag on the Item needs to be unchecked , this needs to be ensured for the Item Master Organization , Item Validation Organization for this operating unit and also the warehouse selected on the order.

If this setup is not correct at all the levels the line will go into Awaiting Shipping status and you will not see the expected behaviour.