Extend OSS note 561593 to SAP_APPL version 617.

guys,
Can you advise the fastest way to update a OSS note to new version.
We recently got upgraded to EHP7 and there the note 561593 cannot be implemented.
please advise.

Open the note from here: 561593 - Sender der Nachricht (Fax und/oder E-Mail) ist falsch
open the last correction e.g.1440722
you find there 2 programs, if you click them you see the coding changes.
Now go into your SAP and check the same program in your system and see if those changes are already there. (which I expect for a new release)
If they are included, then there might be another problem.

Similar Messages

How to find the right OSS Note for my SAP version

Hi All,
There have been issues with the Vendor/Material Master records whenever we run a LSMW by recording process. It is such that all those fields that we have not updated come up with a value as *DELETED* for which i think we should implement a OSS Note to our system.
I am unable to find the right OSS Note Number for this to our SAP system :
SAP_APPL Support Pack: SAPKH50009 Components:Logistics & Accounting.
Request you all to provide me with the correct OSS Note Number so that we can get this issue corrected as this has become very critical.

Hi,
As Jurgen wrote - it could be some programming problem.
But, generally, if you find a SAP Note, that, in your opinion, can solve your SAP problem and it is not intended for your SAP version - simply write to SAP OSS.
If this note really solves your problem, they will extend the validity of this note for your SAP version.
Otherwise, if it is SAP problem, OSS will try to provide solution for it.
I usually act like this - it works.
Hope it helps, not this time, maybe in the future.
Regards,
Wojciech

UPGRADE - OSS NOTE MODIFIED PROGRAMS

Hi all,
we are on verge of upgradtion form 4.6c to ECC 6.00
we have a lot of programs where we have applied oss notes.
Do i need to apply the oss notes in the new version ECC 6.00 too.
How can i know whether SAP has provided the same note modifications in new version i.e ECC 6.00
IN THAT CASE I DON'T HAVE TO APPLY OSS NOTE AGAIN.
Where does SPAU AND SPDD COME IN TO PICTURE
let me know if iam wrong
THANKS
SWATHI

