Pallet and Cube Calculation by Pieces

One of the elements that keeps consulting work interesting is uncovering new or hidden features within the application your working with. At one of my recent clients, I discovered a piece of functionality that I have never played with before and thought it was useful enough that I would like to learn more about it and possibly recommend it to future clients.

Within JDA Transport (I’m working with v7.4.0) there is a configuration setting called “Perform Order Pallet and Cube Calculation by Pieces.” The setting is located in the Configuration UV >> General Tab, and is near the bottom of the page. This setting also exists in versions as early as (at least) 7.0 and possibly earlier.

When selected, this setting forces an extra lookup during the Order Interface process (iordload) to calculate Pallet and Cube quantities on the order, given a ‘Pieces’ value is specified on the order’s Line Item (P) record. The iordload process roughly goes through the following steps:

    – Take the Package Type of the Line Item from the P record
    – Lookup the Pieces Per Unit and Volume Per Unit (Packaging table)
    – Divide the Pieces (Order Line Item) by Pieces Per Unit (Item Packaging) >> This is your Pallet quantity
    – Multiply the Pallet Quantity by the Volume Per Unit (Item Packaging) >> This is your Cube quantity
    – Aggregate calculated Pallet and Cube quantities by Commodity
    – Write to intfc_ord table

So, the formula is pretty basic once you understand how the fields are utilized. The help instructions don’t do a great job explaining, so a test or two to determine how it’s actually working is necessary.

It is important to note that if the Package Type of the Order-Item (P record) does not exist as an entry in the Packaging table, then the application will not calculate Pallet and Cube values for you (they are left at zero). It is also important to note that the formula always rounds up, never down. For example, a volume of 18.3333 would equate to 19.

Implementation: this feature can be very useful given circumstances where ERP or legacy OMS does not provide accurate (or any) Pallet or Volume calculations. In certain circumstances, weight alone is not entire useful as a load-building optimization constraint, and needs to be supplemented with pallet positions or volumetric information. Where none exist, or where the data is imperfect – this can be useful to help further refine the solution.

Drawbacks of using this feature include ongoing maintenance, possibly outgrowing the usefulness of the ‘esimtation’, and confusion around it’s formula. To really make this work, the Item Master interface should be coded to always include a Packaging (P) record and include any possible Package Type. Synchronizing this with the Package Type on the Order must also be considered, and is often difficult to do natively (i.e. as standard ERP or OMS functionality).

Shots:

Config Settings
Config Setting

Item-Packaging Tab Configuration
Config Setting

Order-Line Item Tab Showing Calculated Pallet and Cube
Config Setting

About Brad Forester