Custom Business Object Code missing in EBP 3.5

[Susan R. Keohan]

Hi all,
 
Our EBP development box (EBP 3.5) is on the following support pack levels:
SAP_BASIS       620     0016    SAPKB62016
SAP_ABA 620     0016    SAPKA62016
BBPCRM  350     0004    SAPKU35004
PI_BASIS        2002_1_620      0006    SAPKIPYF56
ST-A/PI 01C_CRM315      0000         -
ST-PI   003C_620        0000         -
WP-PI   500_620 0003    SAPKINE323
 
Today, a workflow developer was editing custom methods for the object ZBUS2121 (Shopping Cart).
When she saved the object, and went back in to look at it, all custom code for methods and
attributes was gone.  The initial screen in SWo1 (expanding the attributes and methods) still shows
our custom methods and attributes, but if you select one, and press 'program', you will only see the
following standard boilerplate:
 
*****           Implementation of object type ZBUS2121             *****
 
 
INCLUDE <object>.
 
 
BEGIN_DATA OBJECT. " Do not change.. DATA is generated
 
 
* only private members may be inserted into structure private
 
 
DATA:
 
 
" begin of private,
 
 
"   to declare private attributes remove comments and
 
 
"   insert private attributes here ...
 
 
" end of private,
 
 
   BEGIN OF KEY,
 
 
       REQUIREMENTREQUEST LIKE REQHEAD-REQNO,
 
 
   END OF KEY,
 
 
       PROFITCENTERLIST LIKE REQACCT-PROFIT_CTR OCCURS 0,
 
 
       CREATEDBYUSER LIKE WFSYST-ACT_AGENT,
 
 
       ALLSTOCKINDICATOR LIKE BOOLE-BOOLE,
 
 
       ALLFREECHARGE LIKE BOOLE-BOOLE,
 
 
       INTERNALORDEREXISTS LIKE BOOLE-BOOLE,
 
 
       LLTOTALVALUE LIKE REQHEAD-TOTAL_VALUE.
 
 
END_DATA OBJECT. " Do not change.. DATA is generated
 
 
 
We now have to recover this object from backup.  The developer is certain that she did not
accidentally delete the business object code herself.
 
The question is, has anyone encountered this before ?  If so, did you ever identify the
circumstances under which this occurred, and are you able to prevent a recurrence ?
 
Tangent:  At roughly the same time, the ITS Server was being upgraded to Windows 2000, SP4.  But I
don't believe this was the cause.
 
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu