Configuring attributes between Items and Sourcing Projects

Have you come across cases where certain fields that show up in an Item's Page Two doesn't show in a Sourcing Project? That could be related to some of the attributes not been mapped correctly between Product Collaboration and Sourcing Project.

In PC's Items & Manufacturer Parts, customers could categorize their data using unlimited number of fields in Page Two. When items and mfr parts are added to a Sourcing Project for costing purposes, not all these fields would be relevant to the sourcing manager and so, the ability to configure what attributes should show up in the Sourcing Project becomes important.

PCM supports the "mapping" functionality wherein, you can setup a "mapping" between a field in Item-Page Two tab and a field in Project-Items tab. The purpose of establishing a mapping between 2 fields is to ensure that a field in Project-Items tab displays the same value as in a field in Item-Page Two. For instance, if you have a Last Paid Cost field (or some kind of standard cost) defined in Page Two of an Item in PC, you can map the same cost field into the Standard Cost field in the Sourcing Project to enable the sourcing manager make informed decisions. At a high level, follow the simple steps below if you want to map a specific field from PC to Sourcing Project:

1. Identify the field in Item-Page Two or MfrPart-Page Two that you want to see in the Sourcing Project and make sure it is visible.
2. Identify the field in Sourcing Project-Items tab or Project-MfrParts tab that you want to see the value from PC-Page Two and setup the mapping.
3. Enable the corresponding field in Project-Analysis tab and RFQ-Responses tab and follow consistent naming.

Let's look at the process in more detail:The mapping of attributes needs to be done in Java Client through

Admin-->Settings-->Data Settings-->Classes-->Sourcing Project-->AML.


The AML tab has 2 "tables" - one for Items (called Attributes:Items in Java Client) and one for Mfr Parts (called Attributes: AML).


Based on whether you want to map an Item's P2 field or a Mfr Part's P2 field to Sourcing Project, you can use the Items table or the AML table within the AML tab in Java Client. Each of those tabs allow you to map 10 Text fields (fields named text1..10), 10 Numeric fields (fields named number1..10), 5 Date fields (fields named date1..5), 5 List fields (fields named list1..5), 5 Money fields (fields named money1..5), 2 Multilist fields (fields named multilist1..2) and 2 Multitext fields (fields named multitext1..2). Each of the above attributes in Java Client would display a property called Map Data To which indicates the field in Item-Page Two from which the values gets displayed in Sourcing Project's Items tab. The Map-Data-To property displays only those corresponding fields from Item-Page Two which are of the same type and which have been turned on. For instance, in the below example, in the Map-Data-To property of text1 field in Sourcing Project-AML-Items table, it displays only "text" fields and those that are enabled.


If one of the attribute from Item-Page Two doesn't show up for being mapped, it could be due to one of the following reasons:

1. Do both the attributes belong to the same type? For instance a numeric attribute from Item-Page Two can only be mapped to a numeric attribute in Project-AML-Items tab.
2. Is the attribute in Item-Page Two set as visible?

Likewise, for mapping MfrPart-Page Two, it needs to be done in the AML table within the AML tab. In addition to the above fields, mapping is also supported for some of the standard fields (Standard Cost, Target Cost, Quote As, Cost, Buyer, Planner and Make/Buy) through Items table. All of the above standard fields, except Target Cost, need to be mapped from the Items table of the AML tab while the Target Cost needs to be mapped from the Price Details tab in Sourcing Project. The primary reason for this is that, the target cost is set based on the price scenario in the Sourcing Project.


When mapping fields in the AML tab of a Sourcing Project, administrators need to ensure that the same set of fields are visible in the Analysis tab and also in the Responses tab of the RFQ Class. These are read-through fields from Items or AML tab in Sourcing Project. In the Analysis tab (within Attributes: Analysis) in Java Client or in the Responses tab, these fields will be called ipnText01, mpnNumeric02 etc to indicate where these fields/values came from. For instance, the name ipnText01 indicates that this is a Text attribute and is specific to an Item, while mpnNumeric02 indicates this as a Numeric attribute specific to a Mfr Part. In the example below, all fields that start with "ipn" (ipnText01, ipnList02 etc) are read through fields from Project-Items tab while the fields that start with "mpn" (mpnDate01, mpnNumber05 etc) are read through fields from Project-AML tab.


When mapping fields, the following things need to be ensured:
Consistent naming - if a field is named and mapped in the Items table of AML tab, the administrator needs to enable the corresponding field and name it the same way in Analysis tab and RFQ-Responses tab. For instance, if the Text01 field is named "Item Text Field" in Items table of AML tab in Java Client, the corresponding field in the Analysis tab, which is ipnText01, should also be named as "Item Text Field". Same thing needs to be done in the RFQ-Responses tab.
Proper Configuration of List attributes - if a list field is enabled and made to point to a specific List in the AML tab, the corresponding list field needs to be enabled and made to point to the same List in the Analysis and Responses tabs. For instance, if the list01 field in Items table of AML tab in Java Client is named as "Continents Field" and points to the Continent List, the administrator should make sure the corresponding attribute in the Analysis tab, which is ipnList01, should also be named as "Continents Field" and should be made to point to the same Continent List. Same thing needs to be done for the RFQ-Responses tab also.

In essence, here are the key points about Mapping with respect to items and Mfr Parts within a Sourcing Project:

• Flex fields of Items and Mfr Parts within a Sourcing Project can be configured to display values from corresponding Page Two fields from Items and Mfr Parts in PC.
• Few (not all) standard fields of Items within a Sourcing Project can be configured to display values from Page Two fields from Items in PC.
• For BOM fields, Qty gets displayed in the Sourcing Project automatically without any mapping. Other BOM fields (like Find Number, Ref Des or other BOM flex fields) can not be mapped from PC to Project.
• Likewise, for AML fields, AML Status and AML Split Percentage are the attributes that get displayed in the Project automatically without any mapping. Other AML flex fields can not be mapped from PC to Project.
• Mapping is NOT supported for BOM (like Find Number, Ref Des etc) or AML fields

Making sure that the mapped attributes are configured correctly across tabs would go a long way in eliminating confusion among the sourcing users.


Post a Comment:
  • HTML Syntax: NOT allowed

Hear from the community that's pioneering PLM's critical role in transforming supply chains into sustainable value chains that power profitable innovation and competitive advantage.

Subscribe to Oracle Agile PLM Blog by Email


« June 2016