Fusion PIM

8/12/2019 Fusion PIM

1/28

">

Fusion PIM: Common Problems and Solutions - Define Catalogs / Catalog Setup [ID 1391190.1]

Modified28-MAR-2012 TypeFAQ StatusPUBLISHED

In this DocumentPurposeQuestions and Answers

Summary:Common Problems:

Unable to create a catalog, the catalog structure list of values is blank in the Create Catalog dialog.Unable to create a category and the category structure segments values are not listed in the Create Category dialogUnable to assign catalog to a functional area in the Manage Default Catalog page.Unable to re-assign a catalog to a functional area in the Manage Default Catalog page.Unable to find my catalog in the Manage Catalog page.Unable to find my category in the category hierarchy table or the Add Category search and select dialogs.Unable to download data from the catalog into a spreadsheet, the spreadsheet is launched but is blank.

Applies to:

Oracle Fusion Product Model - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]Oracle Fusion Product Model - Version: 11.1.1.5.1 and later [Release: 1.0 and later]Information in this document applies to any platform.

Purpose

This document covers common problems in the functionality of Fusion Product Catalog Application.

Questions and Answers

Summary:

Item catalogs are an item classification structure within the Oracle Fusion Product Information Management application, but are usedby many other Oracle applications. Item Catalogs area used for classification of items and for analysis of sets of items represented bycategories.

Dependent Technologies:

None

Mandatory Log Channels:

AppsLogger modules:

oracle.apps.scm.productManagement.productCatalogManagement.itemSecurity.protectedUiModel.applicationModule.ItemSecurityAMImpl

Common Problems:

Unable to create a catalog, the catalog structure list of values is blank in the Create Catalog dialog.

A catalog cannot be created since a value cannot be selected or found by searching for a catalog structure in the list of values. TheCatalog Structure value is flagged as an error when the Save or Save and Close button are clicked.

Solution:

The catalogs are key flexfields enabled and require that the Key Flexfields be created prior to creating catalogs.1. Check to make sure that key flexfields Structure and Structure Instance have been defined for the catalog key flexcode MCAT. Youcan access the key flexfields for catalogs by using the Manage Key Flexfields for Catalogs task in the Oracle Fusion Functional SetupManager application.

2. Prior to defining the key flexfield Structure and Structure Instance, a value set must be defined, please refer to the implementationguides for information on creating value sets.

3. Define a key flexfield Structure and Structure Instance for the catalog key flexfields MCAT using the following steps:

Key Flexfield Setup

Prerequisite: Value sets must be defined prior to creating a key flexfield.

FSM Task: Manage Key Flexfield for Catalogs, search for the task in the FSM Overview page, within the All Task tab.

Steps:

a) Launch the page, the page opens with flexfield code MCAT that is seeded for catalog and categories.

b) The Key Flexfield Code MCAT is seeded; create the Key Flexfield structure for the new Key Flexfield for catalog.

c) Click the Manage Structures button, the Manage Key Flexfield Structure page will be displayed.

Page 1 of 11

4/11/2012https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=FAQ&id= ...


2/28

d) Click on the Create Icon

e) Enter the information:

Structure Code

Name

Select the delimiter used if more than one segment is defined

f) Click on Save button

g) Click the Create Icon in the Segment tables to create one or more segments.

h) Enter Information:

Segment Code

Segment Name

Sequence Number

Prompt (displayed in page)

Short Prompt

Display Width

Select Column name (where value is mapped to be storage)

Default Value Code previously created

i) Click Save and close ( Create Key Flexfield Segment Page)

j) Click Save and Close (Create Key Flexfield Structure Page)

k) Click Done button (Manage Key Flexfield Structures Page)

l) Now that the Key Flexfield structure is c reated, the structure instance for the KFF is created; Select the row for the KFF structure youjust created and click the Manage Structure Instances button

Page 2 of 11



3/28

m) Click the Create Icon to launch the create structure instance

n) Enter information:

Structure Instance Code

Name

Select the Structure Name

o) Click Save button. The segment information from the creation of the key flexfield structure should be displayed in the Segmentinstances table

p) Click Save and Close to close the Create Structure Instances page, control returns to the Manage Key Flexfields for Catalogs page.

q) Click Deploy Flexfield button to deploy the key flexfield structures and structures for the key flexcode MCAT. Do not use the droplist for this button.

r) Once the Deployment process is completed, the deployment status will show as a green check mark indicating the new key flexfieldhas been created.

Validation:

