filtering on display attribute....

[Former Member]

hi guys...

can we put filter on display attribute...

coz i need to show data based on one characteristic value and on another attribute of different characteristic. is it possible... the ods which is containing these objects already in production...

so if we make any changed in dev, what will be the consequences in prod sys....

pl suggest me proper ways...

thanking you....

nithin

[Former Member]

Hi,

You can not put the filter on Display attribute. If you want to have filter on any attribute, you have to define it as navigational attribute,and then make tick mark for 'ON/OFF' for this navigational attribute in EDIT screen of ODS.

With rgds,

Anil Kumar Sharma .P

[Former Member]

hi....

if i make this alteration in dev system, how can i replicate it on to production system...

meaning that the ods is already in production with display attrib...

now if make it nav attrib, how can i reflect this change to production.. if i do transporting again what will be the problems...

pl detail me...

thanking you...

regards,

nithin

[Former Member]

Hi,

You have to make the changes in the production system by transporting the request from QA system.

It will not give any undesired effects .Because including the Nav attr does not alter the 3 tables(New,Active,Change log) of ODS.

So

1) Chanhge the display atribute to navigational attribute

2) Selct tick mark for the above filed under 'ON/OFF', and then activate the ODS.

3) Create the transport request,and then import it.

With rgds,

Anil Kumar Sharma .P

[Former Member]

hi how are you...

here im facing a big problem ... you have given me some solution but... i tell yu the problem clearly...

we have to generate a report for CRM interactive record details on ODS...but this ODS doesnt contain one main object(0CRM_PRCTYP) which is used to tract the record type(interaction record).

but in the same ODS this IO is available as a display attribute of another characteristic...

i need this object as an individual object so that i can track the record type by using this 0CRM_PRCTYP along with another object 0CRM_PREOTP.

to track the record type i must have these two objects..

0CRM_PREOTP is there...but 0CRM_PRCTYP is not there...

can i add this 0CRM_PRCTYP in ODS now...(which is already in production)... so if i add this object what will be the effects and how can i reflect only this change in production..

or any alternative solution is there for me...

pl kindly thro some focus on this issu...

thanking you all...

nithin

problem here in our ODS is we have (0CRM_PREOTP)IObjt as an individual characteristic and (0CRM_PRCTYP) as an attribute of another characteristic(not attrib of 0CRM_PREOTP).

so now i need to restrict the char 0CRM_PREOTP to '126' and attrib 0CRM_PRCTYP = 10.

thanking you...

regards,

nithin

[Former Member]

Hi Nith,

Anil was right in what he suggested..

1. Go to the other characteristic definition and mark 0CRM_PRCTYP as a navigational attribute.

2. Activate the Info Object.

3. Go to the ODS definition, Under the Navigational attribute tab you will find 0CRM_PRCTYP ..Check the Check box against it .

4. Activate the ODS.

5. Transport all these changes to production.

<b>NOTE :</b>You donot have to delete data for any of the above changes in any system.

Now log into Bex.

You should be able to find the Object 0CRM_PRCTYP in the Query definition and then you can restrict it to the desired value..

Hope I made it clear..

Ashish..

[Former Member]

Hi,

I under stood that you do not have any problem with 0CRM_PREOTP .

The availability of IO 0CRM_PRCTYP in ODS can be possible in two ways.

1) Including 0CRM_PRCTYP as one of the object in Data fields of ODS

2) Taking 0CRM_PRCTYP as navigational attribute in ODS( this procedure is explained in the lost posting)

In the first procedure, after including the 0CRM_PRCTYP as one of the object in Data fields of ODS, the value for this field for all existing records becoms Blank. IF you want to have ( For proper reporting you must have it) the value for this field for all records, you have to restart the delta loading.

In the Second procedure, after including the 0CRM_PRCTYP as one of the object in Data fields of ODS, there will be a value for this field for all existing records. But the problem is ther is a chance of changing of value for this field in the master data (the object which has the 0CRM_PRCTYP as the navigational attribute) .So that in the report there is chance to disappear of transaction records.

With rgds,

Anil Kumar Sharma .P

[Former Member]

hi thank you very much...

i found another thing in our production system...

even tho the 0CRM_PRCTYP was an attribute of another characteristic(related to lead), our previous bw expert

didnt maintain any transfr rule to load the data(he dint include this field in infosurce too)so wat happened is so far there is not data in this particular object on bw side even tho the data source is supplying the data to this field(we found in rsa3)...

