Dump RAISE_EXCEPTION NO_CLASSIFICATION

[Former Member]

Hello

Sometime ago a consultant created a workflow of documents. Now, when I tried to display a the Decision Steps in the worflow definition (transaction PFTC) I get a dump:

A RAISE statement in the program "SAPLCLAF" raised the exception

condition "NO_CLASSIFICATION".

Since the exception was not intercepted by a superior

program, processing was terminated.

.

.

.

Termination occurred in the ABAP program "SAPLCLAF" - in

"CLAF_CLASSIFICATION_OF_OBJECTS".

The main program was "SAPLRHW4 ".

I haven't found any Oss note for this issue.

Does anybody know the cause of this error?

Thank you in advanced.

rubé

[Former Member]

Hello

The dump is related to the visualization and selected layout.

Thanks a lot.

Rubé

[Former Member]

hello,

i'm new on basis support, please need help this newbie.

i got the same error but it occur during proses Post Good Issue using tcode VL02N, whenever it successfully PGI or not, it always came up Abap dump on ST22 with RAISE_EXCEPTION "NO_CLASSIFICATION".

the main program was "SAPMSSY1"

was i should fill table T77TD on field classification with the value NO_CLASS with something?

and i don't understand with ruben statement "The dump is related to the visualization and selected layout"?

Best regards,

iqbal

[Former Member]

Hello

Thank you for the information. I have opened an OSS message to resolve this issue, as soon as they answer me I will post the solution.

Best regards.

Rubé

[Former Member]

Hello Florin

Thank you for your complete answer, I think the problem is related with your explanation, but when I put No Classification in transaction PP01 when I check it again the field is blank again and the dump still again.

What do you mean when you say "You should be on the save side when you select NO_CLASS as the classification's value".

Thank you in advanced

Rubé

[Former Member]

Hello again,

what I meant was actually a classification value that got's the name NO_CLASS, which actually is a fake, when you classify an object saying it had no classification.

This may be the root cause, that this "characteristic value" is missing. It is customized in one of the T77-tables, which I don't know by heart right now.

I'd suggest that you put in a classification from one of the values that you have there in the drop-down-box of the field "Classification". If the drop-down-box is empty, you'd really have a problem a missing entry. There might be a SAP-Note available caring this.

Best wishes,

Florin

[Former Member]

Table T77TD

[Former Member]

Hello Rubén,

I give it a guess, that the classification maintenance has changed afterwards and I will show you, how you can peek into the classification without using the transaction PFTC.

Beside the fact, that a Task can be given the property "General task", which is already done by using a classification, there's also another option to classify a task.

This classification is usually used to group task according to a superior organizing principle, which can, e.g.

- functional

- personal

- ...

Later on, this grouping can be used to create a substituion in the SAP Business Workplace only for a specific group.

Call transaction PP01

Plan version = 01 Current plan
Object type  = TS Standard Task
Object ID    = <your task ID, e.g. 90100015>

After hitting Enter you should see a list under the "Active" tab, with "Classification/Lock Ind.". This is what you're looking for. If the list is empty, leave the transaction via the green back arrow and try again.

- Mark the line that says "Classification/Lock Ind.".

- When you see a green-tik icon on the right hand side of the Infotype you click on the Change-Button on the very top, otherwise you'll click on the Create-Button next to it

Now the screen opens, that usually appear when you choose "Additional data>Classification>Create/Change" within the transaction PFTC.

You'd be very interested in checking the entry on "Classification" in the middle of the screen. It possibly uses an entry, which isn't valid anymore. You should be on the save side when you select NO_CLASS as the classification's value.

This probably may fix your dump problem within PFTC.

Good luck,

Florin