The Notification Listener is a tool that monitors the record in the PMX_NOTQ table and performs custom actions when a certain type of data is adjusted. The tool can perform the following actions:

• automatic document creation
• automatic printing (Please see: How to print documents with the Notification Listener)
• document export (Please see: EDI documentation)

For information about the installation of the Notification Listener please see:

• 3.2.4. Produmex SB1 Notification listener
• 3.3.3. Enable the Notification Listener stored procedure

For information about the frequency settings please see:

• SBO Notification Listener- Performance

The configuration file of the Notification Listener tool contains the configurations of the transactions the tool can perform. By default all these transactions are disabled.

In order to define actions for the Notification Listener, update its configuration file.

The configuration file is called ‘Produmex.Foundation.SboNotification.ServiceHost.exe.config’. It is located in the installation folder of the Produmex SB1 Notification Listener, for example: C:\Program Files(x86)\Produmex\Produmex SB1 Notification Listener\

Open the file with a text editor (e.g. Notepad). Locate the line of the transaction and uncomment it then save the file.

Transaction lines might have parameters. Parameters can have the following functions:

• Set conditions. Example: Allow zero price, Allow grouping on shipping type
• Specify the report parameters: the report ID, the report path, the printer

Then run the Notification Listener.

• To run the Notification Listener in the background, start it as a Windows service.
• To run the Notification Listener with an open console, launch the RunConsole.bat file from the installation folder of the Produmex SB1 Notification Listener, for example: C:\Program Files(x86)\Produmex\Produmex SB1 Notification Listener\.

Transaction Line
The transaction line consists of the following:

• action senderType
• objectType
• transactionType
• logic

The objectType and the transactionType determines the transaction that triggers the action defined in the logic parameter.

Possible values:

• objectType
  • SAP Business One object types:
    • 2: Business Partner
    • 13: Sales invoice
    • 14: Sales Credit Note
    • 15: Sales Delivery Note
    • 16: Sales Return
    • 17: Sales order
    • 20: Purchase Delivery
    • 22: Purchase order
    • 59: Goods Receipt
    • 60: Goods Issue
    • 67: Warehouse Transfer
    • 202: Production order
  • Produmex object types:
    • PMX_MVHE: Produmex move
    • POD_RTHE: Produmex route
• transactionType:
  • 'A'=add
  • 'U'=update
  • 'L'=close
  • 'D'=delete
  • 'C'=cancel
  • '*'=all

By default the configuration file of the Notification Listener contains two actions for automatically generating a pick list proposal.

The following parameter is supported in these transaction lines:

• AllowZeroPrice: If set to ‘No’, no pick list proposal will be created if the total price of the sales order is zero.

To create a new pick list proposal automatically every time a sales order is created, uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="17" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePickListProposal, Produmex.Sbo.Logex.SboNotification.Actions">
</action>

To create a new pick list proposal automatically every time a sales order is updated, uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="17" transactionType="U" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePickListProposal, Produmex.Sbo.Logex.SboNotification.Actions">
    <parameter name="AllowZeroPrice" value="N"/>
</action>

If there is an existing pick list proposal for the updated sales order, the system will close the existing proposal depending on the ‘Try to group items on 1 proposal’ setting on the Picklist proposal generator.

The pick list will be automatically generated if the ‘Auto. generate pick list’ UDF is set to ‘True’ for the payment term of the sales order.

The following parameters are supported:

• Allow Grouping On Shipping Type: If set to ‘Yes’, the pick lists of a sales order will be split based on the shipping type of the order lines, otherwise a grouped pick list will be created for the sales order.
• AllowZeroPrice: If set to ‘No’, no pick list proposal will be created if the total price of the sales order is zero.

To create a new pick list automatically every time a sales order is created, uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="17" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePicklist, Produmex.Sbo.Logex.SboNotification.Actions">
     <parameter name="AllowGroupingOnShippingType" value="Y"/>
</action>

To create a new pick list automatically every time a sales order is updated, uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="17" transactionType="U" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePicklist, Produmex.Sbo.Logex.SboNotification.Actions">
    <parameter name="AllowGroupingOnShippingType" value="Y"/>
</action>

Uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="17" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePicklistAndRoute, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

When a new sales order is added, a pick list will be generated and it will be automatically added to a route, if there is a route that meets the following criteria:

• The route is open
• The route date is later than the due date of the sales order
• The route was created from a template for the customer of the sales order

If there is no such route, no pick list will be generated for the sales order.

In order to automatically create a sample order after a Goods Receipt PO document is booked, set the following:

1. Uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="20" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.CreateSampleOrder, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

2. Set the sample generator on the Extensions tab of the Organizational Structure.

3. Set the sample quantity for the item on the Produmex Purchase tab of the Item Master Data. The sample quantity will be the ordered quantity of the item on the sample sales order.

4. Link the customer, to whom you would like to send the sample for inspection, to the vendor on the ‘Linked Business Partner’ UDF on the Business Partner Master Data.

The system will create a sales order automatically for the linked customer with the sample quantity set for the item after a purchase delivery is added. The ‘Is sample order’ UDF will be set to ‘Yes’ on the created sales order and the document number of the Goods Receipt PO document will be added as a remark.

In order to automatically mail the purchase order report to the vendor after the purchase order is created, set the following:

1. Configure the mailing parameters on the Report mailer.

2. Enable the ‘Mail report on document add’ setting for the given shipping type.

3. Make sure that the email address of the business partner is added on the Business Partner Master data.

4. Define the report on the ‘Reports’ tab of the Organizational Structure. The input parameter of the report is @docEntry.

5. Uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="22" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboReportMailerAction, Produmex.Sbo.Logex.SboNotification.Actions">
  <parameter name="ReportId" value="8"/>