After following the above steps to create a key flexfield structure and structure instance for catalogs, invoke the Create Catalogs task orinvoke the Manage Catalogs task (use the Create Icon) in the Oracle Functional Setup Manager, fill in the catalog information, selectthe key flexfields you created in the Catalog Structure LOV choice list, and verify that the catalog is saved.

Unable to create a category and the category structure segments values are not listed in the Create Category dialog

During category creation, the Create Category dialog displays the fields for the category, but the key flexfield segments that are definedfor the key flexfield structure instance are not displayed below the Category Structure field. An error maybe displayed indicating theCategory Structure is not entered when you click the OK button. The category will sometimes be created as well, but an ApplicationError dialog will be launched when the catalog is saved.

Page 3 of 11



4/28

Solution:

The key flexfield definition for the category structure is not complete or the key flexfields are not deployed.

Review the key flexfield that has been created for the catalog. The key flexfield structure should contain a key flexfield structure,segments for the structure and a key structure instance.

Deploy the key flexfields for the catalog flex field code MCAT

2. Launch the Manage Key Flexfield for Catalogs task in the Oracle Function Setup Manager application, Overview Page within the AllTask tab.

3. Click the Deploy Flexfield button, status should indicate the key f lexfields are deployed successfully.

4. Close the Browser ( all tabs )

Validation:

After completion of the Deploy Flexfield operation, close the browser, reopen new browser window, invoke the Oracle ProductInformation Management application and launch the Manage Catalog UI page. Search for the catalog that you created the category in.Create new category, the Category Structure segment prompts should be displayed as fields below the Category Structure field.

Unable to assign catalog to a functional area in the Manage Default Catalog page.

A catalog that is created for a functional area does not appear in the choice list when editing the default catalog for a functional area orwhen searching in the choice list.

Solution:

A Functional area is an application or business process that implements catalogs requiring specific behavior for their catalogs, thebehavior is defined by a set of rules. The validation of the rules for each specific functional area is used to filter the values presented inthe Catalog Name choice list. The Functional Area Rules include the following:

1. The value of the Controlled At attribute for a catalog (see Figure 2) is determined based on Controlled at value of the OperationalAttributes (see Figure 1) for the Functional Area.

While assigning catalogs to a functional area in Default Catalogs UI, if the operational attribute control value is 'Org Level' for anattribute, only those catalogs whose control level is 'Organization Level' shows up in Catalogs LOV.

If the value of the Controlled At operational attribute is 'Master Level', then only those catalogs whose Controlled At value is 'MasterLevel' and 'Organization Level' shows up. The following chart shows the operational attribute groups that are used in the FunctionalArea Rules.

Page 4 of 11



5/28

Check the value for the Controlled At attribute for the operational attributes using the Manage Operational Attribute Groups task in theOracle Functional Setup Manager application to determine what the value for the Catalogs Controlled At attribute value.

Catalog Behavior Rules Based on a Functional Area

All Functional Areas:

The catalog must have a default category assigned to the catalog for the Functional area. Check the catalog to see if a category hasbeen assigned to the Default Category attribute value.

The value of one or more catalog attributes has to have a specific value, for example the functional area may not allow the catalog tohave a category hierarchy and the value of the Enable hierarchies for categories attribute must be No. Check the rule below for eachof the functional area and make sure the catalog conforms to the rules.

Inventory:

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

c. For Inventory attribute group: Inventory Item attribute, if the operational attribute Controlled At value is Master Level then catalogswith Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Inventory attribute group: Inventory Item attribute, if the value of Controlled At operational attribute is Organization Level thenonly catalogs with the value of Controlled At = Organization Controlled can be assigned.

Purchasing:

a) Catalog should not have hierarchy enabled.


Page 5 of 11



6/28

b) Catalog should have a default category assigned.

c) For Purchasing attribute group: Purchased attribute OR Order Management attribute group: Internal Ordered attribute, if theControlled At value operational attribute control value is Master Level then catalogs with Controlled At value of either MasterControlled or Organization controlled catalogs can be assigned.

d) For Purchasing attribute group: Purchased attribute OR Order Management attribute group: Internal Ordered attribute, if the value ofControlled At operational attribute is Organization Level then only catalogs that have the value Controlled At = OrganizationControlled can be assigned.

Planning:




c. For MPS and MRP Planning attribute group: Planning Method attribute, if the value of Controlled At operational attribute is MasterLevel then catalogs with Controlled At value of either Master Controlled or Organization Controlled catalogs can be assigned.

