OSS notes patching

Hi,
I have a series of notes to patch. Some are prerequisites of each other and some involves adding include files to the system. We have decided against using a support package and have decided to patch one note at a time, in the correct order.
Let's say I have patched 2 dependent notes and found that the second note is causing problems. Will I be able to un-implement the 2 notes?
Is it true that once transported to QAS or PROD, I will not be able to un-implement?
Does anyone foresee any problems? Any advice is appreciated and will be rewarded with points. Thanks.

Hi,
Please try these.
1. Go to transaction SNOTE
2. Click on SAP Note Browser
3. Enter OSS Note no. in "SAP Note Number"
4. Execute
5. Highlight the OSS Note
6. Click on Reset SAP Note Implementation.
7. Create transport request and transport to QA and PROD.
Regards,
Ferry Lianto

Similar Messages

OSS Note Patch Implemented?

Hi, if I found an OSS Note which is related to the issue/problem I'm facing. How can I tell if this OSS note is already being applied to my system? Could you provide the detailed steps on how I can check this?
<<Removed>>
Edited by: Matt on Sep 30, 2010 2:54 PM - please do not offer or ask for points

Hi,
If you find that an OSS note is related to the problem that you are facing, you can do some preliminary checks from your end before final check by BASIS team.
In the SAP note, it will give below information.
Affected Releases
Software Component Release From Release To Release And subsequent
SAP_APPL 46C 46C 46C
If your system release is greater than the affected to release, i.e. ECC6.0 then this note may not be applicable to you.
Along with it, there will be information as to in which support package, correction is provided. Check with BASIS team to see if your system is on lower release than the one where correction was provided. If that is the case, then you can apply this note.

OSS note containing fixes for ITS 6.20 patch 19

What is the OSS note that tells of the fixes for patch 19?
Thanks,
Jin Bae

Hello John,
Note 491781 is currently being translated from German to English and should be available in English shortly. If you have a specific note you are looking for then you could also check that note to see if it has been updated with the corrected patch number for ITS.
Edgar

Not able to find proper OSS note for an issue araised in patching

Hi All,
Our client is having ECC 6.0 system and recently done patching. there is an error occuring after patching in a standard program.
How to find the OSS note available if any for the same? i am searching in service market place with search term as the syntax error what I am getting while activating the program but didn't find any useful information.
please help me in this regard.

Hi
I have searched on the description of the systax error I am getting, but not found any clue.
Please find below the program anme and description of the error message I am getting. It looks like the problem is with a standard class corresponding to it.
Program Name: RFFOGB_T
Syntax error:
Method "WRITE_LOG_ENTRY" is not declared or inherited in class "CL_SWF_WFM_PARALLEL_SECTION".
Your inputs are very much helpful.

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

SAP Notes/ Patches.

Hi All,
I just want to have idea about SAP notes patches.
These patches are applied by BASIS guy but what is role of functional consultant regarding SAP HR notes.
Please provide me a clear idea about patches.
Regards
Priya

It is the reponsibility of the Functional Consultant to
1) analyse the contents of all the notes contained in the patches - service.sap.com has detailed information on every single note,
2) identify any potent impact on existing processes.
3) Several Notes have side effects, already identified by SAP, and further notes issued to correct these side effects. This information should be available for most cases in service.sap.com. Be aware and esnure all related notes are applied in the right sequence.
4) SOme notes may require manual changes to table, changes directly to each client etc, get an overview of them, and ensure you have planned time for doing this.
5) Design a detailed regression testing plan based on the impacts identified i.e if the note is touching a specific process, test it to ensure it has'nt changed - Also identify a few critical processes, that you will test anyway, whether or not they are touched by the notes/paatches
6) Carry out regression testing in all clients (except production of course - carry out some sense checks in production)
The above applies to whole sale application of patches such as Annual Legal Changes, Quarterly Hot Patch updates etc. However the general approach holds true even for applying a single OSS note.
Hope this helps.

OSS note and SAP Note

Dear experts
Can Anyone kindly clear me the difference between
1.OSS note and SAP Note.
2.SAP Patch and Support Packages.
Thanx in advance
Regards
G.Reddy.

OSS Note and SAP Note are the same thing.
Support Package / Support Package Stack refers to a group of corrections and/or enahcnements which include a group of OSS Notes, and changes to multiple components that SAP has tested as a group and recommends be installed together.
I think Patch may be a little more ambigous. For some, they might mean Support Package when they use the term Patch, or maybe even an OSS Note. SAP also refers to updates to some components as Patches, e.g. they release database patches, and with BW, the BW SAPGUI Addon is also sometimes referred to as the Front End Patch.

