"BAPI_OBJCL_CHANGE " is locking customers

[satya_devaraju]

HI,

We are passing data from TIBCO into BAPI_OBJCL_CHANGE . It is locking the some customers sometimes. We can't able to replicate the scenario when it is locking. It is throwing error. "Account XXXXX is currently blocked by customer XXXX"

Need your suggestions on how to solve this

regards,

Rao

[Former Member]

You can do debugging by keeping external debuggin point. In settings -> debugging give the user id and select IP matching. Keep break point in FM so that whenever the data comes from TIBCO break point gets hit and you can do the analysis. I think you have to do commit after calling bapi are you doing that.

Call the standard BAPi in a custom bapi and do the commit. Call the custom bapi from TIBCO.

[satya_devaraju]

BAPI commit is already present. Inspite of that we are getting this problem

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = c_x

IMPORTING

return = return.

[Former Member]

Hi,

AFter calling the bapi "BAPI_OBJCL_CHANGE", call Trnaction commit and wait. it may serv your purpose.

call 'BAPI_OBJCL_CHANGE'
.......
.......
call 'BAPI_TRANSACTION*COMMIT' and wait.

regards,

Naveen

[satya_devaraju]

BAPI commit is already included - even then we have this problem

[Former Member]

Hi,

Try like this,

EXAMPLE:

CALL FUNCTION 'BAPI_OBJCL_CHANGE'

EXPORTING

objectkey = objectkey

objecttable = objecttable

classnum = classnum

classtype = classtype

status = status

standardclass = standardclass

changenumber = changenumber

keydate = keydate

no_default_values = no_default_values

IMPORTING

classif_status = classif_status

TABLES

allocvaluesnumnew = numnew

allocvaluescharnew = charnew

allocvaluescurrnew = currnew

return = return_bapi_objcl_change

Then...

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = 'X'

IMPORTING

return = bapi_return.

Regards,

Neelima.

[satya_devaraju]

The solution is in TIBCO , the BAPI call has to be made single threaded. Previously it is multi threaded.