EBS 122 Cum RCD MDM

ORACLE E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Master Data Management

Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.2.13)
Prepared by Oracle E-Business Suite Product Development
Last Updated: November 17, 2023
Copyright © 2011, 2023, Oracle and/or its affiliates.

Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Master Data Management 3
3.1. Oracle Customer Hub (CDH) 3
3.1.1. Overview 3
3.1.2. Release 12.1.1 3
3.1.2.1. Threshold Values for Search Match Rules in Terms of Percentage 3
3.1.2.2. View Operating Unit Name while Submitting Customer Merge Request 3
3.1.2.3. Improved Performance of Create Merge Batch Process 4
3.1.2.4. Improved Performance of System Duplicate Identification Tab 4
3.1.2.5. New “All” Option in Status LOV of Customer Search UI & Account Layer UI 4
3.1.2.6. View Status, Start & End Dates for a Contact Relationship in De-dupe UI 5
3.1.2.7. Web Services for TCA Business Objects and DQM Engine 5
3.1.2.8. Access Third Party Address Validation Adapter across Firewall 6
3.1.3. Release 12.1.2 6
3.1.3.1. Merge Web Services 6
3.1.3.2. DQ Enable Web Services 7
3.1.3.3. View History of Organization and Person Profiles 7
3.1.3.4. Support Zip+4 in All Address Validation Flows for US Addresses 7
3.1.3.5. Time Zone for Resource Group 7
3.1.4. Release 12.2 8
3.1.4.1. Spatial Data Integration 8
3.1.4.2. Real-Time Address Validation 8
3.1.4.3. Enhancement to Customer Import 8
3.1.4.4. Source System References 9
3.1.4.5. Record History 9
3.1.4.6. Merge Web Service 9
3.1.4.7. Industrial Classification Codes for 2012 9
3.1.5. Release 12.2.4 10
3.1.5.1. Additional Search Criteria for Account Site Addresses 10
3.1.6. Release 12.2.5 10
3.1.6.1. Additional Search Criteria for Party Site Addresses 10
3.1.6.2. Customer Merge using OAF UI 10
3.1.7. Release 12.2.6 11
3.1.7.1. Google Maps replaces Yahoo Maps 11
3.1.7.2. Enhancements to Customer Merge 11
3.1.8. Release 12.2.7 11
3.1.8.1. Enhancements to Party Merge 11
3.1.8.2. Merge Extended Attributes during Party Merge 11
3.1.9. Release 12.2.8 11
3.1.9.1. Dun and Bradstreet (D&B) integration Enhancement 11
3.1.10. Release 12.2.9 11
3.1.10.1. Support the ability to allow only one shipment per order 11
3.2. Oracle Product Hub 12
3.2.1. Overview 12
3.2.2. Release 12.1.1 12
3.2.2.1. Extensible Attribute Framework 12
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.2.2.2. Style – SKU Items 12
3.2.2.3. Item Organization Relationships 13
3.2.2.4. Item Supplier and Item Supplier Site Relationships 13
3.2.2.5. Item Supplier Site Organization Relationships 14
3.2.2.6. Pack Management 15
3.2.2.7. New Item Definition and Approval 15
3.2.2.8. Advanced Search 16
3.2.2.9. Excel-based Import and Export 17
3.2.2.10. Mass Maintenance of Item Supplier and Item Supplier Site Relationships 18
3.2.2.11. Mass Maintenance of Item Supplier Site Organization Relationships 18
3.2.2.12. Enhancements to Release 12 Mass Maintenance 19
3.2.2.13. Catalogs 19
3.2.2.14. Rules 20
3.2.2.15. Import Workbench 22
3.2.2.16. Change Management 23
3.2.2.17. Security 23
3.2.2.18. Publication 24
3.2.2.19. Purge 24
3.2.2.20. Inbound Global Data Synchronization 25
3.2.3. Release 12.1.2 26
3.2.3.1. Transaction Attributes 26
3.2.3.2. Metadata Versioning 27
3.2.3.3. Product Structure for Item Catalog Category 28
3.2.3.4. Pre-seeded Libraries 29
3.2.3.5. Context-specific Information 29
3.2.3.6. Publication Framework 30
3.2.3.7. Automatic Import of Un-confirmed Items 32
3.2.3.8. Rules Framework Extensibility 32
3.2.4. Release 12.1.3 33
3.2.4.1. PIM to PIM Sync – APIs for Importing ICC and Value Set Metadata 33
3.2.4.2. Support for Images in BI Publisher (XML Publisher) Reports 33
3.2.4.3. Integration with Stellant/Oracle Universal Content Management (Oracle UCM) 34
3.2.4.4. Item Associations Enhancements 34
3.2.4.5. Lifecycle Phase Enhancement 34
3.2.4.6. Multiple Price List enhancement- Telco Enhancement 34
3.2.5. Release 12.2 35
3.2.5.1. PIM to PIM Sync – Publish/Synchronize Metadata 35
3.2.5.2. Rules Framework Enhancements 35
3.2.5.3. Public Item Search API 35
3.2.5.4. Publish Workbench 36
3.2.5.5. On-Demand Rule Set Execution 36
3.2.6. Release 12.2.4 36
3.2.6.1. Support Time Picker within Date Picker 36
3.2.6.2. Support Modal Popup Windows 37
3.2.6.3. Support Value Set Security 37
3.2.7. Release 12.2.5 38
3.2.7.1. Increase in Item Revision Sequence 38
3.2.7.2. New Modal Popup Windows Uptake 38
3.2.7.3. Enabling NULL value search in advanced Item Search 38
3.2.7.4. Excel Support for Item Relationships 39
3.2.7.5. Serial Tagging Changes 39
3.2.8. Release 12.2.6 39
3.2.8.1. Importing Product Structure/BOM Component Attribute Override Values 39
3.2.8.2. New Product Workbench Structure Search Filter Default Values 39
3.2.8.3. Enabling Product Workbench JavaServer Page (JSP) 39
3.2.8.4. Supporting Material Classification Tagging 39
3.2.9. Release 12.2.7 39
3.2.9.1. Multi-Row Attribute Advanced Search Results 40
3.2.9.2. Filtering Multi-Row Attribute Values in an Item Page 40
3.2.10. Release 12.2.8 40
3.2.10.1. Item Global Flexfield 40
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.2.10.2. Outsource Manufacturing for Process Manufacturing Items 40
3.2.11. Release 12.2.9 40
3.2.11.1. Ability to un-assign item from child organization(s) 40
3.2.11.2. Support to update Item UOM 40
3.2.11.3. Support to retain ECO information for BOM mass changes 40
3.2.12. Release 12.2.10 41
3.2.12.1. View/Edit/Upload multiple multi-row attribute groups in excel sheet 41
3.2.12.2. Allow User Defined Attributes with UOM to have LOV values 41
3.2.12.3. Support Translatable UDA length up to 4000 bytes 41
3.2.12.4. Item Create and Update API available for Inventory IREP users 41
3.2.13. Release 12.2.11 41
3.2.13.1. API / Interface made available for updating Customer Item, Customer Item Cross reference and loading
Manufacturer Part Number 41
3.2.13.2. Display of Item Name, Description, Long description, and ICC Name in Item Search Results Page without
trimming spaces. 41
3.2.13.3. Public API for transferring engineering items to Manufacturing 41
3.2.14. Release 12.2.12 41
3.2.14.1. Item Business Events Extended to Inventory Users 41
3.2.15. Release 12.2.13 42
3.2.15.1. Associate Item Catalog Category (ICC) while Creating Items using Excel Import 42
3.2.15.2. Support Status Change for an Item across Multiple Organizations 42
3.3. Oracle Mobile Product Information for Oracle E-Business Suite 42
3.3.1. Discontinuation Notice 42
3.3.2. Overview 42
3.3.3. Mobile Release 2.1 – Client Version 1.1.0 43
3.3.3.1. Mobile Foundation Updates 43
3.3.3.2. Accessibility Improvements 43
3.3.4.1. Android Support 43
3.3.4.1. Mobile Foundation Release 3.0 Updates 43
3.3.5.1. Product Information and ERP Change Order Workflows 43
3.3.5.2. Item Attachment Support 44
3.3.5.3. Ability to add or remove an Item from the Favorite List 44
3.3.5.4. Translation Support 44
3.3.6.1. View ICC in Overview page 44
3.3.6.2. Enhanced data security check in Overview page Metrics tab 44
3.3.6.3. Enhanced on hand quantity in Overview and Detail pages 44
3.3.6.4. Hid attachment link in Overview page when there is no attachment 45
3.3.8.1. Ability to upload image for item in overview page and attachment list 45
3.3.8.2. Ability to assign mobile specific role to non-EGO responsibility 45
3.4. Oracle Site Hub 46
3.4.1. Overview 46
3.4.2. Release 12.1.1 46
3.4.2.1. Site Creation and Maintenance 46
3.4.2.2. Site Attributes 47
3.4.2.3. Simple and Advanced Search 47
3.4.2.4. Site Clusters 47
3.4.2.5. Site Hierarchies 47
3.4.2.6. Site Mapping 47
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.4.2.7. Web Services 47
3.4.2.8. Publication 48
3.4.2.9. Trading Community Architecture 48
3.4.2.10. Integration with Inventory 48
3.4.2.11. Integration with Property Manager 48
3.4.2.12. Integration with Enterprise Asset Management 48
3.4.3. Release 12.1.2 48
3.4.3.1. Enhanced Hierarchy Management 48
3.4.3.2. Bulk Site Import Interface 49
3.4.3.3. Capture of Longitude/Latitude for Sites 50
3.4.3.4. Creating My Favorites 50
3.4.3.5. Web Services for Hierarchy Manipulation 50
3.4.4. Release 12.2 50
3.4.4.1. Rules Based Access Control for Sites and Hierarchies 51
3.4.4.2. Roles Based Access Control for Site and Hierarchy Attributes 51
3.4.5. Release 12.2.5 51
3.4.5.1. Geo-fencing Enhancement 51
3.4.5.2. Expose Source System References 51
3.4.6. Release 12.2.12 52
3.4.6.1. Site Hub Hierarchy Workbench Revamped with Oracle JET Technology 52
3.5. Oracle Supplier Hub 53
3.5.1. Overview 53
3.5.2. Release 12.1.3 53
3.5.2.1. Supplier Master Profile 53
3.5.2.2. Extended Supplier Profile 54
3.5.2.3. Enhanced Supplier Classification 54
3.5.2.4. Supplier Hierarchy Management 54
3.5.2.5. Data Import & Source System Management 55
3.5.2.6. Data Quality Management 55
3.5.2.7. Data Enrichment using D&B Integration 55
3.5.2.8. Data Publication and Synchronization 56
3.5.2.9. Unified Supplier Profile Business Event 56
3.5.3. Release 12.2.4 56
3.5.3.1. Supplier Merge 56
3.5.4. Release 12.2.5 57
3.5.4.1. Supplier Source System References 57
3.6. Supplier Lifecycle Management 58
3.6.1. Overview 58
3.6.2. Release 12.1.3 58
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified release of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. 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 in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in
subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience,
it also includes new or changed functionality introduced in the RUPs for Release 12,
including 12.0.2 through 12.0.7.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, “Release 12.1.1”.
Features released in an off-cycle patch have a special designation – for example, a feature
released after 12.1.1, but before 12.1.2, is designated as “Release 12.1.1+”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 2
3. New and Changed Features in Master Data
Management
3.1. Oracle Customer Hub (CDH)

3.1.1. Overview
Oracle Customer Data Hub provides comprehensive functionality to manage customer
data: consolidating customer information from disparate systems and business lines into
one repository, cleaning and enriching data centrally, and providing the resulting "single
point of truth" data as a service to consuming applications, enterprise business processes
and decision support systems.
3.1.2. Release 12.1.1
3.1.2.1. Threshold Values for Search Match Rules in Terms of Percentage
When the user creates Search match rules in DQM, the Threshold values such as Match
Threshold and Override Threshold values are represented both in UI and in the code as
“Raw scores”. But in Oracle Customers Online Common Party UI (OCO CPUI), for
example the Party Search UI or in the De-dupe UI, the results are displayed based on the
Match percentage. This confuses customers since the results are displayed inconsistently
in different UIs.
For a more consistent and user-friendly interface, the scores for Threshold in the Search
match rule have been converted from a raw score to a percentage value. All the seeded
Search match rules that contain raw scores have been converted to percentage and any
user created Search type match rules now represent Percentage for Match and Override
thresholds.
With this feature, the Threshold values and the Match criteria will be expressed in
percentages. This will make it easier for users to understand the Search results. Also,
users will be able to relate to percentage based Threshold values and it will be easy for
them to identify the potential match in the Search UI or in the De-Dupe UI as they will
also be based on percentages. No additional calculation is needed from raw score to
percentage.
The following changes have been made to represent the raw score as a percentage:
• UI validation has been added for the Override and Match Threshold fields for
Search type rule in Create / Update match rule UI.
• In the backend code, both Match and Override threshold values entered are
handled as percentages.
• For the existing seeded “Search Type” match rules, the Match threshold and
Override threshold have been corrected in terms of percentage irrespective of the
current value.
3.1.2.2. View Operating Unit Name while Submitting Customer Merge Request
Today, the Customer Merge program does not indicate the operating unit for which the
concurrent request is being run. We will now display the operating unit in the parameter
field in the Request summary screen against the request. The following changes are done
to implement this feature:
The customer merge concurrent program will display the operating unit parameter in the
Request summary screen. If there is more than one operating unit, then the first five
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Customer Hub (CDH) 3
operating units will be displayed. If there are more than five operating units, an ellipsis
(…) will be appended after the fifth operating unit.
If the customer merge is submitted from the Customer Merge form, then the selected
operating unit is displayed. If the user selects “ALL” for the operating unit, then
operating unit parameter displays “ALL”.
3.1.2.3. Improved Performance of Create Merge Batch Process
The Create Merge Batch process takes several minutes to complete because Merge uses
DQM for making default suggestions during preprocessing. We have introduced a new
profile to turn off DQM in the Create Merge Batch process.
The following changes are done to implement this new profile:
A new profile “Enable DQM Merge Suggestion” has been introduced with the default
value as YES
• If the profile is set to NO, then it will not enable DQM at the time of Merge
suggestion and the Create Merge Batch program will run faster. Also, the
“Change Grouping” dropdown will be disabled in the Address mapping page and
in the Relationship mapping page.
• If the profile is set to YES or not set, then it will enable DQM. In this case, the
“Change Grouping” dropdown will be enabled in the Address mapping page and
in the Relationship mapping page.
3.1.2.4. Improved Performance of System Duplicate Identification Tab