How to retire/archive/status a released workbench transport for an OSS note

My Question: Is there a best practice for the "retiring" or "archiving" or "statusing" of released workbench transports for OSS notes that have been imported into the quality environment, but should never be imported into the production environment?
For example an OSS note is applied and imported into QS1, but then a CRT Hotpack is applied as an entire patch upgrade, so that the prior individual transport is no longer needed. Best Business practice indicates to not delete a released transport, but unless there is a way to permanently segregate them from the remaining legitimately viable transports, there is always a risk that the "stale" code could inadvertently slip through thus overwriting good code.

Hello.
Well, you have confirmed what I suspected when I read the descriptions - wrong forum.
I chuckled and couldn't stop a broad smile from creeping across my face when I read your response though: "the old BASIS type questions". I knew we were a bit behind the times here; you have definitely confirmed this suspicion.
Thank you again. I'll try another search of the OSS notes or put in a customer message just for the heck of it.

Is there any OSS note for this DTP failure???

I have loading from DSO to open hub...using DTP.(BI 7 system).It fails frequently..can anybody suggest me some patches needed for this....I have got manual solution..but if somebody..give me OSS note etc..then it will be great help...
regards,
Neo

Neo,
What is your patch / SP level and also what is the error you get - without that no one can get you any Notes specific to your issue...
Arun

OSS note 1060406

Can anyone please pull up OSS note 1060406 for me..thanks.

Summary
Symptom
You execute a (Microsoft Excel) workbook in BEx Analyzer 7.0. The system displays message BRAIN 605 "The requested query &2/&1 does not exist on the current server", even though the query does exist.
Other terms
InfoCube, query, workbook,
Reason and Prerequisites
This problem is caused by a program error.
The error occurs in BEx Analyzer Version 7.0 only.
Solution
SAP NetWeaver 7.0 BI
Import Support Package 15 for SAP NetWeaver 7.0 BI (BI Patch 15 or SAPKW70015) into your BI system. The Support Package is available once Note 991095 "SAPBINews BI7.0 Support Package 15", which describes this Support Package in more detail, has been released for customers.
In urgent cases, you can implement the correction instructions as an advance correction.
You must first read Note 875986, which provides information about transaction SNOTE.
To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".

OSS Notes Please

Dear Gurus,
Can anyone send me the following OSS notes if u have. 567747, 130253 and 417307. Your kind help will be definitely awarded.
My mail ID is [email protected]
Best Regards
Mohan Kumar
Message was edited by: mohan kumar

