Publication XML File Format Whitepaper Fusion Release 9 PDF

Publication Framework
An Oracle White Paper

October 2015
Oracle Fusion Product Hub Publication

XML File Format Details, Release 9
Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or functionality described for
Oracles products remains at the sole discretion of Oracle.
Executive Overview ........................................................................... 1

Introduction ....................................................................................... 1
Terms and Definitions........................................................................ 2
Business Challenges ......................................................................... 2
Solution Overview ............................................................................. 2
Implicit Publication Explained ........................................................ 3
XML Data Output File Format ............................................................ 4
Item Entities................................................................................... 5
Ordering of Item Entities ......................................................................... 7
Attributes Selection: .............................................................................. 10
Attachment: URL Selection .................................................................. 20
Associations: Supplier Site Organizations Selection ............................ 20
Item Category Assignments Selection ................................................. 22
Item Relationships: GTIN Selection ..................................................... 23
Item Relationships: Trading Partner Items Selection ........................... 24
Item Relationships: Related Items Selection ........................................ 29
Item Relationships: Cross-references Selection .................................. 30
Structures: All Selection ....................................................................... 31
Structures: Primary Selection ............................................................... 34
All Pack Items Selection ....................................................................... 36
Pack Hierarchy Selection ..................................................................... 37
All Pack Items and Pack Hierarchy Selection ...................................... 40
Item Class Entity.......................................................................... 40

Catalog Entity .............................................................................. 45
Controlling the Payload Output File Size ..................................... 49
Summary ......................................................................................... 50
XSDs for Publication........................................................................ 51

Item XSD Selection ..................................................................... 51
Item Attributes Selection XSDs ............................................................ 52
Attachment: URL Selection XSDs ........................................................ 56
Association: Supplier Site Organizations Selection XSDs ................... 56
Item Category Assignments Selection XSDs- ...................................... 57
Pack Hierarchy Selection XSDs ........................................................... 57
Item Relationships: GTIN Selection XSDs ........................................... 58
Item Relationships: Trading Partner Items Selection XSDs ................. 59
Item Relationships: Related Items Selection XSDs ............................. 60
Item Relationships: Cross References Selection XSDs ....................... 60
Structures: All Selection XSDs ............................................................. 61
Structures: Primary Selection XSDs ..................................................... 62
All Pack Items Selection XSDs ............................................................. 62
Item Class XSD ........................................................................... 63

Catalog XSD................................................................................ 63
Frequently Asked Questions............................................................ 64
Executive Overview
In todays global environment, companies offer large sets of products and services to their
customers. Moreover, mergers and acquisitions might result in data migration across systems.
The complete and accurate product information residing in Fusion Product Hub needs to be
consumed by various downstream systems for the specific business requirements. Hence, it
has become important for Fusion Product Hub to support the publication of product information
to external systems.
Introduction
Publication Framework offers a set of features that enable you to publish items and their data
elements, such as product structures, packaging hierarchies, catalogs/categories, item
relationships, and item associations; item classes and their metadata and catalogs and their
categories. In order to achieve successful publication to external systems, publication criteria
need to be defined for the spoke system in Product Hub. This white paper provides information
on the XML file format that is published.
.
Terms and Definitions

TABLE 1. TERMS AND DEFINITIONS
TERM
DEFINITION
PIM
Product Information Management
Organization
An organizing unit in the internal or external structure of your enterprise.

Organization structures provide the framework for performing legal reporting,
financial control, and management reporting. An organization can also represent
a physical structure, such as a warehouse.
EGI
Short code for Oracle Fusion Product Hub
Item
Item represents a product in a given organization
Item Structure
Item structure represents all the components that are part of the item's bill of
material.
Pack
Pack, also known as Trade Item Unit Descriptor (TIUD) is used to describe the
GTIN hierarchy level
Item Relationship
Relationship between two Items or Relationship between an Item and GTIN,

Cross Reference, Trading Partner Item or Source System Item
GTIN
Global Trade Item Number
UCM
Unified Content Manager
API
Application Programming Interface
FSM
Functional Set up Manager
Business Challenges
Company ABC Corp has implemented Fusion Product Hub to manage all the product
information. It recently partnered with company MedComp, a company that uses ABC Corps
products for its business transactions. Hence the business requirement is to publish more
than 1000 items and their entities, more than 50 item class metadata and more than 100
catalogs and their category hierarchies from ABC Corp to MedComp.
Solution Overview
Let us discuss how the above business challenge can be achieved using Fusion Product Hub. ABC
Corp can publish items, item classes and catalogs from Product Hub to external system by scheduling
a periodic publication process.
Note: Publication cannot be invoked from individual object pages. This feature is not supported.
Implicit Publication Explained

Implicit publication allows you to set up a periodic schedule for each spoke system to publish the
objects automatically. In order to set up implicit publication of objects from Product Hub to external
systems, the following is required:
1.
Spoke System Definition: Define the publication options for a spoke system
2.
Publication Scheduled Process: Define the schedule and parameters for the scheduled
process job
3.
Profile Options: Define profile options
4.
Accessing the payload: Access the payload generated by the publication scheduled process
5.
Customization: Customize SOA composite to publish to the external spoke system
Below is the typical flow of publishing items, item classes and catalogs to external spoke system.
Figure1: Publication Flow
The data that gets published is determined by
Publication criteria/options selected for each object for a spoke system. These are used to
identify the objects.
For first time publication to a spoke system, you must specify the Criteria Date when for
the scheduled process. For subsequent publications, the last publication date is used. If a
criteria date is populated, then the criteria date is used. For example, for the very first
publication, you entered D1 as the criteria date. Schedule to publish is set for every 5 days,
hence D5, D10 etc. The scheduled publication process on D5 will filter all updated objects
from D1 up to D5 that meets the publication criteria and publish that data. Now for
subsequent publications, data that was updated from D5 (last publication date) that meets the
publication criteria will be published on D10. Before the next publication on D15, if you
entered D7 as the Criteria Date, then all updated records from D7 up to D15 will be
published. In this case, D7 criteria date over writes D10, which is the last publication date.
Records that are changed/updated from the last publish date. Examples
o
For Item1 if attribute Color is changed from Red to Blue since the last published
date, the entire item including attribute Color and all other attributes that did not
change will be published.
For Item2 if only Related Item XYZ is updated since the last published date, the
basic item attributes and the entire Related Item XYZ are published.
For Item Class1, if attribute Material changed from Lead to Aluminum since the last
published date, the entire Item Class1 will be published and not just the attribute
Material.
For Catalog1, if Category1 is updated from last publication date,
Once records and data are identified, the payload is generated. You can access this payload (xml file)
and transform it in the format understood by the external spoke system. Details are explained in the
sections below.
XML Data Output File Format

The publication framework will create a ZIP file as the output based on the settings for the spoke
systems and the ESS Job create.
The example below in Figure 2 illustrates the content of a ZIP file that is generated when Item and
Catalogs are selected in the Manage Spoke Systems Publication Options tab.
Figure 1 XML Data Output File
The ZIP file will contain one or more xml files corresponding to the objects selected in the Manage
Spoke System user interface. The xml files naming convention will be: ITEMS_N.xml, and/or
CATALOGS_N.xml and/or ITEMCLASSES_N.xml, where the N is used to designate the number
of the file for a specific object. For example, if Items, Item Classes and Catalogs are checked for the
Publish attribute, the resulting ZIP file would contain:
PIM_Publication_SC2_124133.zip
File: ITEM_0.xml
File:ITEMCLASS_0.xml
File: CATALOG_0.xml
Item Entities
The first region, Item Entities controls which item entities will be in the Items_n.xml file. The User
will select Items check box in the Publish attribute, the Item Entities regions will expand. Two options
are available for item entities:
Publish Only Changed Entities: This option will restrict the XML output to only item entities
that have changed.
Revision Selection: This option will allow the selection of the revision for the entity. The
default selection is the Current Revision. The XML output will show the current revision
when this value is selected. If the user selects Current and future revision, the user can enter
a value for Days in the Future. The XML output will show the current and all future revisions
based on the value for Days in the Future.
The User will select the item entities that will published using the arrow icons to move the item entity
to the Selected column in the shuttle. In Figure 2 the item attributes and the item attachments entities
will be published. Table 1 below lists the item entities that can be selected.
Figure 2 Publication Options Tab
Table 1 Item Entities
Item Entity
Attributes
Associations: Supplier Site Organizations
Item Category Assignments
Pack Hierarchy
Item Relationships: GTIN
Item Relationships: Trading Partner Items
Item Relationships: Related Items

Item Relationships: Cross References
Structures: All
Structures: Primary
All Pack Items
Attachments: URL
Description
The main attributes and operation attributes for an
item.
The association of an item to a Supplier Site
Organizations.
The assignment of the item to a category within a
catalog.
A multi-level structure that defines the packaging for a
product. Pack Items are arranged using parent child
relationships. For example, the pack hierarchy for item:
AS7200 is defined as a Pallet_01, containing four
cartons, each carton contains for inner packs and each
inner pack contains four boxes.
A relationship between an item and one or more Global
Trade Item Numbers. For example, AS72111, a Envoy
Laptop is represented by GTIN bar code
1061414000415.
The item relationship with a trading partner, who
provides that item, such as item AS12345 is provided
by Zoom Incorporated and has customer item number
AS345. Trading partners include customers,
competitors, Manufacturer, and Supplier
A relationship, defined by a type that is between two
items. For example, The item AS54888 is a substitute
for AS8967, where the type is substitute.
A relationship type and value between an item and any
other identifier such as ISBN, ISAN and so on.
Organizations of components that represents an item
or product. All structure types will be displayed
Organizations of components that represents an item
or product. The structure type: Primary will be
displayed.
An item that represent a component of a pack
hierarchy. All pack items will be displayed.
An electronic document or image that associated to an
item. The URL defines where the attachment is in the
computer system.
The resulting ZIP file that is generated by the Publication System when Items is checked looks like:
File: ITEM_0.xml
<?xml version="1.0" encoding="UTF-8" ?>
<Items>
<ns0:Item xsi:type="ns0:Item" xmlns:xsi-http://www.w3.org/2001/XMLSchemainstance./>
</Items>
. This symbol means that some information has been removed for simplicity. The information
removed contains each of the services that is used to extract the data.
In this example the payload file contains published data for one item that was created on the day the
publication was run.
EGI_PUBLICATION_ITEMS_PER_PAYLOAD Profile Option
In the case of publishing large numbers of items, a profile option

EGI_PUBLICATION_ITEMS_PER_PAYLOAD is provided to control the number of items for
each ITEM_n.XML files for the items published. For example if the publish results contains 1000
items, multiple files for ITEMS will be generated based on the setting for the
EGI_PUBLICATION_ITEMS_PER_PAYLOAD profile option of 100 items. For example the ZIP
file contains:
File: ITEM_0.xml
File: ITEM_1.xml
File: ITEM_2.xml
File: ITEM_3.xml
Each of the files: ITEM_n.xml contains:
<Items>
<ns0:Item xsi:type="ns0:Item" xmlns:xsi-http://www.w3.org/2001/XMLSchemainstance./>
</Items>
Ordering of Item Entities
The order of the item entities in the ITEM_n.xml file is the same for each item record, for example if
we assume that all the item entities are selected and new item was created with content defined for all
of the item entities, then the ITEM_n.xml file will always list the entities in the same order within the
item element tag boundaries. If specific item entities are selected, the ITEM_n.xml file will still
maintain the order, but not list the item entities that are not selected. The order is shown in Figure 3
and 4 is not a complete list of the content of the XML file.
Each of the item entities will be published in a separate set of tags within the
<ns0:Item xsi:type="ns0:Item">tag set. The Item Entities selection will determine the content in the
XML file. For example, if item entities Attributes and Attachments are selected then the file;
ITEM_0.xml would look like:
File: ITEM_n.xml contains:
<Items>
<ns0:Item xsi:type="ns0:Item">
<ns0:ItemAttachment>
</ns0:ItemAttachment>
<ns0:ItemEffCategory>
<ns2:ItemEFFPerformanceGroup>
</ns2:ItemEFFPerformanceGroup>
</ns0:ItemEffCategory>
<ns6:ItemRevisionId>
<ns6:ItemRevisionTranslation>
</ns6:ItemRevisionTranslation>
<ns6:ItemRevisionDFF>
</ns6:ItemRevisionDFF>
</ns6:ItemRevisionId>
<ns0:ItemCategory>
</ns0:ItemCategory>
</ns0:Item xsi:type="ns0:Item">
</Items>
If the Attributes item entity is not selected, the basic attribute set will be displayed for item along with
any other selection as shown below:
<ns0:OrganizationCode>V1</ns0:OrganizationCode>
<ns0:ItemNumber>Test Resistor Item 1303 1</ns0:ItemNumber>
<ns0:ItemDescription>45 Ohms Array 345 Watts Carbon Test
Item</ns0:ItemDescription>
<ns0:ItemStatusValue>Active</ns0:ItemStatusValue>
<ns0:LifecyclePhaseValue>Design</ns0:LifecyclePhaseValue>
<ns0:UserItemTypeValue>Finished Good</ns0:UserItemTypeValue>
</ns0:Item>
When Attributes item entity is selected, a complete set of item attributes is show, please see the
Attribute Selection section below more details. At least one item entity selection must be made for
the Publication Options.
Figure 3 Entity Order of Publication
Figure 4 Entity Order of Publication (Cont)

Attributes Selection:
The Attributes selection in Publication Option tab of the Manage Spoke System user interface will
result in publishing the following item entities for items:
Base Item Attributes: Organization Code, Item Number, Item Description, Item Status,
Lifecycle Phase and User Item Type.
Operational Attributes
Item Extensible Flexfields Attributes:
o Extensible Flexfields Category Item Class
o Extensible Flexfields Context Attribute Group
o Attributes
10
Item Revisions
o Item Revision Translations
o Item Revision Descriptive Flexfields
o Item Revision Extensible Flexfields
Item Descriptive Flexfield Attributes
ItemCategory
Item Attribute XML Tags
Tags
Description
<ns0:Item></ns0:Item>
This tag represents the content for a single