When the user navigates to the System Duplicate Identification Tab, it displays all the
System Duplicate Identification Batch details that are created by all the users. This
affects performance and it takes several minutes to load the data whenever the user clicks
on the System Duplicate Identification Tab. In order to avoid the delay in fetching the
data, the System Duplicate Identification Tab will show only the Batch details that are
created by the Login User. To retrieve the batches created by other users, one can do a
search with the respective user name. The System Batch Search can be performed based
on the search criteria - Batch name, Batch ID, Phase and Created by.
3.1.2.5. New “All” Option in Status LOV of Customer Search UI & Account Layer
UI
Add new “All” option to the Status list of values in the Customer Search UI and display it
in the Account layer UI to eliminate an Oracle Accounts Receivables (AR) regression
when AR migrated from forms to TCA’s OAF based UI.
This feature enables a user to search on ‘All’ status, which will display Active and
Inactive status for Accounts, Address and Contact blocks, with status flag in the result
screens. The ability to search and display ‘All’ status will allow them to return all the
customers in one result set so that they can easily see the information in one glance. The
addition of the ‘Status’ column in the result set will allow them to identify the status of
the records in the overall view. The addition of ‘Restore’ icon in the Address result block
and Contacts result block will enable users to restore inactive records.
In the 11i10 Customer Standard Form, users could search on ‘All’ status of the Party.
‘Status’ flag is also displayed in the result set and users have the ability to toggle at the
Address entity to either show ‘Active’ or ‘All’ status. In Release 12, AR migrated from
the forms based Customer Standard Form to the OAF TCA CPUI to display search
criteria in their UI. As a result, AR customers lost the ability to search on ‘All’ Status in
the Account / Address / Contact components since TCA CPUI did not support it since
11i10.
To support “All” status in the Search UI and in other UI’s, the following changes have
been done.
• TCA has added “All” status in DQM and Non DQM Party \Search block, Display
Account block, Display Address block and Display Contact block
• Also a new Status column has been added in DQM and Non DQM Party Results
Search block, Account Results block, Address Results block and Contact Results
block
• A new “Restore” icon has been added next to the Remove icon in the Address
Result block and the Contact Result block. If the record status is ‘Active’, then
the ‘Remove’ icon is enabled. If the record status is ‘Inactive’, then the ‘Restore’
icon is enabled
• A new lookup with values “ACTIVE”, “INACTIVE” and “ALL” has been
added.
3.1.2.6. View Status, Start & End Dates for a Contact Relationship in De-dupe UI
This feature enables the user to know the Status of the Contact Relationship and the Start
and End date of a Relationship in the De-dupe page without having to navigate to the
Relationship Details UI.
Today, users are unable to view the Status, Start date and End date for a Contact
Relationship in the De-Dupe UI when the user tries to create a new Relationship Contact
for a Party. In order to view the Status and Start date / End date of a Party Relationship,
users have to navigate to Party Relationship > Overview UI to know the details. To
avoid navigating to the Overview page of the Party relationship UI, the following
changes are done in the De-Dupe page to display the Contact Relationships.
1. The ability to display Contact Relationships based on the following.
• Across all Organizations based on a parameter value
• Active or All contacts based on a parameter value.
• Contacts only (Party Group Contacts) based on a parameter value
• Person to Organization Relationships based on a Parameter value
2. The ability to disable radio selection for contact nodes based on a Parameter
value
3. A Status column to display the Status of the Contact Relationship has been added
to the Search Results table.
4. 2 columns to indicate the Start and End date of a Contact Relationship have been
added to the Search results table
3.1.2.7. Web Services for TCA Business Objects and DQM Engine
Oracle has devised a new and enhanced infrastructure to support Web Services. This
solution is targeted at building a set of document style Web Services that are based on
this enhanced infrastructure to avail clients/consumers the benefits of discovering,
downloading and consuming standalone Web Services described fully by a WSDL file.
The Web Service receives the entire document, processes it and returns a response
message. The protocol places no constraint on how that document needs to be structured,
which is totally handled at the Application level. Document-style Web Services follow
asynchronous processing.
In accordance with the Release 12 TCA Business Objects, these new Service Beans
provide users access to the TCA data model at the Business Object-level. They have been
introduced to offer Spoke Systems the ability to invoke TCA public APIs for entities
across both the Party and the Customer Account layer in a platform independent manner.
Each service exposes Create, Update, Save and Get operations based on which Spoke
Systems may integrate with the Oracle Customer Data Hub (CDH). For instance, the
Spoke Systems may invoke a Web Service to Create, Update or Query an organization
Business Object within CDH. In addition, this release also provides Spoke Systems a
service that searches for parties within CDH using the Data Quality Management (DQM)
search engine.
The new Service Bean architecture facilitates creation and consumption of services by
various consumers in a way that maximizes the openness of Oracle e-Business Suite
Applications to support integration efforts with other applications within the enterprise,
be they home-grown, 3rd party vendor products or other legacy systems.
3.1.2.8. Access Third Party Address Validation Adapter across Firewall
With this feature, customers will now have an option to host the third party Address
Validation Adapter either inside the EBS firewall or through a standard firewall.
Currently, the Customer Data Management’s Address Validation functionality is
provided through a third party address validation adapter such as Trillium. However, the
address validation adapter must be behind the same firewall as Oracle EBS. There’s no
flexibility to host the address validation adapter through a standard firewall.
We will provide customers the ability to host the Address Validation Adapter such that it
can be either inside the EBS firewall or through a standard firewall configuration. We are
going to leverage the existing ATG profiles for this purpose:
• Applications Server-Side Proxy Host And Domain (It accepts IP Address other
than the proxy Host value)
• Applications Proxy Port
• Applications Proxy Bypass Domains (accepts multiple values separated by a
comma)
For the existing Customer Data Hub customers that integrate with Trillium, a 3rd party
provider of Address Validation Adapter will not be impacted by this feature if they do
not need to host the adapter via a standard firewall.
3.1.3. Release 12.1.2
3.1.3.1. Merge Web Services
In release 12.1, Oracle Customer Data Hub introduced standards based Web Services that
allows spoke applications to access the customer information in the Customer Hub.
Spoke applications can also search for customers within the Customer Hub using the
Data Quality Management (DQM) search rules.
In this release, Oracle Customer Data Hub provides three new Web Services:
3.1.3.1.1. Web Service to submit a request to merge customer parties
The key input for the Web Service is a list of potential duplicate customers that need to
be merged. The Web Service will submit a merge request to merge the customers passed
in via the input parameter. It will return the merge request id to the calling application.
3.1.3.1.2. Web Service to retrieve the details of a customer party merge
The key input for the Web Service is the Batch ID or a combination of the Batch ID and
the Merge to Party ID. The Web Service will extract the details of the merge referred to
in the input parameter. It will return the details of the merge to the calling application.
3.1.3.1.3. Web Service to retrieve the details of a customer account merge
The key input for the Web Service is the Customer Merge Header ID. The Web Service
will extract the details of the customer account merge referred to in the input parameter.
It will return the details of the merge to the calling application.
3.1.3.2. DQ Enable Web Services

In Release 12.1, Oracle Customer Data Hub Web Services do not use Data Quality
Management (DQM) functionality. Thus, it is possible to create duplicate customers and
the Data Librarian can submit a customer merge to resolve the duplicate.
In this release, Oracle Customer Data Hub Web Services can leverage DQM rules setup
in the Customer Hub. The DQM rules used by the Web Services are of a new match rule
type ‘Integration Services’. The new match rule type allows the user to specify the
attributes, the attribute transformations, the Match Threshold and the Auto merge
Threshold values. The Create Customer Web Service will use the DQM rule to check if
the input customer record specified in the Web Service matches the existing record in the
Customer Hub. By comparing the match score with the threshold values, it determines if
the input record should be merged with the existing record in the Customer Hub.
The following Web Services have been enhanced:
• Create Organization
• Create Organization Customer
• Save Organization (Create operation)
• Save Organization Customer (Create operation)
• Create Person
• Create Person Customer
• Save Person (Create operation)
• Save Person Customer (Create operation)
3.1.3.3. View History of Organization and Person Profiles
This feature allows the user to view the change history for Organization and Person
customer records in the Customer Hub. They can see how the customer record changed
since the time of creation. The user can also filter the change history listing by the source
system identifier.
3.1.3.4. Support Zip+4 in All Address Validation Flows for US Addresses
In Release 11i, US zip codes could be specified in a 5 digit and 5+4 digit formats. In
Release 12, the 5 digit format was supported and 5+4 digit format was not supported.
This enhancement allows the user to specify the US zip codes in the 5 digit and 5+4 digit
formats.
3.1.3.5. Time Zone for Resource Group
As team resources are scattered across the globe in different time zones, it becomes
important to be able to track the time zone at the resource group level instead of that at
the resource level. The resources within a resource group may be in different time zones
but the group has a single time zone that may be different from the time zone of the
resources belonging to that resource group. The time zone for the resource group is used
by EBS Service applications for scheduling purposes.
This enhancement allows the user to specify the time zone for a resource group. The
ability to specify the time zone for a resource is an existing feature.
3.1.4. Release 12.2

3.1.4.1. Spatial Data Integration
The eLocations based Spatial Data Integration allows for retrieving spatial information
from Oracle eLocations and storing the longitude and latitude data for addresses in the
TCA Registry. Currently, the integration works for any location within the US. In this
release, we are extending the list to support eighteen more countries. The additional
countries are Austria, Belgium, Canada, Denmark, Finland, France, Germany, Ireland,
Italy, Liechtenstein, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden,
Switzerland and United Kingdom.
The existing concurrent program “Spatial Information for Locations Batch Update” used
to geocode addresses has been enhanced to support additional parameters. Going
forward, you can also filter the list of input addresses by State, Province, City, Spatial
Data Source and Accuracy Level.
In addition to storing the longitude and latitude for each of the addresses, the accuracy
level and the spatial data source will be saved in the TCA registry. This allows users to
make address corrections and rerun the program for specific accuracy levels.
3.1.4.2. Real-Time Address Validation

Address validation is the process of comparing raw or user-entered addresses against a
known or authorized data source, to determine if the addresses are recognized and correct
according to the authority's database. Currently, you can validate addresses in real time as
you enter them by checking against the TCA Geography model repository. In this release,
you can validate the address in real time by using the third-party address validation
adapter database. The third-party address validation adapter is currently used to validate
the addresses in bulk as part of the batch address validation. Thus, the third-party address
validation adapter can be used to validate addresses in real time and in bulk mode.
3.1.4.3. Enhancement to Customer Import

The Customer Import program is used to import current and historical customer
information from other systems into the Customer Hub. In this release, you can import
tax attributes for each of the customers being imported into the Customer Hub. The
additional tax attributes are associated with the customer and customer addresses. Some
of the key tax attributes include the Tax Registration Number, Tax Exemptions, Fiscal
Classification, Tax Rounding Rule and the Tax reporting codes.
Prior to this enhancement, customers would have to manually specify the tax attributes
for each of the customer records using the E-Business Tax application UI.
3.1.4.4. Source System References
Currently, the Data Steward can view, create, update and remove source system
information for the Person, Organization and relationships entities. They can also view
the audit trail of changes to the source system mappings.
In this release, we are extending this feature to support additional entities. The Data
Steward will be able to view, create, update and remove source system reference details
for the Party Site Addresses, Contact Purposes, Contact Points, Accounts, Account
Contacts, Account Site Contacts and Account Site Purposes entities. They can also view
the audit trail of changes to the source system mappings for these entities.
3.1.4.5. Record History
In 11i Forms based applications, the users can view the record history details for the
customer and the related entities. This feature is not available in the R12 Oracle
Application Framework based pages.
In this release, the users can view the record history details for the customer and the
related entities. The audit details include the record creation date, the date it was last
updated, the user who created it and last updated it. These attributes are collectively
referred to as the “Who” columns. The ability to view the record history is essential from
the legal compliance, auditability, traceability and accountability perspectives.
3.1.4.6. Merge Web Service
In release 12.1, Oracle Customer Data Hub introduced standards based Web Services that
allows spoke applications to access the customer information in the Customer Hub.
Spoke applications can also search for customers within the Customer Hub using the
Data Quality Management (DQM) search rules. We also provided three merge web
services in 12.1.2.
In this release, Oracle Customer Data Hub provides a new API and Web Service to merge
two customer accounts. Spoke applications can use the API and Web Service to merge
two customer accounts.
3.1.4.6.1. API to submit a request to merge two customer accounts
The key input for the public API is the details for the two customer accounts to be
merged, the Merge-From Account and the Merge-To Account. The API will submit a
merge request to merge the two accounts passed in via the input parameter. It will
return the account merge request id and the customer merge header id to the calling
application. The API to retrieve the details of a previously completed customer
account merge is already available.
3.1.4.6.2. Web Service to submit a request to merge two customer accounts
The key input for the Web Service is the details for the two customer accounts to be
merged, the Merge-From Account and the Merge-To Account. The Web Service will
submit a merge request to merge the two accounts passed in via the input parameter.
It will return the account merge request id and the customer merge header id to the
calling application. The web service to retrieve the details of a previously completed
customer account merge is already available.
3.1.4.7. Industrial Classification Codes for 2012
Currently, the latest NAICS (North American Industrial Classification System) customer
classification codes are for 2002. In this release, we have seeded the latest published
NAICS codes for 2012.
3.1.5. Release 12.2.4
3.1.5.1. Additional Search Criteria for Account Site Addresses
In addition to the existing search criteria, the user can search for account site addresses
using the following additional search criteria:
a. Reference (HZ_CUST_ACCT_SITES_ALL.ORIG_SYSTEM_REFERENCE)
b. Category (HZ_CUST_ACCT_SITES_ALL.CUSTOMER_CATEGORY_CODE)
c. Alternate Name (HZ_LOCATIONS. ADDRESS_LINES_PHONETIC)
d. Site Name (HZ_PARTY_SITES.PARTY_SITE_NAME)
e. Location (HZ_CUST_SITE_USES_ALL.LOCATION)
The additional search criteria will help the user find the correct account site address
record without having to drill into the individual address record. The user will not have to
paginate through several records to locate the correct address record.
3.1.6. Release 12.2.5
3.1.6.1. Additional Search Criteria for Party Site Addresses
Provide the following search criteria to allow the user to search for party site addresses:
a. Country (HZ_LOCATIONS.COUNTRY)
b. Purpose (HZ_PARTY_SITES.SITE_USE_TYPE)
c. Site Number (HZ_PARTY_SITES.PARTY_SITE_NUMBER)
d. Postal Code (HZ_LOCATIONS.POSTAL_CODE)
e. Address Line 1 (HZ_LOCATIONS.ADDRESS1)
f. Address Line 2 (HZ_LOCATIONS.ADDRESS2)
g. Address Line 3 (HZ_LOCATIONS.ADDRESS3)
h. Address Line 4 (HZ_LOCATIONS.ADDRESS4)
i. City (HZ_LOCATIONS.CITY)
j. State (HZ_LOCATIONS.STATE)
k. County (HZ_LOCATIONS.COUNTY)
l. Province (HZ_LOCATIONS.PROVINCE)
The additional search criteria will help the user find the correct party site address record
without having to drill into the individual address record. The user will not have to
paginate through several records to locate the correct address record.
3.1.6.2. Customer Merge using OAF UI
Customer Merge helps to consolidate any duplicate customers or transfer site use activity
from a customer or site that is no longer active. After the merge completes successfully,
all activities that were previously associated with the old customer or site are now
associated with the new customer or site. Activity includes (but not limited to) invoices,
debit memos, commitments, credits, receipts, adjustments, quotes, orders and service
contracts.
The OAF UI customer merge allows the data steward to assign the merge request to
another data steward to share the workload. The assignment feature can also be used to
assign the request to a supervisor data steward to ensure correctness prior to submission.
The OAF UI customer merge allows the user to reject a merge request. The OAF UI
customer merge is accessed by the Data Steward via the Data Librarian responsibility.
3.1.7. Release 12.2.6
3.1.7.1. Google Maps replaces Yahoo Maps
Currently, TCA uses Yahoo Maps to show the map for an address. However, Yahoo
retired Yahoo Maps at the end of June 2015. Hence, the existing Yahoo Maps integration
has been replaced with the Google Maps integration. Users can view the Google map for
an address in TCA. This feature requires a separate license from Google to enable this
integration.
3.1.7.2. Enhancements to Customer Merge
The OAF UI based Customer Merge released in 12.2.5 is being enhanced in the 12.2.6
release. The data steward assignment process will validate that the assignee has access to
the operating units for the merge request and to each of the operating units for the
addresses in the merge request. There will be a new setting to default the data steward for
a new account merge request and new party merge request. The data steward parameter
can be passed to the Create Account Merge Request Web Service and Business Object
API.
3.1.8. Release 12.2.7
3.1.8.1. Enhancements to Party Merge
Data Stewards can view additional address related attributes for the Merge-From and
Merge-To Customer addresses to allow them to select the addresses that should be
merged. The additional address attributes include the Site Number, Address Description
and the Identifying address indicator.
3.1.8.2. Merge Extended Attributes during Party Merge
Currently, the User Defined Attributes (Extended Attributes) remain untouched when
merging two or more parties. If the Extended Attributes on the Merge To customer is
blank and the Merge From customer has an Extended Attributes, then that Extended
Attributes is not copied to the Merge To customer.
Going forward, the Extended Attributes for Organization, Person and Party Site
Addresses will be handled per standard merge procedures giving preference to Merge To
record.
3.1.9. Release 12.2.8
3.1.9.1. Dun and Bradstreet (D&B) integration Enhancement
D&B has obsoleted the java toolkit based integration used for online enrichment of
Organization parties in Trading Community Architecture (TCA). This change replaces
older Java APIs with SOAP-based APIs. There is no change in functionality.
This feature is backported to 12.1.3+.
3.1.10. Release 12.2.9
3.1.10.1. Support the ability to allow only one shipment per order
This feature allows customers to specify if they will accept only one shipment per order
or multiple shipments per order. The one shipment per order setting must be set at the
customer account level in the TCA customer model. For more details, refer to the Fill or
Kill for Sales Orders feature in the Order Management and Logistics RCDs.
3.2. Oracle Product Hub
3.2.1. Overview
Oracle Product Hub (PIM) is an enterprise data management solution that enables
customers to centralize all product information from heterogeneous systems, creating a
single view of product information that can be leveraged across all functional
departments.
Oracle Product Hub helps customers eliminate product data fragmentation, a problem that
often results when companies rely on nonintegrated legacy and best-of-breed
applications, participate in a merger or acquisition, or extend their business globally.
3.2.2. Release 12.1.1
The Oracle Product Hub features introduced in Release 12.1 have been largely governed
by requirements from the Retail Industry. Hence this release of PIM offers a vertical
solution for the Retail Industry. However, many features introduced in this release are
applicable and also requested by other industries as well.
3.2.2.1. Extensible Attribute Framework
Release 12.1.1 introduces the ability to master key relationships between an item and
other entities - such as supplier, organization and supplier-organization – and between
items themselves i.e. Style to SKU. The concept of a business entity has been introduced
in the extensible attribute framework, along with key features to provide ease of
maintenance of the attributes across these entities.
3.2.2.1.1. User defined Attribute Groups by Business Entity
An administrator can define user defined attribute groups for one or more business
entities. This includes new business entities Item Supplier, Item Supplier Site, Item
Organization and Item Supplier Site Organization, in addition to the existing Item
and Item Revision business entities.
3.2.2.1.2. Defaulting of Attribute Values across Business Entities
Where an attribute group is associated with one or more business entities, attribute
values will automatically default between business entities as follows:
• Item to Item Supplier,
• Item Supplier to Item Supplier Site,
• Item Supplier Site to Item Supplier Site Organization, and
• Item to Item Organization
3.2.2.1.3. Defaulting and Inheritance of Attribute Values from Style to SKU Items
When defining attribute groups that apply to a Style – SKU relationship, an attribute
value maybe either “Defaulted” or ‘Inherited” between the Style and SKU items.
This behavior is set at the attribute group level. An attribute value which is
“inherited” is copied from the Style item to all SKUs and cannot be overridden on
any SKU item. An attribute value which is “defaulted” is copied from the Style to all
SKUs on initial creation but can subsequently be overridden at the SKU item level.
3.2.2.2. Style – SKU Items
Release 12.1.1 introduces the concept of style items. A style or parent item typically
represents a group of similar items (SKUs) where one or more item variant attributes will
differentiate the items within the group. For example, a certain style of men’s shirt may
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Product Hub 12
have different colors and sizes, where color and size can be defined as the “variant”
attributes for the style. SKU items can be easily generated through the user interface
based on selected valid combinations of colors and sizes i.e. variant attribute values. The
SKU items inherit all properties from the style item. User-defined attribute values can be
either defaulted or inherited between the style and SKU items based on the attribute
group setup. In addition, the following properties are also defaulted to the SKU items
from the style item during item creation:
• Operational Attribute Groups
• Item Suppliers
• Item Supplier Sites
• Item Organizations
• Item Supplier Site Organizations
• Lifecycle and Lifecycle Phase
• People
3.2.2.3. Item Organization Relationships
Release 12.1.1 enhances the item – organization assignment management capabilities in
PIM.
3.2.2.3.1. Managing Item Assignments to Organizations