hi Mohan,
i think you will need to have access to oss yourself,
note 567747 is composite one that contains several notes.
sent to you mail ...
130253
Symptom
Uploading transaction data to BW takes too long
Other terms
Business Warehouse, data upload, batch upload, transaction data upload,
performance, runtime, data load, SPLIT_PARTITION_FAILED ORA00054
Reason and Prerequisites
Loading data from a mySAP system (for example, R/3) or from a file takes a very long time.
Solution
The following tips are a general check list to make the mass data upload to the Business Warehouse (BW) System as efficient as possible.
Tip 1:
Check the parameter settings of the database as described in composite Note 567745.
Check the basis parameter settings of the system.
Note 192658 Setting basis parameters for BW Systems
See the following composite notes:
Note 567747 Composite note BW 3.x performance: Extraction & loading
Note 567746 Composite note BW 3.x performance: Query & Web applications
Tip 2:
Import the latest BW Support Package and the latest kernel patch into your system.
Tip 3:
Before you upload the transaction data you should make sure that ALL relating master data has been loaded to your system. If no master has been loaded yet, the upload may take up to 100 percent longer because in this case, the system must retrieve master data IDs for the characteristic attributes and it must add new records to the master data tables.
Tip 4:
If possible, always use TRFC (PSA) as the transfer method instead of
IDocs. If you (have to) use IDocs, keep the number of data IDocs as low
as possible. We recommend an IDoc size of between 10000 (Informix) and 50000 (Oracle, MS SQL Server).
To upload from a file, set this value in Transaction RSCUSTV6.
To upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
Tip 5:
If possible, load the data from a file on the application server and not from the client workstation as this reduces the network load. This also allows you to load in batch.
Tip 6:
If possible, use a fixed record length when you load data from a file (ASCII file). For a CSV file, the system only carries out the converison to a fixed record length during the loading process.
Tip 7:
When you load large data quantities from a file, we recommend that you split the file into several parts. We recommend using as many files of the same size as there are CPUs. You can then load these files simultaneously to the BW system in several requests. To do this, you require a fast RAID.
Tip 8:
When you load large quantities of data in InfoCubes, you should delete
the secodary indexes before the loading process and then recreate them afterwards if the following applies: The number of the records that are loaded is big in comparison to the number of records that already exist in the (uncompressed) F fact table. For non-transactional InfoCubes, you must delete the indexes to be able to carry out parallel loading.
Tip 9:
When you load large quantities of data in an InfoCube, the number range buffer should be increased for the dimensions that are likely to have a high number of data sets.
To do this, proceed as follows. Use function module RSD_CUBE_GET to find the object name of the dimension that is likely to have a high number of data sets.
Function module settings:
I_INFOCUBE = 'Infocube name'
I_OBJVERS = 'A'
I_BYPASS_BUFFER = 'X'
The numbers for the dimensions are then contained in table 'E_T_DIME', column 'NUMBRANR'. If you enter 'BID' before this number, you get the relevant number range (for example BID0000053).
You can use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges for the dimensions used in BW if you enter BID*. You can use the object name that was determined beforehand to find the required number range.
By double-clicking this line, you get to the number range maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
!! Never buffer the number range for the package dimension !!
Tip 10:
When you load large quantities of data, you should increase the number
range buffer for the info objects that are likely to have a high number of data sets. To do this, proceed as follows:
Use function module RSD_IOBJ_GET to find the number range name of the info object that is likely to have a high number of data sets.
Function module settings:
I_IOBJNM = 'Info object name'
I_OBJVERS = 'A'
I_BYPASS_BUFFER = 'X'
The number for the info object is in table 'E_S_VIOBJ', column 'NUMBRANR'. Enter 'BIM' in front of this number to get the required number range (for example BIM0000053).
Use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges used for the info objects in BW by entering BIM*. By entering the object name determined beforehand you can find the desired number range.
By double-clicking this line you get to the number range object maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
!! Never buffer the number range object for the characteristic 0REQUEST!!
417307
Symptom
Performance load is too high/not justifiable during data load.
Customizing settings via extractors IMG path (Transaction SBIW in the OLTP system; can be called directly in the OLTP or using Customizing, from the BW system) do not yield any considerable improvement or are not clear.
The settings in Table ROIDOCPRMS or in the Scheduler in the BW system are not taken into account by some extractors. How is the data package size defined for the data transfer to the BW? Are there application-specific features to determine the package size? If so, what are they?
Other terms
SBIW, general settings extractors, MAXSIZE, data volume, OLTP, service API, data package size, package size, performance
Reason and Prerequisites
The general formula is:
      Package size = MAXSIZE * 1000 / size of the transfer structure,
                    but not more than MAXLINES.
You can look up the transfer structure (extract structure) in Table ROOSOURCE in the active version of the DataSource and determine its size via SE11 (DDIC) -> Utilities -> Runtime object -> Table length.
The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG Transaction SBIW (in the OLTP system) "Maintain General settings for extractors" to overwrite these parameters in Table ROIDOCPRMS on a system-specific basis. You also have the option of overriding these values in the scheduler (in the target BW system). However, in the Scheduler (InfoPackage) you can only reduce the MAXSIZE. The advantage of using the Scheduler to carry out maintenance is that the values are InfoSource-specific.
However, some extractors have their own flow logic which MAXSIZE does not load 1:1 from the ROIDOCPRMS.
This Note does not cover all SAP applications.
Solution
Application/DataSource               Standard settings or note
Generic extractor                     Standard (Example: Note 409641)
Delta Extraction via DeltaQueue       Standard as of PlugIn 2000.2
                                           Patch 3