item record.
Item Extensible Attribute Group Category
(Item Class).
Item EFF Attribute Group.
<ns0:j_ItemExtensibleFlexfieldCategoryCode>
</ns0:j_ItemExtensibleFlexfieldCategoryCode>
<ns2:ItemEFFBAG_5FNT_5FSR_5F2PrivateVO>
</ns2:ItemEFFBAG_5FNT_5FSR_5F2PrivateVO>
<ns4:_Character1></ns4:_Character1>
<ns4:uagnetweightUE xsi:nil="true">
</ns4:uagnetweightUE xsi:nil="true">
<ns0:ItemRevision></ns0:ItemRevision>
<ns6:ItemRevisionDFF></ns6:ItemRevisionDFF>
<ns0:ItemRevisionEffCategory>
</ns0:ItemRevisionEffCategory>
<ns2:ItemRevisionEFFBAGTESTPrivateVO>
</ns2:ItemRevisionEFFBAGTESTPrivateVO>
<ns0:ItemCategory></ns0:ItemCategory>
<ns0:ItemDFF></ns0:ItemDFF>
EFF Multi-row Attribute Group Column

value.
EFF Attribute
Item Revision
Item Revision Translation values
Item Revision Descriptive Flexfields
Item Revision Extensible Flexfield
Category
Item Revision Extensible Flexfields
Item Descriptive Flexfields
Item Attribute XML File Format
<ns0:ItemId>100100040149840</ns0:ItemId>
<ns0:OrganizationId>204</ns0:OrganizationId>
<ns0:ItemClass>EFF_NT_SR_MR_NV_ALL_LEVEL_ALL_TYPES_2</ns0:ItemClass>
<ns0:Template xsi:nil="true"/>
<ns0:ItemNumber>CSV_EFF_Item_Import_17991961_1</ns0:ItemNumber>
<ns0:ItemDescription>Uploaded from desktop CSV file, Item with Item Level SR MR
EFFs</ns0:ItemDescription>
<ns0:ApprovalStatusValue>Approved</ns0:ApprovalStatusValue>
<ns0:StyleItemFlag xsi:nil="true"/>
<ns0:StyleItemNumberValue>CSV_EFF_Item_Import_17991961_1</ns0:StyleItemNumberValue>
<ns0:Keyword xsi:nil="true"/>
<ns0:IgnoreDuplicateItemFlag xsi:nil="true"/>
<ns0:PackTypeValue xsi:nil="true"/>
11
<ns0:LongDescription xsi:nil="true"/>
<ns0:FormattedDescription xsi:nil="true"/>
<ns0:PrimaryUOMValue>Each</ns0:PrimaryUOMValue>
<ns0:TrackingUnitofMeasure>Primary</ns0:TrackingUnitofMeasure>
<ns0:UOMPricingValue>Primary</ns0:UOMPricingValue>
<ns0:TransactionConversionValue>Both</ns0:TransactionConversionValue>
<ns0:SecondaryUnitofMeasureValue xsi:nil="true"/>
<ns0:DefaultingControlValue xsi:nil="true"/>
<ns0:PositiveDeviationFactor>0</ns0:PositiveDeviationFactor>
<ns0:NegativeDeviationFactor>0</ns0:NegativeDeviationFactor>
<ns0:CopyItemAndApplyTemplatesFlag xsi:nil="true"/>
<ns0:CopyAssociationsFlag xsi:nil="true"/>
<ns0:CopyAttachmentsFlag xsi:nil="true"/>
<ns0:CopyCategoriesFlag xsi:nil="true"/>
<ns0:CopyFromItemValue xsi:nil="true"/>
<ns0:CopyFromRevisionValue xsi:nil="true"/>
<ns0:CopyFromVersionValue xsi:nil="true"/>
<ns0:CopyOrganizationAssignmentsFlag xsi:nil="true"/>
<ns0:VersionId>-1</ns0:VersionId>
<ns0:RevisionForVersion xsi:nil="true"/>
<ns0:Version xsi:nil="true"/>
<ns0:VersionStatus xsi:nil="true"/>
<ns0:VersionDescription xsi:nil="true"/>
<ns0:VersionPlannedEffectiveDateTime xsi:nil="true"/>
<ns0:LastSubmittedNewItemRequest xsi:nil="true"/>
<ns0:ChangeNotice xsi:nil="true"/>
<ns0:ChangeOrderLineSequenceNumber xsi:nil="true"/>
<ns0:StructureItemTypeValue>Standard</ns0:StructureItemTypeValue>
<ns0:CreateConfiguredItem xsi:nil="true"/>
<ns0:ConfigModelTypeValue>Standard</ns0:ConfigModelTypeValue>
<ns0:EffectivityControlValue>Date</ns0:EffectivityControlValue>
<ns0:BaseItemValue xsi:nil="true"/>
<ns0:AutoCreatedConfigurationFlag>false</ns0:AutoCreatedConfigurationFlag>
<ns0:PickComponentsFlag>false</ns0:PickComponentsFlag>
<ns0:AssembleToOrderFlag>false</ns0:AssembleToOrderFlag>
<ns0:CostingEnabledFlag>true</ns0:CostingEnabledFlag>
<ns0:IncludeInRollUpFlag>true</ns0:IncludeInRollUpFlag>
<ns0:StandardLotSize xsi:nil="true"/>
<ns0:InventoryAssetFlag>true</ns0:InventoryAssetFlag>
<ns0:BuildInWIPFlag>true</ns0:BuildInWIPFlag>
<ns0:WIPSupplyTypeValue>Push</ns0:WIPSupplyTypeValue>
<ns0:WIPSupplyLocatorValue xsi:nil="true"/>
<ns0:WIPSupplySubinventoryValue xsi:nil="true"/>
<ns0:OvercompletionToleranceTypeValue xsi:nil="true"/>
<ns0:OvercompletionToleranceValue xsi:nil="true"/>
<ns0:InventoryCarryPenalty xsi:nil="true"/>
<ns0:OperationSlackPenalty xsi:nil="true"/>
<ns0:RecipeEnabledFlag>true</ns0:RecipeEnabledFlag>
<ns0:ProcessQualityEnabledFlag>false</ns0:ProcessQualityEnabledFlag>
<ns0:ProcessCostingEnabledFlag>false</ns0:ProcessCostingEnabledFlag>
<ns0:ProcessExecutionEnabledFlag>true</ns0:ProcessExecutionEnabledFlag>
<ns0:ProcessSupplySubinventoryValue xsi:nil="true"/>
12
<ns0:ProcessSupplyLocatorValue xsi:nil="true"/>
<ns0:ProcessYieldSubinventoryValue xsi:nil="true"/>
<ns0:ProcessYieldLocatorValue xsi:nil="true"/>
<ns0:HazardousMaterialFlag>true</ns0:HazardousMaterialFlag>
<ns0:CASNumber xsi:nil="true"/>
<ns0:AssetItemTypeValue xsi:nil="true"/>
<ns0:AssetActivityCauseValue xsi:nil="true"/>
<ns0:AssetActivityShutdownTypeValue xsi:nil="true"/>
<ns0:AssetTrackedFlag>false</ns0:AssetTrackedFlag>
<ns0:EAMActivityTypeValue xsi:nil="true"/>
<ns0:EAMActivitySourceValue xsi:nil="true"/>
<ns0:EAMActivityNotificationFlag xsi:nil="true"/>
<ns0:AssetClassValue>Equipment</ns0:AssetClassValue>
<ns0:ServiceRequestEnabledValue xsi:nil="true"/>
<ns0:DefectTrackingOnFlag xsi:nil="true"/>
<ns0:ServiceableProductFlag>true</ns0:ServiceableProductFlag>
<ns0:CommsActivationReqdFlag xsi:nil="true"/>
<ns0:ServiceDurationTypeValue>Open Ended</ns0:ServiceDurationTypeValue>
<ns0:ServiceDuration xsi:nil="true"/>
<ns0:ServiceDurationPeriodValue xsi:nil="true"/>
<ns0:ServiceStartTypeValue>Milestone</ns0:ServiceStartTypeValue>
<ns0:ServiceStartDelay>0</ns0:ServiceStartDelay>
<ns0:AllowSuspendFlag>false</ns0:AllowSuspendFlag>
<ns0:AllowTerminateFlag>false</ns0:AllowTerminateFlag>
<ns0:RequiresFulfillmentLocFlag>false</ns0:RequiresFulfillmentLocFlag>
<ns0:RequiresItemAssociationFlag>false</ns0:RequiresItemAssociationFlag>
<ns0:TrackInstalledBaseFlag xsi:nil="true"/>
<ns0:CreateFixedAssetFlag xsi:nil="true"/>
<ns0:InstanceClassValue xsi:nil="true"/>
<ns0:BillingTypeValue xsi:nil="true"/>
<ns0:ServiceBillingEnabledFlag>false</ns0:ServiceBillingEnabledFlag>
<ns0:RecoveredPartDispositionValue xsi:nil="true"/>
<ns0:InventoryItemFlag>true</ns0:InventoryItemFlag>
<ns0:StockEnabledFlag>true</ns0:StockEnabledFlag>
<ns0:MaterialTransactionEnabledFlag>true</ns0:MaterialTransactionEnabledFlag>
<ns0:ReservableFlag>true</ns0:ReservableFlag>
<ns0:CheckMaterialShortageFlag>false</ns0:CheckMaterialShortageFlag>
<ns0:RevisionQuantityControlFlag>true</ns0:RevisionQuantityControlFlag>
<ns0:BulkPickedFlag>false</ns0:BulkPickedFlag>
<ns0:LotControlValue>No lot control</ns0:LotControlValue>
<ns0:StartingLotPrefix xsi:nil="true"/>
<ns0:StartingLotNumber xsi:nil="true"/>
<ns0:MaturityDays xsi:nil="true"/>
<ns0:HoldDays xsi:nil="true"/>
<ns0:LotExpirationControlValue>No shelf life control</ns0:LotExpirationControlValue>
<ns0:ShelfLifeDays>0</ns0:ShelfLifeDays>
<ns0:RetestInterval xsi:nil="true"/>
<ns0:ExpirationActionValue xsi:nil="true"/>
<ns0:ExpirationActionInterval xsi:nil="true"/>
<ns0:ChildLotEnabledFlag>false</ns0:ChildLotEnabledFlag>
<ns0:ChildLotFormatValidationFlag>false</ns0:ChildLotFormatValidationFlag>
<ns0:CopyLotAttributeFlag>false</ns0:CopyLotAttributeFlag>
13
<ns0:ChildLotPrefix xsi:nil="true"/>
<ns0:ChildLotStartingNumber xsi:nil="true"/>
<ns0:ChildLotParent xsi:nil="true"/>
<ns0:LotTranslateEnabledFlag>false</ns0:LotTranslateEnabledFlag>
<ns0:LotSplitEnabledFlag>false</ns0:LotSplitEnabledFlag>
<ns0:LotDivisibleFlag>false</ns0:LotDivisibleFlag>
<ns0:LotSubstitutionEnabledFlag xsi:nil="true"/>
<ns0:LotMergeEnabledFlag>false</ns0:LotMergeEnabledFlag>
<ns0:GradeControlFlag>false</ns0:GradeControlFlag>
<ns0:DefaultGradeValue xsi:nil="true"/>
<ns0:SerialGenerationValue>No serial number control</ns0:SerialGenerationValue>
<ns0:SerialStartingPrefix xsi:nil="true"/>
<ns0:SerialStartingNumber xsi:nil="true"/>
<ns0:NegativeMeasurementError xsi:nil="true"/>
<ns0:PositiveMeasurementError xsi:nil="true"/>
<ns0:CycleCountEnabledFlag>false</ns0:CycleCountEnabledFlag>
<ns0:LotStatusEnabledFlag>false</ns0:LotStatusEnabledFlag>
<ns0:SerialStatusEnabledFlag>false</ns0:SerialStatusEnabledFlag>
<ns0:DefaultLotStatusValue xsi:nil="true"/>
<ns0:DefaultSerialStatusValue xsi:nil="true"/>
<ns0:RestrictSubinventoriesFlag>false</ns0:RestrictSubinventoriesFlag>
<ns0:RestrictLocatorsFlag>false</ns0:RestrictLocatorsFlag>
<ns0:StockLocatorControlValue>No control</ns0:StockLocatorControlValue>
<ns0:DimensionUOMValue xsi:nil="true"/>
<ns0:UnitWidthQuantity xsi:nil="true"/>
<ns0:UnitLengthQuantity xsi:nil="true"/>
<ns0:UnitHeightQuantity xsi:nil="true"/>
<ns0:WeightUOMValue xsi:nil="true"/>
<ns0:UnitWeightQuantity xsi:nil="true"/>
<ns0:VolumeUOMValue xsi:nil="true"/>
<ns0:UnitVolumeQuantity xsi:nil="true"/>
<ns0:ContainerItemFlag xsi:nil="true"/>
<ns0:ContainerTypeValue xsi:nil="true"/>
<ns0:MaximumLoadWeight xsi:nil="true"/>
<ns0:VehicleItemFlag xsi:nil="true"/>
<ns0:InternalVolume xsi:nil="true"/>
<ns0:MinimumFillPercent xsi:nil="true"/>
<ns0:WarehouseEquipmentFlag>false</ns0:WarehouseEquipmentFlag>
<ns0:EventFlag xsi:nil="true"/>
<ns0:CollateralFlag xsi:nil="true"/>
<ns0:CustomerOrderFlag>true</ns0:CustomerOrderFlag>
<ns0:CustomerOrderEnabledFlag>true</ns0:CustomerOrderEnabledFlag>
<ns0:ATPComponentsValue>None</ns0:ATPComponentsValue>
<ns0:PickingRuleValue xsi:nil="true"/>
<ns0:RMAInspectionRequiredFlag>false</ns0:RMAInspectionRequiredFlag>
<ns0:EligibilityRuleFlag xsi:nil="true"/>
<ns0:InternalOrderFlag>false</ns0:InternalOrderFlag>
<ns0:InternalOrderEnabledFlag>false</ns0:InternalOrderEnabledFlag>
<ns0:ReturnableFlag>false</ns0:ReturnableFlag>
<ns0:ATPValue>None</ns0:ATPValue>
<ns0:FinancingAllowedFlag xsi:nil="true"/>
<ns0:SalesProductTypeValue xsi:nil="true"/>
14
<ns0:TransactionEnabledFlag>true</ns0:TransactionEnabledFlag>
<ns0:OrderManagementIndivisibleFlag xsi:nil="true"/>
<ns0:DefaultSalesOrderSourceTypeValue>Internal</ns0:DefaultSalesOrderSourceTypeValue>
<ns0:ElectronicFormatFlag xsi:nil="true"/>
<ns0:ShippableFlag>true</ns0:ShippableFlag>
<ns0:DefaultShippingOrganizationValue xsi:nil="true"/>
<ns0:ShipModelCompleteFlag>false</ns0:ShipModelCompleteFlag>
<ns0:DownloadableFlag xsi:nil="true"/>
<ns0:OverShipmentTolerance xsi:nil="true"/>
<ns0:UnderShipmentTolerance xsi:nil="true"/>
<ns0:OverReturnTolerance xsi:nil="true"/>
<ns0:UnderReturnTolerance xsi:nil="true"/>
<ns0:InvoicedFlag>true</ns0:InvoicedFlag>
<ns0:AccountingRuleValue xsi:nil="true"/>
<ns0:PaymentTermsValue xsi:nil="true"/>
<ns0:OutputTaxClassificationCodeValue xsi:nil="true"/>
<ns0:InvoiceEnabledFlag>true</ns0:InvoiceEnabledFlag>
<ns0:InvoicingRuleValue xsi:nil="true"/>
<ns0:SalesAccountValue xsi:nil="true"/>
<ns0:WebStatusValue>Unpublished</ns0:WebStatusValue>
<ns0:BackOrderableFlag xsi:nil="true"/>
<ns0:OrderableOnWebFlag>true</ns0:OrderableOnWebFlag>
<ns0:MinimumLicenseQuantity xsi:nil="true"/>
<ns0:InventoryPlanningMethodValue>Not planned</ns0:InventoryPlanningMethodValue>
<ns0:PlanningMakeBuyValue>Make</ns0:PlanningMakeBuyValue>
<ns0:Planner xsi:nil="true"/>
<ns0:SubcontractingComponentValue xsi:nil="true"/>
<ns0:MinimumMinmaxQuantity xsi:nil="true"/>
<ns0:MaximumMinmaxQuantity xsi:nil="true"/>
<ns0:MinimumOrderQuantity xsi:nil="true"/>
<ns0:MaximumOrderQuantity xsi:nil="true"/>
<ns0:OrderCost xsi:nil="true"/>
<ns0:CarryPercentage xsi:nil="true"/>
<ns0:ReplenishmentType xsi:nil="true"/>
<ns0:SourceOrganizationValue xsi:nil="true"/>
<ns0:SourceSubinventoryOrganizationValue xsi:nil="true"/>
<ns0:SourceSubinventoryValue xsi:nil="true"/>
<ns0:FixedOrderQuantity xsi:nil="true"/>
<ns0:FixedDaysSupply xsi:nil="true"/>
<ns0:FixedLotSizeMultiplier xsi:nil="true"/>
<ns0:ReleaseAuthorizationRequiredValue>Customer</ns0:ReleaseAuthorizationRequiredValue>
<ns0:AutomaticallyExpireASNFlag>false</ns0:AutomaticallyExpireASNFlag>
<ns0:ConsignedFlag>false</ns0:ConsignedFlag>
<ns0:ReplenishmentMinimumOrder xsi:nil="true"/>
<ns0:ReplenishmentMinimumDays xsi:nil="true"/>
<ns0:MaximumOrder xsi:nil="true"/>
<ns0:MaximumDaysOfSupply xsi:nil="true"/>
<ns0:VMIFixedOrderQuantity xsi:nil="true"/>
<ns0:ForecastTypelValue>Order Forecast</ns0:ForecastTypelValue>
<ns0:ForecastHorizon xsi:nil="true"/>
<ns0:PlanningMethodValue>MPS Planning</ns0:PlanningMethodValue>
<ns0:Pegging>None</ns0:Pegging>
15
<ns0:RoundingControlTypeFlag>true</ns0:RoundingControlTypeFlag>
<ns0:CreateSupplyFlag>true</ns0:CreateSupplyFlag>
<ns0:CriticalComponentFlag>false</ns0:CriticalComponentFlag>
<ns0:PlanningTimeFence>User Defined Time Fence</ns0:PlanningTimeFence>
<ns0:DemandTimeFence xsi:nil="true"/>
<ns0:ReleaseTimeFence xsi:nil="true"/>
<ns0:SubstitutionWindow xsi:nil="true"/>
<ns0:ShrinkageRate xsi:nil="true"/>
<ns0:ForecastControlValue>Consume and Derive Forecast</ns0:ForecastControlValue>
<ns0:AcceptableEarlyDays xsi:nil="true"/>
<ns0:PlannedInventoryPointFlag xsi:nil="true"/>
<ns0:ExcludeFromBudgetFlag>false</ns0:ExcludeFromBudgetFlag>
<ns0:PlanningTimeDays>1</ns0:PlanningTimeDays>
<ns0:DemandTimeDays xsi:nil="true"/>
<ns0:ReleaseTimeDays xsi:nil="true"/>
<ns0:SubstitutionDays xsi:nil="true"/>
<ns0:MRPCalculateATPFlag xsi:nil="true"/>
<ns0:DRPPlannedFlag>false</ns0:DRPPlannedFlag>
<ns0:MaximumInventoryWindow xsi:nil="true"/>
<ns0:DaysMaximumInventorySupply xsi:nil="true"/>
<ns0:TargetInventoryDaysofSupply xsi:nil="true"/>
<ns0:TagetInventoryWindow xsi:nil="true"/>
<ns0:RepairLeadtime xsi:nil="true"/>
<ns0:RepairYield xsi:nil="true"/>
<ns0:PrepositionPointFlag>false</ns0:PrepositionPointFlag>
<ns0:RepairProgramValue>Repair Return</ns0:RepairProgramValue>
<ns0:PreprocessingDays xsi:nil="true"/>
<ns0:PostprocessingDays>0</ns0:PostprocessingDays>
<ns0:ProcessingDays xsi:nil="true"/>
<ns0:VariableLeadTime xsi:nil="true"/>
<ns0:CumulativeTotalLeadTime xsi:nil="true"/>
<ns0:FixedLeadTime xsi:nil="true"/>
<ns0:CumulativeManufacturingLeadTime xsi:nil="true"/>
<ns0:LeadTimeLotSize>1</ns0:LeadTimeLotSize>
<ns0:PurchasingFlag>true</ns0:PurchasingFlag>
<ns0:UseApprovedSupplierFlag>false</ns0:UseApprovedSupplierFlag>
<ns0:NegotiationRequiredFlag xsi:nil="true"/>
<ns0:PurchasingInputTaxClassificationValue xsi:nil="true"/>
<ns0:UnitOfIssueValue xsi:nil="true"/>
<ns0:InvoiceCloseTolerancePercentage xsi:nil="true"/>
<ns0:HazardClassValue xsi:nil="true"/>
<ns0:AssetCategoryValue xsi:nil="true"/>
<ns0:PurchasableFlag>true</ns0:PurchasableFlag>
<ns0:AllowItemDescriptionUpdateFlag>true</ns0:AllowItemDescriptionUpdateFlag>
<ns0:TaxableFlag>true</ns0:TaxableFlag>
<ns0:BuyerOrganizationValue xsi:nil="true"/>
<ns0:DefaultBuyerValue xsi:nil="true"/>
<ns0:ReceiptCloseTolerancePercentage xsi:nil="true"/>
<ns0:UNNumberValue xsi:nil="true"/>
<ns0:PriceTolerancePercentage xsi:nil="true"/>
<ns0:ExpenseAccountValue xsi:nil="true"/>
<ns0:RoundingFactor xsi:nil="true"/>
16
<ns0:OutsourcedAssemblyFlag>false</ns0:OutsourcedAssemblyFlag>
<ns0:OutsideProcessingFlag>false</ns0:OutsideProcessingFlag>
<ns0:OutsideProcessingUnitTypeValue xsi:nil="true"/>
<ns0:MatchApprovalLevelValue xsi:nil="true"/>
<ns0:MatchConfigurationOptionValue xsi:nil="true"/>
<ns0:ReceiptRountingValue xsi:nil="true"/>
<ns0:EnforceShipToLocation xsi:nil="true"/>
<ns0:ReceiptDateActionValue xsi:nil="true"/>
<ns0:DaysEarlyReceiptAllowed xsi:nil="true"/>
<ns0:DaysLateReceiptAllowed xsi:nil="true"/>
<ns0:AllowSubstituteReceiptsFlag xsi:nil="true"/>
<ns0:AllowUnorderedReceiptsFlag xsi:nil="true"/>
<ns0:AllowExpressDeliveryFlag xsi:nil="true"/>
<ns0:QuantityReceivedToleranceAction xsi:nil="true"/>
<ns0:QuantityReceivedTolerancePercentage xsi:nil="true"/>
<ns0:j_ItemExtensibleFlexfieldCategoryCode>EFF_NT_SR_MR_NV_ALL_LEVEL_ALL_TYPES
_2</ns0:ItemExtensibleFlexfieldCategoryCode>
<ns0:CreationDate>2014-03-19T05:27:40.0-07:00</ns0:CreationDate>
<ns0:LastUpdateDate>2014-03-19T05:27:42.987-07:00</ns0:LastUpdateDate>
<ns0:PayloadId>0</ns0:PayloadId>
<ns2:ItemEFFBAG_5FNT_5FSR_5FNV_5FIL_5FSL_5FALL_5FTYPES_5F2PrivateVO>
<ns3:ContextCode>AG_NT_SR_NV_IL_SL_ALL_TYPES_2</ns3:ContextCode>
<ns3:CreatedBy>PIMQA</ns3:CreatedBy>
<ns3:EffLineId>300100071134792</ns3:EffLineId>
<ns3:InventoryItemId>100100040149840</ns3:InventoryItemId>
<ns3:LastUpdateLogin>F558187E92AF11BAE043505000A69C0</ns3:LastUpdateLogin
>
<ns3:LastUpdatedBy>PIMQA</ns3:LastUpdatedBy>
<ns3:ObjectVersionNumber>2</ns3:ObjectVersionNumber>
<ns3:CategoryCode>EFF_NT_SR_MR_NV_ALL_LEVEL_ALL_TYPES_2</ns3:Categ
oryCode>
<ns4:RaiseEvent>Y</ns4:RaiseEvent>
<ns4:IsPersistentAttributeUpdated>false</ns4:IsPersistentAttributeUpdated>
<ns4:IsAddedToChildEntitiesMap>false</ns4:IsAddedToChildEntitiesMap>
<ns4:IsImportCase>false</ns4:IsImportCase>
<ns4:_Character1>SR Update</ns4:_Character1>
<ns4:RedLine_Character1 xsi:nil="true"/>
<ns4:_Character2 xsi:nil="true"/>
<ns4:RedLine_Character2 xsi:nil="true"/>
<ns4:_Number1>231</ns4:_Number1>
<ns4:RedLine_Number1 xsi:nil="true"/>
<ns4:_Number2 xsi:nil="true"/>
<ns4:RedLine_Number2 xsi:nil="true"/>
<ns4:_Date1>2012-10-20</ns4:_Date1>
<ns4:RedLine_Date1 xsi:nil="true"/>
<ns4:_Date2 xsi:nil="true"/>
<ns4:RedLine_Date2 xsi:nil="true"/>
<ns4:_Date_Time1 xsi:nil="true"/>
<ns4:RedLine_Date_Time1 xsi:nil="true"/>
17
<ns4:_Date_Time2 xsi:nil="true"/>
<ns4:RedLine_Date_Time2 xsi:nil="true"/>
<ns4:u_Number_UOM_QTY_1UE xsi:nil="true"/>
<ns4:RedLineu_Number_UOM_QTY_1UE xsi:nil="true"/>
<ns4:_Number_UOM_QTY_1UEUOM xsi:nil="true"/>
<ns4:RedLine_Number_UOM_QTY_1UEUOM xsi:nil="true"/>
<ns4:u_Number_UOM_Length_2UE xsi:nil="true"/>
<ns4:RedLineu_Number_UOM_Length_2UE xsi:nil="true"/>
<ns4:_Number_UOM_Length_2UEUOM xsi:nil="true"/>
<ns4:RedLine_Number_UOM_Length_2UEUOM xsi:nil="true"/>
</ns2:ItemEFFBAG_5FNT_5FSR_5FNV_5FIL_5FSL_5FALL_5FTYPES_5F2PrivateVO>
<ns0:j_ItemExtensibleFlexfieldCategoryCode>
<ns0:ItemRevision>
<ns6:RevisionId>300100071134812</ns6:RevisionId>
<ns6:RevisionCode>A</ns6:RevisionCode>
<ns6:ItemRevisionDescription xsi:nil="true"/>
<ns6:RevisionReasonValue xsi:nil="true"/>
<ns6:EffectivityDate>2014-03-19T05:27:40.0-07:00</ns6:EffectivityDate>
<ns6:RevisionExtensibleFlexfieldCategoryCode>EFF_NT_SR_MR_NV_ALL_LEVEL_AL
L_TYPES_2</ns6:RevisionExtensibleFlexfieldCategoryCode>
<ns6:CreationDateTime>2014-03-19T05:27:41.13-07:00</ns6:CreationDateTime>
<ns6:LastUpdateDateTime>2014-03-19T05:27:43.94-07:00</ns6:LastUpdateDateTime>
<ns6:Description xsi:nil="true"/>
<ns6:Language>KO</ns6:Language>
<ns6:SourceLanguage>US</ns6:SourceLanguage>
<ns6:ItemRevisionDFF>
<ns7:_IREV_Glob_Seg_Char_1 xsi:nil="true"/>
<ns7:_zBIAItemRevDFF xsi:nil="true"/>
<ns7:__FLEX_Context xsi:nil="true"/>
<ns7:_FLEX_NumOfSegments>2</ns7:_FLEX_NumOfSegments>
</ns6:ItemRevisionDFF>
<ns6:ItemRevisionEffCategory
xsi:type="ns8:j_ItemRevisionEffNtSrMrNvAllLevelAllTypes_5F2Private">
</ns6:ItemRevisionEffCategory>
</ns0:ItemRevision>
<ns0:ItemCategory>
<ns6:ItemCatalog>Inv.Items</ns6:ItemCatalog>
<ns6:CategoryName>Uncategorized</ns6:CategoryName>
<ns6:SequenceNumber xsi:nil="true"/>
<ns6:ItemCategoryAssignmentId>300100056583529</ns6:ItemCategoryAssignmentId>
18
</ns0:ItemCategory>
<ns0:ItemDFF>
<ns21:_ITM_Glob_Seg_Char_1 xsi:nil="true"/>
<ns21:_zBIAItemDFF xsi:nil="true"/>
</ns0:ItemDFF>
</ns0:Item>
Notes:
1.
2.
3.
4.
5.
6.
7.
8.
9.
The Item content published is always the Production data for the item. The Draft
and content for non-production Versions are not published.
The Language published for the item attributes will be based on the language of the
session the ESS process is launched. For example, if session language is French, the
records published will show content in the French language. If the session language is
changed to English, and the ESS process is launched, the publication records will be in
English.
A single Revision is shown for the Item
A single language is shown for the Item Revision, additional <ItemRevisionTranslation>
tags may be added based on the language setup.
The content included in the XML for the Item DFFs will depend on what DFFs are
defined for the item.
Item Translation data is not published.
The Organization Association for the item will be published as separate <ns0:Item
xsi:type="ns0:Item"> tags for each organization that the item is assigned to. The value
of the <ns6:OrganizationId> element will indicate the assignment of the item to the
organization. In the example above, the item is assigned to a single organization.
Extensible Flexfields are available for Items and Item Revisions
The Extensible Flexfields publication use different terminology than the user interface
does, the corresponding XML tags for Extensible Flexfields are:
<ns0:j_ItemEffCategory> - corresponds to the Item Class
<ns2:ItemEFFBAGTESTPrivateVO> - Corresponds to the Attribute Group
<ns4:uagnetweightUE xsi:nil="true"/> - Corresponds to an attribute within the
attribute group.
Multi-row attribute group will be indicated by <ns4:_Date2 xsi:nil="true"/>, note
the extra underscore before the attribute name. The UI for this attribute group
looks like image below, see the column: Date2 (Prompt):
10. The Revision Extensible Flexfields publication use different terminology than the user
interface does, the corresponding XML tags for Extensible Flexfields are:
19
<ns0:ItemRevisionEffCategory> - corresponds to the Item Class