While assigning an item to an organization through the item workbench, users can
author the item status in addition to authoring the Primary Unit of Measure, Tracking,
Pricing, Secondary Unit of Measure, Defaulting, Negative Deviation Factor, and
Positive Deviation Factor.
3.2.2.3.2. Changing Organization Context
This feature provides the ability to change the organization context of the item
workbench. Users can navigate from one organization to another from within the
item workbench and retain the item and its data context. Users can navigate to a
different organization by using the short cuts in the item workbench and also from
within the organizations view page in the item workbench by selecting the required
organization. In both cases the user can change the organization context without
losing the item context.
3.2.2.4. Item Supplier and Item Supplier Site Relationships
Release 12.1.1 provides the capability to master the relationship between the item and the
supplier/s of that item. The relationship may be at the supplier level and/or at the supplier
site level.
3.2.2.4.1. View Item Supplier and Supplier Site Relationships
User can view supplier and supplier site assignments based on the context of an item
and organization within the Item Workbench. User can also view associated
information based on the supplier or supplier Site assignment. For example, the user
can view the associated pack items based on the item and supplier assignment.
3.2.2.4.2. Create Item Supplier and Supplier Site Relationships
This feature allows the creation of relationship between multiple suppliers and
associated supplier sites based on the context of an item and organization within the
Item Workbench.
3.2.2.4.3. Create Supplier and Supplier Site Relationships for Style - SKU Items
associated supplier sites for SKU items associated with a Style Item. For example, a
new style item and associated SKU items have been created; the user can select the
style item in the Item Workbench and assign both supplier and supplier sites to the
style Item and the associated SKU items. This feature is controlled by an option flag.
3.2.2.4.4. Create Supplier and Supplier Site Relationships for Pack Items
associated supplier sites for pack items and all items in the pack hierarchy. This
feature is controlled by an option flag.
3.2.2.4.5. Primary Item Supplier and Supplier Site Definition
This feature allows the definition of primary suppliers and supplier sites for a
supplier and/or supplier site relationship. Only one supplier and supplier site can be
designated a primary for an item.
3.2.2.4.6. Update Item Supplier and Supplier Site Attributes
This feature allows the update of existing supplier and supplier site attributes based
on the context of an item and organization within the Item Workbench.
3.2.2.4.7. Mass Update of Item Supplier and Supplier Site Attributes
This feature allows the update of supplier and/or supplier site attributes based on the
context of an item and organization within the Item Workbench. For example, you
can update lead time attribute for all suppliers for an item and organization.
3.2.2.4.8. View Item Supplier and Supplier Site Attribute Changes
User can view pending changes for attributes of a supplier or supplier site
assignment. The current value and the pending changed value for the attribute are
displayed.
3.2.2.4.9. Supplier Management
The menu options for the Product Information Data Librarian responsibility have
been extended to include the search, view, create and edit of supplier information.
3.2.2.5. Item Supplier Site Organization Relationships
Release 12.1.1 provides the capability to master the relationship between the item, the
supplier/s of that item and organizations.
3.2.2.5.1. View Item Supplier Site Organization Relationships
A user can view supplier site organization assignments based on the context of an
item, and organizations within the Item Workbench. The organization context will be
determined by the organization in the Item Workbench and organization/s that the
user has access to. User can also view associated information based on the supplier
site organization assignment.
3.2.2.5.2. Create Item Supplier Site Organization Relationships
This feature allows the creation of multiple supplier site organizations assignments
based on the context of an item and organization within the Item Workbench. This
feature requires the organization assignment and supplier site assignment for the item
to exist prior to creating the supplier site organization assignment.
3.2.2.5.3. Create Supplier Site Organization Relationships for Style - SKU Items
This feature allows the creation of supplier site organization assignments for SKU
items associated with a style item. For example, a new style item and associated
SKU items have been created; the user can select the style item in the Item
Workbench and create supplier site organization assignments for the style item and
the associated SKU items. This feature is controlled by an option flag.
3.2.2.5.4. Create Supplier Site Organization Relationships for Pack Items
This feature allows the creation of supplier site organization assignments for pack
items and all items in the pack hierarchy. This feature is controlled by an option flag.
3.2.2.5.5. Update Item Supplier Site Organization Attributes
This feature allows the update of existing Supplier Site Organization assignment
attributes based on the context of an item and organization within the Item
Workbench. For example, you can update lead time attribute for an item and
organization relationship with a specific supplier and site.
3.2.2.5.6. Mass Update of Item Supplier Site Organization Attributes
This feature allows the update of supplier site organization attributes based on the
context of an item and organization within the Item Workbench.
3.2.2.5.7. View Item Supplier Site Organization Attribute Changes
A user can view pending changes for supplier site organization attributes. The current
value and the pending changed value for the attribute are displayed.
3.2.2.6. Pack Management
Release 12.1.1 provides enhancements to formal pack management capabilities in PIM.
3.2.2.6.1. Homogeneous Multi-Pack Creation for Style/SKUs
This feature provides the ability to mass create packs for multiple SKUs for a given
style item by defining a representative pack hierarchy. SKUs within a style in general
tend to have the same pack requirements; users can easily create homogeneous packs
for several SKUs of a style item at the same time.
3.2.2.6.2. View Packs for an Item
This feature provides a view of the pack definition. Users can view all the packs
created for an item from the Item workbench. Using the available display formats,
users can view various item attributes such as item status for all items in a pack.
3.2.2.6.3. Pack Assignments to Organizations
This feature provides the ability to assign packs to organizations. Packs can be
explicitly assigned to organizations. Users can manage pack assignments to selected
organizations at any level in the pack hierarchy.
3.2.2.6.4. Exporting Packs to Excel
This feature provides the ability to export packs. Users can export an item’s pack
definition to excel. Users can choose to export the pack definition at any level in the
pack hierarchy.
3.2.2.7. New Item Definition and Approval
Release 12.1.1 provides enhancements to new item definition and workflow
capabilities in PIM
3.2.2.7.1. Style Item Flag
Release 12.1.1 introduces the concept of style items. A style or parent item typically
represents a group of similar items (SKUs) where one or more item variant attributes
will differentiate the items within the group. A new flag is available during the item
creation process which the user can check to indicate that the item being created is a
style item.
3.2.2.7.2. Simplified Item Creation Process
The item creation process has been simplified from a multi-step process to a single
user interface where the user can enter basic information about the item before being
taken to directly to the item workbench to provide additional details about the item.
This provides a consistent user experience for item creation and maintenance.
3.2.2.7.3. Application of Item Templates
Item templates provide a means to quickly default item attributes when creating a
new item. This ensures accurate, consistent information at the time of item creation.
You can apply multiple templates to the item, and Release 12.1.1 provides an
enhanced user interface for quickly selecting and applying templates.
3.2.2.7.4. Ad-hoc New Item Request
The New Item Request process has been improved to allow users to create items and
then submit a new item request for the item or group of items at a later date. The New
Item Request will no longer be created automatically at the end of the item creation
process. This allows a user to work on an item or set of items as a draft and then
request approval and/or further definition via workflow when appropriate.
3.2.2.7.5. Multiple Items on a New Item Request

The New Item Request process supports multiple items of the same item catalog
category on a single request. This includes:
• Lines on a New Item Request similar to change lines
• Approval status by line which allows a user to approve or reject an single
item on the New Item Request
• Mass Updates in the New Item Request, allowing a user to select a number of
items in New Item Request for update/action
3.2.2.7.6. Multiple Workflows on a New Item Request
Enhancement to New Item Request workflow to allow multiple workflow processes
for each status as per change workflows.
3.2.2.7.7. Copy New Item Request
Ability to copy items from one New Item Request to another. User can select the
items to be copied to a new New Item Request or to an existing New Item Request.
3.2.2.7.8. Defaulting of New Item Request Type based on Item Catalog Category
Hierarchy
As per other setup on the item catalog, a New Item Request Type can be associated
with a parent item catalog category, and is defaulted to all child categories for that
parent. Users can override the default and select another New Item Request Type at
the child category level. If the New Item Request Type is defaulted from the parent
category it cannot be updated at the child category level.
3.2.2.8. Advanced Search
Advanced Search is enhanced in 12.1.1 to search and display item data based on the
new entities introduced in this release.
3.2.2.8.1. Search Criteria
Search parameters have been enhanced to include the following:
• Item Organization Attributes and Relationships
• Item Supplier and Item Supplier Site Attributes and Relationships
• Item Supplier Site Organization Attributes and Relationships
• Style – SKU Relationships
• Alternate Catalogs
• New Item Request Number
3.2.2.8.2. Display Formats
The primary keys of any entity/s that a user is searching on are automatically
displayed in the search results page. For example, when you search by within a given
catalog, search results will automatically display alternate catalog and categories as
columns.
Display formats have been enhanced to include the following:
• Item Organization Attributes and Relationships
• Item Supplier and Item Supplier Site Attributes and Relationships
• Item Supplier Site Organization Attributes and Relationships
• Alternate Catalogs
• User defined attributes from child catalog categories. For example when
searching on the “TV” item catalog category, attributes from the child item
catalog category “LCD TV” can be shown in the same search results.
3.2.2.9. Excel-based Import and Export
Excel based import/export functionality has been enhanced to support the new
business entities introduced in this release. This includes Item Supplier, Item Supplier
Site and Item Supplier Site Organization entities, plus Style – SKU item
relationships.
3.2.2.9.1. Excel Import/Export for New Business Entities
When importing or exporting item supplier, item supplier site or item supplier site
organization relationships via excel, ‘Supplier” and ‘Supplier Site” columns
(depending on the data) will be added to the file, in addition to the existing ‘Org.
Code” column. These columns are the key identifiers for the item relationships.
The organization identifier ‘Org Code”, will be used to identify both the master
organization for the Item, Item Supplier and Item Supplier Site entities, and also any
child organizations that the item is assigned via an item organization or item supplier
site organization assignment.
3.2.2.9.2. Excel Import/Export for Style – SKU Items
When importing or exporting style and SKU items via excel, a column “Style Flag”
will be added to the file to identify style items, SKU items will have a “Style Item”
column which identifies the style item for that SKU. Both the “Style Flag” and “Style
Item” columns cannot be updated after initial creation.
Variant attributes, which are used to differentiate items within a style group, can be
imported/exported via excel, however the behavior of the column depends on
whether the item is a style or SKU item. Where an item is a style item, the variant
attribute column will contain the name of the variant attribute value set (i.e. all
possible variant attribute values) and if the item is a SKU item the variant column
will contain the variant value. For example, for a style item the variant column
“Color” would contain a reference to the “Color Value Set”, whereas the variant
column “Color” for a SKU item would contain the actual value e.g. “Blue”.
3.2.2.9.3. Excel Import/Export for Pack Items
Pack import and export via excel is enhanced to include user defined attributes in
addition to operational attributes.
3.2.2.10. Mass Maintenance of Item Supplier and Item Supplier Site Relationships
Mass Maintenance is enhanced to include the new item supplier and item supplier
site relationships introduced in this release.
3.2.2.10.1. Mass Creation of Item Supplier and Item Supplier Site Relationships
This feature allows the creation of new supplier and supplier site relationships for
multiple items. For example, create a new set of suppliers and their supplier sites for
all paint items.
3.2.2.10.2. Mass Creation of Item Supplier Site Relationships
This feature allows the creation of new supplier site relationships for existing
suppliers for multiple items. For example, add a new set of supplier sites for existing
suppliers for all paint items.
3.2.2.10.3. Mass Update of Item Supplier and Item Supplier Site Attributes
This feature allows Item Supplier or Item Supplier Site attributes for multiple items
and/or suppliers/supplier sites to be updated in a single flow. For example, update the
supplier minimum quantity for all paint items sourced from suppliers in Northern
California, or update the lead time for all paint items, for all supplier sites that these
items are sourced in for Northern California and Utah.
3.2.2.10.4. Mass Creation of Style - SKU Supplier and Supplier Site Relationships
This feature allows the creation of supplier and/or supplier site relationships for
multiple SKU items associated with a style item. For example, a new group of style
items and associated SKU items have been created for the new fall line of women
clothes; the user can select the style items and assign them to a group of suppliers and
supplier sites. The supplier and/or supplier site relationships will be created for the
style items and their associated SKU items. This feature is controlled by an option
flag.
3.2.2.10.5. Mass Creation of Pack Supplier and Supplier Site Relationships
This feature allows the creation of supplier and/or supplier site relationships for
packs. This includes all items in the pack hierarchy. For example, to add additional
suppliers for existing pack configurations, a user can select multiple packs and assign
them to the new suppliers and/or supplier sites. All items in the pack configurations
will be assigned to the new suppliers and/or supplier sites. This feature is controlled
by an option flag.
3.2.2.11. Mass Maintenance of Item Supplier Site Organization Relationships
Mass Maintenance is enhanced to include the new item supplier site organization
relationships introduced in this release.
3.2.2.11.1. Mass Creation of Item Supplier Site Organization Relationships
This feature allows the creation of new supplier site organization relationships for
multiple items. For example, create a new set of suppliers and supplier sites for all
paint items for stores in California. The organization and supplier site relationships
must exist prior to creating the supplier site organization relationships.
3.2.2.11.2. Mass Update of Item Supplier Site Organization Attributes
This feature allows Item Supplier Site Organization attributes for multiple items
and/or suppliers/supplier sites and/or organizations to be updated in a single flow. For
example, update the lead time for all paint items sourced from suppliers in Northern
California Sites for each of the Northern California stores.
3.2.2.11.3. Mass Creation of Style - SKU Supplier Site Organization Relationships
This feature allows the creation of supplier site organization relationships for
multiple SKU items associated with a style item. For example, a new group of style
items and associated SKU items have been created for the new fall line of women
clothes; the user can select the style items and assign them to a group of new supplier
sites for a group of stores. The supplier site relationships will be created for the style
items and their associated SKU items. The organization and supplier site relationship
for the selected items must exist prior to creating the supplier site organization
relationships. This feature is controlled by an option flag.
3.2.2.11.4. Mass Creation of Pack Supplier Site Organization Relationships
This feature allows the creation of supplier site organization relationships for packs.
This includes all items in the pack hierarchy. For example, to add additional suppliers
for existing pack configurations for a group of stores, a user can select multiple packs
and assign them to the new suppliers and/or supplier sites for a group of stores. All
items in the pack configurations will be assigned to the new supplier sites and
organizations. The organization and supplier site relationship for the selected items
must exist prior to creating the supplier site organization relationships. This feature is
controlled by an option flag.
3.2.2.12. Enhancements to Release 12 Mass Maintenance
3.2.2.12.1. Simplified Mass Update with Excel
Where a mass maintenance flow uses only excel for making the changes, the user can
go directly to excel, avoiding the additional step of the “Choose Action” page.
3.2.2.12.2. Future Data Scheduling for Mass Update Changes
This feature allows for future date scheduling of mass update changes. It is available
in both the “Export to Excel” and “Apply to Database” options. For example, a user
may want to make a set of items active in a set of stores on a future date; with this
feature the item organization assignments can be created but scheduled for processing
at a later date.
3.2.2.12.3. Mass Creation of Item Organization Relationships
The user can choose one of the following options when assigning items to
organizations:
• Assign Structures to Organizations
This feature assigns structures for the selected items to the set of
organizations. Structures are specified by structure name and can be either
created as common structures in the organizations or can be copied to each
organization.
• Assign Packs to Organizations
This feature assigns packs for the selected items to the set of organizations.
The pack is created as a common structure for each of the selected
organizations. For example, a user can assign sellable items and associated
packs configuration to a set of stores.
3.2.2.13. Catalogs
3.2.2.13.1. Item Catalog User Defined Pages for Business Entities
The concept of a business entity is applied to user defined pages as well as user
defined attributes. A page can only be associated with one business entity, and hence
all attribute groups on that page must be for the same business entity. An item page
can be defined for new business entities Item Supplier, Item Supplier Site, Item
Organization and Item Supplier Site Organization, in addition to the existing Item
and Item Revision business entities.
3.2.2.13.2. Item Catalog Import Formats
Import formats are used to specify the attributes that users can enter in the import
process for an item catalog category. These attributes are generated as columns in the
excel file along with required item attributes. Import formats have been extended to
include attributes across business entities such that a user can include Item Supplier,
Item Supplier Site, Item Organization and Item Supplier Site Organization attributes
in an import format, in addition to Item and Item Revision attributes.
3.2.2.13.3. Item Catalog Number / Description Generation for Style / SKU Items
Depending on the policy defined for an Item Catalog Category the Item Number
and/or Item Description can automatically generated for all items created in that item
catalog category. With the introduction of style and SKU items there is a need to
have a different scheme for Item Number / Description generation for the SKU Items
as compared to that of the Style Item. In most cases, the SKU Item has the Style Item
Number or Description appended to its number or description.
By allowing a different policy for style items versus SKU items, the item number /
description generation can be ignored for Style Items and only be applicable to SKU
and Standard Items. Setup also allows users to select the primary attributes of the
style item to generate the item description for the SKU items.
3.2.2.13.4. Item and Alternate Catalog Mappings
Item Catalog Categories and/or Alternate Catalog Categories can be mapped to
define rules which can automatically determine an item catalog category or alternate
catalog assignment for an item. During the inbound Global Data Synchronization
process orchestration, these mappings are used to automatically classify the items for
example in the primary catalog based on a GPC or UDEX classification.
3.2.2.13.5. Ad-hoc Item Grouping / Lists
There is often a need to create a group or list of items for different business activities.
For example, in retail a user may wish to create a seasonal collection for rollout to
stores. The catalog management capabilities have been enhanced to easily allow a
user to create a new grouping of items in a category or add items to an existing
category / group of items. A user can search for items using simple or advanced
search and select items from the result set and add them to a new or existing group /
category. This group / category of items can be available to that user i.e. a private
group, or can be made available to groups of users based on the catalog security
setup.
3.2.2.13.6. Catalog Browse displays Items in Child Categories
While viewing a category in a catalog, all the items in that category plus those
belonging to any child categories of the selected category are displayed.
3.2.2.14. Rules
3.2.2.14.1. Constraint-based Rules
This feature enables the user to defined integrity constraints for items and related
business entity attributes. There are two types of constraints:
• Validations
These define expressions that have to be satisfied for the attribute data to be
valid. For example:
Physical_Attributes.Net_Weight <= Physical_Attributes.Gross_Weight
This expression ensures that for each business entity that is assigned this
constraint, the Net Weight will be less than or equal to the entity’s Gross
Weight.
• Assignments
These compute values for attributes based on other attribute values. For
example:
if (Logistics.Shippable) then Physical_Attributes.Volume =
Physical_Attributes.Length * Physical_Attributes.Height *
Physical_Attributes.Width
In other words, the Volume of an entity is always computed from the most
current values of Length, Height and Width. This example also illustrates
that assignments can have if conditions preceding them, which have to
evaluate to true before the assignment takes place.
Validations and Assignments are supported for items and related entities: Item
Organization, Item Supplier, Item Supplier Site and Item Supplier Site Organization.
3.2.2.14.2. Expression-based Rules
In addition to the business entities listed above, expressions can also make use of
related entities such as Alternate Catalogs, Suppliers, Supplier Sites and
Organizations. For example, the following expression will check if an Item belongs
to a “Summer 2007” Catalog:
assignedTo(Summer 2007)
Expressions can make use of standard operators:
Logical and, or, not

