OSS notes during upgrade

Dear All,
We are doing ecc6.0 upgradation. While doing this in SPAU there are oss notes with green question marks under Note Corrections.
Kindly suggest me what to do with this oss notes. Whether to consider that or skip that?
Kind Regards,
Ranjith C.

Hi,
What is your OS & DB , What is your soruce release, At what phase you are currently in upgrade.
However your SPAU phase stands for your respository corrections , when we are upgrading SAP system we need to identify list SPDD & SPAU objects where standard objects are corretced. I beleive list objects SPDD & SPAU objects are shown by upgrade tool during pre-processing. SPAU corrections can also be done with in 2 weeks of time after the upgrade.
Do not skip talk to your abaper abaper & take a decision ....
-rahul

Similar Messages

Disck Space not enough during upgrade CUCM 9.1(2)SU1 to 9.1(2)SU2a

Hi,
I face an issues during upgrade my current CUCM 9.1(2)SU1 to 9.1(2)SU2a, it show with this error message "There is not enough disk space in the common partition to perform the upgrade, for steps to resolve this condition please refer to CUCM 9.1(1) release notes or view defect CSCuc63312 in bug toolkit on Cisco.com". I had check the bug id and got 2 way to do it:-
1. reduce the amount of traces on the system, but I not ready want to do this
2. install a COP file name: ciscocm.free_common_space_v1.0.cop.sgn
If I select option 2, will it have any risk? Is it mean 9.1(2) - inactive version will be clear out from disk space or it will clear out 2 version - active and inactive version from disk space?
I need have some advice on this before I perform.
Thanks.

Hi,
As per the following link
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_011.html
You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version."
Additionally, regarding the first option, if you do not want to reduce the tracing levels you can still delete some old traces using RTMT which gives you an option of deleting the traces from the server as well as transferring / downloading them to your pc simultaneously by checking the 'delete from server' option on last page of log file collection option.
HTH
Manish

SIS structure not being generated during upgrade

Hello,
We are in the early phase of an upgrade project. Our custom SIS structures are failing with the update rules generation. Looks like the data element associated with the characteristic of the info structure is changed that is causing inconsistency hence the error. I have looked at an OSS note that talks about rebuilding the info structure from scratch. Has any one experienced this situation. I would appreciate any inputs on this.
Thanks,
Girish

Hi Girish,
I think you have to recreate the SIS from scratch.
May be try to Copy your SIS Strycture to a new one
Remove the Key figure (which has faulty data element )
--- Save SIS structure
---Reassign the Key figure Via T/code MC21.
May be this may help you.
Regards,
Lanka

OSS notes relevant for FI/CO for upgrade from 4.7 to ECC 6.0

Hello,
I need the list of the applicable OSS notes relevant for the FI/CO module for upgrade from 4.7 to ECC 6.0
Thanks
Sid

Hi,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Please assign points if it useful.
Regards
Ravinagh Boni

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 <b>service.sap.com/notes</b> 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

Structure SI_BBSEG not found during upgrade from 4.6C to ECC 6.0

Hi
We are upgradingour SAP system from 4.6c to ECC 6.0 and we are having an issue while generating the programs, error says '.INCLUDE SI_BBSEG ' not found. It seems like structure SI_BBSEG was not created by SAP'. How would i resolve this issue? i couldnt find any OSS note on this. Please advice.
thank you,
- A

Anil
SI_BBSEG is Include structure of BBSEG & comes already included in it as std SAP. (u can see it in SE11 >> BBSEG)
It does not exist till you want to enhance BBSEG & add your custom fields. Normally those fields will be added to Std SAP screens as custom enhancements . You can go to SE11 & double click; it will ask Do you want to create ?
What is the process you are following for moving Enhancements from 4.6 to ECC6 (user Exits, screen exits) ? If this SI_BBSEG exists in old system, then there must be std screen enhanced which uses the fields of this structure. There could be some programs too which are using this structure while creating FI Documents using std BAPI. recomended that these should move to ECC6 together.
If you have not enhanced BBSEG in 4.6 then refer note : 590977

Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

Dear SAP Gurus,
Greetings
My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
Please clarify. Thanks in advance for your time and efforts
Regards,
Chaps
P.S. Points will be awarded for answers !!

Hi,
I think that you should read long text of OSS note 999614 carfully and you are
aware of the fact that you will have additional migration efforts in
case you need to migrate to new G/L later on.
In case you are convinced that this is the best way please feel free
to deactivate new G/L as described in note 999614.
Please make sure that you deactivate new G/L in all clients of your
new system in case there were already client copies done.
Yes this is possible and I would not automatically assume that
error during posting of transactions are due to New GL not being activated.
Note 756146 documents the issue and possible repercussions
of using Classic GL.
In the case of a new installation the new G/L accounting
is active by default in ERP. In principle, the use
of the classic GL is also possible for new customers, however,
SAP does not recommend it since this requires an additional
migration expense in later years.
Regards,
Aidan

Close the Programs that are opened by OSS Note

Hi,
We had opened some of the standard programs (With access key) and made the modifications as per the OSS note some time back, the programs that were modified are still open for editing even now and the client is concerned about the sanctity of the standard programs as they are open for everyone any one can make changes to the programs, how one can make sure that the object once opened should be closed immediately afer applying modifications, does SAP has any kind of mechanism using which we can track this,
Any help would be highly appreciated,
Rgds,

Hi Sailatha,
Once you have modified an SAP Object using an access key it becomes a custom Object. It can be modified at any time by any developer in the development system. If you have used the Modification Assistant or SNOTE while making the changes the first time, you will be prompted to retain your changes or reset to original in SPAU during upgrades / support packs.
Regards
Suresh Datti