d. For MPS and MRP Planning attribute group: Planning Method attribute, if the value of Controlled At operational attribute isOrganization Level then only catalogs that have the Controlled At = Organization controlled can be assigned.

Service:




c. For Service attribute group: Contract Item Type attribute, if the value of Controlled At operational attribute is Master Level thencatalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Service attribute group: Contract Item Type attribute, if the value of Controlled at operational attribute is Organization Levelthen only catalogs where the Controlled = Organization controlled can be assigned.

Cost:




c. For Costing attribute group: Costing Enabled attribute, if the value of Controlled at operational attribute is Master Level thencatalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Costing attribute group: Costing Enabled attribute, if the value of Controlled at attribute is Organization Level then only catalogswith the value of Controlled at = Organization controlled can be assigned.

Order Entry:




c. For Order Management attribute group: Customer Ordered attribute, if the value of Controlled At operational attribute is MasterLevel then catalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Order Management attribute group: Customer Ordered attribute, if the value of Controlled At operational attribute isOrganization Level then only catalogs with the value of Controlled at = Organization controlled can be assigned

Product Line Accounting:




c. For Main attribute group: Item Description attribute, if the value of the Controlled At operational attribute is Master Level thencatalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Main attribute group: Item Description attribute, if the value of the Controlled At operational attribute is Organization Level thenonly catalogs with Controlled At=Organization controlled can be assigned.

Asset Management:




c. For Asset Management attribute group: Asset Item Type attribute, if the value of the Controlled At operational attribute is MasterLevel then catalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Asset Management attribute group: Asset Item Type attribute, if the value of the Controlled At operational attribute isOrganization Level then only catalogs with Controlled at=Organization controlled can be assigned.

Contracts:




Page 6 of 11



7/28

c. For Service attribute group: Contract Item Type attribute, if the value of the Controlled At operational attribute is Master Level thencatalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.

d. For Service attribute group: Contract Item Type attribute, if the value of the Controlled At operational attribute is Organization Levelthen only catalogs with a value of Controlled at = Organization controlled can be assigned.

Product Reporting:




c. Catalog should have Enable auto assign of categories = No

d. Catalog should have Allow multiple item category assignments = No

e. Catalog should have the value of Controlled At = Master Controlled.

GDSN Syndication for UDEX:





d. Catalog have the value of Controlled At = Master Controlled.

Process Product Line:




Distributed Order Orchestration:





d. Catalog should have Allow multiple item category assignments = No.

Supplier Product and Services:




Validation:

Review the attribute values for the catalog you area assigning to a functional area and check to see that they match the rules listedabove.

Unable to re-assign a catalog to a functional area in the Manage Default Catalog page.

In the Manage Default Catalogs UI page, a new catalog is selected from the Catalog Name choice list and the Save and Close buttonis clicked, an error dialog stating: The functional area catalog cannot be updated. (EGP-2775752) is launched preventing from thenew catalog to be assigned to the functional area.

Solution:

Once item has been assigned to any categories in the catalog assigned to a functional area, a new catalog cannot be assigned to thefunctional area. Check the catalog that is being assigned to the functional area to see if item have been assigned to the catalog.

Continue to use the catalog that is assigned to the functional area. Use the date enablement features to end date categories andcategory associations that are no longer in use.

Page 7 of 11



8/28

Unable to find my catalog in the Manage Catalog page.

I search for a catalog is that is created, but do not find the catalog using the search or when I search for a group of catalog using awildcard, the catalog does not appear in the Search Results table in the Manage Catalogs UI page.

Solution:

Catalogs are date enabled; the display, use and specific operations for catalogs are controlled by the values of the Catalog Start Dateand Catalog End Date. The Search Results table in the Manage Catalogs UI page has date filter to control which catalogs aredisplayed. Check the Catalog filter in the table header, the default value is display only the Active catalogs. Active catalogs haveCatalog Start Date value that is later or equal to the current date and have a Catalog End Date value later or equal to the current date( or the End Date can be blank ). If the catalog you are looking for does not appear in the Search Result table, change the Catalog filterto a value of All, which will display active, inactive and future dated catalogs.

Validation:

Set the Catalog filter value to All and search for the catalog. The filter allows the display of Active, Inactive and Future Datedcatalogs.

Unable to find my category in the category hierarchy table or the Add Category search and select dialogs.

In the Category Hierarchy tab of the Edit Catalog UI page, specific categories are not displayed in the category hierarchy tree table orthe categories cannot be found using the category search.

Solution:

Categories and Category Associations are date enabled, the display, use and specific operations for categories are controlled by thevalues of the Category Start Date and Category End Date or Category Association Start Date and Category Association End Date. ).