Comparison == < <= > >== in
Tolerance* changed, delta, percent, previous
Math + - * / abs, sum, min, max, round, roundup, rounddown
String + indexOf, length, lowercase, substring, trim, uppercase,
Date + - (date +/- number of days)
* Tolerance expressions can be used to compare a new value with the value that is the current
value for that attribute, for example if you want to ensure that an item cannot change by more
than 10% the expression would be as follows :
abs(percent(Physical_Attributes.Weight)) <= 10
3.2.2.14.3. Rule Sets
Rules (validations and assignments) are grouped into Rule Sets for ease of
administration. Each Rule Set is executed in the context of an Attribute Group or an
Item Catalog Category. Rule Sets in the Attribute Group context can only use
Attributes from that Group. Rules Sets in the Item Catalog Category context can use
any Attribute from the Attributes Groups assigned to that Item Catalog Category
(except for multi-row groups, see below).
Restriction on using Multi-Row Attribute Groups
Due to technical restrictions, rules using attributes from multi-row attribute groups
cannot access attributes from any other attribute group.
Composite Rule Sets
Rule Sets can include other Rule Sets to form “Composite” Rule Sets. This
encourages the modular grouping of rules, which can be assembled into more
complex Rule Sets.
3.2.2.14.4. Assignment of Rule Set to Business Entities
Rule Sets are explicitly assigned to a Business Entity to indicate which Rule Set is
used to validate it. Entities will then be validated any time the attributes of that entity
can change. For example, validations will be performed during item import and
when a user updates an item through the user interface.
3.2.2.14.5. Using Rules in Change Management
Validation Rules can indicate if a change requires a Change Order to be created.
This is done by setting the “Severity” of a Validation to “Needs Approval”.
Whenever that validation fails, it will force the creation of a Change Order for that
Attribute Group. The other values of Severity are “Error”, which disallows the Entity
to be processed further, and “Warning”, which simply alerts the user that a validation
failed.
3.2.2.15. Import Workbench
The Import Workbench has been enhanced to support the new business entities and
pre-built synchronization with the Global Data Synchronization Network (GDSN).
See section on Global Data Synchronization for description of the latter.
3.2.2.15.1. Batches for new Business Entities
The Import Workbench Batch Detail pages have been enhanced to display the
following additional information for the batch:
• Item Supplier
• Item Supplier Site
• Item Supplier Site Organization
• Alternate Catalog Category Assignments
3.2.2.15.2. Matching
Match Rules have been enhanced to support matching based on item supplier and
item supplier site attributes, in addition to the item attributes already supported.
3.2.2.15.3. Batch Scheduling
Batches can now be scheduled for processing on a future date. For example, a user
may want to make a set of items active in a set of stores on a future date; these
changes can be made in advance and the item status update scheduled for processing
in batch at a later date.
3.2.2.15.4. Pack Management
The user interface for managing structures has been enhanced to provide an H-Grid
display for pack hierarchies.
3.2.2.15.5. Import Management
The Import process has been enhanced to execute validation and approval rules
defined through the new rules framework. Rules can be used to validate data prior to
import or define whether a change order will be required or not depending on the
change. For example, on import a supplier cost change of more than 2% would
initiate a change approval process.
When importing new items, an option on the batch (defaulted from the source
system) controls whether one new item request is created for all items in the same
item catalog category or whether a new item request is created per item (Release 12
behavior).
3.2.2.16. Change Management
3.2.2.16.1. Change Management for new Business Entities
Change Management has been enhanced to support change definition and approval
for the new business entities. The following can now be authored on a change order:
• Item Organization Attributes
• Item Supplier Attributes
• Item Supplier Site Attributes
• Item Supplier Site Organization Attributes
3.2.2.16.2. Change Management integration with Rules Framework
The rules framework has been integrated with Change Management to provide
exception-based change management. Rules executed on item attributes or the new
item relationship business entities can determine whether a user will need to create a
change order for the change. In prior releases this was only configurable by item
lifecycle phase. For example, if case-pack item dimensions change by more than 5%
route the change for approval.
3.2.2.17. Security
3.2.2.17.1. Item Supplier and Item Supplier Site Security
With the introduction of new business entities – Item Supplier, Item Supplier Site and
Item Supplier Site Organization – new privileges have been seeded to secure those
entities. These are “View Item Supplier Assignment”, “Create Item Supplier
Assignment” and “Edit Item Supplier Assignment”. These privileges are used to
control view, creation and edit respectively of the supplier and supplier site
assignments for an item. External users / vendors can only view / create /edit supplier
and supplier site assignments for their own supplier id/company.
Item Supplier and Item Supplier Site user defined attributes can be secured as per
item attributes.
3.2.2.17.2. Item Organization Security
Security for Item Organization relationships has been enhanced, such that a user can
only assign items to organizations if they have “View Item Organization
Assignments” and/or “Create/Edit Item Organization Assignments” respectively.
Item Organization user defined attributes can be secured as per item organization
attributes.
3.2.2.17.3. Item Supplier Site Organization Security
The new business entity – Item Supplier Site Organization – is secured based on Item
Supplier Site and Item Organization privileges. To view / create / edit a supplier site
organization relationship for an item, a user must have both view / create / edit item
supplier privileges (listed above) and also “View Item Organization Assignments”
and/or “Create/Edit Item Organization Assignments” respectively.
Item Supplier Site Organization user defined attributes can be secured as per item
attributes.
3.2.2.17.4. Security Inheritance based on Item Catalog
People and roles assigned to an Item Catalog Category are inherited to child
categories based on the Item Catalog hierarchy. For example, a user having item edit
privileges for the item catalog category “TV” will have those privileges on the child
category “LCD TV”.
3.2.2.17.5. Security Inheritance based on Style – SKU Item Relationship

People and roles defined for a style item are defaulted to all SKU items when SKU
items are created for a style, or when an existing item is assigned to a Style item.
3.2.2.17.6. Security for Item Assignments to Alternate Catalogs
Alternate Catalogs are created for many different classification purposes and hence
could be created and maintained by many different groups within an organization.
Hence, it is essential to control who can assign items to these Alternate Catalogs.
Security privileges on an Alternate Catalog control who can assign items to that
Alternate Catalog. Only users with appropriate privileges on an Alternate Catalog
will have the ability to assign items to that Alternate Catalog.
3.2.2.18. Publication
This release includes new query services and additional business events for
publishing data from PIM.
3.2.2.18.1. Business Events
Business events are now raised whenever an Item Supplier, Item Supplier Site or
Item Supplier Site Organization is create / updated or deleted.
In addition a new business event is raised whenever a batch is processed.
3.2.2.18.2. Query Services
Query services are available to required extract data from PIM based on the
requirements of a subscribing application. For example a BPEL process could
generate a payload from a query service based on a business event subscription. The
following is a list of query services:
getItemAttributes Returns primary and user defined attributes for the
specified Item Organization
getItemSupplierAttributes Returns information about the specified Item Supplier
Assignment
GetItemSupplierSiteAttributes Returns information about the specified Item Supplier
Site Organization Assignment
getItemCategoryAttributes Returns information about the specified Item Category
getCategoryAttributes Returns information about a Category
getCatalogAttributes Returns information about a Catalog
getStructureAttributes Returns information about the BOM/Structure/Pack
Hierarchy header for the specified item
3.2.2.19. Purge
Item purge functionality has been enhanced to purge related entities – Item Supplier,
Item Supplier Site and Item Supplier Site Organization when an item is purged. A
style item can be purged, as long as there are no SKU items for the style i.e. these
would need to be purged in advance of the style item.
3.2.2.20. Inbound Global Data Synchronization
For inbound data synchronization, this release delivers pre-packaged integration with
the 1SYNC data pool. This provides support for both the inbound message from the
data pool, plus any responses that are required to be sent back to the data pool based
on the incoming data.
3.2.2.20.1. Pre – Processing of Inbound Data
The solution leverages a flexible middleware architecture that makes it easily
configurable and extensible to add new or modified attributes for other data pools,
different supplier feeds or new industry verticals etc. A seeded BPEL process is used
to process the data prior to loading the staging tables in PIM. This flow can be easily
modified by a customer to add additional checks or spawn different processes, for
example to handle data received from different suppliers or for items that have
hazardous material information etc.
The pre-packaged solution leverages Oracle’s B2B Server to communicate with the
1SYNC data pool using an AS2 communications protocol. This configuration can be
modified at the customer site to use, for example, another B2B gateway already used
at that site for B2B integration (e.g. for PO processing).
Rules-Based Category Classification
The orchestration flow includes a pre-built service to identify the primary item
catalog classification based on external classification scheme specified in the inbound
payload – such as GPC or UDEX. The service uses the Item Catalog Categories
and/or Alternate Catalog Categories mappings setup within PIM.
3.2.2.20.2. Import Workbench
A source system can be enabled as a data pool. A batch created for a source system
which is enabled as a data pool will be flagged as GDSN batch.
A batch which is defined as a GDSN batch will have additional capabilities to enable
processing of the GDS data and also message choreography with the data pool,
specifically these are:
• A Group ID is used to group the product hierarchy from the data pool to
ensure that all items in the hierarchy are processed together
• A confirmation message is sent automatically to the data pool when data is
imported from the Import Workbench to the repository
• A user can select items in a GDSN batch and based on the selected action,
send the appropriate message back to the data pool.
The integration of the rules engine with batch import will validate the data from the
data pool on import. If the data fails validation, the user is able to send a message
from the import workbench user interface to the supplier via the GDSN to fix the
data. Similarly, the user is able to leverage the rules engine integration with change
management to ensure that any supplier changes greater than the thresholds defined
in the rules can automatically initiate a change approval workflow.
3.2.2.20.3. Post – Processing of Inbound Data

Once the GDSN inbound data has been processed i.e. accepted (imported), rejected
or sent back to the supplier for correction, a seeded BPEL post – processing flow is
used to send the response back to the data pool. This flow can be easily modified by a
customer to add additional process steps to add logic based on the response. For
example, if an item is sent back to the supplier for correction, an audit log could be
created to identify suppliers that frequently send erroneous data.
3.2.3. Release 12.1.2
In order to stay competitive in a cutthroat, product-driven market, customers must
continually offer new value-added services and products. However, when trying to
design and sell new and innovative products and services for different markets and users,
customers are typically burdened with complex application and IT architectures with
stove-piped, siloed information that represent basic product and service definitions in
costly point-to-point integrations between applications with heterogeneous data models.
The result has been less flexibility and agility in providing customer-focused products
and services, lengthier times to market, etc.
To achieve flexibility and agility, customers are increasingly moving away from IT-
centric and siloed approaches to manage their products and service portfolios and, rather,
are looking at data-driven approaches.
The latest capabilities of Oracle Product Hub addresses these issues, providing a central
repository for both product and service data that was traditionally fragmented across
multiple product catalogs, and then publishes that information to the relevant systems for
business or operational purposes.
3.2.3.1. Transaction Attributes
Some product characteristics are represented by attributes whose values belong to a

