Attribute Field missing in BEx Query Designer

[Former Member]

Hello Experts,

I'm trying to create a report to show materials but there are some Attributes that I am unable to show in the Query.

I need to show the Label Type and Label Form in my Query.

When I check the Masterdata's Attribute, the fields are available.

But when I go to Query Designer, and expand the Attributes of 0MATERIAL, I don't see Label Type and Label Form.

May I know what I am doing wrong? Thank you.

[former_member209895 · Accepted solution]

Hi Juan,

       Please do not compare the fields in the info object's attribute datasource, instead please right click on the infoobject and then DISPLAY and look into the Attributes tab. If the fields you are lookin for are DISPLAY ATTRIBUTES then only they should appear under Attributes folder in BEx. You can look into the attributes tab and figure out if they are display attributes or not.

Hope this helps, please check in the attributes tab and get back.

Regards,

   Manohar. D

[snitwipro]

Hi,

   Please check whether 0MATERIAL includes the attributes of your choice. Please try to active the infoobject again once (check the attribute table and see if those attributes are available). Reactivate the cube and regenerate the query (from RSRT). Disconnect from Query designer and reopen the query.

  Also please see if you have made those info objects navigational, if so then turn on those navigational attributes from the cube and reopen the query in QD.

Regards

Sourav

[Former Member]

Thank you experts, I think I found the problem.

I need to create mappings in the Transfer Rules correct? They are currently blank (see below.)

[former_member209895]

Thats correct Juan, but please map it to the relavent info objects, if they are not already created and added as attributes in the Infoobject then please do so, and make sure to have them as DISPLAY attributes as suggested earlier..

Good Luck.

Regards,

  Manohar. D

[Former Member]

Yes correct.

Was under impression you have mapped it correctly as i dint get any reply

[Former Member]

Thanks Manohar,

I tried assigning the field to an InfoObject, but I found 2 with the same name. How will I know which one to use?

Also can you suggest a document that I can review? This is my first time to manage transfer structures for master data. I only have experience in loading LO Data extraction (via LBWE).

[Former Member]

You could use 0ac_doc_typ...

[former_member209895]

Hi Juan,

     The best way to assign fields to infoobject, when you are in confusion, is to check for the length and data type of the fields first and then match it with the corresponding infoobject which has the same length and data type. Try to view the fields length and data type from the datasource display, as partially displayed in your first post, 2nd screenshot.

And I'm afraid I do not find any good document on transfer structure maintenance but I can tell you this:

1. Transfer Rules are mappings between the communication structure and transfer structure / datasource.

2. Communication structure resembles the sequence of infoobjects in the target, in your case it is Material.

3. Transfer Structure/ Datasource resembles the sequence of fields in the source.

So if you have added new fields into the attributes of 0MATERIAL please check if the communication structure displays the same, if not then you might have to create the infosource again. Once done / once they appear in communication structure, the rest of the job is to map the transfer rules. If at any point of time you need to delete transfer rules then take screenshots so that the mappings are saved, which can be referred when you create new transfer structure.

I will search for any good document on infosource creation  in 3.X and the mapping of transfer rules, and if I find any I'll get back on this post.

Regards,

  Manohar. D

[Former Member]

Use the table rsosfieldmap in BW side... This will give you a suggestion on which info object to be used..

1.Goto table rsosfieldmap

2. Pass the field to which u need to map info object in the FIELDNM field

3. You will get a list of info objects that where used to map this field.

This is regarding the mapping of ECC fields with the info object...

This way would help you out in most of the case... If it doesnt works out the best option is to create a z info object as same type of the field to which it needs to be mapped.

manohar has explained few things, please have look into those too..

Revert back if you need any other clarifications.

Thanks,

Nithesh.

[Former Member]

Thank you Manohar, no need for you to search, you already helped a lot we are using BI 7 so it should be easier to do this. I'll just do some further research.

[former_member182516]

Hi,

Are the fields mapped to BW, check in the transfer rules for the respective IOs.

Have you added these 2 IOs newly to 0MATERIAL?

If mapped check if they are display or navigational attributes, If they are display attributes then they will be appeared under attributes folder if not check in Key part as well.

Cheers -- KP

[Former Member]

Hi!

I would check if those material attributes infoobjects are actived, and, in any case, I would activate them again.

As a workaround (don't know how you're building your modelling), mark them as NAVigational attributes of 0MATERIAL, add them to the infoprovider and in the last transformation, link them to 0MATERIAL as Read Master Data. In that way for sure you'll have them in BEx and as separate objects.

[Former Member]

Hi

Please check the following:

1. Are these datasource attributes defined in the update rule to 0MATERIAL?
2. If yes, check if you want to use it as navigational attribut? Then you must activate this attribute in Infocube maintenance.
3. Do you use a multi provider for your query? If yes, then you must also activate nav.attribute in multiprovider.

Thereafter you should be able to drag and drop this navigational attribut in BEx query.

Regards

PC

[Former Member]

Hi,

The screen shot refers to the data source fields which are nothing but field names in the ECC side, these names will not be available in the material master unless it is mapped to the corresponding info objetcs... Even if it is mapped you need to search with the info object.

Please do check the mappings for these fields in the transformation and then check for those info objects to which it is mapped...

Hope this helps...

Thanks,

Nithesh.

[Former Member]

Regards,

Venkatesh

Why you want to check with your data source , goto RSA1 --> 0Material --> Display and see whether

Label type and label form are available or not.

If not just add the two info-objects , connect the DS field with these 2 info-objects through transformation.

Regards,

Venkatesh

[RamanKorrapati]

Hi Juan,

Please check again are you checking 0MATERIAL or any custom object of material.

if your checking right one, just close your bex designer and relaunch and check it again.

Thanks

[ravi_chandra3]

Hi Juan,

Display attributes are dependent on master data IO, Let say u have CID as the master data and CNAME,CADDRESS as the display attributes , if you place that CID in the rows and the cname, caddress in the rows then in the result output the display attribute will be visible,

and without placing the CID in the rows if you try to place the CNAME and CADD in the rows then it will be dragged into the rows because that display attributes are dependent on the master data IO( CID ) .

If you want to keep the display attributes in the rows independent of the master data (CID ) then make the CNAME, CADD as NAVIAGATIONAL ATTRIBUTE.

Hope u got it,