Re: BAPI runs in SE37 but not from MII using JCo

Hi all,

firstly to clarify the logic in the custom BAPI:

1. Receive IL Data
2. Loop through all Inspection Points and create a record of the Sample ID (placeholder for the results)
   1. If Sample is already there, then don't try to re-create it.
3. Commit the above step
4. Clear cache (it's more to try fix the problem rather than part of the logic)
5. Loop through all the results for each sample and Record the results against the sample created in step 2
6. Commit the above step

If anything fails, the rollback will rollback everything (except the sample place holders as these have already been commited).

I call the BAPI using the JCo action blocks and then depending on the success / fail status, call a commit / rollback action.

Sam, I'm not sure where the option is to Auto Commit - so can't confirm either way.

Image may be NSFW.
Clik here to view.

The key thing here is that the process works from SE37, so there's something different when the BAPI is called from MII - which is different to what I'd imagined it to be.