POS system in NAV
Andwian
Member Posts: 627
Dear Experts,
I have an idea to implement NAV on the Serviced Retail Store, so that it will be used as POS.
I have heard about LS-Retail, and I do not think to use it as solution.
The business process:
And the process of the cashier from Create Whse. Shipment until Posting & Print Shipment & Invoice from Whse. Shipment, I want to automate that by using only one button. However, I will let the COMMIT intact.
Is that advisable?
Any comment would be greatly appreciated. Thank you.
I have an idea to implement NAV on the Serviced Retail Store, so that it will be used as POS.
I have heard about LS-Retail, and I do not think to use it as solution.
The business process:
-
1. The salesperson create Sales Order to take the customer order.
2. The customer go to the cashier
3. The cashier will:
-
a. Create Whse. Shipment
b. Create Whse. Pick
c. Register Pick
d. Posting & Print Shipment & Invoice from Whse. Shipment
And the process of the cashier from Create Whse. Shipment until Posting & Print Shipment & Invoice from Whse. Shipment, I want to automate that by using only one button. However, I will let the COMMIT intact.
Is that advisable?
Any comment would be greatly appreciated. Thank you.
Regards,
Andwian
Andwian
0
Comments
-
I have done the same automation for a customer:
On the Sales Order you can set up what should happen when the order is released:
- Nothing
- Create Shipment
- Create Shipment and Pick
On the Warehouse Shipment you define what should happen when the Pick is posted:
- Nothing
- Ship
- Ship + Invoice
- Ship + Print
- Ship + Invoice + Print
We left all commits intact.
There might be several reasons why this process can fail. In our case people know how to solve it. You might need to add lots of code to work around pitfalls.
But one general question: Is it in this setup really neccessary to use shipments and picks? Couldn't you just use another location without shipment/pick?Frank Dickschat
FD Consulting0 -
Thanks Frank for sharing the light.
I keep the COMMIT intact, and I did not give any Condition where the COMMIT will be run or not.
Therefore like you said, that there will be at some point the process will be failed, and not rolled back.
However, the user must known at what point the error occurred.
What do you mean with this?FDickschat wrote:You might need to add lots of code to work around pitfalls.
Would you give any explanation or example?
Actually, I need:FDickschat wrote:But one general question: Is it in this setup really neccessary to use shipments and picks? Couldn't you just use another location without shipment/pick?-
1. to know on which Bin Code I should pick item, by FEFO.
2. to prevent negative inventory.
Actually, I could use Inventory Pick, instead of Whse. Shipment and Whse. Pick, and I still can use FEFO, however the user must select the Lot No. manually the First Expired item. That's why I use the Shipment and Pick. Not really worth enough, since there are a lot of effort to do for just sell one order.Regards,
Andwian0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions