on 07-30-2012 8:15 AM
Hello everybody!
I have a report in which I must show Personnel Area (0PERS_AREA) and Personnel Subarea (0PERS_SAREA). The problem is that as P. Subarea is related with P. Area, the Subarea char shows the Area code as well, I mean, for example, a P. Subarea is code AT880 and its related Area is IAME. In the report, when showing P. Subarea, it shows IAME/AT880 instead of just AT880.
Do you know how can I do to remove that 'IAME' part from P.Subarea characteristic? Is it possible to do it at query level or should I do some modifications in data flow below?
Thanks in advanced!
Alberto
Hi Alberto,
Yes If Area is the compounding attribute of Subarea, you can hide it from being shown in query.
All you have to to is to modify the query like below.
1. Drag and Drop the object Personnel Area (0PERS_AREA) in the rows.
2. Change the display property of this object as 'No Display'. And this will hide the area value.
Now the Subarea will be displayed as AT880.
Hope this solves your issue.
Regards,
Jeevitha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jeevitha,
Thanks for your reply, however this doesn't solve my concern.
0PERS_AREA and 0PERS_SAREA are both Free Characteristics, it means both can be displayed in the report as per customer needs.
If I display Area report shows IAME , and having it displayed, if I add Subarea too, Subarea is correctly displayed: AT880.
But if I add Subarea before adding Area, value displayed is IAME/AT880.
Any help?
Hey Alberto,
If the 0PERS_AREA is compounded to 0PERS_SAREA it will always be displayed as IAME/AT880 unless you hide the 0PERS_AREA object.
If you have to also display the 0PERS_AREA in the same query, try using the replacement path variable with the value of this info object.
So instead of using the 0PERS_AREA the users can have the replacement variable
Regards,
Jeevitha
Actually 0PERS_SAREA is not compounded with 0PERS_AREA. It's a bit extrange indeed. I'm running the query with BEx Analyzer, both chars are defined as Free Characteristic.
If I display 0PERS_AREA first and then 0PERS_SAREA, values are correct, but in the moment I remove 0PERS_AREA, the other characteristic becomes compunded.
For example
0PERS_AREA = IAME
0PERS_SAREA = T808
Displaying first _AREA and then _SAREA:
IAME T808 -> Correct
Displaying first _SAREA or removing _AREA from the above example:
IAME/T808
Anyway, I solved it creating a new CHAR using as template 0PERS_SAREA with the difference that in "Relation" tab I've deleted the relation with 0PERS_AREA, I've filled this Z char with 0PERS_SAREA in the transfer rule and now it's working fine (just texts are not showed, I'll figure out how to solve it).
Thanks for your help!
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.