Update routine bringing wrong data in Report

Hello Experts,
I have a strange situation on Inventory data. We have update rules from data source 2LIS_03_BF to our inventory cube.There is a characteristic in the cube which was not doing any thing in the past(I mean not mapped),which I am filling it currenlty using a update routine. The cube data looks absolutley fine for that field, I mean its bringing what it supposed to bring from my routine.The cube data looks fine for that field, but when I run the report on this cube,the field data is getting some numbers from some where,which is totally wrong.
I checked whether there is BADI written on this field (Virtual Characteristic), but seems there is none for this characteristic except for some key figures based on some other characteristics.
I am confused here as why the report is bringing some wrong numbers when it supposed to get the correct values from cube.
Please advise,
Regards,
JB

Hi,
i hope you have checked it for non cumulative objects as there will be a different way of aggregation in that case.
also, if the inventory is modelled based on cumulative key figures and if you are sure there is no code written for virtual key figures then it could be exception aggregation in the reporting settings or in the key figure general settings.
Also during checks you are considering the historical data as well from the cube and its effect on the report output.
just do a check and let us know.
regards
Ajeet

Similar Messages

Wrong data in Reports

HI,
I have a characteristic( ex. ID number) in my report for which i am getting wrong data.
when i go and check in the respective info providers i can see the data properly for that characteristic. But when i run the report i m getting data as
08/ZR923854A (correct - ZR923854A)
08/YS890040D (correct - YS890040D)
#/YY879565C (correct - YY879565C)
I have checked in Query designer for Characterstic Values, there also the same wrong data is coming.
Please help if you have any clue for this.

Hi,
Adding it to free cha. will not make much difference to the output. If you want ZR923854A only you have to create new infoobject which is not componded and then write routine in the transactional data flow to fetch ID number from this compounded object.
If it is a standard infoobject I would not recommend anyone to use single infoobject as SAP has desinged many objects considering the business functionalityies. We should not change it. You can convince business same way. If you need more info on Compounding please refer below link,
http://help.sap.com/saphelp_nw04/helpdata/EN/ff/f470375fbf307ee10000009b38f8cf/frameset.htm
Hope this helps.
Kind Regards,
Viren

Issue in Update routine due to Data Package

We have this peculiar situation.
The scenario is ..
We have to load data from ODS1 to ODS2.
The data package size is 9980 while transferring data from ODS1 to ODS2.
In the update rule we have some calculations and we rank the records based on these calculations.
The ODS key for both ODS1 and ODS2 is same ie Delivery Number , Delivery Item & Source System.
For example a Delivery Number has 12 Delivery Items.
These Delivery Items are in different Data Packages namely Data Package 1 and Data Package 4.
So instead of having the ranks as 1 to 10 its calculating it as 1 to 5 and second item as 1 to 5.
But what we require is Rank as 1 to 10.
This is due to the fact that the items are in different Data packages.
In this case the ABAP routine is working fine but the Data Package is the problem.
Can anybody any alternative solution to this issue.?
Thanks in advance for assistance.............

CODE FOR INTER DATA PACKAGE TREATMENT
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
DATA: v_packet_nbr TYPE i VALUE 1.
DATA:
g_requnr TYPE rsrequnr.
DATA:
l_is        TYPE string VALUE 'G_S_IS-RECNO',
l_requnr    TYPE string VALUE 'G_S_MINFO-REQUNR'.
FIELD-SYMBOLS: <g_f1> TYPE ANY,
               <g_requnr> TYPE ANY.
TYPES:
BEGIN OF global_data_package.
        INCLUDE STRUCTURE /bic/cs8ydbim001.
TYPES: recno   LIKE sy-tabix,
END OF global_data_package.
DATA lt_data_package_collect TYPE STANDARD TABLE OF global_data_package.
DATA ls_datapack TYPE global_data_package.
datapackage enhancement Declaration
TYPES: BEGIN OF datapak.
        INCLUDE STRUCTURE /bic/cs8ydbim001.
