[quote] To avoid having to log in as many different profiles, navigation steps in the walkthroughs are based on department menus and not on the Role Centers.[/quote]
So even Microsoft acknowledges that the Role-Tailored-Client interface is cumbersome.
Not seeing the benefit in that listing though, just some more examples of how NAV is more cumbersome to use for processes that any number of other programs out there also do.
I don't know who this NAV mobile push is aimed at, but I'm not seeing entering 20,000 invoices with my finger on a mobile tablet every month. Are they aiming it at ebay sellers?
Last I heard, PowerBI was a 3rd party 'solution' that needs you to use Microsoft's cloud features to really benefit from. Still another few fingers in the pie and a tighter squeeze from the python...
Microsoft's explanation of why a small bike shop needs a separate quality controller person to navigate through NAV, from one of the walk-throughs above:
[quote]
Tracing from Usage to Origin
--------------------------------------------------------------------------------
From the sales department, the quality controller knows that the returned racing bike, item 1002, has the serial number SN1. By using this basic information, he can determine where the finished racing bike was last used, in this case, on the sales shipment to Selangorian Ltd.. Then, the quality controller must trace backward to the earliest origin to establish which lot number the faulty racing frame came from and which vendor supplied it.
To determine which lot included the faulty frame and who supplied it
- In the Search box, enter Item Tracing, and then choose the related link.
In the Item Tracing window, enter SN1 in the Serial No. Filter field, and then enter 1002 in the Item Filter field.
- Keep the default setting of Item-Tracked Only in the Show Components field, and keep the default trace method of Usage – Origin in the Trace Method.
On the Actions tab, in the General group, choose Trace.
Note that one sales shipment header matches the search criteria. Before you continue the trace, verify that the shipment is the one that shipped the faulty racing bike to Selangorian Ltd.
- Select the trace line, and then, on the Navigate tab, in the Line group, choose Show Document.
Now continue to trace the origin of the sales shipment of the racing bike with number SN1.
- Choose the + icon on the trace lines to gradually expand and trace backward in the chain of transactions that the sales shipment originates from.
You can trace the following transaction history:
â—¦ The first posted document backward in the chain of transactions is the output posting of SN1 from the first released production order.
â—¦ The next posted document backward after that is the consumption posting from the first released production order. Here the quality controller sees that a racing frame from LOT1 was used.
â—¦ The lowest posted document in this chain is the posted purchase receipt on which racing frames with LOT1 entered inventory.
The quality controller has now established which lot of racing frames was faulty and he can search for the last trace line to see which vendor supplied them, namely Custom Metals Incorporated.
Note
Do not make any additional modifications to the trace result, as you will use it in the next section.
This completes the first defects-management task using the Item Tracing window. The quality controller must now determine whether other posted documents have processed racing frames from LOT1.
Tracing from Origin to Usage
--------------------------------------------------------------------------------
The quality controller has established that the faulty racing frames came from LOT1. He must now find any other racing bikes that contain racing frames from the faulty lot so that those bikes can be stopped or recalled.
One way to prepare this trace task in the Item Tracing window is to manually enter LOT1 in the Lot No. Filter field and 2000 in the Item Filter field. However, this walkthrough will use the Trace Opposite - from Line function.
To find all usage of the faulty lot
- In the Item Tracing window, select the line of the purchase receipt, the last trace line, and then, on the Actions tab, in the Functions group, choose Trace Opposite – from Line.
The trace result is now based on the filters of the trace line for the purchase receipt, LOT1 and item 2000, and the result is based on trace method Origin - Usage.
To obtain an overview of all usage of item 2000 with LOT1, continue to expand all trace lines.
- On the Actions tab, in the General group, choose Expand All.
The first four trace lines refer to the sales shipment to Selangorian Ltd., which is already resolved. The last line indicates that one more racing bike, SN2, was produced in the same released production order and then sold and shipped on another sales shipment.
The quality controller immediately informs the sales department so that they can initiate a recall of the defective racing bike from the customer, Cannon Group PLC.
At the same time, he can see from the last three trace lines that another two items, SN3 and SN4, have been produced based on racing frames from LOT1. He takes action to block these end items in inventory.
This completes the second defects management task using the Item Tracing window for defects management. Since the Item Tracing window is based on posted entries only, the quality controller must continue to the Navigate window to make sure that LOT1 is not used in non-posted documents.
Finding All Records of a Serial/Lot Number
--------------------------------------------------------------------------------
With the Item Tracing window, the quality controller learned that LOT1 contained the faulty racing frames, which vendor supplied them, and in which posted transaction they have been used. He must now determine whether LOT1 is in any open documents by integrating from the trace result to the Navigate window where he can perform a search through all database records.
To find all occurrences of LOT1 in non-posted records, such as open orders
- In the Item Tracing window, select the first trace line, the purchase receipt of LOT1.
On the Actions tab, in the General group, choose Navigate.
The Navigate window is preset with search filters based on the trace result for LOT1. The quality controller recognizes most of the records as pertaining to documents already identified in the Item Tracing window. For example, the last Navigate line of type Production Order refers to the two released production orders that consumed racing frames from LOT1.
However, the second Navigate line of type Sales Line is a non-posted document line, so the quality controller proceeds to investigate.
- To open the sales line record, select the second Navigate line, and then, on the Home tab, in the Process group, choose Show. Alternatively, choose the value in the No. of Records field.
Here the quality controller sees one open sales line for the faulty racing frames. He immediately suggests to the sales department that this order be canceled and a new production order, based on good racing frames, be initiated.
This completes the walkthrough of how to use the Navigate window for defects management in integration with the Item Tracing window.[/quote]
"cumbersome" doesn't begin to describe this.