<ns2:ItemRevisionEFFBAGTESTPrivateVO> - Corresponds to the Attribute
Group
<ns4:uagnetweightUE xsi:nil="true"/> - Corresponds to an attribute within the
attribute group.
See Multi-row attribute group above
11. One or more ItemCategory records will be displayed depending on the automatic
assignment process at Item creation or by the user making manual assignments.
12. Additional records maybe published if more than one extensible flexfileds is define for
the item or item revisions.
Attachment: URL Selection
The Attachment URL selection will publish any item that has an attachment where the attachment
Type =URL and will be designed by the <ns0:ItemAttachment>
</ns0:ItemAttachment> tag set in the file. If the Attachment: URL is the only selected entity for
items, then the Base Item Attribute information will be displayed for the item along with the Item
Attachment tag data, as shown below. Otherwise if multiple item entities are selected, Attachment
URL data will be published along with other item entities.
Item Attachment XML Tags
Tags
Description

item record.
Item Attachments (URL Only)
<ns0:ItemAttachment></ns0:ItemAttachment>
Item Attachment XML File Format
<ns0:ItemNumber>SMC_ALL_1</ns0:ItemNumber>
<ns0:ItemDescription>SMC_ALL_1</ns0:ItemDescription>
<ns0:ItemAttachment>
<ns0:AttachedDocumentId>300100076175574</ns0:AttachedDocumentId>
<ns0:DocumentURL>https://stbeehive.oracle.com/bconf/jspfiles/private.jsp?</ns0:Docu
mentURL>
</ns0:ItemAttachment>
</ns0:Item>
Associations: Supplier Site Organizations Selection
The Associations: Supplier Site Organizations item entities will publish only the Item Supplier Site
Organizations association for the item and will be designated by <ns0:ItemSupplierAssociation>
</ns0:ItemSupplierAssociation> tag sets in the file.
Item Supplier Site Organization Association XML Tags
Tags
Description
20
<ns0:ItemSupplierAssociation>
</ns0:ItemSupplierAssociation>
<ns6:SupplierExtensibleFlexfieldCategoryCode>
</ns6:SupplierExtensibleFlexfieldCategoryCode>
<ns0:ItemSupplierEffCategory>
</ns0:ItemSupplierEffCategory>
<ns2:ItemSupplierEFFBAGTESTPrivateVO>
</ns2:ItemSupplierEFFBAGTESTPrivateVO>
<ns4:_Character1></ns4:_Character1>
<ns4:uagnetweightUE xsi:nil="true">
</ns4:uagnetweightUE xsi:nil="true">

