﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>IT博客-SAP BI Blog - Collingwood Park</title><link>http://www.cnitblog.com/BI-Blog/</link><description>SAP BW/SEM</description><language>zh-cn</language><lastBuildDate>Wed, 29 Apr 2026 05:57:22 GMT</lastBuildDate><pubDate>Wed, 29 Apr 2026 05:57:22 GMT</pubDate><ttl>60</ttl><item><title>Currency Conversion in BPC</title><link>http://www.cnitblog.com/BI-Blog/archive/2009/09/17/61458.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Thu, 17 Sep 2009 07:19:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2009/09/17/61458.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/61458.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2009/09/17/61458.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/61458.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/61458.html</trackback:ping><description><![CDATA[<p>I got a few error messages when trying to run Currency Conversion for Consolidation Application in SAP BPC 7 NW, finally everything works. Now would like to share as below:<br><br>1. The Currency Conversion Script Logic:<br><br>The standard Script Logic is:<br>*RUN_PROGRAM CURR_CONVERSION<br>CATEGORY = %C_CATEGORY_SET% <br>GROUP = %GROUPS_SET% <br>TID_RA = %TIME_SET%<br>RATEENTITY = GLOBAL<br>OTHER = <a href="http://forums.sdn.sap.com/" target=_newWindow><u><font color=#0000ff>ENTITY=%ENTITY_SET%</font></u></a>//For More than one other scope parameters: OTHER = <a class=jive-link-external href="http://ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%..." target=_newWindow><u><font color=#0000ff>http://ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...</font></u></a><br>*ENDRUN_PROGRAM<br><br>I got an error message of "Member "USD" not exist" when run the data package.<br><br>This SDN&nbsp;thread provides a solution: <a href="https://forums.sdn.sap.com/message.jspa?messageID=7718017">https://forums.sdn.sap.com/message.jspa?messageID=7718017</a><br><br>Add: SELECT(%CURRENCY_SET%,"<a href="http://forums.sdn.sap.com/" target=_newWindow><u><font color=#0000ff>ID</font></u></a>",CURRENCY,"<a href="http://forums.sdn.sap.com/" target=_newWindow><u><font color=#0000ff>CURRENCY_TYPE</font></u></a>='R'")<br><br>However it did not work for me, still have the same error.</p>
<p>Then I found another SDN thread: <a href="https://forumsa.sdn.sap.com/message.jspa?messageID=8026975">https://forumsa.sdn.sap.com/message.jspa?messageID=8026975</a><br><br>The last post is very important, you SHOULD adapt the standard Script to your own Dimension names. Then the script passed the validation.<br><br>2. The P_DataSrc Dimension Properties:<br><br>Data Package is still not work, with an error of "Package status : RUNNING".<br><br>The third SDN thread is really helpful: <a href="https://forums.sdn.sap.com/thread.jspa?threadID=1432486&amp;tstart=1">https://forums.sdn.sap.com/thread.jspa?threadID=1432486&amp;tstart=1</a><br><br>After I added properties of "DATASRC_TYPE" and "IS_CONVERTED", my package finished successfully.<br><br><br></p>
<p>&nbsp;</p>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/61458.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2009-09-17 15:19 <a href="http://www.cnitblog.com/BI-Blog/archive/2009/09/17/61458.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>BPC Template Version</title><link>http://www.cnitblog.com/BI-Blog/archive/2009/09/04/61231.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Fri, 04 Sep 2009 04:22:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2009/09/04/61231.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/61231.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2009/09/04/61231.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/61231.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/61231.html</trackback:ping><description><![CDATA[



