The sales order, also known as SO, is an order raised by a business to a customer. A sales order can be created for both products and/or services. A sales order is an internal document of the company, meaning it is generated by the company itself. A sales order should record the customer's originating purchase order which is an external document. Rather than using the customer's purchase order document, an internal sales order form allows the internal audit control of completeness to be monitored. A sequential sales order number may be used by the company for its sales order documents. The customer's PO is the originating document which triggers the creation of the sales order. A sales order, being an internal document, can therefore contain many customer purchase orders under it. In a manufacturing environment, a sales order can be converted into a work order to show that work is about to begin to manufacture, build or engineer the products the customer wants. Customer may request a Sales Order (SO) to view exact details of the products, price, terms and delivery dates.
Prerequisites
Step-by-step guideThe process is divided into the following steps:
|
Batch/Serial functionality can be applied for all those owner sites which are not consignment mode organization sites.(GRT advice only) Changes in Item Grid
Validation on SAVE
Important Note Import Barcode population mode has been affected by Batch/Serial implementation because GRT advice may contain items where Batch/Serial is not specified. Hence, Ginesys has provided batch/serial LOV from where user can select as per his choice if required. Import barcode:
Assumption Currently Ginesys does not have batch/serial applicability for SO/TO but at the time of DC, batch/serial may be applicable. Now if pricing of the item is at batch/serial level then system should not pick item rate, otherwise user will be in dead lock situation as Ginesys does not allow price change in DC against Order. Hence as a workaround, Ginesys auto populates batch/serial price against the item in the in order itself when item price management is at batch/serial level. User can change the price there and same will flow to DC. In future, Ginesys will introduce a user profile in which system will ask if rate recalculation is required at the time of creation of DC and accordingly rate based on batch/serial will get populated in DC. |
Prerequisites
Step-by-step guideThe process is divided into the following steps:
|
Prerequisites
Step-by-step guideThe process is divided into the following steps:
|
Prerequisites
Step-by-step guideThe steps are as follows:
|
Prerequisites
Step-by-step guideThe steps are as follows:
|
Prerequisites
Step-by-step guideThe steps are as follows:
|
Prerequisites
Step-by-step guideThe steps are as follows:
|
Prerequisites
Step-by-step guideThe process is divided into the following steps:
|