The tree table in the Edit Catalog UI page has two date filters to control which categories are displayed. Check the Categories and theAssociations filters in the table header, the default value is display only the active categories and active category associations. Activecategories have Category Start Date value that is later or equal to the current date and have a Category End Date value later or equalto the current date (or the End Date can be blank).

The display of the category in the tree table is depended on values for both filters. If you do not see the category in the categoryhierarchy table or cannot find it by searching the category hierarchy, then set the value of the Category and Association filters to All,this will display active, inactive and future dated categories and associations.

Validation:

Set the Categories filter value to All and Associations filter value to All. Then view or search for the category in the categoryhierarchy.

Unable to download data from the catalog into a spreadsheet, the spreadsheet is launched but is blank.

The spreadsheet that is launched from the Edit Catalog page is blank. The system launches a dialog Opening CategoryImport.xlsx,you select to open with Microsoft Office Excel, the spreadsheet opens, but the spreadsheet is blank.

Page 8 of 11



9/28

Solution:

Check the following:

1. Check to see that you are using Microsoft Office Excel 2007, this release is required to support the export/import process.

2. Check to see the Oracle ADF 11g Desktop Integration Runtime Add-in for Excel client is i nstalled on your local machine. Thevalidate the client is installed:

Open the Windows Control Panel

Click on Add or Remove Program

Search for Oracle ADF 11g Desktop Integration Runtime Add-in for Excel

If the client is not installed, download the client using the following steps:

In the Items Work Area: Click on the drop list for the Navigator in upper left hand corner of the work area.

Select Tools->Download Desktop Integration Installer

Follow directions for installing client.

3. Check to see if browser security is blocking access between the browser and application using the following steps:

Open Microsoft Office Excel 2007

Click on the Microsoft office button and then click on Excel Options (See image below)

Click the Trust Center tab and then click Trust Center Settings

Page 9 of 11



10/28

Click the Trusted Locations tab.

Verify that the path to Oracle Product Information Management application is listed in the trusted locations table, see below.

If the path to the application server is not listed, add the path

Select the Allow Trusted Locations on my network (not recommended) checkbox

Click the Add New Location button (refer figure below)

Enter the hostname of the server that your Integrated Excel workbook will be accessing. The path should end with the/productManagement/.

Select the checkbox Subfolders of this location are also trusted

Click Ok.

Microsoft Office Excel is now configured to allow the integrated excel workbooks to access your remote hosts. Additional information isavailable in the ADF Desktop Integration User Guide.

Validation:

Launch the export of the catalog information by clicking the Export Hierarchy button, download the information to Microsoft OfficeExcel, login to the using the same userID and password used to access the application, the information from the catalog will bedisplayed within the spreadsheet.

Related

Products

Oracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product ModelOracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product Model

Page 10 of 11



11/28

Keywords

CATALOGS; FUSION APPLICATIONS; KEY FLEXFIELD FOR CATALOGS; MANAGE KEY FLEXFIELD FOR CATALOGS

Errors

EGP-2775752

Back to top

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

Page 11 of 11



12/28

Fusion PIM: Item Interface Upload - Column 'ITEM_CATALOG_GROUP_ID' [ID 1353796.1]

Modified16-SEP-2011 TypeHOWTO StatusPUBLISHED

Applies to:

Oracle Fusion Product Hub - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]

Information in this document applies to any platform.

Goal

What value should be populated in column 'ITEM_CATALOG_GROUP_ID' while importing items using Interface tables?

Is this column related to Item Class or Catalog?

Solution

Column 'ITEM_CATALOG_GROUP_ID' actually refers to the Item Class and NOT the Catalog.

Following changes are planned post Fusion version 1 (11.1.1.5.1).The 2 columns that represent Item Class in EGP_SYSTEM_ITEMS_INTERFACE refer to Item Class.

Below are their existing and suggested new names

Existing column

ITEM_CATALOG_GROUP_ID

ITEM_CATALOG_GROUP_NAME

Rename to

Item_Class_NameItem_Class_ID

In Fusion Applications 11g ( version 11.1.1.5.1), these fields should be populated with Item Class Id and Item Class Name respectively. SeeNote 1299158.1- [Sample SQL To Import Items Into Fusion Product Information Management(PIM) Using Open Interface Tables] for anexample of how these columns can be used.

References

Related

Products

Oracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product Hub

Keywords

CATALOGS; CLASS; CLASS ID; IMPORT ITEMS; INTERFACE; ITEM; OPEN INTERFACES

