on 02-02-2011 7:08 AM
Hi Experts
I have a Business Scenario in Allocation Check with my client.
Product A and Product B has 3 customers(CUST1, CUST2 & CUST3)
Scenario 1: I want the allocation check only for CUST1 and CUST 3.I dont want to check allocation for CUST2.
When Product A is ordered by CUST1, system should check allocation for CUST1, When Product A is ordered by the CUST3 , system should check Allocation. When Product A is ordered by the CUST2 system should not check allocation.
Scenario 2 In the case of Product B is Ordered by CUST1,CUST2 & CUST3, system should check allocation Quantity of CUST1 & CUST2 and it should not check the allocation qty of CUST3.
Is to possible to maintain this scenario in GATP.
Please give your advice.
Thanks
Kanth
Kanth,
Allocation sets a maximum limit. If there is no specific product/customer CVC for a given customer, then the customer will be checked against product/wild card CVC. You can set 'wild card' allocation at a very high value, which in effect means 'no allocation limitation' for customers who do not have a specific product/customer CVC.
Assume that the max total allocated qty for product A is 100, max total allocated qty for product B is 200. If your business has no logical maximum (very uncommon in a normal allocation business situation), then just enter a very large figure for the product/wild card CVC. In the examples below I am just making up the allocated quantities.
For scenario 1, your CVCs
Product A/Cust1----
10
Product A/Cust2 Do not create CVC
Product A/Cust 3----
10
Product A/wild card----
80
For scenario 2, your CVCs
Product B/Cust1----
30
Product B/Cust2----
50
Product B/Cust 3 do not create CVC
Product B/Wild card----
120
I don't know what your wild card character is, it is set when you create your collective characteristics (txn /SAPAPO/ATPQ_COLLECT)
Best Regards,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.