File to IDOC. How to handle locks at the receiver side?

[alejandro_sedanogonzlez]

Hi experts,

We 've got a problem with a File->IDOC scenario.

The sender file channel can receive multiple files at once, but, at the receiver side, processing those messages at the same time can generate locks.

How can we avoid those locks?

Maybe changing the QOS in the channel?

Thanks a lot for your help...

[MichalKrawczyk · Accepted solution]

Hi,

>>>>but, at the receiver side, processing those messages at the same time can generate locks.

a) you can serialize them at the receiver SAP backend (it does not mean EOIO from File adapter but only IDOC serialization)

b) you can schedule restart job for IDOC processing - the most common option - it will restart those with locks and they will get processed

>>>Maybe changing the QOS in the channel?

this is a VERY bad idea as all IDOCs will stay in yellow status in case of fails... very dangerous for production env unless you use content based EOIO (not supported instandard by PI, required a custom adapter module)

Regards,

Michal Krawczyk

[alejandro_sedanogonzlez · Accepted solution]

Hi,

It seems that the "serialization at the receiver" option is the one that fit our needs the best...

¿Do you know any link about how to do this?

Thanks for your help Michal..

[Former Member]

Hello,

You can also schedule a batch job for SAP Standard Program RBDMANI2 for reposting of failed idocs which will ensure that they are posted.

Regards

[Former Member]

Hi Alejandro,

As you are trying to post more messages into SAP system through IDOC's there is a possibility to get the table locked.

Try to process the messages in serialized order, the option we have at the receiver agreement.

[Former Member]

Hi Alejandro Sedano Gonzalez

could you please explain your process in detail. sender  side have multiple files and receiver side is only single IDoc. or multiple Idocs?.  by the way at the receiver side, processing those messages at the same time can generate locks.

1) if you didn't specify the receiver side then data generate the locks

<REMOVED BY MODERATOR>

<COPIED CONTENT - READ RULES OF ENGAGEMENT BEFORE POSTING>

Message was edited by: Prateek Raj Srivastava

[alejandro_sedanogonzlez]

Thanks for your reply,

Each file in the sender, is an idoc on the receiver. Processing multiple idocs simultaneously at the receiver generates the locks.

Due to other problems, this lock stuff will have to wait until the next week.

we'll see then wich option fit our needs the best, I think the job might be the chosen one.

Thanks a lot for your help.

[Former Member]

okay Thanks

[former_member190624]

Hi,

Correct me if i got your requirement wrongly , you are facing  problem to pick the files from source directory since there are many files with same same file name? or any problem in processing at  receiver end (ECC)

Regards

Hari.

[alejandro_sedanogonzlez]

The sender channel picking more that one file at the same time (with the same name pattern) is ok for us.

The problem comes at the receiver side, because processing those files (idocs) at the same time, may generate locks.

Sorry about my English and thanks for the answer.