hi Swathi,
A typical SAP version version upgrade has two phases:
1 - technical upgrade (installing the new version of SAP and migrating all the current objects to the new system)
2- adjusting the modifications.
SPAU/SPDD comes in the second phase.
Once we install the new version and migrate all the active objects into the new version, you can see the list of modified objects (including OSS note applications) in SPAU and SPDD.
SPDD contains all the data dictionary objects and SPAU the rest.
You need to drill down from SPAU and do a versin comparison with the active version in the existing system (the system with SAP's older version). If you come across changes with OSS notes,
firstly, you need to check in service.sap.com/notes the releases it supports. If it does not support the latest version, you will need to find a replacement note for this and implement the same. Else, if it is supported in the new release, you need to carry forward the changes in previous version to the new version. For this you need only to right click on the object in SPAU and select "adopt changes".
Hope this helps,
Sajan Joseph.
only the objects coming in SPAU

OSS Note for Updating the SHE Cess in 4.6 Version - Urgent

Hi,
Good Afternoon!
In Form 26Q, I am not getting Separate column for SHE Cess and under WHTax amount it is adding up all other amounts ( i.e. WHTax Amt + Surcharge Amt + Ecess Amt+ SHE Cess Amt). I am working on 4.6 version.
Can anybody update me what is the OSS note get SHE Cess while printing form 26Q.
Regards
Srinivas

If you are using separate tax codes for Education cess, those tax codes should be maintained in the J_1IEWTECESS table and 'X' should be maintained for the company code in J_1IEWT_ECFLAG table
Refer (only refer) the solution part of the note 870991 and 853918 for details relating to table creation.
1067759 J1INQEFILE - Changes related to Customer TDS
assign points if its useful

OSS Note of Older Version ?

Dear All,
Can we download a OSS note which is of older version than the latest version.
i.e. if the latest version is 17 and I want to have the same OSS note of version 5 then can i download the same from SNOTE Transaction ?
Regards,
Deepu.k

Hello Amit,
Do u mean to say, we cannot download the older version for a OSS Note ?

OSS Note-version

hi,
i am downloading OSS Note 852990.it is downloaded successfully.But while implementing it gives error-'SAP Note does not contain valid correction instruction'.
But while going to error log,this shows the message-'SAP NOte 852990 in version 0004 downloaded'.
any idea how to correct the error?

Hi,
Check what is the Highest support package applied.Since this is Valid to Support Package    500 - SAPKH50008 .
Go to se37 and check for the code in FUNCTION module BAPI_INB_DELIVERY_CHANGE
IF NOT GS_VBKOK-LIKP_DEL IS INITIAL.                       "v_n_852990
    PERFORM CSL_REORG TABLES TOKENREFERENCE.
ENDIF.                                                                           "^_n_852990
PERFORM ROLLBACK_CHECK.
If this code is present then the Note is applied.
Thanks,
Ahsan
Edited by: Mohammed Ahasanullah Mulla on Apr 11, 2008 8:25 AM

Can u send oss notes 192658...

hi friends, can any one post the OSS Notes 192658, for basic (parameters)setting for bw.
thanks in advance

Summary
Symptom
You want to set the Business Warehouse System (BW) basis parameters. The BW basis parameters must be set optimally for the BW system to work without errors and the system to perform efficiently. The recommendations for BW systems are not always the same as those for R/3 systems.
Other terms
Memory Management, EarlyWatch, GoingLive, Release 1.2B, Release 2.0A,
Release 2.0B, Release 2.1C, Release 3.0A, Release 3.0B, Release 3.1
Release 3.5
Reason and Prerequisites
The recommendations for BW systems are not always the same as those for R/3 systems. This note describes the differences between the parameter settings of a BW system and an R/3 system. Therefore, this note supplements Note 103747 for BW systems (Performance 4.0/4.5/4.6: Parameter recommendations). As with the recommendations in Note 103747, the recommendations here are intended as initial settings before you start using the system productively. After you start using the system productively, you must adjust individual parameters as required and adapt them to the actual requirements.
Number and type of work processes
This note does not contain any recommendations about the number and type of work processes. You can receive work processes tailored for your system from the recommended remote services. However, if you have not received any recommendations from the GoingLive services, you have to set up a minimum of six dialog work processes and three batch work processes.
This note is valid only for BW 1.2B, BW 2.0A, BW 2.0B,
BW 2.1C, BW 3.0A, BW 3.0B and BW 3.1, BW 3.5.
For NetWeaver 2004s or BI 7.0, see Note 1044441.
Solution
Support by Support Services *
To ensure that the system performs efficiently after you start using it productively, we recommend you use the support services, for example, the GoingLive check for BW systems or an EarlyWatch contract for BW systems. With a GoingLive check for BW systems, you should schedule two sessions for 4-6 weeks before you start using the system productively and one session 4-6 weeks after you have started using the system productively.
TO AVOID LONG WAITING TIMES FOR A SERVICE SESSION APPOINTMENT, BOOK IN SUFFICIENT TIME BEFORE YOU START USING THE SYSTEM PRODUCTIVELY. TO DO THIS, CONTACT YOUR LOCAL SUPPORT.
This note supplements Note 103747 (Performance 4.0/4.5/4.6: Parameter recommendations) for BW systems. It describes the different parameter settings of a BW system and an R/3 system.
Recommendations given in Note 103747 for R/3 systems that are different for BW systems:
1a. Export/import buffer
BW 1.2B:
This buffer is frequently used in BW systems so the export/import buffer must be set to at least 10 MB. If you work with large hierarchies, you have have to increase the size of this buffer considerably. You should be able to store at least 5,000 objects in the buffer.
rsdb/obj/buffersize 10000 or higher (10 MB)
rsdb/obj/max_objects 5000 or higher (entries)
rsdb/obj/large_object_size 10000 (10 MB)
BW 2.X: The buffer should be set to the size recommended for R/3 4.6 systems (see Note 103747).
BW 3.X: The buffer should be set to a larger size than the buffer for BW 2.X.
rsdb/obj/buffersize 40000 or higher (40 MB)
1b. Export/import buffer SHM
BW 3.X ONLY (OLAP cache):
Parameter name Value Description
rsdb/esm/buffersize_kb 40000 or higher Size of exp/imp SHM buffer (kB)
rsdb/esm/max_objects 10000 Maximum number of objects in buffer
2. Program buffer (abap/buffersize)
Depending on the size of the main memory, the program buffer should be between 200 and 400 MB. Unlike in R/3 Systems, a higher number of program buffer swaps is less important in BW Systems and is often unavoidable since the information stored in the program buffer is significantly less likely to be reused. While the response times of R/3 transactions is only around several hundred milliseconds, the response times of BW queries takes seconds. However, by tuning the program buffer, you can only improve the performance by milliseconds.
Therefore, if the available main memory is limited, you should increase the size of the extended memory. However, the program buffer should not be set lower than 200 MB. If the available main memory is sufficient, the program buffer in BW 2.X/3.X systems should be set to at least 300 MB.
3. Extended Memory
BW users require significantly more extended memory than R/3 users. The size of the extended memory is related to the available main memory but should not be lower than 512 MB.
4. Single Record buffer
BW 2.X & 3.X: The buffer should be set to the size recommended for R/3 4.6 systems (see Note 103747).
Limits for BW 2.X:
See Note 414220 for information about setting the parameter rtbb/max_tables, rtbb/buffer_length.
You must not exceed certain limits.
Limits for BW 3.X:
See Note 480710.
5. Recommendations for the 64-bit R/3 kernel
In addition to the recommendations from Note 146289, set the following parameter specifically for BW:
 em/blocksize_KB 4096
6. Maximum runtime for a work process
Set a higher runtime than is usual for R/3 systems:
rdisp/max_wprun_time 3600
7. Connection to the front end
To avoid connection terminations, set the gw/cpic_timeout parameter to a sufficiently large value:
gw/cpic_timeout 60
8. Further CPIC/RFC settings
 gw/max_conn 2000
 gw/max_overflow_size 25000000
 rdisp/max_comm_entries 2000
 Because of the high RFC load, see the recommendataions from Note 74141.
9. Oracle Database Interface
Set the parameter dbs/ora/array_buf_size to a sufficiently large size to keep the number of array inserts, for example, when you upload data or during the rollup, as low as possible. This improves the performance during insert operations. Depending on the size of the available main memory, set the parameter dbs/ora/array_buf_size to a value of 1000000 (1MB).
dbs/ora/array_buf_size 1000000
10. Internet Communication Manager (ICM) Parameter
icm/host_name_full <fully qualified name>
 You use this parameter to specify
 the fully qualified host name of the
 of the host on which the ICM is
 running. If this parameter is
 not set, the system queries the
 system for the host name.
 With several host names, this
 parameter can override this value.
SAPLOCALHOSTFULL <fully qualified name>
General timeouts:
icm/keep_alive_timeout 3600
 This parameter refers to the
 "keep-alive-feature" of HTTP1.1
rdisp/plugin_auto_logout 3600
 The user context is closed only after
 this time interval
Kernel Release 6.20
icm/server_port_: PROT=<xxxx>,PORT=<xxxx>,TIMEOUT=3600
 Defines keep_alive_timeout per port
 binding
Kernel Release 6.40ff
icm/server_port_: PROT=<xxxx>,PORT=<xxxx>,TIMEOUT=60, PROCTIMEOUT=3600
icm/keep_alive_timeout = 60
Further information:
Note 622629: Procedure when timeouts occur in BW Web Reporting
Note 622130: Timeout problems in BW Web Applications
Note 538405: Composite SAP Note on the SAP Web Dispatcher
11. Notes for configuring the databases
BW and R/3 Systems can differ significantly in terms of the configuration of the database.
The following notes contain recommendations for setting the database in a BW system:
 0632556 Oracle 9.2.0.* databaseparameterization for BW
 0632427 Oracle 8.1.7* database parameterization forBW
 0180605 Oracle database parameter settings for BW
Informix 0114884 Performance Guide: BW 1.2B on Informix
 0181945 Performance guide: BW 2.0X & BW 3.0X
MS SQL Server 0142334 Installation BW 1.2B on MS SQL server
 0209596 Setting up Microsoft SQL Server 2000
DB2 UDB Unix/Windows 0374502 DB6: BW performance: Note overview
 0546262 DB6: Performance on SAP BW 3.0B
DB2 UDB OS/390 0390016 DB2/390: BW: Database settings and
 performance
DB2 UDB AS/400 541508 iSeries: Checking the system parameters for BW
12. Essentials for parameter settings
- Save your old profile before you make any changes. If the instance does not start with the new parameters, you can use the old profile.
- Check all parameter settings before you use them (program sappfpar, in the test system, and so on).
- Take into account limitations due to the architecture of the operating system (for example, shared memory limitations). Errors and terminations may occur if you do not take these limitations into account.
Bear in mind that concrete recommendations for parameter settings using TTC can only be given during a session service. ***********************************************************************
WARNING:
If the settings in the R/3 memory areas (R/3 buffer, R/3 extended memory and so on) are too small, unnecessary performance problems can occur. If the settings are too large, errors can occur when you start the R/3 instance or runtime errors can occur. The optimal settings depend on the hardware (CPU and RAM), the R/3 release and the operating system release.
The Solution Support remote services GoingLive and EarlyWatch provide recommendations tailored to your system.
Header Data
Release Status: Released for Customer
Released on: 25.07.2007 09:50:34
Priority: Recommendations/additional info
Category: Consulting
Primary Component: SV-BO-BI Business Information
Secondary Components: SV-BO Backoffice Service Delivery
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 45 45A 45A
SAP_APPL 46 46A 46A
SAP_BW 20 20B 20B
SAP_BW 21 21C 21C
SAP_BW 30 30A 30B
SAP_BW 310 310 310
SAP_BW 35 350 350
SAP_BW 70 700 700
Related Notes
1013912 - FAQ: Oracle BW performance
923610 - Memory param recommendations for Bank Analyzer 4.0 or higher
688647 - DB6: SAP BW and SAP NetWeaver BI Administration Tasks
624852 - Shared Memory segments 62, 63, 64 and 65 for AIX
618868 - FAQ: Oracle performance
567745 - Composite note BW 3.x performance: DB-specific setting
563688 - SYSTEM_NO_ROLL during the file upload
546262 - DB6:Administration & Performance on SAP BW, SAP SCM, SAP SEM
541508 - iSeries: Checking the system parameters for BW
480710 - Profile parameters for table buffers
414220 - Data corruption possible if rtbb/buffer_length is > 200000
390016 - DB2/390: BW: Database settings and performance
209596 - Setting up Microsoft SQL Server 2000
184905 - Collective note Performance BW 2.0
181945 - Performance guide: BW on Informix
180605 - Oracle database parameter settings for BW
156319 - Collective note performance BW 1.2B
139173 - DB2 UDB: Performance BW 1.2B
103747 - Performance: Parameter recommendations as of Release 4.0
74141 - Resource Management for tRFC and aRFC
Print Selected Notes (PDF)
Attributes
Attribute Value
Transaction codes DB2
Transaction codes KAUM
Transaction codes TRANSAKTIONEN
weitere Komponenten XX-SER-TCC
<div class="urMnu" onkeydown="me.sapUrMapi_PopupMenu_keyDown(window,'popupMenuVersions',event);" onmousemove="me.sapUrMapi_PopupMenu_hoverItem(window,'popupMenuVersions',event);"><table cellpadding="0" cellspacing="0" border="0" id="popupMenuVersions-r" visidx="0" viscnt="10"><thead style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrUp" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','false',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','false',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','false',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr><tbody><tr id="0000000000" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 32 : 25.07.2007 - 18.09.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000031" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000031','Version: 31 : 10.05.2007 - 25.07.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 31 : 10.05.2007 - 25.07.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000030" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000030','Version: 30 : 20.01.2006 - 10.05.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 30 : 20.01.2006 - 10.05.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000029" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000029','Version: 29 : 14.07.2005 - 20.01.2006');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 29 : 14.07.2005 - 20.01.2006</td><td class="urMnuSub"> </td></tr><tr id="0000000028" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000028','Version: 28 : 18.04.2005 - 14.07.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 28 : 18.04.2005 - 14.07.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000027" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000027','Version: 27 : 03.08.2004 - 18.04.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 27 : 03.08.2004 - 18.04.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000026" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 26 : 03.08.2004 - 03.08.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000025" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 25 : 12.03.2004 - 03.08.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000024" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000024','Version: 24 : 29.01.2004 - 12.03.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 24 : 29.01.2004 - 12.03.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000023" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000023','Version: 23 : 18.12.2003 - 29.01.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 23 : 18.12.2003 - 29.01.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000022" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 22 : 24.02.2003 - 18.12.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000021" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000021','Version: 21 : 30.01.2003 - 24.02.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 21 : 30.01.2003 - 24.02.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000020" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 20 : 30.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000019" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000019','Version: 19 : 17.01.2003 - 30.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 19 : 17.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000018" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000018','Version: 18 : 08.10.2002 - 17.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 18 : 08.10.2002 - 17.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000017" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000017','Version: 17 : 26.09.2002 - 08.10.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 17 : 26.09.2002 - 08.10.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000016" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 16 : 26.09.2002 - 26.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000015" class="urMnuRowDsbl" dsbl="true"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 15 : 25.09.2002 - 26.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000014" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000014','Version: 14 : 02.05.2002 - 25.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 14 : 02.05.2002 - 25.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000013" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000013','Version: 13 : 05.07.2001 - 02.05.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 13 : 05.07.2001 - 02.05.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000012" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupMenuVersions:onSelectPopupMenuItem','','0000000012','Version: 12 : 25.05.2001 - 05.07.2001');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 12 : 25.05.2001 - 05.07.2001</td><td class="urMnuSub"> </td></tr><tfoot style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrDwn" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','true',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','true',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupMenuVersions','true',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr></table></div>
<div class="urMnu" onkeydown="me.sapUrMapi_PopupMenu_keyDown(window,'popupitemslevel2_D',event);" onmousemove="me.sapUrMapi_PopupMenu_hoverItem(window,'popupitemslevel2_D',event);"><table cellpadding="0" cellspacing="0" border="0" id="popupitemslevel2_D-r" visidx="0" viscnt="10"><thead style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrUp" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','false',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','false',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','false',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr><tbody><tr id="0000000000" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000000','Version: 32 : 25.07.2007 - 18.09.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 32 : 25.07.2007 - 18.09.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000031" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000031','Version: 31 : 10.05.2007 - 25.07.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 31 : 10.05.2007 - 25.07.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000030" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000030','Version: 30 : 20.01.2006 - 10.05.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 30 : 20.01.2006 - 10.05.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000029" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000029','Version: 29 : 14.07.2005 - 20.01.2006');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 29 : 14.07.2005 - 20.01.2006</td><td class="urMnuSub"> </td></tr><tr id="0000000028" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000028','Version: 28 : 18.04.2005 - 14.07.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 28 : 18.04.2005 - 14.07.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000027" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000027','Version: 27 : 03.08.2004 - 18.04.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 27 : 03.08.2004 - 18.04.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000026" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000026','Version: 26 : 03.08.2004 - 03.08.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 26 : 03.08.2004 - 03.08.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000025" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000025','Version: 25 : 12.03.2004 - 03.08.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 25 : 12.03.2004 - 03.08.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000024" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000024','Version: 24 : 29.01.2004 - 12.03.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 24 : 29.01.2004 - 12.03.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000023" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000023','Version: 23 : 18.12.2003 - 29.01.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 23 : 18.12.2003 - 29.01.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000022" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000022','Version: 22 : 24.02.2003 - 18.12.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 22 : 24.02.2003 - 18.12.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000021" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000021','Version: 21 : 30.01.2003 - 24.02.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 21 : 30.01.2003 - 24.02.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000020" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000020','Version: 20 : 30.01.2003 - 30.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 20 : 30.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000019" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000019','Version: 19 : 17.01.2003 - 30.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 19 : 17.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000018" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000018','Version: 18 : 08.10.2002 - 17.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 18 : 08.10.2002 - 17.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000017" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000017','Version: 17 : 26.09.2002 - 08.10.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 17 : 26.09.2002 - 08.10.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000016" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000016','Version: 16 : 26.09.2002 - 26.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 16 : 26.09.2002 - 26.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000015" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000015','Version: 15 : 25.09.2002 - 26.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 15 : 25.09.2002 - 26.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000014" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000014','Version: 14 : 02.05.2002 - 25.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 14 : 02.05.2002 - 25.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000013" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000013','Version: 13 : 05.07.2001 - 02.05.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 13 : 05.07.2001 - 02.05.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000012" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_D:onSelectPopupMenuItem','','0000000012','Version: 12 : 25.05.2001 - 05.07.2001');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 12 : 25.05.2001 - 05.07.2001</td><td class="urMnuSub"> </td></tr><tfoot style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrDwn" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','true',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','true',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_D','true',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr></table></div>
<div class="urMnu" onkeydown="me.sapUrMapi_PopupMenu_keyDown(window,'popupitemslevel2_E',event);" onmousemove="me.sapUrMapi_PopupMenu_hoverItem(window,'popupitemslevel2_E',event);"><table cellpadding="0" cellspacing="0" border="0" id="popupitemslevel2_E-r" visidx="0" viscnt="10"><thead style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrUp" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','false',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','false',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','false',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr><tbody><tr id="0000000000" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000000','Version: 32 : 25.07.2007 - 18.09.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChkOn"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 32 : 25.07.2007 - 18.09.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000031" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000031','Version: 31 : 10.05.2007 - 25.07.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 31 : 10.05.2007 - 25.07.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000030" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000030','Version: 30 : 20.01.2006 - 10.05.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 30 : 20.01.2006 - 10.05.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000029" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000029','Version: 29 : 14.07.2005 - 20.01.2006');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 29 : 14.07.2005 - 20.01.2006</td><td class="urMnuSub"> </td></tr><tr id="0000000028" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000028','Version: 28 : 18.04.2005 - 14.07.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 28 : 18.04.2005 - 14.07.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000027" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000027','Version: 27 : 03.08.2004 - 18.04.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 27 : 03.08.2004 - 18.04.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000024" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000024','Version: 24 : 29.01.2004 - 12.03.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 24 : 29.01.2004 - 12.03.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000023" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000023','Version: 23 : 18.12.2003 - 29.01.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 23 : 18.12.2003 - 29.01.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000021" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000021','Version: 21 : 30.01.2003 - 24.02.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 21 : 30.01.2003 - 24.02.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000019" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000019','Version: 19 : 17.01.2003 - 30.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 19 : 17.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000018" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000018','Version: 18 : 08.10.2002 - 17.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 18 : 08.10.2002 - 17.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000017" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000017','Version: 17 : 26.09.2002 - 08.10.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 17 : 26.09.2002 - 08.10.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000014" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000014','Version: 14 : 02.05.2002 - 25.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 14 : 02.05.2002 - 25.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000013" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000013','Version: 13 : 05.07.2001 - 02.05.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 13 : 05.07.2001 - 02.05.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000012" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_E:onSelectPopupMenuItem','','0000000012','Version: 12 : 25.05.2001 - 05.07.2001');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 12 : 25.05.2001 - 05.07.2001</td><td class="urMnuSub"> </td></tr><tfoot style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrDwn" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','true',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','true',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_E','true',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr></table></div>
<div class="urMnu" onkeydown="me.sapUrMapi_PopupMenu_keyDown(window,'popupitemslevel2_J',event);" onmousemove="me.sapUrMapi_PopupMenu_hoverItem(window,'popupitemslevel2_J',event);"><table cellpadding="0" cellspacing="0" border="0" id="popupitemslevel2_J-r" visidx="0" viscnt="10"><thead style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrUp" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','false',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','false',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','false',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr><tbody><tr id="0000000000" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000000','Version: 32 : 25.07.2007 - 18.09.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 32 : 25.07.2007 - 18.09.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000031" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000031','Version: 31 : 10.05.2007 - 25.07.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 31 : 10.05.2007 - 25.07.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000030" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000030','Version: 30 : 20.01.2006 - 10.05.2007');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 30 : 20.01.2006 - 10.05.2007</td><td class="urMnuSub"> </td></tr><tr id="0000000029" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000029','Version: 29 : 14.07.2005 - 20.01.2006');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 29 : 14.07.2005 - 20.01.2006</td><td class="urMnuSub"> </td></tr><tr id="0000000028" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000028','Version: 28 : 18.04.2005 - 14.07.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 28 : 18.04.2005 - 14.07.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000027" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000027','Version: 27 : 03.08.2004 - 18.04.2005');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 27 : 03.08.2004 - 18.04.2005</td><td class="urMnuSub"> </td></tr><tr id="0000000024" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000024','Version: 25 : 12.03.2004 - 03.08.2004');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 25 : 12.03.2004 - 03.08.2004</td><td class="urMnuSub"> </td></tr><tr id="0000000021" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000021','Version: 22 : 24.02.2003 - 18.12.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 22 : 24.02.2003 - 18.12.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000019" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000019','Version: 19 : 17.01.2003 - 30.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 19 : 17.01.2003 - 30.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000018" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000018','Version: 18 : 08.10.2002 - 17.01.2003');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 18 : 08.10.2002 - 17.01.2003</td><td class="urMnuSub"> </td></tr><tr id="0000000014" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000014','Version: 14 : 02.05.2002 - 25.09.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 14 : 02.05.2002 - 25.09.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000013" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000013','Version: 13 : 05.07.2001 - 02.05.2002');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 13 : 05.07.2001 - 02.05.2002</td><td class="urMnuSub"> </td></tr><tr id="0000000012" class="urMnuRowOff" onclick="me.htmlbSL(this,78,'popupitemslevel2_J:onSelectPopupMenuItem','','0000000012','Version: 12 : 25.05.2001 - 05.07.2001');;me.sapUrMapi_PopupMenu_hideAll();return false;"><td class="urMnuChk"> </td><td> </td><td class="urMnuTxt" nowrap>Version: 12 : 25.05.2001 - 05.07.2001</td><td class="urMnuSub"> </td></tr><tfoot style="display:block;"><tr class="urMnuScr"><td colspan="4" class="urMnuScrDwn" isscroll="true" onmousedown="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','true',false,event);" onmouseup="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','true',true,event);" onmouseout="me.sapUrMapi_PopupMenu_timeScroll(window,'popupitemslevel2_J','true',true,event);"><img width="1" class="urMnuScrImg" src="1x1"></td></tr></table></div>
German
English
Japanese