item record.
Item Association between an item, Supplier
Site and Organization.
Item Supplier Association Extensible
Flexfield Category ( Item Class).
Flexfield Attribute Group.
Flexfield Attribute.
EFF Multi-row Attribute Group Column
value.
EFF Attribute
Item Supplier Site Organization Association XML File Format
<ns0:ItemNumber>SMC_01</ns0:ItemNumber>
<ns0:ItemDescription>SMC_01</ns0:ItemDescription>
<ns0:ItemSupplierAssociation>
<ns6:AssociationId>300100063167553</ns6:AssociationId>
<ns6:SupplierName>Office Max</ns6:SupplierName>
<ns6:SupplierNumber>50623</ns6:SupplierNumber>
<ns6:PartySiteNumber>22367</ns6:PartySiteNumber>
<ns6:AddressName>SALES</ns6:AddressName>
<ns6:Address>20098 Florida Avenue</ns6:Address>
<ns6:SupplierItemNumber xsi:nil="true"/>
<ns6:PrimaryFlag>false</ns6:PrimaryFlag>
<ns6:SupplierSiteAssociationStatus xsi:nil="true"/>
<ns6:SupplierExtensibleFlexfieldCategoryCode>ROOT_ICC</ns6:SupplierExtensibleFlexfie
ldCategoryCode>
<ns6:ItemSupplierEffCategory xsi:type="ns16:j_ItemSupplierRootIccPrivate">
<ns16:AcdType>PROD</ns16:AcdType>
<ns16:AssociationId>300100063167553</ns16:AssociationId>
<ns16:ChangeBitMap>0</ns16:ChangeBitMap>
<ns16:ChangeLineId>-1</ns16:ChangeLineId>
<ns16:ImplementationDate>2014-03-13T06:42:02.007:00</ns16:ImplementationDate>
<ns16:JobDefinitionName xsi:nil="true"/>
<ns16:JobDefinitionPackage xsi:nil="true"/>
21
<ns16:LastUpdateLogin>F4786FDEB61E2DE2E0435050FAA7E4</ns16:LastUpdate
Login>
<ns16:PrimaryFlag>N</ns16:PrimaryFlag>
<ns16:ProgramAppName xsi:nil="true"/>
<ns16:ProgramName xsi:nil="true"/>
<ns16:RequestId xsi:nil="true"/>
<ns16:StatusCode>1</ns16:StatusCode>
<ns16:VersionEndDate xsi:nil="true"/>
<ns16:VersionStartDate>2014-03-13T06:42:02.0-07:00</ns16:VersionStartDate>
<ns16:MasterOrganizationId>204</ns16:MasterOrganizationId>
<ns16:OrganizationId1>204</ns16:OrganizationId1>
<ns16:SupplierId>299394</ns16:SupplierId>
<ns16:SupplierSiteId>172951</ns16:SupplierSiteId>
<ns16:ContextChangeLineId>-1</ns16:ContextChangeLineId>
<ns16:ContextVersionId>-1</ns16:ContextVersionId>
<ns16:ContextDate xsi:nil="true"/>
<ns16:ItemCatalogGroupId>100000011369001</ns16:ItemCatalogGroupId>
<ns16:Duns xsi:nil="true"/>
<ns16:SupplierName>Office Max</ns16:SupplierName>
<ns16:SupplierSiteName>SALES</ns16:SupplierSiteName>
<ns16:SupplierNumber>50623</ns16:SupplierNumber>
<ns16:CategoryCode>ROOT_ICC</ns16:CategoryCode>
<ns16:StyleItemId>300100063167480</ns16:StyleItemId>
</ns6:ItemSupplierEffCategory>
</ns0:ItemSupplierAssociation>
</ns0:Item>
Item Category Assignments Selection
The Item Category Assignment selection will publish within the <item> tag the data for the category
assignments for an item and will be designated by the <ns0:Item xsi:type="ns0:Item"></ns0:Item
xsi:type="ns0:Item"> tags in the file. Each Item Category tag set will contain one assignment for the
item and multiple sets of Item Category Tags may exist for the item.
Item Category Assignments XML Tags
Tags
Description

item record.
Item assignments to a category in a catalog.
<ns0:ItemCategory></ns0:ItemCategory>
Item Category Assignments XML File Format
22
<ns0:ItemDescription>SMC_ALL_1</ns0:ItemDescription>
<ns0:ItemCategory>
<ns6:ItemCatalog>Purchasing</ns6:ItemCatalog>
<ns6:CategoryName>Miscellaneous_1</ns6:CategoryName>
<ns6:ItemCategoryAssignmentId>300100076175572</ns6:ItemCategoryAssignmentId>
</ns0:ItemCategory>
</ns0:Item>
Item Relationships: GTIN Selection
The Item Relationships: GTIN selection publishes the data for the item relationships of type GTIN
for an item. The GTIN Item Relationship data will be displayed using the GTINXref tags:
<ns0:GTINXref>.Multiple GTIN tags may exist for the item. The GTIN Item Relationship data may
contain translated values records and/or Descriptive Flexfields records as part of the <GINXref> tag
data. The translation records use the <ItemRelationshipTranslation> tags, and the descriptive
flexfields use the <ItemRelationShipDFF> tags. The number of <ItemRelationTranslation> record
will depend of how many languages are enabled and the number of elements within the
<ItemRelationShipDFF> tags will be based on the descriptive flexfields defined for the Item
Relationship GTINs.
Item Relationships: GTIN XML Tags
Tags
Description
<ns0:GTINXref> </ns0:GTINXref>

item record.
Item relationship between Item and GTIN.
<ns11:ItemRelationTranslation>
</ns11:ItemRelationTranslation>
<ns11:ItemRelationShipsDFF>
</ns11:ItemRelationShipsDFF>
Translated Content for Item Relationship:

GTIN
Descriptive Flexfields for Item
Relationship: GTIN
Item Relationships: GTIN XML File Format
<ns0:GTINXref>
<ns11:ItemRelationshipId>300100063167560</ns11:ItemRelationshipId>
23
<ns11:TradingPartnerTypeValue>Manufacturer</ns11:TradingPartnerTypeValue>
<ns11:TradingPartnerName>TCP Manufacturer</ns11:TradingPartnerName>
<ns11:TradingPartnerNumber>100000017351024</ns11:TradingPartnerNumber>
<ns11:UOMCodeValue>Bag</ns11:UOMCodeValue>
<ns11:GTIN>00012345600012</ns11:GTIN>
<ns11:RevisionCode>A</ns11:RevisionCode>
<ns11:GTINDescription xsi:nil="true"/>
<ns11:EPCGTINSerial xsi:nil="true"/>
<ns11:RelationshipDescription xsi:nil="true"/>
<ns11:LastUpdateDateTime>2014-03-13T09:47:58.86307:00</ns11:LastUpdateDateTime>
<ns12:ItemRelationshipType>GTIN_XREF</ns12:ItemRelationshipType>
<ns12:_REL_Glob_Seg_Char_1 xsi:nil="true"/>
<ns12:_zBIAItemRelDFF xsi:nil="true"/>
</ns0:GTINXref>
</ns0:Item>
Note: One or more ItemRelationshipTranslation records maybe displayed based on the number of
languages that are being translated.
Item Relationships: Trading Partner Items Selection
The Item Relationships: Trading Partner Items selection will publish data for each of the Trading
Partner type: Competitor, Customer, Manufacturer and Supplier. Each of the Trading Partner types
will be identified in the output by deferent tags sets. Each of the Trading Partner types may have
multiple translations and descriptive flexfields.
Since one or more Item Relationships for Trading Partner Items can be define multiple tags maybe
published for each of the Trading Partner types.
Item Relationships: Trading Partner Items XML Tags
Tags
Description

