NDR-SC, Using the phase a picture is worth a thousand words ,perhaps a few examples will do likewise to help clear the air regarding the UDEF UIDs. The following are example UDEF name constructs plus their associated UDEF IDs. <ProductScheduledDeliveryDate UID= 9_3.29.6 > <ProductActualDeliveryDate UID= 9_2.29.6 > <ProductLastPossibleDeliveryDate UID= 9_2.1.29.6 > <ProductFirstPossibleDeliveryDate UID= 9_1.1.29.6 > <ReplacementProductScheduledDeliveryDate UID= m.9_3.29.6 > <NewProductScheduledDeliveryDate UID= h.9_3.29.6 > <NewProductWholesalePriceAmount UID= h.9_5.2.1 > <NewProductRetailPriceAmount UID= h.9_4.2.1 > <ReplacementProductRetailPriceAmount UID= m.9_4.2.1 > <InvoiceDocumentTotalTaxAmount UID= bd.2_1.3.1 > <InvoiceDocumentTotalDueAmount UID= bd.2_2.12.1 > <InvoiceDocumentMinimumDueAmount UID= bd.2_1.12.1 > <ContractDocumentRevisionIdentifier UID= e.2_9.8 > <PurchaseOrderDocumentRevisionIdentifier UID= d.t.2_9.8 > <WorkOrderDocumentRevisionIdentifier UID= a.t.2_9.8 > <RealEstateAssetListPriceAmount UID= c.1_3.2.1 > <EquipmentAssetCostAmount UID= d.1_1.1 > <CashAssetBalanceAmount UID= a.1_6.1 > <EnterpriseName UID= 3_10 > <SupplierEnterpriseName UID= y.3_10 > <PaymentRemitterEnterpriseName UID= a.w.3_10 > <PaymentReceiverEnterpriseName UID= a.x.3_10 > <CarrierEnterpriseName UID= ae.3_10 > <ManufacturerEnterpriseName UID=ah.3_10 > <SupplierEnterprisePurchaserAssignedIdentifier UID= y.3_2.35.8 > <ProductVendorAssignedIdentifier UID= 9_1.35.8 > <DestinationPlaceCountryName UID= i.7_1.10 > <AddressPlaceCountryName UID= k.7_1.10 > <HomeAddressPlaceCountryName UID= a.k.7_1.10 > <DeliveryAddressPlaceCountryName UID=d.k.7_1.10 > <DeliveryAddressPlaceCityName UID= d.k.7_10.10 > I hope these illustrations provide insight to the possibilities that a structured UID might offer. Ronald L. Schuldt Senior Staff Systems Architect Lockheed Martin Enterprise Information Systems 11757 W. Ken Caryl Ave. #F521 MP DC5694 Littleton, CO 80127 303-977-1414
ron.l.schuldt@lmco.com