TYPES: END OF datapak.
DATA: datapak1 TYPE STANDARD TABLE OF datapak,
      wa_datapak1 LIKE LINE OF datapak1.
Declaration for Business Rules implementation
TYPES : BEGIN OF ty_ydbsdppx.
        INCLUDE STRUCTURE /bic/aydbsdppx00.
TYPES: END OF ty_ydbsdppx.
DATA : it_ydbsdppx TYPE STANDARD TABLE OF ty_ydbsdppx WITH HEADER LINE,
       wa_ydbsdppx TYPE ty_ydbsdppx,
       temp TYPE /bic/aydbim00100-price,
       lv_tabix TYPE sy-tabix.
$$ end of global - insert your declaration only before this line   -
The follow definition is new in the BW3.x
TYPES:
BEGIN OF DATA_PACKAGE_STRUCTURE.
     INCLUDE STRUCTURE /BIC/CS8YDBIM001.
TYPES:
     RECNO   LIKE sy-tabix,
END OF DATA_PACKAGE_STRUCTURE.
DATA:
DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
       WITH HEADER LINE
       WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
           MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
           DATA_PACKAGE STRUCTURE DATA_PACKAGE
USING    RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line        -
fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
to make monitor entries
TABLES: rsmonfact.
TYPES:
    BEGIN OF ls_rsmonfact,
      dp_nr TYPE rsmonfact-dp_nr,
    END OF ls_rsmonfact.
DATA: k TYPE i,
        v_lines_1 TYPE i,
        v_lines_2 TYPE i,
        v_packet_max TYPE i.
declaration of internal tables
DATA: it_rsmonfact TYPE STANDARD TABLE OF ls_rsmonfact.
INTER-PACKAGE COLLECTION TREATMENT *******************
ASSIGN (l_requnr) TO <g_requnr>.
SELECT dp_nr FROM rsmonfact
    INTO TABLE it_rsmonfact
    WHERE rnr = <g_requnr>.
DESCRIBE TABLE it_rsmonfact LINES v_packet_max.
IF v_packet_nbr < v_packet_max.
APPEND LINES OF DATA_PACKAGE[] TO lt_data_package_collect[].
    CLEAR: DATA_PACKAGE.
    REFRESH DATA_PACKAGE.
    v_packet_nbr = v_packet_nbr + 1.
    CLEAR: MONITOR[], MONITOR.
    MONITOR-msgid = '00'.
    MONITOR-msgty = 'I'.
    MONITOR-msgno = '398'.
    MONITOR-msgv1 = 'All data_packages have been gathered in one. '.
    MONITOR-msgv2 = 'The last DATA_PACKAGE contains all records.'.
    APPEND MONITOR.
ELSE.
last data_package => perform Business Rules.
    IF v_packet_max > 1.
      APPEND LINES OF DATA_PACKAGE[] TO lt_data_package_collect[].
      CLEAR: DATA_PACKAGE[], DATA_PACKAGE.
      k = 1.
We put back all package collected into data_package, handling recno.
      LOOP AT lt_data_package_collect INTO ls_datapack.
        ls_datapack-recno = k.
        APPEND ls_datapack TO DATA_PACKAGE.
        k = k + 1.
      ENDLOOP.
      CLEAR : lt_data_package_collect.
      REFRESH : lt_data_package_collect.
    ENDIF.
sorting global data package and only keep the first occurence of the
*record
SORT DATA_PACKAGE BY material plant calmonth.
DELETE ADJACENT DUPLICATES FROM DATA_PACKAGE
        COMPARING material plant calyear.
SELECT * FROM /bic/aydbsdppx00
      INTO TABLE it_ydbsdppx
      FOR ALL ENTRIES IN DATA_PACKAGE
        WHERE material = DATA_PACKAGE-material
          AND plant    = DATA_PACKAGE-plant
          AND calyear = DATA_PACKAGE-calyear.
