Original requirements in
Split from
Create a new custom object : named Pricing Campaign CPC with: the following characteristics:
| Label | Pricing Campaign CPC |
|---|---|
| Plural Label | Pricing Campaign CPCs |
| Object Name | Pricing_Campaign_CPC |
| Description | IPP-182 |
| Record Name | Pricing Campaign CPC Name |
| Data Type | Auto Number |
| Display format | CPC -{00000000} |
| Allow Reports | True |
| Allow Activitie | True |
| Track Field History | True |
| Allow in Chatter Groups | False |
| Enable Licensing | False |
| Allow Sharing | True |
| Allow Bulk API Access | True |
| Allow Streaming API Access | True |
| Deployment Status | Deployed |
| Allow Search | True |
| Record Types | None required (Master only) |
Data Dictionary - Pricing Campaign CPC
| Field Name | API Name | Data Type | Track History | Mandatory field | Read Only | Picklist Values or formula | Help Text | Profile access | Comments | Layout Section | Needed for initial Data Load (Kunal files)? | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Owner | Owner | Lookup(User,Group) | Yes | Yes (default) | Pricing Campaign CPC Owner (standard Owner field of the object); See Automation Section | Information | |||||
| 2 | Account Manager Review | Account_Manager_Review__c | Picklist | Yes |
Should we have a default value for this picklist called "Not Started" - aka, every new CPC record created will always have this default value until a User changes it (to Rejected or Commited) AND a VR to prevent Users from making this field = null? (making it Required is a problem because it would "force" uploaders/Dataiku to always have to input "Not Started" at CPC record creation | Restrict picklist to the values defined in the value set = TRUE | Account Manager input | |||||
| 3 | Annual sales | Annual_sales__c | Number(18, 0) | Yes, on layout | Metrics | |||||||
| 4 | Annual volume | Annual_volume__c | Number(18, 0) | Yes, on layout | Metrics | |||||||
| 5 | Capped Reco price - Document Currency | Capped_Reco price_Document_Currency__c | Currency(18, 0) | Not relevant for initial Data load | ||||||||
| 6 | Capped Reco price - Pricing Currency | Capped_Reco price_Pricing_Currency__c | Currency(18, 0) | Not relevant for initial Data load | ||||||||
| 7 | Capped Recommended price (%) | Capped_Recommended_price__c | Percent(18, 0) | Yes, on layout | Overall | Not relevant for initial Data load | ||||||
| 8 | Committed price | Committed_price__c | Number(18, 0) | Pre-populate with Capped Recommended Price on record creation NOE, Julien- does it make sense to pre-populate a Number field with the initial value of a Percent field? | Account Manager input | |||||||
| 9 | Contracting model | Contracting_model__c | Text Area(255) | Dimension | Not relevant for initial Data load | |||||||
| 10 | Country | Country__c | Formula (Text) | TEXT(Sold_To__r.Payment_Country__c) | NOE, Julien - Account object has 8 different fields where "Country" can be captured - which one should we look to to expose in the Pricing Campaing CPC record? Prod Analysis here | Dimension | Not relevant for initial Data load | |||||
| 11 | CPC Status | CPC_Status__c | Picklist |
| Workfow to create : If Commit/Reject is Blank: WIP NOE, Julien - unless there is a need to allow Users to change this value at their own will - this does not seem like it should be a picklist field, rather a formula field that retrieves the value from:
| Overall | ||||||
| 12 | Dataiku ID | Dataiku__ID__c | Text(50) (External ID) | Yes, on layout | Field to be populated by Dataiku with the Pricing campaign ID | Not relevant for initial Data load | ||||||
| 13 | Decision logic (path to microsegment) | Decision_logic_path_to_microsegment__c | Text Area(255) | Yes, on layout | To be aligned with Cheryl | Model Data | Not relevant for initial Data load | |||||
| 14 | Document Currency | Document_Currency__c | Currency(18, 0) | Dimension | Not relevant for initial Data load | |||||||
| 15 | End Use | End_Use__c | Picklist | X NOE, Julien why do we need a picklist field just to make it read-only??? | Use Global Value Set: End Use | Dimension | Not relevant for initial Data load | |||||
| 16 | Forecasted annual volume | Forecasted_annual_volume__c | Number(18, 0) | If below MOQ populate first bracket on quote NOE, Julien what is the purpose of this requirement/automation? Where would the MOQ value be retrieved from? | Metrics | Not relevant for initial Data load | ||||||
| 17 | FX rate used | FX_rate_used__c | Number(18, 0) | Yes, on layout | Metrics | Not relevant for initial Data load | ||||||
| 18 | Important features | Important_features__c | Long Text Area(32768) | X NOE, Julien why do we need a long text area field just to make it read-only??? | Model Data | Not relevant for initial Data load | ||||||
| 19 | Last price | Last_price__c | Number(18, 0) | Yes, on layout | Metrics | Not relevant for initial Data load | ||||||
| 20 | Local Currency | Local_Currency__c | Currency(18, 0) | Yes, on layout | NOE, Julien What is the purpose of this field? Define a currency (ie USD, EUR, etc) or define a currency value (ie, 5 USD or 4 EUR). | Dimension | Not relevant for initial Data load | |||||
| 21 | Market Cluster | Market_Cluster__c | Picklist | XNOE, Julien why do we need a picklist field just to make it read-only??? | Use Global picklist values NOE, Julienthere is no Global picklist value for Market Cluster. | Overall | ||||||
| 22 | Market segment | Market_Segment__c | Picklist | XNOE, Julien why do we need a picklist field just to make it read-only??? | Use Global Value Set: Market Segment Global | Dimension | Not relevant for initial Data load | |||||
| 23 | Microsegment (node) | Microsegment_node__c | Number(18, 0) | Yes, on layout | Model Data | Not relevant for initial Data load | ||||||
| 24 | Modelling approach | Free text | X | Dimension | Not relevant for initial Data load | |||||||
| 25 | Modelling level | Free text | X | Dimension | Not relevant for initial Data load | |||||||
| 26 | Node price | Number(18, 0) | X | Metrics | Not relevant for initial Data load | |||||||
| 27 | Price reco rationale | URL | X | Link to Dataiku chart | Account Manager input | Not relevant for initial Data load | ||||||
| 28 | Pricing Campaign | Lookup(Pricing Campaign) | Yes, visible only on Compact Layout | Dimension | on initial load, 3 campaigns: Long Tail, non-Long Tail and H2 | |||||||
| 29 | Pricing Currency | Currency(18, 0) | Yes | Overall | Not relevant for initial Data load | |||||||
| 30 | Pricing Increment - Document Currency | Currency(18, 0) | Not relevant for initial Data load | |||||||||
| 31 | Pricing Increment - EUR | Currency(18, 0) | Not relevant for initial Data load | |||||||||
| 32 | Pricing Increment - Pricing Currency | Currency(18, 0) | Not relevant for initial Data load | |||||||||
| 33 | Pricing region | Picklist | Yes | Use picklist value - same as quote ones | Overall | Not relevant for initial Data load | ||||||
| 34 | Product | Product lookup | Yes | Compact Layout | Retrieved from Product Code (Material Group Code); If failing to match during upload, needs to notify campaign owner | Overall | will come from Product code automation | |||||
| 35 | Product code | Free text | Yes | X | material_group_product_lvl3_code on dataiku export Material Group Code field at product level | Overall | ||||||
| 36 | Product H4 | Picklist | X | Use Global picklist values | Dimension | Formula field to bring the Product H4 Name (ie. Aquivino) | ||||||
| 37 | Projected sales impact | Number(18, 0) | X | Overall | Formula - will be used for Dataiuk entries only | |||||||
| 38 | Quantified importance of feature | Number(18, 0) | X | Model Data | Not relevant for initial Data load | |||||||
| 39 | Quote | Lookup to Opportunity automatically filled if Quote was created via that specific CPC record | X | Not relevant for initial Data load | ||||||||
| 40 | Reason for rejection | Picklist | - Competitive threat - Growth customer or initiative - Price fixed by contract - Customer or product discontinued - Other (Please describe) | Account Manager input | Not relevant for initial Data load | |||||||
| 41 | Region | Formula field to capture the Sold-to Account ECCO Reporting Region | Formula field | Use Global picklist values | Dimension | Not relevant for initial Data load | ||||||
| 42 | Rejection description | Free text | Account Manager input | Not relevant for initial Data load | ||||||||
| 43 | Sold-To | Account Lookup | Compact Layout | For full CPC - Needs to be aligned with account access rules (confidentiality, roll up to managers) | Retrieved from Sold To "SAP Code"; If failing to match during upload, needs to notify campaign owner Check SAP Code at account level. | Overall | Not relevant for initial Data load | |||||
| 44 | Sold-To SAP Name | Free text | X | To store the SAP Name of the Sold-To "Account" | Overall | |||||||
| 45 | Sold-To Code | Free text | Yes | X | Overall | |||||||
| 46 | Team Cluster | Picklist | Formula | Formula field to grab value from Account;s Team Cluster | Dimension | Not relevant for initial Data load | ||||||
| 47 | Uncapped Recommended price - EUR | Number(18, 0) | X | Metrics | Not relevant for initial Data load | |||||||
| 48 | Uncapped Recommended price (%) | Number(18, 0) | X | Metrics | Not relevant for initial Data load | |||||||
| 49 | Unit of Measurement | Picklist | Same values as Unit of Measurement at Pricing setting level: Retrieve value of "Unit of Measure" from the corresponding product pricing setting (Region, currency, market segment) | Not relevant for initial Data load | ||||||||
| 50 | Weighted average price | Number(18, 0) | X | Metrics | Not relevant for initial Data load |
Validation Rule(s)
| Validation Rule Name | Formula | Error Message | Error Location | |
|---|---|---|---|---|
| Account_Manager_Rejected |
| Please provide a Reason for Rejection | Field: Reason for Rejection |
Sharing and security : Private (only Owner and user above in role hiearchy) + Edit access. Do we need to give a view all and/or modify all to some profiles or users ? Is some region managers who need to see more than their records ? What about confidential accounts ? Access only by owner or account team ? Product manager access ?
Don’t create tab for this object
Create a “Pricing Campaign CPC” tab at Pricing campaign level
Automations Required
1. On record insertion - the field Sold-To (Account lookup) needs to be automatically populated with the Account found via the value available in the Pricing Campaign CPC field Sold-To Code - the Account field where the code can be queried is:
SAP Code | SAP_Sold_To_Number__c | Text(10) (External ID) (Unique Case Insensitive) |
2. On insertion of Pricing Campaign CPC record - the standard Owner User lookup needs to be the same as the Account Owner from the Account lookup labeled as Sold-To