OSS NOTE Number required

Hi Gurus,
could you plese provide me the Related OSS NOTE number for the folowing exception .
TSV_TNEW_PAGE_ALLOC_FAILED
No storage space available for extending the internal table.
You attempted to extend an internal table, but the required space was not available .

Hi u can see the copd here
REPORT /rb17/ym_forc_model_ext_new .
*& T Y P E S *
TYPES: BEGIN OF typ_itab_rec.
 INCLUDE STRUCTURE /rb17/ym_mod_new.
TYPES: END OF typ_itab_rec.
table types
TYPES: typ_itab_table TYPE STANDARD TABLE OF typ_itab_rec
 WITH KEY matnr werks .
*& D A T A *
Internal table to store records from database
DATA : g_t_itab TYPE typ_itab_table WITH HEADER LINE .
Internal table to fill datbase
DATA : g_t_jtab TYPE typ_itab_table WITH HEADER LINE .
Work area
DATA : g_r_itab TYPE typ_itab_rec.
DATA : counter TYPE i .
DATA cnt type i value 0.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS : p_vers TYPE vrsio.
SELECTION-SCREEN END OF BLOCK b1.
*& Event START-OF-SELECTION
PERFORM get_data.
PERFORM populate_data.
PERFORM assign_version.
PERFORM update_table.
*& Form get_data
 text