Enhance Data_package with Target additionnal fields.
LOOP AT DATA_PACKAGE.
    CLEAR : wa_datapak1, wa_ydbsdppx.
    MOVE-CORRESPONDING DATA_PACKAGE TO wa_datapak1.
    READ TABLE it_ydbsdppx INTO wa_ydbsdppx
      WITH KEY material = DATA_PACKAGE-material
                  plant = DATA_PACKAGE-plant
                calyear = DATA_PACKAGE-calyear.
    IF sy-subrc NE 0.       "new product price
      APPEND wa_datapak1 TO datapak1.
    ELSE.                   " a product price already exists
      IF wa_ydbsdppx-calmonth GE DATA_PACKAGE-calmonth.
keep the eldest one (for each year), or overwrite price if same month
        APPEND wa_datapak1 TO datapak1.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.
Edited by: mansi dandavate on Jun 17, 2010 12:32 PM

Update routine infinite loop

Hello Experts,
For loading ODS2 we are making a lookup on ODS1 for 0material based on
purchaing document number, item line item.
Is there any mistake in the start routine or update routine.
Because the load goes in infinite loop. I think update routine should be changed.
Any suggestions are appreciated
Start routine:
data: begin of itab occurs 0,
        pur_doc like /BIC/AZODS100-OI_EBELN,
        item like /BIC/AZODS100-OI_EBELP,
        material like /BIC/AZODS100-material,
      end of itab.
clear itab.
select OI_EBELN OI_EBELP MAT_PLANT from /BIC/AZODS100
         into table itab.
Update routine for 0material
loop at itab where pur_doc = COMM_STRUCTURE-OI_EBELN
                   and item = COMM_STRUCTURE-OI_EBELP.
       RESULT = itab-matplant.
endloop.

Hi,
this takes a long time, because with each record of your data packaged it is doing the loop and scanning each row of the internal table. Use the following instead.
Start routine:
types: begin of t_itab,
pur_doc like /BIC/AZODS100-OI_EBELN,
item like /BIC/AZODS100-OI_EBELP,
material like /BIC/AZODS100-material,
end of t_itab.
data: itab type hashed table of t_itab with unique key pur_doc item.
select OI_EBELN OI_EBELP MAT_PLANT from /BIC/AZODS100
into table itab order by oi_ebeln oi_ebelp mat_plant.
I hope these fields are the key of the ods object.
Update routine for 0material
data: wa_itab type t_itab.
read table itab into wa_itab with table key pur_doc = COMM_STRUCTURE-OI_EBELN
item = COMM_STRUCTURE-OI_EBELP.
if sy-subrc = 0.
RESULT = wa_itab-matplant.
else.
clear result.
endif.
Hope this helps
regards
Siggi

Can routine replace "master data attribute of" update rule for performance?

Hi all,
We are working on CRM-BW data modeling, We have to look up agent master data for agent level and position for each transaction data. So now we are using "Master data attribute of" update rule. Can we use routine instead of "Master data Attribute of" ? Will it improve the loading performance? Since we have to load 1 lack transaction records , where as we have 20,000 agent details in agent master data.My understanding is, for each record in data package the system has to go to master data table and bring the agent details & store in cubes. Say one agent created 10 transactions, then this option "master data attribute of" will read the agent master data 10 times even though we are going to pull same details for all 10 transactions from master data. if we use routine, we can pull the agent details& storing in internal table removing all duplicates and in update routine we can read the internal table.
Will this way improve performance?
let me know if you need further info?
Thanks in advance.
Arun Thangaraj

Hi,
your thinking is absolutely right!
I don't recommend to use the standard attribute derivation since it will perform a SELECT to the database for EACH record.
Better implement a sorted table in your start routine; fill it with SELECT <fields> FROM <master_data_table> FOR ALL ENTRIES OF datapak WHERE OBJVERS = 'A' etc...
In your routine perform a READ itab ... BINARY SEARCH.... I believe that you won't be able to go faster...
hope this helps...
Olivier.

Interactive Report - Chart axis value wrong data

