Functional Specification

Functional Specification
Coke One North America - CONA
Functional Specification -
Enhancements
Title of Enhancement -
MTO-030-010-010 New Field to Allow Activation/Deactivation of Trade Promotions
(Gap 48)
FSD_E_sss-nnn-nnn-nnn_dddddddddddd_ggg.docx Page 0 of 10
Classified - No Category
Table of contents
1 Object Overview ...................................................................................................................... 2
1.1 Document Details ................................................................................................................................. 2
1.2 Revision History ................................................................................................................................... 2
1.3 Business Details ................................................................................................................................... 2
1.4 Related Documents .............................................................................................................................. 2
1.5 Responsible Organizations .................................................................................................................. 3
1.6 Object Technical Details....................................................................................................................... 3
2 Functional Overview ............................................................................................................... 3
2.1 Enhancement Description .................................................................................................................... 3
2.2 Detailed Requirement........................................................................................................................... 3
2.3 Flow Diagram ....................................................................................................................................... 6
2.4 Switch Framework ................................................................................................................................ 6
2.5 Security, Integrity and Controls ............................................................................................................ 6
2.6 Assumptions ......................................................................................................................................... 6
3 Additional Information ............................................................................................................ 6
3.1 Configuration Requirements ................................................................................................................ 6
3.2 Custom Table/Structure Definitions ..................................................................................................... 7
3.3 Messages/ Error handling .................................................................................................................... 7
3.4 Performance Consideration.................................................................................................................. 7
3.5 Others ................................................................................................................................................... 7
4 Business Impact Analysis ...................................................................................................... 7
5 Change Management Requirements ...................................................................................... 8
6 Testing ..................................................................................................................................... 8
6.1 Functional Unit Testing Requirement ................................................................................................... 8
7 Appendix .................................................................................................................................. 9
7.1 Glossary of Terms ................................................................................................................................ 9
8 Review/Sign-off ......................................................................................................................10
8.1 Review Feedback and Comments ..................................................................................................... 10
New Field to Allow Activation/Deactivation of

Trade Promotions (Gap 48)
1 Object Overview
1.1 Document Details

Release 1.0 SAP Module CRM-TPM
Complexity Medium Priority High
Stream Market-To-Order (MTO)
Document
Location
1.2 Revision History

Date Version Description Author
4/30/2013 1.0 Initial Creation Gerald Kainz
6/03/2013 Replaced MCM Activation by Mobile Activation Gerald Kainz
Marked Archiving as Destination
6/26/2013 Added Unit Test Requirements Gerald Kainz
1.3 Business Details

Impacted UPM L2 MTO-030 Trade Promotion Management and Optimization
Impacted UPM L3 MTO-030-010 Promotion planning
Impacted UPM L4 MTO-030-010-010 Identify and create promotion options
1.4 Related Documents

Document Link to File Comment
Report Tech Design n/a
Business Requirement https://partner.coca-
Report/ Functional cola.com/sites/CONA/Project%20Delivera
Design Document bles%20Library/10%20Customer/CONA_
TP_activation_BRR.docx
Process Design https://partner.coca-
Document cola.com/sites/CONA/Project%20Delivera
bles%20Library/10%20Customer/CONAR
10_PDD_MTO-030-010-
010_Identify_and_create_promotion_optio
ns_48.xlsx
Other n/a
1.5 Responsible Organizations

Business / Process Owner CCBCC: Darrel Thompson, Jeff Bundy
CCBCU: Mike Suco, Tommy Ammons, Chip Sutter
CCR: Stennis Shotts (SFA), Jim Ryan (Price Strategy), Kevin Hagan (Price
Execution), Jason Reiling (Promotions)
Swire: Scott Neeley, Teresa Martinez, Jeff Edwards, Heather Curtis, Janice
Alires, Linda Rogers
Functional Designer Gerald Kainz
1.6 Object Technical Details

Associated Transaction Code TPM-WebUI: Create Trade Promotions
Objects/Transactions Affected Trade Promotion
Design Alternatives
2 Functional Overview
2.1 Enhancement Description

Trade promotions need to be enhanced to allow mobile device (CAS) control of calculation.
Possible scenarios are
 Can be activated
o Trade promotion needs to be activated on the mobile device (CAS) prior to calculation.
Default value is deactivated, meaning no calculation will take place.
 Can be deactivated
o Trade promotion can be deactivated on the mobile device (CAS) to prevent further
calculation. Default value is activated, meaning promotion will be calculated according to
specifications.
 Cannot be changed