Back to top


https://support.oracle.com/CSP/main/article?cmd=show&type=NO

4/10/20


13/28

Fusion PIM - Understanding Item Cross References [ID 1309859.1]

Modified02-MAR-2012 TypeHOWTO StatusPUBLISHED

In this DocumentGoalSolutionReferences

Applies to:


Goal

In this document we will understand what are Item Cross-references and how to implement and use them.

Solution

Cross references are just a form of Item Relationships.

The following Item Relationships are supported:

1. Related Items: Relationship between two Product Master Items2. Trading-Partner Item (TPI) Relationship: Relationship between a Product master Item and a Trading Partner Item3. GTIN Relationship: Relationship between a Product master Item and GTIN (Global Trade Item Number)4.Item Cross reference: Cross-referencing of Item. This cross reference can be of any pre-defined type.5. Source System Item: Relationship between a Product master Item and an external Source System Item

In this document, we will discuss only:4. Item Cross reference5. Source System Item

Item Cross-references Vs. Source System Item Cross-references

Item Cross references Source System Item Cross References

Does not require Oracle Fusion Product Hub Requires Oracle Fusion Product Hub

Can define custom cross reference types Cross reference type is Source System

Can be created on Item Relationships UI Can be created on Item Relationships UI

Must be defined manually or explicitly imported (via interface tables or web services) Are created automatically when source system items are imported using Item Batches

Is not used for any matching or validation of data Is used to match items during Item Import

Defining Custom Item Cross Reference Types

Items can have many cross-references. Example of cross-references are, customer part number, superseding / preceding item number etc. An administrator can define their own cross-refertypes based on their business need. Cross-reference types have effectivity dates, which controls them being active or inactive.

Item Cross-reference types are defined as standard lookups in Fusion Applications. These can be defined using Functional Setup Manager (FSM) and/or Applications Core Setup.

FSM Task NameManage Cross Reference Types

Using Applications Core setup:Applications Core Setup > (Lookups) Manage Standard Lookups

Query for Meaning = 'Item Cross Reference Types'Lookup Type = 'EGP_ITEM_XREF_TYPES'

Rate this document

Page 1 of 3

4/11/2012https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&...


14/28

You can use the following query to get a list of all Cross Reference types defined.

SELECT LOOKUP_TYPE, LOOKUP_CODE, MEANING

FROM FND_LOOKUPS

WHERE LOOKUP_TYPE = 'EGP_ITEM_XREF_TYPES';

If using only Oracle Fusion Product Model, source system cross-references are not available. For integration with other products like Distributed Order Orchestration (DOO), Item cross-references can be used instead.

Creating Cross References

Both Item cross references and Source System cross references can be created using the Manage Item Relationships task Or Manage Items task.

Using Manage Items TaskNavigation: Manage Items > Relationships > Cross-ReferencesUse the Item Cross-reference type defined to create a new item cross-reference

Using Manage Item Relationships TaskNavigation: Manage Item RelationshipsSelect Relationship TypeQuery Item(s) for which you wish to manage cross references

>>>>

Import Using Open Interface Tables

Page 2 of 3



15/28

Item cross references can be imported explicitly using the Open Interface (OI) tables. Please see Note 1311629.1for a sample script to be used to import cross references.

Source System cross references are created automatically when a source system item is imported using Item Batches (via ADFdi or OI tables or web services). Please see following documavailable on how to import items.Note 1279983.1- Fusion PIM - Data import upload steps generic exampleNote 1299158.1- Sample SQL To Import Items Cross References Into Fusion Product Information Management(PIM) Using Open Interface Tables

Finding Cross References

Both Item cross references and Source System cross references can be queried using the Manage Item Relationships task Or Manage Items task.

You can also use the following queries to see the cross-references defined for an item:

Item Cross ReferencesSELECT ITEM_RELATIONSHIP_ID, SUB_TYPE, CROSS_REFERENCE, ORG_DEPENDENT_FLAG

FROM EGP_ITEM_RELATIONSHIPS_B

WHERE ITEM_RELATION_SHIP_TYPE = 'ITEM_XREF'

AND INVENTORY_ITEM_ID = (SELECT INVENTORY_ITEM_ID FROM EGP_SYSTEM_ITEMS_B WHERE ITEM_NUMBER = '&ITEM_NUM');

Source System Cross References

SELECT ITEM_RELATIONSHIP_ID, SUB_TYPE, CROSS_REFERENCE, ORG_DEPENDENT_FLAG