Hi,
we created an interactive report based on demo_orders table.
The interactive chart is displaying wrong data on the value axis (4,00000 instead of 4,000.00)!
Values in the table are ok, even the value displayed when user clicks on specific data point is correct.
Did somebody had similar problems?
Application Express 3.2.0.00.27
AnyChart #5.1.3
Thanks.
Regards,
Kristjan

Hi Kristjan,
I'm able to reproduce the issue you report, using an Interactive Report in APEX 3.2.1 and 4.0, where the Application Language is a non-English option. So for example, if my chart label in English is *10,000.00* and when I switch the Application Primary Language to German, then the displayed values should be *10.000,00* however it is incorrectly appearing as *10,000*. When running in some non-English languages, the NLS decimal separator used is a comma ',', but this isn't been correctly applied to the Interactive Report chart. The problem is arising from the fact that the decimal separator setting in the chart XML is not being escaped correctly, and is therefore being ignored. I've logged bug 10154666 to track this issue, and a fix for this will be available in our next release. Thanks for bringing this to our attention. In the meantime, and to ensure the values on your chart are accurately displayed, it might be best to create a separate chart region on the page in question, rather than using the Interactive report chart.
Regards,
Hilary

Update Routine to populate 0VENDOR from either of the 2 data source fields

Hi,
I have a requirement to write an update routine for 0VENDOR based on the below logic :
Create routines to populated BW Info Object u201CVendoru201D (0VENDOR) based on the following logic:
IF field u201CVendoru201D (ITM_VENDOR_ID) is populated from data source 0BBP_SC_TD_1, THEN populate 0VENDOR with that value
ELSE IF u201CPreferred Vendoru201D (ITM_PROPVEN_ID) is populated from data source 0BBP_SC_TD_1, THEN populate 0VENDOR with that value
ELSE IF neither u201CVendoru201D (ITM_VENDOR_ID) or u201CPreferred Vendoru201D (ITM_PROPVEN_ID) are populated from data source 0BBP_SC_TD_1, then 0VENDOR = NULL
Can anyone help me in converting this logic into ABAP routine.
Thanks,
Suchitra

