ECC 6 Upgrade from 4.6C : BDC code not working with WF-BATCH

[Ramki Maley]

Sandy,

As Paul suggests, if a BAPI exists, that is your best option.
BTW, have you selected the 'Simulate Background Mode' checkbox in SHDB 
while creating your recording? If not, you can try creating a new 
recording with the Simulate selected. You can also 'Process' your 
recording in Simulate BG mode with SHDB and see if you get a similar error.

Cheers,
Ramki.



On 2/17/11 6:34 PM, Paul.Bakker at osr.treasury.qld.gov.au wrote:
> Sandy,
>
> I assume you have already checked to see if this BDC can be replaced by a
> call to a function module or a BAPI (BAPI_ISU*) ?
>
> It gets very hard to keep using BDCs in ECC 6.....many sites no longer use
> BDCs at all.
>
> cheers
> Paul
>
> PS If I remember rightly, SAPMSSY0 120 is a list processing screen.
>
>
>
> From:	Sandy<sandysydney at gmail.com>
> To:	sap-wug at mit.edu
> Date:	18/02/2011 08:57 AM
> Subject:	ECC 6 Upgrade from 4.6C : BDC code not working with WF-BATCH
> Sent by:	sap-wug-bounces at mit.edu
>
>
>
> Hello Guys,
> We are upgrading to ECC 6 from 4.6C. We have encountered a very strange
> problem with user WF- BATCH.
>
> There is Background method that uses a Call Transaction BDC for Transaction
> EL37 (ISU Meter Read Reversal process) in one of workflows.Now if this
> method is marked as Dailog, this BDC works (reverses the meter read : with
> no message in BDC return table). This method works fine for any dailog user
> but NOT FOR WF-BATCH USER when executed from WF. We have tested it
> separately in SWO1 and also in SE37 by keying in the desired container
> values and it works but when the WF is executed and this method is executed
> in background by WF-batch, BDC fails to do the desired operation and we
> have only one message in BDC return table : "No batch input data for screen
> SAPMSSY0 0120" and this a SUCCESS message (Message ID: 00 and Message no
> 344). Since WF-batch is non dailogue user, we cant do a MODE A selection
> with BDC to see exactly which screen are poped up at runtime.
>
>   In 4.6C, EL37 transaction involved a ABAP list display but in ECC 6, this
> transaction has a ALV grid display with custom containers. We have built
> the BDC's for EL37 in ECC 6 in SHDB and successfully tested it for both
> Dailog users and WF- Batch by creating a session and then executing it in
> background in Transaction SM35. Does this means that BDC using session only
> works for WF-batch and not Call transaction in SOME cases? BDC invovling
> ALV has some problems with WF-batch since it is a NON dailouge user ?
>
> Now why this BDC method is not working with WF- Batch when called online?
> is there any authorisation issue? We have even checked that, its look fine.
> Can we make WF-Batch dailoge user from system user since this method works
> well for dailouge users: Making a WF-Batch dailogue users would have some
> implications or NOT?
>
> Could you please help me resolving this issue?
>
> Much appreciated.
>
> I have found a SDN thread similiar to my issue but information is not
> enough:
> https://forums.sdn.sap.com/thread.jspa?threadID=1246633&tstart=0
>
>
> Thanks&  Regards
>
> Sandy
>   _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> ******************************************************************************************************************************************************
>
> Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.
>
> The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.
>
> ******************************************************************************************************************************************************
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110218/ebcc54a5/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: moz-screenshot-12.png
Type: image/png
Size: 10488 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20110218/ebcc54a5/attachment.png