| Agile Product Lifecycle Management Product Cost Management User Guide Release 9.3.6 E71147-01 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Product Cost Management User Guide Release 9.3.6 E71147-01 |
|
Previous |
Next |
This section provides information about nodes in the Product Cost Management folder under System Settings.
Use the following checklist to configure Agile PLM server settings for Product Cost Management:
Define your company profile - Specify the name, address, phone number, URL, and the corporate currency for your company. For more information, see the Agile PLM Administrator Guide.
Define currency exchange rates - Suppliers may quote prices in different currencies. You must maintain a table of currency exchange rates so that you can view normalized prices that have been converted to the project currency. For more information, see the Agile PLM Administrator Guide.
Define your company's Ship To locations - Ship To locations are essential to take advantage of Product Cost Management features. For more information, see "Ship To Location."
Configure SmartRules - Make sure you properly configure SmartRules related to price fields, effectivity periods, automatic publishing of quote histories, and commodities. For more information, see the "Configuring SmartRules For PCM."
Configure the Product Cost Management class - Configure the Agile PLM classes for Product Cost Management. For more information, see "Configuring Product Cost Management Classes."
Configure the Sourcing Projects class - There are several things you can do to customize the Sourcing Projects class, which affects all of its subclasses. For example, you can enable flex fields on different tabs, configure AML tab attributes to pull values from other Item and Manufacturer Part attributes, and define price adders and non-material price fields for RFQ responses. For more information, see "Configuring Product Cost Management Classes."
Define Suppliers - Define the suppliers with whom sourcing project managers and RFQ managers will be working. This may be the responsibility of another user, someone with the Organization Manager role. For more information about creating and managing suppliers, see Getting Started with Agile PLM.
|
Note: Separately, supplier managers should define the contact users and line cards for their particular suppliers. Supplier users have restricted access to Product Cost Management functionality. |
Define Supplier Offering Ratings - In the Agile PLM List Library, there is a list called Supplier Offering Rating, which is used to rate each supplier offering. You can customize the list of ratings. By default, the ratings are Approved, Strategic, Offered Active, and Offered Inactive. For more information, see the Agile PLM Administrator Guide.
Define Product Cost Management Users and Roles - Define the users who will create and manage sourcing projects, RFQs, and prices. Assign those users appropriate roles, such as Sourcing Administrator, Sourcing Project Manager, RFQ Manager, and Price Administrator. For more information, see "Product Cost Management Roles." Make sure every user who will create sourcing projects has at least one authorized Ship To location. Otherwise, the user will not be able to move a project from Draft to Open status. For more information about the available PCM roles, see the Agile PLM Administrator Guide.
Configure Administrator Privilege - To see the RFQ Terms and Conditions node on the Admin tab in Java Client, you must configure the Administrator privilege. This is covered in "Configuring the RFQ Terms and Conditions Node."
Define new subclasses of the Sourcing Projects class - Agile PLM provides one subclass of the Sourcing Projects class called Sourcing Project, but you can extend Sourcing Projects and define any number of subclasses for specific types of projects. For more information, see the Agile PLM Administrator Guide.
Configure BOM Filters - To use the BOM filtering feature in PCM, you must create and configure certain attributes in Data & Workflow Settings > Classes > Parts. For more information about how to use this feature after it is set up, see "Configuring BOM Filters."
Establish Relationships between Objects - For information about how to establish relationships between fields, refer to Getting Started with Agile PLM, "Working with Business Objects" chapter.
Define Preferences for Price - For information, see, "Configuring Preferences for PCM."
Ship To locations are important for differentiating sourcing projects and for disseminating requests for quotes (RFQs) to suppliers.
To add a Ship To location:
Under System Settings > Product Cost Manageent, double click Ship To Location. The Ship To Locations window opens.
Click New icon. The Create Ship To Location dialog box appears.
Type the name and location code of the new Ship To location. Fill in other fields as needed.
Click OK. The new Ship To location appears on the list.
|
Note: Sourcing project managers must have at least one Ship To location defined in their user profiles. Otherwise, the projects they create cannot be opened. Similarly, each sourcing project must have a specified Ship To location. A project's Ship To location determines how RFQs are disseminated to suppliers based on their line cards. |
|
Note: When a Ship To Location is being used (referenced to) in any Sourcing Project, be the project in Draft or Open stage, it cannot be deleted in Java Client. When you attempt deleting, system issues a warning message "Fail to delete Ship To; one of the Ship To(s) is referenced to other objects". |
The following are PCM-specific SmartRules:
Negative Value For Material Price Adder Fields - See "Applying Price Adders to Responses."
Zero Value For Material Price Adder Fields - See "Applying Price Adders to Responses."
Negative Value For Material Price Fields
Zero Value For Material Price Fields
Negative Value For Non-Material Price Fields
Zero Value For Non-Material Price Fields
DuplicateItemNumbers - See "Adding Items to a Project."
Auto Publish Quote History
See the Agile PLM Administrator Guide for more details about SmartRules.
Agile PLM provides pre-defined roles that you can assign to Product Cost Management users. These roles grant users the privileges to work with sourcing projects, RFQs, prices, discussions, suppliers, customers, and PCOs.
Roles with names that start with the prefix (Restricted) are intended for Suppliers. For a complete list of the predefined Agile PLM roles, see the Agile PLM Administrator Guide.
|
Note: Although the Agile PLM administrator may not have assigned you the privileges needed to work with a sourcing project, other users with access to a project can share them with you, thereby granting you the same privileges that apply to the project and all the objects contained within it. However, you cannot access other projects that are not shared with you. |
You can limit a supplier's access to an RFQ until they electronically agree to RFQ Terms and Conditions that you specify in Java Client. The RFQ Terms and Conditions node must be enabled in Java Client, then you can set and store the content of the Terms and Conditions page.
To use the RFQ Terms and Conditions feature, you will need to complete several tasks.
Tasks to Enable RFQ Terms and Conditions:
Enable the RFQ Terms and Conditions node in Java Client. For a detailed description of this task, see "Configuring the RFQ Terms and Conditions Node."
Set up and enter the content of the RFQ Terms and Conditions that you want the supplier to read and accept. For a detailed description of this task, see "Setting and Storing the RFQ Terms & Conditions Content."
Make the Require RFQ Terms and Conditions attribute visible in the Sourcing Project class. For a detailed description of this task, see "Making the Attribute visible in Sourcing Project class."
Make the Require RFQ Terms and Conditions attribute visible in the Requests for Quotes class. For a detailed description of this task, see "Making the Attribute Visible in Requests for Quote Class."
Update Modify My Sourcing Project General Info privilege to include Applied To field value: Sourcing Projects.Sourcing Project.Require RFQ Terms and Conditions. For a detailed description of this task, see "Adding criteria to Modify My Sourcing Project privilege."
Update Read RFQs privilege to include Applied To field value: Requests for Quote.RFQHeader.Require RFQ Terms and Conditions. For a detailed description of this task, "Adding Criteria to Read RFQs Privilege in Sourcing Project Manager Role."
Update Read RFQs privilege to include the following Applied To field values: Status Accept Date, Status Accept User, Status Status, and Status Supplier. For a detailed description of this task, see "Adding Criteria to Read Privilege."
|
Note: Optionally, you can make Terms mandatory at the project level. |
To see RFQ Terms and Conditions node in Java Client, you must configure the user's Administrator privilege. By default, it is disabled.
For more information about the Administrator Privilege, and how Administrator nodes are made available to a user, see the Agile PLM Administrator Guide.
Configuring the Administrator Privilege:
Go to Settings > User Settings > Privileges.
Double-click Administrator privilege key to open the Administrator window.
Select Show All in the Match If drop-down list and click Apply.
Double-click the Administrator privilege line. The Privilege:Administrator window opens.
Click the Arrow button in the Applied To field.
Select the RFQ Terms and Conditions option in the choices list and move it to the Selected list. Click OK.
Make sure the Enabled field is set to Yes.
Click Save and Close.
Close the Privileges for Administrator window.
Log out of Java Client and log back in. You should see RFQ Terms and Conditions node under Settings > System Settings > Product Cost Management.
After you have enabled the RFQ Terms & Conditions node, you can set and store the content.
Create RFQ Terms & Conditions Content:
Under Settings, expand System Settings node, and then the Product Cost Management node.
Double-click RFQ Terms and Conditions. The RFQ Terms and Conditions window appears.
Enter the content for your RFQ's Terms and Conditions in the text field.
Click Save followed by Close.
You must make the Require RFQ Terms and Conditions attribute visible in the Sourcing Project class General Information tab.
To make the attribute visible:
Double-click the Settings > Data Settings > Classes.
Double-click the Sourcing Projects class.
Double-click the General Information in User Interface Tabs tab.
Go to Attributes: General Information tab and double-click Require RFQ Terms and Conditions.
Select Yes in the Visible field.
Click Save followed by Close.
To enable the attribute for search:
Double-click Settings > Data Settings > Classes.
Double-click Sourcing Projects class.
Double-click General Information in User Interface Tabs tab.
Go to Attributes: General Information tab and double-click Require RFQ Terms and Conditions.
Select Yes in Enable for Search Criteria.
Click Save followed with Close.
You must make the "Require RFQ Terms and Conditions" attribute visible in the Requests for Quote class.
To make the attribute visible:
Double-click Classes in Settings > Data Settings.
Double-click Requests for Quote class.
Go to User Interface Tabs tab and double-click Cover Page.
Go to Attributes:Cover Page tab and double-click Require RFQ Terms and Conditions.
Select Yes in the Visible field.
Click Save and Close.
The List entries of Bid Decision attribute are pre-defined by Agile. You can neither add a new list item, nor modify or delete any.
To see the available list items:
In Request for Quote class, go to User Interface Tabs tab.
Double-click the Responses row and go to Attributes:Response tab.
Double-click the Bid Decision attribute.
In Attributes:Bid Decision window, click View Details button. The List:Response_Bid_Decision window opens.
Go to the List tab to see the pre-defined entries.
You need to add criteria to "Modify My Sourcing Project General Information" privilege.
To add criteria to Modify My Sourcing Project General Information Privilege:
Go to Settings > User Settings > Privileges.
Double-click All Privileges.
Type Modify My Sourcing Project in the Value field and click Apply.
Double-click Modify My Sourcing Project row.
Click the arrow button next to the Applied To field.
From the Choices cell, pick Sourcing Projects.General Information.Require RFQ Terms and Conditions and move it in the Selected cell.
|
Note: If you do not find Sourcing Projects.General Information.Require RFQ Terms and Conditions in the Choices list, clear the 'Show visible attributes only check box. |
To add criteria to Read RFQs Privilege in Sourcing Project Manager Role:
Double-click Roles in Settings > User Settings.
Type Sourcing Project Manager in the value field and click Apply.
Double-click Sourcing Project Manager.
Go to Privileges tab.
Double-click the Read RFQs in the Name column.
Click the arrow button next to the Applied To field.
From the Choices cell, pick Requests for Quote.RFQHeader.Require RFQ Terms and Conditions and move it to Selected cell
Click OK.
To add criteria to Read Privilege:
Double-click Read privilege key in Settings > User Settings > Privileges.
Type Read RFQs in the Value field and click Apply.
Double-click Read RFQs.
Click the arrow button next to the Applied To field.
From Choices cell, pick the following and move them to Selected cell
Requests for Quote.Terms and Condition Status.Accept Date
Requests for Quote.Terms and Condition Status.Accept User
Requests for Quote.Terms and Condition Status.Status
Requests for Quote.Terms and Condition Status.Supplier
Click OK.
This section describes ways to configure Product Cost Management specific Agile PLM classes. For details on how to configure Agile PLM classes, see the Agile PLM Administrator Guide.
Product Collaboration and Product Cost Management automatically exchange data between the Item Master and Sourcing Projects. If your Agile PLM system has enabled custom flex fields, you must configure the fields consistently and map them correctly to make sure the data exchange occurs successfully between the Item Master and sourcing projects for those fields.
If you require help customizing your Agile PLM system, contact your Oracle Consulting - Agile Practice representative.
If your company has purchased both Product Cost Management and Product Governance & Compliance solutions, you must decide how to configure the Part Groups class.
|
Note: If you have set the Force Commodity and Part Family to be Identical SmartRule to No, enable the Make Available As attribute in Class:Part groups > User Interface Tabs tab > General Info > Attributes:General Info tab (set Visible to Yes). The Make Available As attribute enables you to specify whether a part group is used as a commodity in PCM, a part family in Product Governance & Compliance (PG&C), or both. |
| Class | Flex Fields Supported | |
|---|---|---|
| This cell is blank. | Page Two | Page Three |
| Sourcing Project | Yes | Yes |
| Request for Quote | Yes | No |
| RFQ Responses | No | No |
To avoid Create New Attribute buttons being disabled (grayed out) in an RFQ or Sourcing Project's Page Two, you must set the Page Two tab as invisible in Java Client.
The creation of a new flex field in Page Two or Page Three is not supported for Request of Quote and Sourcing Projects classes. By default, the Icon "New" in their corresponding Attributes Tabs is disabled (grayed out), however, the Page Two/Page Three attributes can be enabled or disabled in Java Client.
|
Note: User-defined flex fields can be created in Prices and PCO classes. |
To make Page Two invisible in Java Client:
Go to Settings > Data Settings > Classes.
Double-click either Sourcing Projects or Request for Quotes class.
Click User Interface Tabs, and double-click Page Two.
Select the attribute Visible as No.
Click Save and Close.
When you configure flex fields to share data between the Item Master and sourcing projects, make sure you configure the fields consistently across classes. Otherwise, the Map Data To and Publish actions in a sourcing project may not work. If you map a list field to another list field, both fields must be configured to use the same list.
Remember to name flex fields consistently across classes. Before modifying the Name of an attribute, copy the original name into the Description field so that you can identify the original attribute name later.
Product Cost Management does not support user-defined flex fields, except for Product Collaboration classes such as Parts and Manufacturer Parts. Consequently, you cannot map sourcing project attributes to any user-defined flex fields.
Sourcing projects can contain items and manufacturer Parts added directly from the Item Master. They are added as a copy of the part in Item Master, and not as a reference. The item or manufacturer part inside a sourcing project supports only a few flex fields, as opposed to an unlimited amount in the Item Master.
Standard fields on the Title Page tab of Items and the General Info tab of Manufacturer Parts are mapped automatically to related sourcing project AML fields. You may, however, also want to pull data from item and manufacturer part flex fields (such as those on Page Two or Page Three) into the AML and Analysis tab of sourcing projects and the Responses tab of RFQs. You can map custom fields so that sourcing projects automatically pull data from them correctly when you import those objects.
List flex fields (SingleList or MultiList) in a sourcing project have both a List property and a Map Data To property. If you select a value for the Map Data To property, the List property is automatically disabled (you cannot pull data from two places into one field). You can subsequently reconfigure the list field to pull data from another item master field, even after items have already been added to the project. However, when you change the value of the Map Data To property, you will see a message warning that application data already exists with the current settings. If you decide to continue, the original flex field mapping is purged and cannot be recovered.
|
Note: There are a limited number of flex fields provided for the AML tab of sourcing projects, so you cannot map AML attributes to all the flex fields that exist for item and manufacturer part attributes. |
| Field Type | Number of Fields |
|---|---|
| Date | 5 |
| List | 5 |
| Money | 5 |
| Multi-list | 2 |
| Multi-text | 2 |
| Number | 5 |
| Text | 10 |
You can map these fields to flex fields in Item-Page Two & Item-Page Three.
Similarly, a Manufacturer Part in a Sourcing Project has the same number of flex fields. You can map them to flex fields in Manufacturer Parts > Page Two or Page Three.
When you map attributes from Project to the Page Three attributes of Items or Manufacturer Parts, you must ensure that they follow the names of Page Three attributes and point to the same list (for List attributes) across all subclasses of the Item or Manufacturer Part.
To map sourcing project flex fields to Item and Manufacturer flex fields:
Enable and configure any of the following item, manufacturer part, and sites flex fields:
Enable and configure similar flex fields (that is, of the same data type) in the Sourcing Projects class. Make sure the fields are configured consistently with their related Item and Manufacturer Part flex fields. Otherwise, the data transfer between Product Collaboration and Product Cost Management will not work. For more information, see "Tips for Configuring Flex Fields."
The mapping of flex fields for Items & Manufacturer Parts can be done only in Sourcing Projects > AML tab. For each flex field that you enable in Sourcing Projects > AML > Items and in Sourcing Projects > AML > AML, specify the Map Data To property. This establishes the mapping between Product Collaboration and Product Cost Management.
The following table lists the Sourcing Projects flex fields that you can map to Item and Manufacturer Part flex fields.
| Class/Tab | Attributes | Pull From |
|---|---|---|
| Sourcing Projects > AML > Items | Date (5)
List (5) MultiText (2) Text (10) Money (5) Number (10) MultiList (2) |
Items.Page Two fields
Page Three fields |
| Sourcing Projects > AML > AML | Date (5)
List (5) Money (5) MultiList (2) MultiText (2) Number (10) Text (10) |
Manufacturers Parts.Page Two fields
Page Three fields |
You can also enable flex fields on the Sourcing Projects > Analysis > Analysis and Requests for quote > Responses tabs. Fields with an "ipn" prefix and an "mpn" prefix automatically map to the Map Data To fields that you have selected for Sourcing Projects > AML.
For example, the Sourcing Projects > AML > Items > Date01 field shares its Map Data To mapping with Sourcing Projects > Analysis > Analysis > ipnDate01 and Requests for quote > Responses > ipnDate01.
The following table lists IPN and MPN flex fields.
| Class/Tab | Item flex fields | Manufacturer Part flex fields |
|---|---|---|
| Sourcing Projects > Analysis > Analysis | ipnDate (5)
ipnList (5) ipnMoney (5) ipnMultiList (2) ipnMultiText (2) ipnNumber (10) ipnText (10) |
mpnDate (5)
mpnList (5) mpnMoney (5) mpnMultiList (2) mpnMultiText (2) mpnNumber (10) mpnText (10) |
| Requests for quote > Responses | NA | NA |
The following example shows how to configure sourcing projects to map data to flex fields, a Page Two field for items and a Page Two field for manufacturer parts. You can follow these steps to configure other item or manufacturer part flex fields for Product Cost Management.
Step 1: Enable a Page Two field for the Parts class
Under Data Settings, double-click the Classes node. The Classes page appears.
Double-click the Items > Parts class.
Click User Interface Tabs.
Double-click Page Two.
Click the Attributes: Page Two tab.
Double-click Text01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Part Dimensions.
In the Visible field, select Yes.
Click Save.
|
Note: In Java Client, when you, for example, map part.pagetwo.Text01 to Sourcing Project.AML.Items.Text05, this data will be pulled to Text05 in sourcing project.AML tab. If the sourcing project.item.Text05 is enabled, this value will be pulled to sourcing project.items.Text05. |
Step 2: Enable a Page Two field for the Manufacturer Parts class
Under Data Settings, double-click the Classes node. The Classes page appears.
Double-click the Manufacturer Parts > Manufacturer parts class.
Click User Interface Tabs.
Double-click Page Two.
Click the Attributes: Page Two tab.
Double-click Text01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Mfr Part Dimensions.
In the Visible field, select Yes.
Click Save.
Step 3: Map a sourcing project AML attribute to a Page Two attribute for items
Under Data Settings, double-click the Classes node. The Classes page appears.
Double-click the Sourcing Projects class.
Click User Interface Tabs.
Double-click AML.
Click the Attributes: Items tab.
Double-click text1.
|
Note: To map a List or a Multi List field, make sure it points to the same list as pointed by the Page Two field in Items |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Part Dimensions.
In the Visible field, select Yes.
Click Map Data To field. Select Parts.Page Two.Part Dimensions. The AML tab attribute will pull its data from that Page Two attribute.
Click Save.
Step 4: Map a sourcing project AML attribute to a Page Two attribute for manufacturer parts
Go to Data Settings > Classes.
Double-click Sourcing Projects class.
Click User Interface Tabs.
Double-click AML.
Click the Attributes: AML tab.
Double-click text1.
|
Note: To map a List or Multi List field, make sure it points to the same list as pointed by the Page Two field in Manufacturer Parts. |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Mfr Part Dimensions.
In the Visible field, select Yes.
Click Map Data To field. Select Manufacturer Parts.Page Two.Mfr Part Dimensions. The AML tab attribute pulls its data from that Page Two attribute.
Click Save.
Step 5: Enable corresponding text attribute in Sourcing Project > Analysis tab
Go to Data Settings > Classes.
Click User Interface Tabs.
Double-click Analysis.
Click the Attributes: Analysis tab.
Double-click ipnText1.
|
Note: To map a List or Multi List field, make sure it points to the same list as pointed by the Page Two field in Items. |
|
Note: Each flex field with the "ipn" prefix is automatically mapped to the same Item flex field as its related Sourcing Projects > AML > Items flex field. |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Part Dimensions.
In the Visible field, select Yes.
Click Save.
Double-click mpnText1.
|
Note: To map a List or multiList field, make sure it points to the same list as pointed by the Page Two field in Manufacturer Parts |
|
Note: Each flex field with the "mpn" prefix is automatically mapped to the same Manufacturer Part flex field as its related Sourcing Projects > AML > AML flex field. |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Mfr Part Dimensions.
In the Visible field, select Yes.
Click Save.
Step 6: Enable corresponding text attributes in RFQ Responses > Response tab
Go to Data Settings > Classes.
Double-click the Requests for Quote > Requests for quote class.
Click User Interface Tabs.
Double-click Responses.
Click the Attributes: Responses tab.
Double-click ipnText 1.
|
Note: To map a List or Multi List field, make sure it points to the same list as pointed by the Page Two field in Items |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Part Dimensions.
In the Visible field, select Yes.
Click Save.
Double-click mpnText1.
|
Note: To map a List or Multi List field, make sure it points to the same list as pointed by the Page Two field in Manufacturer Parts. |
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, change the value to Mfr Part Dimensions.
In the Visible field, select Yes.
Click Save.
Your company can enable custom price fields, such as additional material or non-material prices, for Item Master classes, such as Parts and Manufacturer Parts, and the Sourcing Project class. After you receive price quotes from a supplier, you can publish the prices from the project back to the Item Master. For subsequent sourcing projects, you can verify existing price scenarios by doing price lookups from the Analysis tab.
The Price Details tab of a sourcing project provides several price flex fields that you can enable for Product Cost Management. There are both Material Price Adder fields and Non Material Price Adder fields.
Price adders are essentially overhead rates. Price adders can be the additional cost of an item such as the intellectual property value, the royalty value, and so on, apart from the material cost. You are limited to seven price adder fields, which are common to all projects. Price adder fields can be enabled for suppliers or buyers, that is, for Supplier or Internal only (Buyer) purposes.
|
Important: There are seven Material Price Adder fields. All the material price adders can be set to visible "internally" (these will not be visible to suppliers) or to suppliers (suppliers will be able to view and edit these fields). You can configure these fields also if they have to store a "fixed" value or a "percent" value. |
Non-material prices are prices that include the labor rate, sales tax, and other overhead costs.
The following table lists Material Price and Non-Material Price flex fields you can enable in different classes. Make sure you configure the fields consistently from one class to another.
The fields are automatically mapped to one another based on ID. For example, Non Material Price 1 in one class is automatically mapped to other Non Material 1 fields. For more information about configuring flex fields, see "Tips for Configuring Flex Fields."
| Class/Tab | Material Price Attributes | Non-Material Price Attributes |
|---|---|---|
| Sourcing Projects > Price Details | 7 Material Price Adders | Non Material Price (25) |
| Sourcing Projects > Analysis > Non Material Price Entry | n/a | nonMaterialModifier (20)
Non-Material Price (5) |
| Prices > Published Prices > Price Lines | Material Price (7) | Non Material Price (25) |
| Prices > Quote Histories > Price Lines | Material Price (7) | Non Material Price (25) |
| Items > Documents > Prices | Material Price (7) | Non Material Price (25) |
| Items > Parts > Prices | Material Price (7) | Non Material Price (25) |
| Manufacturer Parts > Prices | Material Price (7) | Non Material Price (25) |
Price Adders can be either material or non-material. Many customers require partners/suppliers to apply adders to the top level of assemblies, not at the individual line items. Often, these adders are represented as a percent (%) value instead of a fixed value.
Most non-material costs can only be a fixed value, so to use a percent value, configure one of the percent-specific Non-Material Adders that are configurable.
The price adders that are configurable are:
Material Adders - numbers 1 through 7 are configurable as Internal or Supplier.
Non-Material Adders - numbers 20 through 25 are configurable as a calculation type of either percent (%) or a fixed value.
When a supplier enters a percent value, the system will multiply the percentage with the material cost and the result is added to the non-material price.
|
Note: Non-material percent types are useful only if a material price exists. |
The attributes are added to the total cost and are not associated with the non-material costs as shown in the table below.
| Non-Material Price | Material Price |
|---|---|
| Non-Material Price_1 (fixed value) = 50 | Material Price = 100 |
| Non-Material Price_20 (percent value) = 25 | NA |
| Total Non-Material Price = 75
((0.25 * 100) + 50) |
Total Material Price = 100 |
| Total Extended Cost = 175 | NA |
You can configure Material Adders numbered 1 through 7 as Internal or Supplier, with a fixed or percent value. The Material Adders function as Cost Elements that are added to every Cost Estimate after the initial Estimate of Costs for material and labor. Adders typically include General and Administrative Cost, Overhead and Profit.
|
Note: The Material Adders can be given a fixed or percent value. |
Configuring Material Adders
Go to Data Settings > Classes.
Double-click the Sourcing Projects class and go to User Interface Tabs tab.
Double-click Price Details and go to Attributes: Price Details tab.
Double-click Material Price Adder 1.
Select either Fixed or Percent from the Calculation Type drop-down list
Select either Internal Only or Supplier from the Visible To drop-down list
Click Save and Close.
Non-material costs support a percent value of Material Costs. Some costs that are added to a Cost Estimate, such as royalties, warranties, and guarantees.
You can configure Non-Material Adders 20 through 25 to support a percent value of Material Costs.
|
Note: Sometimes the Non-Material Adders are referred to as Non-Standard Adders in the industry. |
Configuring Non-Material Adders as a Percent value:
Go to Data Settings > Classes.
Double-click the Sourcing Projects class and go to User Interface Tabs tab.
Double-click Price Details and go to Attributes: Price Details tab.
Double-click Non-Material Price 20.
|
Note: You can only configure Non-Material Price Adders 20 to 25 as "Percent." All others are set to "Fixed" and are not configurable. |
Select either Fixed or Percent from the Calculation Type drop-down list.
Select Yes in the Visible list.
Click Save and Close.
The following example shows how to enable a Non-Material Price flex field called Labor Cost Per Unit for several Agile PLM classes. You can follow these steps to configure other price flex fields for Product Cost Management.
Enabling a Labor Cost Per Unit Field
Go to Data Settings > Classes.
Complete steps 3 through 9 for each of the following steps:
a. For Parts: Double-click the Items > Parts class
b. For Documents: Double-click the Items > Documents class
c. For Manufacturer Parts: Double-click the Manufacturer Parts > Manufacturer parts class
d. For Published Prices: Double-click the Prices > Published Prices class
e. For Quote Histories: Double-click the Prices > Quote Histories class
f. For Sourcing Projects: Double-click the Sourcing Projects > Sourcing projects class.
Go to User Interface Tabs tab.
Double-click Prices and go to Attributes: Prices tab.
Double-click Non-Material Price1.
Cut the text from the Name field and paste it in the Description field. This will help you identify the original attribute name.
In the Name field, type Labor Cost Per Unit.
Select Yes in the Visible list.
Click Save.
|
Note: In all the above, to use a specific price field (like Non-Material Price1), you must use the same Non-Material Price1 field in all corresponding classes (Parts, Documents, Manufacturer Parts, Published Prices, Quote Histories & Sourcing Projects). You cannot use Non-Material Price1 to capture Labor Cost in Parts Class and Non-Material Price 2 to capture the same in Manufacturer Parts Class. |
RFQ Responses contain a header area that can include several flex fields. If you enable any flex fields on the Responses tab of RFQs, you can map to Page Two fields in Published Prices & Quote Histories. When you publish the responses to the Item Master, the flex fields that you map will be updated.
To map Response flex fields in Project-Analysis tab to Page Two or Price Line fields in Published Prices & Quote Histories
Enable and configure any of the following flex fields in the Sourcing Projects class. The same set of flex fields is also available in "Requests for Quote" class and can be filled by the Suppliers when responding to RFQs.
Enable and configure similar flex fields (that is, of the same data type) listed in the tables below. Make sure the fields are configured consistently with their related Requests for Quote flex fields. Otherwise, the data transfer between Product Collaboration and Product Cost Management will not work. For more information, see "Tips for Configuring Flex Fields."
| Class/Tab | Attributes |
|---|---|
| Sourcing Projects > Analysis > Analysis | resp Date (5)
resp List (5) resp Money (10) resp MultiList (2) resp MultiText (2) resp Number (10) resp Text (10) |
| Items > Documents > Prices | Date (5)
List (5) Money (5) MultiList (2) MultiText (2) Number (10) Text (10) |
| Items > Parts > Prices | NA |
| Manufacturer Parts > Prices | NA |
| Prices > Published Prices > Page Two | NA |
| Prices > Published Prices > Page Three | NA |
| Prices > Published Prices > Price Lines | NA |
| Prices > Quote Histories > Page Two | NA |
| Prices > Quote Histories > Page Three | NA |
| Prices > Quote Histories > Price Lines | NA |
Finally, enable and configure flex fields on the Sourcing Projects > Projects > Analysis > Analysis tab. Make sure you specify the Map Data To property. This establishes the mapping between Product Cost Management and Product Collaboration.
To publish data from Flex Fields in Sourcing Project to Item Master, you can use the Map Data To field. This field actually functions to "push" data to that location, and requires a value.
| Class/Tab | Attributes | Push Data To |
|---|---|---|
| Sourcing Projects > Analysis > Analysis | respDate (5)
respList (5) respMoney (10) respMultiList (2) respMultiText (2) respNumber (10) respText (10) |
Prices.Price Lines fields
Prices.Page Two fields Page Three fields |
The following example shows how to enable a Response flex field called Supplier Note in Sourcing Project so that it is mapped to "Published Price" or "Quote History" classes. You can follow these steps to configure other RFQ flex fields for Product Cost Management.
Step 1: Enabling a Supplier Note field for the Responses tab of RFQs
Go to Data Settings > Classes.
Double-click the Requests for Quote > Request for quote class.
Click User Interface Tabs.
Double-click Responses.
Click Attributes: Responses.
Double-click resp MultiText 1.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 2: Enabling a Supplier Note Field for Published Prices
Go to Data Settings > Classes.
Double-click the Prices > Published Prices class.
Click User Interface Tabs.
Double-click Price Lines.
Click the Attributes: Price Lines tab.
Double-click MultiText01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 3: Enabling a Supplier Note Field for Quote Histories
Go to Data Settings > Classes.
Double-click the Prices > Quote Histories class.
Click User Interface Tabs.
Double-click Price Lines.
Click the Attributes: Price Lines tab.
Double-click MultiText01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 4: Enabling a Supplier Note Field for Parts
Go to Data Settings > Classes.
Double-click the Items > Parts class.
Click User Interface Tabs.
Double-click Prices.
Click the Attributes: Prices tab.
Double-click MultiText01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 5: Enabling a Supplier Note Field for Documents
Go to Data Settings > Classes.
Double-click the Items > Documents class.
Click User Interface Tabs.
Double-click Prices.
Click the Attributes: Prices tab.
Double-click MultiText01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 6: Enabling a Supplier Note Field for Manufacturer Parts
Go to Data Settings > Classes.
Double-click the Manufacturer Parts > Manufacturer parts class.
Click User Interface Tabs.
Double-click Prices.
Click the Attributes: Prices tab.
Double-click MultiText01.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
Click Save.
Step 7: Enabling a Supplier Note field for the Analysis tab of sourcing projects
Go to Data Settings > Classes
Double-click the Sourcing Projects > Sourcing projects class.
Click User Interface Tabs.
Double-click Analysis.
Click the Attributes: Analysis tab.
Double-click resp MultiText 1.
Copy the text in the Name field and paste it into the Description field. This will help you identify the original attribute name.
In the Name field, type Supplier Note.
In the Visible field, select Yes.
In the Map Data To field, select "Published Prices.Price Lines.MultiText01". Even though the drop-down will list the fields from both Published Prices & Quote Histories, you can choose only one.
You can also map the above flex field to a Multi Text field in Page Two tab of "Published Prices" class. The above example maps it to the Price Lines tab of the "Published Prices" class.
|
Note: Although the field is named Map Data To, in this case it pushes data to the selected field when you publish responses to the Item Master. |
Click Save.
This section explains how to set up the BOM filters. For more details on concepts and usage of BOM filters, see the "Working with Sourcing Projects" chapter which contains a section, "Adding Items to a Project," that explains how to set up the BOM filter in Web Client.
Set up a Sourcing Project Class BOM attribute:
Go to Data Settings > Classes.
Double-click Sourcing projects class.
Go to User Interface Tabs tab and double-click Items in the list.
Go to Attributes: Items tab.
Double-click Filter in the Attributes name list.
Select Yes from the Visible drop-down list.
Rename the Filter for your purposes. For example: "Production BOM."
To distinguish between BOM items that you will filter for import, you must first set up and name certain attributes for each specific BOM that you plan to import.
For example, if you have two versions of the same BOM, one called "Production" and another called "Prototype," you would need to set up a list attribute for each BOM. It is suggested that you name the list attribute based on your use case scenario. You can use any existing attribute as a template; this example uses "BOM List 3" as a template.
|
Note: BOM Filters are supported in the Parts class, but not in the Documents class. |
|
Note: A BOM Filter supports filtering on multiple BOM flex fields only. It supports only Text1-5, Numeric1-5, List1-5 that are defined in Item.BOM tab, besides Qty from the Item.BOM tab. It does not support filtering on date fields, multi-list fields, and multi-text fields. |
Set up a Parts Class BOM attribute:
Go to Data Settings > Classes.
Double-click Parts class.
Go to User Interface Tabs tab and double-click BOM.
Go to Attributes: BOM tab.
From the list of attribute names, double-click the attribute you will use as a template. For example, "BOM List 3."
Copy the original attribute's name into the description field and rename the attribute according to your use case scenario, for example: "Prod Load."
In the Visible field, select Yes.
To the right of the List field, click the New List button to create a list. A Create List window pops up.
Name the list the same as the new attribute, and give a description. For example, name it "Prod Load" and give it the description, "Filter."
You may Enable or Disable the New List by making appropriate selection in Enabled drop-down list.
Chose Yes or No from Cascade drop-down list to create a cascaded List.
a. If you select No for Cascade, the List window (the New List name window) appears along with the Create a new list value pop-up. Enter a name in Name field and click Add button, or click Add Another button to continue adding more list values.
b. You can also add the list values later. For more information on adding or configuring Lists, see Lists.
c. If you select Yes for Cascade, the List window (the New List name window) appears. In the List tab, you will find the New List Name as the first item, denoting that it is the base value of the Cascade List. Click New button to add cascade list values under this.
d. The Create a new list value pops up. Enter a name in Name field and click Add button, or click Add Another button to continue adding more list values. These list values appear as cascaded under the New List name.
e. You can add list values to these list values to get any level of cascaded lists. To do so, select a List Value and click New button. Follow step 3 above.
f. Click Save and Close to return to BOM List 3.
Click Save and Close.
For detailed instructions on how to create a sourcing project using this new BOM filter, refer to "Working with Sourcing Projects".
The PCM money attributes' decimal values are controlled by the Price Scale preference setting. The Price Scale can range from 0 to a maximum of 9. The default value is 6. If you attempt to lower the value of the Price Scale, a warning appears to remind you that lowering the Price Scale may cause rounding errors.
To set Price Scale:
Go to Server Settings > Preferences.
On the General Information tab, find the Price Scale field.
Set the new value of Price Scale.
Click Save.
The value set by the administrator is copied to all of the PCM money attributes and cannot be overwritten on the attribute itself.
In Agile PLM, a preconfigured event is an automation that occurs when a user performs a task that is specified by the event mask. The triggered event then results in event outcome, such as the delivery of a notification to a user. An Agile administrator, with the appropriate privileges, can manage the different components of the event process.
There is limited event functionality for the PCM solution, however, some events are configurable for PCM objects including Sourcing Projects, RFQs, RFQ Responses, Suppliers, Prices, and PCOs. Additionally, some events are supported only for certain tabs of an object.
The following content breaks down the PCM objects tab by tab to show you which event types are supported.
For the Commodity object:
(at object level) - Create Object, Delete Object, Export Object, Save As Object
General Info Tab - Update Table
Parts Tab - Update Table
Relationships Tab - Update Table
Attachments Tab - Check In Files, Check Out Files, Get File, Update Table
For the Price object:
(at object level) - Create Object, Delete Object, Export Object, Save As Object
General Information Tab - Update Table
Relationships Tab - Update Table
Attachments tab - Check In Files, Check Out Files, Get File, Update Table
For the PCO object:
(at object level) - Create Object, Delete Object, Export Object, Save As Object, Change Status For Sourcing Object
Cover Page Tab - Update Table
Relationships Tab - Update Table
Attachments tab - Check In Files, Check Out Files, Get File, Update Table
For the RFQ object:
(at object level) - Delete Object, Change Status For Sourcing Object
Cover Page Tab - Update Table
Relationships Tab - Update Table
Attachments tab - Check In Files, Check Out Files, Get File, Update Table
For the RFQ Response object:
Cover Page Tab - Update Table
Relationships Tab - Update Table
Attachments tab - Check In Files, Check Out Files, Get File, Update Table
For the Sourcing Project object:
(at object level) - Create Object, Delete Object, Save As Object, Change Status For Sourcing Object
General Information Tab - Update Table
Relationships Tab - Update Table
Attachments tab - Check In Files, Check Out Files, Get File, Update Table
For the Supplier object:
(at object level) - Create Object, Delete Object, Export Object, Save As Object
General Info Tab - Update Table
Relationships Tab - Update Table
Attachments Tab - Check In Files, Check Out Files, Get File, Update Table
The following are examples of practical situations in which events could be used in PCM:
Once a sourcing buyer sets authorized users for a sourcing project or an RFQ, notifications can be sent to the users by using the Update Table event type.
You can use the Create Object event type to automatically open a project for RFQ creation.
You can use the Create Object event type to carry prices over to a newly created MCO.
A global commodity manager imports parts into a sourcing project. some parts are associated with specific regional commodity managers. You can use the Change Status for Sourcing Object event type to send notifications to the regional managers once the project is open and ready for RFQ creation.
There are many other situations in which the use of events may be a useful and efficient way to achieve a certain outcome. For more details about events and how to configure and manage them, see the Agile PLM Administrator Guide.
