on 01-12-2011 8:26 AM
I admit that I cannot see under which forum I should ask this question. I have posted it under this forum as the question I have is customer related and therefore could be something that someone else has encountered under SD.
So I'm apologizing in advance if this is not the place. Advice on which would be the best place would therefore be appreciated.
The problem:
We use Classifications from Cross Application Components to build classifications for Customers. It's fairly simple. The Customer Classification exists as a Class. The Class has various Characteristics created against it. Any one of the Characteristics could have a number of Characteristic Values. And against each of these Values a number of Customers is assigned.
In a simple example a Characteristic might be defined as 'Major Customers'. That characteristic might have Values such as Northern Region, Southern Region, Western Region and Eastern Region. Against each of these Values is assigned appropriate Customers.
The database records have appropriate keys. We use these keys externally in communication with Partners. We have found that when these Values are sorted or deleted, or new entries added, that the database keys change. This means that the customers previously identified using one key are now looking at a completely different set of customers on the Partner systems.
What I'd like to know is if there is any way that the database keys can be made to remain stable, despite sorting, deletion and insertion of new entries.
Hi Andrew,
I understand that you have a Z program that is reading classification data directly from the database; is that so?
If it is, then in my experience when reading classification data it is better to use (existing standard) function modules, exactly for the reason that you raise. Classification data structure is rather dynamic, which also makes classification a very flexible environment.
Regards,
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually we are using SAP functions where appropriate. The problem is that having used the database keys to identify a particular customer list, and passed those keys externally to Partners, if the keys get changed dynamically within SAP (when sorting, deleting or inserting) then the database keys no longer identify the same list of customers that our Partners believe they are identifying using the keys we have given them.
But I'm guessing from your answer that that's the way SAP works and that whilst it may add to flexibility it means we can't 'fix' the database keys of records we create. They will get changed regardless by the delete, insert and sort activities. Is that what you are saying?
For some additional information, we do have an alternative to using Classifications in mind, so it's not necessarily the end of the world.
Our own system used to use Classifications, but for many other reasons we had to develop an alternative, which in the end is actually far easier to use for our purposes. I think Classifications was used originally in our system to avoid the need to develop anything bespoke, but it was a bit of overkill in the end. Classifications is a wonderful tool nonetheless.
The alternative would mean we'd replace our Partners use of Classifications with the same bespoke functionality we now use in our own system.
My question is based on the need to identify options. If amending Classifications (in some way) so that database keys remain stable is not possible, then it will not be an option we can consider.
Thank you for your reply. Much appreciated.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
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.