so wat im thinking is instead of going to change it to nav attrib, its better to add this object as a data field in ods...

if so how can i get the data for this particular field related to previous existing records...

can i delta initilize only for this field, if so how??

pl suggest me...

thankig you both...

regards,

nithin

[Former Member]

Hi Nith,

I don`t think you will be able to load data just for one field into an ODS..You might have to do a reload..

So You will have to Drop data from ODS, Add this Info Object and reload data ..

If you donot want to reload data..

the second option is to maintain the transfer rules and populate this object in the Master data and use it as a navigational attribute as i suggested earlier..

To me populating it in master data seems simpler..

Ashish..

Message was edited by: Ashish Gour

[Former Member]

Hi,

First of all let us know one thing:

You are populating the data from one of the OLTP table(transaction data) to this ODS.So has this table any filed which represents the value for 0CRM_PRCTYP.

If so, I hope , you can update this information to ODS with out distrbing the existing delta, by taking as intermediate ODS. You will built an intermediate ODS(say ODS2) with key fields as same as ODS first ODS. And the in data field you will take only 0CRM_PRCTYP. You will populate the data from OLTP table to this ODS using a generic extraction .And then populate the data from the ODS2 to ODS1.Here the existing records will be updated.in the update rule (ODS2--->ODS1), make sure that 'no update' is selected for all data fields and keyfigure except 0CRM_PRCTYP . Here you will take 'overwrite' for 0CRM_PRCTYP .And this is one time procedure which will update the existing records of ODS1. Then after you will go with as usual existing delta process(OLTP table to ODS1) .

This is just my idea, So wait for our experts' view also.

With rgds,

Anil Kuamr Sharma .P

[Former Member]

hi asish ur solution is looking good...

first option(reloading may be a problem here)...

so second option is looking better...

but i dint understand that you said maintaing the transfer rule and populate in master data..

how it is possible...

i have the transactional data source 0CRM_SALES_ACT_1, wihich is supplying this 0CRM_PRCTYP.

so if i want to load it into as master data, as you said can you tell me the procedure...

hey one more doubt here im facing...

as of now 0CRM_PRCTYP is an display attrib of 0CRM_LEAD.

so will this 0CRM_PRCTYP attib contain the data only related to 0CRM_LEAD, OR it contains all data as supplied by data souce...???

THANK YOU VERY MUCH...

regards

nithin

[Former Member]

Hi Nith,

By maintaining the transfer rues I meant that you need to map 0CRM_PRCTYP to the R/3 field..

I would suggest first check the data source for 0CRM_LEAD which would be a master data source..not the Transactional Data source..

See if you find the field for 0CRM_PRCTYP on the R/3 side in the 0CRM_LEAD master datasource..and then map it..

The Master data source should give you all values for 0CRM_LEAD corresponding to all 0CRM_LEAD values.

Let me know..

Ashish..

[Former Member]

no man... i dint find 0CRM_PRCTYP under master data source 0CRM_LEAD... BUT i found this under tansactional data source 0CRM_SALES_ACT_1.

i will think about your valuable suggesions to apply one procedure and let you know b4 applying....

thanking you all..

regards,

nithin..

[Former Member]

GOOD Man..I will sleep now..hope you find a solution by tomorrow morning..

Good Luck..

Ashish..

[Former Member]

hi friends how are you....

i've studied our system clearly...and decided to enhacne the ODS by adding this field(0crm_prctyp) in data fields.

and i need to enhance the transfer structure by adding this field and maping the related data source field, to populate the data for this field.

as you said these changes can be replicated in production by transporting the change request.

can yu tell me is change request is something different from ordinary request...(i never created this)..

and how can i initialize the delta for this field...

can i initilize(delta) only for this field or shud i do it for all fields again.. if so shud i delete the data from ODS in production first???

frankly speaking we dont have the requirement of the data for this particular field(0CRM_PRCTYP) for already existing records...

if it can maintain the data for the field(0CRM_PRCTYP) along with the forthcoming records into this ODS... thats enough for us...

now suggest me still i need to initialize the delta for all fields or not....??

thanking you...

regards

nithin

[Former Member]

As far as I know just adding a new data field to the ODS , you will not have to delete data in the production ..since you mentioned you donot need this field for pre-existing data..

You can start populating this field going forward..without deleting previous data..

Since you have already transported the ODS to Production,

Now when you make changes to the Existing ODS in development..It will ask you to assign these changes to a request..You justr need to transport this request to Production..

Ashish..