Fields hidden by SAP in Standard BW Data Sources
Many a times you would have observed that there are a few fields present in the extract structure of the SAP BW datasource but are not available in RSA6 or the data source which is replicated in BW.
This blog talks about all steps as to how can we enable fields present in the extract structure of the data source, make them visible in RSA3 and fetch the data in BW.
Let’s take an Example.
Here we take an example of a data source 0COMP_CODE_TEXT No. of Fields in the Extract structure is 7.
No. of fields in RSA3 output of the Datasource is ‘2’:
Fields present in RSA6 in the source system for the data source 0COMP_CODE_TEXT
Data source in SAP BW.
The Reason for this:
The value for the field SELECTION of the table ROOSFIELD for the fields which are not visible in the Data source or RSA3 is maintained as ‘A’.
If a request for a Data Source is scheduled in the Business Information Warehouse, selection conditions are specified across certain fields. The property that determines whether a selection in BW using a field is possible or required is established in the Data Source in the Source System.
In addition, the visibility of the field in BW can be set.
Definition of the individual values:
‘A’: Field is hidden in OLTP and BW; property cannot be changed by the customer.
‘M’: The Data Source requires a selection across this field before it is able to extract data (Required field for the generation of a request); property cannot be changed by the customer
‘X’: The Data Source can select across this field. The customer can change selections and visibility (the field is currently visible and selectable, compare with ‘P’, ‘3’)
‘1’: Pure selection field for the Data Source. The customer can change the selection, but not the visibility (the field is currently selectable, compare with ‘2’).
‘2’: Pure selection field for the Data Source. The customer can change the selection, but not the visibility (field is currently no selectable, compare with ‘1’).
‘3‘: The Data Source can select across this field. The customer can change selection and visibility (the field is currently not visible not selectable, compare with ‘P’, ‘X’)
‘4’: The Data Source cannot select across this field. The customer can change visibility (the field is currently not visible, compare with ‘ ‘)
Summary:
| Filed Attribute | Description |
| A | Field in OLTP and BW Hidden by SAP |
| M | Selection Required, Visible |
| No Selection Possible, Visibility Set | |
| P | Selection Adjustable, Visibility Set. |
| X | Selection Adjustable, Visibility Set |
| 1 | Pure Selection Field, Selection Set |
| 2 | Pure Selection Field, Selection Set |
| 3 | Selection Adjustable, Visibility Adjustable |
| 4 | No Selection Possible, Visibility Adjustable |
Here are Steps to make the field visible in RSA3 and to populate data into BI.
Let’s consider the filed DATETO (Valid-to date) to be displayed in RSA3 and in the Data source so that the data can be extracted into BI.
STEPS to be followed:
1. Create a test program through the transaction SE38. Write the below code in the program. Activate it and then execute.
2. After execution you would see that the value of the filed selection has been changed from ‘A’ to ‘P’.
3. Go to RSA6 and find the data source 0COMP_CODE_TEXT and select Change.
4. Put a check in the checkbox Selection if you want it to be a part of the selection in RSA3 and in the Infopackage and Generate the data source.
5. Go to RSA3 and you will find the new filed DATETO in your output.
PS. Note: If there is data it would automatically get populated in this case there isn’t any data in the new filed
6. Go to the BI System find the data source and Replicate it.
7. After replication the new field will appear in the data source.
To Summarize following the above steps you can un-hide / enable the fields present in the Extract Structure of an SAP BW Datasource.