--> p1 text
<-- p2 text
FORM get_data .
REFRESH : g_t_itab[].
SELECT * FROM /rb17/ym_model INTO CORRESPONDING FIELDS OF
 TABLE g_t_itab.
ENDFORM. " get_data
*& Form populate_data
 text
--> p1 text
<-- p2 text
FORM populate_data .
DATA : l_f_bstrf TYPE bstrf,
 l_f_prctr TYPE prctr,
 l_f_maabc TYPE maabc,
 l_f_mfrnr TYPE mfrnr,
 l_f_kondm TYPE kondm,
 l_f_ktgrm TYPE ktgrm,
 l_f_bezek TYPE bezap,
 l_f_lifnr TYPE lifnr.
CLEAR : l_f_bstrf , l_f_prctr , l_f_maabc, l_f_mfrnr,
 l_f_kondm , l_f_ktgrm , l_f_bezek, l_f_lifnr.
CLEAR g_r_itab.
LOOP AT g_t_itab.
 SELECT SINGLE bstrf prctr maabc INTO
 (l_f_bstrf , l_f_prctr , l_f_maabc) FROM marc
 WHERE matnr = g_t_itab-matnr AND
 werks = g_t_itab-werks.
 SELECT SINGLE mfrnr INTO l_f_mfrnr FROM mara
 WHERE matnr = g_t_itab-matnr.
 SELECT SINGLE kondm ktgrm INTO (l_f_kondm , l_f_ktgrm) FROM mvke
 WHERE matnr = g_t_itab-matnr.
 SELECT SINGLE bezek INTO l_f_bezek FROM t25b1
 WHERE wwz02 = g_t_itab-prmgr.
 SELECT SINGLE lifnr INTO l_f_lifnr FROM eord
 WHERE matnr = g_t_itab-matnr AND
 werks = g_t_itab-werks AND
 flifn = 'X'.
 IF sy-subrc NE 0.
 SELECT SINGLE lifnr INTO l_f_lifnr FROM eord
 WHERE matnr = g_t_itab-matnr AND
 werks = g_t_itab-werks .
 ENDIF.
