We are writing a Java Web application that accesses SAP BAPIs using JCo. We are facing a problem when we have multiple simultaneous calls from different Web users using the same BAPI with the same parameters. Some of them get a message that "the material is locked by user XXX," where XXX is the SAP username used in JCo.
I am not sure whether this is an SAP issue, or a Java issue, or if I should handle this by implementing some kind...
of queue system, so that I will never have two users calling the same BAPI with the same parameters at the same time. Do you have any documentation on this problem?
This is totally application-specific (nothing to do with JCo or BAPIs in general). You need to talk to an application expert to determine whether the SAP customizing can be changed in a way that helps you. Otherwise, this is normal behavior to prevent multiple concurrent updates.
Dig Deeper on SAP Java and J2EE
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.