How to see OSS Notes?
HI ,
i got my certification recently.I have some OSS notes numbers.But i don't know how to see them.Can any body tell me how to see them?
RamaChandra
Hi
To access OSS notes you should have access to service.sap.com. For gwtting this access your company should be an SAP partner or you should have done SAP certification.
Once you login to service.sap.com, you can access the SAP notes.
OSS notes are now called SAP Notes
This notes are for differenct reason, it can be Correction to SAP Tcodes, programs,,etc, it can be bug correction, or to implement new functionality or Business Process
https://service.sap.com/notes
Here you can see the details and if you have OSS S id and Pwd then only you can see the notes You can implement by Tcode SNOTE
To access OSS notes you should have access to service.sap.com. For gwtting this access your company should be an SAP partner or you should have done SAP certification.
Once you login to service.sap.com, you can access the SAP notes.
Refer below link for further details
http://www.sap-img.com/basis/oss-notes.htm
Similar Messages
-
How to implement OSS notes : 207260
Hi All,
Can anybody please let me know how to impement oss note : 207260.
I need to implement Note : 207260 which is settlement rule for incorrect last used period.In this note its saying to run ZMIGCOBR to repair incorrect settlement rule for incorrect objects. But in this notes its not given any such program.
Please let me know how to implement OSS notes since i never done this before.
Thanks in advance.
Regards,
VishalCheck the below point:
SAP R/3 Document : Using Transaction SNOTE
Implementing OSS Notes Using the new Transaction Code SNOTE
In this document we will see how to implement an OSS note using the SNOTE
transaction code.
The transaction code SNOTE is used to implement OSS Notes. With the SNOTE
transaction, it is no longer necessary to register ABAP objects such as report function
modules etc. manually. But data dictionary objects such as screens, tables need to
be modified manually by registering them in OSS system.
In order to use the transaction code SNOTE, the relevant transport which implement
this transaction in the system need to be transported. Please refer to the SNOTE
guide available at http://service.sap.com
Execute the Transaction code SNOTE
One of the first steps to do is to upload the note into your system.
Follow Goto à SAP Note Download
You can also use the SAP Note upload if the note has been saved in your local
machine
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
In the following box that you get, enter the note number. We will take Note 388732
as an example
and click on the Execute icon. You will get the note number displayed in the list of the
OSS notes
In the above screen, we have two notes listed.
By double clicking on or on the note number you can display the OSS note.
You can also check the Status of the note by clicking on the Check SAP Note icon
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
Select the note and click on Check SAP Note icon. In this case we have selected
note number 388732.
If the note is not implemented as part of some support pack as per the support pack
level of your system, you should get the following pop up box.
Select the note number that you want to implement and goto Edit à Select/deselect
node
To implement the OSS note click on the Implement OSS Note icon
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
You will get a confirmation box like the following
Click on Yes
Click on the Continue icon
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
You will be prompted to enter a change request number.
Click on the Create Request icon
Enter a brief description of for the note and click on the continue icon
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
A change Request number is created for the change that you are making
Click on the continue icon
The system will display the objects that are going to be modified during the process
of note application.
In our case, Report LTXW0F10 and RTXWCHK1 are going to be modified.
Click on the Continue icon
For while the system will show the note in IN PROCESS status
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
After a while, select the note and click on the Check SAP Note icon on the application
toolbar
But still the Status of the note is displayed under In Process category.
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
You can also check the status of the note by checking the meaning of the icon next
to the note number.
To check the legend, follow Utilities à Color Legend
As you can see from the legends box, means Implemented Correctly.
Since the note is implemented, you can change the status of the note from In
Process to Completed manually.
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
Select the note and click on the Set Processing Status icon
In the Pop up box that you get, select the Completed radio button
And click on the Continue icon
SAP R/3 Document : Using Transaction SNOTE
http://www.sappoint.com
The note number is removed from the list
ü You can also check the logs of the activities performed during the OSS note
implementation by clicking on the Logs icon on the application toolbar. The log
information will contain all the steps that were performed from the point of
downloading the note will its implementation is completed.
ü If there are any pre-requisite notes for the note that is being applied, the
system will prompt you to load those notes too into the system. Depending on
their applicability to your system, the system will prompt you accordingly to
apply the pre-requisite notes.
ü You can register the manually implemented SAP notes by executing the report
SCWN_REGISTER_NOTES.
ü SNOTE cannot change or modify data dictionary objects. If there is a note
which requires changes to be made to a structure or a screen then SNOTE will
not help. Such objects have to be registered and modified manually.
http://www.sappoint.com/basis/snote.pdf
Regards,
Prakash. -
how to access OSS notes. i'm working in a reputed company, i would like to see OSS how can i access that.
Hi
OSS note provided by SAP for standard program issues. Based on problem which is facing sap will provide OSS note number. After getting the OSS note number follow the below procedure.
Implementation of OSS Note procedure
Go to development system, then enter t_code(snote) then Goto option (Menu bar),then select sap note down load option then type the sap note and then execute.
after that goto (menu bar) select note browse and type the sap note then select execute button and double click on the line then check implementation status whether sap note is implemented or not.
if implemented,come back snote home page, expand in process then select your sap note and then execute.
it will show one screen for confirmation of sap note select 'yes' button then click on continue icon after that it will ask cts for your sapnote then click on continue again click on continue icon.
after that it will show one information message that 'sap note implemented completely'.
Reward points!!
Thanks & Regards,
Vasudeva Rao -
How to apply OSS note and how to use it?--thanks
Hi, morning all,
I want to know how to apply OSS notes and how to use it, pls help me.
Thanks.Applying OSS note is a critical activity in the system. Usually this task is carried out by the basis, as they maintain the system and the notes, support packs, etc.
A OSS note has potential to impact the system in several ways. So it is better to work with the basis if you need to apply a OSS note to be applied.
Transaction code is Snotes. But pl dont attempt to apply by yourself.
Reg your other question as how to use the OSS note, there is nothing like using aOSS note. Just apply and depending on what the notes do, it may change the config, or download a program or something.
Ravi Thothadri -
From where do we see OSS notes and message errors...
hi,
From where do we see OSS notes and message errors details if the error number is provided??
Thanks & Regards*OSS* are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.
In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.
For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.
Access the SAP Support Portal:
*http://service.sap.com/*
- Keys and Requests
-- Request license key
--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite
Follow this step to obtain the Program Access key:
Menu Path: System -> Services -> SAP Service (Transaction code OSS1)
Login in with your OSS ID and Password
Click the Registration button
Click Register Object
Double click R/3 Value Contract
Fill in the Object Registration for Installation:
For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C
Finished, click the Register button
Select the Key number and use the Copy and Paste short key to copy the Access key
You are now able to modify the SAP standard program.
Finished the modification, do remember to transport it to the production system after all the necessary testing.
http://www.sap-img.com/basis/what-are-sap-notes.htm
http://www.sap-img.com/basis/oss-notes.htm
http://www.sap-img.com/basis/manually-applying-the-oss-note.htm
Regards,
Ashok -
Hi friends
Please send me path how to refer OSS notes
RajeshHi Rajesh,
OSS NOTES: ONLINE SERVICE SUPPORT.
This was provided by SAP. if you have any issue for which you dont find solution for this kind of things you can put a note to SAP in www.service.sap.com for which you should have user id and Password provided by the company
SAP Notes give you instructions on how to remove known errors from SAP Systems. They include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs.
Depending on the type of error, an SAP Note may also include:
Workarounds
Descriptions of how to correct repository objects in the ABAP workbench, known as correction instructions
Links to Support Packages that solve the problem
You can access SAP Notes both from the SAP Service Marketplace and SAPNet - R/3 Frontend.
You can raise an OSS note if you feel there is some error in standard functionality or program.
The OSS note is the official SAP note, which is available on the marketplace. You can search for the note on https://websmp109.sap-ag.de/notes (or https://portal.wdf.sap.corp/home ---> Service Marketplace-). The note 80183 contains the information regarding the pricing. #
Visit the following link for information regarding SAP Notes:
http://help.sap.com/saphelp_nw04/helpdata/en/b8/3cf839fd35384de10000000a11402f/frameset.htm
<REMOVED>,
Thanks and Regards,
Sateesh.Kandula -
hi guru's,
how to get OSS notes ? is there any special subscription for this,
Edited by: ravi netyam on Oct 29, 2008 11:34 AMyou can go to service.sap.com/notes to browse note than in sap go to snote (tcode) to download and apply it .
Please check below thread to get more details.
Can a functional guy check if a certain NOTE had been implemented
Checking if different versions of a SAP Notes are implemented or not
Manish
Edited by: Manish Kumar Rathi on Oct 29, 2008 7:58 AM -
Hi Dear Friends,
How to search OSS notes, tell each and every step; this is the interview question. I answered that using OSS1 but they did not satisfy with that. How to answer for this question
Thanks in advance, LearnerHello Paul,
the ability to find the right SAP Notes for customer problems is essential for all consultants.
SAP Notes can be found on our SAP Support Portal using http://service.sap.com/notes. There You will find a form to fill out to search for SAP Notes.
To get access to this portal, please ask Your customer for an User ID. If You are a certified SAP Consultant You can logon with Your S-User. If You have further questions regarding Your personal access You can also contact Your local SAP Support Hotline (for USA U.S. Products and Services Phone: +1-800-872-1727)
Kind regards
Ralph Richter -
how to create 'OSS ' notes
Hi
You can't create OSS notes. SAP already provides them.
Only thing is you have to see them and change/modify your programs as per tthe corrections mentioned in them.Again you should have a User id and Password to view them.You can view them through --search notes..
http://www.sap.help.com/
Regards,
Anji
Message was edited by:
Anji Reddy Vangala -
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
<b>
Anyws here is the note</b>
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 -
How to create OSS note for SAP?
Hi,
How do I create OSS for SAP? Any step by step or notes related?
appreciate your help!!!!!!
Thanks,Hi Afi,
If you are looking for creating an oss message with SAP follow the path
http://service.sap.com/notes --> Report a Product Error --> select your system --> Enter the search term ( related to your issue) and componenet ( if its basis BC , change management BC-CTC , if its for solution manager use SV-SMG or the sub component )
Now it will show the related oss notes and if that notes are not helpful you can create a message with SAP by clicking create message.
Thanks
Prince Jose -
How to reset OSS Notes with Question mark status in SPAU
Hi,
We are doing SPAU adjustments. In that under Note we have many OSS notes with status "Question Mark". We ran SAPRUPGM again. But still we have this question mark.
We realized some of the notes are not applicable and want to reset. But when I select the note and reset, it gives a pop up to confirm the reset. I select "reset" there. But instead of reseting it gives me a popup asking to download the OSS note. If I cancel it it goes back to the initial SPAU screen. Nothing done. If I okay it it tries downloading the note.
How to solve this situation?
Can you also tell me if it is okay to leave the notes without resetting.
Regards,
Ravikanth
Edited by: Ravikanth Tunuguntla on Aug 12, 2008 5:37 PMAppreciate the reply. I of course did try to re-execute SAPRUPGM. In background, it runs for 2 seconds and produces no log or spool. When I run on-line, and un-tick the box for output log file, the resulting list shows these messages for the gree question mark notes. These notes are no longer visible in SNOTE. Basically I'm stuck - with the green question mark, I don't know how to get rid of these Notes in SPAU.
Corrections in SAP Note
NOTE 0000683004 0003 Inconsistent data
NOTE 0000693190 0002 Inconsistent data
NOTE 0000731027 0001 Inconsistent data
NOTE 0000764040 0003 Inconsistent data
NOTE 0000768618 0001 Inconsistent data
NOTE 0000770227 0001 Inconsistent data
NOTE 0000772460 0001 Data for SAP Note 0000772460 incomplete
NOTE 0000775691 0002 Inconsistent data
NOTE 0000777671 0003 Inconsistent data
NOTE 0000782311 0002 Inconsistent data
NOTE 0000784108 0001 Inconsistent data
NOTE 0000785324 0002 Inconsistent data
NOTE 0000802475 0004 Inconsistent data
NOTE 0000826538 0002 Inconsistent data
NOTE 0000843717 0002 Inconsistent data
NOTE 0000864505 0002 Inconsistent data -
Hi ,
I have very basic clarification. Please give me some idea on oss notes. Like currently i am fworking on first implimentaion project. Here my role is testing some specific scnarios. Actually i got some errors while testing. So i have mailed to seniors into the project . I got the replies like : Please check oss note " Note 1174020 - SURVEY: Error when applying a XSLT transformation" this is for supplier registration testing.
Please advise me where i have to cehck oss notes like this. If next time any errors then how I will check for that errors??
(i know service market place uid and pwd)
Thanks in advance,Hello Viswanah,
SAP note is the official fix released by SAP to the customer issues. Any one can access such notes from SAP service market place. But you need to have service market place access i.e. SUSER ID.
If you working in a project, your basis team can create SUSER ID for you.
https://websmp210.sap-ag.de/support
is the URL to access service marekt place where you will be asked to enter login id & credentials. Under Help & Support tab you can find a field SAP Note where you can enter the sap note number if you know or you can enter the description of your error message to find relevant sap notes.
Also you can raise a OSS call under report a product error section if you are unable to find any relevant note for your issue.
Regards,
Krish -
How to see my notes from Mail in Gmail?
The Notes label in Gmail is there in the left column of my gmail but there isn't any note in there. How can I sync my Mail account of gmail with Gmail so I can see my notes in both platforms?
I have Lion 10.7.1Hi,
In Leopard in System Preferences > Sharing With File Sharing selected go to the Advanced Button.
Is SMB Enabled ?
Also is the Finder's Preferences set to the Share items marked with the Red Info ?
Lastly, on the Windows Machines is Sharing Enabled (i.e Can the PCs see each other ?) If the PCs can not see each other then it is unlikely the Macs will "see" them.
(Just covering bases with this one - you seem to imply this but don't actually state it)
8:32 PM Wednesday; December 15, 2010 -
Dear Sir ,
I want to follow SAP note , pl guide that how to go thru the link , which link i have to follow , pl guide me in step by step manner , what is contained in these notes , as i had never gone thru this , where the notes number is to be put.
thanks in adv.
sap11Hello,
If you have an OSS id then go to
http://service.sap.com/
Click on SAP notes Search
it will ask your OSS id
Screen for searching OSS notes will appear, enter the keywords for searching
or
If you have an OSS id then enter the OSS id in the Number Field on the right side of the screen
Hope this solves
Regards,
Kumar
Maybe you are looking for
-
IIf Expression: The first of many questions. Thank you in advance.
One of the situations I am in need of assistance with is the following "IIf" statement: =IIf([Check36]=Off,10,0) The expression is located in a field [LateFee]. When, [Check36], is Off, $10.00 is displayed, if On then $0.00 is displayed. I
-
I had a Microsoft tech access my computer remotely to resolve issues with my hotmail acct. There were files that needed to be deleted and he also changed some settings. Later, when I tried to open InDesign I received the following error: AMT Subsyste
-
Converting slideshow from iphoto with itune playlist as background music
I have created a slideshow in iphoto with an itune playlist as the background music and when I convert it throught quicktime into a movie it only plays the first song from the playlist. All photos look good in the slide. This problem has started sinc
-
When I try to preview a video in final cut express it is very laggy.
-
Business Area-Cost Center error while doing VL09 (PGI Reversal)
Hi Friends, Kindly go through the "ERROR" message and "IMPORTANT" point as mentioned below:This is happening while reversal of PGI in VL09. IMPORTANT: Just to make you aware, the cost center in error (CONSDSPL) was nowhere assigned in FS00 or OKB9. A