WHERE ITEM_RELATION_SHIP_TYPE = 'SYS_ITEM_XREF'

AND INVENTORY_ITEM_ID = (SELECT INVENTORY_ITEM_ID FROM EGP_SYSTEM_ITEMS_B WHERE ITEM_NUMBER ='&ITEM_NUM');

>>>>

References

Related

Products

Oracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product ModelOracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product Model

Keywords

CROSS REFERENCE; ITEM; ITEM RELATIONSHIPS; RELATED ITEM; RELATIONSHIPS

Back to top


Page 3 of 3



16/28

Fusion PIM - Pre Requisite Add In for Excel 2007 ADFDI [ID 1273076.1]

Modified16-SEP-2011 TypeHOWTO StatusPUBLISHED

In this Document

Goal Solution

References

Applies to:

Oracle Fusion Product Hub - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]

Information in this document applies to any platform.

Goal

This document will outline the requirements for setup of Microsoft Excel upload of Item related data to Fusion Product Information Management(PIM).

This pre requisite is for the initial setup phase of installing / configuring the product and ADFDI and should be executed prior to first attempt toupload data to the Fusion PIM product in any of the 5 defined import batch data types.The action is not required subsequently for a workstationunless a problem is flagged during execution of Excel.

Solution

Pre Requisite: At time of publication of this document the minimum technical requirement is the use of Microsoft Excel 2007 for spreadsheet

based batch data import.

The action of installing the Excel / ADFDI Add-In is only required once for the setup phase of any installed instance of Microsoft Excel 2007 and

is suitable for all data import batch types.

To determine whether the Add-In has already been installed and is active within the instance of Excel 2007 being used perform the following.

1. Open Excel2. Click on the top left 'Excel control' button which will drop down generic options.


4/10/20


17/28

3. Click on the 'Excel Options' button.4. Click on Add-Ins from left hand column options.

5. Look for an Add-In commencing title 'Oracle ADF 11g Desktop Integration' in the active section of Add-Ins. If the Add-In is present in theinactive section, a conflict has deactivated it and it requires reset to reactivate it.


4/10/20


18/28

6. If not present at all then visit the Oracle ADFDI pages on the www.oracle.comweb site to download and install the free Add-In. Onlinetraining for ADFDI and steps to download are located herein 11g JDeveloper Tutorials.7. If the Add-In is present; but ADFDI errors are occurring when batch upload is attempted, your driver may be out of date, please ensure that

the latest recommended version of the Add-In has been loaded.

References

Related

Products


Keywords

ADD-IN; ADF; BATCH UPLOAD; DESKTOP INTEGRATION; EXCEL; IMPORT; INTEGRATION; PRODUCT INFORMATION

MANAGEMENT


4/10/20


19/28

Back to top



4/10/20


20/28

Fusion PIM - Understanding Item Cross References [ID 1309859.1]

Modified02-MAR-2012 TypeHOWTO StatusPUBLISHED

In this DocumentGoalSolutionReferences

Applies to:


Goal

In this document we will understand what are Item Cross-references and how to implement and usethem.

Solution

Cross references are just a form of Item Relationships.

The following Item Relationships are supported:

1. Related Items: Relationship between two Product Master Items2. Trading-Partner Item (TPI) Relationship: Relationship between a Product master Item and aTrading Partner Item

3. GTIN Relationship: Relationship between a Product master Item and GTIN (Global Trade ItemNumber)4.Item Cross reference: Cross-referencing of Item. This cross reference can be of any pre-defined type.5. Source System Item: Relationship between a Product master Item and an external SourceSystem Item

In this document, we will discuss only:4. Item Cross reference5. Source System Item

Item Cross-references Vs. Source System Item Cross-references

Item Cross references Source System Item Cross References

Does not require Oracle Fusion Product Hub Requires Oracle Fusion Product Hub

Can define custom cross reference types Cross reference type is Source System

Can be created on Item Relationships UI Can be created on Item Relationships UI

Must be defined manually or explicitly imported (viainterface tables or web services)

Are created automatically when source system itemsare imported using Item Batches

Is not used for any matching or validation of data Is used to match items during Item Import

Rate this document

Page 1 of 5

4/11/2012https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO& ...


21/28

Defining Custom Item Cross Reference Types

Items can have many cross-references. Example of cross-references are, customer part number,superseding / preceding item number etc. An administrator can define their own cross-referencetypes based on their business need. Cross-reference types have effectivity dates, which controlsthem being active or inactive.

