2.3. User defined tables
The user defined tables are available via SAP Tools > Default Forms.
Note: The following user defined tables are no longer used:
- Links between GS1 units of measurement and GS1 measure types (PMX_LUMT)
- Produmex measure types (PMX_PMTY)
2.3.1. Box for WAS (PMX_BFWA)
Definition of all boxes that can be used in the warehouse automation system (WAS).
Box type
The box type can be selected from a list. The list comes from the Box type for WAS UDT.
2.3.2. Box type by item for WAS (PMX_BTIT)
If needed, it can be specified how many items in a certain box type can be stored.
Box type
The box type can be selected from a list. The list comes from the Box type for WAS UDT.
Quantity
The quantity of the item that can be stored in the given box type.
2.3.3. Box type for WAS (PMX_BTWA)
Definition of box types that can be used in the warehouse automation system (WAS).
# Compartments
The number of compartments a box has
2.3.4. Container shipping status (PMX_CSST)
This table holds the shipping statuses a container can have.
Sequence
The sequence is used for the sorting on the combobox on the container management screen.
2.3.5. Defines the weighing scales available to a specific thin-client (PMX_TCSC)
Links a scale to a thin client.
Thin client code
The code of the thin client, as defined in the organizational structure.
Scale def. code
The scale definition code. It can be selected from a list coming from the Defines the weighing scales available to a specific thin-client UDT.
2.3.6. Down time types (PMX_DTTY)
List of down time types. This is used in the time registration module when entering a down time.
2.3.7. List of selectable drivers (PMX_DRIV)
A list of known drivers that can be selected during shipping process.
Is the record canceled?
If it is set to Yes, the record is cancelled. The user cannot select cancelled records when the data is asked on the scanner or the touchscreen.
2.3.8. Freight charges definitions (PMX_FCDE)
Configuration of freight charges that will be added to a sales document.
Freight code
The line number of the freight to be added.
The freight charges are added on a sales order when it is added. The line number must correspond to a line in the freight charges screen on sales order header:
Shipping type code
The shipping type code where this freight charge needs to be added.
Cost
The price to be added.
Min. document price
The minimum document price that is required to add the cost.
Example:
| Freight code | Shipping type code | Cost | Min document price |
|---|---|---|---|
| 1 | 1 | 30 | 0 |
| 1 | 1 | 20 | 100 |
| 1 | 1 | 0 | 200 |
If the price is between 0 and 99,999999, a cost of 30 will be added to Freight for shipping type 1
If the price is between 100 and 199,999999, a cost of 20 will be added to Freight for shipping type 1
If the price is above or equal to 200, no cost will be added to Freight for shipping type 1
2.3.9. Expiry definitions (PMX_EXDE)
A list of possible expiry definitions. This is used to calculate best before dates.
Days
The number of days to add.
Months
The number of months to add.
Years
The number of years to add.
2.3.10. Hidden Fat Client buttons (PMX_HFCB)
This table holds configuration to hide buttons on flows used in the Fat Client.
This configuration table is intended to be used by consultants who are familiar with the workflows and know how to retrieve the needed information to complete the configuration.
Calling workflow
The work flow that is used.
Title key
The title key of the screen where the button needs to be hidden.
Button key
The button key of the button that needs to be hidden.
Disabled
Check this checkbox to disable the configuration to hide the button.
Pmx User Group
The user group this configuration applies to.
If no user group is set, it applies to all users.
Examples:
- How to hide button 'No PO' on the reception flow
- How to hide button 'Change lined up location' on the production flow
2.3.11. Item storage location type (PMX_ISLT)
This table holds a list of item storage location types.
An item and/or location can have this property.
It is used in the functionality for Location Suggestions.
2.3.12. Link packline to zone table (PMX_LPLZ)
Defines the zone linked to pack lines. This is use on the ‘Consolidated packing’ flow.
The pick list destination location should be on that zone. Also the available stock to pack needs to be stored on that zone.
The level of the zone is 1. This means that the zone you define here needs to be the direct zone of the location.
Name
The code of the user.
Code of the pack line
The code of the pack line, as define in the organizational structure.
Code of the zone
The code of the zone, as define in the organizational structure.
2.3.13. Link usergroup to authorization table (PMX_UGAU)
Define the authorization a user group can have.
User code
The code of the user.
User group code
The user group code. The user group code can be selected from a list. The list comes from the ‘User group for PMX’ UDT.
User authorization code
The user authorization code. The user authorization code can be selected from a list. The list comes from the ‘User authorization definition’ UDT.
Value
The actual authorization.
Possible values:
- Disabled
- Enabled
- Hidden
2.3.15. List of actions for certain events (PMX_EVAC)
Defines actions that can be performed for certain events.
Possible events:
- Open extra documents when another print job within SAP is performed.
This print job needs to be for Sales quotation/order/invoice.
It will get documents defined on the item master data in the column defined.
Configuration:
- Table name = OITM
- Colum name = [a column name within OITM where the path to the document that needs to be opened is stored]
- Object type = The object type for Sales quotation/order/invoice
- Action type = Does not need to be filled
- For event = Does not need to be filled
For event
Defines the event this action is for.
Action type
The type of action that needs to be performed.
2.3.16. List of selectable license plate (PMX_LIPL)
A list of known license plates that can be selected during shipping process.
Is the record canceled?
If set to Yes, the record is cancelled. The user cannot select cancelled records when the data is asked on the scanner or the touchscreen.
2.3.17. List of selectable trailer numbers (PMX_TRNR)
A list of known trailer numbers that can be selected during shipping process.
Is the record canceled?
If set to Yes, the record is cancelled. The user cannot select cancelled records when the data is asked on the scanner or the touchscreen.
2.3.18. List of warehouse to warehouse where serial numbers need to be entered (PMX_WSMM)
Defines whether a PMX serial number needs to be asked when performing a move between warehouses.
From warehouse (PMX)
The source warehouse. This is the code of the warehouse as defined in the organizational structure.
To warehouse (PMX)
The source warehouse. This is the code of the warehouse as defined in the organizational structure.
Ask serial number?
Do serial numbers need to be asked?
Print documents?
Do warehouse documents need to be printed?
2.3.19. Package Dimensions (PMX_PADI)
Depending on the pick list type, the user might have to add the dimensions of the package after a logistic unit is finished during picking and packing. The user can enter the dimensions manually or select a package dimension that was defined on this table.
Code
Internal code of the package dimension.
Name
The name of the package dimension that is displayed on fat client screens.
Is the record canceled? (Y/N)
If checked, it indicates that the record is cancelled and cannot be selected as the package dimension during picking or shipping. Cancelled records can be restored.
Width
The width of the package.
Length
The length of the package.
Height
The height of the package.
2.3.20. Port (PMX_PORT)
This table holds the ports.
It is used for the container management: Port of origin, port of destination.
Normal lead time (in days)
The lead time in days for normal delivery at this port.
This is used for calculation of dates in the container management.
Express lead time (in days)
The lead time in days for express delivery at this port.
This is used for calculation of dates in the container management.
2.3.21. Pmx priority (PMX_PRIO)
The Produmex priorities. This is used on pick list (proposals) and move orders. The system has already 3 predefined priorities:
- High (100)
- Normal (200)
- Low (300)
Sequence
A number defining the order of the priority. The value needs to be unique.
Order is done ascending. This means that 1 has a higher priority than 99.
Is default?
For the default priority this option should be set to true.
2.3.22. Produmex allergen types (PMX_ALLE)
A list of possible values an allergen can have.
This is used on the item master data to select an allergen.
2.3.23. Produmex batch attribute types (PMX_BATT)
The defined batch attribute types can be added to items in the Item Master Data window > Produmex tab > Attributes > Batch Attribute Code drop-down menu.
Convertor
The data is stored in the database as text. The system needs to know what type to convert it to. This can be set with the convertor.
Possible values:
- Int
- String
- Date
- Double
- List
Sequence
The sequence of the defined batch attribute types in the Batch Attribute Code drop-down menu.
The key for translation
The key that will be used for the translation of the title. When this is not set, the system will use MSG_TITLE_BATCH_ATTRIBUTE.<Code of the batch attribute>.
In case there is only 1 language in the company, a title can be entered here directly.
A list of possible batch attributes that can be linked to an item.
Some predefined codes have been added:
- COUNTRY_OF_ORIGIN: Country of origin
- MANUFACTURING_DATE: Manufacturing date
When custom batch attribute types are added, a translation should be added to the system. This translation is used on a device when entering the batch attributes.
The translation node for COUNTRY_OF_ORIGIN looks like:
<PmxLocalizationKey>
<Canceled>False</Canceled>
<LocalizationKey>MSG_TITLE_BATCH_ATTRIBUTE.COUNTRY_OF_ORIGIN</LocalizationKey>
<ApplicationTypeCode>SLIM_SCR</ApplicationTypeCode>
<LocalizationProperties>
<PmxLocalizationProperty>
<Canceled>False</Canceled>
<LocalizationProperty />
<ExtensionCode>CONVSTR</ExtensionCode>
<LocalizationValues>
<PmxLocalizationValue>
<Canceled>False</Canceled>
<LocalizationValue>Enter the country of origin</LocalizationValue>
<LanguageCode>3</LanguageCode>
</PmxLocalizationValue>
<PmxLocalizationValue>
<Canceled>False</Canceled>
<LocalizationValue>Vul het land van herkomst in</LocalizationValue>
<LanguageCode>16</LanguageCode>
</PmxLocalizationValue>
</LocalizationValues>
</PmxLocalizationProperty>
</LocalizationProperties>
</PmxLocalizationKey>
The LocalizationKey starts with ‘MSG_TITLE_BATCH_ATTRIBUTE.’
Add the code of the attribute type at the end.
When making a complete valid translation file to import, make sure the root tags are also added:
<?xml version="1.0" encoding="utf-8"?> <TestRoot> </TestRoot>
AI
The application identifier. It allows a scanned value from a barcode to be automatically stored in the batch attributes.
2.3.24. Produmex batch attribute valid values (PMX_BAVV)
A list of possible values a batch attributes type can have.
Batch attribute type
The batch attribute type. This is a link to the table PMX_BATT
Value
The possible value for the batch attribute type
2.3.25. Produmex cycle count – other operations filter (PMX_COOF)
Cycle counting can be done during other operations. To have a more flexible way of configuring when such a cycle count can be performed, configuration settings can be defined in this table.
[Days of the week]
Define whether the cycle count during other operations can occur or not on a certain day of the week.
Other operation type for cycle count
The type of operation where the cycle count can be performed.
Possible values:
- Ad hoc picking – Transport (Pick list or route)
- Ad hoc picking – Customer collect.
- Picking
2.3.26. Produmex item pick types (PMX_IPIT)
This lists the possible item pick types. This is used on the item master data on fields ‘Item pick type’ and ‘Item pick type 2’.
This is only used in the Zone Picking Flow.
2.3.27. Produmex Item Serial Number Format (PMX_ISFT)
In the Produmex Item Serial Number Format window serial number formats can be defined. The defined format applies to SAP serial numbers and Produmex serial numbers as well.
In the Serial Format column define the format of the serial number in .Net regular expression (regex). For more information on regex click here.
Example of serial number format:
- (SN)[0-9]{8}
- ^(SN)[0-9]{8}$
Symbols:
- The value in parenthesis ( ) is a constant character-string.
- The value in brackets [ ] defines the range of valid character values, e.g. 0-9, A-Z.
- The value in braces { } defines the length of the character set provided in the brackets [ ].
- The caret symbol ^ and the dollar symbol $ can be used to define the beginning and the end of the serial number pattern.
The defined formats are displayed in the Serial Number Format drop-down menu on the General tab of the Item Master Data window.
2.3.28. Produmex location types (PMX_LOTY)
A list of location types. These types can be selected on the organizational structure – location.
3PL item code
For 3PL invoicing only. The code of the item that will be used on the A/R invoices sent to the 3PL customers. The price of one day of storage in each location of that location type is represented by the 3PL item’s price.
The item must be non-inventory.
3PL active?
For 3PL invoicing only. If disabled, the price for this location type will not be included in the A/R invoices sent to the 3PL customers.
2.3.29. Produmex picklist types (PMX_PLTY)
Open the Picklist types table:
Tools > Default Forms > PMX_PLTY Produmex Picklist tyes
Picklist types are used on picklist proposals and picklists and can affect the following:
- if it is split to multiple picklist proposals or not,
- which users are allowed to pick the pick list (see: user picklist types),
- in which flows it can be picked,
- whether certain dimensions should be added during packing.
For the following Picklist workflows you must enable these settings in the Produmex Picklist types table:
| Picklist Type | Setting | Enable |
|---|---|---|
| Box Pick and Pack | Use for Picking? | Yes |
| Zone Box Picking | Use for Zone Picking? | Yes |
| Prepare carts | Use for multi picking? | Yes |
When creating a proposal, the system determines the picklist type based on the following settings in the mentioned order:
- Picklist type on document. The picklist type can be set on sales orders, sales invoices and warehouse transfer requests.
- Picklist type on business partner. A default picklist type for sales documents can be set for business partners on the Business Partner Master Data.
- Default picklist type. The default picklist type is the 'Standard' picklist type. Do not delete the 'Standard' picklist type as it might lead to errors when creating picklist proposals.
| Column | Description |
|---|---|
| Code | The code of the picklist type |
| Name | The name of the picklist type |
| Split PL on item pick type? | When this is true, several picklist proposals can be created, grouping items with the same item pick type. |
| Split PL on item pick type 2? | When this is true, several picklist proposals can be created, grouping items with the same item pick type 2. |
| Full pallet picklist type | When this is set, the created proposal is split up between full quantity (this is a multiple of the default quantity defined on the item master data) and partial quantity (Item pick). The proposal created for the full pallet have this picklist type. |
| Item pick picklist type | When this is set, the created proposal is split up between full quantity (this is a multiple of the default quantity defined on the item master data) and partial quantity (Item pick). The proposal created for the item pick have this picklist type. |
| Always status picked? | When this is true, the picklist line status after picking will always bePicked, that is, when you pick without a moveable location, the status will not be Packed. Picklists with a type that have this setting, need to go through the Consolidated Packing flow. If any picklist within the same wave has this option, all pickings will follow this setting. |
| Ask weight? | When this is true, the weight of the (master) logistic unit is asked when the logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Weight UoM set on the Display tab of General Settings. |
| Ask length? | When this is true, the length of the (master) logistic unit is asked when the logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Ask width? | When this is true, the width of the (master) logistic unit is asked when the logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Ask height? | When this is true, the height of the (master) logistic unit is asked when the logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Use for production? | When this is true, the picklist can be used for picklists of type Production. When this is false, the picklist type can be used for shipping and warehouse transfer. |
| Use for Picking? | When this is true, the pick list can be used in the Picking flow. At least 1 of the picklists in the flow needs to have a picklist type with this flag enabled. |
| Use for Ad Hoc Picking? | When this is true, the picklist can be used in the Ad Hoc Picking flow. |
| Use for Zone Picking? | When this is true, the picklist can be used in the Zone Picking flow. At least 1 of the picklists in the flow needs to have a picklist type with this flag enabled. |
| Use for multi picking? | When this is true, the picklist can be used in the multi picking flow. |
| Number of pallets | This defines the number of pallets that can be added to a picklist proposal. When the value is higher than 0, the proposals are split during creation. The splitting is done based on the setting on the item master data for the default quantity on a logistic unit. (OITM.U_PMX_DQLU) The system calculates a fill rate of the proposal line, based on this setting. The fill rate of the proposal lines can go up to the defined number of pallets. In case the default quantity on a logistic unit on the item master data is not set (=0), the fill rate of that proposal line is 0. |
| Ask weight Sub SSCC? | When this is true, the weight of the logistic unit is asked when the sub logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Weight UoM set on the Display tab of General Settings. |
| Ask height Sub SSCC? | When this is true, the height of the logistic unit is asked when the sub logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Ask width Sub SSCC? | When this is true, the width of the logistic unit is asked when the sub logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Ask length Sub SSCC? | When this is true, the length of the logistic unit is asked when the sub logistic unit is finished. The data is stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the Display tab of General Settings. |
| Use for Cash Register Packing? | When this is true, the picklist can be used in the Cash Register Packing flow. |
| Print after item picked | If print event 204 - Picking: after item is picked is set on the Print Events tab of the Organizational Structure, the print event applies to those picklist types where setting Print after item picked is set to true. |
| Num of PL per Wave | Number of picklist per wave: In this column you can add the maximum number of picklists of the given type that has to be grouped into a wave. For more information click here. |
2.3.30. Produmex quality types (PMX_QUTY)
This is the configuration of quality types that can be asked during certain processes. The recorded values are stored in the table PMX_QUVA.
Supported flows:
- Reception
- Bulk reception
- Production
- Production receipt
- Disassembly
Configuration:
Code
The code.
Name
The name.
Convertor
The data is stored in the database as text. The system needs to know what type to convert it to.
This can be set with the convertor.
Possible values:
- Int
- String
- Date
- Double
- List
Document type
The document object type for this quality type. This is the ObjType from SAP.
For the moment only Purchase delivery (=20) and production order (202) are supported.
Remarks
Additional remarks. This is just informational.
Sequence
The sequence the quality type should be shown when entering the data. This is used to sort the quality types. This can be any numeric value.
Moment of capture
The moment of capture: When does this quality type need to be asked?
Possible values:
- Start
- End
The key for translation
The key that will be used for the translation of the title. When this is not set, the system will use MSG_TITLE_QUALITY_TYPE.<Code of the quality type>.
In case there is only 1 language in the company, a title can be entered here directly.
When custom quality types are added, a translation should be added to the system. This translation is used on a device when entering the quality values.
The translation node for TEMP_TRUCK looks like:
<PmxLocalizationKey>
<Canceled>False</Canceled>
<LocalizationKey>MSG_TITLE_QUALITY_TYPE.TEMP_TRUCK</LocalizationKey>
<ApplicationTypeCode>SLIM_SCR</ApplicationTypeCode>
<LocalizationProperties>
<PmxLocalizationProperty>
<Canceled>False</Canceled>
<LocalizationProperty />
<ExtensionCode>CONVSTR</ExtensionCode>
<LocalizationValues>
<PmxLocalizationValue>
<Canceled>False</Canceled>
<LocalizationValue>Enter the temperature of the truck</LocalizationValue>
<LanguageCode>3</LanguageCode>
</PmxLocalizationValue>
<PmxLocalizationValue>
<Canceled>False</Canceled>
<LocalizationValue>Vul de temperatuur in van de vrachtwagen</LocalizationValue>
<LanguageCode>16</LanguageCode>
</PmxLocalizationValue>
</LocalizationValues>
</PmxLocalizationProperty>
</LocalizationProperties>
</PmxLocalizationKey>
The LocalizationKey starts with ‘MSG_TITLE_QUALITY_TYPE.’
Add the code of the attribute type at the end.
When making a complete valid translation file to import, make sure the root tags are also added:
<?xml version="1.0" encoding="utf-8"?> <TestRoot> </TestRoot>
AI
The GS1 application identifier (AI) linked to this batch attribute.
On the flows batch attributes can be entered, based on the batch attributes linked to an item. When a GS1 barcode has been scanned, and a batch attribute needs to be entered with an AI, the system will check if this AI is available in the scanned barcode. If so, this value will be used and the user will not have to manually enter a value for this batch attribute.
2.3.31. Produmex quality valid values (PMX_QUVV)
A list of possible values a batch attributes type can have.
Sequence
The sequence of the valid value in the list. This is used to sort the values to select from.
Quality type
The quality type. This is a link to the table PMX_QUTY
Value
The possible value for the quality type
2.3.32. Produmex user item groups (PMX_UITB)
Here it can be defined what item groups can be visible for a certain user.
This is used on the RF terminals and Produmex screens in the administrative module (SAP).
If the user is not present in the table, he can view data for all item groups.
User code
The code of the user.
Item group
The item group a user is allowed to view.
2.3.33. Produmex user item pick types (PMX_UIPT)
This table is to configure the item pick types a user can pick. If the user is not present in the list, he is allowed to pick all items. If the user is present in the list, he can only pick items with item pick types defined in the table.
This is only used in the Zone Picking Flow.
User code
The code of the user.
Item pick type
The item pick type. The item pick type can be selected from a list. The list comes from the ‘Produmex Item pick types’ UDT.
Item pick type property
The property on the item master data the current line refers to.
Possible values:
- ItemPickType1: The item pick type on item master data.
- ItemPickType2: The item pick type 2 on item master data.
2.3.34. Produmex user picklist types (PMX_UPLT)
This table is to configure the pick list types a user can pick. If the user is not present in the list, he is allowed to pick all pick lists. If the user is present in the list, he can only pick from pick lists with pick list types defined in the table.
User code
The code of the user.
Pick list type
The pick list type. The pick list type can be selected from a list. The list comes from the ‘Produmex pick list types’ UDT.
2.3.35. Produmex user warehouses (PMX_UWHS)
With the Produmex user warehouses UDT you can define the warehouses that can be visible for a certain user. It is used on the RF terminals and Produmex screens in the administrative module of SAP Business One.
If the user is not present in the table, the user can view data for all warehouses.
User code
It can be 25 characters long.
SBO Warehouse
The SBO warehouse that the user is allowed to view.
2.3.36. Produmex variable GTIN configuration (PMX_VGTC)
This table holds a list of configurations of variable GTIN barcodes. The user can store a prefix, define the variable part of the barcode, and what the purpose is of the quantity retrieved from the barcode.
Prefix
The prefix of a barcode that needs to be regarded as a variable GTIN.
This does not need to be the full fixed part of the barcode.
Start index variable part
The barcode has variable part. This field stores the index where the variable part of the barcode starts. This index is zero-based. Supported values: 8, 9, 10.
Length variable part
The barcode has variable part. This field stores the length of the variable part. The sum of the fixed and variable part should be 13 in order to create a GTIN-14 barcode.
# Decimals
The number of decimals of the variable value.
Value purpose (AI)
This defines on what Application Identifier the value needs to be stored, after the value has been captured. Note: Not all listed AI is supported.
2.3.37. Put away zone (PMX_PAZO)
This table holds a list of put away zones. It is used in the functionality for Location Suggestions.
2.3.38. Scale definition (PMX_SCLD)
Configuration of scales that can be used in Produmex RF terminals.
Linked object type
Data needed by the system for the current weighing object. Do NOT adjust values in this column.
Linked doc entry
Data needed by the system for the current weighing object. Do NOT adjust values in this column.
Linked line number
Data needed by the system for the current weighing object. Do NOT adjust values in this column.
Scale setting
Settings for the scale. What needs to be entered here is depending on the scale.
Scale provider type
Provider type for the scale. What needs to be entered here is depending on the scale.
Scale setting
Settings for the scale.
Instance ID
The instance ID
Max. Weight
The maximum weight the scale can handle.
Nr. of decimals
The number of decimals the weight is captured in.
2.3.39. Scale weight result (PMX_SCWR)
Code
The code of the scale. Add the Organizational Structure scale code here.
Name
The name of the scale.
Weigh
The measured weigh. This field will be filled by the ScaleComm Service if the ‘Skip Polling’ option is set to ‘False’ in the configuration file of the ScaleComm Service.
Uom
The Uom of the scale. This field is for information only.
2.3.40. Sequence configuration (PMX_SECO)
This table holds the configuration of sequence numbers.
It is used when Produmex creates a document.
It sets the sequence on a document for the Brazilian localization.
(Like ODLN.SeqCode)
So when a document is created by Produmex, the sequence code for the type of document, and branch is retrieved from this configuration table.
When no configuration is found, no sequence code is set.
Document type
The type of the document.
Like '17' = Sales order, '15' = Sales delivery, …
Branch ID
The branch ID.
Sequence code
The sequence code. This is a numeric value.
2.3.41. Seveso classes (PMX_SEVE)
It defines a seveso class for an item to hold the maximum quantity allowed for the total inventory.
The system checks the total inventory and gives a warning if it exceeds the defined maximum quantity.
Example:
- Maximum quantity = 10
- Stock in warehouse 1 = 251
- Stock in warehouse 2 = 0
2.3.42. Shelf life per country and business partner (PMX_CSSL)
A list of default shelf lives per business partner and country.
These shelf lives are taken into account for items where no shelf life per business partner and country is defined on the item master data. They have however precedence over the general shelf lives defined on the item master data.
You can enter a shelf life for either just a customer, or just a country, or a combination of both a customer and a country.
Country code
The country code (from table OCRY).
Card Code
The card code of the business partner.
Shelf life
The shelf life in days.
2.3.43. Shipping quality option (PMX_SQOP)
In the quality status, it is possible to set the status to “Can Be shipped under quarantine” but still allow shipping. On the sales document line, there is a column (Shipping quality option) to set the allowed quality statuses.
The options for shipping qualities are the following:
- CAN_USE_SUQ: All quality statuses that ‘Can be shipped’ and ‘Can be shipped under quarantine’ are allowed.
- MUST_USE_SUQ: Only quality statuses that ‘Can be shipped under quarantine’ or ‘Can be shipped’ are allowed.
- RELEASED or no selection: Only quality statuses that ‘Can be shipped’ are allowed.
It is allowed to delete an option if it is not needed, but changes to the code are not allowed.
This is used on an SAP document line UDF (Shipping quality option) in combination with the Pick List proposal creation.
Useful Information
Shipping quarantined items can be affected by the following settings:
- Quality Status tab on the Organization Structure:
- Learn more about the Organization tabs:Promumex WMS Fields and Settings
- Learn more about the defined tables:2.3. User defined tables
- Inventory Report: Ensure the Quality Status column is correctly set.
- Sales Order: Adjust the Shipping Quality Option column as needed.
Important Notes!
- Pick locations cannot be used for items labeled as “Quarantined” or “Shipping Under Quarantined (SUQ).”
- Ensure that items with different quality statuses (e.g., Quarantined and SUQ) are not stored in the same location. Mixing items with different quality statuses can cause issues during the picking process.
If items must be shipped even if it's quarantined make sure to set the following settings.
Procedure for Shipping Quarantined Items
- Inventory Report: In the Inventory Report window of the Desktop Client, you have the capability to modify the quality status. Similarly, the Mobile Client also provides the functionality to change the quality status: Change Quality Status Flow.
- Sales Order: On the sales order line, set the Shipping Quality Option to “Shipping under Quarantine”. If you set the “Released or SUQ” option on the Sales Order line during the picking, you can pick from both Released and SUQ stock.
- Organization Structure (OSE): Under the Quality Status tab, enable the “Can be shipped Under Quarantine” setting for the SUQ. This allows SUQ items to be shipped.
Picking and Shipping Flow for SUQ items
- Create a Picklist from the SUQ stock.
- Open the Mobile Client and navigate to Sales > Picking, then select the previously created Picklist.
- On the Identify Pick Location screen, click on Other Task and then Alternate Stock.
- During the standard picking flow, if your stock has an SUQ status, the Identify Pick Location will only work if you select Alternate Stock.
- After selecting the needed alternate stock, the Identify Pick Location screen can be filled.
- On the next screen, Scan a Product and select the product.
- Select a Batch Number. Here, you can see the stock’s quality status: SUQ.
- Finish the picking flow by entering the quantity. Items are successfully picked.
- Continue with the Shipping on the Mobile Client: Sales> Shipping > Select the Picklist and scan the SSCC. The shipping in finished!
Ad Hoc Picking Flow cannot work with “Shipping Under Quarantine” items!
Note:In Ad Hoc picking, it only allows products with the “Can be shipped “ setting on the quality status, even if the shipping quality option has “Can be shipped under quarantine”. The “Can be shipped” status is the strongest point of view and cannot be overwritten by the “Cannot be shipped under quarantine” status.
2.3.44. User authorization definitions table (PMX_UAUT)
Definition of possible authorizations that can be set. This is system information. Do not adjust/delete the code.
Possible values:
- PRD_FLOW_ON_HOLD: The ‘on hold’ button on the Production flow
- PRD_FLOW_STOP_BTN: The ‘stop’ button on the Production flow
- PROPOSAL_CLOSE_BUTTON: The close button to close pick list proposals (Open documents report, pick list proposal form, …)
- PICK_LIST_CLOSE_BUTTON: The close button to close pick lists (Open documents report, pick list proposal form, …)
- QC_SUPERVISOR: The ‘Change Qualification’ button on the Quality Test Results form.
- WO_OVERRULE_SCALE_SWITCH: The ‘Switch scale’ button in the weighing flows.
- WO_OVERRULE_WEIGHT: For weighing outside of the tolerance range in the weighing flows.
2.3.45. User group for PMX (PMX_USGR)
Definition of Produmex user groups. The user group can be linked to a user.
There are already 2 predefined user groups.
- 01_ADMIN: Administration
- 02_SHPFLR: Shopfloor