We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
Adding, Editing, Deleting & Printing Sales Order (SO) in Ginesys Web
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.
Impact of Batch/Serial functionality on Sales/Transfer order
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
Three new columns have been added in the grid - Batch/Serial No., Mfg. Date and Valid Upto
The columns are hidden by default but can be made visible by the column chooser.
Batch/Serial No. column details
It is an LOV. All existing batch/serial (in INVBATCH_SERIAL) for the item will be displayed here. Mfg. Date and Valid Upto column types are “View only”, i.e. modification is not allowed. Values in Mfg. Date and Valid Upto columns are displayed as populated from the selected batch/serial no., if not available then it will be blank.
Validation on SAVE
User can either provide item/batch-serial combination OR only item, for particular item in the grid
Example: Row1 having Item1 with batch-serial info. & Row2 having Item1 without batch-serial info. This is not allowed.
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:
Batch/Serial No. column has been added and it is a Non Mandatory column.
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.