TSV_LIN_ALLOC_FAILED
Hi All,
I'v been having this error when loading Business Partner Master Data (Delta). Does anybody have an idea why this load is going out of memory? There are several others loads bigger than this ones, that works perfectly well.
what do you think??
Dinesh, Kedar,
there is some extensions in the infosource.
the amount of data is arround 10.000 rows/load.
there is no table, is a program.
I'll be checking the programs.
thanks for the help.
Mauricio
Similar Messages
-
hi all the experts,
When the job SAP_COLLECTOR_FOR_JOBSTATISTIC ,
I searched in service.sap.com notes and have not achieved anything specific.
This is canceled and when I check the st22 said that there is not enough space in memory. annex the dump TSV_LIN_ALLOC_FAILED.
thanks and regards.
Gustavo Gonzalez
ShrtText
No roll memory available to extend the index of an internal table.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The linear index of an internal table was supposed to be extended.
However, the 2293776 bytes of memory requested for it were not available
in the roll area.
Storage location: "Session memory"
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server sapsrv01_D01_01 on host sapsrv01 (wp 2)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1886
How to correct the error
Decide by analysis whether this request is reasonable or whether there
is a program error. Pay particular attention to the internal table
entries listed below.
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 1708928
Extended memory (EM)........... 114982560
Assigned memory (HEAP)......... 276176080
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... " "
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"TSV_LIN_ALLOC_FAILED" C
"RSBPCOLL" or "RSBPCOLL"
"START-OF-SELECTION"
System environment
SAP Release.............. "640"
Application server....... "sapsrv01"
Network address.......... "10.0.0.15"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 2
Short dump setting....... "full"
Database server.......... "SAPSRV01"
Database type............ "MSSQL"
Database name............ "D01"
Database owner........... "d01"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Oct 3 2007 00:34:24"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "203"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 1708928
EM....................... 114982560
Heap..................... 276176080
Page..................... 24576
MM Used.................. 379558912
MM Free.................. 10752584
SAP Release.............. "640"Hi ,
You can increase the roll area and see if this problem persists.
The parameter is ztta/roll_area .
Also , you can increase the Heap memory too (abap/heap_area_total).
But before increasing the meory , find out if there is any possibility to correct the program , by reducing the size ofthe internal table.
Regards,
Ponni.
from Eric Brunelle: begging for points is totally against forum rules. read them -
Dump TSV_LIN_ALLOC_FAILED in SRM
While extracting the datasource in RSA3 it throws the TSV_LIN_ALLOC_FAILED runtime error in SRM.It is a costomized extractor using the customized function module.
Thanks,Here is the ST22 dump,
Runtime Errors TSV_LIN_ALLOC_FAILED
Date and Time 12/19/2011 07:54:24
Short text
No memory available to extend the index of an internal table.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator .
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
The linear index of an internal table was to be enhanced. However, the
requested memory for this purpose of 706240 bytes was no longer available
in the roll area.
Storage location: "Session memory"
How to correct the error
Try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_LIN_ALLOC_FAILED" " "
"SAPLBBP_PDBUP" or "LBBP_PDBUPF2C"
"FILL_X_TABLES"
System environment
SAP-Release 701
Application server... "sappr1a2"
Network address...... "10.163.2.46"
Operating system..... "HP-UX"
Release.............. "B.11.31"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "hpbpgc01"
Database type..... "ORACLE"
Database name..... "PR1"
Database user ID.. "SAPSR3"
Terminal.......... "FFXCTXGC26"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Oct 31 2010 21:56:13"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.4.0) "
Patch level. 117
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 701
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1917712
EM...... 2002743520
Heap.... 1998752864
Page.... 1867776
MM Used. 3846087392
MM Free. 143093200
User and Transaction
Client.............. 100
User................ "XMSELVA"
Language key........ "E"
Transaction......... "RSA3 "
Transactions ID..... "4EEEF6C8B62E4B0BE10000000AA3022E"
Program............. "SAPLBBP_PDBUP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLBBP_PDBUP" - in "FILL_X_TABLES".
The main program was "RSFHGEN2 ".
In the source code you have the termination point in line 120
of the (Include) program "LBBP_PDBUPF2C".
Source Code Extract
Line SourceCde
90 log_not_found = 1
91 OTHERS = 2.
92 IF sy-subrc <> 0.
93 PERFORM abort.
94 ENDIF.
95 IF c_on = c_off. MESSAGE w536(bbp_pd). ENDIF.
96
97 ELSE.
98
99 *------ address data were not found
100 CALL FUNCTION 'BBP_PD_MSG_ADD'
101 EXPORTING
102 i_msgty = c_msgty_w
103 i_msgid = 'BBP_PD'
104 i_msgno = 163
105 EXCEPTIONS
106 log_not_found = 1
107 OTHERS = 2.
108 IF sy-subrc <> 0.
109 PERFORM abort.
110 ENDIF.
111 IF c_on = c_off. MESSAGE w163(bbp_pd). ENDIF.
112 ENDIF.
113
Information on where terminated
Termination occurred in the ABAP program "SAPLBBP_PDBUP" - in "FILL_X_TABLES".
The main program was "RSFHGEN2 ".
In the source code you have the termination point in line 120
of the (Include) program "LBBP_PDBUPF2C".
Source Code Extract
Line SourceCde
90 log_not_found = 1
91 OTHERS = 2.
92 IF sy-subrc <> 0.
93 PERFORM abort.
94 ENDIF.
95 IF c_on = c_off. MESSAGE w536(bbp_pd). ENDIF.
96
97 ELSE.
98
99 *------ address data were not found
100 CALL FUNCTION 'BBP_PD_MSG_ADD'
101 EXPORTING
102 i_msgty = c_msgty_w
103 i_msgid = 'BBP_PD'
104 i_msgno = 163
105 EXCEPTIONS
106 log_not_found = 1
107 OTHERS = 2.
108 IF sy-subrc <> 0.
109 PERFORM abort.
110 ENDIF.
111 IF c_on = c_off. MESSAGE w163(bbp_pd). ENDIF.
112 ENDIF.
113
113
114 ENDIF.
115 *---fill gx_bup
116 PERFORM insert_gx_bup USING it_bup.
117
118 ENDLOOP.
119
>>>>> SORT gx_addr BY guid.
121 ENDFORM. " fill_x_tables
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 53
SY-DBCNT 0
SY-FDPOS 45
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Report for the extractor call
SY-MSGTY E
SY-MSGID R1
SY-MSGNO 201
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 2
SY-DATUM 20111219
SY-UZEIT 052933
Thanks, -
Short dump errors desc--how to resolve
I would like to know the short dump errors meaning and how to resolve it. i have the following errors
1. TSV_TNEW_PAGE_ALLOC_FAILE----
for this the description for ERROR ANALYSIS is : The internal table "IT_24" could not be enlarged further. To allow error handling, the table has to be deleted before this log was created.HOW TO CORRECT THE ERROR is : the amount of storage space was (in bytes) filled at termination time was:
Roll area..........1708928
Extended memory (EM).........440057520
Assigned memory (HEAP).......465813648
short area.........." "
Paging area.....33857536
Maximum address space....." "
2. DBIF_DSQL2_SQL_ERROR----
HOW TO CORRECT THE ERROR is:
Database error text......."ORA-01555: snapshot too old: rollback segment number 2 with name "PRS_0" too small"
Database error code - 1555
Triggering SQL statement......."FETCH NEXT"
Internal call code................"[DBDS / NEW DSQL]"
Please check the entries in the system log (Trasaction SM21)
3. TSV_LIN_ALLOC_FAILED----
this error analysis which also gives HOW TO CORRECT THE ERROR is almost the same like the first error description which i have written like memory space and so on
i would appreciate if u could clarify these errors and how to resolve it. Thanks in advance.Hi,
TSV_TNEW_* error are the memory problems in BI, you need to wait untill the system load is reduced...check the TA: SM37 and then repeat the failed steps, it will be successful.
DBIF_* are database releated errors....oracle backend error, u need to find out where the error has occured in the SQL statement and fix the error.
Usually these errors will the locks.
Oracle 8i error message says:
<u><b>ORA-01555</b></u>
snapshot too old: rollback segment number string with name "string"
too small
Cause: Rollback records needed by a reader for consistent read are overwritten
by other writers.
Action: Use larger rollback segments.
Regards,
Vijay
Message was edited by:
Vijaya Kumar Malyavantham -
Last error code set: Unresolved requests in buffer SID
Hi All,
We are installing EHP4 SP6 in our ECC 6.0 system. Weu2019ve created a .xml
file in our solution manager and calculated a download queue with the MOPZ. The installation is on a Windows 2003 32 Bit platform with a SQL server 2005 SP2 DB. There is 40Gb pagefile and 15Gb memory available. The latest SAP kernel (254) is also installed.
In roadmap step 5 (Preprocessing) the installation stops with the
message: u201CChecks after phase MAIN_SHDRUN/ACT_UPG were negative! Last
error code set: Unresolved requests in buffer <SID>Check logfiles 'ACTUPG.ELG' and 'J:\EHPI\abap\log\SAPehpi.ECO'u201D
In the log files there many entryu2019s of: DDIC ACTIVATION ERRORS and
RETURN CODE in SAPAW70106.VCW 1 ETP111 exit code : "12"
By looking at the logfiles, it seems to be a problem with the job RDDMASGL in the shadow instance. The job terminates and a runtime TSV_LIN_ALLOC_FAILED error occurs.
Iu2019ve changed some parameters in the shadow instance profile to:
abap/heap_area_total = 4000000000
ztta/max_memreq_MB = 1000
ztta/roll_area = 2000000
ztta/roll_extension = 2000000000
abap/heap_area_dia = 2000000000
abap/heap_area_nondia = 2000000000
em/initial_size_MB = 2048
But after repeating the phase, the installation stops again.
Hopefully some of you can provide me some information so that I can solve this problem and continue the installation.
Thanks in advance for your reply and support.
Kind regards,
Rik HutHi,
Choose option Accept non-severe errors and repeat the phase. Because sometimes in ACT_UPG phase it tries to activate some obsolete object and get stuck.
Thanks
Sunny -
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
Maybe you are looking for
-
How can I import contacts from my iPhone into my iCloud account?
Hi. I synchronized my iPhone with my eMac, and as a result all my eMac contacts were transfered to my iPhone, while I was seeking just the contrary. Can someone tell me how I can do this?
-
Vendor invoice posting through IDOC - Cost center determination (OBCC)
Dear experts As per SAP Notes 31126 and 137686 I have maintain all configuration settings for "Automatic posting of vendor invoice from Billing" in different company codes. It is working perfectly the way we need, we need help in Transaction Code "OB
-
Performance problem with synchronized singleton
I'm using the singleton pattern to cache incoming JMS Message data from a 3rd party. I'm seeing terrible performance though, and I think it's because I've misunderstood something. My singleton class stores incoming JMS messages in a HashMap, so that
-
IIneed code to send & receive mails to MS OutLook Express using java
Hi Friends, Please help me in the following area.. I need code to send and receive mails and attachments to MicoSoft OutLookExpress in java, please give me the steps and entire code. Thanks In advance Thanks & Regards Kiran [email protected]
-
Webcam stops working after a few minutes
Hi everyone, I'm having some trouble with the live video stream using Adobe Connect and I wonder if anyone can offer any advice. I´m a trainer using Adobe Connect giving classes. Everything was fine until I got a new laptop. This is what happens befo