Run time error: mass deletion of locations in APO

[Former Member]

Hi,

While deleting the locations /SAPAPO/DELETE_LOCATIONS (after setting the deletion flags in MASSD header: Location: deleiton flag) in background, i get the following run time error.

If someone has fixed this before please help.

Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED

The internal table "???" could not be further extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "Session memory"

Row width: 2890

Number of rows: 0

Allocated rows: 1492

Newly requested rows: 4 (in 372 blocks)

Termination occurred in the ABAP program "/SCMB/SAPLMDL_LOCATION" - in

"MAP_DATA_MULTI".

The main program was "/SAPAPO/DELETE_LOCATIONS ".

In the source code you have the termination point in line 435

of the (Include) program "/SCMB/LMDL_LOCATIONF06".

The program "/SCMB/SAPLMDL_LOCATION" was started as a background job.

Job Name....... "/SAPAPO/DELETE_LOCATIONS"

Job Initiator.. "LR249J"

Job Number..... 03254500

code extract

432 LOOP AT ls_data-adrs INTO ls_adr.

433 IF <fs_adrs> IS ASSIGNED.

434 MOVE-CORRESPONDING ls_adr TO <fs_adrs>.

>>>>> INSERT <fs_adrs> INTO TABLE <ft_adrs>.

436 ENDIF.

437 ENDLOOP.

438 ENDIF.

439

440 INSERT <ls_data_out> INTO TABLE et_data.

I did not find any notes with key words suggested in the log. I don't quite understand ABAP debugging

Regards,

Loknath

[tibor_nagy · Accepted solution]

Dear Loknath,

the mentioned error in //delete_locations can occure if you are trying to delete a huge volume of datas (locations) at once.

Please try to delete in smaller packages with less of 1000 of locations at once to avoid such memory problems.

Best regards,

Tibor

[Former Member · Accepted solution]

Hi Tibor,

This happens even if i delete in piecemeal. In any case my locations are much less than 1000.

Now this problem is solved by deleting the tables entries entirely and starting the client build up again.

These deletion activities were resultant of clinet copy from another system.

Thanks for the reply.

Regards,

Loknath

[keiji_mishima]

Hi Loknath

As DB49 mentioned, this is related to memory setting.

I guess if you look for the used memory area in the ABAP dump,

you may see how much memory was consumed.

If it already consumed around 2GB, you have better to execute

MASSD with more less data.

If it is not, You have better to ask your basis people to check

following parameters. (By extending these parameter, one user

can use much more memory space).

-Allowed memory space for one user session.

ztta/roll_extension

em/address_space_MB (Only when you use windows OS)

-Allowed memory space for system wise.

em/initial_size_MB

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

abap/heaplimit

Best Regards

Keiji

[Former Member]

Lok,

TSV_TNEW_PAGE_ALLOC_FAILED is a generic error meaning that the program has exceeded one of the space limitations set up by your Basis Admins and Database Admins. You will usually see this a lot in test systems, which are typically sized smaller than production systems.

Long term, ask your Basis guys to find the limiting factor and 'make it bigger'. Short term, you need to run the offending program with a smaller selection set, if possible. For your program, try one location type at a time. If this doesn't work, try subset ranges of actual location names.

Regards,

DB49