FUNCTION 'SWE_EVENT_CREATE' in background

[Soady, Phil]

Thierry,
 
Batch input stops at "commit work."
Normally dialog mode continues.
In dialog mode the next screen change cause an implicit
commit work. Every screen change is a free Commit work.
Hence a simple dialog abap with one line of code works.
 
insert table x
 
Due to the free commit.
 
Your batch program may or may not get this "free" commit work.
 
It is technically possible for a transaction to not be background
BDC processable. Due to the way BDC reacts to commit work.
 
Try, calling the bdc in mode "E" instead of "n"
or call function HR_MAINTAIN_MASTERDATA instead of using BDC.
Even better use FUNCTION BAPI_BASICPAY_CHANGE (object - EmployeeBasicpay)
 
Beware of BDC !!!
 
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Thierry Logiest [mailto:logiest_thierry at hotmail.com]
Sent: Thursday, 17 October 2002 5:31 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: FUNCTION 'SWE_EVENT_CREATE' in background
 
 
Dear all,
 
I have been surprised yesterday with the following phenomenon :
 
We generate events with standard FUNCTION 'SWE_EVENT_CREATE'. This function is called indirectly from table T779X for infotype 8. This works in foreground but when the function is called through a BDC session (i.e. the change to infotype 8 is made through a batch-input) although the function is called correctly (and commited)  the event is not generated (SWEL is empty). We proved that the code was called correctly by running the batch-input in foreground.
 
Any ideas would be very welcome.
 
Thank you.
 
Regards, Thierry
ABAP-Workflow-HR SAP Certified Senior Consultant
 
 
 
 
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963