Trigger report program if Z table field is modified/created

Question

Hi,
I have a requirement where i want to run the report program ONLY if a particular field ( Dispatch date ) is modified or updated of a 'Z' Table ( Custom Table ).
The report program would fetch data from the same 'Z' table only for those records which are modified/updated. This data is then transferred to an application server.
1. How should i trigger the report program for the above requirement.
2. If a background program is to be created, then what should be the trigerring criteria & where it should be defined.
3. Do i need to set any change pointers etc.
Pointers to the above requirement would be very helpful.
Thanks in advance,
Best regards,
Prashant

Answer 1

hi prashant,
   i'm working on a similar query as that of ur's.
  see the logic is as we proceed in ur case is DISPATCH DATE say are to be modified in the process of inserting 0r changing the contents of a ZTABLE.
so here the logic would be
loop at itab.
MODIFY ZTABLE FROM TABLE ITAB.
endloop.
This is the key reference in our logic .
now it is known that u have a ZTABLE with dispatch date
here the data element will be DATUM .
now in the ZTABLE go to DISPATCH DATE filed i.e its DATA ELEMET double click on data element  DATUM .
now if u see here there will be a tick called as Checkbox on change document which is enabling the CDHDR and CDPOS.
*if its not checked get it checked in .
This is the source to the logic.
now what u need to do in ur logic part is
1. collect all the entries of the table.
(im not sure how many entries are there but try to get all the primary keys + one or two more fields so that the time is saved . this we do to check.
2. before the modify comes into affect see if u can store all the content of the table i.e step 1.
3.lets say we have modified the ZTABLE.
4.now collect all the entries i.e newly modified into new inttab with same logic as the basic primary key configurations + two fields .
5. let the two internal tables be compared and based on the comparision derive a new internal table as follows .
REPORT ztemp .
TYPES: BEGIN OF line,
          brand(10) TYPE c,
          rate(3)   TYPE p DECIMALS 2,
          gender(1) TYPE c,
          sno       TYPE i,
          desc(30)  TYPE c,
        END OF line.
DATA: it_lines_1 TYPE TABLE OF line
                  WITH KEY brand
                           rate
                           gender,
       wa_lines_1 LIKE LINE OF it_lines_1.
DATA: it_lines_2 TYPE TABLE OF line
                  WITH KEY brand
                           rate
                           gender,
       wa_lines_2 LIKE LINE OF it_lines_2.
DATA: gi_counter TYPE i.
START-OF-SELECTION.
   PERFORM fill_it_line_1. " not included; tested with your 4 records
   SORT it_lines_1.
   CLEAR gi_counter.
   LOOP AT it_lines_1 INTO wa_lines_1.
     wa_lines_2 = wa_lines_1.
     ADD 1 TO gi_counter.
     AT END OF gender.
       IF gi_counter > 1.
         APPEND wa_lines_2 TO it_lines_2.
       ENDIF.
       CLEAR gi_counter.
     ENDAT.
   ENDLOOP.
This only works if you are able to define the fields of the internal table in this order, so with the key fields first in the right order. Otherwise the AT END OF will not work.
6. now if u can reach upto here then we need not create a background program .
7. u are exactly right change pointers will have to come into picture .
8 .then comes the picture of moving this content to application server using datasets etc.
hope this helps u in building the logic .
i would like to hear from other developers too in this regard.
Thanks and regards,
vijay.