continuous domain as opposed to a discrete set of values. The resulting components
of such attributes cannot be defined in advance, such as when we create value sets for
our standard attributes. Such attributes are often used by applications that manage
sales-related business transactions or service fulfillment. These kinds of product
attributes are generally referred to as transaction attributes, as opposed to static
attributes where the values are both specified in advance and also do not change
irrespective of the business process performed on or around the item.
3.2.3.1.1. Transaction Attributes Definition

Release 12.1.2 allows users to define Transaction Attributes (TA), which may have
an associated value set. If no value sets is associated, then an appropriate value can
be specified during a business transaction or service fulfillment. These Transaction
Attributes are defined within the context of an Item Catalog Category (ICC).
3.2.3.1.2. Transaction Attribute Metadata

Once the TA has been defined for an ICC, users may specify metadata for each TA
that controls the behavior of the TA. After the creation of specific products, certain
Metadata values can be changed at the product level. This allows users to control the
behavior of the TA for that specific product
3.2.3.1.3. Inheritance of Transaction Attribute and Attribute Metadata

Transaction Attributes defined at any ICC are then inherited down the hierarchy to
the child ICCs.
Child ICCs can have two kinds of TAs:

• Local: A local TA is one that is defined at the child ICC.
• Inherited. An inherited TA is one that is inherited from a parent ICC.
Users may modify the metadata of inherited Transaction Attributes for individual
child ICCs. If a user does so, this breaks the inheritance from the Parent ICC to the
Child ICC for the specific metadata. Any subsequent changes to that metadata of the
TA at the Parent ICC are no longer reflected at the Child ICC.
3.2.3.1.4. Privileges for Transaction Attributes

Like other user-defined attributes (UDAs), privileges are associated with TAs that
determine who can view and update these attributes and their associated metadata
definitions.
• Privileges at the ICC Level:

No additional privileges other than those required to update an ICC are
required. Any user having the privilege to update the ICC is able to create
and update TAs associated with that ICC.
• Privileges at the Product Level:

o View Privilege: Any user who has an Item View Privilege is allowed to
view the TAs associated with that Item. No additional privileges are
required. The View Privilege does not differ from one TA to another.
o Edit Privilege: A new “Edit Transaction Attribute” privilege is seeded
within the product. Only those users with Item Roles having this
privilege would be allowed to update the TAs for a product. This
privilege governs the edit behavior for all TAs and does not differ from
one TA to another.
3.2.3.1.5. Transaction Attributes within a Product

Transaction Attributes associated with an ICC are available in all products created
within that ICC. However, because of the very nature of TAs, their attribute values
cannot be set during product definition within PIM. Their values are specified only
by the down-stream execution systems. But users can modify certain metadata related
to these Transaction Attributes, and these modifications become specific to the
product for which it’s been done so. All TAs are grouped together in single page that
is displayed along with all the other UDA and Operational Attribute Pages.
3.2.3.2. Metadata Versioning
Versioning is the creation and management of multiple releases of an object, all of

which have the same general function. It allows users to keep and browse though the
object’s change history.
3.2.3.2.1. Value Set Versioning

Value Sets define a set of values, which can be associated with one or more attributes
so as to define the available list of values for that attribute.
By enabling versioning for Value Sets users would now be able to track changes to a
Value Set thru its various versions.
3.2.3.2.2. Item Catalog Category Versioning

Versioning has now been also enabled for Item Catalog Categories (ICCs). This
allows users to version ICCs and, therefore, to track changes being made to the ICC
with reference to Transaction Attributes and Associated Structures. This provides the
foundation for the ability to release products utilizing different definitions of catalog
categories and attributes.
For example, version 1 of a Transaction Attribute might have certain values (128
kbps, 256 kbps) while version 2 might include additional values (512 kbps, 1 Mbps).
Similarly, version 1 of an ICC might have only “Download Speed” as the
Transaction Attribute associated with it, while version 2 might also have another one
called “Upload Speed” added to it.
3.2.3.2.3. Transaction Attribute Update

Transaction Attributes are created and updated only within the context of the Draft
Version of an ICC. Any changes to the metadata of a TA or the removal of an
existing TA from an ICC definition can only be made in the Draft version of the ICC.
3.2.3.3. Product Structure for Item Catalog Category
Often products belonging to the same Item Catalog Category (ICC) have a similar
Product Structure associated with it. Prior to this release, users were required to
individually define these structures for each product, even though a majority of it was
common across the products.
With this release of PIM, users would have the ability to define a structure for an ICC
so as to be able to specify components that are common to all items created within
that ICC.
For example, a Telco operator might be selling a DSL service that has multiple
configurable models that share the same Modem, Router, Installation Options, and
Value added services. In such a scenario, a user can create an ICC and a structure
consisting of these components and then create new products or configurable models
of this category adding additional components that are specific to that new,
configured model or complex product.
3.2.3.3.1. Product Structure Inheritance

As mentioned above, users can define an ICC and use it as a template for building
products that have a common set of components. Any components specified for the
structure for an ICC would be inherited by any child categories of the ICC.
Users would have the ability to add additional components at the child categories.
However, any components or component attribute values that have been inherited
from the parent ICC cannot be updated at the child ICC level.
Once a Structure is specified at the ICC level, then any time a user tries to create the
same Structure for one of the items belonging to the ICC, the components specified at
the ICC level would default as components of the item along with any component
attribute values that have been specified. Users will be able to add more components
to the Item, in addition to the ones inherited from the ICC.
3.2.3.3.2. Updating ICC’s Product Structure

Similar to Transaction Attributes, structures for an ICC are also specified for a
specific version of the ICC. Hence any changes to the associated structure are only
possible by releasing a new version of the ICC. If user wishes to update the
associated structure, they would need to lock the ICC and make changes to the Draft
version of the ICC. Once all the changes have been made, user can release a new
version of the ICC with the modified structure.
The modified structure would be available for any new Items that are created within
the ICC as well as in any new Revisions of the Items belonging to the ICC. Any
existing Items will not be affected with these changes. Similarly, the modifications
would be inherited by the child ICCs only when new versions of the child ICCs are
released.
3.2.3.4. Pre-seeded Libraries
With this release of PIM a set of pre-seeded attribute groups, attributes and value sets
have been provided to manage the product information used by other execution
applications. These seeded attribute libraries based on PIM’s User-Defined Attribute
framework; help provide an easy extension to the product definition and modeling
capabilities within PIM. Once the attributes from the libraries are included within the
definition of an ICC, users will be able to provide additional product information and
behavior details as required by some of the downstream execution systems like
Seibel, Oracle Billing and Revenue Management (BRM) etc. during order capture,
fulfillment and billing.
A decision was made to use the user-defined attribute framework to provide an out of
the box definition for these new attributes, rather than adding them to the Item Master
definition. This provides the users the flexibility to choose any of these attribute
groups they would be interested in to model their business process.
The pre-seeded libraries are classified and named as follows:

• Sellable Product Information Library: This library deals with Promotion
and Product related attributes and has been classified as Horizontal. Any
cross-industry customers can uptake this library.
• Product Management Library: This library deals with general product
distribution related data and has been classified as Horizontal. Any cross-
industry customers can uptake this library.
• Communications Services Billing Library: This library deals with billing
related information and has been classified as Vertical. It was determined
that these attributes are the most commonly used by Communications
industry customers and this library requires additional licensing.
• Communications Product Details Library: This library deals with
attributes that allow for additional product definition that is most common in
the Communications industry. Since Communications industry customers
most commonly use these attributes, this library requires additional licensing.
3.2.3.5. Context-specific Information
Prior to this release most of the product definition that is done in PIM remains the same
irrespective of how the product or service or item was being used. To satisfy the need for
users to be able to define values or modify values or to make exclusions, under special
circumstances for specific events, there was a need for PIM to support context specific
information within an items definition or its usage in a structure.
3.2.3.5.1. Context-specific Item Transaction Attribute Value Sets
As discussed above, a Transaction Attribute can have a Value Set associated with it,
and thus a set of values. However, even though TAs can have values associated with
them through a Value Set, a user does not get to select a value in PIM for the item or
product. Within PIM, a Product or Item having a TAs will have all possible values
available as defined for the TA as per the current effective version of the Value Set.
These values are specified for selection in downstream execution systems, such as
Oracle’s Seibel CRM application.
Because these TAs are Item attributes, they are the same for a particular Item
Revision irrespective of where the item is used. So, if the same Item Revision were
included in a number of Item Structures, then for each structure the TAs available
and their values would be the same per the Item Revision.
However, users can exclude one or more values of an Item / Product’s TA values
within the context of a specific End Item. That End Item is the top-most parent item
to whose structure the item belongs that has the excluded TA values.
3.2.3.5.2. Context-specific Component Attribute Values

Component attributes are attributes defined on the relationship between a Parent and
a Component item. The component attributes are specific to the relationship type and
to the type of the structure. Therefore, all structures of the same type have the same
component attributes in all the structure relationships between any parent and child in
the structure.
The component attributes specified for a parent-component item remains the same
irrespective of if the parent-child relationship is used multiple times in a structure or
in structure of different items (e.g. a sub-assembly used in many assemblies). The
components attribute values would be the same in all instances where that parent-
child combination is used. This is due to the fact that the component attributes is
specific to the relationship of a specific component item with its immediate parent
item.
With this release of PIM, users have the flexibility to over-ride the component
attribute value for a component item in a parent-child relationship in the context of a
specific End-Item or Top Assembly item for a specific instance of the relationship.
Similar to the feature in the previous section, this changed value is only applicable in
the context of a specific End-Item and only for the specific instance of the
relationship. If the same parent-child relationship is used in another structure, the
component values should be what were originally set when the relationship between
the component and its Parent item was defined.
3.2.3.6. Publication Framework
The New Product and Service Launch business process involves the creation,
enrichment and publication of all product master data to a common product model
and syndication of the relevant information to various consuming systems. This is
achieved by publishing the appropriate product data at the right time and to the right
place leveraging the Application Integration Architecture (AIA) integration layer.
Even though this process flow can vary from one industry to another, but the
underlying integration flows through Application Integration Architecture (AIA)
would remain the same irrespective of the orchestration variants.
In this release of PIM, the product addresses publishing and synchronizing of two
key entities, Product Class/Catalog, which represents the product master data model
(modeled in PIM as a hierarchy of Item Catalog Categories, also known as the
Primary Item Catalog) and Product instances (modeled in PIM as Items and
Structures, referred to as Simple and Complex/Bundled products, respectively), from
PIM to all consumers of various facets of their definition.
3.2.3.6.1. Publishing of Item Catalog Categories (ICC) or Product Class

When publishing ICC (Product Class) information for a particular revision of an ICC,
PIM allows users to publish the entire definition of the individual category, including
Attribute Groups (including inheritances) and ‘Domain’ Value Sets associated with
the Attributes.
More precisely, the published payload includes only the following metadata:
• Category definition
• Associated Attribute Groups and Attributes
• Associated Transaction Attributes
• Value Sets linked to each Attribute
• Associated Structures
When publishing an ICC, PIM allows users to publish just the ICC and the ICC’s
‘genealogy’ in the form of its inverse hierarchy (parents and parents of parents) and
its hierarchy of child categories along with the definition of each category in the
hierarchy.
3.2.3.6.2. Value Set Publishing

With this release of PIM users now have the ability to publish one or more Value
Set(s) with their entire definition, including the ‘Domain’ Values associated with the
Value Set.
Specifically, Value Set publishing allows publication of:

• Value Sets associated with Transaction Attributes as part of an ICC
• Value Sets associated with Transaction Attributes independent of an ICC
• Value Sets associated with static Attributes as part of an ICC
• Value Sets associated with static Attributes independent of ICC
3.2.3.6.3. Publication of Items and Structures

As a part of the synchronization process between PIM and various other spoke
systems, users can choose to publish one or more Products or items to one or more
spoke systems. By selecting the different publication parameters users have been
given a lot of flexibility to choose what information of the item they want to publish
and as of when. This flexibility allows users to choose if they want to publish the
Items Structure or not and if so, till what level and effective as of what date.
The systems an item is to be published can be specified for the Item’s ICC. But at the
time of publication the user has the final choice of deciding which systems they
would like to publish the item’s information. They can go with the systems defined at
the ICC level or add or remove systems.
3.2.3.6.4. Publication History & Status
Each time a product or the metadata (ICC and Value Sets) is published, the system
creates a grouping for the entities published thru a common batch ID. Once the
publication process has been initiated, users can track the progress of publication
through the status of this Batch on the Publish History page.
The system maintains a unique status for each entity that was published in a batch for
each system it was published to. The user interface displays a log of each process
within the batch.
The messaging interface provided in PIM allows users to query historical publication
events for product / class data by user-defined criteria, such as batch ID, item /
revision, product class / version, target (spoke) system, etc.
3.2.3.6.5. Purge Publication History Log

PIM allows users to manage the size of Publish History Log by purging records that
are no longer required from time to time.
3.2.3.6.6. Publishing Security

PIM provides some basic security checks for the publication of Data. For the PIM
Metadata only users having the Functional role of having access to setup the
Metadata have been given the privilege to publish it.
For the publication of products or items, users need to have a special privilege to
Publish items. The right to Publish is controlled through this privilege such that the
publish action is only available to the user if they have this privilege in their role on
the item.
3.2.3.6.7. Web Services

A new set of web services to extract the metadata about Item Catalog Categories,
Value sets and also the Item and Structure data have been introduced in 12.1.2. The
web services can be used to retrieve the entities published as part of a batch or could
be used to retrieve the data about entities based on their identifiers. The web services
accept various configuration parameters to configure the level of detail returned in
the payload.
3.2.3.7. Automatic Import of Un-confirmed Items
PIM will now allow the automatic import of new, unmatched items without any
manual intervention. In Import Workbench, items imported from various sources are
matched and are combined to form a blended product record (single source of truth).
However, there can be many items that need to be created for the first time. When
items from various sources are added to a batch they are matched, provided the
option for matching is selected during import. Items for which no matches are found
have to be manually confirmed for import as new items. There could be a large
number of records for which this needs to be done, thus making the effort substantial.
An option will be available to the users where they can automatically confirm
unmatched items and import these as new items. This option will be provided at the
source system level, the batches level and during import thru excel.
3.2.3.8. Rules Framework Extensibility
Extensibility is being provided in the Rules framework, to allow validation rules that
reference attributes belonging to other entities than the one for which the rule is
written. For example, while executing a validation rule on an attribute in an item
supplier attribute group, it is desired that the rule should first assess an item attribute
to check if this rule should be run or not. An example would be, while updating the
item supplier Lead Time attribute for a specific item, there is a need to check the
item’s primary attribute "Status" value. If status is "Active" then attribute change
needs to be placed on a change order, otherwise the Item Supplier Attribute value can
be updated without any change order.
3.2.4. Release 12.1.3
In release 12.1.3, Product Hub has introduced the following features that are relevant
across different industries:
3.2.4.1. PIM to PIM Sync – APIs for Importing ICC and Value Set Metadata
A new concurrent program ‘EGO Import Metadata’ has been introduced to import key
metadata in product hub. The new concurrent program can be used to import the
following entities collectively or one at a time.
• Item catalog categories definitions
• Attribute groups and attribute definitions
• Value set definitions
The concurrent program imports the data through interface tables created to support
import of above entities.
3.2.4.2. Support for Images in BI Publisher (XML Publisher) Reports
Product Hub users will now have the ability to include images in BI Publisher reports for
images that are stored in the EBS repository. In PIM, images are added to items as
attachments. In the current release, the following attachment level images can be included
in the reports:
• Item level attachments

• Description level attachments (these are subset of Item level attachments)
• Item Revision level attachments
There will be no seeded Rich Text Format (RTF) templates delivered out of the box.
However, users will be allowed to create RTF based templates for the reports. An XML
Schema Definition (XSD) is shipped out of the box for users to map the RTF template
elements from XSD. Users need to configure the RTF template to map the XSD elements
to the appropriate report section as needed to print the images in the reports.
To avoid any performance issues in non-image report scenarios, users will have the
option to specify whether or not they want to see images in the report ‘Generate Report’
action. Based on the option selected by users, the image data will either be included or
not included in the XML payload. The following three options will be provided to users:
• Include Item level image

