topic Re: The IDOC INBOUND function is locking an object in Application Development and Automation Discussions

The IDOC INBOUND function is locking an object

Former Member — Wed, 04 Apr 2007 08:22:54 GMT

Hi ,

I have created a wrapper bapi around IDOC_INPUT_SHPMNT , this is because i need to change the shipment using a BDC. No the problem is that once the control comes out of IDOC_INPUT_SHPMNT the locks are still maintained on the shipment.Now is this beacuse i am using WE19 to test the program or will i have manually realease the lock from this. Any pointers with function modules will be helpful.

Re: The IDOC INBOUND function is locking an object

Former Member — Wed, 04 Apr 2007 08:26:32 GMT

IDOC_INPUT_SHPMNT will be locking the shipment. The lock will not be released until the IDoc has finished processing.

You could remove the lock yourself.

Can you not use a user exit in IDOC_INPUT_SHPMNT to provide your solution instead of running a BDC yourself. If your BDC fails how will this error be reported back to the IDoc. You would then not be able to re-process the IDoc either.

Re: The IDOC INBOUND function is locking an object

Former Member — Wed, 04 Apr 2007 08:28:07 GMT

YOu can use a commit work or rollback work statement after the call to the IDOC_INPUT_SHPMNT to avoid locks.

Regards,

Ravi

Re: The IDOC INBOUND function is locking an object

Former Member — Wed, 04 Apr 2007 08:29:26 GMT

is there a user exit in this function module?

Re: The IDOC INBOUND function is locking an object

Former Member — Wed, 04 Apr 2007 08:34:14 GMT

Do a search in the function for the text 'CUSTOMER FUNCTION'.

There will be several I would suspect.

I would not be using a commit work to remove the lock. That is a tad bit dodgy.