item record.
Item relationship between Item and
Competitor Item.
Item Relationship between Item and
<CompetitorItemXref> </CompetitorItemXref>
<CustomerItemXref></CustomerItemXref>
24
<MfgPartNumber></MfgPartNumber>
<SupplierItemXref></SupplierItemXref>
Customer Item.
Manufacturer part number.
Supplier Item.
Translated Content for Item Relationship:
Relationship
The following sections show content that is published for the Item Relationships: Trading Partner
Items:
Item Relationships: Trading Partner Items: Competitor
<ns0:CompetitorItemXref>
<ns11:TradingPartnerType>COMPETITOR</ns11:TradingPartnerType>
<ns11:TradingPartnerName>Aberdeen LLC</ns11:TradingPartnerName>
<ns11:TradingPartnerItemNumber>cp-item1-apr30</ns11:TradingPartnerItemNumber>
<ns11:StartDate>2014-03-13</ns11:StartDate>
<ns11:EndDate xsi:nil="true"/>
<ns11:CustomerItemRelationshipRank xsi:nil="true"/>
<ns11:CompetitorItemRelationshipTypeValue>Complementary</ns11:CompetitorItemRelatio
nshipTypeValue>
<ns11:RelationshipDescription>Aberdeen LLC</ns11:RelationshipDescription>
<ns11:RelationshipDescription>Aberdeen LLC</ns11:RelationshipDescription>
<ns12:ItemRelationshipType>COMPETITOR_ITEM_XREF</ns12:ItemRelationshipTyp
e>
<ns12:_zBIAItemRelDFF>1234</ns12:_zBIAItemRelDFF>
25
</ns0:CompetitorItemXref>
</ns0:Item>
Item Relationships: Trading Partner Items: Customers
<ns0:CustomerItemXref>
<ns11:TradingPartnerType>CUSTOMER</ns11:TradingPartnerType>
<ns11:TradingPartnerName>Computer Service and Rentals</ns11:TradingPartnerName>
<ns11:TradingPartnerItemNumber>zDOO-Cust-Item</ns11:TradingPartnerItemNumber>
<ns11:CompetitorItemRelationshipTypeValue xsi:nil="true"/>
<ns11:RelationshipDescription>Computer Service and
Rentals</ns11:RelationshipDescription>
<ns11:RelationshipDescription>Computer Service and
Rentals</ns11:RelationshipDescription>
<ns12:ItemRelationshipType>CUSTOMER_ITEM_XREF</ns12:ItemRelationshipTyp
e>
26
</ns0:CustomerItemXref>
</ns0:Item>
Item Relationships: Trading Partner Items: Suppliers
<ns0:SupplierItemXref>
<ns11:TradingPartnerType>SUPPLIER</ns11:TradingPartnerType>
<ns11:TradingPartnerName>GE Capital</ns11:TradingPartnerName>
<ns11:TradingPartnerItemNumber>OATS_SUPPLIER_TPI_Jan19221559</ns11:TradingPart
nerItemNumber>
<ns11:RelationshipDescription>SMC_03</ns11:RelationshipDescription>
<ns11:RelationshipDescription>TCP_Manufacturer</ns11:RelationshipDescription>
<ns12:ItemRelationshipType>MFG_PART_NUM</ns12:ItemRelationshipType>
</ns0:SupplierItemXref>
</ns0:Item>
27
Item Relationships: Trading Partner Items: Manufacturers
<ns0:MfgPartNumber>
<ns11:TradingPartnerType>MANUFACTURER</ns11:TradingPartnerType>
<ns11:TradingPartnerName>TCP Manufacturer</ns11:TradingPartnerName>
<ns11:TradingPartnerItemNumber>TCP_Manufacturer_IMB_2527</ns11:TradingPartnerIte
mNumber>
<ns12:ItemRelationshipType>MFG_PART_NUM</ns12:ItemRelationshipType>
</ns0:MfgPartNumber>
</ns0:Item>
28
Item Relationships: Related Items Selection
The Item Relationships: Related Items selection will publish data using the <ns0:RelatedItem> tags.
Item Relationships: Related Items XML Tags
Tags
Description

item record.
Item relationship between Item and related
type..
Translated Content for Item Relationship
<ns0:RelatedItem></ns0:RelatedItem>

Relationship
Item Relationships: Related Items XML File Format
<ns0:RelatedItem>
<ns11:FromItemNumber>SMC_01</ns11:FromItemNumber>
<ns11:ToItemNumber>S01</ns11:ToItemNumber>
<ns11:RelationshipTypeValue>Substitute</ns11:RelationshipTypeValue>
<ns11:RelationshipDescription>SMC_01 to SO1</ns11:RelationshipDescription>
<ns11:ReciprocalFlag>false</ns11:ReciprocalFlag>
<ns11:PlanningEnabledFlag>false</ns11:PlanningEnabledFlag>
<ns11:RelationshipDescription>SMC_01 to SO1</ns11:RelationshipDescription>
<ns12:ItemRelationshipType>RELATED_ITEM</ns12:ItemRelationshipType>
29
</ns0:RelatedItem>
</ns0:Item>
Item Relationships: Cross-references Selection
The Item Relationships: Cross-references selection will publish data using the
<ns0:ItemCrossReference> tag and the <ns0:SysItem.
Item Relationships: Cross-references XML Tags
Tags
Description

item record.
Item relationship between two items based
on Cross-reference type.
Translated Content for Item Relationship
<ns0: ItemCrossReference >

</ns0: ItemCrossReference >

Relationship
Item Relationships: Cross-references XML File Format
<ns0:ItemCrossReference>
<ns11:CrossReferenceTypeValue>Charge Master</ns11:CrossReferenceTypeValue>
<ns11:CrossReferenceValue>12345</ns11:CrossReferenceValue>
<ns11:ApplyToAllOrganizationFlag>false</ns11:ApplyToAllOrganizationFlag>
<ns11:ApplicableOrganizationCode>V1</ns11:ApplicableOrganizationCode>
30
<ns12:ItemRelationshipType>ITEM_XREF</ns12:ItemRelationshipType>
</ns0:ItemCrossReference>
</ns0:Item>
Structures: All Selection
The structure selection will publish all the structures that have been created for items and the content
will be listed using the <ns0:Structure> tag set.
The structure may have one or more Components that are published and each component may have
descriptive flexfields published.
The structure hierarchy is not published.
Structure All XML Tags
Tags
Description

item record.
<ns0:Structure></ns0:Structure>
<ns14:Component></ns14:Component>
A structured collection of components.
<ns14:ComponetDFF>
</ns14:ComponentDFF>
<ns11:ItemStructureDFF>
Component for a structure representing

and item.
Component descriptive flexfields
Relationship
Structure All XML File Format
<ns0:Structure>
<ns14:BillSequenceId>300100076175551</ns14:BillSequenceId>
31
<ns14:StructureName>Primary</ns14:StructureName>
<ns14:Description>SMC_ALL_1</ns14:Description>
<ns14:CommonItemNumber>SMC_ALL_1</ns14:CommonItemNumber>
<ns14:CommonOrganizationCode>V1</ns14:CommonOrganizationCode>
<ns14:SourceItemNumber>SMC_ALL_1</ns14:SourceItemNumber>
<ns14:SourceOrganizationCode>V1</ns14:SourceOrganizationCode>
<ns14:StructureDFF>
<ns15:_STR_Glob_Seg_Char_1 xsi:nil="true"/>
<ns15:_STR_Glob_Seg_Num_1 xsi:nil="true"/>
<ns15:_STR_Glob_Seg_Date_1 xsi:nil="true"/>
<ns15:_STR_Glob_Seg_DtTm_1 xsi:nil="true"/>
<ns15:_zBIAStrucHeadDFF xsi:nil="true"/>
</ns14:StructureDFF>
<ns14:Component>
<ns14:ComponentSequenceId>300100076175553</ns14:ComponentSequenceId>
<ns14:ComponentItemNumber>AS10001</ns14:ComponentItemNumber>
<ns14:ItemSequenceNumber>30</ns14:ItemSequenceNumber>
<ns14:Quantity unitCode="Each">1</ns14:Quantity>
<ns14:Yield>1</ns14:Yield>
<ns14:Comments xsi:nil="true"/>
<ns14:StartDateTime>2014-03-24T06:45:20.0-07:00</ns14:StartDateTime>
<ns14:EndDateTime xsi:nil="true"/>
<ns14:ImplementationDateTime>2014-03-24T06:45:20.007:00</ns14:ImplementationDateTime>
<ns14:FromNumber xsi:nil="true"/>
<ns14:ToNumber xsi:nil="true"/>
<ns14:PlanningPercent>100</ns14:PlanningPercent>
<ns14:BasisValue>Item</ns14:BasisValue>
<ns14:EnforceIntegerRequirementsValue>None</ns14:EnforceIntegerRequirementsValu
e>
<ns14:SupplyType xsi:nil="true"/>
<ns14:AutoRequestMaterialFlag>true</ns14:AutoRequestMaterialFlag>
<ns14:MinimumQuantity xsi:nil="true"/>
<ns14:MaximumQuantity xsi:nil="true"/>
<ns14:OptionalFlag>false</ns14:OptionalFlag>
<ns14:MutuallyExclusiveFlag>false</ns14:MutuallyExclusiveFlag>
<ns14:CheckATPFlag>false</ns14:CheckATPFlag>
<ns14:SalesOrderBasisValue>None</ns14:SalesOrderBasisValue>
<ns14:InstantiabilityValue xsi:nil="true"/>
<ns14:ShowInSalesValue xsi:nil="true"/>
<ns14:RequiredToShipFlag>false</ns14:RequiredToShipFlag>
<ns14:RequiredForRevenueFlag>false</ns14:RequiredForRevenueFlag>
32
<ns14:IncludeOnShipDocsFlag>false</ns14:IncludeOnShipDocsFlag>
<ns14:ComponentDFF>
<ns13:_COMP_Glob_Seg_Char_1>A</ns13:_COMP_Glob_Seg_Char_1>
<ns13:_COMP_Glob_Seg_Char_2>ASD</ns13:_COMP_Glob_Seg_Char_2>
<ns13:_COMP_Glob_Seg_Num_1 xsi:nil="true"/>
<ns13:_COMP_Glob_Seg_Date_1 xsi:nil="true"/>
<ns13:_COMP_Glob_Seg_DtTm_1 xsi:nil="true"/>
<ns13:_zBIACompDFF xsi:nil="true"/>
</ns14:Component>
</ns0:Structure>
<ns0:Structure>
<ns14:StructureName>RULES</ns14:StructureName>
<ns14:Description>SMC_ALL</ns14:Description>
<ns14:StructureDFF>
<ns14:Component>
<ns14:ComponentItemNumber>BX3</ns14:ComponentItemNumber>
33
<ns14:EnforceIntegerRequirementsValue>None</ns14:EnforceIntegerRequirementsValue>
<ns14:ComponentDFF>
<ns13:_COMP_Glob_Seg_Char_1 xsi:nil="true"/>
<ns13:_COMP_Glob_Seg_Char_2 xsi:nil="true"/>
</ns14:Component>
</ns0:Item>
Structures: Primary Selection
The structure selection will publish only the structures that the structure name=Primary. The content
will be listed using the <ns0:Structure> tag set.
The structure may have one or more Components that are published and each component may have
descriptive flexfields published.
The structure hierarchy is not published.
Structure Primary XML Tags
Tags
Description

item record.
<ns0:Structure></ns0:Structure>
<ns14:Component></ns14:Component>
A structured collection of components.

Component for a structure representing an
34
<ns14:ComponetDFF>
<ns11:ItemStructureDFF>
item.
Component descriptive flexfields
Relationship
Structure Primary XML File Forma
<ns0:Structure>
<ns14:StructureName>Primary</ns14:StructureName>
<ns14:Description>SMC_ALL_1</ns14:Description>
<ns14:StructureDFF>
<ns14:Component>
<ns14:ComponentItemNumber>AS10001</ns14:ComponentItemNumber>
35
<ns14:EnforceIntegerRequirementsValue>None</ns14:EnforceIntegerRequirementsValu
e>
<ns14:ComponentDFF>
<ns13:_COMP_Glob_Seg_Char_1>A</ns13:_COMP_Glob_Seg_Char_1>
<ns13:_COMP_Glob_Seg_Char_2>ASD</ns13:_COMP_Glob_Seg_Char_2>
</ns14:Component>
</ns0:Structure>
</ns0:Item>
All Pack Items Selection
The All Pack Items selection will publish all items that are part of a Pack.. If any items within a pack
change, all the items in the pack will be published. All Pack Items selection uses the same tag sets as
parameters which are the <ns0:Item > tag sets. The content that is published is the Base item
attributes.
Pack Item XML Tags
Tags
Description

item record.
36
In this example the following pack was defined:

Item: Test_Item_Pub was defined with pack type=Base Unit or each
Item: PK_Case_Sept2 was defined with pack type=Case
Item: PK_Pallet_Oct1 was defined with pack type=Pallet
Pack Item XML File Format
<ns0:ItemClass>Packs</ns0:ItemClass> <ns0:Template xsi:nil="true"/>
<ns0:ItemNumber>PK_Case_Aug30</ns0:ItemNumber>
<ns0:ItemDescription>PK_Case_Desc_Aug30</ns0:ItemDescription>
(additional rows)
<ns0:PackTypeValue>Case</ns0:PackTypeValue>
(additional rows)
</ns0:Item>
<ns0:ItemClass>Packs</ns0:ItemClass> <ns0:Template xsi:nil="true"/>
<ns0:ItemNumber>PK_Pallet_Oct1</ns0:ItemNumber>
<ns0:ItemDescription>PK_Pallet_Desc_Oct1</ns0:ItemDescription>
(additional rows)
<ns0:PackTypeValue>Pallet</ns0:PackTypeValue>
(additional rows)
</ns0:Item>
<ns0:ItemClass>Capacitors_DQ</ns0:ItemClass> <ns0:Template xsi:nil="true"/>
<ns0:ItemNumber>TEST_PUB1</ns0:ItemNumber> <ns0:ItemDescription>10 Micro
Farads al 10 Volt 5 % TEST_PUB1</ns0:ItemDescription>
<ns0:ApprovalStatusValue>Approved</ns0:ApprovalStatusValue>
<ns0:LifecyclePhaseValue>Design</ns0:LifecyclePhaseValue> <ns0:StyleItemFlag
xsi:nil="true"/> <ns0:StyleItemNumberValue>TEST_PUB1</ns0:StyleItemNumberValue>
<ns0:Keyword xsi:nil="true"/> <ns0:IgnoreDuplicateItemFlag xsi:nil="true"/>
<ns0:PackTypeValue>Base Unit or Each</ns0:PackTypeValue>
(additional rows)
</ns0:Item>
Pack Hierarchy Selection
37
When the Pack Hierarchy option is selected for items and the not the All Pack Items option , the
pack items that part of items that is published are included in the payload and area published within
the Item tag structure.
The Pack Hierarchy selection publishes the pack item content and the pack hierarchy content that the
pack item is a participates in. The pack hierarchy is published using the <ns0:Pack> tag set. The
<ns0:Pack> tag contains the following tag sets:
<ns0:Pack> - The pack hierarchy structure
<ns14:PackComponent> The pack component assigned to the pack item.
When the pack hierarchy is created, the User selects the initial pack item and assigns additional pack
items to the initial pack item. This process is repeated to create the hierarchy. The Pack Hierarchy
selection does not publish the complete hierarchy for the pack item, but only show one level of the
pack hierarchy. In the example below, a simple pack hierarchy was created for the following pack
items:
SMC_PALLET_3 Pack Item with Pack Type=Pallet
SMC_CASE_3 Pack Item with Pack Type=Case
SMC_INNER_3 Pack Item with Pack Type=Pack or Inner Case
SMC_BASE_3 Pack Item with Pack Type=Base Unit or Each
Each of the Pack Items (Items with Pack Type attribute set to selected values) is listed as a separate set
of tags <ns0:Item ></ns0:Item >, within these tags, the <ns0:Pack> tags will contain the pack
hierarchy content. In the example below, the Pack Hierarchy defined at Pack Item
SMC_PALLET_3 show one pack component SMC_CASE_3 that is assigned as the first level in
the pack hierarchy.
The next <ns0:Item ></ns0:Item > tags show pack Item SMC_CASE_3 and the Pack Component
assigned to this pack item. The <ns0:Item ></ns0:Item >, tags continue to complete the pack
hierarchy.
The last level in the pack hierarchy is pack item SMC_BASE_3, which does have assigned pack item
to it so this <ns0:Item ></ns0:Item >, tag set does not contain <ns0:Pack> tag set.
Pack Hierarchy XML Tags
Tags
Description