• Include Description level image
• Include Revision level image
3.2.4.3. Integration with Stellant/Oracle Universal Content Management (Oracle
UCM)
With the integration to Oracle Universal Content Management (Oracle UCM), PIM can
now provide extensive content management capability using UCM’s enterprise document
management repository. PIM users now have the ability to manage documents such as
word-processing files, image files, CAD 2D or 3D drawing files or any other
unstructured data in UCM repositories and attach them to various entities in Product Hub.
With PIM’s integration to UCM, users can now perform the following tasks:
• Upload a new file to a folder in the UCM repository and attach the file to an
entity within Product Hub.
• Attach an existing file/folder in the UCM repository to entities within Product
Hub.
• Render content of an attached UCM repository file from Product Hub.
• Detach files/folders from entities within Product Hub.
• Use the Where Attached feature to find all EBS objects to which a UCM
repository file/folder is attached.
3.2.4.4. Item Associations Enhancements
This release introduces new and enhanced APIs to support bulk load import capability
for:
• Related Items
• Item Cross References
Two new concurrent programs ‘EGO IMPORT RELATED ITEMS’ and ‘EGO IMPORT
X REF’ have been introduced to enable users to import Related Items and Item Cross
References into Product Hub.
These concurrent programs import the data through the new interface tables created to
support bulk load import of the above entities.
3.2.4.5. Lifecycle Phase Enhancement
You can now promote or demote an item to any other lifecycle phase within the
item's lifecycle. Previously, you could only promote an item from its current
phase to the next phase or demote it to the previous phase in the lifecycle. This
enhancement applies to both items and item revisions under lifecycle control.
3.2.4.6. Multiple Price List enhancement- Telco Enhancement
This release provides the ability to the Product Administrator in Product Hub to associate
a Siebel Price list name to a Rate Plan, which is associated with non-usage subscription
and item products. This applies to complex billing pricing model as well.
3.2.5. Release 12.2
In release 12.2, Product Hub introduces the following features that are relevant
across different industries:
3.2.5.1. PIM to PIM Sync – Publish/Synchronize Metadata
Product Hub (PIM) users can now synchronize the following entities from one PIM system
to another PIM system.
• Item Catalog Categories
• Attribute Groups
• Value Sets
Users can select multiple instances of an entity in a batch and synchronize the entities to
another PIM system. When syncing an ICC, users can also choose to sync the "Parent
ICCs" and "Child ICCs". Attribute Groups associated to the ICC and the Value Sets
associated to the Attribute Groups are automatically synced along with the ICC.
Users can track the Sync Status and History for all the entities and dependent entities where
applicable.
The PIM to PIM Sync feature leverages the existing PIM publication framework and the
EGO import metadata concurrent program.
3.2.5.2. Rules Framework Enhancements

The Rules Framework now supports the Item Revision business entity level. Users can
define the following types of rules on Item Revision level attributes:
• Validation Rules
• Assignment Rules
• Composite Rules
These rules enable the users to ensure data integrity for Item Revision level attributes.
In addition, Item Primary Attributes are now available as read only values for rule
evaluation at all business entity levels (Item, Item Revision, Item Organization, Item
Supplier, Item Supplier Site and Item Supplier Site Organization levels).
3.2.5.3. Public Item Search API

A new Item Search Public API is now available for users to perform simple and advanced
search. This API supports search criteria and display formats consistent with the UI based
search. The API also supports:
• Alternate Catalog/Category Search – ability to search for items assigned to a
specific alternate catalog/category.
• Cross-Organization Search – ability to search for items in a specific organization,
hierarchy of organizations, or across all organizations.
• Display of number UDAs in user UOM – ability to display number UDAs in a
UOM specified by the user.
• Support of multiple data levels for attributes in criteria templates and display
formats – support for Item, Item Revision, Item Organization, Supplier, Supplier
Site and Supplier-Site-Organization attributes.
3.2.5.4. Publish Workbench

From this release, from the Publish Batch Search page, you can perform the following
actions:
1) Search for batches using any of the following criteria:
• Batch ID
• Batch Name
• Object Name
• Published By
• Published Date
• Status
• System
• Workspace Name
2) Create a draft publication batch (for items, value sets, and attribute groups only).
3) Update a draft publication batch of items or metadata (item catalog categories attribute
groups, and value sets)
4) Merge publication batches (for items, value sets, and attribute groups only).
5) Delete a publication batch of items or metadata.
6) Publish a draft publication batch of items or metadata.
7) Copy a publication batch of items or metadata.
8) View the publishing history of items or metadata.
3.2.5.5. On-Demand Rule Set Execution

You can now use On-Demand Rule Set Execution to quickly select one or more items, then
apply item business rules to them.
Items can be searched using the same criteria when conducting a simple or advanced
search. The search results displays the items as well as the rule sets to apply to those items
before giving the opportunity to submit the rule set execution concurrent program.
The execution results display whether each item passed or failed any validation rules
applied, as well as any updates made to each item as a result of assignment rules applied.
3.2.6. Release 12.2.4

In Release 12.2.4, Oracle Product Hub is introducing the following features:
3.2.6.1. Support Time Picker within Date Picker
As part of 12.2.4 new UI features, users now have the ability to select time within
a Date Picker window.
Via this enhancement, new spin boxes are added for hour, minute and seconds
within the Date Picker window. Users can now choose the time to be entered.
Before this, when users chose a date from a Date Picker window for DATETIME
fields, the time component was defaulted to the current System Time.
3.2.6.2. Support Modal Popup Windows
In this Release Oracle Product Hub has taken up the Oracle Application
Framework feature of Modal Popup Windows. This feature allows the User
Interface to be simplified and allows users to complete their tasks with minimal
UI redirections.
By accessing the popup component users get to see requested contents via the
Modal Popup Window and need not be redirected to other pages.
This minimizes additional page refresh and operations
This feature has been implemented in the following pages-
• Item Workbench -> Overview -> Created By link, link on Hover
• Change Order -> Cancel(Action Dropdown, Go button) , button on Click
• Change Order -> Change Priority(Action Dropdown, Go button) , button on
Click
• Change Order -> Change Schedule Date(Action Dropdown, Go button) , button
on Click
• Change Order -> Promote(Action Dropdown, Go button) , button on Click
• Change Order -> Demote(Action Dropdown, Go button) , button on Click
• Change Order -> Hold(Action Dropdown, Go button) , button on Click
• Change Order -> Reassign(Action Dropdown, Go button) , button on Click
• Change Order -> Request Comment(Action Dropdown, Go button) , button on
Click
• Item Workbench -> Revisions -> Create/Update Revisions, button on Click
• Item Workbench -> Lifecycle -> Update Item Lifecycle Phase/Status, button on
Click
3.2.6.3. Support Value Set Security

In Release 12.2.4 Oracle Product Hub has taken up the Value Set Security enhancement
provided by ATG.
Value set security provides a way for System Administrators to implement security to
restrict users from adding or updating values in specific Value Sets.
In Oracle Product Hub changes have been made to the Value Set List Page, Value Set
Edit Page and Child Value Set Creation Page.
• List page: Added a security predicate to filter Value Sets that user accesses.
• Edit page: Added checks for Create/Update privileges and hid Value Set Values
for Create and Update Buttons.
• Child Value Set Edit Page: Added checks to Create/Update privileges and hid
Child Value Set values in shuttle region.
3.2.7. Release 12.2.5
3.2.7.1. Increase in Item Revision Sequence
As part of 12.2.5 there is an increase in the item revision sequence where maximum value
from Integer: 2147483647 is increased to Number: 4294967294. This is reflected in the
following User Interfaces:-
1. Web page UI
2. Form
3. WEBADI
4. API
5. PWB
6. Web service
7. Mobile Project: item Inquiry
3.2.7.2. New Modal Popup Windows Uptake

Prior to this Release the user was redirected to individual pages to view simple Product
Hub capabilities. This caused additional page refresh and operations. To resolve such
issues, in Release 12.2.5, Product Hub is using new popup component provided by OAF,
to help users see the contents without redirects to other pages. We are implementing this
in the following pages.
1. Setup Workbench -> ICC -> Item Pages -> Create Page
2. Setup Workbench -> Change Management -> Categories -> Change Type Info -
> Pages -> Create Page
3. Setup Workbench -> Structures -> Structure Info -> Structure Pages -> Create
Page
4. People and Roles -> Roles -> People -> people detail page
5. People and Roles -> People, Groups and Companies -> Company ->
Companies list -> company detail page
6. Change Order -> Post Comment (Action Dropdown, Go button) , button on
Click
7. Change Order -> Workflow, Statuses action (Demote, Promote)
8. Change Order -> Relationships -> Add Dependency
9. Change Order -> Relationships -> Add Reference
We also enabling auto-resize feature for the 12.2.4 modal popup pages.
3.2.7.3. Enabling NULL value search in advanced Item Search

In Release 12.2.5 users can search for NULL values for various attributes. They can also
save this search criterion for future use.
The existing behavior of item search will be retained.
3.2.7.4. Excel Support for Item Relationships
In this Release we are providing Excel Support for Item Relationships. In the past excel
import was available for entities like Item, Item Revisions and Item Org Assignment
From 12.2.5 we will provide support for Item Relationships.
3.2.7.5. Serial Tagging Changes

In Release 12.2.5 we are making the following changes to Serial Tagging
1) Existing check box “Serial Tagging at Issue” prompt is renamed as ‘Serial Tagging
Enabled’ in the Items (Forms and OA Page) and Item Templates UI. .
This field will be checked only when there is at least one serial controlled issue
transaction for an organization item in the Serial tagging assignments table
2) The existing Serial Tagging Assignments UI is enhanced to display the following
additional transactions for serial tagging –
• Sales Order Pick
• Internal Sales Order Pick
3.2.8. Release 12.2.6

3.2.8.1. Importing Product Structure/BOM Component Attribute Override Values

Users can now override structure component attribute values by exporting these values to
Excel, then importing them directly into the database. This feature enables users to do
overrides in bulk.
3.2.8.2. New Product Workbench Structure Search Filter Default Values

The default value for the Filter field has changed to Current and Future in the following
Product Workbench windows:
Copy Structure: Select Structures
Select structures to be compared
Since common structures include both current and future revisions, this default value
more accurately displays a common structure to be copied or compared.
3.2.8.3. Enabling Product Workbench JavaServer Page (JSP)
You must enable the Product Workbench if installing or updating Oracle E-Business
Suite to release 12.2.6 or later. To enable the Product Workbench, see:
• Allowed Resources, Oracle E-Business Suite Security Guide

• How To Enable Security For Product Workbench After Upgrade To 12.2.8
(Adding It To JSPs Allowed resources) (Doc ID 2536268.1)
3.2.8.4. Supporting Material Classification Tagging

Oracle Product Hub supports the new Oracle Inventory Management feature, Material
Classification Tagging. This feature enables you to set up material classification codes
and tag the material during picking or shipping.
3.2.9. Release 12.2.7
3.2.9.1. Multi-Row Attribute Advanced Search Results
In Item Search Results page, user can choose to view specific item information within a
show/hide region for each item. To activate the show/hide region, select the Details field
drop-down list. Then choose what is to be displayed in the show/hide region by selecting
AML (Approved Manufacturers List), Manufacturer Part Numbers, or an attribute group.
If user selects a multi-row attribute group in the Details field, then a Show Matched Rows
check box appears. If user searched on a multi-row attribute field value, then check this
box to view only the multi-row attribute values that match search criteria.
3.2.9.2. Filtering Multi-Row Attribute Values in an Item Page

User can filter multi-row attribute values from an item's Overview page. From an item's
Overview page, select an item page link. If the item page contains multi-row attribute
groups, then user can select a Show/Hide Filter link for each attribute group to filter the
multi-row attribute values that display.
3.2.10. Release 12.2.8
3.2.10.1. Item Global Flexfield

Item Global flexfield number of attributes are increased from 20 to 40. It now
supports requirements from Brazilian localization related to Public Digital
Bookkeeping System.
This feature is backported to 12.1.3+
3.2.10.2. Outsource Manufacturing for Process Manufacturing Items

Product Hub now allows items in process manufacturing organizations to be
defined as outsourced manufacturing enabled.
3.2.11. Release 12.2.9
3.2.11.1. Ability to un-assign item from child organization(s)

From the Organization Assignments tab in either Item Overview HTML page or
Master Items form, users can deselect one or more child organization assignments
for an item. This will launch a concurrent program to validate and delete the item
from those child organizations.
3.2.11.2. Support to update Item UOM

Users can update an Item’s primary unit of measure before performing any
transactions like material transactions, Sales Orders, Purchase Orders e.t.c. or
creating associated entities like Bills, Routings etc. This feature helps to reduce
data entry issues when items were originally created with an incorrect UOM.
3.2.11.3. Support to retain ECO information for BOM mass changes

In the Engineering Change Orders form, users will be able to query the
implemented mass change orders for bills of material and view their details.
3.2.12. Release 12.2.10
3.2.12.1. View/Edit/Upload multiple multi-row attribute groups in excel sheet

Users can select “Include All AGs” from Item Search Results page and export all
multi-row attribute groups into excel sheet. Users can view the multiple items
exported including multiple attribute groups for each item. User can edit and
upload the modified items including multiple multi-row attributes by importing
the excel sheet.
3.2.12.2. Allow User Defined Attributes with UOM to have LOV values
Users can now setup User defined attributes with UOM to have value sets. These
value set can be of validation type none, independent or table value set.
3.2.12.3. Support Translatable UDA length up to 4000 bytes

The length of translatable user defined attributes is increased to 4000 bytes.
3.2.12.4. Item Create and Update API available for Inventory IREP users
Users of Oracle Integration Cloud Service ICS EBS adapter, can now create
integrations with Oracle EBS Item Master. This integration can be done using
Item Master API available from Oracle Integration repository IREP for EBS
Inventory or EBS Product Hub.
3.2.13. Release 12.2.11
3.2.13.1. API / Interface made available for updating Customer Item, Customer
Item Cross reference and loading Manufacturer Part Number
Users can update the customer item and customer item cross reference through
API. An additional API is also provided to load Manufacturer Part Numbers.
3.2.13.2. Display of Item Name, Description, Long description, and ICC Name in
Item Search Results Page without trimming spaces.
PDH Item Search Results page will to be display Item Name, Item Description, Item
Long Description, Item Catalog Category Name without trimming the multiple spaces
between the text.
3.2.13.3. Public API for transferring engineering items to Manufacturing

Users can now transfer the engineering items, BOM, routing to manufacturing
using public API.
3.2.14. Release 12.2.12
3.2.14.1. Item Business Events Extended to Inventory Users

Inventory users can leverage business events to trigger events when a new item is
created, item is updated, items created/updated in bulk, item revision is
created/updated, or category is assigned/unassigned for an item.
3.2.15. Release 12.2.13
3.2.15.1. Associate Item Catalog Category (ICC) while Creating Items using Excel
Import
Now ICC can be made mandatory while creating the items using excel import by
turning on the profile option “EGO: Item Catalog Category required for Item
Import using Spreadsheet” to Yes. This will avoid user creating item without
associating the required ICC.
3.2.15.2. Support Status Change for an Item across Multiple Organizations

This feature allows user to change status of an item for multiple organizations
simultaneously using the new “Item Status Change Entry Across Organization”
Forms. This will improve productivity by avoiding user to change item status
individually for each organization.
3.3. Oracle Mobile Product Information for Oracle E-Business Suite

3.3.1. Discontinuation Notice
Oracle is discontinuing Oracle Mobile Product Information for Oracle E-Business Suite as
of August 3, 2018. Oracle will support this app, but will not deliver any new updates to the
app.
• The app will remain on the Apple App Store and Google Play with the latest client
version delivered, as long as technically feasible. Apple and Google may remove
apps that no longer meet their technical requirements.
• The corresponding MAA file for the latest client version is available on the Oracle
Software Delivery Cloud.
• Oracle will continue to deliver REST services for selected functionality in this app
for use in custom app development.
Customers who have installed this app will continue to receive technical support including
access to online support tools, knowledge bases, pre-existing fixes, and service request
resolution. As of August 3, 2018, error correction support will no longer be available for
this app.
Additionally, Oracle will not certify this app with any further operating system updates,
new devices, or new Oracle E-Business Suite releases after its discontinuation date. Oracle
will continue to assist you to the best of our ability; however, we are unable to provide any
new fixes.
3.3.2. Overview
With Oracle Mobile Product Information for Oracle E-Business Suite, product and supply
chain managers can quickly search and view product information on the go.
• Search or scan items

