on 08-27-2012 10:31 PM
Greetings,
We have created two Categorization Schema with completely different content, one for Incidents (with only Incidents defined in the Application Area) and another for all other transactions including Problems. The basic functionality worked perfectly except when we create a Problem as a Follow-up Document from an Incident (or Incident from Problem). Then the entered categorization values are attempted to be copied and a warning message displays indicating that 'Schema ZXXXXX_SCHEMA, category XXXXX is not a valid assignment'. This is understandable since the values for the two schema are totally different. The warning message disappears when you save the new message and doesn't stop entry of any new categorization values. Is there any way to configure 7.1 to not copy Categorization data, specifically between two transaction types to stop the warning message? I couldn't find anything in Mapping Rules for Copy Controls configuration that worked.
Thanks in advance!
Paul Maraijko
Hi,
Did anyone find a solution for this?
We are facing exactly the same issue.
We have Schema 1 for Incidents & Problems and Schema 2 for Change. When a request for change is created as a follow-up from an incident then this warning message is displayed - " Schema XXX, category XXX is not a valid assignment".
The incident transaction type is not added in the application area of Schema 2 and change type is not added in the application area of Schema 1. Also, in the copying control for follow-up documents 'category' hasn't been checked.
Please suggest if it can solved using the standard available settings rather than development.
Regards
Shubhra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good day:
After 2 years, does anyone found a solution for this issue?
Has SAP agreed with the fact that it is quite logic that 2 different transaction types use not only 2 different categorization schemas, but that the number of branches may not be a perfect match between the 2 of them, which is what causes the warning message to appear?
Thanks,
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juan-Carlos,
I included a development fix earlier in this thread which suppresses the warning message from being issued. Please check my response at September 19, 2013 8:28 PM to Anita Barrer. I am not aware of any configuration fix or anything you can do with the Category Schema themselves.
I created an SAP Service Message about this issue back in 2013 but could never get SAP to really understand what the issue was or provide any kind of solution.
Kindest regards
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi paul,
In two schema,
1. one for Incidents (with only Incidents defined in the Application Area)
2.all other transactions including Problems.
In 7.1 to not copy Categorization data, specifically between two transaction types, using application setup,
In first schema remove the all the application id except incident .
In second shema remove the incident appilication id.
Normally, in the Categorization Schema, copy Categorization data only if the application id is mapped in the application area. so once created new schema or new vesion and remove the required application id under the application area and release and active the schema id.
I hope it will slove the "not a valid assignment" issue and warning message.
Rg,
Karthik
Hi Karthik,
I think I already have the Application IDs setup correctly on each schema.
This is what I have for the non-Incident schema:
All transaction types other than Incidents but including Problems are defined in this schema.
This is what I have for the Incident only schema:
The only transaction type defined in this schema is Incidents.
Data content of the two categorization schema are completely different.
Activating and using these two schema still produced a warning message that the copied categorization value was invalid when creating any transaction as a follow-up from an Incident. The same warning occurs when creating an Incident from a Problem.
Please let me know if I missed something or if you verify that the above setup should not produce such a warning message.
Thanks and Kindest Regards!
Paul
Hi,
Are there any solution for this??
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anita,
We came up with a development fix for this.
1. Use transaction SE11 to access View 'CRMV_MESSAGES_V'.
2. Display the contents. Enter Application Area 'CRM_SERVICE_OS'.
3. Enter Message Number 126 and select Degree of Detail = 'Only collect in trace mode' and select Message Type = 'Warning'.
4. Save.
The warning message should disappear when you create a follow-up document where the two transactions types use different schema.
Let me know if you have any questions.
Kindest Regards
Paul
hi,
have you checked any access sequence for preceding document on ZMPR partner determiation procedure?
Thanks,
Jansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
this is my view,
since you are using ZMPR as follow up from ZMIN, if you define any access sequence for preceding document ( Can be accessed via partner determination procedure)
your catagorisation data also might copied. Just the other way of thinking,
But not sure abt ur case.
Thanks,
Jansi
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.