*get backorder value
 PERFORM get_backorders USING g_t_itab-matnr
 CHANGING g_t_itab-backord.
 g_r_itab-bstrf = l_f_bstrf.
 g_r_itab-prctr = l_f_prctr.
 g_r_itab-maabc = l_f_maabc.
 g_r_itab-mfrnr = l_f_mfrnr.
 g_r_itab-kondm = l_f_kondm.
 g_r_itab-ktgrm = l_f_ktgrm.
 g_r_itab-bezek = l_f_bezek.
 g_r_itab-lifnr = l_f_lifnr.
*set version = 1 for new rows.
 g_r_itab-version = 1.
 MODIFY g_t_itab FROM g_r_itab TRANSPORTING bstrf mfrnr prctr kondm
 ktgrm lifnr bezek maabc
 backord version.
ENDLOOP.
SORT g_t_itab BY spmon vrsio bukrs matnr version.
ENDFORM. " populate_data
*& Form get_backorders
 text
 -->P_G_T_ITAB_MATNR text
 <--P_G_T_ITAB_BACKORD text
FORM get_backorders USING p_g_t_itab_matnr TYPE matnr
 CHANGING p_g_t_itab_backord TYPE netwr_ap.
TYPES: BEGIN OF typ_outord.
 INCLUDE STRUCTURE /rb17/yv_outord.
TYPES: END OF typ_outord.
DATA: t_outord TYPE TABLE OF typ_outord WITH HEADER LINE.
REFRESH: t_outord.
first load outstanding orders for out materials from
nightly extract of data (run from /rb17/yv_outstanding_orders)
SELECT * FROM /rb17/yv_outord INTO TABLE t_outord
 WHERE matnr = p_g_t_itab_matnr.
accumulate all past due orders
LOOP AT t_outord .
 IF t_outord-edatu < t_outord-wadat "backorder
 OR t_outord-edatu < sy-datum.
 IF t_outord-bmeng > 0.
 ADD t_outord-bmeng TO p_g_t_itab_backord. "+ confirmed
 ELSE.
 ADD t_outord-kwmeng TO p_g_t_itab_backord. "+ ordered
 ENDIF.
 SUBTRACT t_outord-lfimg FROM p_g_t_itab_backord. "- delivered
 ENDIF.
ENDLOOP.
ENDFORM. " get_backorders
*& Form update_table
 text
--> p1 text
<-- p2 text
FORM update_table .
DELETE FROM /rb17/ym_mod_new.
MODIFY /rb17/ym_mod_new FROM TABLE g_t_jtab .
COMMIT WORK.
ENDFORM. " update_table
*& Form assign_version
 text
--> p1 text
<-- p2 text
FORM assign_version .
delete records with version = no of versions given by user.
LOOP AT g_t_itab .
 IF g_t_itab-version EQ p_vers.
 DELETE g_t_itab.
 CONTINUE.
 ENDIF.
ENDLOOP.
Changing versions and populating final internal table
LOOP AT g_t_itab .
 counter = p_vers - 1 .
 DO counter TIMES .
 MOVE-CORRESPONDING g_t_itab TO g_r_itab.
 g_r_itab-version = counter + 1 .
 APPEND g_r_itab TO g_t_jtab .
 counter = counter - 1.
 CLEAR g_r_itab.
 ENDDO .
ENDLOOP.
SORT g_t_itab BY spmon vrsio bukrs matnr version.
ENDFORM. " assign_version

Can anyone tell me where to see OSS notes

Hi
Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.

www.service.sap.com
SAP Support Portal
Quick Lnks :
Search for OSS notes.
You need to have a login..its not free.
After login - Help & Support - Search for SAP notes