• Easily access favorite or recently viewed items
• View product operational and user-defined attributes
• View product images
• View suppliers and on-hand quantities in list or map
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Product Information for Oracle E-Business Suite 42
• View key transaction metrics, including open SO and PO quantities and open
work orders
• Personalize what information is displayed
• Collaborate in transaction context using device features (email, phone)
Oracle Mobile Product Information for Oracle E-Business Suite is compatible with
Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a user
of any Oracle E-Business Suite product that defines or uses items, with mobile services
configured on the server side by your administrator. Items are defined in an item master
organization to represent products and services you buy, sell, or otherwise transact.
3.3.3. Mobile Release 2.1 – Client Version 1.1.0
3.3.3.1. Mobile Foundation Updates

• Improvements in login and configuration flow
• Ability to change the URL without having to reinstall the app
• Diagnostics Improvements
3.3.3.2. Accessibility Improvements

There are accessibility improvements in the Oracle Mobile Product Information
Smartphone application:
• Improvements in springboard labels and Search LOV headers
3.3.4.1. Android Support

In previous versions for Oracle Mobile Product Information, Oracle E-Business
Suite was available only for iOS devices. Starting with version 1.2.0, the app is
now available for Android devices as well.
3.3.4.1. Mobile Foundation Release 3.0 Updates

• Changes to support both iOS and Android with the same client code
• Ability to update server URL from Connection Details page
3.3.5.1. Product Information and ERP Change Order Workflows

In this version the Oracle Mobile Approvals for Oracle E-Business Suite will
support PIM Change Order Approval workflows and ERP change Order
Approval Workflows
In the Oracle Mobile Approvals for Oracle E-Business Suite Notification List
you would be able to see notifications for both the ERP and the PIM Change
Order Approval Workflows
Upon clicking on one of these Workflows you will be taken to the Approval
Notification Header screen. This screen will provide the Notification Details.
From this screen you can either approve or reject the Notification or can get
further information on Revised Items, or view the Action log.
The Revised Items screen and the Action log screen also provide the ability to
either accept or reject the Notification
3.3.5.2. Item Attachment Support

In this Release PIM has taken up the ATG common component for attachments.
Till now you could see just the item overview image, but now item level
attachments are supported as well
3.3.5.3. Ability to add or remove an Item from the Favorite List

From this release onwards you would have the ability to add or remove an Item
from the Favorite List. The Favorite Items List is shared between the Oracle
Mobile Product Information for Oracle E-Business Suite and the HTML
Application.
3.3.5.4. Translation Support

This app is available in the following languages:
Brazilian Portuguese, Canadian French, Dutch, English, French, German, Italian,
Japanese, Latin American Spanish, Simplified Chinese, and Spanish.

• Support for enterprise distribution
• Customization support for corporate branding
• Support for Web SSO authentication to delegate authentication to Oracle
Access Manager (OAM)
3.3.6.1. View ICC in Overview page

From this release, Products app has ability to view Item Catalog Category in the
Item Overview page.
3.3.6.2. Enhanced data security check in Overview page Metrics tab

From this release, the data showed in Metrics tab in item overview page honors
the same security level as of in EBS HTML UI.
3.3.6.3. Enhanced on hand quantity in Overview and Detail pages

From this release, the item on hand quantity information is presented in a better
manner.
3.3.6.4. Hid attachment link in Overview page when there is no attachment
From this release, the attachment link would not be shown for an item where no
attachment exists.

• User installation and usage metrics for administrators
• Updated look and feel for selected app interactions
• Technical updates with uptake of Oracle Mobile Application Framework (MAF)
2.2.2

• Ability to open links to external websites within the app on iOS devices
3.3.8.1. Ability to upload image for item in overview page and attachment list
• From this release, item level image could be uploaded from mobile app.
• The item attachment access privileges honor the security setup in EBS.
3.3.8.2. Ability to assign mobile specific role to non-EGO responsibility

• From this release, the UMX|PIM_RESTFUL_SERVICES_ROLE mobile specific
role could be assigned to non-EGO responsibility.

• Ability to open links to external websites within the app on Android devices
• Updated look and feel, including native look and feel for action sheets on iOS
devices
• Ability to easily clear user credential fields in the Sign In page
2.3.1

• Ability to import custom CA or self-signed server certificates to standard apps
for TLS connections to Oracle E-Business Suite
• Ability to download the mobile app configuration automatically from the server
2.4.0
3.4. Oracle Site Hub
3.4.1. Overview
Oracle Site Hub is an enterprise site lifecycle management solution that enables
customers to consolidate all site-specific information from heterogeneous systems,
creating a single source of truth of site information that can be leveraged across all
functional departments.
Oracle Site Hub helps customers eliminate site data fragmentation, a problem that often
results when companies participate in a merger or acquisition, extend their business
globally or rely on non-integrated legacy or best-of-breed applications.
3.4.2. Release 12.1.1

3.4.2.1. Site Creation and Maintenance
To initiate and capture a site’s lifecycle in a business application, an organization first
needs to create the site, e.g. retail location, manufacturing plant, office, warehouse,
distribution center or kiosk. Site Hub provides organizations the ability to create sites and
capture all related information using the following multiple methods.
3.4.2.1.1. Manual Site Creation
For organizations with a smaller number of sites the preferred method to create a site
is manual entry of the entire site related information. Site Hub allows a user to
manually create a single site by simply logging on to the application and capturing
the necessary site related information in a HTML user interface.
3.4.2.1.2. Site Creation using Templates
For organizations such as retailers or banks, which have a collection of stores or
branches that are similar in size, store layouts, merchandise carried and/or services
offered, Site Hub offers a more efficient method of creating these sites with
templates. A template contains a preconfigured site that serves as a blueprint for all
comparable sites. When creating sites with similar attributes, creating the site from a
template that has the same definition is easier than creating and entering all
information manually for each site. Site Hub allows users to create new sites by
copying all or selected attributes from predefined templates.
3.4.2.1.3. Site Creation by Copying an Existing Site
When creating new sites with similar attributes, many organizations will prefer to
create new sites from predefined templates; however, there may be organizations that
prefer to copy an existing site to create a new site rather than define templates for site
creation. Site Hub enables users to create a new site by copying all or selected fields
from an existing site. While similar to using a template, the site definition is derived
from an existing site rather than from a template.
3.4.2.1.4. Site Creation using File Import (Bulk Site Creation)
Manual creation of sites is a labor-intensive process for organizations with a very
large number of sites. Organizations such as retailers or hospitality chains, which
have thousands of sites and are constantly expanding by opening a few hundred sites
every year will prefer a more streamlined way of creating the sites. Hence, Site Hub
offers the ability to create multiple sites easily using a Microsoft Excelbatch file
import process.
3.4.2.1.5. Site Maintenance
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Site Hub 46
Once the sites are created in Site Hub, the users can maintain the sites in two ways.
Changes to a single site at a time can be accomplished using the HTML user
interface. Updating of multiple sites is possible by exporting the relevant site into
Microsoft Excel, followed by making changes in Excel, and then uploading the
changes from Excel into Site Hub.
3.4.2.2. Site Attributes
For any site that an organization owns, leases or is evaluating, the organization has the
ability to capture all information about a site to assist the organization with business
decisions. Site Hub allows organizations to capture associated site attributes for all
functional areas including business characteristics, physical characteristics, financial
information, competitive information, demographic data, etc. Organizations have the
ability to define attributes specific to their business requirements. These can be used in
downstream processes to assist business users in a variety of tasks.
3.4.2.3. Simple and Advanced Search
Searching for available sites in Site Hub is possible in two modes, Simple Search and
Advanced Search. Simple Search allows users to quickly search for sites based upon site
identification information. For users interested in performing more complex searches,
Advanced Search provides the ability to perform parametric search by selecting one or
more site attributes. Additionally, Advanced Search also allows the use of various search
qualifiers such as begins with, contains, matches, etc. to make the search more focused.
For users who need to perform complex searches on a regular basis, Site Hub allows
users to pre-define one or more search criteria and save the criteria for later use. Users
can also pre-define the format in which the search results will be displayed.
3.4.2.4. Site Clusters
A cluster is an assortment of sites that are grouped together based on one or more shared,
i.e. common, characteristics. Site Hub allows users to group multiple sites into
meaningful clusters for use at a later time in other business functions. There is neither a
limit to the number of clusters users can establish nor a limit in the purposes or uses to
which these clusters might be used.
3.4.2.5. Site Hierarchies
A hierarchy is a classification of relationships in which each node except the top one is a
specialized form of the node above it. Each node can have one or more nodes below it in
the hierarchy. Site Hub allows users to define various hierarchies as needed for their
business. Once hierarchies are defined, users can associate sites at any node of the
hierarchy. There is neither a limit to the number of hierarchies users can establish nor a
limit in the purposes or uses to which these hierarchies might be used.
3.4.2.6. Site Mapping
A geographic location, i.e. an address, is associated with each site. While playing a
major role in the site selection process, the geographic location of the site is also an
important component of ongoing business processes such as merchandise selection,
revenue forecasts, competitive analysis, marketing, etc. Users have the ability to view
sites on a map using Google Maps embedded in Site Hub. Trade areas leveraging
geospatial data for a selected site are available as overlays on the map.
3.4.2.7. Web Services
Web services capability is provided for select business objects and functions, e.g. to
create and update limited site data, and to associate existing hierarchies, trade areas
groups and clusters. Web services in Site Hub launches the technology roadmap for a
service-oriented architecture allowing other applications, including third party
applications, to leverage the functionalities of Site Hub.
3.4.2.8. Publication
This release includes business events for publishing data from Site Hub.
3.4.2.8.1. Business Events
Business events are raised whenever a site, hierarchy or cluster is created or updated
as well as for pre and post update of site attribute groups. In addition, a new business
event is raised whenever there is a bulk upload of sites via Web Applications
Desktop Integrator (Web ADI). All the events are lightweight i.e. minimal number of
attributes is passed when an event is raised.
3.4.2.9. Trading Community Architecture
Trading Community Architecture (TCA) supports linking any and all types of
relationships to a single representation of an entity, e.g. a party associated to a site. Site
Hub will leverage relevant TCA entities and relationships, e.g. Party, Party Sites and
Locations.
3.4.2.10. Integration with Inventory
Site Hub provides out of the box integration with Oracle Inventory for organizations to
keep track of their inventory specific to a site. In that respect, Site Hub provides a
mechanism to automatically create an inventory organization for that site in Oracle
Inventory. Users can also create maintenance organization associated with the site in the
same flow. This automated process would make the implementation of Oracle Inventory
and Site Hub efficient and more streamlined for an organization.
Users can drill down into Oracle Inventory directly from Site Hub to manage the
inventory organizations associated with a given site.
3.4.2.11. Integration with Property Manager
Site Hub provides out of the box integration with Oracle Property Manager for
organizations to keep track of their properties and leases specific to a site. For
organizations also using Oracle Property Manager to keep track of their location-related
transactions at a given site, Site Hub provides a mechanism to automatically create
property location for a site for a selected property.
Users can drill down into Oracle Property Manager directly from Site Hub to manage the
property locations associated with a given site.
3.4.2.12. Integration with Enterprise Asset Management
Most of an organization’s sites have assets that require continued maintenance to prevent
interruption of the business functions being performed at these sites. For example,
retailers have assets such as cash registers, fixtures, refrigeration units, HVAC units, etc.
that require maintenance as well as required maintenance for the facility itself. For sites
that require maintenance management, an organization will also be able to use Oracle
Enterprise Asset Management to manage the assets at these sites. An organization will be
able to use the Site Hub to perform additional downstream setup required to make a site
maintenance enabled, including creating or assigning maintenance organizations, copying
maintained groups and activities, searching and viewing maintenance organization
information, managing maintenance organizations, viewing asset hierarchy, and
managing asset maintenance.
3.4.3. Release 12.1.2
3.4.3.1. Enhanced Hierarchy Management

Release 12.1.2 introduces superior site hierarchy management capability.
.
3.4.3.1.1. Enhanced relationships- site-to-site and site-to-node
For organizations with a large number of sites, there often exists a need for parent-
child relationship amongst the sites. This feature provides the ability to create the
site-to-site as well as site-to-node relationships in the context of a hierarchy. Sites in
a hierarchy can be related amongst themselves as well as be part of a node that may
contain more sites and nodes.
3.4.3.1.2. Rules framework for hierarchy management
Using this feature, user can define the relationship rules between sites and nodes in a
hierarchy. Rules can be defined utilizing the ‘site/node purpose’ associated with each
site/node. The relationship rules would limit the possible associations between
different site/node types identified by their purposes. Two examples of relations rules
are given below
1. Sites of purpose ‘Shopping Mall’ can only be a parent to sites of purpose
‘Shop’
2. Nodes of purpose ‘Apparel Shop’ can only be a parent to sites of purpose
‘Kids Apparel Shops’
3.4.3.1.3. Hierarchy manipulation Rich User Interface

This feature brings in a rich user interface, drag & drop feature for enabling an
efficient and user friendly mechanism of hierarchy manipulation. Users have the
ability of rich UI features for site hierarchy manipulation including
• Ability to manipulate multiple hierarchies in a single UI
• Ability to order sites and nodes in a persistent sequence
• Ability to create parent-child relationships between sites and nodes
• Add parent/child site/node
• Create new site/node
• Drag and drop site and node within and across hierarchies
• Right mouse button click pop-up menu for hierarchy manipulation actions
• View configurable site and hierarchy attributes within the UI
• View configurable icons for sites and nodes
• Perform quick search for any hierarchy or hierarchy elements
3.4.3.1.4. User defined attributes for hierarchies

With this release, comes the ability for users to add unlimited user defined attributes
(UDAs) to the hierarchy entity to define the various characteristics of the hierarchy.
Also added is the concept of hierarchy purpose. This provides the ability to
categorize any hierarchy and its attribute structure. In addition, advanced search
capability including UDA attribute search that was available for sites is extended to
hierarchies as well.
3.4.3.2. Bulk Site Import Interface

Bulk site import interface provides the ability to carry out high speed site data import.
During the import process data is first validated in the interface tables and on successful
validations, moved to the base tables. Invalid rows of data are copied over to error log
with appropriate error message. The invalid rows can be corrected and resubmitted for
processing. This feature is very useful for loading voluminous data sets to the application
during initial implementation as well as on an on-going basis as needed.
3.4.3.3. Capture of Longitude/Latitude for Sites
Now it would be possible to manually capture the latitude/longitude of any site in Site
Hub. This is very important for sites which do not have assigned postal address.
Examples of such a site would a telecommunication tower, postal delivery mail stop etc.
It would also be possible for sites in Site Hub to exist even if the site does not have a
street address associated with it. This solves the problem in mastering prospective sites,
virtual sites and physical sites whose precise postal address is yet to be assigned.
Also added is the capability of automated site numbering, thereby enhancing user’s
ability to manage sites much easily. The automated site numbering is effective
irrespective of the method of site data load whether it is through bulk load, web services
or input through the application UI. Users can take advantage of this feature to arrange all
their sites with the auto assigned site numbers. However, if users already have site
numbering, they can keep using that too.
3.4.3.4. Creating My Favorites

My favorite allows an end user to bucket his/her favorite sites, hierarchies and clusters
for easy access. When a user logs in, s/he can have his/her favorite sites, hierarchies and
clusters show up. This is a productivity enhancement as user does not have to search for
his/her sites or hierarchies of concern every time.
3.4.3.5. Web Services for Hierarchy Manipulation

To SOA enable the hierarchy manipulation capabilities, a comprehensive set of web
services have been provided including coarse and fine grain web services for creating,
updating and querying site hierarchies. The create and update hierarchy services allows
users to create/update a hierarchy with nodes and sites, create a hierarchy node and
update the hierarchy header information including hierarchy name, description, start date,
end date, etc .With the query web service, users can get information about the hierarchy
header, the hierarchy members and the attributes of the hierarchy.
3.4.4. Release 12.2

In release 12.2, Site Hub introduces comprehensive security features with roles
based access control for key business entities and attributes within those entities.
Access is restricted via user privileges and roles to users or user groups.
• Privilege: It defines the user’s ability to access an object such as a site

record or a hierarchy. For example, user’s ability to view a site record or
edit a site record is determined by user’s privilege to that record.
• Role: A role is a collection of privileges that can be applied to a user or
user group. Roles are a convenient way to group privileges into a bundle
so that it can be assigned to user or user groups. Roles are object specific.
o E.g. - For the role ‘Tax auditor’ the privileges assigned are view
and edit the attribute group ‘tax information’.
• User Groups: In order to manage user roles and assignments easily, user
groups can be created. Individual users can be assigned to one or more
user groups
o E.g. - all real estate managers can be grouped into one user group.
These features are relevant across all industries.
3.4.4.1. Rules Based Access Control for Sites and Hierarchies