item record.
A collection of pack items in a hierarchy.
<ns0:Pack></ns0:Pack>
<ns14:PackComponent></ns14:PackComponent>
A component within a pack hierarchy

representing an item.
Pack Hierarchy XML File Format
<ns0:ItemNumber>SMC_PALLET_3</ns0:ItemNumber>
<ns0:ItemDescription>SMC_PALLET_3</ns0:ItemDescription>
38
<ns0:Pack>
<ns14:ItemNumber>SMC_PALLET_3</ns14:ItemNumber>
<ns14:CommonItemNumber>SMC_PALLET_3</ns14:CommonItemNumber>
<ns14:PackComponent>
<ns14:ComponentItemNumber>SMC_CASE_3</ns14:ComponentItemNumber>
<ns14:PackType>Case</ns14:PackType>
</ns14:PackComponent>
</ns0:Pack>
</ns0:Item>
<ns0:ItemNumber>SMC_CASE_3</ns0:ItemNumber>
<ns0:ItemDescription>SMC_CASE_3</ns0:ItemDescription>
<ns0:Pack>
<ns14:ItemNumber>SMC_CASE_3</ns14:ItemNumber>
<ns14:CommonItemNumber>SMC_CASE_3</ns14:CommonItemNumber>
<ns14:ComponentItemNumber>SMC_INNER_3</ns14:ComponentItemNumber>
<ns14:PackType>Pack or Inner Pack</ns14:PackType>
</ns0:Pack>
</ns0:Item>
<ns0:ItemNumber>SMC_INNER_3</ns0:ItemNumber>
<ns0:ItemDescription>SMC_INNER_3</ns0:ItemDescription>
39
<ns0:Pack>
<ns14:ItemNumber>SMC_INNER_3</ns14:ItemNumber>
<ns14:CommonItemNumber>SMC_INNER_3</ns14:CommonItemNumber>
<ns14:ComponentItemNumber>SMC_BASE_3</ns14:ComponentItemNumber>
<ns14:PackType>Base Unit or Each</ns14:PackType>
</ns0:Pack>
</ns0:Item>
<ns0:ItemNumber>SMC_BASE_3</ns0:ItemNumber>
<ns0:ItemDescription>SMC_BASE_3</ns0:ItemDescription>
</ns0:Item>
All Pack Items and Pack Hierarchy Selection
When the Pack Hierarchy option and the All Pack Items option are selected for items the
output will be a combination of the formats that were published when the options are selected
separately.
Item Class Entity

The second region in the Publication Options tab in the Edit Spoke Systems user interface allows the
user to select which item classes will be published. The Publish Item Class box must be checked to
allow the item classes to be published. In the Item Class Publication Criteria table, the Publish check
box is checked for each item class to be published. If the parent item class is selected, the child item
classes will be published as well. If the Root Item Class is checked, then all item classes will be
published. If a child item class is enabled for publication under the Root Item Class, the Root Item
Class will be selected when the child item class is selected.
The published data for Item Class contains the following child entities of Item Classes:
Transactional Attributes These are attributes that are defined for any item created in the
item class. The transaction attributes are used by downstream applications which will define
the storage and the values for the attributes. Transactional attributes appear in the Manage
Item Class UI only. The transactional attributes metadata is defined within the
<ns0:TransAttrMetaData> t
40
Attribute Groups Attribute groups are defined for the item class, so that any item created in
this item class will inherit these attribute groups. Attribute Groups use the Extensible
Flexfields infrastructure.
Attributes Attributes are define for each Attribute Group defined for the item class.
Attributes use the Extensible Flexfields infrastructure.
Item Class DFF Descriptive flexfields can be defined for the item class and any item
created using this item class will inherit the descriptive flexfields.
Item Class XML Tags
Tags
Description
<ItemClasses></ItemClasses>
<ns0:ItemClass xsi:type="ns0:ItemClass">
</ns0:ItemClass xsi:type="ns0:ItemClass">
<ns0:TransAttr></ns0:TransAttr>
One or more item class records.

item class.
<ns0:TransAttrMetaData>
</ns0:TransAttrMetaData>
<ns0:AttributeGroups></ns0:AttributeGroups>
<ns0:Attributes></ns0:Attributes>
<ns0:ItemClassDFF></ns0:ItemClassDFF
Transactional attributes are attributes

that are define in the system but used in
some other application. The value and
storage for this attributes is part the
other application.
The definition for the transactional
attribute.
Extensible Flexfields categories for the
item class (Attribute Groups)
Extensbile Flexfields context segments
for the item classs (Attributes)
Descriptive Flexfields for the item class.
Item Class XML File Format
<ItemClasses>
<ns0:ItemClass xsi:type="ns0:ItemClass">
<ns0:ItemClassId>100000011369001</ns0:ItemClassId>
<ns0:ItemClassCode>ROOT_ICC</ns0:ItemClassCode>
<ns0:ItemClassName>Root Item Class</ns0:ItemClassName>
<ns0:DefaultItemClassFlag>Y</ns0:DefaultItemClassFlag>
<ns0:DisableDate xsi:nil="true"/>
<ns0:NirReqd>N</ns0:NirReqd>
<ns0:NirChangeTypeId xsi:nil="true"/>
<ns0:VersionEnabledFlag>N</ns0:VersionEnabledFlag>
<ns0:ItemCreationAllowedFlag>Y</ns0:ItemCreationAllowedFlag>
<ns0:ParentItemClassId>-1</ns0:ParentItemClassId>
<ns0:ItemNumGenMethod>C</ns0:ItemNumGenMethod>
<ns0:ItemDescGenMethod>C</ns0:ItemDescGenMethod>
<ns0:ChangeOrderTypeId>300100052116610</ns0:ChangeOrderTypeId>
<ns0:Description>OATS_Child_TemplateMar24125254</ns0:Description>
<ns0:Attribute1 xsi:nil="true"/>
41
<ns0:AttributeCategory xsi:nil="true"/>
<ns0:AttributeDate1 xsi:nil="true"/>
<ns0:AttributeNumber1 xsi:nil="true"/>
<ns0:AttributeTimestamp1 xsi:nil="true"/>
<ns0:EnabledFlag>Y</ns0:EnabledFlag>
<ns0:TransAttr>
<ns0:BaseValueSetId>111</ns0:BaseValueSetId>
<ns0:CurrDBTime>2014-03-31T08:58:56.0-07:00</ns0:CurrDBTime>
<ns0:DataTypeCode>S</ns0:DataTypeCode>
<ns0:Description>Graceann</ns0:Description>
<ns0:DisplayName>Graceann</ns0:DisplayName>
<ns0:DisplayNameDisp xsi:nil="true"/>
<ns0:InternalName>Graceann</ns0:InternalName>
42
<ns0:LastUpdateLogin>F1C05C0456A74E79E0435050F00A5F91</ns0:LastUpdateLogin>
<ns0:StartDate>2014-03-31T08:58:56.0-07:00</ns0:StartDate>
<ns0:TransAttrId>300100054605283</ns0:TransAttrId>
<ns0:UomCode xsi:nil="true"/>
<ns0:Pk1Value>100000011369001</ns0:Pk1Value>
<ns0:TransAttrMetadataId>300100054605285</ns0:TransAttrMetadataId>
<ns0:TransAttrMetaData>
<ns22:TransAttrMetadataId>300100054605285</ns22:TransAttrMetadataId>
<ns22:TransAttrId>300100054605283</ns22:TransAttrId>
<ns22:DomainCode>25</ns22:DomainCode>
<ns22:ObjectName>EGO_CATALOG_GROUP</ns22:ObjectName>
<ns22:Pk1Value>100000011369001</ns22:Pk1Value>
<ns22:DateValue xsi:nil="true"/>
<ns22:HiddenFlag>N</ns22:HiddenFlag>
<ns22:InactiveFlag>N</ns22:InactiveFlag>
<ns22:LastUpdateLogin>F1C05C0456A74E79E0435050F00A5F91</ns22:LastUpdateLogin
>
<ns22:NumberValue xsi:nil="true"/>
<ns22:Pk2Value xsi:nil="true"/>
<ns22:ReadonlyFlag>N</ns22:ReadonlyFlag>
<ns22:RequiredFlag>N</ns22:RequiredFlag>
<ns22:TimestampValue xsi:nil="true"/>
<ns22:UomCode xsi:nil="true"/>
<ns22:ValueSetId>111</ns22:ValueSetId>
<ns22:VarcharValue xsi:nil="true"/>
<ns22:TransAttrDomainId>25</ns22:TransAttrDomainId>
<ns22:NewDomainCode xsi:nil="true"/>
<ns22:CharacterValueSet xsi:nil="true"/>
<ns22:NumberValueSet xsi:nil="true"/>
<ns22:DateValueSet xsi:nil="true"/>
<ns22:TimeValueSet xsi:nil="true"/>
<ns22:ValueSetValue xsi:nil="true"/>
<ns22:Valueset xsi:nil="true"/>
<ns22:DataTypeCode/>
<ns22:DateFilter xsi:nil="true"/>
<ns22:DepValueSet xsi:nil="true"/>
43
<ns22:TransAttrId1>300100054605283</ns22:TransAttrId1>
<ns22:InternalName>Graceann</ns22:InternalName>
<ns22:ItemClassCode>ROOT_ICC</ns22:ItemClassCode>
<ns22:DefaultValueId xsi:nil="true"/>
</ns0:TransAttrMetaData>
</ns0:TransAttr>
<ns0:AttributeGroups>
<ns0:ApplicationId>10010</ns0:ApplicationId>
<ns0:CExtAttribute1 xsi:nil="true"/>
<ns0:ContextCode>AGAHOLDTEST</ns0:ContextCode>
<ns0:Description>TO_NUMBER test data</ns0:Description>
<ns0:DescriptiveFlexfieldCode>EGO_ITEM_EFF</ns0:DescriptiveFlexfieldCode>
<ns0:LastUpdateLogin>F4896D440AF83BD8E0435050F00AD16F</ns0:LastUpdateLogin>
<ns0:MultirowFlag>N</ns0:MultirowFlag>
<ns0:Name>AGAHOLDTEST</ns0:Name>
<ns0:TranslatableFlag>N</ns0:TranslatableFlag>
<ns0:CategoryCode>ROOT_ICC</ns0:CategoryCode>
<ns0:ApplicationId1>10010</ns0:ApplicationId1>
<ns0:DescriptiveFlexfieldCode1>EGO_ITEM_EFF</ns0:DescriptiveFlexfieldCode1>
<ns0:ContextCode1>AGAHOLDTEST</ns0:ContextCode1>
<ns0:Attributes>
<ns0:ApplicationId>10010</ns0:ApplicationId>
<ns0:BIEnabledFlag>N</ns0:BIEnabledFlag>
<ns0:BIEqualizationTag xsi:nil="true"/>
<ns0:ColumnName>ATTRIBUTE_CHAR1</ns0:ColumnName>
<ns0:ContextCode>AGAHOLDTEST</ns0:ContextCode>
<ns0:DefaultType xsi:nil="true"/>
<ns0:DefaultValue xsi:nil="true"/>
<ns0:DerivationValue xsi:nil="true"/>
<ns0:Description>TO_NUMBER test</ns0:Description>
<ns0:DescriptiveFlexfieldCode>EGO_ITEM_EFF</ns0:DescriptiveFlexfieldCode>
<ns0:DisplayType>TEXT_BOX</ns0:DisplayType>
<ns0:DisplayWidth xsi:nil="true"/>
<ns0:LastUpdateLogin>F4896D440AF83BD8E0435050F00AD16F</ns0:LastUpdateLog
in>
<ns0:Name>AGNETCOTENT</ns0:Name>
<ns0:Prompt>AGNETCOTENT</ns0:Prompt>
<ns0:ReadOnlyFlag>N</ns0:ReadOnlyFlag>
<ns0:RequiredFlag>N</ns0:RequiredFlag>
44
<ns0:SegmentCode>AGNETCOTENT</ns0:SegmentCode>
<ns0:ShortPrompt>AGNETCOTENT</ns0:ShortPrompt>
<ns0:ValueSetId>115</ns0:ValueSetId>
</ns0:Attributes>
</ns0:AttributeGroups>
<ns0:ItemClassDFF>
<ns23:_global_segment1 xsi:nil="true"/>
<ns23:_IC_Glob_Seg_Char_1 xsi:nil="true"/>
<ns23:_IC_Glob_Seg_Char_2 xsi:nil="true"/>
<ns23:_IC_Glob_Seg_Num_1 xsi:nil="true"/>
<ns23:_IC_Glob_Seg_Date_1 xsi:nil="true"/>
<ns23:_IC_Glob_Seg_DtTm_1 xsi:nil="true"/>
<ns23:_zBIAItmClasDFF xsi:nil="true"/>
</ns0:ItemClassDFF>
</ns0:ItemClass>
</ItemClasses>
Catalog Entity
The third region, Catalog Entities controls which catalogs will be in the CATALOG_1.xml file. The
User will search and select Catalogs in the Catalog Publication Criteria table. In Figure 5, a catalog:
SMC_ITEMS has been selected to be published.
Figure 5 Catalog Publishing
The resulting ZIP file that is generated by the Publication System when Catalogs is checked looks like:
File: CATALOG_1.xml
<Catalogs>
<ns0:Catalogs xsi:type="ns0:Catalog">
</Catalogs>
45
Catalog XML Tags
The catalogs that are entered in the Catalog Publication Criteria will be published to a single XML file
Figure 6 contains the descriptions for the catalog tags.
Tags
<Ca<Catalogs><Catalogs>
<ns0:Catalog xsi:type="ns0:Catalog"></ns0:Catalog>
<ns0:ValidCategory></ns0:ValidCategory>
<ns0:Category></ns0:Category>
<ns0:CategoryDFF></ns0:CategoryDFF>
<ns0:CatalogDFF></ns0:CatalogDFF>
Description
One or more catalogs.
catalog. All of the remaining tags in this
table are contained within the catalog tags.
Multiple sets of these tags may exist in the
XML file.
Contains the relationship between the
Catalog (Category Set) and the Category. It
will also contain the Parent Category for
the specified Category. There will be one
Valid Category tag set for each Category in
the catalog.
category. Multiple sets of these tags may
exist in the XML file.
This tag represents the descriptive
flexfields for the category. This tag is
contained within the category tag set.
This tag represents the descriptive
flexfields for the catalog
Figure 6 Catalog XML Tags

