SD - Surya - 2017-10-31 - 65262 - Spec - Rebate Automation for Dicks (Rizwan by 2017-11-30) #Billing #US #Quality
SPECIFICATIONS
65262 - Spec - Rebate Automation for Dicks
Purpose
Rebate automation for Dicks.
Admin Info
| Purpose |
Rebate automation for Dicks |
| Requested By |
Rizwan Shah |
| Spec Created By |
Surya Basa |
| Spec Created Date |
11/14/2012 |
| Spec QA by |
Surya Basa |
| Objects |
|
| Document Status |
WIP |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
24 |
| 2 |
Documentation |
08 |
| 3 |
Development/ Config |
04 |
| 4 |
Unit test in DEV |
04 |
| 5 |
Unit test in QUA |
04 |
| 6 |
Other activity |
|
| TOTAL |
48 |
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]NA
Documents
[Attach any document(s) received for the requirement(s)]Dick's Rebate (2).msg
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
| 1 |
Remove custom routine 903 assignment from Rebate access ZB01 as the Rebates should also be applied to Items having HOT season |
Rizwan Shah |
01/16/2018 |
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]Hi, we recently created a Lid's rebate accrual process in SAP to take the place of manual adjustments. I would like to implement the same process for Dick's sporting goods. Please find the details attached.
SAP should not calculate rebates for the orders which contain season Hot. Please create a routine and assign to condition type ZB01 to exclude season hot from calculating rebates.
Mike,
As discussed in our meeting we will be creating a discovery session for Dick’s rebate to review the rebate functionality.
Below are the take away points which I will keep in mind while building the solution. Please advise if any of the bullet point is incorrect or requires more information.
1) The rebate will be given based on the value and not quantity.
2) The rebate will be given annually.
3) The rebate will be given in USD only, since Dick’s only do business in U.S.
4) The rebate agreement will start from .5%. But once Dick’s meet the threshold of $8,999,999.99, we will close the .5% and open a new rebate agreement for 1.5% and so on till it reaches 3.5% for the amount of $10,900,000.
5) The hot market season should be excluded from the rebate process.
6) The rebate will be given on all the materials which are headwear and apparel.
In Scope:
[List the activities to be included in scope]The rebate agreement and the key combination is only applicable to Dicks.
Out of Scope:
[Out of scope activities]Other discounts are not impacted by this change.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
The solution involves setting up a new access for Rebate using key combination of sales org/customer/season and sales org/customer/Mat group
Develop a custom routine that checks for season HOT and doesn't apply the Rebate; and assign to the access sequence.
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| SD001 |
||
| SD002 |
Solution Details
[Provide complete technical details for configuration or programming here]
Config
1. Necessary configuration was done in the menu path- SPRO->SD->Billing->Rebate Processing->Rebate Agreements and Condition Technique for Rebate Processing
Rebate Agreement type - ZMRB (MG Dicks Rebate)
Condition Type Gr - ZMRB (Material/Rebate Grp)
Rebate Condition Type - ZD01 (DickMat/Group Rebate)
Condition Table - 512 (Sales org/customer/matl gr)
Access Sequence - ZB01 (Rebate for Dicks)
Requirement routine - 903
Pricing Procedure - ZNECAP
Step - 903
2. Activate COPA postings for ZD01 condition type in transaction KE4I with field name VV08.
Issues
[List Issues / Bugs identified in configuration or development]
An issue has been noticed in DEV clients 100, 300 and 500.
In the standard system Rebate condition technique access sequence doesn't have EXCLUSION indicator activated. However, SAP has provisioned the same in the versions upward of 4.6x. In NECNED500/300, the EXCLUSION indicator is activated and also the Rebate pricing kicks in as standard pricing if the option is flagged, as shown below-
Example with EXCLUSION activated (NECNED500) and Rebate Settlement executed successfully-
1. Billing Documnent - 92157304
2. Rebate Agreement - 207
NECNED100
Approach
1. Open OSS with SAP for troubleshooting
2. Explore requirement routine creation to restrict the Rebate applicability to Items having HOT season.