User Tools

Site Tools


implementation:wms:custom_view

7. How to customize Produmex WMS views

It is possible to customize some of the Produmex WMS queries through the use of the views.

7.1. List of customizable queries

Picklist proposal manager screen
Controller: 5.1.3.60. Picklist proposal manager screen controller
Standard view name

  • Production: PMX_PICKLIST_PROPOSAL_MANAGER_PRODUCTION
  • Sales: PMX_PICKLIST_PROPOSAL_MANAGER_SALES
  • Transfer: PMX_PICKLIST_PROPOSAL_MANAGER_TRANSFER

Stock allocation screen
Controller: 5.1.3.59. Stock allocation controller
Standard view name

  • Customer info: PMX_STOCK_ALLOCATION_SCREEN_CUSTOMER
  • Sales order info: PMX_STOCK_ALLOCATION_SCREEN_SALES_DOCUMENT

Route planning
Controller: 5.1.3.52. Route controller
Standard view name

  • Route details: PMX_ROUTE_PLANNING_DETAILS
    Because the order of the rows is defined in the ‘Route planning’ window, there is no ‘Order by’ field on the controller.
  • Open picklists: PMX_ROUTE_PLANNING_OPEN_PICK_LIST_PROPOSALS

Open documents report
Controller: 5.1.3.66. Open documents screen controller
Standard view name

  • Route: PMX_OPEN_DOCUMENT_REPORT_ROUTE
  • Pick list: PMX_OPEN_DOCUMENT_REPORT_PICKLIST
  • Proposal: PMX_OPEN_DOCUMENT_REPORT_PICKLIST_PROPOSAL
  • Move order: PMX_OPEN_DOCUMENT_REPORT_MOVE_ORDER
  • PMX Sales Shipping: PMX_OPEN_DOCUMENT_REPORT_PMX_SALES_SHIPPING
  • Container: PMX_OPEN_DOCUMENT_REPORT_CONTAINER
  • Weight orders: PMX_OPEN_DOCUMENT_REPORT_WEIGH_ORDER

Open sales order form
Controller: 5.1.3.42. Open Sales Orders Controller
Standard view name

  • PMX_OPEN_SALES_ORDERS_WITH_STOCK_STATUS

7.2. Customization process

Note: It is recommended to use the Form Setting tool for disabling a column or for changing the order of columns because making these changes in the view might cause issues with the query.

Example: stock allocation screen- customer

Open the controller of the view.

7.2.1. View name

The ‘View name’ field is filled with the standard view by default.
To customize the grid, make a copy of the standard view and adjust it. Do not adjust the standard view, because it will be overwritten during a version update.
Note: When adding columns always paste the new columns after the default columns. The order of the columns can be changed later on with the Form Setting tool.

In the example we added a new column with the source table.

Copy the new view name and paste it to the ‘View name’ field, then save it. Always restart the add-on after a parameter change.

7.2.2. Order by

To customize the sorting of the grid, change the clause in the ‘Order by’ field.
The order by clause will be included at the end of the query using the view. It can contain any column referenced by the view.

Note: When using SAP HANA, column names are case sensitive. Don’t forget the quotation marks when they are needed.

After adding the clause save it. Always restart the add-on after a parameter change.

7.2.3. Form setting tool

Open the ‘Form Setting’ window and go to the ‘Table Format’ tab.
To change the order of the grid, click on and hold a ‘Column’ field then drag and place it to the desired position. After saving it, the grid will be displayed with the newly set order.

To disable a column, disable the ‘Visible’ box next to the ‘Column’ field. After saving it, the disabled column will not be visible in the grid.

Please note: The customizations made by the Form Settings tool will affect only the user. To hide a column from every user, use the localization file. Please see: 7.3.3. Hide column

7.3. Localization

When adding a custom view without a translation file, the system will take the column name from the view.

To change the column name or to support more than one language, create a new custom translation file from the standard ‘ImportLocalizationKeys.xml’ translation file. The standard translation file can be found under the ‘Localization’ folder in the install zip.

Open the file with a text editor and find the Localization Key of the view. The Localization Key can be seen on the controller of the view.

