Produmex WMS integration with Inspect

When goods are delivered to a logistics warehouse, that's quite common to make quality control and then to release or reject them.

That's why the integration between Produmex WMS and Inspect makes total sense.

Hereunder you gonna find an example on how to set up this integration, but keep in mind that you should adapt it to meet your customers expectations.

With that customization, when an inspection order is passed it will :

• Post a PMX Move to update the Quality Status. You can retrieve it in the Traceability Report, and the Inspection Order Code is mentioned in the comment field.

• Print a label for each SSCC to identify them as Quality Controlled product.

STEP 1 : PRODUCT RECEPTION

In this scenario, I am going to receive the item MILK01 that needs to be controlled after reception.

This item will have the Produmex Quality Status QUARANTINE at reception and as a consequence, needs to be quality controlled.

STEP 2 : CONDUCT QUALITY CONTROL IN INSPECT

I set up the item to create an Inspection Order in Inspect per batch received.

I will then do the quality controls and complete the inspection order that will be closed.

STEP 3 : CAPTURE INSPECTION ORDER RESULTS IN SAP

My inspection control results are posted back to SAP in the UDT BOY_CLOUD_INSP_RESO.

I will capture this event using SBO_SP_PostTransactionNotice.

ACTION : add the code from PostTN_Code.txt in SBO_SP_PostTransactionNotice

• Event Trigger : when there is a new entry in UDT "@BOY_CLOUD_INSP_RESO"
• Action : it will insert data in Produmex Notification Listener queue (PMX_NOTQ) including the inspection order results ID ("@BOY_CLOUD_INSP_RESO"."Code")

STEP 4 : CONFIGURE PRODUMEX NOTIFICATION LISTENER

We gonna use Produmex Notification Listener so it should be installed for the company (Link to Wiki)

Then you should find the config file Produmex.Foundation.SboNotification.ServiceHost.exe.config in 

C:\Program Files\Produmex\Produmex SB1 Notification Listener (Company_Name)\

ACTION : add the code from PMX_NotificationListener_Config.txt in Notification Listener config file

• Notification Listener event trigger : record in PMX_NOTQ coming from Inspect (senderType="InspectToPmx" and objectType="BOY_CLOUD_INSP_RESO")
• Action : it will call a script file called InspectChangeQS_TN.cs passing some parameters (script created during STEP 6)

STEP 5 : DEFINE THE REPORT FOR THE CERTIFICATE LABEL

One of the expected action will be to print a label to identify the controlled goods.

This report needs to be created in Produmex Organizational Structure.

You can find the Crystal Report used in this example attached and you will need to create a dedicated Stored Procedure as well.

ACTION : Create the SP used by the CR PMX_SP_InspectionCertificate.txt

ACTION : Download and define properly the CR for your organization DefaultInspectionCertificate.rpt

NB : Pay attention to the report key that will need to be set during STEP 6

STEP 6 : CREATE THE SCRIPT FILE AND DEFINE EXPECTED ACTIONS

As seen on step 4, notification listener will call a script file to do the expected actions.

ACTION : add the script InspectChangeQS_TN.cs on a network folder

Here is a script description :

1. The script received "@BOY_CLOUD_INSP_RESO"."Code" from Notification Listener (called ResoCode in next queries)

2. It will call the view PMX_WMS_INSPECT_CHANGE_QS filtering on the ResoCode

   ACTION : create the view View_PMX_WMS_INSPECT_CHANGE_QS.txt

   NB : You need to adapt the view to determine the right report code  ("ReportCode") created in step 5, as well as the number of copies desired ("NbCopies")  and the printer name ("PrinterCode").

3. This view will retrieve Inspection Order related data (such as item code, GRPO DocEntry, Batch Nb, SSCC...) if and only if :

   - Inspection Results is PASSED

   - Goods have been received in a GRPO or in a Production Receipt

   - PMX Quality Status is QUARANTINE

   - Items are batch managed

4. If the view gives back results, then two actions will be triggered per SSCC identified in the view : 

   a. Update PMX Quality Status to RELEASED by posting a Produmex Move in SAP

   b. Print a label to identify the goods as controlled

ADDITIONAL INFORMATION :

You can now test the whole flow.

As mentioned, this is an example, you will need to adapt some part of it for every customer case.

If you are facing an issue, you can debug by shutting down PMX Notification Listener and see if a record is created in PMX_NOTQ.

Then you can activate logs of Notification Listener and Produmex Robot following this link to the wiki.

On the product certificate, you can print much more data coming from Inspect such as Inspection Date, Inspector name, test results, etc.. (link to Inspect data model)

If you try to print the label on a pdf printer, this will be tricky cause those kind of printer are usually working with interactive user, not batch. You can try to run PMX Notification Listener as a real user (setting in Windows Services) and use Bullzip Pdf Printer.