Anyws here is the note
Summary
Symptom
You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
This note should help you to analyze this problem.
Other terms
2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
Non-cumulative InfoCubes, stock key figures, stock, stocks,
RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
data consistency, healthcare, health service
Reason and Prerequisites
This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
Solution
Contents
1. Release strategy
a) General information
b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
c) Recommended objects for BW Releases 2.0B and 2.1C
d) Obsolete objects
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
2. Sources of information
a) BW technology
SAP BW online documentation
"How to" documents
b) Business Content
Online documentation for BI Content
Extraction Documentation:
"How to" documents
Plug-In information
3. Extracting non-cumulative data from R/3
a) Explanations for the extraction
b) Known errors
Stocks (2LIS_40_S278/2LIS_03_BX)
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
Industry-specific notes
4. Technical information regarding non-cumulative info cubes in BW
a) Warehouse Management
b) Queries
c) Update rules
d) Known errors
5. Stock Analyses in BW
a) Explanations on data flow
b) Known errors
c) Tips and tricks
6. Performance
1. Release strategy
Use the following objects depending on your BW and R/3 or plug-in releases:
a) General information
The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
For information about the general support for DataSources based on information structures, see also Note 543002.
As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
The 0IC_C03 InfoCube is available as of Release 3.0B.
b) Recommended objects for BW Release 3.0B and higher
InfoCube: 0IC_C03 (Material movements)
InfoSources and update rules:
2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
c) Recommended objects for BW Releases 2.0B and 2.1C
InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
 - available for Release 2.1C as ofSupport Package 22
 2LIS_03_BF (movements)
 2LIS_03_UM (revaluations)
If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
d) Obsolete objects
If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
For more information, see Note 591063.
2. Sources of information
The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
a) BW technology
This area contains documentation on the technical mapping of stock analyses in SAP BW.
Online documentation SAP BW (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration -> SAP BW
i Stocks
 -> BI Platform -> OLAP
 -> Performance Optimization -> Stocks
ii Validity Table
 -> Data Warehousing
 -> Administrator Workbench -> Modeling -> InfoCube
 -> Additional functions for InfoCube maintenance
 -> Stock Parameter Maintenance
iii Compression
 -> Data Warehousing
 -> Administrator Workbench -> Data Warehouse Management
 -> Process Management
 -> Managing Data Targets
 -> Managing InfoCubes -> InfoCube Compression
iv Aggregation
 -> Data Warehousing
 -> Administrator Workbench -> Modeling
 -> InfoObject -> Create InfoObject: Key Figure
 -> Aggregation v Exception Aggregation
 -> BI Platform -> OLAP
 -> Special OLAP Functions and Services
 -> Aggregation
 -> Scenarios for the Use of an Exception Aggregation
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> In the information index: N ("Non-cumulatives") ->
"Non-Cumulative Values 3.x (ppt)"
b) Business Content
This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
Online documentation for BI Content (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration: BI Content
-> BI Content -> Supply Chain Management
-> Supply Chain Performance Management -> Inventory Management
Documentation for extraction (OLTP system)
-> Transaction SBIW
-> Business Information Warehouse
-> Settings for application-specific DataSources
-> Logistics
Here you will find the relevant documentation for each of the relevant nodes.
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: N ("Non-cumulatives") ->
"How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
Plug-In information
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Extractors - Plug-in
3. Extracting non-cumulative data from R/3
This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
a) Explanations for the extraction
Determining transaction keys
Note 492828
Determining the component
When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
The "GETSYSDEF" report provides the system setting.
Creating non-cumulative relevance
In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
Logistics data extraction: Customizing Cockpit (transaction LBWE)
You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
Generic extraction of stocks
This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
User exit (SAP enhancement RSAP0001)
Note 413807
Update methods/extract structures/XPRAs
i Update methods (V3 update, DeltaQueue, and so on).
Notes 380078, 396647, 486784 and 505700.
For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
A change to "Queued Delta" may occur.
For performance reasons, you should not select "Direct Delta".
ii Changes to extract structures/XPRAs
Notes 328181, 489259, 511657 and 566917.
If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
Possible reason:
XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
b) Known errors
Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
i Rounding error/valuation at company code level
 Notes 663681 and 762219
ii Project stocks
 Note 535657
iii Valuated sales order stocks or project stocks
 Notes 487043, 616119, 674351 and 756151
iv Vendor consignment stocks
 Notes 585619 and 726485
v Special stocks for customers/vendors
 Note 533682
vi Valuation class
 Note 684789
vii Stock in transit
 Notes 767786 and 898231
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
i Delta ability/procedure
 Notes 385703 and 581778
ii Update methods (V3 update, delta queue, qRFC and so on)
 Notes 339691, 444261, 498484 and 631562
iii Missing BW derivation (component,
 transaction key, and so on)
 Notes 315880 and 353042
 Caution: You MUST read these notes
 BEFORE you transfer data to the BW system.
iv Movements (2LIS_03_BF)
 - Returnable packaging with customer
 Notes 512597 and 530730
 - Vendor consignment
 Notes 585139 and 607710
 - Project stocks
 Note 522770
 - Stock transfers
 Notes 399929, 557378 and 628090 (stock in transit/
 valuation type)
 - Purchase orders with account assignment (consumptions)
 Notes 587320 and 629726 (non-valuated materials,
 see also Notes 752607 and 790506)
 - Batches
 Notes 445632 and 685450
 - Incorrect stock type
 Notes 438649 and 451355
 - Customer consignment
 Note 563342
 - Incorrect / missing valuation class
 Notes 735425, 747581 and 770858
 - Returns (movement types 122/123)
 Notes 741396 and 763424
 - Profit center
 Note 769660
 - Subsequent adjustments
Note 822396
v Revaluations (2LIS_03_UM)
 - Incorrect update because the
 BSTAUS and BSTTYP fields are missing
 Notes 494288 and 675610
 - Missing BW derivation of characteristics with settlement ofrequests
 Notes 523298 and 747361
 - External display of the WBS element does not exist
 Note 512611
 - Incorrect transaction key during setup
 Note 587241
 - Incorrect sign
 Note 587283
 - Duplicate document for MR22
 Note 587304
 - Incorrect/missing document number
 Notes 489290, 500825, 507958, 521046, 619482,
 667534, 739050, 839711, 845307, 856669 and
 864630
 - The BUZEI field is not filled
 Note 599731
 - Currency field not filled
 Note 612131
 - Returns (movement types 122/123)
 Note 715176
 - Reconstruction report RMCBNERP
 Note 735209
 - Missing valuation class
 Note 837052
vi Master data (0STOCKTYPE/0STOCKCAT)
 Note 766954
 - 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
 Note 907195