LO-LIS                                 Standard
Logistic Cockpit SD                       Notes 419465 and 423118
Logistic Cockpit MM-IM:
Extraction 2LIS_03_UM                     Notes 537235 and 585750
Extraction 2LIS_03_BF                     Note 454267
           In general, the following applies to Logistic Cockpit Extraction: The package size set only serves as guideline value.
            Depending on the application, contents and structure of the documents, and the selection in the reconstruction program, the actual size of the transfer packages may differ considerably. That is not an error.
            For 'Queued Delta' update mode the package size of 9999 LUWs (=Logical Unit of Work, in this particular case documents or posting units per transaction are concerned) is set for LO Cockpit. However, if a transaction updated more than 10000 documents at once, the number 9999 would be invalid. This is because an update process cannot be split.
            In the case of a 'Direct Delta' update mode there is no package size for LUW bundling. In the DeltaQueue (RSA1) every LUW is updated individually.
           Also note the following:
                     If you want to transfer large data sets into the BW System, it is a good idea to carry out the statistical data setup and the subsequent data transfer in several sub-steps. In doing so, the selections for the statistical data setup and in the BW InfoPackage must correspond to each other. For performance reasons, we recommend using as few selection criteria as possible. You should avoid complex selections. After loading init delta with selection 1, the setup table has to be deleted and rebuilt with selection 2.
                     Bear the following in mind: The delta is loaded for the sum of all selections from the init deltas. Remember that the selections are made so that they do not impede the delta load, for example, if you have initialized the delta for the periods January 1st, 1999 to December 1st, 2000 and December 2nd, 2000 to August 1st, 2001 then you get a time interval from January 1st, 1999 to August 1st, 2001 in the BW. Documents from August 2nd, 2001 are no longer loaded.
CO-OM                                     Note 413992
PS                                        Standard or according
                                           to Note 413992
CO-PC                                     Standard
FI (0FI-AR/AP-3)                          First tables with open items(BSID for customers, BSIK for vendors) are read. The package size from the MAXISE field in Table ROIDOCPRMS is used in the extraction from these tables. If the packages are grouped together according to ROIDOCPRMS and a few data records still remain, these remaining records are transferred in one additional package.
After the open items are extracted, the system extracts from the table of cleared items (BSAD for customers, BSAK for vendors). In this extraction,the package size from the MAXSIZE field is adhered to.
FI (0FI-/AR/AP/-4 , new as of BW 30A) Like FI-AR/AP-3, but with one difference: if there are remaining records after the system reads the open items using the setting in the MAXSIZE field, they are not transferred in one extra package, but added to the first package of items read from the table of cleared items. For example, if 10 data packages with 15000 data records are extracted from Table BSID in accordance with ROIDOCPRMS, and 400 data records remain, the package size of the first data package from Table BSAD is 15400.
Both new and changed records are formatted in the following sequence in the delta transfer: 1) new BSIK/BSID records; 2) new BSAK/BSAD records; 3) changed BSIK/BSID records; 4) changed BSAK/BSAD records.
Package size 0FI_GL_4:
Prior to Note 534608 and the related notes, package size could vary considerably since the MAXLINES were applied to the document headers only. Then all documents lines for the document headers were read and transferred. As a result, the packages were 2 to 999 times as large as MAXLINES depending on the number of line items per document.
Note 534608 and the related notes changed the logic so that the MAXLINES is now also applied to the document lines. For each package, MAXLINES can be exceeded by up to 998 lines since a document is always transferred completely in one package. Smaller 'remaining packages' may also occur; for example if MAXLINES = 10000, and 10000 document headers with 21000 lines are selected, 2x10000 and the remainder of 1000 were were transferred in a separate package. Selection logic in 0FI_GL_4: Selection of the new FI documents via CPUDT -> the changed documents are then selected via Table BWFI_AEDAT. When changing the selection from new to changed documents, a package may occur which consists of the 'remainder' of the CPUDT selection and the first package of the BWFI_AEDAT selection. This package can then have a maximum size of 2 x MAXLINES.
FI-FM                                  Note 416669
EC-PCA                                 For the most part, the systemadheres to the standard settings but for technical reasons, packages packages smaller than the MAXSIZE or 7200 larger than the MAXSIZE may be omitted in Table ROIDOCPRMS
FI-SL                                  as in EC-PCA
PT                                     Standard (refer to Note
                                       397209)
PY                                     Standard
PA                                     Standard
RE                                     Standard
ISR-CAM (Category Management,
         new as of PlugIn 2001.1)     Standard
