Skip to Content
0
Former Member
Nov 12, 2015 at 11:14 AM

UJ_VALIDATION use

212 Views

Hi all

This is my first time using UJ_VALIDATION and am a bit flummoxed.

The scenario is as such:

We have two kinds of cost elements - A7 (direct cost elements) and A9 (secondary cost elements). There are a few columns on the planning input form, that are separated by the category and transaction type. The transaction type (PDO_TT) is TT_02 for data flowing from ERP. We would like only A7s to arrive this way. All allocations (which write to A9s) are run in BPC.

However, we have had a few rogue users (grr!!!) who insist on writing manually to A9s and then the numbers go for a toss.

So we would like a validation to be introduced that says: if a value is being posted against an A9 under the TT_02 column, then that should not be saved.

Towards this I have created the following rule using UJ_VALIDATION (using one A9 cost element as an example) - Pic 1

I then tried to post a value in the input form in the TT_02 column for the cost element A9010020. It allows me to do so. - Pic2

So I thought maybe it allows the combination (A9010020 with TT_02) but wouldn't allow any others. So I tried to post to an A7 - A7010010. It still allows me to post - Pic3.

!!!

Then I changed the operand in the validation to <> and it doesn't allow me to post to A9 now.

So my question is this:

What does the equal to sign do?

regards

Shrikant

BPC NW10

EPM Add in Sp21

BPC 8001 sp3

Attachments

Pic3.JPG (70.4 kB)
Pic2.JPG (87.4 kB)
Pic1.JPG (62.0 kB)