o Validity of trade promotion is defined in the backend (CRM-TPM) and cannot be influenced
by mobile device (CAS)
This feature will mainly be used for Traditional Trade.
2.2 Detailed Requirement

WebUI Enhancements
New Field on Trade Promotion Header “Mobile Activation” for Planning Level:
 ZT01 – Discounts / Rebates Promotion
 ZT02 – Free Goods Promotion
 ZT03 – Value Added Consumer Promotion
Please note that template already has field “MCM Pricing” implemented. This field should be reused for this
functionality.
In addition, field “MCM Relevance” should be removed from configuration for screens (removed from
available fields list).
Possible values for field “Mobile Activation” are

 Cannot be changed (=Default)
o Validity of trade promotion is defined in the backend (CRM-TPM) and cannot be influenced
by mobile device (CAS)
 Can be activated
o Trade promotion needs to be activated on the mobile device (CAS) prior to calculation.
Default value is deactivated, meaning no calculation will take place.
 Can be deactivated
o Trade promotion can be deactivated on the mobile device (CAS) to prevent further
calculation. Default value is activated, meaning promotion will be calculated according to
specifications.
General checks to be implemented:

 Only enable field “Mobile Activation” for data for pricing relevant trade promotions. Set to display-only
when pricing relevant is not checked.
Checks to be implemented when promotion is saved:
 Don’t allow “Mobile Activation” different then “Cannot be changed” for

o Off-Invoice promotions
Mobile Activation option “Can be activated” or “Can be deactivated” not allowed for
Condition Usage = “BO” of selected Condition Type (Combination Spend Type / Spend
Category / Spend Method / Discount Method)
=> error message “Mobile activation or deactivation not allowed for rebate promotions”
o Assortment Pricing / Bonus Buy

Mobile Activation option “Can be activated” or “Can be deactivated” not allowed for Spend
Types Z0AP = Assortment Pricing and Z0BB = Bonus Buy
=> error message “Mobile activation or deactivation not allowed for Assortment Pricing /
Bonus Buy Promotions
Please note that this functionality might be implemented in an upcoming release!
Checks to be implemented when promotion status is released:

 Set field Mobile Activation to display only
ECC-Integration
Need to pass field “Mobile Activation” to ECC when promotion is released. Implement a Function Module
(OTC team to provide FM) and pass following information:
 Trade promotion ID
 Campaign ID
 Mobile Activation
Archiving (Destination)
Custom program to archive Promotion Exception Data from ECC tables when trade promotion is archived
and data deleted in CRM.
2.3 Flow Diagram
2.4 Switch Framework

Please specify the switch framework information in this section. Provide the business functions that can be
controlled through the switches.
Business Function Link Technical Object
Please provide the business function Please mention the technical object that will be assigned to this
that can be made switchable. business function.
2.5 Security, Integrity and Controls

To detail the security requirements for processing this object, any data integrity issues associated with the
object and the teams that will be responsible for processing the object
2.6 Assumptions
Describe any assumptions that have been made in the process of completing this design.
ID Notes
1 [Enter assumption or comment here]
3 Additional Information
3.1 Configuration Requirements

Specify the configuration requirements for this object. Like in case of forms specify the configuration for
output type etc.
3.2 Custom Table/Structure Definitions

Specify any custom table that needs to be created for this development.
Field Name Primary Key (Yes) Description Check Table
3.3 Messages/ Error handling

Message Text Logic Reference
“Mobile activation or deactivation Mobile Activation option “Can be activated” or 2.2 Detailed
not allowed for rebate promotions” “Can be deactivated” not allowed for Condition Requirement >
Usage = “BO” of selected Condition Type WebUI
(Combination Spend Type / Spend Category / Enhancements
Spend Method / Discount Method)
“Mobile activation or deactivation Mobile Activation option “Can be activated” or 2.2 Detailed
not allowed for Assortment Pricing “Can be deactivated” not allowed for Spend Requirement >
/ Bonus Buy Promotions Types Z0AP = Assortment Pricing and Z0BB = WebUI
Bonus Buy Enhancements
3.4 Performance Consideration

Specify if there are any specific performance factors that need to be taken into consideration during
development
3.5 Others
4 Business Impact Analysis

Overall Risk Assessment is determined using the following criteria:
A CR is classified as “High Risk” if any of the following are true:
• “Business Priority” is identified as “High”
• “Business Criticality to Deliver” is identified as “High”
• “Confidence Level in ability to deliver” is identified as “Low”
• Business determines “Risk to Critical Business Operations” is “High
If none of the above is true, then a CR is classified as “Medium Risk” if two or more of the following are true:
• “Business Priority” is identified as “Medium”
• “Business Criticality to Deliver” is identified as “Medium”
• “Confidence Level in ability to deliver” is identified as “Medium”
• Business determines “Risk to Critical Business Operations” is “Medium”
If none of the above is true, then a CR is classified as “Low Risk”
Description Classification
Business Priority (High, Medium, or Low)
Business Criticality to Deliver (High, Medium, or Low)
Confidence Level in ability to Deliver (High, Medium, or Low)

