on 01-21-2015 5:53 AM
I am able to assign 99 condition tables in an access sequence. but as per the client requirement we need to assign 120 condition tables.How can i do this? Please reply <text removed, to lower to priority>
thanks
Srinivas
Message was edited by Moderator: Jyoti Prakash
Hi,
it sounds very extreme scenario and requirement to have more than 99 combinations in a condition ( price ). But if there is not room for improvement or you cannot convince the client to redesign his pricing then maybe you could use a second condition with some condition exclution e.t.c. to meet the requirement.
It depends of course of the exact need.
BR.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
definetely, there must be room for improvement !. Sit and review key combinations. Bear in mind that so many accesses will impact performance ...
Regards,
JM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Srinivas,
In the same lines as JP, 120 tables in an access sequence...this is a huge number of tables! This is for what condition type (price, discount etc.) What are these tables? and will condition records be maintained for all these tables?
Give a business scenario which will make use of this condition type. Thanks!
TW
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Srinivas,
Thanks for this interesting post! and Jurgen's input is also appreciated!
120 condition tables! It is difficult to imagine that so many tables will be needed. You must be having these tables (information) in a document e.g. excel sheet. Could you please past it here? It will certainly be a learning to go through it.
TW
There is usually no way around such technical limitations. There are many other examples like the limit of 999 items per accounting document, the 5 digit integer alternative unit conversion, the 500 condition tables, the maximum number of digits for the value in a purchase order.
Did you already ask SAP Support?
But as per my client pricing requirement, i need to accommodate 120 tables in an access sequence.
It is a known fact that all clients will demand whatever they want which is not possible to address in SAP. As a Functional Consultant, you should be able to convince the client the wrong process they expect from SAP. I have seen many clients who demands many tcodes / reports initially and after some period of time, if we take a log of transactions used, it would be hardly 20% to 30%.
G. Lakshmipathi
I had come across similar scenario, but was able to cut down the steps in the access sequences.
You can check with SAP for any of their input.
Alternatively, proposal 1) still if you think, these many needed, then split the access sequences into half and assign to two different condition types (sure your customer won't like).
Proposal 2) If your client is not in US, you can think about using the field Access type with value A, for certain fields in the table-keys details of the access sequence. By this way, you have limited key combination that can satisfy different combinations.
Note that you may need to check with SAP on using this functionality as in US, SAP asked its customers to move away on using this functionality due to legal issue.
Regards,
Can you share the combination of fields used in those condition table?
Who suggested 120 key combination for access sequence, you or client?
Thanks,
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.