Industry-specific notes
i IS Retail
- Revaluation at retail (2LIS_40_REVAL)
Notes 533577 and 600460
- Miscellaneous
Note 841878
ii IS Oil/IS Mine
- G/L quantity for two-step stock transfer procedure
Notes 608744, 608975 and 629320
4. Technical information regarding non-cumulative info cubes in BW
In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
a) Warehouse Management
Validity table: Notes 360249 and 534865
Selective deletion: Note 510680
Aggregates: Note 456359
ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
747037, 752492/782314 and 773823
DataMart/Open Hub capability: Notes 375098, 566145 and 566762
Compression (updating the stock marker)
->>> ESSENTIAL INFORMATION <<<-
You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
For example:
"START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
"refpoint update" or "no refpoint update" provides the relevant information.
See Notes 613701 and 639253 if you are using Oracle 9.
Also see Notes 643687 and 655798.
For a BW system with several application servers, see also Note 834829.
->>> ESSENTIAL INFORMATION <<<-
b) Queries
-> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
Slow-moving item/slow seller reports: Note 541559
A How to document is also available:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
c) Update rules
The following special features are provided for updating in non-cumulative cubes:
The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
Only receipt key figures are provided for updating from the InfoSource with the stocks.
The issue and receipt key figures are provided for updating from the InfoSource with movements.
Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
d) Known errors
Warehouse Management
i Loading data
 Notes 534865 and 529610
ii MultiCube/MultiProvider
 Note 435227
iii Compression (updating the stock markers)
 Notes 613064, 613701 and 615349
iv Updating
 Note 574341
Queries
i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
and 0FISCYEAR)
 Note 490067
ii Exception aggregations
 Notes 145630 and 607608
iii No/multiple time restrictions
 Note 388983
5. Stock Analyses in BW
This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
a) Explanations on data flow
See the How to paper from Section 2 b)
"How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
You will find further information on the SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Business Content
-> SAP Supply Chain Management
-> Supply Chain Performance Management
-> In the navigation area on the left: Related Topics
-> Business Content
-> Inventory Management.
b) Known errors
0IC_C03
Notes 637927, 655798, 668085 and 710404
0IC_MC01
Note 664520
Queries
Notes 534429, 630034 and 676960
c) Tips and tricks
Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Realize summarized display of stock values on storage"
Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
Individual analysis of revaluations
After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
Incorrect results if quantity key figures and value key figures are analyzed together.
For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
Enhancing the 0IC_C03 InfoCube with additional characteristics
These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
The following enhancements are possible:
1. Valuation type (0VAL_TYPE)
Source field from 2LIS_03_BX/BF: BWTAR
2. Company code (0COMP_CODE)
Source field from 2LIS_03_BF/UM: BUKRS
3. Valuation area (0ID_VALAREA)
Source field from 2LIS_03_BX/BF/UM: BWKEY
4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
Source field from 2LIS_03_BX/BF/UM: LIFNR
This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
5. Customer (0CUSTOMER) - for consignment stocks at customer
Source field from 2LIS_03_BX/BF/UM: KUNNR
6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
7. Project number (0WBS_ELEMT) - for project stocks
Source field from 2LIS_03_BX/BF: PS_PSP_PNR
8. Evaluation class (0VAL_CLASS)
Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
Enhancement possibilities for 2LIS_03_BX:
Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
Only SAP can enhance this DataSource (Note 684789).
Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
Changing the exception-aggregation of the stock key figures
There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
-> Create a new calculated key figure.
-> Drag the relevant basic key figure to the formula area.
-> Choose "OK".
-> In the next window, choose "Extend >>".
-> Then, maintain the required exception aggregation and the reference characteristic.
Mapping FIFO logic
The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
Unexpected or negative stock values due to FI document summarization
If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
Options for the R/3 and BW data verification/consistency check
TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
With Note 766622 you can also create a LOG file for the extraction.
Archiving
See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: A ("Archiving")
MultiProvider and non-cumulative key figures
Note 690475
Displaying the contents of the InfoCube with TAC "LISTCUBE"
Note 629451
Snapshot scenario
The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
Validity period of stocks
You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
Evaluations of cross-company code stock transfers.
Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
0IC_C03 data modeling
Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
- Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
- Based on stock instance/type, you can then limit the query to the special stock
- Advantage: Uses less database space
- Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
Inventory management and ODS
ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
In this connection, you should use the ODS technology only for:
- Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
- The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
Posting to a prior period and postings to the future
If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
-> Postings to a prior period are selected by mistake.
-> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
Consumption key figures in 0IC_C03 (the same as LIS reports)
See Note 804781.
Avoiding data inconsistencies, HASH solution.
See Note 838050 for more information.
Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
Suppressing the display of the previous period in the BEx Web Analyzer.
See Note 623944.
6. Performance
a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
Notes 409641, 417307, 419465, 548845 and 589997
b) Extraction 2LIS_03_BX
The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_LIN_ALLOC_FAILED
You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
This is no longer required as of Note 823951 (for more information, see Note 655798).
c) Extraction 2LIS_03_UM
Notes 537235 and 585750
d) Extraction 2LIS_03_BF
Note 454267
e) Warehouse
Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
f) Queries
Notes 419490 and 784682
Message was edited by:
 Jr Roberto

Pdf form created in Acrobat 9 Pro Extended does not function properly when viewed by Reader

Hello all-
I have created a form in Acrobat 9 Pro Extended and have an issue because when others view the form in Adobe Reader some of the functions do not work- such as the attach a file button I created, or the save, print buttons (all are execute a menu item). These work on my Acrobat 9 Pro Extended but not on Reader.
I have tried saving many different versions- with security (password) and made sure to allow printing and commenting, editing, digital signatures etc...
Without any security...
Even tried extending features in Adobe Reader!
The response from others is that it all works, except the ATTACH A FILE button- when they click on it it compresses, but, nothing happens!
I don't know what else to do! (I guess people could just attach things to the e-mail that is generated from the submit button, but worried people might forget at that step once they are past that section on the form and they jump to email to submit).
Help please!
A.

I've already extended the rights and made sure to save to activate that... as well as password protected the docs etc... still nothing...
I am aware that those with Basic Adobe Reader need rights extended to be able to use functions available to Adobe Pro.

"Extended" is not showing in the slash screen of PS Cs6

Recently i had downloaded trail version of PS Cs6 extended..!!
but i was amazed to see that the term EXTENDED is not showing is the splash sceen, and even the splash screen is also different t :\ even 3d menu don't appears..??
What might be the reason..??
Here is the System info provided by ps..!!
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1
System architecture: AMD CPU Family:15, Model:6, Stepping:2 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 2
Processor speed: 2812 MHz
Built-in memory: 2431 MB
Free memory: 544 MB
Memory available to Photoshop: 1976 MB
Memory used by Photoshop: 60 %
Image tile size: 132K
Image cache levels: 4
OpenGL Drawing: Disabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: False.
OpenGL Allow Advanced Mode: False.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce 7025 / nForce 630a/PCI/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 900, right: 1600
Video Card Number: 1
Video Card: NVIDIA GeForce 7025 / NVIDIA nForce 630a
OpenCL Unavailable
Driver Version: 8.17.12.5896
Driver Date: 20100709000000.000000-000
Video Card Driver: nvd3dumx.dll,nvd3dum
Video Mode: 1600 x 900 x 4294967296 colors
Video Card Caption: NVIDIA GeForce 7025 / NVIDIA nForce 630a
Video Card Memory: 128 MB
Video Rect Texture Size: 4096
Serial number: 92628701192123445467
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Tuhin\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
F:\, 138.6G, 21.9G free
E:\, 136.7G, 18.2G free
D:\, 146.5G, 80.5G free
C:\, 43.9G, 15.0G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Collada 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Difference Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Embed Watermark 4.0
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Measurement Core 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mezzotint 13.0
   MMXCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Picture Package Filter 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Sumi-e 13.0
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   Underpainting 13.0
   Vanishing Point 13.0
   Variations 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   WIA Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