Item Cross-reference types are defined as standard lookups in Fusion Applications. These can bedefined using Functional Setup Manager (FSM) and/or Applications Core Setup.

FSM Task NameManage Cross Reference Types

Using Applications Core setup:Applications Core Setup > (Lookups) Manage Standard Lookups

Query for Meaning = 'Item Cross Reference Types'Lookup Type = 'EGP_ITEM_XREF_TYPES'

You can use the following query to get a list of all Cross Reference types defined.

SELECT LOOKUP_TYPE, LOOKUP_CODE, MEANINGFROM FND_LOOKUPS

WHERE LOOKUP_TYPE = 'EGP_ITEM_XREF_TYPES';

If using only Oracle Fusion Product Model, source system cross-references are not available.For integration with other products like Distributed Order Orchestration (DOO), Item cross-references can be used instead.

Page 2 of 5



22/28

Creating Cross References

Both Item cross references and Source System cross references can be created using the ManageItem Relationships task Or Manage Items task.

Using Manage Items TaskNavigation: Manage Items > Relationships > Cross-ReferencesUse the Item Cross-reference type defined to create a new item cross-reference

Using Manage Item Relationships TaskNavigation: Manage Item RelationshipsSelect Relationship TypeQuery Item(s) for which you wish to manage cross references

>>>>

Page 3 of 5



23/28

Import Using Open Interface TablesItem cross references can be imported explicitly using the Open Interface (OI) tables. Please seeNote 1311629.1for a sample script to be used to import cross references.

Source System cross references are created automatically when a source system item is importedusing Item Batches (via ADFdi or OI tables or web services). Please see following documents

available on how to import items.Note 1279983.1- Fusion PIM - Data import upload steps generic exampleNote 1299158.1- Sample SQL To Import Items Cross References Into Fusion Product InformationManagement(PIM) Using Open Interface Tables

Finding Cross References

Both Item cross references and Source System cross references can be queried using the ManageItem Relationships task Or Manage Items task.

Page 4 of 5



24/28

You can also use the following queries to see the cross-references defined for an item:Item Cross References



WHERE ITEM_RELATION_SHIP_TYPE = 'ITEM_XREF'

AND INVENTORY_ITEM_ID = (SELECT INVENTORY_ITEM_ID FROM EGP_SYSTEM_ITEMS_B

WHERE ITEM_NUMBER = '&ITEM_NUM');

Source System Cross References



WHERE ITEM_RELATION_SHIP_TYPE = 'SYS_ITEM_XREF'

AND INVENTORY_ITEM_ID = (SELECT INVENTORY_ITEM_ID FROM EGP_SYSTEM_ITEMS_B

WHERE ITEM_NUMBER ='&ITEM_NUM');

>>>>

References

Related

Products

Oracle Fusion Applications > Supply Chain Management > Product InformationManagement > Oracle Fusion Product Model

Oracle Fusion Applications > Supply Chain Management > Product InformationManagement > Oracle Fusion Product Model

Keywords

CROSS REFERENCE; ITEM; ITEM RELATIONSHIPS; RELATED ITEM; RELATIONSHIPS

Back to top

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | PrivacyStatement

Page 5 of 5



25/28

Fusion PIM: Common Problems and Solutions - Consolidate Product/Service Master Data-Manage Import Batches [ID 1391189.1]

Modified19-JAN-2012 TypeFAQ StatusPUBLISHED

In this Document

Purpose Questions and Answers

Summary: FAQ Unable to add items to an Item Batch using Microsoft Excel spreadsheet.

Errors displayed when editing an item batch after loading data into interface tables.

Applies to:

Oracle Fusion Product Hub - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]Information in this document applies to any platform.

Purpose

This FAQ covers Product Item data import using Fusion Product Hub functionality.

Questions and Answers

Summary:

Item batches are used to import items and related information as part of the consolidation process. Once an item batch is created, users mustinsert item and related data into interface tables before processing the item batch. Items can be added to a batch either through ADF DesktopIntegration (ADFdi) using Microsoft Excel 2007 or by directly populating the interface tables. There are several options available at the item

batch to control how the items are processed. This task can be accessed through the Manage Item Batch or Create Item Batch task in theItems work area for users with the Product Data Steward Job Role or appropriate duty role as documented in the Product ManagementSecurity Reference Manual.

Dependent Technologies:

Oracle ADF Business Component

Oracle Enterprise Scheduler

Oracle ADF Desktop Integration

Oracle PL/SQL

Oracle Fusion Middleware Extensions (ApplCore)

FAQ

Unable to add items to an Item Batch using Microsoft Excel spreadsheet.

