Delivery, Invoice, and Order
Processing 
Use
The structure of deliveries, invoices, and orders is similar in that all documents consist of headers and items that contain the following information:
Document header
· Document number
· Link to visit and tour
· Indicator that states if a document was created on the mobile device or downloaded from the backend
· Indicator that tracks whether the sales representative has modified the document
· Create/change time stamp
· Status
· Cancellation flag and reason code
Document item
· Materials and quantities
· Sub-items for both normal materials and tied empties
· Link to the associated item (for tied empties)
· Indicator that tracks whether the sales representative has modified the item
· Reason code to indicate why the item was changed
Document numbering
Document numbers are specified in the DSD Connector Cockpit and downloaded to the individual devices. Document numbers are incremented by one with every new document of a given type. After the tour data is uploaded in the route accounting database, the last document number is stored in the DSD Connector Cockpit and used to determine initial number download for new tour data.
Document status
The status of documents is either unprocessed or confirmed. Document statuses are independent from activity statuses and are stored on the device in the background. A document is confirmed when it has been transmitted to the customer – either the document has been printed or the sales representative has indicated customer acceptance. As soon as a document has been confirmed, it is locked and cannot be changed any more. If a confirmed document needs to be changed, the sales representative creates a copy of the cancelled document. This way, he can then change the new document while maintaining the audit trail of the cancelled document. It is also possible for the sales representative to cancel a document without creating a copy first.
Editing and displaying documents
Unconfirmed documents can be edited. As soon as a document has been confirmed, it can only be displayed.
Changing documents
Sales representatives can change documents that have not been confirmed. They can change quantities and order items for existing deliveries as well as add items. If they need to delete items, these items are not actually deleted but the quantity is set to zero. When making any of these changes, sales representatives enter reason codes that explain why they have made the changes.
Tied empties
Tied empties represent the full empties on a document (for example, a full case of 24 beer bottles has 24 implied empty bottles and 1 implied empty case). Within the mobile application, each item whose material has an associated empties BOM, tied empties are exploded and added as sub-items. Sub-items for tied empties are displayed on a separate screen. The main screen only shows the normal material items. The tied empties screen shows totals for each implied empties material number.
If multiple items have “12 ounce brown bottle” as implied empties, the tied empties screen shows one item for “12 ounce brown bottle” with the total quantity.
The tied empties summary is the default view but tied empties can also be shown as associated with normal items. This allows you to view the exact quantity of empties for each individual normal item.
Normal transactions versus return transactions
Deliveries and orders support both outgoing transactions and incoming, that is return transactions. These are not differentiated at header level. The sales representative has to manually set a return flag at item level to mark an item as a return. When a return item is added, the sales representative needs to select the reason for the return and indicate whether the return is going into normal or blocked stock.
Customer master data
The value of some customer master fields has direct impact on delivery and invoice processing. You can specify the following:
· Collection type (see Payment Processing)
· Proof of delivery (POD) versus invoice (see Invoicing)
· Invoice generation method (ditto)