I also don't know why is this so confusing. I can't tell what I have.
The About screen is the same. No 3D menu, but if you go to "menus" properties, #D is under Panel Menus like it should be available.
During download is was also confusing, because in one place it just said CS6 the other it said extended.
System info should tell us what is going on.
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x32
Operating System: Windows Vista 32-bit
Version: 6.0 Service Pack 2
System architecture: Intel CPU Family:6, Model:15, Stepping:11 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 4
Processor speed: 2394 MHz
Built-in memory: 3325 MB
Free memory: 837 MB
Memory available to Photoshop: 1675 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce 8800 GT/PCIe/SSE2

OSS note 506603 What is it And where can I get it?

Hello,
I am trying to create my form with a SAP Table wizard connection, when I try to use the Table wizard I got the error: "No such interface supported". I can see in a lot of comments the solution is on OSS note 506603. I was trying to find this patch in the sdn site but I could not find it. I am not sure if it is a document, an exe file, a dll,,, and when I see the same question asking where to get the OSS note 506603 there is no answer, could somebody help me telling me what is this and where can I get the patch? I would really appreciate it.
Many thanks.

Hi Eden,
How are you doing ?
OSS note is the older nomenclature for what is now SAP Notes.
They are available at :
http://service.sap.com/notes
you will need a service marketplace user id to log on.
alternatively, if you do not have access to service.marketplace.
send me an email [view my business card], i will reply with the patch. it is a few hundred kb.
with respect,
amit
the note number 506603 :-
Summary
Symptom
Additional information for SAP.Net Connector that was not included in the guide.
Other terms
SAP .NET Connector, Proxy Wizard
Solution
SAP.NET Connector Version 1.0 has been available since Nov 21, 2002. You can download the software from http://service.sap.com/connectors.
Version 2.0 is also available. Use only the new version for new developments.
Report any problems with the SAP.NET Connector under the components:
BC-MID-CON-DNW for problems with the .NET Proxy Wizard for Visual Studio.NET.
BC-MID-CON-DNC for problems with Communication Runtime.
Known problems
1. The Proxy Wizard terminates with the error message "Exception caught in method createFunction for DD_GET_UCLEN Reason: null".
This is caused by a missing function module, which can be installed as described in Note 580834.
2. Corrections for SAP.NET Connector 1.0
The updated version corrects various problems that have been noted during the interim period. You can download it from http://service.sap.com/connectors. To install this version, see the "Release Notes" file. For SAP.NET Connect 1.x, the newest patch-version is called "1.0.3".
3. Corrections for SAP.NET Connector 2.0
For Visual Studio Integration (Design Time) following problems have occurred:
For proxies with several functions, the following runtime error can occur under certain circumstances: "Method xyz can not be reflected." The cause is a combination of an error in the .NET framework and the way in which the proxy generator uses XML-attributes.
The SAP wizard table does not work. Existing tables are not recognized.
Both problems are solved by the patch attached to this note. Stop all instances of Visual Studio and unpack the ZIP file into the "%Program Files%\Microsoft Visual Studio .NET 2003/Common7/IDE" directory, whereby the "SAP.Connector.Design.DLL" file is replaced.
Header Data
Release Status: Released for Customer
Released on: 10.12.2004 16:40:26
Priority: Recommendations/additional info
Category: Installation information
Primary Component: BC-OP-NET-NCO SAP .Net Connector
Secondary Components: BC-OP-NET-VS Visual Studio .Net Connector Wizard
Message was edited by:
amit chawathe

CS5: Could not complete your request because the file is not compatible with this version of Photosh

After several hours creating a PSD file in Photoshop CS5 I attempted to revert some changes and got this error "Could not complete your request because the file is not compatible with this version of Photoshop".
I closed the file and restarted Photoshop and still get this error.
I restarted the computer and still get this error. Now my hours of work are WASTED!
This file was created using Photoshop CS5 Extended and was never in any other software.
Details:
Mac Photoshop CS5 (12.0 running in 32 bit mode)
File had a video layer (h.264)
MaxBook Pro 2.8Ghz
OSX 10.6.3

I was able to open the file in Photoshop CS2 and all layers were intact. PS CS2 gave me the message: "A layer is corrupt and will be discarded." Turns out that was the video layer. The file itself was fine and I am again working on it in PS CS5.
Which leads me to ask: If a video layer gets corrupted why can't PS CS5 open it?
PS CS2 had no problem opening the file, it just flatteded the video layer - it even kept the current key frame.
Additional info: Just before the file went bad I made a level adjustment to the video layer and set a keyframe in the animation panel. Then I saved and got the error "Could not complete your request because the file is not compatible with this version of Photosh' in Photoshop Macintosh". Also the source H.264 video file appears to be fine, it's only a 5 second clip and it play fine in every app - even PS CS5.

File Not Compatible With This Version

I opened and created various files today, and after saving and trying to reopen I get this error:
"Could not complete your request because the file is not compatible with this version of Photoshop."
One of the same files opened just fine earlier, and after opening and making small changes to adjustment layers and resaving, I encountered this error.
I did some searching, and all the causes seem to be related to using large files, Network Storage and Norton Anti-Virus. However, my files are under 2 gb, created locally (not on a Network Drive) on a machine that does NOT have Norton Anti-Virus. Hard drive was replaced on this machine in the last 3 weeks, so it's unlikely that there's an issue with that.
Any other possible explanations? All of the posts I've seen on this topic seem to be related to Smart Object and/or Placed Photo/Video layers. Perhaps it is a Photoshop glitch related to certain types of Smart Objects / Placed Photo/Video layers?
Running:
MacBook Pro Mid-2010
Mac OS X 10.6.4
Adobe Photoshop CS5 Extended Version 12.0.1
8 gb RAM
341 gb free space
Intel HD Graphics & NVIDIA GeForce GT 330M
Thanks!

What you can try..
Create a blank doucument in photoshop .
Try to place the file on that by Goint to File -> Place .
It works if its not a multi layered file.
- Vishal

How to check the OSS note in SAP Client system ?

Hi all
I just have a small question ... how do we check whether an OSS note is applied in the SAP client System or not ?
Please let me know..
Thanks
Mallikarjun

Hi
1) One way is checking the version and support pack applied.I.e,
On the main SAP screen > Systems > Status > Check details of the "Component version".
2) STMS > Double click on the system you need to check > Check the status of your request.
Nadini

Extend OSS note 561593 to SAP_APPL version 617.

Similar Messages

Maybe you are looking for