This is an old revision of the document!
Produmex WMS How-to Guides
- How to Migrate and Export/Import the SAP HANA Schema
- How to Convert a SAP Delivery Report to a Produmex Delivery Report
- How to Get an Overview of the Open Amount of Clients/Suppliers on a Certain Date
- How to Print Documents with a Batch File
- SQL Job that Creates a txt File in a Certain Path
- How to Change the Starting Number for Produmex Documents
- How to Print Documents Automatically with Notification Listener
- How to Update the Standard Location/Zone Automatically
- How to Configure Handheld Devices to Keep Configuration after a Cold Boot
- How to Preprint Pallet Labels
- How to Copy Large Organization Structures with the Import Tool
- How to Create a Test Environment
- How to Use the Export/Import Wizard in SAP HANA Studio
How to Migrate the SAP HANA Schema
- The following documentation is for Produmex WMS version 19.2 and later. If you use a previous version, click here.
- The next steps have been tested on HANA 1.00.112.03 and 1.00.122.05.
There are some extra steps to perform in order to migrate a company database from MSSQL to HANA, when Produmex WMS is also running on that database.
1. Before executing the SAP migration tool, run the following query on the MSSQL database:
ALTER TABLE PMX_ADDON ADD CONSTRAINT PK_PMX_ADDON PRIMARY KEY CLUSTERED (DbUserName)
2. Install the correct HANA client version.
3. Run the SAP migration tool (migration.exe) from the SAP Patch Level installer.
4. If necessary, upgrade the company patch level on the target HANA server.
5. Log in once to the company using the SAP Business One client, set SAP license.
6. Install the Produmex Tools from ProdumexSuiteInstaller (HANA version)
7. Run the Produmex Hana Migration Tool, which you can find in the Produmex Tools folder. (c:\Program Files\Produmex\Produmex Tools\)
It does the following:
- Removes the primary key on PMX_ADDON that was created at step 1.
- Creates all SQL sequences for auto-incremented columns.
8. Restart the HANA database server, so it reinitializes the sequences.
9. Run the Produmex Tools Config and upgrade the database (ProdumexSuiteIsntaller).
10. Modify the SBO_SP_TRANSACTIONNOTIFICATION procedure.
- 3.4.1. Enable the standard PMX stored procedure Topic: 3.4.1.2. With SAP HANA
Print Documents Automatically with Notification Listener
It is possible to automatize document printing with the help of the SBO Notification Listener.
1. List of documents
List of documents that can be printed automatically with the standard solution
| Document type | Object type code | Default report | Supported transactions | PMX_NOTQ Column |
|---|---|---|---|---|
| pick list | PMX_PLHE | DefaultPickList.rpt | A U D L | DocEntry |
| sales order | 17 | A C U L | DocEntry | |
| purchase order | 22 | DefaultPurchaseOrder.rpt | A C U L* **See: section 4 | DocEntry |
2. Set the report
2.1. Customize the report
For reports, the Notification Listener will use the Column and Key values from the PMX_NOTQ table as the Crystal Report parameters. In order to print with the Notification Listener, change the input parameter of the report to the Column value.
Open the default report in Crystal Reports. Go to Field Explorer and expand the Parameter Fields. Rename the parameter to ‘DocEntry’ (Column value).
In the example we set the Notification Listener to print newly created pick lists automatically. The Column value in the PMX_NOTQ table is ‘DocEntry’ therefore in Crystal Reports we rename the standard ‘@pickListDocEntry’ to ‘DocEntry’.
Save it as a new report. Make sure that you save it to the folder that is defined for the reports on the ‘Reports’ tab of the organizational structure.
In the example we save the report as ‘DefaultPickListForSBONotification.rpt’.
2.2. Define the report in the organizational structure
In order to use the pick list in other flows properly, create a separate entry for this report on the ‘Reports’ tab of the organizational structure.
3. Configure the Notification Listener
Open the config file of the Notification Listener. Uncomment the following transaction line:
<action senderType="SboToPmx" objectType="PMX_PLHE" transactionType="A" logic="Produmex.Sbo.Logex.SboNotification.Actions.PrintReport, Produmex.Sbo.Logex.SboNotification.Actions"> <parameter name="ReportPath" value="DefaultPickListForSboNotification.rpt"/> <parameter name="PrinterDevice" value="Printer02"/> </action>
Adjust the following values in the transaction line:
- objectType: add the code of the object type. See the list of the document types for the corresponding object type value.
- transactionType: specify the transaction type. Possible values:
- 'A'=add
- 'U'=update
- 'L'=close
- 'D'=delete
- 'C'=cancel
- '*'=all
Please note: Not every transaction type works for an object. Please see the table that contains the supported transaction types for each object
- Printer: Add the printer code from the organizational structure as the value of the “PrinterDevice” parameter.
- Report path: Add the custom report as the value of the “ReportPath” parameter.
In our example we set the Notification Listener to automatically print newly generated pick lists.
Therefore the object type is “PMX_PLHE’ and the transaction type is ‘A’. The code of the printer is ‘Printer02’ and the report name is ‘DefaultPickListForSboNotification.rpt’.
Please note that when a pick list is created, its status is ‘Not Ready’. When creating a similar setting than in the example, be aware that the Notification Listener will print the pick list in the non-ready state.
When the Notification Listener is running the report is automatically printed after the transaction.
4. Automatically print report for closed purchase orders on goods receipt
There is a special transaction line in the config file of the Notification Listener to print the purchase orders after a goods receipt.
Create a new report as described above.
In the configuration file of the Notification Listener, find and uncomment the following transaction line:
<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>
Adjust the printer and the report path as described above.
How to configure handheld devices to keep configuration after a cold boot
Overview
Handheld devices have different rebooting options based on their operating system:
Windows CE
- warm boot:
- clears program memory
- keeps storage memory
- cold boot:
- clears both program and storage memory
- keeps flash memory and memory card
- returns formats, preferences and other settings to factory default
Windows Embedded Handheld
- warm boot:
- clears program memory
- keeps storage memory
- cold boot:
- clears program and storage memory
- keeps persistent memory
- on Motorola devices resets the Real-Time-Clock
- clean boot:
- clears program, storage and persistent memory
- keeps flash memory and memory card
- returns formats, preferences and other settings to factory default
On devices that have Windows CE as an operating system, it is advised to install and configure Produmex applications in a way that they will resist after a cold boot. The installation and configuration method is device-dependent.
1. Motorola/Symbol device
On Motorola devices, all memory is volatile except the /APPLICATION and /PLATFORM folders (flash memory). The /APPLICATION folder is used to store application programs.
1.1. Produmex WMS
To keep the configurations after a cold boot, store the following files in the /APPLICATION folder:
- RDP file: Setup the remove desktop connection as described in: Remote desktop connection. Make sure that you save it in in the \APPLICATION folder.
- .reg file: The registration file that contains specific registry settings. See: Details of the .reg file
- Default.xml file: This file is for the scanner setup. It contains scanner settings such as DataWedge setup and intercharacter delay setting
- TSC.CPY: This file contains the commands to copy the .rdp and the default.xml file after a cold boot. See: Details of the .cpy file
Download the example files from the FTP. \\In order to keep the Wi-Fi settings, configure it as described in Setup the Wi-Fi connection, then export it to the /APPLICATIONS folder. This way it also will be automatically reimported after a cold boot.
Details of the .reg file
After a cold boot the Motorola system will check for .reg files in the /APPLICATION folder and will place these files back automatically. See the example file here: Power-Desk-Vol-RDP.reg
To restore the power usage setup insert the following to the .reg file:
REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts] "BattSuspendTimeout"=dword:00000000 "ACSuspendTimeout"=dword:00000000 "ACResumingSuspendTimeout"=dword:0000000F "BattResumingSuspendTimeout"=dword:0000000F "ChangeEvent"="PowerManager/ReloadActivityTimeouts" "ACUserIdle"=dword:00000000 "BattUserIdle"=dword:00000000 "BatteryPoll"=dword:000007D0
Optional settings:
1. Background image
To restore the background picture insert the following:
[HKEY_CURRENT_USER\ControlPanel\Desktop] "Wallpaper"="\\APPLICATION\\DestopPicture.PNG" "tile"=dword:00000000
Adjust the image name (in the example: DestopPicture.PNG). Supported formats: PNG or JPG.
2. Mute touch sound
To mute the sound on touch insert the following:
[HKEY_CURRENT_USER\ControlPanel\Volume] "Screen"=dword:00010000 "Key"=dword:00010000 "Mute"=dword:00000007 "Volume"=dword:99999999
This setting will mute only the sound when touching the scanner. All other sounds (eg. when scanning, or in the case of an error) will still work.
3. Set default RDF user
To set the default RDP user for the device insert the following:
[HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\UsernameHint] "RDP SERVER IP"="DOMAIN\\WINDOWS_USER"
Adjust the domain name (in the example: DOMAIN) and the user name (in the example: WINDOWS_USER) according to your specifics.
Details of the .CPY file
On a cold boot the system will look for .cpy files in the /APPLICATION folder then initiate them. The .cpy files will copy files from a non-volatile source to a destination. See the example files: TSC.CPY, TSC.CPY.1
In the .cpy file the source file and path and the destination file and path will be separated by ‘>’.
- To place the RDP file on the desktop for easy access add:
\Application\PDMX.rdp > \Windows\Desktop\PDMX.rdp
- To places the scanner settings in the correct location add:
\Application\Default.xml > \Windows\DataWedge\Config\Profiles\Default.xml
1.2. Produmex Scan
To keep the configurations after a cold boot, create an install folder in the non- volatile /APPLICATION folder. The install folder should contain the following files:
- the application loader that can be found in the /WINDOWS folder on the device
- on OEM devices, the file name is: wceldcmd.exe
- on non-OEM devices, the file name is: wceload.exe
- .cab file (For example the Produmex Scan install cab file)
The /APPLICATION folder also should contain:
- .reg file (for the application loader)
- .reg file (for the configurations)
Details of the .reg file – for the application loader
The .reg file runs the .cab file(s) on cold boot only.
[HKEY_CURRENT_USER] "Name"="\Application\ INSTALL FOLDER NAME \wceldcmd.exe" "Command"="/delete 0 \Application\INSTALL FOLDER NAME\EXAMPLE.cab" "Continue"=dword:1 "ColdBootOnly"=dword:1
- /delete 0: this parameter determines that the .cab file will not be deleted after the installation
- ColdBootOnly: this parameter determines that no changes will be made in the case of a warm boot
Adjust the .cab file name and path in the 'Command' parameter.
Details of the .reg file – for the configurations
After installing and configuring the applications, export the registry. From the Registry menu choose the ‘Export Registry File’ option. Save the file to the /APPLICATION folder.
The following values store the configurations for Produmex Scan:
Example:
[HKEY_CURRENT_USER] "Database"="DATABASE NAME" "ServerUrl"="SERVER_URL” "Language"="English" "NoBuiltInButtons"="N" "TesterMode"="N" "DemoMode"="N" "CustomizationAssits"="N" "WinLayout"="Normal" "HID"="HID" "RegPersisted"=dword:00000001
2. M3 Mobile
On M3 Mobile Devices use the MS-Backup function to restore configurations and registries after a cold boot. In order to use the MS-Backup you must have copy of the flash disk files provided with the OS.
2.1. Preparation
Open the power properties and set the configurations as below to prevent the device going to sleep mode:
MS-Backup Usage:
Launch MS-Backup by either
- My Device > Flash Disk > xPIMS > MS-Backup.exe
- Start > Programs > Utility > MS-Backup
From MS-Backup, select whether you want to backup all data or personal information management (PIMS) data. Then select the ‘Name’ and the ‘Location’ and press ‘Backup Start’ to back up the data. To restore the data, go to the 'Restore' tab and select appropriate data then press 'Restore Start'.
2.2 Auto Restore After Cold Boot
Automatically restoring data after cold boot requires a little configuration in M3.ini. In addition, backup data must be saved as 'ExBackup' as shown in the above figures.
Set folder options to view hidden files: Open ‘Folder Options’ by My Device > View > Option and uncheck all options.
Open M3.ini file with Microsoft WordPad. Launch WordPad and open the M3.ini from \Flash Disk\StartUp.
From the M3.ini file, set the ‘Install’ and ‘Reset’ value of [RESTORE] to '1' as shown in the following figure.
[KEYPAD_LED] Install=0 //Automatic restore after Hardware reset with a help of MS-Backup.exe. //ExeFile: Program Path //Reset: 0-> reset after restore, 1-> no reset after restore //Type: 0-> restore all data, 1-> restore only PIMS data [RESTORE] Install=1 ExeFile=\FlashDisk\xPIMS\MS-Backup.exe Type=0 Reset=1
After cold boot, the device will automatically restore the backup data (ExBackup) and perform a warm boot after a successful restoration.
Preprint pallet labels
It is possible to pre-print logistic labels so they can be used later when creating stocks.
Because in this case the SSCC’s do not exist in the system when they are printed, it requires a special procedure in order to create the labels and to avoid SSCC duplications.
1. Add the stored procedure
Before adding the stored procedure, go to the ‘SSCC tab’ of the Organizational Structure and check the ‘Current SSCC’ number.
Add the ‘PMX_SP_GoodsReceiptLabel_Mass’ stored procedure to the PMX_<database_name> database. Modify the start SSCC by entering the current SSCC number plus one as the value for the set @currentSSCCInt parameter.
The added SSCC number will be the first SSCC number to be printed.
EXAMPLE: In the example the Current SSCC number was 10, therefore we added 11 as the start SSCC number.
2. Crystal Reports
Open the ‘GoodsReceiptLabel_MASS’ report in Crystal Reports.
Set the datasource location of the report to the ‘PMX_SP_GoodsReceiptLabel_Mass’ stored procedure.
Print the labels from Crystal Reports. On the ‘Enter values’ form add the number of the logistic labels to print to the @count field and click on the ‘Ok’ button.
3. Modify the current SSCC number
As the pre-printed SSCC’s do not exist is the system, the current SSCC number did not change. In order to avoid SSCC duplication, increase the current SSCC number with the number of the printed SSCC’s on the PMX_SSCC table.
EXAMPLE: We printed 10 labels therefore we increased the value in the Current SSCC column by 10. Because the original value was 10, we set 20 as the new value.
