TAG Column Has Different Widths In Different Tables Causing Failures. (Doc ID 1334049.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

When attempting to plan an Order Release that has TAG1 populated on the Ship Unit Line, the following error occurs.

ERROR
-----------------------

insert into s_ship_unit_line (s_ship_unit_gid,s_ship_unit_line_no,weight,volume,tracking_tag1,tracking_tag2,tracking_tag3,tracking_tag4,or_line_gid,order_release_gid,order_base_gid,packaging_unit_gid,packaging_unit_count,item_package_count,declared_value,packaged_item_gid,hazmat_item_gid,received_weight,received_volume,received_item_package_count,ship_unit_gid,ship_unit_line_no,weight_per,volume_per,count_per_ship_unit,received_packaging_unit_count,received_count_per_ship_unit,t_order_release_gid,t_or_line_gid,t_ship_unit_gid,t_ship_unit_line_no,user_defined_commodity_gid,domain_name,volume_per_uom_code,weight_per_uom_code,received_volume_uom,received_weight_uom,declared_value_currency_gid,volume_uom_code,weight_uom_code,volume_per_base,weight_per_base,received_volume_base,received_weight_base,declared_value_base,volume_base,weight_base) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) at <COMMA SEPARATED VALUES>
java.sql.BatchUpdateException: ORA-12899: value too large for column "GLOGOWNER"."S_SHIP_UNIT_LINE"."TRACKING_TAG1" (actual: 34, maximum: 30)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

01. Create an order release with TAG1 populated on the Ship Unit Line.
02. Select the order > Actions > Direct plan > See the error

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.