You need the following components to be able to use Produmex PDC for Production:
The PDC bookings created by the mobile PDC are stored in the SAP database/schema in user tables. These tables are created by the Produmex Manufacturing add-on which means you cannot use the Produmex PDC until you have installed the add-on and run the database setup. The used production orders also need to have the Produmex Manufacturing Settings in order to be able to user the mobile client.
For more information about installing the Produmex Manufacturing Add-on, please see: Produmex Manufacturing Installation Guide
Not all versions of the Produmex Manufacturing add-on and the Produmex PDC client are compatible with each other. We recommend always using the latest versions of both.
Make sure you do not run both the 32-bit version and the 64-bit version Service Broker on one environment as they conflict with each other. Only one service broker instance should be installed on a server at any time.
The Service Broker establishes the connection between the company database/schema and the application on the mobile device. It queries the data from the database/schema and sends it to the mobile application, and it creates the SBO documents based on the requests from the mobile devices. The SBO documents are created with SAP DI API 32bit version.
The Service Broker can run as a service or from a command window. It creates threads for the different requests which are independent from each other so if one thread has a problem it can be closed and the others are not influenced by it.
If the Service Broker does not run, the communication between the clients and the company database/schema is not possible.
The service broker creates its log files at C:\ProgramData\BX\BX Service Broker\Logs. The ProgramData folder is hidden, you have to either enable 'Show hidden folders and files' in Windows Settings or you have to enter it directly to the address bar in Windows Explorer:
Install the service broker on the server which has access to the company database/schema. The installation file is an .exe file with a name like this one: BxServiceBroker.Setup.exe.
After launching the .exe file, the End User Licence Agreement will open up. Produmex Service Broker can only be installed if the License Agreement is accepted.
When you start the installation, the Produmex Service Broker installer will request information based on the system and will set up the service based on the information you enter.
The installer will first ask the user who will be assigned to the service broker service in windows. This must be a user who has rights to write the event log and the program data directory where the logs are created. The service broker service will also make a connection to the company database/schema, the user must have rights for that as well.
Local System users usually do not have the right to use printers, therefore, it is recommended to configure a Windows user.
The default port for the communication between the service broker and the clients is 50231. The installer will open the firewall for this port automatically, but if you change the port, you will have to change the firewall settings manually.
You can also set up the start mode of the service. The recommended start mode is Auto.
On the next screen specify a password for the Service Broker Administration web page.
Then you have to provide connection data to the database server.
Select the database type from the dropdown menu.
When working on SAP B1 Cloud, add the domain user name and password as well.
Default SAP Company
After that you have to set up the company database/schema. You can only set up one company here, if you have more than one database/schema, you can add the others in the Produmex Service Manager after installation. For more information please see: Produmex Service Manager-Add new database.
Enter an SAP user here which has at least an indirect access license as of SBO 9.2. PL08.
At the end of the installation you will see a summary screen about you settings. Click ’Finish’ to end the installation.
Configure dependency from the SBO Server Tools service on an MSSQL system
If the server where Produmex Service Broker runs needs to be restarted frequently, we advise to configure dependency from the SBO Server Tools service.
When Produmex Service Broker starts, it tries to connect to the SAP environment. If the connection fails, Produmex Service Broker will not start.
If the Produmex Service Broker is dependent from the SBO Server Tools service, it will only start after the SBO Server Tools service is started, therefore it will be able to connect to the SAP environment.
To configure the dependency, open the Command Prompt window and enter the following:
C:\>sc config BXServiceBroker depend=B1ServerTools
On the Dependencies tab of the Produmex Service Broker properties you can see that the dependency is successfully added:
Make sure you do not set the dependency on HANA enviroments. Since the Produmex Service Broker is a Windows service, SAP HANA and Produmex Service Broker are running on separate servers. In order to avoid this issue, make sure that the HANA server is already running when you restart the server of the Service Broker.
The Produmex Service Broker can work together with different Produmex add-ons. In order to do it, it uses the dlls of the given add-on. You need to install these dlls with the server installer which has a name like this: ProdumexADD-ON NAME_ServerSetup_version nbr_ SBO Version_Database server type.32/64 bit installers.zip.
The add-on and the server dlls must be for the same version. If you use different versions, error messages may appear. You simply have to start the installer and it will automatically copy the dlls and then restart the service broker service. You can check the installed modules in the Service Manager. For more information please see: Configuring Produmex Service Broker
The PDC Processor also runs as a service on the same server as the Produmex Service Broker. It processes the created PDC bookings and it creates the necessary material bookings based on the milestone settings in the belonging production order. The bookings are usually issue for production or receipt from production bookings.
If the PDC Processor doesn’t run, the PDC bookings are not created therefore the stock data of materials or products are false. The last run date and time of the PDC Processor can be seen on the PDC tab of Produmex Manufacturing settings.
The last run date and time of the PDC Processor is logged in the [@BXPCONFIG] table on the ‘PDCProcessor Last Run Date’ [BXPPRCDT] and ‘PDCProcessor Last Run Time’ [BXPPRCTM] fields. We recommend that you create an SAP alert which checks the last run date, and if it has been more than 5 minutes ago and there are unprocessed PDC entries (U_BXPPrcSt = 0) in the [@BXPPDCBOOKING] table, it triggers an alert to the system administrator to restart the PDC processor service on the server.
The PDC processor creates its log files at C:\ProgramData\BX\BX Service Broker\Logs. The ProgramData folder is hidden, you have to either enable 'Show hidden folders and files' in Windows Settings or you have to enter it directly to the address bar in Windows Explorer.
The Produmex Service Manager is a standalone program that can handle the Produmex Service Broker and other Produmex services. Service parameters, connection data to the database server, and the connection data to the company database/schema can also be modified on the Service Manager.
It is automatically installed by the Produmex Service Broker installer. The Service Broker will automatically appear in the Produmex Service Manager, together with all other installed Produmex services that are supported by the Service Manager.
Click on the ’Setup Companies’ button. On the opening window you have to enter the connection data to your SAP company database/schema.
How to check the port number on SQL
Open the SQL Server Configuration Manager. Select the SQL Server instance then right click TCP/IP on the right side and click on Properties. In the small window go to the bottom and check the port number.
Please note: in this example there are no instances, so the port is the default 1433.
When working on SAP B1 Cloud, add the domain user name and password as well.
At 'Language' it is possible to modify the language of the DI API transactions.
If you click on Test DB Connection, Service Manager will try to connect to the server with the given data. If the connection can be established, you will get a message: Database connection test – success!
Click on the Setup Companies button.
On the opening ‘Setup companies’ screen check the connection data. If you would like to add a database from a different database server, modify the connection parameters then click on the ‘Test DB Connection’ button to test the connection. The modification of the connection parameters does not affect the connection settings of the already added databases.
Click on the ‘+’ icon to add a new database/schema.
On the ’Database Setup’ window select the database/schema from the dropdown menu.
Enter an SBO User and its password to create the connection to the database/schema. SAP employees are used for log in the mobile device. Transactions initiated by the employees will be posted by the SAP user defined for the Service Broker. The SBO user must have the authorizations to create stock related bookings in SAP Business One (Delivery, Goods Receipt PO, Stock Transfer, etc.) The SBO user also need at least an SAP Indirect Access license type as of SBO 9.2. PL08.
Click on the ‘Save’ button then close the window. You can close now Setup Companies and go back to the Service Manager main screen.
Now you have to assign your companies to the Produmex Service Broker and other Produmex services.
Click on the ‘Companies…’ button and select the company database/schema on the opening ‘Select Companies’ screen.
It is possible to start the PDC application with a -database parameter. If multiple databases are configured in the Service Broker, you do not have to start the PDC Configuration every time you would like to switch between databases.
Create shortcuts for the BXPPSMobilePDCClient.WinForm.exe. The file is located in C:\Program Files (x86)\Produmex\Produmex PDC
Add the database with the '-database=' parameter to the end of the file path in the Target field.
Please note: Make sure that the Produmex Manufacturing add-on is installed on all databases with the same version as the Service Broker.
The Produmex Service Broker can work together with different Produmex add-ons, therefore in the Service Manager you have to configure which add-on you want to use. To do that, click on the ‘Configure…’ button or select it from the line of the Service Broker.
If you set the 'Debug writeline log' parameter to true, it will write a log about each command the Service Broker processes. Only set it to true, if Produmex support asks you to do that.
'Kill time' means that if a thread doesn’t respond to a request within this time limit, it will be killed. The setting depends on your server. If you have a quick server, set it to a small number, if you have a slow server, set it higher. Default is 10 seconds.
'Modules to load' is the module of the add-on to which the service broker connects. It is automatically done by the module installer for you, so you only have to set this manually in specific cases. To add multiple modules, separate them by comma.
At the 'Port to listen on' you can set which port is used by the service broker to communicate with the clients. The default is 50231. Make sure that the port you set here is not blocked by any firewalls or antivirus software.
The 'Server Discovery Enable' turns on the feature that the client can look up the running service broker server automatically. It makes setting up the clients easier.
You have to assign an administrator user to the service in the Windows Service Manager, otherwise the Service Broker cannot connect to SBO and cannot write to its log files. If the Service Broker stops right after starting it, and in the log file you have access denied errors, then the cause is that you haven’t assigned the administrator user to the service.
Produmex Service Broker tab
On the Produmex Service Broker tab you can see the loaded modules, and you can remove/install new modules if needed.
If you see a check icon before the module name, it means it could be loaded successfully. If a problem arises, you will see error beside the module name.
After you have set all settings and installed the server module, you can start the Service Broker service in the Service Manager by selecting first the service then clicking on the ‘Start’ button. If you want to stop a service, click on the ‘Stop’ button.
You can also stop or start the services from windows service manager, but you cannot change the Produmex settings there. It is recommended that you set the service to Automatic start and that you set the recovery options to Restart at Recovery in Service Properties for the service.
If you want to start the Service Broker from the command window, you can start it with “C:\Program Files (x86)\Produmex\ServiceBroker\BxServiceBroker.Console.exe” (or Service Broker (Console) program in the Windows Start menu) and you will see a window like this:
The use of the command window is recommended for debugging purposes. In production environment the use of the service is more efficient.
The Produmex PDC Client must be installed on the client computer. The installer is an exe file located in the ProdumexManufacturingMobilePDCClientSetup_version number_SBO version_Database server type.32/64 bit version.zip folder. For the time being it is a windows application that uses .NET 4 framework.
Extract the .zip folder, initiate the installation and follow the steps of the Produmex PDC Setup Wizard.
After you have installed it there will be two new programs at All Programs > Produmex: