How to Easily Improve Traceability via M3 and your Delivery Note

Scenario: The Quality Department have informed you that they want the trailer number pirnted on every delivery note from now on however, the despatcher will only find out the trailer number at the time of loading.

For the solution I will use the Ext tracking no: textbox in the MWS410/F panel.

Solution Part 1: StreamServe

  1. Open the PageOut and add a label to the header section of your delivery note
  2. Enter the following text into the label: Trailer Number
  3. Drag the field AHOQETRN from the Field folder in the Message window and place it opposite (or beneath) the label Trailer Number
    1. If you have multiple pages you need to complete this step for each page
  4. Export and deploy the project

Solution Part 2: M3

  1. Open MWS410 (Delivery. Open Toolbox)
  2. Right-click on the delivery that you are currently despatching and select Change
  3. The panel MWS410/E opens however, you need to click Next (or hit Enter) to open panel F
  4. In the highlighted textbox in Figure 1, enter the trailer number which is being used for the despatch and click Next.
  5. Click the Back button until you return to MWS410 and proceed with the despatch as normal.

48
Figure 1: Snapshot of MWS410/F
When the Delivery Note is generated it will display the trailer number used for the despatch.

 

 

How to control the display of a label based on the value of a spool-field

SCENARIO: Some of your customers require their VAT number to be displayed on the invoice document. Your M3 customer master file only has the VAT number for several customers however you do not want to have the label VAT Number appearing with no accompanying value on an invoice.

  1. Open the OIS1990H event and transform the spool-field 0HWYVRNO into a variable 
  2. Open the PageOut and insert a Static Text object (this will be your label) to your canvas
  3. Rename the label to VAT Number
  4. In the Message window, collapse the Variable folder and drag the variable $0HWYVRNO to your canvasto the right/below of the label.
34
Figure 1: The Variable folder on the PageOut canvas
  1. Right-click on the label and select Edit Script…
  2. Insert the following code:

    if ($0HWYVRNO = “”) {
    skip();
    }
    else {
    {}
    }

The label VAT Number will now only appear if a value exists for the spool-field 0HWYVRNO. If the spool-field 0HWYVRNO value is blank then the label will be skipped (i.e. not appear).

Export and deploy and test!

Troubleshoot: Control Center producing the error: ‘Fatal error: portx spool=connector (port/printserver)’

Explanation: You are probably trying to create a new output connector in the Platform and you are using the connector type Spool and you are encountering this error. This is because you have not entered % into the To property – see Figure 1

33
Figure 1: Missing To property value

 

  1. Open the Platform
  2. Right-click on the new Output Connector and select Settings…
  3. From the Selected layer dropdown select Production (Physical)
  4. Make sure your Connector Type is Spool
  5. Enter % as the To property value
  6. Click OK

Export, deploy and test!

Troubleshoot: Control Center producing an ‘Fatal error: args start.arg(2:No such file or directory)’ error

Explanation: The first time you deployed an exported project in Control Center you did not check the Include argument file in export checkbox

The very first time you export a project you must check the Include argument file in export checkbox so that the start.arg file is created in the Working Directory

Figure 1 displays the checkbox to check:

32
Figure 1

Export, deploy and test!

Troubleshoot: Control Center producing the ** UNLICENSED ** warning

Explanation: The application license is not present in your Working Directory folder structure

  1. Obtain the strs.lic file

TIP: Copy an existing / valid file from the same path as another application of another licensed project

  1. Open the Working Directory by accessing the Platform folder on the host server:

..\ManagementGateway\5.6.1\root\applications\Application_Name\Platform

  1. Paste the file into the Platform folder

31

Export, deploy and test! The ** UNLICENSED ** will now disappear.

 

 

Troubleshoot: Control Center producing an ‘There is already an instance running of service’ error

Scenario: You try to restart your Control Center application but Control Center only produces the error message in Figure 1.

code9
Figure 1: Control center error
  1. Open the Services application on your host server and check the status of the Control Center application – it should be status Stopping.
  2. Open Task Manager and select the Processes tab and view the CommunicationServer.exe process (see Figure 2) – This process needs to be killed.
  3. To kill this process, right-click on the process and select End Process.
  4. Start your application and it should run normally.
30
Figure 2: Task Manager process view