0recordMode setup doubts

Question

Hello
I still cant figure out how to make it work a Delta DS which needs to control deleted records. Up to now I have:
1. defined 0recordmode in Transfer Structure  but is not in my ODS (do I need to define it there too?)
2. Read in related threads that code for filling 0RecordMode = D should be in Start Routine between IP and ODS ??? is this OK for handling individual records marked as deleted in r3?
3. my delta Ds is type AIE (functional module F2)
do I need to do any other settings or modifications ?
appreciate the most of your support!

Answer 1

hello Srini
My start routine is suppose to only move D to 0recordmode whenever incoming (DS) delete_field is = to "X".
The problem now is that is mixing dates (I use last_modif_date as delta) but in ODS date is the creation date ???
If I have in psa:
document-itemmater--creatdate-modifdate-ammount-- deleteind
400030-----10--6812---25072006-0811200710uni--
x
400030-----30--6812---25072006-0811200710uni--
it appears in ODS as
document-lineitemmater--modifdate-ammount---- deleteind
400030-----10--6812---2507200610uni--
400030-----30--6812---0811200710uni--
and in Icube as
document-lineitemmater--modifdate-ammount---- deleteind
400030-----10--6812---25072006-- (-10uni) -
400030-----30--6812---08112007--  10uni    -
(note that also lineitem 30 I did not change but when modifying in R3 for lineitem 10 it changes the last-modif-date for all material with same code (in this case 6812) so it appears as modified on delta extract....
My code in the start routine is as follows: (appreciate your support !)
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line  -
Communication Structure ZD_2_CVC_CHAR
DATA: BEGIN OF g_it_data_package OCCURS 0.
        INCLUDE STRUCTURE /bic/cszd_3_zpic_zpdvymas.
DATA: END OF g_it_data_package.
$$ end of global - insert your declaration only before this line   -
The follow definition is new in the BW3.x
TYPES:
  BEGIN OF DATA_PACKAGE_STRUCTURE.
     INCLUDE STRUCTURE /BIC/CSZD_3_ZPIC_ZPDVYMAS.
TYPES:
     RECNO   LIKE sy-tabix,
  END OF DATA_PACKAGE_STRUCTURE.
DATA:
  DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
       WITH HEADER LINE
       WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
  TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
           MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
           DATA_PACKAGE STRUCTURE DATA_PACKAGE
  USING    RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
  CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line        -
fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
to make monitor entries
Move the data to a new internal table
  g_it_data_package[] = DATA_PACKAGE[].
  CLEAR: DATA_PACKAGE.
  REFRESH: DATA_PACKAGE.
  CHECK g_it_data_package[] IS NOT INITIAL.
Update the delete Indicator
  LOOP AT g_it_data_package.
    IF g_it_data_package-/bic/zd_picwhs = 'X'.
      g_it_data_package-recordmode = 'D'.
    ENDIF.
      MOVE-CORRESPONDING g_it_data_package TO DATA_PACKAGE.
      APPEND DATA_PACKAGE.
      CLEAR DATA_PACKAGE.
  ENDLOOP.
if abort is not equal zero, the update process will be canceled
  ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.