SD - Surya - 2017-07-24 - 49708 - Spec - Additional discount for AC products (Rizwan by 2017-07-28) #US #OrderEntry #EDISD
SPECIFICATIONS
49708 - Spec - Additional discount for AC products
Purpose
Additional discounts for AC products.
Admin Info
Purpose
|
Additional discount for AC products
|
Requested By
|
Rizwan Shah
|
Spec Created By
|
Surya Basa
|
Spec Created Date
|
07/24/2017
|
Spec QA by
|
Surya Basa
|
Objects
|
VVC_T682_VA
VV_T687_V1
VV_T683S_EL_VA
C005
VV_T685A_VA
VVC_T683_VA
VV2_T258I_V
A809
|
Document Status
|
Complete
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
01
|
2
|
Documentation
|
08
|
3
|
Development/ Config
|
10
|
4
|
Unit test in DEV
|
08
|
5
|
Unit test in QUA
|
08
|
6
|
Other activity
|
|
|
TOTAL
|
35
|
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)]
Condition type testing.xlsx
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
24/07
The AC initiative is to offer customers an additional 2.00 off per cap for a specific period of time to boost sales.
The initial suggestion was to track the sales and then issue credit memos after the fact.
As I would prefer to use a systematic solution rather than issuing credits after the fact, current pricing conditions were investigated and we found that with a little tweaking we might be able to use condition type ZNSD
This condition type adds the additional discount AFTER commission and royalty computes which is what we need to insure that we pay royalty on the higher price
We are meeting later this morning to discuss further but am opening this ticket as the following will need to occur
Change from manual condition type of automatic condition type
Change calculation from the header level to the item level
Change the condition type from calculating a % and using a fixed amount (2.00)
Create 2 new key combinations
Sales Org Collection
Sales Org Collection Customer
Determine what MLB Category would like to call the condition type and rename
Determine what GL Finance would like the additional discount to hit and then create a new GL account number for this as it needs to be separated for royalty purposes.
Need clarification on Tax
Spoke with Marianne and tax should compute AFTER all discounts are applied -
Need clarification on whether this condition type should or should not include contract orders – not sure if this is possible to exclude from certain order types
Need clarification from business on what customers will be excluded from this offering
Need testing on manual, ROC and EDI orders. Testing should include a taxable and non taxable customer, a commissionable and non-commissionable customer. Testing should include credit memo return. Testing must provide a royalty report sample
New Changes
Rizwan Shah –According to the email attach we will need 3 key combinations with the exclusive access sequence.
1) Sales org/Collection/Order type
2) Sales org/Collection/Customer
3) Sales org/Collection
Any other order type in SAP which uses the same pricing procedure as ZOR for 1000 sales org should be added in the 1st key combination with the 0 value to exclude that order type from the additional discount.
Please rename the condition type ZNSD to "Addl Disc post Roy/Com calc".
The new G/L for condition type ZNSD is 421015. Please let me know in case of any further question.
In Scope:
[List the
activities to be included in scope]
Out of Scope:
[Out of scope activities]
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
1. Update ZNSD condition to meet the requirements
2. Create a new condition table for sales org/collection/sales doc type
3. Update access sequence Z028 with the three key combinations and assign to condition type ZNSD
4. Assign GL account to the corresponding key to post to accounts for the ZNSD condition
5. Maintain condition for COPA postings
6. Create a new account key for ZNSD condition and assign the new GL with Tab5 for account determination
7. Pricing procedures, ZNECAP, ZNECON, ZNECDR should be updated with the the new account key and ZNSD should be set up on them.
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected Results
|
SD001
|
|
|
Condition type testing.xlsx
Solution Details
[Provide complete technical details for configuration or programming here]
All config changes were restored to original state as the business decided not to proceed with the changes.
The reason being, business didn't foresee issue with the EDI orders where the customers already aware of this promotional offer would discount the price on their EDI orders. This would cause an issue where the EDI customers are likely to get a double discount with this change.
A BI report, "SC100 - Sales Incentives for collection" was developed to provide the required information to customer service.
Issues
[List Issues / Bugs identified in configuration or development]
NA