Applying support package during upgrade [ BW 3.1 - BW 3.5 ]

Hello,
We are performing the upgrade of BW 3.1 to BW 3.5. In the upgrade phase XPRAS_UPG we cam across error and on reporting the same to SAP were advised to apply the support package SAPBW35013 upto level 13, the present level being 9.
Support packages cannot be implemented during an upgrade. On informing this to SAP they replied back saying as below:
"Kindly implement the correction instructions via TA snote mentioned in the note #844007"
What does he mean. Does he want me to apply the notes present within the support packages. If yes how can I apply so many notes manually, is there a better way of doing this.
Please assist.
Thank you,
Kind regards,
Zaheer Shaikh

Zaheer,
You just need to apply only the note 844007 to your BW 3.1 system through the t.code SNOTE.
Go to SNOTE
Download the OSS note 844007 to your system.
Apply the OSS note from SNOTE.
The correction instructions will be auomatically applied to your system by SNOTE.
Thanks
Gautam

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

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

How to switch back to old depreciation calc method during upgrade to ECC6.0

Hi Everyone,
We are doing a technical upgrade from 4.6C to ECC 6.0 and we have activated the enterprise extension EA-FIN via SWF5 (switch framework) to use the functionality of accrual engine, closing cockpit etc. However, activating EA-FIN has activated the new depreciation calculation method (Period based depreciation calculation) which, we do not want. We still want to continue using old depreciation method (transaction based depreciation calculation).
So, is there a customization that turns off the new depreciation calculation? Or an OSS note? I read in SDN Wiki and it said, one has to post a customer message (OSS) to SAP and they in turn provide the notes to switch back to old depreciation method and also it is mentioned that these notes are not available in service market place. Is that how it is? Had anyone got into this issue before? Please help me in this regard.
Thanks in advance,
K

You already found your answer on the Wiki:
I read in SDN Wiki and it said, one has to post a customer message (OSS) to SAP and they in turn provide the notes to switch back to old depreciation method and also it is mentioned that these notes are not available in service market place.
What is not clear about that?

Error in transaction KEA0 during upgrade

Dear All,
During upgrading the custmer system from 4.7 to ECC 6.0 we found some error in the transaction KEA0 while trying to activate the cross client for an operating concern.
The activation logs says that there are the syntax errors in the gereted subroutine pool: RK2O0100.
I however corrected the error and activated the code but again when I am trying to execute the same it gave me the same error and when I go to the sub routine pool I found that the changes are again undone and the previos version is activated. This happens repeatedly that the code is corrected and activated by me and says no error and ones I log off and login again it says the same error.
Help will be appriciated.
Thanks iin advance....
Abhi...

Dear Raymond,
Thankds for your help..........
I tring to run RKEAGENV it shows the error message with STOP button saying that the field WTGBTR not contained in the nametab for table CE1E_B1 and when Io run RKEAGENF it gives a short dump saying that entry for CE10100 is not allowed for TTABS.....
Please help.

Encounter a problem during upgrade sap r/3 4.7 to ecc6

Hi expert:
i encounter a problem during upgrade sap r/3 4.7 to ecc6
in START_SHDI_FIRST step.
here is the error msg~
MSSCRESPDEFN.LOG
Msg 2812, Level 16, State 62, Server Jack, Line 6
Could not find stored procedure 'dbo.sap_upg_getrelease'.
setuser
i checked MS SQL DB and found out that i only got 'erp.sap_upg_getrelease' but not dbo owner.
can any one tell me how to solve this problem?~
thanks.
Regards
Jack Lee

It's the kernel for the shadow the correct?.
Regards,
Alfredo.

MAIN_SHDRUN/ACT_UPG ends during upgrade

During upgrade from CRM 6.0 to 7.0 EHP1 MAIN_SHDRUN/ACT_UPG phase ends.
In ACTUPG.ELG file I see:
******* LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCI702.CRT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EEDO519X"Table" "CRMST_QUERY_OPP_BTIL" could not be activated
1 ETP111 exit code
I read SAPACCI702.CRT:
3 DDT012XAktiviere Tabelle "CRMST_QUERY_OPP_BTIL"
3 DDT402 Append-Struktur "ZCRMST_QUERY_OPP_BTIL" an Tabelle "CRMST_QUERY_OPP_BTIL" angefügt
2WDDT191 Erweiterungskat. "3" möglich, aber Include oder Subtyp ist noch unklassif.
1EDDT963 Feld "PROD_HIERARCHY" in Tabelle "CRMST_QUERY_OPP_BTIL" ist doppelt (Bitte überprüfen)
3 DDT013 Tabelle "CRMST_QUERY_OPP_BTIL" wurde nicht aktiviert
3 DDT014XAktiviere abhängige Tabelle "CRMST_QUERY_OPP_BTIL"
3 DDT402 Append-Struktur "ZCRMST_QUERY_OPP_BTIL" an Tabelle "CRMST_QUERY_OPP_BTIL" angefügt
2WDDT191 Erweiterungskat. "3" möglich, aber Include oder Subtyp ist noch unklassif.
3 DDT038 Aktivierung abhängige Tabelle "CRMST_QUERY_OPP_BTIL" erfolgreich
Oh... in german language... it's a problem for me. How can I check this structure? how?
Have you got any suggest?
Regards.

Hi Ganimede,
i have the similar kind of error can you please explain the steps for deleting the entry you have specified...
would be greate if you coulkd reply earliest
Thanks and Regards
Amar Ghuge

OSS notes during upgrade

Similar Messages

Maybe you are looking for