Catch weight item?
Indicates if the item is a catch weight item.

GS1 AI for uom
The GS1 application identifier to capture the quantity for pieces. Possible values:

• 37 (Count)
• 31 (Net weight Kilo)
• 32 (Net weight Pound)

GS1 AI for uom2
The GS1 application identifier to capture the quantity for the weight. Possible values:

• 37 (Count)
• 31 (Net weight Kilo)
• 32 (Net weight Pound)

1 uom = xxx uom 2
The weight of 1 piece.

Weight tolerance (%)
The weight tolerance in percentage. Here it can be defined what the allowed tolerance for the weight is. If the tolerance >= 100, no tolerance check will be done. This check will be used for all documents except: goods issue and goods receipts. Calculation:
( Pieces * Default weight of 1 piece ) -
( Pieces * Default weight of 1 piece ) * Weight tolerance/100
< Allowed weight <
( Pieces * Default weight of 1 piece ) +
( Pieces * Default weight of 1 piece ) * Weight tolerance/100

Uom to use for purchase
The uom that should be asked when receiving items.
Possible values:

• Pieces (UOM1): The weight is calculated based on the weight of 1 piece.
  
• Weight (UOM2): The number of pieces are calculated based on the weight of 1 piece.
  
• Pieces and weight
  

Uom to use for inventory
The uom that should be asked when moving items.
Possible values:

• Pieces (UOM1): The weight is calculated based on the weight of 1 piece.
  
• Weight (UOM2): The number of pieces are calculated based on the weight of 1 piece.
  
• Pieces and weight
  

Uom to use for sales The uom that should be asked when delivering items.
Possible values:

• Pieces (UOM1): The weight is calculated based on the weight of 1 piece.
  
• Weight (UOM2): The number of pieces are calculated based on the weight of 1 piece.
  
• Pieces and weight
  

Price calculation for sales
The calculation of the price for creating a sales delivery.
Possible values:

• Price by piece: This option is the default option. In this case no price calculation is done because the price from SAP is already by piece
  
• Price by weight: The calculation of the price is done by weight.
  

Price by weight
When a sales delivery/reserve invoice is generated, the price will need to be set when:

• The item is a catch weight item
  
• The option for price calculation is set to 'Price by weight'
  
• The base document is NOT an invoice
  
• Delivery is made through Produmex functionality
  

The unit price before discount will be adjusted. The default unit price is based on the default weight of a catch weight item. So a recalculation based on the actual delivered weight needs to be done.

The calculation formula is: Unit price before discount = (Unit price before discount sales order / Default weight by piece) * Actual weight) / Quantity

Database columns: DLN1.PriceBefDi = ( RDR1.PriceBefDi / OITM.U_PMX_DQUM) * DLN1.U_PMX_QTY2 ) + DLN1.Quantity

Example:

ItemA
* Inventory uom = Case
* Weight uom = Pounds
* 1 Case = 24 pounds (U_PMX_DQUM = 24)
* Price per case = 48$ (= 2$ / pound)

Sales order
* 20 cases
* Unit price = 48$
* Total price = 960$

When we deliver the 20 cases the actual weight = 500 pound (Nominal weight was 480 pound)
The calculation is as follows:

(Unit price sales order / Default weight by piece) * Actual weight) / Quantity = Unit price

(48$/24 pounds) * 500 pounds) / 20 cases = 50$

Total price of the delivery line will be 1000$
This means if you deliver 500 pounds, this is 2$ by pound.

Scan weight for each case
When this is enabled, when scanning/entering the weight in the device, the system will not automatically calculate the number of pieces that would be associated with the weight, but it will use the # pieces in a case.
So on the first entry of the weight, the user can either enter the total weight for all pieces.
Flow:

• Check if scanned weight is within tolerance of the # pieces in case
• Yes: Use the pieces and weight, and ask for next weight
• No:
  • Check if the scanned weight is within tolerance of the needed number of pieces
  • Yes: Use the needed number of pieces, and total weight
  • No: Error is shown that weight is not within tolerance

# pieces in case
This is used in combination with the setting 'Scan weight for each case'. It stored the number of pieces in a case.

Record weight details during picking
When this is enabled, the entered weight during picking on a device will be stored in a separate table: PMX_WDET.
It stores the pick list doc entry, item and batch details.
This allows to retrieve the detailed weight entry for an item on a pick list.