<span style="FONT-SIZE: 10pt">Could not find the Template Version is stored as a web admin parameter in table UJA_USER_DEF!?&#160;And what is the usage of the BPC Process Chain Type, "BPC: Modify Dynamically"?</span><img src ="http://www.cnitblog.com/BI-Blog/aggbug/61231.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2009-09-04 12:22 <a href="http://www.cnitblog.com/BI-Blog/archive/2009/09/04/61231.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Web Interface and Cookie</title><link>http://www.cnitblog.com/BI-Blog/archive/2008/08/07/47600.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Thu, 07 Aug 2008 08:41:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2008/08/07/47600.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/47600.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2008/08/07/47600.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/47600.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/47600.html</trackback:ping><description><![CDATA[<br>"No seesion cookie" parameter has been added at the end of URL generated for&nbsp;BPS Web Interface by below SAP notes (BW 3.5 SP21&amp;22).&nbsp;<br><br><a class="urLnkFunction urVt1" title="Right mouse click to add this SAP Note to your browser favorites" href="https://service.sap.com/sap/support/notes/1023893" alt="Right mouse click to add this SAP Note to your browser favorites"><span class=urTxtH1 id=header_data ct="TextView"><u><font color=#0000ff>Note 1023893 - BPS Web: Connection time out / session cookie</font></u></span></a><br><br><a class="urLnkFunction urVt1" title="Right mouse click to add this SAP Note to your browser favorites" href="https://service.sap.com/sap/support/notes/1132985" alt="Right mouse click to add this SAP Note to your browser favorites"><span class=urTxtH1 id=header_data ct="TextView"><u><font color=#0000ff>Note 1132985 - Follow-on note for Note 1023893 - no sessioncookie</font></u></span></a><br><br>However when testing in SE80 or SICF, or creating iview in EP, cookie might cause issues. Then please manually add parameter "sap-syscmd=nocookie" at the end of URL.<br><br>Something else of BSP:<br><br>Stateful or Stateless Programming?:&nbsp; <a href="http://help.sap.com/saphelp_nw04/helpdata/en/d5/6b113a2604c679e10000000a114084/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/d5/6b113a2604c679e10000000a114084/frameset.htm</a><br><br><br>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/47600.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2008-08-07 16:41 <a href="http://www.cnitblog.com/BI-Blog/archive/2008/08/07/47600.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Check SAP Note in German as well </title><link>http://www.cnitblog.com/BI-Blog/archive/2008/04/18/42499.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Fri, 18 Apr 2008 03:52:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2008/04/18/42499.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/42499.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2008/04/18/42499.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/42499.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/42499.html</trackback:ping><description><![CDATA[<br>Got an error message of "incorrectly defined FRANGE row in the THX_FROM for inforobject" when executing Key Figure Definition in the BW Query, it was caused by excluding selections in the Query Definition. However could not find a SAP Note in English, and was told by a OSS message that Note in German 1160835 can correct the bug.<br><br>I think I could only find it if I had used "BRAIN 415" to search a SAP Note in German. So when could not find a note next time, try in German. But how to understand&nbsp;the content then? By Google...http://translate.google.com/translate_t<br><br>-------------------------------------------------------------------<br>1160835 Note - The definition does not figure. BRAIN 415 <br><br>Summary <br><br>Symptom <br><br>Query execution: <br>It is the message "Incorrect FRANGE line in the THX_FORM to InfoObj &lt;XYZ&gt;" BRAIN 415th <br><br><br>Further terms <br><br>Parenthesis. Indicator definition. Explain query. <br><br><br>Cause and conditions <br><br>The filter is a stapled feature. <br>The definition does not figure. <br><br><br><br>Solution <br><br>BW 3.0B / BW 3.10 Content <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Please use the specified corrections management. For the SAP BW releases 3.0B and 3.10 are also up to no longer support packages delivered. <br><br>BW 3.50 <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Play the Support Package 23 for 3.5 (BW3.50-Patch23 or SAPKW35023) to your BW system. The support package is available if the notice 1146357 with the short text "SAPBWNews BW SP23 NetWeaver'04 stack 23" is released for customers who support this package closer describes. <br><br><br>In urgent cases, the correct leadership of uranium used. <br>These guidelines can even before the release of the support packages available for advance information available. In this case, however, the short text, the word "pre-release". <br><br><br><br><br>Data header <br><br>&nbsp;&nbsp; <br>Release Status: Released for Customer <br>Released on: 15.04.2008 10:40:56 <br>Priority: Correction with medium priority <br>Category: Program Error <br>Primary Component: BW BEX-OT-OLAP Analyzing Data <br><br>Affected Releases <br><br>Software&nbsp;component&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From release&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;To release &nbsp;And Release&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Following <br>SAP_BW&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30B&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30B <br>SAP_BW&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 310&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 310&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 310 <br>SAP_BW&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 35&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 350&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 350 <br>SAP_BW_VIRTUAL_COMP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 30350&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30 B&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;30B<br><br><br>Corrections Instructions <br><br>Correction Instructions&nbsp;&nbsp;&nbsp; &nbsp;Valid&nbsp;&nbsp;&nbsp;&nbsp; Validity of Up&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; software Component&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type *)<br>991214&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;30B&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;30B&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SAP_BW_VIRTUAL_COMP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; C&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>References&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last Correction Change<br>J19K029019&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15.04.2008 08:44:46 <br>&nbsp; <br>*) C correction, preliminary B, A reworking, m still not certain work Attributes <br><br>Attribute&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; value <br>Downtown Port UpPort WF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; examination necessary UpPort&nbsp;&nbsp;&nbsp; <br><br>--------------------------------------------------------------------<br><br>Not bad Huh?<br>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/42499.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2008-04-18 11:52 <a href="http://www.cnitblog.com/BI-Blog/archive/2008/04/18/42499.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>How to Load a Flat File into BW-BPS Using  a Web Browser V 3.0 - System Files</title><link>http://www.cnitblog.com/BI-Blog/archive/2008/04/08/42125.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Tue, 08 Apr 2008 06:21:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2008/04/08/42125.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/42125.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2008/04/08/42125.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/42125.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/42125.html</trackback:ping><description><![CDATA[<br>In SAP How-to document "How to Load a Flat File into BW-BPS Using&nbsp; a Web Browser V 3.0.PDF", you might notice there are no Chapter 11 and 12 as indicated in Version History.&nbsp;although March 2006 version PDF file&nbsp;can be found, the "Chapter 12.3: Fix for CX_SY_REF_IS_INITIAL exception. Change Event Handler: OnInitialization&nbsp;" part is still missing.<br><br>Fortunately the system files are archived in SDN -&gt; Articles&nbsp;(by date), then the new code is:<br><br><font face=Arial color=#0000ff size=2>* event handler for data retrieval</font> <br><font size=3>&nbsp;</font> <br><font face=Arial color=blue size=2>* call initialization here<br>call method application-&gt;initialization(<br>&nbsp; &nbsp; &nbsp;runtime &nbsp; &nbsp;= runtime<br>&nbsp; &nbsp; &nbsp;page &nbsp; &nbsp; &nbsp; = page<br>&nbsp; &nbsp; &nbsp;request &nbsp; &nbsp;= request<br>&nbsp; &nbsp; &nbsp;response &nbsp; = response<br>&nbsp; &nbsp; &nbsp;navigation = navigation<br>&nbsp; &nbsp; &nbsp;version &nbsp; &nbsp;= 300<br>&nbsp; &nbsp; &nbsp;).</font> <br><font size=3>&nbsp;</font> <br><font face=Arial color=blue size=2>runtime-&gt;keep_context = 1.</font> <br>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/42125.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2008-04-08 14:21 <a href="http://www.cnitblog.com/BI-Blog/archive/2008/04/08/42125.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>5 T-codes</title><link>http://www.cnitblog.com/BI-Blog/archive/2008/01/01/32553.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Mon, 31 Dec 2007 23:53:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2008/01/01/32553.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/32553.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2008/01/01/32553.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/32553.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/32553.html</trackback:ping><description><![CDATA[1. RSSMQ: check user authorization<br><br>2. SE38: run program "WRITEQUERY". "EXCEL" unselected can have more than 256 columns. <br><br>3. SCU3: Evaluate logged table;<br><br>4. SM30: maintain table TVARV - Variable selection of Query;<br><br>5. RSRV: Analysis and Repaire of BW objects;<br><br>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/32553.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2008-01-01 07:53 <a href="http://www.cnitblog.com/BI-Blog/archive/2008/01/01/32553.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Q&amp;A</title><link>http://www.cnitblog.com/BI-Blog/archive/2007/12/08/37481.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Fri, 07 Dec 2007 16:12:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2007/12/08/37481.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/37481.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2007/12/08/37481.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/37481.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/37481.html</trackback:ping><description><![CDATA[<br><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Some friends asked me BI technical questions; I think it is a good idea to have a post to host all.<br><br>Q: When I create the infosource, there are two methods, one is infosource with flexible update, the other is infosource with direct update. can you explain the difference between them in detail? Thanks. <br><br>A: Flexible update is via update rules, master data (Hierarchy is not applicable) with flexible update is considered as a Data target; Direct update updates Master data only, not via update rules. Please find details @ <a href="http://help.sap.com/saphelp_nw04/helpdata/en/57/e537373aedaf43e10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/57/e537373aedaf43e10000009b38f839/frameset.htm</a></span>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/37481.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2007-12-08 00:12 <a href="http://www.cnitblog.com/BI-Blog/archive/2007/12/08/37481.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>A Standard ODS</title><link>http://www.cnitblog.com/BI-Blog/archive/2007/11/21/36667.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Wed, 21 Nov 2007 09:46:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2007/11/21/36667.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/36667.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2007/11/21/36667.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/36667.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/36667.html</trackback:ping><description><![CDATA[<br>An ODS can be considered as a table, which means it is different from a Cube, it has only 2 dimensions.<br><br>Take an standard ODs from Business Content as an instance: 0CCA_O09&nbsp;- Cost Center Actuals<br><br>1. Settings:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;BEx Reporting - select if you want to report on&nbsp;it;<br>&nbsp;&nbsp;&nbsp; Unique data records - select if you do not want loada data record into the ODS object if the key combination already exists; usually not to select&nbsp;it;<br>&nbsp;&nbsp;&nbsp; Set quality status to 'OK' automatically;<br>&nbsp;&nbsp;&nbsp; Activate ODS object data automatically;<br>&nbsp;&nbsp;&nbsp; Update data target from ODS object automatically;<br><br>2.&nbsp;&nbsp;Key Fields:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp; Controlling Area<br>&nbsp;&nbsp;&nbsp;&nbsp; CO Document Number<br>&nbsp;&nbsp;&nbsp;&nbsp; Line item of CO Document<br>&nbsp;&nbsp;&nbsp;&nbsp; Currency Type<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Key figure Type<br>&nbsp;&nbsp;&nbsp;&nbsp; Value type for reporting<br>&nbsp;&nbsp;&nbsp;&nbsp; Fiscal year variant<br><br>3. Data Fields:<br>&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; The rest of Char and Key Figures (Key figures are Cumulative Values)<br><br>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/36667.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2007-11-21 17:46 <a href="http://www.cnitblog.com/BI-Blog/archive/2007/11/21/36667.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Transactional ODS Vs. Standard ODS</title><link>http://www.cnitblog.com/BI-Blog/archive/2007/10/31/35640.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Tue, 30 Oct 2007 21:17:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2007/10/31/35640.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/35640.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2007/10/31/35640.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/35640.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/35640.html</trackback:ping><description><![CDATA[&nbsp;
<p><span>Tonny, a new BW pal asked me a question of the difference between the Transactional ODS and the Standard ODS. Frankly I just remember my SAP trainer mentioned it during BW3.5 Delta course, in APD (Analysis Process Designer) part; but never use transactional ODS in my projects, so I have done some research on it. Well, you always can search using key word of &#8220;transactional ODS&#8221; by Google; you might need SAP SDN and </span><st1:street><st1:address><span>Service Market Place</span></st1:address></st1:street><span> accesses to open some links though.</span></p>
<p>&nbsp;</p>
<p><span>* I always prefer go to SAP Lib for information first, basically the difference can be summarised as below:</span></p>
<p><span><a href="http://help.sap.com/saphelp_sem320bw/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm">http://help.sap.com/saphelp_sem320bw/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm</a></span></p>
<p>&nbsp;</p>
<ol type=1>
    <li><span>The Transactional ODS contains only once table that is the Active table where as the standard ODS contains Active Data Table, New Data Table and change log. </span>
    <li><span>So delta update from transactional ODS to other data target is not possible, however you can use a full update. You can not find &#8220;Update&nbsp;ODS data&nbsp;in&nbsp;Data target...&#8221; in the menu as for a Standard ODS. </span>
    <li><span>When converting a Standard ODS to a transactional one, the update rules and transfer rules will be inactive.</span>
    <li><span>Data can be read faster from a transactional ODS than a Standard ODS (no activation). <span>&nbsp;&nbsp;</span></span>
    <li><span>A transactional ODS can not be used for a Query directly; however you can create an InfoSet based on it, in BW 3.5. In BW 7, with the new name &#8220;DataStore object for direct update&#8221;, it can be used as an InfoProvider for BEx Query.</span> </li>
