Is a COMMIT OK in PAI of user (sub)screen 100 in XQPL ???

[Former Member]

FM QPL1 allows for a user subscreen in the PBO for screen 200:<br><br>

<b>PROCESS BEFORE OUTPUT.<br>

...<br>

MODULE USER0001_OUTPUT.<br>

CALL CUSTOMER-SUBSCREEN USER0001 INCLUDING 'SAPLXQPL' '0100'.</b>

<br><br>

I have used the PBO module of the custom (sub)screen 100 in FM XQPL to do what the customer needs to do, but now the customer wants update ability out of this same custom subscreen.<br><br>

So here's the question - if I do a direct update in the PAI module of the subscreen 100 in XQPL, can I code a COMMIT in this PAI ?<br><br>

Thanks for whatever authoritative info anyone can provide.<br><br>

djh

[suresh_datti]

I have been through a slightly similar scenario & ended up putting the relavant code in another Report & SUBMIT that report from the PAI. This would isolate the two work processes & avoid any COMMIT WORK conflicts. Another option would be to put the code in a custom function module & call it as a background TASK or separate unit.

~Suresh

[former_member181923]

Suresh -

As usual, thanks very much. If the in-stream commit gives me problems, then I will code the FM as you suggest.

Another alternative is the following: since I will only be giving the user update ability when the subscreen is called in QA02, not in QA01 or QA03, maybe I don't need a commit at all.

Maybe my OpenSQL update will get committed as part of the general QA02 commit. At the moment, I don't see any need to commit my private update before the general QA02 commit, but I may be wrong about this ... I'll have to see how it goes ...

... but anyway, I'm sure your FM suggestion will work as the "last-resort" ...

Thanks again

djh