Routing_create Idocs crash server

[Former Member]

Hello Guys,

I´m using the LSMW to migrate 140.000 routings...

As soon as the Idocs are created, they 'want' to be processed immediately... (This means that I don´t have to start to 'process' the Idocs. Somehow these Idocs want to be processed, the moment they were created)

As a consequense they seize every single thread available on the server...

After less than 15 minutes: the server is blocked,

after an hour or so: the server doesn´t respond anymore

I tried to create packages of Idocs (each package containing 100 Idocs), but that doesn´t help eather...

Can anybody help me?

(It would be great if somebody could tell me how I can turn off the auto-processing functionality...)

Thanx!

Greetz from Germany to the world!

[Former Member]

Hi,

To turn off the autoprocessing , go to the partner profile (Transaction: WE20). If the partner type is LS and click on the partner name ( Destination logical system). You must be seeing all the message types in the outbound parameter. By clicking the routing message , you can see two types of output mode:

1) Collect idoc

2) Transfer Idoc immed..

If you don't want the autoprocesing , click on first option and go to BD87 transaction code for further processing of IDoc.

Regards,

M.Saravanan

[Former Member]

To turn off the autoprocessing , go to the partner profile (Transaction: WE20). If the partner type is LS and click on the partner name ( Destination logical system). You must be seeing all the message types in the outbound parameter. By clicking the routing message , you can see two types of output mode:

1) Collect idoc

2) Transfer Idoc immed..

-> Thanx a lot... I ´d forgotten about that!!!

[Former Member]

hi check with the lock object for idoc creation in

server

[Former Member]

Hi Sukumar,

check with the lock object for idoc creation in

server

-> Could you define a bit more precise, so I can explain this to our Server-admin? It really sounds like the solution I need...

Thanx a lot for your reply!!!

[Former Member]

Come to think of it,

Acutally, the problem is the Idoc Processing, not the Idoc creation...

Is there a possibility to enter a number of threads that can be used instead of the Idoc-processing just using all threads available?

Cheers,

Pieter

[laxmanakumar_appana]

Hi,

Use : Collect idoc option at partner profiles (WE20), after that use program RBDAPP01 and create a batch job to process these 64 status Idoc's. set this batch job to be run periodically means every hour or every 5 hours.

in this case you should not face any Idoc processing problem.

Regards

Laxman

[Former Member]

Hi Laxman,

Hmmm not a bad idea... Wouldn´t work though... because it would just try and process my 140.000 Idocs and flood the server...

What I can try is create numerous jobs (using a batch input).

Each Job schould process let´s say: 200 Routings

Every job should start 5 minutes later as the previous one....

Thanx!

[Former Member]

Hello Pieter,

Although the thread I just read is a little bit ancient, I just thought I'd give a shot.

I cannot seem to fill the Idoc in question properly in order to create multiple routings with parallel and / or alternate sequences.

The system always can process the Idoc succesfully, but the values for parallel sequences are not where they should be..... routing is created..... but no sequences.

Perhaps you (or others) have an answer.... maybe you can send me a sample (well filled) Idoc (routing_create).

thnx in advance!

Marcel