Hi Suchitra,
In the Transfer Rules ... You will be mapping each field then the mapping field click on the button with Triangle then you can see the which type you want.
Then select the routine and select the datasource fields (don't forget to select the both fields VENDOR and PROPITM)...
Then give a name to routine ...
and in the code just change the COMM_STRUCTURE to TRANSFER_STRUCTURE.
Then you can get this .... done..
Regards,
Ravi Kanth

Report returns wrong data when run on server

Hi,
I'm runing CRS XI R2 on Windows Server 2003 SP2. When I refresh a report in the Crystal Reports XI Designer, I'm getting correct data. But when I schedule the report to run on the server it returns wrong data. The data is different from what I see when I refresh it from the designer. In the report I have running totals set up to count customers that meet a certain criteria. The report is very large. It take almost 2 hours to refresh.
I was wondering what is causing the difference in running total data between refreshing it on the designer and running it on the server. Is it returning wrong data b/c of it not reading all the records? Should I be making any changes to the server settings? I saw that under pageserver, there are options for setting the 'Minutes Before an Idle Report Job is Closed' and 'Database Records To Read When Previewing Or Refreshing a Report". Do either of those have anything to do with the report returning incorrect data when being scheduled to run on the server?
Thanks,
Kim

Hi Xuandao,
You would need to Use Cell Binding and Trigger concept to accomplish this.
Its simple, however, you would have to work on a trial and error basis to understand this concept as implementing the same is subject to your dashboard and WEBI Design.
Open you LiveOffice.
Insert your WEBI, Now, go to Object Properties of your WEBI, select the second tab that says Prompt, Here, it lists the prompts that you have for your WEBI. This would also enlist your BEx variables as well. Select this BEx variable and click on the button that says Prompt at the bottom of this window. Here, select choose Excel Data Range and click on the cell select button on the right (small button that lets you choose what cell you want to bind this prompt to), Now select a free cell that would not be even populated later on when you run the dashboard say A1 (remember the value that you select). Click on OK and again OK. The WEBI Refreshes and you can see all the prompt values at the cell A1. These are all the possible values stored for your BEx prompt variables (these values are fetched from BW system dynamically).
Now, save this LiveOffice, Go to you dashboard. Connect your dashboard to your Live office. Go to Data-> connections-> Now, select the WEBI and in the right hand pane go to Usage tab, here, Click on Trigger cell button on the right hand side and select A1 in you LiveOffice.
It should work fine.
Let me know.
Rgds,
Sreekul Nair

Wrong DATE-TIME FORMAT among REPORTS NOTIFICATION EMAILs

Dear all,
I create a report request with url
https://ocixxxx2.oci.xxcl.net/reports/rwservlet?>destype=printer&desformat=PDF&server=rep_xxxxx2_orahome&userid=ixxxxxx/xxxxxxx@saas&notifysuccess=IASL&notifyfailure=IASL&report=R1000R13.rdf&jobname=R1000R13&desname=HPLaserJet4150PCL6
Email notification was generated with wrong date format .
It's expected to be in UK English but it shows encoded text , may be random. I route it to another email servers such that find the date time is in chinese characters . That caused problem on original email server in which was not supported
Could any expert please advice ?
Warmly
Edited by: MosielleKwan on 2010年2月26日下午11:31

It's indeed an expected behavior.
When a Reports Server starts on a Windows machine, it likely detect the Windows Regional Settings in order to use it when needed later. This let the Reports Server communicate in the same format/way the Server machine uses. For example, if the System / Application Server administrator prefers to use the Windows (on which the Application Server is installed) with Chinese Regional Options, it is normal that the Reports Server send the Notification Email with a "Date/Time" Format matches the Windows.
Thence, you like to get English/Western Date and Time format in the Reports Server Notification Email, it is required to change the Windows Regional Settings from Chinese to English and restart the Reports Server and restart the corresponding compoent. This will let the Reports Server detect the change and will send the Notification Email(s) then with English/Western Date and Time formats.
If English/Western Date and Time format in the Reports Server Notification Email but still have the Windows Regional Settings set to Chinese, you can implement it
that :-
1. Change the Windows Regional Settings from Chinese to English.
2. Restart the Reports Server and restart others.
3. Change the Windows Regional Settings back from English to Chinese. .
With these 3 steps, the Reports Server will keep sending the Notification Emails with English/Western Date and Time format, and maintain original settings.

EWA Report collect the wrong data

Hi all
Our EWA Report can not collect data perfectly
It says that
When we checked the log files of the archive runs, we detected that your archive strategy does not follow the SAP archive recommendations.
In the time period from 28.04.2009 to 25.05.2009 , we noticed the following problems:
- There was neither a successful archive run nor a successful off-line backup on Friday 22.05.2009
- There was neither a successful archive run nor a successful off-line backup on Thursday 21.05.2009
- There was neither a successful archive run nor a successful off-line backup on Wednesday 20.05.2009
- There was neither a successful archive run nor a successful off-line backup on Tuesday 19.05.2009
- There was neither a successful archive run nor a successful off-line backup on Monday 18.05.2009
There are 5 working days without successful archive run this week.
In fact, the backup run smoothly, for that period. I think the system read the wrong period. On 5 May - 6 May 2009, backup error but from 7 May until now, backup run smoothly
FYI : On 8 Mei 2009 we restart our production system
The saposcol and sapccmsr run already
but when I hit OS07N, there is no data on casapdb system, error "Partner casapdb_CAP_32 not reached (reading table)
Can anybody help to to solve my problem?
thanks
regards,
Della

well for backups as you say.....
SAP looks for offline backups every day and since you are not doing offline backups,so it says an error during EWA report,so you must not be too much concerned on backup error in EWA report,
what wrong data is EWA collecting apart from this
Rohit

I have a feeling this has been up here a lot. I updated ios 6 to my phone with no problems but I also back my phone up. I decided to help the wife out and update hers and something went wrong data lost. All contacts, photos, etc without backup, help.

I have a feeling this has been up here a lot. I updated ios 6 to my phone (4S) with no problems but I also back my phone up. I decided to help the wife out and update hers and something went wrong data lost. All contacts, photos, etc without backup, help.

if you have no back up in icloud or itunes the best you can do is sync with your computer and get back what you can from there

Look up at master data in update routine

Hi all,
I am loading from flat file in to an infocube. My transaction data comes in the format Subcategory, Area,Date, Sales qty,UOM. But my infocube should be filled with Category,Subcategory,Region,Area,Date,SalesQty,UOM. My business requirements want me to model Category, Subcategory,Region area as characteristics of dimension. ie I cannot model Category as navigational attribute of Subcategory and Region as navigational attribute of Area.
But I can get the master data file for Subcategory in Sucategory, Category format and Area in Area, Region format. So when I load the transaction data I can make a table lookup on these master data table and fill the required fields.
But the problem is I donot have much experince in ABAP routines.
Can any one help me with a sample start/update routine on how to do this.
Any help will be appreciated.
Regards,
Amith

Amith,
Actually, you may everything do in a start routine of the URs (including lookup itself).
There is no need to declare internal table in a global part of routine and then read values in routines.
The code may look the following. (Don't have the system on hand. So, some syntax may require some modification.)
TABLES: <Your Master Data Table>.
DATA: wa_temp TYPE DATA_PACKAGE_STRUCTURE OCCURS 0 WITH HEADER LINE,
     wa_md TYPE <Your Master Data Table> OCCURS 0 WITH HEADER LINE.
SELECT * FROM <Your Master Data Table> INTO wa_md.
SORT wa_md ASCENDING BY <Basic Char Key>.
LOOP AT DATA_PACKAGE INTO wa_temp.
   READ TABLE wa_md WITH KEY <Basic Char Key> = wa_temp-<Basic Char Key>.
   wa_temp-<YourLookupIO> = wa_md-<YourLookupAttribute>.
   MODIFY DATA_PACKAGE FROM wa_temp.
ENDLOOP.
Best regards,
Eugene

Urgent BEX Report Showing the Wrong data

Hi Experts,
In my Cube the data is available curreclty, but where as my bex report showing the wrong data.
like xeample:
Infocube
Material               Plant    Year    Units Qty
000000000002001032     003     2006     BAG   1,500
But in bex i took the same selection's, but it displays as
000000000002001032     003     2006     BAG   2
i am Unable to trace this
any help plzzz
Anil

Hi,
since Quantity(units PC??) can not be in decimals,Bex will round off 1.5 to 2 in bex report.
Use NODIM function i.e. NODIM(Qty) instead of Quantity.
NODIM function is available under data functions of Formula builder.
From context menu fo KF structure>new formula>NODIM(Qty).
or
try by setting Decimal places to 2 or 3 in KF properties in Bex Query.
hope this helps.
Message was edited by: Murali

Report showing wrong data

Hi Gurus,
When we are generating report in the answers in one column it is showing wrong data from where i have to start for this issue.
Thanks,
Rafi

Pull that column alone,run report, compare the results with your manual query, and also compare the physical query.
if all are good then try to add other column from any other dim and then do the same as above
repeat till you know the cause.
Pls mark if helps

Is there any way for updating wrong data in ODS and infocube?

Hi all
Is there any way for correcting wrong data in ODS and infocube?

You could do a selective deletion, by specifying the filter values, so that you only delete a subset of the entire data. You could then do a re-load for the same selection so that there is no duplication of records.
This is on the assumption, that your incorrect data is due to some incorrect update or transfer rules, which you have now corrected (before the re-load).
mate, you have mentioned that You could then do a re-load for the same selection .
could you please tell me how to do a re-load ? thank you very much

Update routine bringing wrong data in Report

Similar Messages

Maybe you are looking for