This feature restricts access to Sites and Hierarchies via user privileges and roles. Role
assignment rules allow users to secure object access by individual site or hierarchy.
Accesses rights include create/update and view of individual sites and hierarchies.
For example:
• User A can only view sites of a specific brand; however s/he can edit sites of
another brand.
• User Group G can only create/update sites of another brand. Members of this
user group cannot view/edit/create sites of any other brand
Broader criteria’s are available for defining access rules.
3.4.4.2. Roles Based Access Control for Site and Hierarchy Attributes
Along with securing key business objects including sites and hierarchies users will now be
able to implement roles based access control for securing user defined attributes (UDA’s)
of sites and hierarchies.
E.g. - If a particular user should not be allowed to access financial lease terms of a site
which are stored as an UDA attribute group named ‘Financial Lease Terms’, then that
access can be secured by assigning appropriate privileges about the attribute group to the
concerned user.
Security for view and update privileges for site and hierarchy attributes are implemented
across all points of data entry including web user interface, excel upload through web ADI,
web services and bulk import interface.
3.4.5. Release 12.2.5
3.4.5.1. Geo-fencing Enhancement

In Release 12.2.5 we are introducing a new feature via which the user can create a
polygon site on Google Maps
By using polygon sites, the customer can define coverage areas where their services are
provided.
These coverage areas are broadly used by retailers, postal services, garbage services gas
& electricity providers, etc. to find potential clients and define expansion strategies.
To find out if a potential client falls within the coverage area, the customer can now
query coverage area for a given address.
Via this enhancement the user would be able to
• Create and view polygon sites on Google Maps.
• Do a Bulk import of polygon sites to Oracle Site Hub.
• Query coverage areas for a given address.
3.4.5.2. Expose Source System References

In Release 12.2.5, Source System References will be exposed on the Site Hub User
Interface.
Source System References for Sites
Now the user can create and maintain source system references for each Site.
Importing Source System References
When importing Site data, the application would allow importing source system
references for the Sites.
3.4.6. Release 12.2.12
3.4.6.1. Site Hub Hierarchy Workbench Revamped with Oracle JET Technology
As Adobe Flash is deprecated, Site Hierarchy workbench is developed using

Oracle JET Technology. New workbench UI works with any EBS supported
browsers.
3.5. Oracle Supplier Hub
3.5.1. Overview
Oracle Supplier Hub is a new application that provides a portfolio of Master Data
Management tools to enable organizations to better manage their supplier master records.
Built on the foundational technology used to support mastering of customer information,
Supplier Hub will be used by both organizations that need to aggregate supplier data from
a range of application systems and also by those running a single E-Business Suite
instance.
It provides comprehensive functionality to manage supplier data: consolidating supplier
information from disparate systems and business lines into one repository, cleaning and
enriching data centrally, and providing the resulting "single point of truth" data as a
service to consuming applications, enterprise business processes and decision support
systems.
Deployment of Supplier Hub will enable organizations to have a consistent understanding
of the trading partners that they use to procure the various goods and services required to
support their business. This clarity is essential in order to be able to carry out effective
analysis of spending patterns so that appropriate tactical and strategic decisions can be
made about company procurement policies.
In order to ensure that customers are able to manage supplier records across their
organization, Supplier Hub supports a variety of deployment modes.
Standalone Mode - Separate E-Business Suite Instance
This is the traditional Master Data Management deployment mode – the Supplier
Hub is set up in a separate instance and vendor data from an organization’s source
systems is loaded into the Hub in order to be mastered.
Integrated Mode – Existing E-Business Suite Instance
This configuration allows a customer to run the Supplier Hub functionality as part of
their existing E-Business Suite R12.x transactional instance.
Note: The product is referred to as Supplier Hub Add-on for E-Business Suite when
it is licensed as an option as part of an existing E-Business Suite install.
Mixed Mode
This hybrid setup is essentially an extension of the Integrated Mode in that it allows
customers to run the Hub as part of their existing E-Business Suite instance and at the
same time, feed it with additional supplier records from other legacy systems for the
purposes of mastering the details across all of those systems.
3.5.2. Release 12.1.3
3.5.2.1. Supplier Master Profile

Supplier Hub allows an organization to gather all of the key details they store about their
vendors from across all of their heterogeneous environments and store them in a central
repository. Given the wide range of information that Purchasing and Payables
departments need and wish to maintain, the Hub has been architected to allow data across
a range of categories to be stored.
Supplier Identity
This refers to the attributes that uniquely identify an individual supplier - primarily
the supplier name and tax reference id/number(s).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Supplier Hub 53
Supplier Business Details
These are the attributes that are typically required to be able to do business with the
supplier and so provide the more granular details about a supplier’s identity, such as
location, contact and bank account information
Supplier Profile Details
These are the pieces of information that identify the characteristics of the supplier,
and can range from things like the corporate structure of the supplier, names of C-
level officers through to the goods and services they can provide, classifications that
apply to them and 3rd party credit risk information
Supplier Control Details
These are the flags and settings that are used to manage the business relationship for
order collaboration, receiving, invoicing and payment between the buying
organization and the supplier
For the initial release of Supplier Hub, all data categories can be managed using the
Integrated deployment mode and Identity, Business and Profile category details will be
supported for the Standalone and Mixed deployment modes.
3.5.2.2. Extended Supplier Profile

To better understand the capabilities of suppliers in key product categories, and to track
subjective information about how that supplier is performing, buying organizations need
to be able to store a wide range of additional details in their supplier master. Typically,
this is the sort of information that is gathered by different departments and stored using
paper-based systems, preventing an organization from using the details to gain a better
insight into a supplier’s performance.
Supplier Hub utilizes User Defined Attribute technology that allows administrators to add
an unlimited range of attributes to the supplier definition and to group these into logical
Profile sections. In addition to the attribute name, administrators are able to add
descriptive text to help explain the purpose of the attribute.
The extended profile attributes allow disparate details to be imported from a variety of
source systems or for the Hub to be used to capture and store this information centrally.
Fine-grained access control tools allow administrators to manage which users can have
access to the individual attributes in the extended set of profile details. This is a key
feature when sensitive information is stored in the profile and access need to be restricted
to appropriate users either internally or at the supplier.
3.5.2.3. Enhanced Supplier Classification

It is becoming increasingly important to a large number of organizations to be able to
track classification and diversity information across their supply base in order to ensure
that spending patterns can be matched to Corporate Social Responsibility goals.
To allow organizations to track a wide variety of classification & diversity information
about their suppliers, the Hub enables administrators to define multiple classification
schemas. This information can then be used when building reports to track spending
patterns.
3.5.2.4. Supplier Hierarchy Management

A crucial part of supply base analysis is to understand the relationships that exist between
the different suppliers that are doing business with different parts of the buying
organization. This allows an organization to leverage aggregated spend information
within the negotiation process with the supplier.
Supplier hierarchy management functionality within the Hub provides the ability to
identify Parent and Child supplier company relationships across all of the supplier
records that have been consolidated from the different systems within a company.
In addition to the basic parent /child relationship, the Hub allows business users to define
an unlimited number of custom supplier relationship types and then use these to track
relations between different suppliers. The custom hierarchy information can be viewed
in a tree structure and can be utilized for various reporting and supplier management
purposes.
3.5.2.5. Data Import & Source System Management

Supplier Hub provides an Import Workbench to allow administrators to setup and control
the process of consolidating supplier records from any spoke applications or systems
running within the organization.
The Import tools enable supplier Identity, Business, and Profile Details from multiple
spoke/source systems to be cross-referenced. Batch Management capabilities then allow
the administrator to control the loading of the imported supplier data into the Hub
repository.
The initial release of the Hub will support backend concurrent program import for
Identity, Address, Contacts, General Classifications and User defined profile attributes.
3.5.2.6. Data Quality Management

A critical element of an administrator’s role in managing supplier data is in dealing with
duplicate supplier records and establishing processes to prevent duplication in the first
place.
The Data Quality Management (DQM) functionality incorporated into Supplier Hub
provides features that allow an administrator to carry out systematic de-duplication and
cleansing of supplier Identity, Business and Profile Details. The DQM tools have also
been incorporated into the supplier creation flows that are supported by the Hub to
prevent the setup of multiple records for the same supplier.
DQM provides tools to setup match rules and other data quality setups required for
performing de-duplication tasks. It also provides tools for blending of the supplier
records to harmonize the information about a single supplier that exists in multiple source
systems.
It provides tools for automatic identification of potential duplicate supplier records in the
system in order that administrators and business users can take further data quality
actions as required.
3.5.2.7. Data Enrichment using D&B Integration

The Supplier Data Enrichment functionality provides features that allow organizations to
enrich the profile information they are maintaining for a supplier by pulling detailed
information from D&B. Information packets for a supplier(s) can be gathered during the
supplier registration process and also as part of general supplier profile management.
Administrators or business users are able to interactively search the D&B repository and
order/purchase various D&B products to enrich the Supplier information.
3.5.2.8. Data Publication and Synchronization
One of the primary reasons for deploying Supplier Hub is to establish a single definition
for each supplier and then to make sure that this representation is used across all of the
systems operated across the organization.
The Supplier Data Publications feature set provides the capabilities to integrate Supplier
Hub with other spoke systems. It provides the infrastructure to raise the necessary
business events to trigger publication of updated supplier information and APIs that can
be used by spoke systems to query and consume the updated supplier information. It also
provides APIs for querying potential duplicate supplier records in the hub and for
processing the source system supplier information into the hub.
3.5.2.9. Unified Supplier Profile Business Event

A new business event, Unified Supplier Profile Business Event has been introduced in
this release.
This event will be raised whenever a supplier or any of its entities -address, site, or
contact are created or updated.
The event parameters will contain the details on the supplier and the entity which raised
the event.
In the past there was inconsistent behavior with regards to business events for different
attributes and users had to subscribe to several events. Not so anymore.
The other flows that also raise this event are-
• Supplier Import
• Supplier Merge
For User Define Attributes this event will not be raised.
3.5.3. Release 12.2.4
3.5.3.1. Supplier Merge

In release 12.2.4, Oracle Supplier Hub enhanced the Supplier Merge functionality by
providing the capability to merge Suppliers and Supplier Sites in the OA Framework UI.
Supplier Merge Pages
2 new pages can be accessed via Supplier Data Librarian Super User Responsibility
and by going to the Supplier Merge sub tab under Data Quality-
• Supplier Merge Summary Page
• Create Site Merge Request Page
The user first creates and generates a batch on the Supplier Merge Summary Page
and accesses the Create Site Merge Request Page.
The Create Site Merge Request Page replicates the functionality of Oracle Payable’s
Supplier Merge Form.
After a Batch has been created and generated, the user can choose whether to transfer
invoices/POs, the source/destination of the transfer, and whether to copy to a new site
or to an existing site between Suppliers.
He then clicks the Submit button to submit the Supplier Merge and generate the
Supplier Merge Request Concurrent Program.
Once the Supplier Merge is successfully done, the user can access the Party Merge
functionality and create a Party Merge.
Supplier Merge Request concurrent program
This Concurrent Program is launched when a Supplier Merge batch is submitted.
The program validates records in the batch and updates batch status, then calls
Payable’s Supplier Merge program in a loop to process each row in the batch.
If there is no error, Supplier Sites are merged, and Suppliers become ready for Party
Merge.
3.5.4. Release 12.2.5
3.5.4.1. Supplier Source System References

Before Release 12.2.5, Source System references can only be maintained at the supplier
level
In release 12.2.5, Oracle Supplier Hub is exposing Source System reference at the
following level as well –
Source System References for Supplier Address

Buyer users would now be able to create and maintain source system references for each
supplier address.
When the user imports supplier data via the Integrated Supplier Import Program, source
system references for supplier addresses would be imported as well.
3.6. Supplier Lifecycle Management
3.6.1. Overview
In addition to the Supplier Hub capabilities for mastering supplier records, many
organizations also need tools that will help them exercise proper control over suppliers
throughout the lifecycle of the relationship between the two parties; from initial
discovery, through qualification and on-boarding, to ongoing maintenance and possible
obsolescence.
Oracle Supplier Lifecycle Management (SLM) is a new application that provides an
extensive set of features to support the qualification, profile management and
performance assessment of suppliers as well as tools to track ongoing supplier
compliance with corporate and legal requirements.
A key factor in improving the quality of an organization’s supplier master file is to
establish proper processes to formally qualify different types of prospective suppliers and
to proactively maintain their profile information. Oracle Supplier Lifecycle Management
enables any and all of the peculiar information required to assess a prospect to be
gathered and then routed through the organization to ensure efficient review of the
supplier’s credentials. Once approved, SLM also allows ongoing feedback to be gathered
about the supplier from key stakeholders in the organization as part of an overall supplier
performance tracking process.
3.6.2. Release 12.1.3
Oracle Supplier Lifecycle Management provides the following set of features:
• Supplier Registration and On-Boarding
• Supplier Profile Management
• Supplier Qualification Management
• Supplier Compliance and Profile Audit
• Supplier Performance Evaluation
• Supplier Notifications
Full details about the capabilities of the Supplier Lifecycle Management application can
be found in the Advanced Procurement Release Content Document.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Supplier Lifecycle Management 58

EBS 122 Cum RCD MDM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS 122 Cum RCD MDM

Uploaded by

Copyright:

Available Formats

ORACLE E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Master Data Management

Prepared by Oracle E-Business Suite Product Development

Last Updated: November 17, 2023

Copyright © 2011, 2023, Oracle and/or its affiliates.

2.1. Purpose of Document

3.1. Oracle Customer Hub (CDH)

3.1.2.4. Improved Performance of System Duplicate Identification Tab

3.1.3.1.2. Web Service to retrieve the details of a customer party merge

3.1.3.2. DQ Enable Web Services

3.1.3.5. Time Zone for Resource Group

3.1.4. Release 12.2

3.1.4.2. Real-Time Address Validation

3.1.4.3. Enhancement to Customer Import

3.2.2.3.1. Managing Item Assignments to Organizations

3.2.2.7.5. Multiple Items on a New Item Request

Logical and, or, not

3.2.2.17.5. Security Inheritance based on Style – SKU Item Relationship

3.2.2.20.3. Post – Processing of Inbound Data

3.2.3.1. Transaction Attributes

Some product characteristics are represented by attributes whose values belong to a

3.2.3.1.1. Transaction Attributes Definition

3.2.3.1.2. Transaction Attribute Metadata

3.2.3.1.3. Inheritance of Transaction Attribute and Attribute Metadata

Child ICCs can have two kinds of TAs:

3.2.3.1.4. Privileges for Transaction Attributes

• Privileges at the ICC Level:

• Privileges at the Product Level:

3.2.3.1.5. Transaction Attributes within a Product

3.2.3.2. Metadata Versioning

Versioning is the creation and management of multiple releases of an object, all of

3.2.3.2.1. Value Set Versioning

3.2.3.2.2. Item Catalog Category Versioning

3.2.3.2.3. Transaction Attribute Update

3.2.3.3. Product Structure for Item Catalog Category

3.2.3.3.1. Product Structure Inheritance

3.2.3.3.2. Updating ICC’s Product Structure

3.2.3.4. Pre-seeded Libraries

The pre-seeded libraries are classified and named as follows:

3.2.3.5. Context-specific Information

3.2.3.5.2. Context-specific Component Attribute Values

3.2.3.6. Publication Framework

3.2.3.6.1. Publishing of Item Catalog Categories (ICC) or Product Class

3.2.3.6.2. Value Set Publishing

Specifically, Value Set publishing allows publication of:

3.2.3.6.3. Publication of Items and Structures

3.2.3.6.4. Publication History & Status

3.2.3.6.5. Purge Publication History Log

3.2.3.6.6. Publishing Security

3.2.3.6.7. Web Services

3.2.3.7. Automatic Import of Un-confirmed Items

3.2.3.8. Rules Framework Extensibility

3.2.4.2. Support for Images in BI Publisher (XML Publisher) Reports

• Item level attachments

• Include Item level image

3.2.4.4. Item Associations Enhancements

3.2.4.5. Lifecycle Phase Enhancement

3.2.4.6. Multiple Price List enhancement- Telco Enhancement

3.2.5.1. PIM to PIM Sync – Publish/Synchronize Metadata

3.2.5.2. Rules Framework Enhancements

3.2.5.3. Public Item Search API

3.2.5.4. Publish Workbench