RL_TA archiving run time error

[Former Member]

Dear Experts,

   I'm unable to give more TO numbers while archiving. As the log is getting full, i'm getting run time error. It is allowing if less number of TOs are given. How should i clear this? I want to run many at once.

Thanks in advance.

Regards,

Shanthi

[Former Member]

Dear Experts,

   I'm unable to give more TO numbers while archiving. As the log is getting full, i'm getting run time error. It is allowing if less number of TOs are given. How should i clear this? I want to run many at once.

Thanks in advance.

Regards,

Shanthi

[Former Member]

Hi Shanti,

Can you please let me know what is your archiving object!

If you are getting the 'DATASET_WRITE_ERROR'  it has occurs because of the space problem

Please share some more information!

[Former Member]

Hi,

   I'm using "RL_TA" archiving object used to archive TOs (Transfer Orders). I have to archive around 3 lakh Tos. I'm just testing in Test Mode and checking. So it is not allowing me to archive all at once. The job is getting cancelled. It is not even allowing 5,000 TOs. When i gave 1000, there are no issues.

[former_member187748]

Hi Shanthi,

please once see the SAP note 1137327, which is used for archieving program

Please see this thread, which might help you in resolving your issue.

Poor performance when archiving RL_TA and RL_TB objects | LinkedIn

[Former Member]

Hi Shanti,

Check the program is available in your system: RLREOT00SN

If yes try try to replace the Read Program in transaction:  AOBJ

Proposal: its good practice to archiving the jobs in parallel

Never try to schedule the job in a single stretch, Please make the multiple variants and start the parallel processing!

for example you have 4 warehouse numbers: better to schedule 4 jobs parallel!

If you have one warehouse number: make the variants based on TO number range

Make the settings of automatic deletion- its very important

Rg Kiran

Message was edited by: Matthew Billingham - removed predictive text error which indicated a house of ill-repute.

[Former Member]

I have divided based on warehouse number. Still each Warehouse has many TOs around 1 lakh for each.

[Former Member]

Hi Shanti,

This is the standard program! I don't think so we can investigate more

Is it possible to reduce the resident time and then have the jobs!

This is also one parameter, where we can reduce the hits!

    CLEAR TANUM_LOW.

   QDATU_HIGH = SY-DATUM - LAUFZEIT.

*   Holen aller TA-Nummern aus LTAK für die Lagernummer

    select tanum from LTAK into table lt_ltak_key

      where lgnum = it300-lgnum

        and tanum in rt_tanum

        and kquit = con_x

        and qdatu <= qdatu_high.

or you can copy the read program to customize program! can add the more selection for user friendly to run the job

Rg, Kiran

[Former Member]

I got the error "Internal session terminated with runtime error DBIF_RSQL_INVALID_RSQL"

[Former Member]

It is a standard error , when you are providing inputs more than 4500 entries you will get this error, try to restrict the no of TO's to 4500.

[Former Member]

There are around 3 lakh TOs to be archived. Is this the only way?

[Former Member]

Hi Shanthi,

My experience I could this way only! may be little bit time consuming and monitoring is required! need to be careful on variant selection and sequence!

[Former Member]

Sorry, but this is the only way..!!

[JL23]

Maybe you should explain in more detail how you maintained your selection screen.

There is no need to enter any TO number in the selection screen at all.

The warehouse number and the residence time is just enough for selection.

further you should check the technical settings in customizing  for archiving object RL_TA

I use for maximum size of an archive just 80MB. if  you have more data, then SAP will split the archive

Do not enter a maximum number or records, especially not 3 lakh

[Former Member]

Hi,

   The problem is not in giving input. When i gave warehouse number as input, the job got cancelled as the given warehouse has more TOs. It as allowing upto 9,000 TOs at a time.

Regards,

Shanthi

[JL23]

I archive about 100000 each month with just one job. How poor would a software like SAP be if it could not archive more than 9000 TOs per job?

You had not given any information about your setup, about your selection, about your joblog, about a dump. About the sequence your are executing this task.

How do you expect help if you make a secret around everything?

If you are seeking for help, then it should be your own interest to provide as much info as you can.

I just remember one case where SAP really has problems, this is when WM inventory document has more than 5000 items

for this case SAP created OSS note  524716.

But if yours is a similar case can only be known when you give more input

[Former Member]

Actually when i gave Warehouse number and more number of TOs as input, it didn't work. But when i gave just Ware house number without any TOs as input it is archiving. Thanks for the info my issue is solved.

Regards,

Shanthi

[Former Member]

All the TOs are getting archived when i specify warehouse number. But when i give many TOs in the selection, the job is getting cancelled. My issue is cleared. Thank you all.

Regards,

Shanthi

[Former Member]

The write job cant process more then 9000 records as input in the selection screen, its a standard limitation.

Try to provide a range and archive.