Let's say we need to provide one of our vendors with a Sales order confirmation in the form of XML file for the further consuming in their automated system. We suppose your license configuration is OK for that.
First of all, the appropriate service has to be set up in AIF module of AX 2012. (For the previous version, take a look at Microsoft Dynamics AX AIF: Sending Outbound Documents Automatically post) Given that we are going to export this information, we need to create a new outbound port.
Setting new Outbound port
Open the form of Outbound ports (System administration/Setup/Services and Application Integration Framework) to set up one: give it a name and short description to recognize it later among others.
Adapter should be File system adapter to generate XML file.
URI is the path where you can find generated XML files. Of course, AX has to have appropriate rights for this folder.
Now, we are choosing in the drop-list the appropriate service defined in AOT. For the most documents these services are already created; however, if you need to set up some specific or even new document service, please refer to the development manual.
The one we are looking for is SalesSalesConfirmationService. As you can see, all the document services are named in a very evident style: you always know for which document it serves.
Do not worry, if you cannot find this service in the list because it exists but needs to be registered from AOT like follows.
Open Services branch in AOT tree, find this service in it, and register by the context menu item. You need to do it every time you add a new document service. Now this service appears in the list.
Read method will be enough for our job, so we activate our new port. Now we can proceed with the next step:
Adding a batch job maintaining AIF module
For my particular case, I am adding two tasks within it:
- AifOutboundProcessingService responsible for outbound processing; and
- AifGatewaySendService that will save XML files in the folder of URI, defined on the preceding step.
Note that you have to strictly follow the sequence so that a document will be pushed in the Message queue first and then a file will be created.
Do not forget to start the batch job with the right recurrence rules. You find more detail on how to deal with this batch job here.
Print management for clients
Finally, we change the print management for the client to whom we want to send XML files while updating Sales order confirmation.
Choose Print archive as a Destination to avoid the real printing and to generate an XML file.
Since now, when I confirm a sales order for this client I get after within one-two minutes an appropriate XML file in the folder.
For your environment, of course, you need to use your own parameters like those for the file folder or period of time for the batch job.
Also, it is possible to set up Sales order confirmation as a batch job, too.
Let me know if you have any troubles with this!
First of all, the appropriate service has to be set up in AIF module of AX 2012. (For the previous version, take a look at Microsoft Dynamics AX AIF: Sending Outbound Documents Automatically post) Given that we are going to export this information, we need to create a new outbound port.
Setting new Outbound port
Open the form of Outbound ports (System administration/Setup/Services and Application Integration Framework) to set up one: give it a name and short description to recognize it later among others.
Adapter should be File system adapter to generate XML file.
URI is the path where you can find generated XML files. Of course, AX has to have appropriate rights for this folder.
Now, we are choosing in the drop-list the appropriate service defined in AOT. For the most documents these services are already created; however, if you need to set up some specific or even new document service, please refer to the development manual.
The one we are looking for is SalesSalesConfirmationService. As you can see, all the document services are named in a very evident style: you always know for which document it serves.
Do not worry, if you cannot find this service in the list because it exists but needs to be registered from AOT like follows.
Open Services branch in AOT tree, find this service in it, and register by the context menu item. You need to do it every time you add a new document service. Now this service appears in the list.
Read method will be enough for our job, so we activate our new port. Now we can proceed with the next step:
Adding a batch job maintaining AIF module
For my particular case, I am adding two tasks within it:
- AifOutboundProcessingService responsible for outbound processing; and
- AifGatewaySendService that will save XML files in the folder of URI, defined on the preceding step.
Note that you have to strictly follow the sequence so that a document will be pushed in the Message queue first and then a file will be created.
Do not forget to start the batch job with the right recurrence rules. You find more detail on how to deal with this batch job here.
Print management for clients
Finally, we change the print management for the client to whom we want to send XML files while updating Sales order confirmation.
Choose Print archive as a Destination to avoid the real printing and to generate an XML file.
Since now, when I confirm a sales order for this client I get after within one-two minutes an appropriate XML file in the folder.
For your environment, of course, you need to use your own parameters like those for the file folder or period of time for the batch job.
Also, it is possible to set up Sales order confirmation as a batch job, too.
Let me know if you have any troubles with this!
_1074.jpg)
Posts