CO-PA                                  During the initialization and fullupdate in the profitability analysis, a join is always read from two tables (For details see Note 392635). To avoid terminations caused by Select statements that run for too long, access occurs with intervals for the object numbers (fixed size 10,000). New intervals are read until the package size requested by BW is reached. Therefore the size of the data package is always equal to or larger than the specification, but it can vary considerably.
Master data:
Business partner                       Standard
Product                                Standard
Customer                               Standard
Vendor                                 Standard
Plant                                  Standard
Material                               Standard
567747
Symptom
You want to improve the performance of the extraction and loading of your data into SAP BW 3.x.
Solution
This is a composite note that deals with performance-relevant topics in the area of extraction and loading.
If you encounter performance problems, ensure that the current Support Package has been imported.
This note is continually updated. You should therefore download a new version on a regular basis.
You will find further documents in the SAP Service Marketplace, alias bw under the folder "Performance".
Contents:
I.    Extraction from the OLTP
II.   Loading generally
III. Master data
IV.   Roll-Up/aggregate structure
V.    Compression
VI.   Hierarchies/attribute realignment run
VII. DataMart interface
VIII. ODS objects
IX.   Miscellaneous
I.    Extraction from the OLTP
Note 417307: extractor packet size: Collective note for applications
Note 505700: LBWE: New update methods from PI 2002.1
Note 398041: INFO: CO-OM/IM IM content (BW)
Note 190038: Composite note performance for InfoSource 0CO_PC_01 and
Note 436393: Performance improvement for filling the setup tables
Note 387964: CO delta extractors: poor performance for Deltainit
II.   Loading generally
Note 130253: Notes on uploading transaction data into BW
Note 555030: Deactivating BW-initiated DB statistics
Note 620361: Performance data loading/Admin. data target, many requests
III. Master data
Note 536223: Activating master data with navigation attributes
Note 421419: Parallel loading of master data (several requests)
IV.   Roll-Up/aggregate structure
Note 484536: Filling aggregates of large InfoCubes
Note 582529: Rollup of aggregates & indexes (again as of BW 3.0B Support Package 9)
V.    Compression
Note 375132: Performance optimization for InfoCube condensation
Note 583202: Change run and condensing
VI.   Hierarchies/attribute realignment run
Note 388069: Monitor for the change run
Note 176606: Apply Hierarchy/Attribute change ... long runtime
Note 534630: Parallel processing of the change run
Note 583202: Change run and condensing
VII. DataMart interface
Note 514907: Processing complex queries (DataMart, and so on)
Note 561961: Switching the use of the fact table view on/off
VIII. ODS objects
Note 565725: Optimizing the performance of ODS objects in BW 3.0B
IX.   Miscellaneous
Note 493980: Reorganizing master data attributes and master data texts
Note 729402: Performance when compiling and searching in the AWB

Identify OSS Notes Applied to J2EE Stack

We are running CRM 5.0 Netweaver CRM 5.0 2004s. We have applied several OSS Notes to the Java stack in DEV, QA, and PRD. Is there any way to determine which notes have been applied, short of re-applying the notes? Some of you may remember life before transaction SNOTE on the ABAP stack. The J2EE engine seems to be at that same stage, with no easy way to determine patches applied. Am I missing something?
Best regards,
Mike

Thanks Timo,
I realize there is no equivalent to SNOTE on the Java side, but is there any way to determine which notes have been applied, short of re-applying?
Take care,
Mike

Shall I undo the Applied OSS notes

Hi Team,
I applied 3 OSS notes in my BI system using SNOTE Transaction after BI 7 patch 12. Now I want back to the original state of the system by un doing the 3 OSS notes. My question: Is it possible to undo the applied ossnotes ? If yes please let me know the procedure?
Thanks in advance.
Regards
Ramana
Edited by: Ramana Murthy on Jan 17, 2008 4:30 AM

Yes go to snote T code and then press clt+F2... it is available in start screen itself...
Thanks...
please assign points if useful...

OSS note Note 1616259

Hello Gurus,
Can you please help me to understand the below information about the OSS note 1616259
u2022     what is the security issue/concern
u2022     what is the fix (SAP Note) & it's potential impact
u2022     when we can implement it
u2022     what kind of testing required
Thanks
Praveen Kumar

Hi,
There are a few threads all ready on this topic, here is the latest:
SAP Portal J2EE engine u201Cflawu201D discover at the recent Black Hat Conference
Notes 1616058 and 1589525 contain all the information available so far, Applying the patches mentioned in the note won't casue any problems, will require some down time to apply the patch though thats availble from the market place.
More info on the security threat can be found at http://erpscan.com/wp-content/uploads/2011/08/A-crushing-blow-at-the-heart-SAP-J2EE-engine_whitepaper.pdf
Kind regards,
Cathal

How to find out the list of implemented OSS Notes in a particular period.

Hi Friends,
Need help.
I need to find out the list of OSS Notes implemented in a period in a particular system.
Could you please suggest the table or program or any way to find out the OSS Notes Implemented date wise?
Thanks in Advance.
Sreenivas

Hi Sreenivas.
How did you find the solution to this? Trying to do the same thing!
Cheers,
Tom

OSS notes patching

Similar Messages

Maybe you are looking for