Adjust the settings of the proof of delivery on the 184.108.40.206. Proof of delivery controller.
Make sure that the Notification Listener is installed. For more information about the installation of the Notification Listener see: 3.2.4. Produmex SB1 Notification listener, 3.3.3. Enable the Notification Listener stored procedure.
Update the configuration file of the Notification Listener. The file is located in the installation folder of the Produmex SB1 Notification Listener, for example: C:\Program Files\Produmex\Produmex SB1 Notification Listener\
The configuration file is called ‘Produmex.Foundation.SboNotification.ServiceHost.exe.config’.
Open the file with a text editor (e.g. Notepad).
Locate the line below and uncomment it:
<action senderType="P" objectType="POD_RTHE" transactionType="U" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.NotificationQueue, Produmex.Sbo.Logex.SboNotification.Actions"/>
To create the export files for the proof of delivery solution, enable the Notification Listener procedure.
When creating a route where a proof of delivery is needed, set the Route for ‘Proof of delivery’? option to true on the Create new route screen.
It is also possible to modify this setting on the Route detail window.
Perform the delivery on the fat client. Collect the stock based on the pick list, pack the goods then start the shipping. After every logistic unit has been loaded, the system displays the ‘Adding sales delivery notes in SAP. Can take some seconds… ‘ message regardless of using the proof for deliver function or not.
When the Route for ‘Proof of delivery’? option is enabled for the route, the system does not create a sales delivery note until the delivery is confirmed. By the help of the Notification Listener an export file is created for the proof of delivery solution. A separate file will be generated for each route.
The export file will be created to the ’Interface monitor output path’ defined on the Config tab on the company level of the Organizational Structure.
Export file naming convention: PMX_EPOD_Route_routekey_timestamp.csv
The file contains information about the customer, address and goods delivered.
When the export file was not created, first check if the Notification Listener is running.
After the shipping, the status of the route will be changed to ‘POD pending’. The pick list will remain open with the status ‘Packed’.
In the inventory record the stock to deliver will remain on the shipping dock. The stock will be locked for the pick list until the delivery has been confirmed.
The proof of delivery solution takes the output files as an input.
After the delivery has been confirmed, the proof of delivery solution creates an import file with the confirmation data. A separate file will be generated for each delivery address.
After the synchronization, the file will be imported to the folder defined with the ‘Interface monitor input path’ on the Config tab on the company level of the Organizational Structure.
The signature images and the captured pictures from the delivery solution will be imported to the folder defined in the 220.127.116.11. Proof of delivery controller
Import file naming convention: EPOD_PMX_EPOD_Route_routekey_jobsequencenumber_timestamp.csv
The file contains information about the route, the goods delivered and the failed deliveries. Start the Interfacing tool with the /t:POD /d:import /rf parameters.
With the help of the Interfacing tool, Produmex imports the file from the proof of delivery solution and creates the sales delivery note. The delivery note only contains the SSCC’s or quantities confirmed with the proof of delivery solution. On the ‘Attachments’ tab links to the signature and other images are inserted.
Based on the import file, the system closes the confirmed pick list lines and generates the sales delivery note. Pick lists linked to a failed delivery will remain open. The system unlinks those open pick lists from the route, and closes the route.
After the Interfacing tool processed the import file, it is moved to the archive or the error folder defined on the Config tab on the company level of the Organizational Structure.