|
Mapping No.8 - Posted outgoing sales invoice |
Scroll |
When creating an outgoing sales invoice, the application scenario of NAV's Thereforeâ„¢ interface ensures that the corresponding NAV document is saved as a Thereforeâ„¢ document in the Thereforeâ„¢ archive. The corresponding settings for this are shown below in figure 15.
Figure 15: Mapping No. 8 (Sales Invoice)
All field allocations are taken from NAV table 112 (SalesInvoice Header) and are allocated to the corresponding index data fields of the Therefore's SalesInvoice(Outgoing) category.
|
•Under General, the box Allow multiple versions is activated. This allows changes to NAV documents to be saved as different versions of Thereforeâ„¢ documents, which are then displayed in the document history. •Activating the box Save outgoing documents immediately ensures that when posting an outgoing invoice, the corresponding NAV document is saved to the Thereforeâ„¢ archive immediately. The box has been deactivated by default for performance reasons. |
The transfer is from NAV into the Thereforeâ„¢ archive. The application scenario in figure 16 shows saving and booking of an outgoing sales invoice.
Figure 16: generation and booking of a sales invoice
The booking process in NAV archives a booked sales invoice as well as a booked sales delivery (booked documents). These documents ( if Save outgoing documents immediately is deactivated) are not immediately transferred to the Thereforeâ„¢ archive, but can then either be processed at a time when NAS is activated (see Base Setup) or, as shown below, be processed manually from the processing journal (queue).
