You can automatically send documents electronically when you post the record that the document is based on. You can also produce physical copies of electronic documents for physical archiving when you post the record that the document is based on.
A document is sent to a recipient (endpoint) automatically when you post or print the posting for a record from any form on which:
-
An electronic document has been set up.
-
The recipient has a configured endpoint and endpoint action policy.
The following table lists some of the documents included with Microsoft Dynamics AX and their related posting forms.
Outbound document |
Open the posting form |
---|---|
Purchase requisition |
|
Sales invoice |
|
Picking list |
|
Advance ship notice |
|
Price list |
|
Chart of accounts |
|
Dimensions |
|
Exchange rates |
|
Send documents from a posting form
Use the following steps to enable the sending of documents when posting:
-
Open the posting form. For example, if you want to automatically send a picking list, follow the steps in the previous table to navigate to the picking list.
-
Click and select the check box.
-
In the field, select the batch group in which the document should be included.
-
Click OK. An Infolog message confirms that the job has been added to the queue.
Note |
---|
To electronically send documents through the posting form, the administrator must have the batch services configured correctly. For more information, see "Start and stop the asynchronous AIF services" in the Server and Database Administration Help. |
Receive documents electronically
If the endpoint policy has been correctly set up, incoming electronic documents automatically appear in the tables and forms defined in the document and endpoint policy.
Depending on the setup, an inbound document is registered in a posting form or a journal form. For example, an inbound sales order can be placed in the form (a posting form) or in the journal (a journal form) by selecting the relevant option in the field on the tab in the form.
It is not necessary to define the placement of all inbound documents in posting or journal forms. If the sender and recipient endpoints are configured to exchange documents and the document itself is accepted by Microsoft Dynamics AX, the document is automatically imported into the appropriate forms.
The following table lists a subset of documents that ship with Microsoft Dynamics AX, their corresponding forms, and rules regarding receiving updates and duplicates of the document in question.
Note |
---|
An update is a change made to an existing record in the table. Receiving a new exchange rate for one or more currencies is not an update, but a new exchange rate record. A duplicate document is an identical copy of a previously received document, and might have been sent again mistakenly. |
Inbound document |
Receiving form |
Updates |
||
---|---|---|---|---|
Sales order |
The receiving form depends on the parameter set in the field on the tab of the form. ( > > )
|
Updates to sales orders that were received previously are always added to the sales order journal in the form. ( > > > ) Any differences between the previous sales order and the updated sales order must be resolved before the sales order is posted. |
||
Invoice |
The invoice document is received in the invoice register defined in the field on the tab of the > >
|
Updates to existing invoices and invoices that are received more than once (duplicate invoices) are received as new and independent invoices in the defined invoice register.
|
||
Packing slip |
The packing slip document is received in the form. ( > > > )
|
Updates to existing packing slips are accepted and posted into the system, which permits partial deliveries of the sales order lines. If the remaining sales line quantity is less than the packing slip quantity, the packing slip update document is rejected. |
||
Inventory counting |
The inventory counting document is received in the form. ( > > > )
|
Updates to the inventory counting document are treated as new inventory counting documents, and a new inventory counting record is created by the document. Duplicate inventory counting documents are also treated as new inventory documents, and a new inventory counting record is created by the document. |
||
Inventory transfer journal |
The inventory transfer journal document is received in the form. ( > > > )
|
Updates to the inventory transfer document are treated as new inventory transfer documents, and a new inventory transfer record is created by the document. Duplicate inventory transfer documents are also treated as new inventory transfer documents, and a new inventory transfer record is created by the document. |
||
Inventory profit/loss |
The inventory profit/loss document is received in the form. ( > > > )
|
Updates to the inventory profit/loss document are treated as new inventory profit/loss documents, and a new inventory profit/loss record is created by the document. Duplicate inventory profit/loss documents are also treated as new inventory profit/loss documents, and a new inventory profit/loss record is created by the document. |
||
Chart of Accounts |
The chart of accounts document is received in the form. ( > ) |
Updates to the existing chart of accounts are not permitted and the chart of accounts document is rejected. Duplicate chart of account documents are treated as an update of the chart of accounts and are rejected. |
||
Dimensions |
The dimensions document is received in the form in the module. |
Updates to the existing dimensions are not permitted and the dimensions document is rejected. Duplicate dimensions documents are treated as an update of the dimensions and are rejected. |
||
Exchange rates |
The dimensions document is received in the form. ( > > ) |
Updates to the existing exchange rates are not permitted and the exchange rates document is rejected. Duplicate exchange rates documents are treated as an update of the exchange rates and are rejected. |
||
Price/discount agreement |
The default journal name for the price/discount agreement journal must be selected in the field on the tab of the form. ( > > )
|
Updates of existing trade agreements are not permitted and the price discount document is rejected. Duplicate price discount documents are treated as an update of the trade agreement and are rejected. |