Risk to Critical Business Operations (High, Medium, or Low)
Overall Risk Assessment (High, Medium, or Low)
High Risk Narrative
If the Overall Risk Assessment is “High Risk”, include a brief narrative describing the specific risk .
5 Change Management Requirements

List any additional training or change management requirements – A description of any special training
requirements needed by this development
6 Testing
Indicate the business-level/ technical test conditions used to verify successful operations of the report.
6.1 Functional Unit Testing Requirement

Please indicate the business level test conditions that should be used to verify successful operations of the
object. Please also include the impacted UMP L4 activities.
Please provide following - 1) testing an error-free run; 2) testing the exception processes; 3) testing the error
etc.
Step Condition Expected Results Data Business Role Impacted UPM

# Requirements L4
1 Create/update Trade Promotion MTO-030-010
Promotion (TP) for Planner
Planning Levels:
ZT01 – Discounts /
Rebates Promotion
ZT02 – Free Goods
Promotion
ZT03 – Value Added
Consumer Promotion
1.1 Field “Mobile Field available in
Activation” “General Data”
1.2 Planning Level ZT03 field display only
when pricing related
flag not checked
1.3 Field Values Cannot be changed
(=Default)
Can be activated
Can be deactivated
2 Save TP Cross Checks Promotion MTO-030-010
Planner
2.1 Activation or Error message:

deactivation selected “Mobile activation or
for off-invoice deactivation not
promotions allowed for rebate
promotions”
2.2 Activation or Error message:
deactivation selected “Mobile activation or
for Assortment pricing deactivation not
or Bonus Buy allowed for
Assortment Pricing /
Bonus Buy
Promotions
3 Release TP Promotion MTO-030-010
Leader
3.1. Field “Mobile Field set to display-
Activation” only
3.2. ECC-tables Check corresponding

ECC control tables
populated
7 Appendix
7.1 Glossary of Terms

Term Definition
8 Review/Sign-off
Specify the name of the reviewers and approvers for this object including quality reviewers.
Milestone Name Role Version Date
Peer Review
CCR Review
(Optional)
CCBCC Review
(Optional)
CCU Review
(Optional)
Swire Review
(Optional)
PSL Sign-off
8.1 Review Feedback and Comments

Copy and paste feedback you receive here as it comes in. Update the relevant document pieces which are
impacted by the feedback. Maybe sure you circle back to the sender of the feedback to show that the
feedback was handled.

Functional Specification - Enhancements

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Functional Specification - Enhancements

Hochgeladen von

Copyright:

Verfügbare Formate

Coke One North America - CONA

New Field to Allow Activation/Deactivation of

1.1 Document Details

1.2 Revision History

1.3 Business Details

Impacted UPM L3 MTO-030-010 Promotion planning

Impacted UPM L4 MTO-030-010-010 Identify and create promotion options

1.4 Related Documents

1.5 Responsible Organizations

1.6 Object Technical Details

2.1 Enhancement Description

This feature will mainly be used for Traditional Trade.

2.2 Detailed Requirement

Possible values for field “Mobile Activation” are

General checks to be implemented:

Checks to be implemented when promotion is saved:

 Don’t allow “Mobile Activation” different then “Cannot be changed” for

o Assortment Pricing / Bonus Buy

Please note that this functionality might be implemented in an upcoming release!

Checks to be implemented when promotion status is released:

2.3 Flow Diagram

2.4 Switch Framework

2.5 Security, Integrity and Controls

3.1 Configuration Requirements

3.2 Custom Table/Structure Definitions

Field Name Primary Key (Yes) Description Check Table

3.3 Messages/ Error handling

3.4 Performance Consideration

4 Business Impact Analysis

If none of the above is true, then a CR is classified as “Low Risk”

Confidence Level in ability to Deliver (High, Medium, or Low)

High Risk Narrative

5 Change Management Requirements

6.1 Functional Unit Testing Requirement

Step Condition Expected Results Data Business Role Impacted UPM

2.1 Activation or Error message:

3.2. ECC-tables Check corresponding

7.1 Glossary of Terms

8.1 Review Feedback and Comments

Das könnte Ihnen auch gefallen