Catalog XML File Format
The following is an example of the XML output for a catalog, a single element is shown for each tag
set listed in Figure 6.
<Catalogs>
<ns0:Catalog xsi:type="ns0:Catalog">
<ns0:Attribute1>A</ns0:Attribute1>
<ns0:Attribute10>1234</ns0:Attribute10>
<ns0:Attribute4>C</ns0:Attribute4>
<ns0:Attribute5>1</ns0:Attribute5>
<ns0:CatalogCode>SMC_ITEMS</ns0:CatalogCode>
<ns0:CatalogContentCode>LEAF_ITEMS</ns0:CatalogContentCode>
<ns0:CategorySetId>300100077190891</ns0:CategorySetId>
46
<ns0:CategorySetName>SMC_ITEMS</ns0:CategorySetName>
<ns0:ControlLevel>1</ns0:ControlLevel>
<ns0:DefaultCategoryId xsi:nil="true"/>
<ns0:Description>SMC_ITEMS</ns0:Description>
<ns0:HierarchyEnabled>Y</ns0:HierarchyEnabled>
<ns0:LastUpdateLogin>F5B08695B4A07390E0435050F00A33B8</ns0:LastUpdateLogin>
<ns0:MultItemCatAssignFlag>N</ns0:MultItemCatAssignFlag>
<ns0:RaiseAltCatHierChgEvent xsi:nil="true"/>
<ns0:RaiseCatalogCatChgEvent xsi:nil="true"/>
<ns0:RaiseItemCatAssignEvent xsi:nil="true"/>
<ns0:SharingContentCode xsi:nil="true"/>
<ns0:SourceCategorySetId xsi:nil="true"/>
<ns0:StructureInstanceNumber>2</ns0:StructureInstanceNumber>
<ns0:ValidateFlag>Y</ns0:ValidateFlag>
<ns0:ValidCategory>
<ns25:CategoryId>300100077190892</ns25:CategoryId>
<ns25:ParentCategoryId>100000018724020</ns25:ParentCategoryId>
<ns25:ReferenceCategorySetId xsi:nil="true"/>
</ns0:ValidCategory>
<ns0:Category>
47
<ns0:CatalogHierFlag xsi:nil="true"/>
<ns0:CatalogValidateFlag xsi:nil="true"/>
<ns0:CategoryCode xsi:nil="true"/>
<ns0:CategoryContentCode>MIXED</ns0:CategoryContentCode>
<ns0:CategoryName>SMC_Laptops</ns0:CategoryName>
<ns0:CategorySetId xsi:nil="true"/>
<ns0:Description>SMC_Laptops</ns0:Description>
<ns0:EndDateActive xsi:nil="true"/>
<ns0:ParentCategoryId xsi:nil="true"/>
<ns0:Segment1>SMC_Laptops</ns0:Segment1>
<ns0:Segment10 xsi:nil="true"/>
48
<ns0:StartDateActive>2014-03-28T12:47:32.0-07:00</ns0:StartDateActive>
<ns0:StructureInstanceNumber>2</ns0:StructureInstanceNumber>
<ns0:SummaryFlag>Y</ns0:SummaryFlag>
<ns0:SupplierEnabledFlag>Y</ns0:SupplierEnabledFlag>
<ns0:WebStatus>N</ns0:WebStatus>
<ns0:autoAssignFlag xsi:nil="true"/>
<ns0:CategorySetId1>300100077190891</ns0:CategorySetId1>
<ns0:CategoryId1>300100077190892</ns0:CategoryId1>
<ns0:ObjectVersionNumber1>1</ns0:ObjectVersionNumber1>
<ns0:CategoryDFF>
<ns24:_CATY_Glob_Seg_Char_1 xsi:nil="true"/>
<ns24:_zBIACategoryDFF xsi:nil="true"/>
</ns0:CategoryDFF>
</ns0:Category>
<ns0:CatalogDFF>
<ns26:_global_segment1>A</ns26:_global_segment1>
<ns26:_global_segment5>1</ns26:_global_segment5>
<ns26:_CATG_Glob_Seg_Char_1>C</ns26:_CATG_Glob_Seg_Char_1>
<ns26:_zBIACatalogDFF>1234</ns26:_zBIACatalogDFF>
</ns0:CatalogDFF>
</ns0:Catalog>
</Catalogs>
Controlling the Payload Output File Size

You can use the profile options provided for publication process:
EGI_PUBLICATION_ITEMS_PER_PAYLOAD - Number of Items per Payload for
Publication
49
This profile option determines the number of items to be used per payload in the publication
concurrent program.
EGI_PUBLICATION_NUMBER_OF_PAYLOADS - Number of Parallel Payloads for
Publication
This profile option determines the number of parallel payloads to be used in the publication
concurrent program
The profiles can be access through the Oracle Functional Setup Manager through the following
steps:
1. Launch the Setup and Maintenance work area using the links in the Navigator
2. In the Overview page, within the All Task tab, search for the task: Manage Administrator
Profile Values
3. Click the Got to Task icon to launch this page

4. In the Search region, enter the Profile Option Codes listed above for the
publication profile option.
5. Select one of the publication profile option in the Search Results table.
6. Edit the Profile Value field.
7. Click the page level Save and Close button.
Figure 25 Changing Profile Option Value
Summary
Items and their child entities, item class metadata and catalogs and their category hierarchies can be
published periodically to a spoke system. The publication is via backend scheduled process job. You
have the ability to define the publication criteria to filter the items, item classes and catalogs for each
spoke system and set up a publication schedule.
50
XSDs for Publication

The XSD for each item, catalog and item class entities are provided in this section for the entities that
have static definition. Since the some of the entities can be extended, the XSD will change based on
how the entity is setup. For example the parameters selection for item publication publishes entities
such as extensible flexfields that can be added to the base item definition, so the XSD for the
parameters for items changes based on the item configuration.
Item XSD Selection

The XSD for the item entity contains additional sub-entities and the content is dynamic depending on
the composition of the item and what is selected in the Manage Spoke Systems, Publication Option
tab. Each of the selection is shown below:
The diagram below shows the relationship of entities in a consolidated view of the item entity (All
item selection options are enabled). Each of the next sections contains XSD information based on the
Publication Options for Items.
Item.xsd
ItemAttachment.xsd
j_ItemEffCategory.xsd
ItemEFF[Attribute Group]PrivateVO.xsd
ItemRevision.xsd
ItemRevisionTranslation.xsd
ItemRevisionDFF.xsd
ItemRevisionEffCategory.xsd
ItemCategory.xsd
ItemCrossReference.xsd
ItemRelationTranslation.xsd
ItemRelationShipsDFF.xsd
RelatedItem.xsd
CompetitorItemXref.xsd
CustomerItemXref.xsd
MfgPartNumber.xsd
Structure.xsd
StuctureDFF.xsd
Component.xsd
ComponentDFF.xsd
Pack.xsd
PackComponent.xsd
ItemSupplierAssociation.xsd
51
j_ItemSupplierAssociation.xsd
GTINCrossReference.xsd
SysItemXref.xsd
SupplierItemXref.xsd
ItemDFF.xsd
The corresponding tag sets in the XML output are:
XSD File
ItemAttachment.xsd
j_ItemEffCategory.xsd
ItemRevision.xsd
ItemRevisionDFF.xsd
ItemRevisionEffCategory.xsd
ItemCategory.xsd
ItemRelationTranslation
ItemRelationShipsDFF
RelatedItem.xsd
TradingPartnerItemCrossReference.xsd
Structure.xsd
StructureDFF.xsd
Component.xsd
ComponentDFF.xsd
Pack.xsd
PackComponent.xsd
ItemSupplierAssociation.xsd
J_RevisedItemSupplierAssociation.xsd
SystemCrossReference.xsd
ItemDFF.xsd
XML Tags
<ItemAttachment>
<j_EffCategory>
<ItemRevision>
<ItemRevisionTranslation>
<ItemRevisionDFF>
<ItemRevisionEffCategory>
<ItemCategory>
<ItemCrossReference>
<ItemRelationTranslation>
<ItemRelationShipDFF>
<RelatedItem>
<MfgPartNumber>
<CustomerItemXref>
<CompetitorItemXref>
<SupplierItemXref>
<Structure>
<StructureDFF>
<Component>
<ComponentDFF>
<Pack>
<PackComponent>
<ItemSupplierAssocation>
<ItemSupplierEffCategory>
<GTINXref>
<SysItemXref>
Item Attributes Selection XSDs
The items attribute selection provides item Operational Attributes, Item Extensible Flexfields, Item
Revision, and Item Descriptive Flexfields. The XSD relationship hierarchy is displayed below:
Item.xsd
ItemEFFCategory.xsd
52
ItemEFF[Attribute Group]PrivateVO
ItemRevision.xsd
ItemRevisionDFF.xsd
ItemDFF.xsd
Extensible Flexfields
Extensible Flexfields are available for three entities: Item, Item Revision and Item Supplier Site
Organizations. The content of the XML file will be variable based on what extensible flexfields are
define for the entities. The XSD provided will define the attributes for the extensible flexfields that are
considered standard, in that they will always be present in the XML file.
The Item Extensible Flexfields are setup at the Item Class Level, where the Extensible Flexfields for
Item Revisions and Item Supplier Site Organizations entities are setup in the Manage Item Attributes
Groups and Attribute setup user interface.
Item EFF
Item Extensible Flexfields content that is published in the XML file will depend on the attribute
groups and attributes that are define for the Item Class for the item. If no extensible flexfields are
defined for the item, only the ItemEFFCategory tags set will be part of the XML output and will use
the ItemEFFCategory.xsd..
Figure 7 shows an example of the Item user interface and relationship to the terms used for
extensible flexfields. For example; the category in extensible flexfields refers to the Item Class for the
item. The Context refers to the Attribute Group assigned to the Item Class and Context Sensitive
Segments refers to the attribute assigned to the Attribute Group.
53
Figure 7 EFF Displayed in UI
The item extensible flexfields are published using two tag sets, the first represents the extensible
flexfield category (which is the Item Class) and the attributes that identify the item the extensible
flexfields are define for. The j_ItemEffCategory.xsd file represents the item the extensible flexfield is
assigned to. Each Attribute Group that is defined for the item will be published in a separate tag set
labeled <ItemEFFResistor_5FAGPrivateVO></ItemEFFResistor_5FAGPrivateVO>. If more than one
attribute group is defined for the item, then the tag listed above will be repeated with the attribute
group name replacing the string: Resistor_5FAG.
The <ItemEFF[name]PrivateVO> tag content is generated by the publication process, but does
contain a common set of tags for each attribute groups published, as shown below:
<ns3:LastUpdateLogin>B2D3B98D8E741106E040F00A50161269</ns3:LastUpdateLogin>
<ns3:CategoryCode>EFF_NT_SR_MR_NV_ALL_LEVEL_ALL_TYPES_2</ns3:CategoryCode>
The attribute group is published with the <ContextCode> tags. The remainder of the published
content is all of the attributes that are defined for the attribute group.
54
Item Revision Extensible Flexfields
The Item Revision Extensible Flefield are published using the tags:
</ItemRevisionEffCategory><ItemRevisionEffCategory> and
<ItemRevisionEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO></ItemRevisio
nEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO>. The first tag is defined by
file j_ItemRevisionVersion.xsd.
The second tag sets is variable depending on what extensible flexfields are set for the item revision entity.
The static portion of the
<ItemRevisionEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO> tag set is as
follows:
Item Supplier Site Organization Flexfields
The Item Supplier Site Organization Extensible Flefield are published using the tags:
</ItemSupplierEffCategory><ItemSupplierEffCategory> and
<ItemSupplierEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO></ItemSupplie
rEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO>. The first tag set is defined
by file: j_RevisedItemSupplierAssociation.xsd.
The second tag sets is variable depending on what extensible flexfields are set for the item revision entity.
The static portion of the
<ItemRevisionEFFBAG_5FNT_5FSR_5FNV_5FRL_5FALL_5FTYPES_5F2PrivateVO> tag set is as
follows:
55
Attachment: URL Selection XSDs
The ItemAttachment.xsd file used to describe the XML output for the Attachments: URL selection
when publishing Items. If this selection is the only selection chosen, a set of item elements are also
published for identification of the item the attachments are assigned to. The ItemAttachment.xsd file
describes the XML content within the <ns0:ItemAttachment> tag set. The common elements that
also published with the attachment tags are:
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<LifecyclePhaseValue>
<UserItemTypeValue>
The definitions of these elements are:
<xsd:sequence>
<xsd:element name="OrganizationCode" type="xsd:string" minOccurs="0" nillable="true"/>
<xsd:element name="ItemNumber" type="xsd:string" minOccurs="0" nillable="true"/>
<xsd:element name="ItemDescription" type="xsd:string" minOccurs="0"/>
xsd:element name="ItemStatusValue" type="xsd:string" minOccurs="0" nillable="true"/>
<xsd:element name="LifecyclePhaseValue" type="xsd:string" minOccurs="0" nillable="true"/>
<xsd:element name="UserItemTypeValue" type="xsd:string" minOccurs="0" nillable="true"/>
<xsd:element name="itemAttachment" type="ns1:ItemAttachment" minOccurs="0" sdoXML:dataType=
sdo:DataObject
</xsd:sequence>
Association: Supplier Site Organizations Selection XSDs
The ItemSupplierAssociation.xsd file used to describe the XML output for the Item Supplier
Association: selection when publishing Items. If this selection is the only selection chosen, a set of
item elements are also published for identification of the item the attachments are assigned to. The
ItemCategoryAssignments.xsd file describes the XML content within the
<ns0:ItemSupplierAssociation> tag set.
The XSD for the Item Supplier Association entity contains additional sub-entities. The diagram below
shows the relationship of entities:
ItemSupplierAssocication.xsd
ItemSupplierEffCategory.xsd
The common elements that also published with the attachment tags are:
<OrganizationCode>
<ItemNumber>
56
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
<xsd:element name="itemSupplierAssociation" type="ns1:ItemSupplierAssociation" minOccurs="0"
sdoXML:dataType= sdo:DataObject
</xsd:sequence>
Item Category Assignments Selection XSDs-
The ItemCategory.xsd file used to describe the XML output for the Item Category Assignment:
selection when publishing Items. If this selection is the only selection chosen, a set of item elements
are also published for identification of the item the attachments are assigned to. The
ItemCategoryAssignments.xsd file describes the XML content within the <ns0:ItemCategory> tag set.
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
<xsd:element name="itemCategory" type="ns1:ItemCategory" minOccurs="0" sdoXML:dataType=
sdo:DataObject
</xsd:sequence>
Pack Hierarchy Selection XSDs
The Pack.xsd file used to describe the XML output for the Pack Hierarchy selection when publishing
Item Pack Hierarchies. If this selection is the only selection chosen, a set of item elements are also
published for identification of the item the attachments are assigned to. The Pack.xsd file describes
the XML content within the <ns0:Pack> tag set.
57
The XSD for the Pack Hierarchy entity contains additional sub-entities. The diagram below shows the
relationship of entities:
Pack.xsd
PackComponent.xsd
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
<xsd:element name="pack" type="ns1:Pack" minOccurs="0" sdoXML:dataType= sdo:DataObject
</xsd:sequence>
Item Relationships: GTIN Selection XSDs
The GTINCrossReference.xsd file used to describe the XML output for the Item Relationships:
GTIN selection when publishing GTIN Cross References. If this selection is the only selection
chosen, a set of item elements are also published for identification of the item the attachments are
assigned to. The GTINCrossReference.xsd file describes the XML content within the
<ns0:GTINXef> tag set.
The XSD for the GTIN Cross Reference entity contains additional sub-entities. The diagram below
shows the relationship of entities:
ItemRelationshipTranslation.xsd
ItemRelationshipsDFF.xsd
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
58