When attempting to add items to an item batch using Microsoft Excel 2007 (ADF Desktop Integration), an error is observed.

Solution:

1. Verify if the Microsoft Excel version 2007 is being used. This is the only supported version.

2. Verify if the ADF Desktop Integration add-in has been installed by following these steps:

a. In Excel click on the 'Home' icon (top left) and choose the button for Excel Options

b. In Excel options box select the Add Ins option

c. Does 'Oracle ADF 11g Desktop Add In for Excel' exist within the list?

d. Confirm that the add-in is in the active. Sometimes add-ins are inactivated due to conflicts.

3. If the add-in needs to be installed, in Fusion Applications go to Navigator -> Tools -> Download Desktop Integration


4/10/20


26/28

a. You will be prompted to download the installer. Run the installer on your desktop to install the add-in. Note: Some browsers do not add the

exe file extension to the downloaded file automatically. You will have manually add the extension in such cases.

b. Verify the settings mentioned in step 2.

Validation:

After following the above steps, add items to a batch by choosing the Item Class and Import format from the Add Items to Batch dialog. Whenyou click on Download, Excel should prompt you to login with the appropriate Fusion Applications credentials.

Following that, you will be presented with a spreadsheet with the appropriate column headers to add items.

Errors displayed when editing an item batch after loading data into interface tables.

After creating an item batch and inserting data into the item interface tables, errors are observed when attempting to edit the item batch.Typically application 'Incidents' are raised due to these errors.

Solution:

The most likely reason for this issue is that the Item extensible flexfields were not deployed after a modification was made to the item classhierarchy or associated attributes.

1. Verify the deployment status of Item Extensible Flexfields by performing the following steps in the Application:

a. Go to Navigator -> Tools -> Setup and Maintenance

b. Click on the All tasks tab and search for the task Manage Extensible Flexfields

c. Click on Go to Task and query for Name = Item Extended Attributes

d. Verify that the deployment status is Deployed (Green check icon)

2. If the status is anything other than Deployed, re-deploy by clicking on the Deploy Flexfield button. Note that this process may take some timebased on the size of the Item Class hierarchy and associated attribute.

Validation:

You should be able edit an item batch without encountering any errors.

Related

Products


Keywords

ADFDI; CONSOLIDATE PRODUCT/SERVICE MASTER DATA; CREATE ITEM BATCH; DATA; FUSION APPLICATIONS; ITEM

BATCHES; MANAGE ITEM BATCHES

Back to top



4/10/20


27/28

">

FUSION PIM - How to deploy Key Flex Fields ( KFF ) for PIM Catalog 'MCAT' [ID 1390427.1]

Modified29-FEB-2012 TypeHOWTO StatusPUBLISHED

In this DocumentGoalSolution

Applies to:

Oracle Fusion Product Model - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]Information in this document applies to any platform.

Goal

Prior to use of Fusion Product Infomation Management (PIM) Catalog and Categories and in the event of any changes to requirements,it is necessary to deploy the KFF (Key Flex F ields) associated with application functionality.The key value PIM Catalogs are concernedwith is a KFF called 'MCAT' which has a specific build and deploy steps outlined in this note.

Solution

1. Log on with a user role with FSM (Functional Setup Manager) capability. Navigate to FSM via Setup and Maintenance menu.2. Search for task ' Manage Key Flexfield for Catalogs'.

3. The application should default KFF for Product Model (Catalog functionality is controlled from this designation). If a KFF has notbeen created previously select [ACTION] Create and build the MCAT KFF relationship.

4. If a KFF has already been created use [BUTTON] 'Manage Structures' to drill into the current definition.

5. Use an open search to bring back a full list of available KFF structures.

Page 1 of 2



28/28

6. After creating KFF structures, Structure instances must be maintained BEFORE deployment.7. Finally once the KFF has been constructed it needs to be propagated to the system, this is performed by [BUTTON] 'DeployFlexfield' which will replace any existing definition.

For more detailed study of flexfields and other considerations please refer to Oracle Fusion Applications Common ImplementationGuide.

Please note if changes are being made to a production scenario it should be performed out of hours and should not involveremoval of KFF values without careful consideration of existing data.

Related

Products

Oracle Fusion Applications > Supply Chain Management > Product Information Management > Oracle Fusion Product Model

Keywords

DEPLOY; DEPLOYMENT; FUSION APPLICATIONS; KEY FLEX FIELD; KFF

Back to top


Page 2 of 2

Fusion PIM

Documents

Transcript of Fusion PIM