IBM Sterling
This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Bharat,
We have multiple business use cases for this below are some examples from PROD:
Recently We got item Integration for an item with Quantity UOM as IN but item integration failed because IN UOM does not exist at Quantity UOM level and we can not create IN UOM at Quantity UOM level because it already exists at Dimension UOM level
Input XML:
<?xml version='1.0' encoding='UTF-8'?>
<ItemList>
<Item Operation="Manage" ItemID="BE5Y958Z8" OrganizationCode="WESCO_GLOBAL" UnitOfMeasure="IN">
<PrimaryInformation MasterCatalogID="WESCO_GLOBAL_MASTER_CATALOG" IsHazmat="N" ItemType="STD" KitCode="" Description="Tape, 2 x 1000 in., Black/Red" ExtendedDescription="" ShortDescription="Tape, 2 x 1000 in., Black/Red" Status="3000" DefaultProductClass="Goods" ManufacturerName="MISC SIM"
Output XML:
<?xml version="1.0" encoding="UTF-8"?>
<Errors>
<Error ErrorCode="YCM0031"
ErrorDescription="Invalid ItemId-UOM-OrganizationCode Combination" ErrorRelatedMoreInfo="">
<Attribute Name="ErrorCode" Value="YCM0031"/>
<Attribute Name="ErrorDescription" Value="Invalid ItemId-UOM-OrganizationCode Combination"/>
<Attribute Name="UnitOfMeasure" Value="IN"/>
<Attribute Name="OrganizationCode" Value="WESCO_GLOBAL"/>
<Attribute Name="ItemID" Value="BE5Y958Z8"/>
<Stack>com.yantra.yfc.util.YFCException
Another Example we got an item integration with UOM MIN but it failed because we don't have MIN at Quantity UOM level and we can not create it at Quantity UOM level because it already exist at Time UOM level
Input XML:
<?xml version='1.0' encoding='UTF-8'?>
<ItemList>
<Item Operation="Manage" ItemID="EF52Z8ZZ6" OrganizationCode="WESCO_GLOBAL" UnitOfMeasure="MIN">
<PrimaryInformation MasterCatalogID="WESCO_GLOBAL_MASTER_CATALOG" IsHazmat="N" ItemType="LBR" KitCode="" Description="ASSEMBLE CHARGE" ExtendedDescription="" ShortDescription="ASSEMBLE CHARGE" Status="3000" DefaultProductClass="Goods" ManufacturerName="APPROVED MANUFACTURERS" ManufacturerItem="LBR-ASSEMBLE" IsShippingAllowed="Y" AssumeInfiniteInventory="Y" UnitHeight="" UnitHeightUOM=
Output XML:
<?xml version="1.0" encoding="UTF-8"?>
<Errors>
<Error ErrorCode="YCM0031"
ErrorDescription="Invalid ItemId-UOM-OrganizationCode Combination" ErrorRelatedMoreInfo="">
<Attribute Name="ErrorCode" Value="YCM0031"/>
<Attribute Name="ErrorDescription" Value="Invalid ItemId-UOM-OrganizationCode Combination"/>
<Attribute Name="UnitOfMeasure" Value="MIN"/>
<Attribute Name="OrganizationCode" Value="WESCO_GLOBAL"/>
<Attribute Name="ItemID" Value="EF52Z8ZZ6"/>
<Stack>com.yantra.yfc.util.YFCException
We have same example for HR and LB UOM as well
As of now as a work around we are moving these UOM to Quantity UOM level and creating new UOM for Dimension and Weight because for our business use case Quantity UOM takes precedence over other level UOM
Hi Akash, Thanks for sharing your query with IBM.
Looking at your query, could you please elaborate more on the business scenario where same UOM is expected across different UOM types? I don't see it as a common industry use case. In a product, we also allow UOM conversions within the UOM type. It will not be possible to do these conversions if UOM types talks about completely different dimension of the products.
You have a choice to use different UOMs per UOM types.
regards,
Bharat K