Anda di halaman 1dari 3

SAP Knowledge Base Article

1880318 - Memory dumps during data extraction from a planning area


Version 2 Validity: 15.07.2013 - active

Language English

Symptom
The extraction of Data via InfoPackage or Data transfer process (DTP) dumps with a memory dump like TSV_TNEW_PAGE_ALLOC_FAILED or
TSV_TNEW_OCCURS_NO_ROLL_MEMORY or TSV_TNEW_BLOCKS_NO_ROLL_MEMORY.
A typical dump call stack is the following:
ActiveCalls/Events
No.Ty.ProgramIncludeLine
Name
9FORMGP4GUSAAVPZUMFQQO54OZQNTXY9GP4GUSAAVPZUMFQQO54OZQNTXY93050
MERKMALE_SELEKTIEREN
8FUNCTION/SAPAPO/SAPLMSDP_PAR/SAPAPO/LMSDP_PARU0998
/SAPAPO/MSDP_PLOBS_PREPARE_SET
7FORM/SAPAPO/SAPLOO_TS_DM/SAPAPO/LOO_TS_DMFE11891
EXTRACTION_BUFFER_PLOBS
6FUNCTION/SAPAPO/SAPLOO_TS_DM/SAPAPO/LOO_TS_DMU38311
/SAPAPO/TS_DM_EXTR_INITIALIZE
5FUNCTION/SAPAPO/SAPLOO_TS_DM/SAPAPO/LOO_TS_DMU2042
/SAPAPO/TS_DM_EXTRACT_DATA
4FORMGP4GSK0G59ITUVEJOFKRGNKJ1UPGP4GSK0G59ITUVEJOFKRGNKJ1UP91
DATA_TRANSFER
3FUNCTIONSAPLRSAPLRSAPU06141
RSAP_DATA_TRANSFER
2FUNCTIONSAPLRSAPLRSAPU19191
RSAP_PERFORM_EXTRACTION
1EVENTSBIE0001SBIE000160
START-OF-SELECTION

Environment
l
l

SupplyChainManagement(SCM)releaseindependent
Demand planning (DP)

Reproducing the Issue


1. Start the InfoPackage or the DTP.
2. After a while, the extraction job (starting with BI_REQ*) will turn red in transaction SM37.
3. You will see a shortdump in transaction ST22.

Cause
l

TheissueiscausedbyahighnumberofCharacteristicValueCombinations(CVC)inthePlanningObjectStructure(POS)and/orahigh
number of characteristics.
The overall number of entries collected into an internal table is the the number of CVC multiplied by the number of characteristics (including
navigational attributes).

Example:APlanningObjectStructurewith200.000CVCs,20characteristicsand10navigationalattributeswillcreate6.000.000(200.000*30)
entries in the internal table. At a certain point, the system memory is exhausted and the dump occurs.

Resolution
There are 2 possibilities to reduce the memory usage:
1.Incasenavigationalattributesareused:
Remove the navigational attributes from the DataSource. As they are linked to their basis characteristics directly, it's not necessary to have them in
the DataSource. This can be done as follows:
1. Determine the navigational attributes in the corresponding POS. This can be done by displaying the POS details in
transaction /SAPAPO/MSDP_ADMIN for example:

The navigational attributes are indicated by a double underline. In the example above, ZRZ_MAT__0ABC_CLASS,
ZRZ_MAT__0APO_APN01 and ZZRF_NAVI__ZWEIGHT are navigational attributes.
2. Enter transaction /SAPAPO/SDP_EXTR and change your DataSource.
3. The navigational attributes appear as basic characteristics in the change-screen. So check the technical names in order to find out which
entries contain navigational attributes.
4. In order to hide the navigation attributes, unflag the "Selection" Checkbox and flag the "Hide field" Checkbox.

5. Save the DataSource.


2 - In all cases: reduce the data volume
Restrict the data to be extracted in one InfoPackage (or DTP) and split the extraction process into 2 (or more) InfoPackages that will be executed
sequentially. Assuming you have 2 locations in your planning scenario, Location 1000 and 2000.
1.
2.
3.
4.

Call transaction RSA1.


Find your InfoPackage or DTP that extracts the data.
Navigate to the "Data selection" Tab.
Restrict the data by extracting Location 100 only (for example).

5. Create a 2nd Infopackage to extract Location 2000.


!!Attention!!: It is not sufficient to restrict the time horizon for the extraction (e.g. extract data for the current month only). By doing so, the system still
needs to read all CVC at once and the dump will not be resolved.
It is important to restrict the extraction by extracting data for a smaller number of CVCs (eg Plant 1000 only). Only this restriction does reduce the
memory usage for the corresponding dump.

Keywords
Extraktion,Speicher,Shortdump

Header Data
Released On 15.07.2013 12:54:44
Release Status Released to Customer
Component
SCM-APO-FCS-EXT Extraction
Priority
Normal

Category

Problem

Product
Product
Product Version
SAP Supply Chain Management SAP Supply Chain Management 2005
SAP Supply Chain Management 2007
SAP Supply Chain Management 4.0
SAP Supply Chain Management 4.1
SAP Supply Chain Management 7.0

Anda mungkin juga menyukai