</ol>
<p>&nbsp;</p>
<p><span><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm</a></span></p>
<p><span><br><br></span></p>
<p><span>* Then you might need a transactional ODS when:</span></p>
<p>&nbsp;</p>
<ol type=1>
    <li><span>in APD </span></li>
</ol>
<p>&nbsp;</p>
<p><span><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/49/7e960481916448b20134d471d36a6b/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/49/7e960481916448b20134d471d36a6b/frameset.htm</a></span></p>
<p>&nbsp;</p>
<p><span>A simple case:</span></p>
<p>&nbsp;</p>
<p><span><a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4419">https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4419</a></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<ol type=1 start=2>
    <li><span>Or want to read the data written to the ODS instantly (without activation).</span> </li>
</ol>
<p>&nbsp;</p>
<p><span>Scenario 1:</span></p>
<p>&nbsp;</p>
<p><span><a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=184702">https://www.sdn.sap.com/irj/sdn/thread?threadID=184702</a></span></p>
<p>&nbsp;</p>
<p><span>We had data coming from two sources, one is from R/3 side and the other one is the dynamic data which the user enters. The client wanted to have the result of the user entered data instantly.<br>So for the user entered data was maintained in the transactional ODS and R/3 data was updated in a standard ODS. We combined the two ODS objects in an Infoset and created the queries.</span></p>
<p>&nbsp;</p>
<p><span>Scenario 2:</span></p>
<p>&nbsp;</p>
<p><span>You have data in an InfoProvider, and you have a query that provides you the results you are looking for, but the query does logic that you cannot easily replicate in any update rules.<br><br>So, you use an APD (Analysis Process Design) to use a query as a DataSource. Then you update a transaction ODS with that DataSource (a BW query). Then move the data from the transactional ODS to a reportable object (ODS or cube) for last combination in other reporting.<br></span></p>
<p><br>* Actually you also can Set the query as an ODBO, and use RSCRM_BAPI to&nbsp;create Query Extract (to table), or use MDX to realize.&nbsp;&nbsp;</p>
<p><span>Scenario 3:</span></p>
<p>&nbsp;</p>
<p><span>During planning, it is often necessary to maintain a comment (a short text up to 60 characters long) for each data record. This article explains (with sample ABAP code) how to maintain text fields like comments directly in the planning layout using then interface with Transaction ODS.</span></p>
<p>&nbsp;</p>
<p><span><a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60938938-de6f-2910-2080-fc80d38ebfec">https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60938938-de6f-2910-2080-fc80d38ebfec</a></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>* Available APIs when using transactional ODS objects:</span></p>
<p>&nbsp;</p>
<p><span><a href="http://help.sap.com/saphelp_sem320bw/helpdata/en/c7/dc833b2ab3ae0ee10000000a11402f/content.htm">http://help.sap.com/saphelp_sem320bw/helpdata/en/c7/dc833b2ab3ae0ee10000000a11402f/content.htm</a></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>* You might also be interested in the new member of DSO family&nbsp;in BI 7, &#8220;write-optimized DataStore Objects&#8221;, then you can find the details in SAP Lib via:</span></p>
<p>&nbsp;</p>
<p><span><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm</a></span></p>
<p>&nbsp;</p>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/35640.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2007-10-31 05:17 <a href="http://www.cnitblog.com/BI-Blog/archive/2007/10/31/35640.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>Synchronize the hierarchy between BW and SEM-BCS</title><link>http://www.cnitblog.com/BI-Blog/archive/2007/08/06/31357.html</link><dc:creator>Jonathan Ji</dc:creator><author>Jonathan Ji</author><pubDate>Mon, 06 Aug 2007 13:45:00 GMT</pubDate><guid>http://www.cnitblog.com/BI-Blog/archive/2007/08/06/31357.html</guid><wfw:comment>http://www.cnitblog.com/BI-Blog/comments/31357.html</wfw:comment><comments>http://www.cnitblog.com/BI-Blog/archive/2007/08/06/31357.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnitblog.com/BI-Blog/comments/commentRss/31357.html</wfw:commentRss><trackback:ping>http://www.cnitblog.com/BI-Blog/services/trackbacks/31357.html</trackback:ping><description><![CDATA[<br>To synchronize the hierarchy between BW and SEM-BCS use program UGMDSY20, so BW hierarchies become available for SEM-BCS.<br><br>Or, if you load the hierarchy through flex-upload in SEM-BCS, then hierarchy becomes available in both SEM-BCS and BW.<br><br>However, in practice SEM-BCS projects utilize BW implementation in exist, and UGMDSY20 is for that. <br><br>* Quoted from a thread in IT ToolsBox, thanks to Metin Colak.<br><br>*&nbsp;You also can find a&nbsp;How-to guide of "How To Upload Hierarchy and Master Data of FS Items in SAP SEM-BCS 4.0 by Using Flexible Upload Method" in SAP SDN, contributed by <a href="https://weblogs.sdn.sap.com/pub/u/32317" target=_top><span style="COLOR: #000000"><u>Eugene Khusainov</u></span></a><span style="COLOR: #000000">.&nbsp; </span>
<img src ="http://www.cnitblog.com/BI-Blog/aggbug/31357.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cnitblog.com/BI-Blog/" target="_blank">Jonathan Ji</a> 2007-08-06 21:45 <a href="http://www.cnitblog.com/BI-Blog/archive/2007/08/06/31357.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item></channel></rss>