<xsd:sequence>
<xsd:element name="gTINCrossReference" type="ns1:GTINCrossReference" minOccurs="0" sdoXML:dataType=
sdo:DataObject
</xsd:sequence>
Item Relationships: Trading Partner Items Selection XSDs
The Item Relationships: Trading Partner Items selection will publish data for each of the Trading
Partner type: Competitor, Customer, Manufacturer and Supplier. The
TradingPartnerItemCrossReference.xsd is used for each of the Trading Partner Item types.
The XSD for the Trading Partner Item Cross Reference entity contains additional sub-entities. The
diagram below shows the relationship of entities:
TradingPartnerItemCrossReference.xsd
The XML output file will contain multiple tag sets one for each of the Trading Partner Item types:
<ns0:CustomerItemXref> tag set is used for the Customer Item type
<ns0:CompetitorItemXref> tag set is used for the Competitor Item type
<ns0:MfgPartNumber> tag set is used for the Manufacturer type
<ns0:SupplierItemXref> tag set is used for the Supplier Item type
If the Item Relationship: Trading Partner Items is the only Item entity selected, then a common set of
attributes describing the item the Trading Partner Items are associated with are used. The common
elements that also published with the attachment tags are:
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
59

<xsd:element name="tradingPartnerItemCrossReference" type="ns1:TradingPartnerCrossReference" minOccurs="0"
</xsd:sequence>
Item Relationships: Related Items Selection XSDs
The RelatedItem.xsd file used to describe the XML output for the Item Relationships: RelateItems
selection when publishing Item Relationship: Related Item. If this selection is the only selection
chosen, a set of item elements are also published for identification of the item the attachments are
assigned to. The RelatedItem.xsd file describes the XML content within the <ns0:RelatedItem> tag
set.
RelatedItem.xsd
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
<xsd:element name="tradingPartnerItemCrossReference" type="ns1:TradingPartnerCrossReference" minOccurs="0"
</xsd:sequence>
Item Relationships: Cross References Selection XSDs
The ItemCrossReference.xsd file used to describe the XML output for the Item Relationships: Cross
References selection when publishing Item Relationship Cross References. If this selection is the only
selection chosen, a set of item elements are also published for identification of the item the
attachments are assigned to. The ItemCrossReference.xsd file describes the XML content within the
<ns0:ItemCrossReference> tag set.
60
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
<xsd:element name=itemCrossReference" type="ns1:ItemCrossReference" minOccurs="0" sdoXML:dataType=
sdo:DataObject
</xsd:sequence>
Structures: All Selection XSDs
The Structure.xsd file used to describe the XML output for the Structures: All selection when
publishing Structure types. If this selection is the only selection chosen, a set of item elements are also
published for identification of the item the attachments are assigned to. The Structure.xsd file
describes the XML content within the <ns0:Structure> tag set.
Stucture.xsd
StructureDFF.xsd
Component.xsd
ComponentDFF.xsd
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
61
<xsd:sequence>
<xsd:element name=structure" type="ns1:Structure" minOccurs="0" sdoXML:dataType= sdo:DataObject
</xsd:sequence>
Structures: Primary Selection XSDs
The Structure.xsd file used to describe the XML output for the Structures: Primary selection when
publishing of the Structure name=Primary. If this selection is the only selection chosen, a set of item
elements are also published for identification of the item the attachments are assigned to. The
Structure.xsd file describes the XML content within the <ns0:Structure> tag set.
Stucture.xsd
StructureDFF.xsd
Component.xsd
ComponentDFF.xsd
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
</xsd:sequence>
All Pack Items Selection XSDs
The PackIem.xsd file used to describe the XML output for the All Pack Items selection when
publishing of all the items in the Pack if there are changes to any pack item in the pack. If this
selection is the only selection chosen, a set of item elements are also published for identification of the
item the attachments are assigned to.
62
<OrganizationCode>
<ItemNumber>
<ItemDescription>
<ItemStatusValue>
<UserItemTypeValue>
<xsd:sequence>
</xsd:sequence>
Item Class XSD

The XSD for the item class entity contains additional sub-entities. The diagram below shows the
ItemClass.xsd
TransactionalAttribute.xsd Transactional Attributes
Attribute Groups.xsd Extensible Flexfields Contexts (Attribute Groups)
Attributes.xsd Extensible Flexfields Segments (Attributes)
ItemClassDFF.xsd
The XSDs for publication are provided in the sample data provided.
Catalog XSD
The XSD for the catalog entity contains additional sub-entities. The diagram below shows the
Catalog.xsd
Category.xsd
CategoryDFF.xsd
ValidCategory.xsd Catalog to category Associations
CatalogDFF.xsd Catalog Descriptive Flexfields
The XSDs for publication are provided in the sample data provided.
63
Frequently Asked Questions

Which product license is required for the publication feature?
You need to license Fusion Product Hub to be able to use Publication features.
Which objects are supported for publication?
Objects that can be published to external spoke systems are Items (including selected entities), Item
Classes, and Catalogs.
Can I create a spoke system in Product Hub?
No, you cannot create a new spoke system using Product Hub. Spoke systems are created in Trading
Community Services task.
What if I do not select any objects on the spoke system to publish?
If you do not select any objects on the spoke system, you will not be able to define the publication
options and no data will be published to the spoke system.
Which item entities are supported for publication?
Item Entities that are supported for publication are:

Attributes
Attachments: URL
Associations: Supplier Site Organization
Pack Hierarchies
Item Relationships: GTIN
Item Relationships: Related Items
Item Relationships: Trading Partner Items
Item Relationships: Cross References
Structures: All
Structures: Primary
All Pack Items
Will all items in Product Hub get published?
Items that have been updated since the last publication date or the criteria date that meets the
publication criteria for the spoke system will get published.
How is it determined which items will get published?
Which items will get published is determined by the selection rules defined on the publication options
for a spoke system. These selection rules can be based on Organization, Organization Hierarchy,
Catalog and Item Class.
64
Can items for child orgs be selected and published?
No, only Master Organizations are available to filter the items. Hence items from child orgs cannot be
published. Based on the selected orgs Item (Master and/or Child Item) with its attributes will be
published. We do not publish the Org Assignments.
If a catalog is selected for publication, will the item category assignments for that catalog be published?
No. If a catalog is selected for publication in the Catalog Publication Criteria region, the item category
assignments will not be published. In order to publish item category assignments, you need to select
Item Category Assignments in the Item Entities region.
What item class metadata will get published?
Item Class metadata that will get published is:

Item class definition (Name, Description and other header level fields/metadata)
Associated attribute groups/attributes (operational and extended flex fields)
Item Class Descriptive Flexfields
Can I select the categories within the catalog for publication?
No, you cannot select individual categories in a catalog to publish. If a catalog is selected, the whole
category hierarchy under it will get published.
Where is the publication schedule defined for the spoke system?
You can setup the publication schedule in the Parameters pop-up for the Product Hub Publication
Job
If no schedule is defined, how can I publish objects?
Setting up a schedule is optional. You can publish by entering the parameters on the Product Hub
Publication Job and submitting the request.
What is the scheduled process used to publish objects to spoke system?
The scheduled process is called Product Hub Publication Process.

The parameters required for scheduling an ESS process are:
TABLE 5. SCHEDULED PROCESS PARAMETERS
*SCHEDULED PROCESS
VALUE
MEANING
Spoke System
Choice-list
Name of the spoke system
Publish Items
Yes/No
Indicates if items will get published
Publish Item Classes
Yes/No
Indicates if item classes will get published
Publish Catalogs
Yes/No
Indicates if catalogs will get published.
Criteria Date
Date picker
Over writes the Last Publication Date.
PARAMETERS
65
Folder Location
Text field
UCM folder location to save the output xml file
Is Criteria Date enforced for spoke system publication?
First time publication Yes, Criteria Date is required. This was primarily done to minimize
the chances of an arbitrarily large payload from being mistakenly generated.
Subsequent publication Optional. If not populated, the Last Publication Date is used. If
populated, Criteria Date always takes precedence.
Does Criteria Date apply only to Items or all objects, i.e. Item Classes, Catalogs?
Criteria Date applies to all objects: Items, Item Classes and Catalogs.
How do we handle chunking of data so that payload size does not exceed what the middleware can handle?
You can use the profile options provided for publication process:
EGI_PUBLICATION_ITEMS_PER_PAYLOAD - Number of Items per Payload for Publication
This profile option determines the number of items to be used per payload in the publication
concurrent program.
EGI_PUBLICATION_NUMBER_OF_PAYLOADS - Number of Parallel Payloads for Publication
This profile option determines the number of parallel payloads to be used in the publication
concurrent program
Where can I add values for the profile options?
The profile options values can be defined at Manage Administrator Profile Values task in FSM.
What is the format of the payload file?
The format of the payload file is xml.

Where can I access the payload file?
For on premise customers only, the xml file can be accessed in Enterprise Manager. Alternatively if
you have opted to save the file in UCM, it can be accessed in the respective UCM folder location.
66
Fusion Product Hub Publication Process
Copyright 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
August 2012
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
Author: Priyanka Ashar
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
Oracle Corporation
means, electronic or mechanical, for any purpose, without our prior written permission.
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
Worldwide Inquiries:
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
Phone: +1.650.506.7000
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open
Fax: +1.650.506.7200
Company, Ltd. 0112
oracle.com

Publication XML File Format Whitepaper Fusion Release 9 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Publication XML File Format Whitepaper Fusion Release 9 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Publication Framework

An Oracle White Paper

Oracle Fusion Product Hub Publication

Executive Overview ........................................................................... 1

Item Class Entity.......................................................................... 40

XSDs for Publication........................................................................ 51

Item Class XSD ........................................................................... 63

Terms and Definitions

Product Information Management

An organizing unit in the internal or external structure of your enterprise.

Short code for Oracle Fusion Product Hub

Item represents a product in a given organization

Relationship between two Items or Relationship between an Item and GTIN,

Global Trade Item Number

Unified Content Manager

Application Programming Interface

Functional Set up Manager

Implicit Publication Explained

Profile Options: Define profile options

Customization: Customize SOA composite to publish to the external spoke system

Figure1: Publication Flow

The data that gets published is determined by

For Catalog1, if Category1 is updated from last publication date,

XML Data Output File Format

Figure 1 XML Data Output File

Figure 2 Publication Options Tab

Table 1 Item Entities

Item Relationships: GTIN

Item Relationships: Trading Partner Items

Item Relationships: Related Items

In the case of publishing large numbers of items, a profile option

Figure 3 Entity Order of Publication

Figure 4 Entity Order of Publication (Cont)

Item Attribute XML Tags

This tag represents the content for a single

EFF Multi-row Attribute Group Column

Item Attribute XML File Format

<ns0:ItemRevisionEffCategory> - corresponds to the Item Class

This tag represents the content for a single

Item Attachment XML File Format

This tag represents the content for a single

Item Supplier Site Organization Association XML File Format

Item Category Assignments Selection

This tag represents the content for a single

Item Category Assignments XML File Format

This tag represents the content for a single

Translated Content for Item Relationship:

Item Relationships: GTIN XML File Format

Item Relationships: Trading Partner Items Selection

This tag represents the content for a single

Item Relationships: Trading Partner Items: Customers

Item Relationships: Trading Partner Items: Suppliers

Item Relationships: Trading Partner Items: Manufacturers

Item Relationships: Related Items Selection

This tag represents the content for a single

Descriptive Flexfields for Item

Item Relationships: Related Items XML File Format

Item Relationships: Cross-references Selection

This tag represents the content for a single

<ns0: ItemCrossReference >

Descriptive Flexfields for Item

Item Relationships: Cross-references XML File Format

Structures: All Selection