topic Re: CL_BCS is a commit work required for output? in Application Development and Automation Discussions

CL_BCS is a commit work required for output?

former_member195355 — Fri, 14 Feb 2014 16:14:10 GMT

Hiya,

I'm using CL_BCS in document output.

Basically after the smartform is created I have code which sends an email and then the smartform output program finishes

i.e. my code is after the Smartform function module that creates the form.

My question is that I'm not using a commit work after using CL_BCS and it seems to be working fine - sending emails, attachments etc.

However whenever I read things on SCN they say there must be an explicit commit work when using CL_BCS?

Am I missing something as it is working fine for me?

Re: CL_BCS is a commit work required for output?

Abhijit74 — Fri, 14 Feb 2014 16:46:22 GMT

This message was moderated.

Re: CL_BCS is a commit work required for output?

Former Member — Fri, 14 Feb 2014 18:14:44 GMT

It is possible that your process is somewhere issuing the explicit commit work.

A runtime trace can confirm that.

Re: CL_BCS is a commit work required for output?

Former Member — Sun, 16 Feb 2014 10:21:30 GMT

Hi Robert,

As mentioned by Manish, the process itself is issuing the explicit commit work.

I assume you trigger the output immediately hence the commit work occurs.

Try sending it using applications own transaction option.

Regards,

Ankur Parab

Re: CL_BCS is a commit work required for output?

Former Member — Sun, 16 Feb 2014 11:32:27 GMT

Hi Robert,

After the LUW, there will anyway be an implicit commit work. This would trigger the mail even if you have not explicitly specified it.

Re: CL_BCS is a commit work required for output?

Former Member — Sun, 16 Feb 2014 12:29:04 GMT

Implicit commit is not enough. Documentation says explicit commit is required because of persistence layer. Perhaps this is why all the BCS_EXAMPLE_* reports have commit work statement.

Re: CL_BCS is a commit work required for output?

former_member195355 — Sun, 16 Feb 2014 18:31:55 GMT

Hello everyone,

Thank you for your helpful replies.

The smartform output program, with the email at the end of it is working so perhaps there is an explicit commit somewhere...

Manish,

could you just let me know how I could do a trace on an output program?

Would I go into RSNAST00, start ST05/SE30 and then run the output?

I think I'll have a lot of code to search through...

Would there be a line that said COMMIT WORK or would I be looking for something else?

Thanks!

Re: CL_BCS is a commit work required for output?

former_member195355 — Sun, 16 Feb 2014 18:33:59 GMT

Hi Ankur,

Thank you for the reply.

Could you please explain why sending it 'using applications own transaction option' is a useful thing to test?

Thanks!

Re: CL_BCS is a commit work required for output?

Former Member — Mon, 17 Feb 2014 05:17:32 GMT

I wrote commit work statement in an empty program and ran it through SAT transaction.

In Trace results, commit work statement can be seen in Hit list.

Since your trace would have lot of data, hit list can be filtered to show data related to Data Accesses Internal.

As a test, you can compare trace of a BCS_EXAMPLE_* and its copy without commit work to see the difference.

Re: CL_BCS is a commit work required for output?

Former Member — Mon, 17 Feb 2014 05:28:03 GMT

Hi Robert,

When output immediately is selected, the driver program is started in an update task.

When you trigger the output using applications own transaction, you need a separate transaction for example like VT70 in case of shipment, to trigger the output.

Regards,

Ankur Parab

Re: CL_BCS is a commit work required for output?

Former Member — Mon, 17 Feb 2014 06:51:53 GMT

Hi Robert,

In my case, (CL_BCS for Email funcitonality) COMMIT WORK was required while the Program being run in foreground.

If it is running in background, it works fine without COMMIT WORK. It throws a dump if we use commit work for a batch program.

-Sowmya

Re: CL_BCS is a commit work required for output?

former_member195355 — Mon, 17 Feb 2014 12:53:21 GMT

Hi Sowmya,

Thanks for the reply and that sounds like he scenario we're having - If I explicitly state the commit work it dumps. Otherwise whenever I process the smartform output it works fine without the commit work.

So I think it is safe to leave it out - unless anyone disagrees.