</action>

Change the value of the Report ID parameter to the report ‘Key’ value of the report that can be found on the ‘Reports’ tab of the Organizational Structure.

It is possible to automatically copy the User Defined Fields of the Bill of Materials to the Production order on the creation with a Produmex action. Uncomment the following line in the configuration file of the Sbo Notification Listener:

<action senderType="SboToPmx" objectType="202" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.NewProdOrderCopyUDFsFromBOM, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

The configuration file of the Notification Listener contains the following printing actions by default:

<action senderType="SboToPmx" objectType="17" transactionType="L" logic="Produmex.Sbo.Logex.SboNotification.Actions.PrintReport, Produmex.Sbo.Logex.SboNotification.Actions">
   <parameter name="ReportPath" value="DefaultGoodsReceiptLabel.rpt"/>
   <parameter name="PrinterDevice" value="RPT"/>
</action>

<action senderType="SboToPmx" objectType="20" transactionType="*" logic="Produmex.Sbo.Logex.SboNotification.Actions.PrintReportForClosedPOOnGR, Produmex.Sbo.Logex.SboNotification.Actions">
    <parameter name="ReportPath" value="DefaultGoodsReceiptLabel.rpt"/>
    <parameter name="PrinterDevice" value="RPT"/>
</action>

Specify the report and the printer with the parameters:

• Add the report path from the Reports tab of the Organizational Structure as the value of the ‘ReportPath’ parameter.
• Add the printer code form the Organization Structure as value of the ‘PrinterDevice’.

For more information about automatic printing with the Notification Listener please see: Automatically print documents with the Notification Listener

For information about exporting documents with the Notification Listener please see: Standard EDI module

The configuration file of the Notification Listener contains the following transaction lines for document export:

<action senderType="P" objectType="POD_RTHE" transactionType="U" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.NotificationQueue, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

If this line is uncommented, the POD route will be exported as a .csv file after the route is loaded. For more information please see: Proof of delivery

<action senderType="SboToPmx" objectType="PMX_MVHE" transactionType="*" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.PmxStockUpdateExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a move has been executed, the inventory will be exported as defined with the extension for the ‘IPmxStockInterface – Pmx stock im-/exporter (IPSTOCK)’ controller, if this line is uncommented. The controller does not have a standard extension.

<action senderType="SboToPmx" objectType="15" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesDeliveryExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales delivery has been created, it will be exported as defined with the extension for the ‘Interface for SBO sales delivery im-/export (ISBOSDLN)’ controller, if this line is uncommented. When using the standard extension parameter, the document will be exported to an .xml file.

<action senderType="SboToPmx" objectType="15" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesDeliveryExport2Action, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales delivery has been created, it will be exported as defined with the extension for the ‘Interface for SBO sales delivery 2 im-/export (ISBOSDLN2)’ controller, if this line is uncommented. The controller does not have a standard extension.

<action senderType="SboToPmx" objectType="20" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboPurchaseDeliveryExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a purchase delivery has been created, it will be exported as defined with the extension for the ‘Interface for SBO purchase delivery im-/export (ISBOPDLN)’ controller, if this line is uncommented. When using the standard extension parameter, the document will be exported to an .xml file.

<action senderType="SboToPmx" objectType="16" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesReturnExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales return has been added, it will be exported as defined with the extension for the ‘Interface for SBO sales return im-/export (ISBOSR)’ controller, if this line is uncommented. When using the standard extension parameter, the document will be exported to an .xml file.

<action senderType="SboToPmx" objectType="16" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesReturnExport2Action, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales return has been created, it will be exported as defined with the extension for the ‘Interface for SBO sales return 2 im-/export (ISBOSR2)’ controller, if this line is uncommented. The controller doesn’t have a standard extension.

<action senderType="SboToPmx" objectType="60" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboGoodsIssueExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a goods issue document has been created, it will be exported as defined with the extension for the ‘Interface for SBO goods issue im-/export (ISBOGI)’ controller, if this line is uncommented. The controller doesn’t have a standard extension.

<action senderType="SboToPmx" objectType="59" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboGoodsReceiptExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a goods receipt document has been created, it will be exported as defined with the extension for the ‘Interface for SBO goods receipt im-/export (ISBOGR)’ controller, if this line is uncommented. The controller doesn’t have a standard extension.

<action senderType="SboToPmx" objectType="13" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesInvoiceExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales invoice has been added, it will be exported as defined with the extension for the ‘Interface for SBO sales invoice im-/export (ISBOSINV)’ controller, if this line is uncommented. When using the standard extension parameter, the document will be exported to an .xml file.

<action senderType="SboToPmx" objectType="14" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboSalesCreditNoteExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a sales credit note has been added, it will be exported as defined with the extension for the ‘Interface for SBO sales credit note im-/export (ISBOSCN)’ controller, if this line is uncommented. When using the standard extension parameter, the document will be exported to an .xml file.

<action senderType="SboToPmx" objectType="2" transactionType="*" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboBusinessPartnerExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

The document will be exported after a business partner was created, updated or removed as defined with the extension for ‘Interface for SBO business partner im-/export (ISBOBP)’ controller, if this line is uncommented. The controller does not have a standard extension.

<action senderType="SboToPmx" objectType="67" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.Interfacing.SboWarehouseTransferExportAction, Produmex.Sbo.Logex.SboNotification.Actions"/>
</action>

After a warehouse transfer has been created, it will be exported as defined with the extension for the ‘Interface for SBO whs transfer im-/export (ISBOWT)’ controller, if this line is uncommented. The controller does not have a standard extension.