1. Overlapping time periods
When loading data from R/3, data record errors often occur due to Overlapping Time Period. The reason for this type of error is BW has tried to load multiple records that contain the same key and overlapping validity periods (start date/end date). The records are then rejected during the update.
You can sometimes get around this error by adding additional selection entries to the Infopackage that load the data. Even though this workaround may work, it should be as a quick fix.
Another, more permanent option is to tailor your data extractor to exclude the invalid data records via ABAP. Even though this may well be sufficient to allow the data load to work, there will still be incorrect data in the source system that needs correcting.
Correcting the invalid data in the source system is the next step but you shouldn’t stop there. You need to investigate how this situation occurred in the first place. Quite often this situation appears in newly installed systems and can be classed as early teething problems with the R/3 configuration and may never occur again. If, however, users continue to create invalid records, the issue needs to be resolved permanently, e.g. through revisiting the configuration and adding thorough data validation.
2. How to identify the R/3 source for an extractor
To resolve problems and answer queries, it is often necessary to compare R/3 data with the data reported through BW. Just identifying the datasource for an extractor can sometimes be a challenge in itself.
For Master Data, Text and Hierarchies take a look at table ‘RODCHABAS‘. This table contains entries of InfoObject/Basic Characteristics together with various entries detailing the source of the object, e.g. Function Module (field ‘MSDFNAME’), View (field ’MSDVIEWNM’ for Master Data objects based on a view). The table also contains indicators such as Object is Time Dependant and Object has Attributes.
If it is a Transaction datasource you are investigating look at table ‘ROIS’. This table lists all the function modules used to generate the data. Select the function module you require and enter the name into transaction SE37.
3. Formatting date fields in BW
It is sometimes unclear how BW handles the formatting of dates. Here is a quick overview:
For BEx reporting, SAP uses the settings stored on the users local machine. On your desktop click Start > Settings > Control Panel > Regional options to view the settings local to your PC.
Some date-related reporting objects get their settings elsewhere.
0FISCPER , 0CALWEEK and 0CALMONTH take their format setting from the BW User Profile default settings (transaction SU01).
0CALDAY though takes it's setting from the PC Regional Options as shown above.
The format for year is always yyyy (4 digits).
4. Working with action type and action reason
Users have difficulty understanding how to use the Action Type and Action Reason dimensions on the employee and personnel action Infocube.
The confusion exists when a user tries to restrict the BW query on Action Reason without first choosing the Action Type. When this happened a pop-up window display all the entries of Action Reason independent of any Action Type. Very confusing.
The rule of thumb is ‘Action Reason is a sub-division of action type’. Therefore, users should always select the Action Type before selecting the Action Reason. Doing this will ensure only the relevant Action Reasons are displayed in the pop-up selection window.
5. Restricting the display of sensitive data in the F4 search Dialog functionality
When users run queries and use the F4 key to select values for selections and parameters, there is the possibility they will get to see sensitive information they are not authorised to view e.g. Payroll information (Pay Grade) which could be part of the Employee master data Infoobject.
To alter the settings that determine the attributes that are displayed to the user, go to InfoObject Maintenance screen through transaction RSA1 or RSD1 and select the characteristic that contains the sensitive data as an attribute.
Select the Attributes tab and there you will see a column called Order for F4 Help. This column determines the sequence in which the attributes are displayed in the F4 help dialog. To stop the sensitive attribute in question from being displayed in the F4 help dialog enter a value of zero in this field.
No comments:
Post a Comment