SY-BINPT in the background task

[Vera, Guillermo]

Hi Kim ,
 
  It looks like a pure ABAP problem , you must fulfill the BDC table in a suitable manner . The problem seems like transaction ME12 has different behaviours in test mode (SWO1) and in WF-Runtime mode . 
 
 
 Maybe this sdn thread  fix to your problem:
 
https://www.sdn.sap.com/irj/sdn/thread?threadID=733171 <https://www.sdn.sap.com/irj/sdn/thread?threadID=304593> 
 
I remark this lines : 
 
*------------------------------------------------------------------------------------
In addition, Specifically for BDC, if you wants to avoid the popup the following approach can be taken : 

Declare a work area of type CTU_PARAMS.
Fill the fields of CTU_PARAMS. The field NOBINPT should be set to 'X'.
This will set the SY-BINPT to space. So now the transaction which you will be calling will run in online mode. 

Example.

clear X_OPTIONS.
X_OPTIONS-DISMODE = 'E'.
X_OPTIONS-UPDMODE = 'S'.
X_OPTIONS-CATTMODE = ' '.
X_OPTIONS-DEFSIZE = ' '.
X_OPTIONS-RACOMMIT = ' '.
X_OPTIONS-NOBINPT = 'X'.
 X_OPTIONS-NOBIEND = ' '.


call transaction 'BP' using T_BDCDATA[] options from X_OPTIONS.

Note:
Do not use the MODE & UPDATE additions when you are using OPTIONS. The mode & update values are passed in the CTU_PARAMS structure.

{code}
CALL TRANSACTION 't_code' USING i_bdcdata[]
OPTIONS X_OPTIONS
MESSAGES INTO i_message.
{code)
*-------------------------------------------------------------
 
 
I hope this will be useful for you.
 
Regards.
 
Guillermo. 

________________________________

De: sap-wug-bounces at mit.edu en nombre de Kim, Ji Hoon
Enviado el: jue 19/06/2008 14:58
Para: SAP Workflow Users' Group
Asunto: SY-BINPT in the background task


Hello experts,
 
I'm creating a standard task (BACKGROUND) which calls ME12 transaction as BATCH INPUT (BDC).
When I test it in a dailog mode in SWO1 it works fine.
However, when I put it in the workflow template as background task. It generates a ABAP DUMP.
 
According to ABAP dump the system variable SY-BINPT is set to 0. And it processes an additional screen which was not recorded.
This is the root cause of the problem, I think.
 
When I debug it in the SWO1, the value of SY-BINPT is set to 1. (The additional screen is not appeared).
 
Can anyone provide any hint for further analysis?
 
Thanks 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080619/018eb872/attachment.htm