Localization Key

Copy the node within <PmxLocalizationKey> and paste it to a new file. Make sure that you added the root tags.

<?xml version="1.0" encoding="UTF-8"?>
<TestRoot>
</TestRoot>

7.3.1. Add the translation of a custom column

The node within <PmxLocalizationProperty> contains the translation of one column. Copy the node of any column and paste it right after the <LocalizationProperties> tag or after any </PmxLocalizationProperty> tag.

Change the column number in Columns[number of the column].Title/Header Text after <LocalizationProperty>. The new column number must be one more than the existing highest column number.

The node within <PmxLocalizationValue> contains the localization value of a language.

The <LanguageCode> defines the language. You can find the languages and language codes on the OLNG table. Add the column title as the <LocalizationValue> to the node containing the corresponding <LanguageCode>. It is not mandatory to keep the localization values of every language. You can delete the <PmxLocalizationValue> nodes containing the code of languages not required.Save the file in xml format.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<TestRoot>
<PmxLocalizationKey>
    <Canceled>False</Canceled>
    <LocalizationKey>Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute</LocalizationKey>
    <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode>
    <LocalizationProperties>
   

   <PmxLocalizationProperty>
        <Canceled>False</Canceled>
        <LocalizationProperty>Columns[1].HeaderText</LocalizationProperty>
        <ExtensionCode>CONVSTR</ExtensionCode>
        <LocalizationValues>
          <PmxLocalizationValue>
            <Canceled>False</Canceled>
            <LocalizationValue>Type</LocalizationValue>
            <LanguageCode>3</LanguageCode>
          </PmxLocalizationValue>
          <PmxLocalizationValue>
            <Canceled>False</Canceled>
            <LocalizationValue>Type</LocalizationValue>
            <LanguageCode>16</LanguageCode>
          </PmxLocalizationValue>
        </LocalizationValues>
      </PmxLocalizationProperty>
   

 </LocalizationProperties>
  </PmxLocalizationKey>
</TestRoot>

7.3.2. Edit the title of a standard column

It is also possible to change the title of a standard column. Find the column based on the column number then simply rewrite the text after the <LocalizationValue> tag in the node with the corresponding <LanguageCode>.

7.3.3. Hide column

To hide a column from every user, add a new <PmxLocalizationProperty> node in the same way as described above. Change the <ExtensionCode> to ‘CONVBOOL’.

As the <LocalizationProperty> add Columns[number of the column].Visible. Add ‘False’ as the <LocalizationValue> to the node with the respective <LanguageCode>.

When using multiple languages, create a <PmxLocalizationValue> node for every used language.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<TestRoot>
<PmxLocalizationKey>
    <Canceled>False</Canceled>
    <LocalizationKey>Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute</LocalizationKey>
    <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode>
    <LocalizationProperties>
   

    <PmxLocalizationProperty>
        <Canceled>False</Canceled>
        <LocalizationProperty>Columns[13].Visible</LocalizationProperty>
        <ExtensionCode>CONVBOOL</ExtensionCode>
        <LocalizationValues>
          <PmxLocalizationValue>
            <Canceled>False</Canceled>
            <LocalizationValue>False</LocalizationValue>
            <LanguageCode>3</LanguageCode>
          </PmxLocalizationValue>
          <PmxLocalizationValue>
            <Canceled>False</Canceled>
            <LocalizationValue>False</LocalizationValue>
            <LanguageCode>16</LanguageCode>
          </PmxLocalizationValue>
        </LocalizationValues>
      </PmxLocalizationProperty>


</LocalizationProperties>
  </PmxLocalizationKey>
</TestRoot>

7.3.4. Import the translation file

Use the Produmex Import Tool to import the translation file.

Select the database with the connection string then add the file path to the field next the ‘Import Localization’ button or click on the ‘Browse’ button and browse the file. Click on the ‘Import Localization’ button to import the file. Restart the add-on.

Import tool

The translation file will be overwritten during a Produmex database upgrade therefore you have to repeat the import after every Produmex database upgrade.

implementation/wms/custom_view.txt · Last modified: 2018/06/25 11:08 by csuhaa