topic Surprise Error in Enhancements & Feedback

Surprise Error

aranciglio — Thu, 22 Feb 2024 16:08:47 GMT

Hello!

I'm receiving an error after 2 months of no issues. I've checked my hierarchy info and compared it to other items that are not producing an error, and they are identically set up. I must be missing something. Anyone have time to check this GTIN and error?

GTIN : 00860008758507
quantityOfLayersPerPallet (NON-Pallet GTIN) - One of pairs Quantity Of Trade Items Per Pallet Layer (NON-Pallet GTIN)/Quantity Of Layers Per Pallet (NON-Pallet GTIN) at the Highest Below Pallet level OR Items Per Pallet Layer/Layers Per Pallet at the Pallet level is required.

Any help is appreciated!

Re: Surprise Error

Montavio — Thu, 22 Feb 2024 18:28:58 GMT

Hi @aranciglio, thanks for reaching out! We would be happy to assist. Could you clarify which Case linked to item 00860008758507 was getting the error above? Also, was this error seen when attempting to publish or when validating?

Re: Surprise Error

AngieR — Thu, 22 Feb 2024 18:58:33 GMT

This item is linked to the case 00860008758538, as well as the display 00860010237113

The error is coming back from a scorecard from PFG. Case and Display validate with no issues. There are no errors or warnings on the dashboard either. When validating the each, there is an error for an ordering unit, but I tend to ignore those if the parent validates.

Re: Surprise Error

Montavio — Thu, 22 Feb 2024 21:43:54 GMT

Hi @AngieR, thank you for following up. When looking further into this I see that you have some unneeded fields populated along with one field populated incorrectly. Please ensure only the highlighted fields below are populated when filling in the 'Hierarchy Information' (on the Case and Display item only):

Please also be made aware that, specifically the "Count of This Specific Item in a Non-GTIN Logistic Unit/NonGTIN Pallet Quantity", is populated with the value of the Non-GTIN Ti multiplied by the value of Non-GTIN Hi.

Once these changes are made you should only need to save them, which should push them to PFG to be reviewed.

If you have any further questions, please feel free to contact us.

Thanks!