Splitting the date based on the selection screen input

Hi all,
In the Selection screen of my report i had maintained two fields
SELECT-OPTIONS  : S_DATE    FOR TPCDATE-FROM_DATE.
PARAMETERS      : P_NUMBER  TYPE ZMMAREA-NUMBER.
I need to code such that
S_DATE should be splitted into P_NUMBER times
for example if P_NUMBER is 4 i need  S_DATE should be splitted into 4 equal parts or near by equal parts
                    IF  P_NUMBER is 2 i need  S_DATE should be splitted into 2 equal parts or  near by equal parts
Please suggest me the code of if any Function module exists fot this date splitting
Thanks in advance
Ajay.D

though date question are not allowed, this requirement sounds little different.
you can take a difference between those days by: S_date-high - S_date-low.
then divide the difference by p_number. now you get the split positions.
now in a do enddo you can negate the dates by the split amount you got from the divisions.
like...
PARAMETERS: num type i.
select-OPTIONS: s_date for sy-datum.
data : gv_split type i, gv_temp type sy-datum.
gv_split = s_date-high - s_date-low.
gv_split = gv_split / num.
gv_temp = s_date-high.
do num times.
  gv_temp = gv_temp - gv_split.
  WRITE / gv_temp.
enddo.

Similar Messages

  • I've to extract the data based on the sysdate...like today dd is 11,

    BM_PERF is the table name and
    BM_PERF_YR,BM_PERF_MONTH,BM_NOP_CT_1........BM_NOP_CT_31 are the column names.
    I've to extract the data based on the sysdate...like today dd is 11
    so i've to get data from BM_NOP_CT_11 and the column names changes dynamically based on the sysdate. don't use any procedures and functions.

    You could always pivot it into a more convenient form for querying:
    WITH t1 AS
         ( SELECT 2008 AS yr, 4 AS mnth
                , 20 AS dy1
                , 10 AS dy2
                , 15 AS dy3
                , 1  AS dy4
                , 17 AS dy5
                , 99 AS dy6
                , 55 AS dy7
                , 45 AS dy8
                , 33 AS dy9
                , 22 AS dy10
                , 74 AS dy11
                , 35 AS dy12
                , 62 AS dy13
                , 24 AS dy14
                , 85 AS dy15
           FROM dual )
       , t2 AS
         ( SELECT yr
                , mnth
                , sys.DBMS_DEBUG_VC2COLL
                  (dy1,dy2,dy3,dy4,dy5,dy6,dy7,dy8,dy9,dy10,dy11,dy12,dy13,dy14,dy15)
                  AS day_data
           FROM   t1 )
    SELECT t2.yr, t2.mnth, sys_op_ceg(t2.day_data,5) day_value
    FROM   t2;
            YR       MNTH DAY_VALUE
          2008          4 17
    1 row selected.Note that SYS_OP_CEG (first discovered by Padders) is undocumented and unsupported - for production code you'd need to pick the collection row using a WHERE clause, and for that you'd need a custom object and collection type with an attribute to hold the day number.
    Message was edited by:
    William Robertson
    ...like this:
    CREATE TYPE id_value_ot AS OBJECT
    ( id INTEGER, val NUMBER );
    CREATE TYPE id_value_tt AS TABLE OF id_value_ot ;
    WITH t1 AS
         ( SELECT 2008 AS yr, 4 AS mnth
                , 20 AS dy1
                , 10 AS dy2
                , 15 AS dy3
                , 1  AS dy4
                , 17 AS dy5
                , 99 AS dy6
                , 55 AS dy7
                , 45 AS dy8
                , 33 AS dy9
                , 22 AS dy10
                , 74 AS dy11
                , 35 AS dy12
                , 62 AS dy13
                , 24 AS dy14
                , 85 AS dy15
           FROM dual )
       , t2 AS
         ( SELECT yr
                , mnth
                , id_value_tt
                  ( id_value_ot(1,dy1)
                  , id_value_ot(2,dy2)
                  , id_value_ot(3,dy3)
                  , id_value_ot(4,dy4)
                  , id_value_ot(5,dy5)
                  , id_value_ot(6,dy6)
                  , id_value_ot(7,dy7)
                  , id_value_ot(8,dy8)
                  , id_value_ot(9,dy9)
                  , id_value_ot(10,dy10)
                  , id_value_ot(11,dy11)
                  , id_value_ot(12,dy12)
                  , id_value_ot(13,dy13)
                  , id_value_ot(14,dy14)
                  , id_value_ot(15,dy15) )
                  AS day_data
           FROM   t1 )
    SELECT yr, mnth, dd.val
    FROM   t2, TABLE(t2.day_data) dd
    WHERE  dd.id = 5;
            YR       MNTH        VAL
          2008          4         17
    1 row selected.

  • Filtering of the data based upon the selection screen data using ldb

    Hi Experts ,
    I am using ldb pnpce, for my report ,and i created my own report category with selection paramaters
    action type and payroll area
    now the problem is when i am giving the action type as Z0 ,the data to be extracted is not getting filtered
    based upon the action type ,the data consists the records having different action types other than Z0
    Please give me some solution for this

    Thanks Durga ,but the link wat ever u was for hiding the selection screen fields
    but my question is when am using get pernr event my data is not getting filtered with the selection screen paramater value
    i,e m giving action type as only hiring ,but m getting the data for all the action types ,its not filtering based upon my selection

  • To display the user login details in selection-screen( input screen )

    HI Experts,
    I have a requirement.
    Assume there is a report on travel details. Report access has been given to all in the organization based on authorization level.
    Before excecuting the report, in the selection-screen(input screen) itself I need to display the login user details.
    suppose user A belongs to ITS-business unit and user B-belongs to RDS-business unit and Industry group-Multi markets.
    so when User B logs into production system and try to access the report, in the selection screen, i need to display like
    user-id-- XXXX          Business Unit---RDS             and IG -
    Multi Markets 
    how to achieve this? User details will vary based on login.
    Regards,
    Praveen

    check this
    REPORT  Z_demo.
    *& Function Modules:  HR_GET_EMPLOYEE_DATA
    *&                    HR_IMAGE_EXISTS
    *&                    SCMS_DOC_URL_READ
    *&                    HR_IMAGE_RESET
    *& Class & Methods :  CL_GUI_DOCKING_CONTAINER
    *&                    CL_GUI_PICTURE->SET_POSITION
    *&                    CL_GUI_PICTURE->SET_DISPLAY_MODE
    *&                    CL_GUI_PICTURE->DISPLAY_MODE_FIT
    *&                    CL_GUI_PICTURE->LOAD_PICTURE_FROM_URL_ASYNC
    *REPORT  ZEMPLOYEE.
    TABLES: PA0001, PERSON.
    *----------------------Declaration for Image------------------------*
    DATA: DOCKING_CONT TYPE REF TO CL_GUI_DOCKING_CONTAINER, " Custom Container
          PICTURE TYPE REF TO CL_GUI_PICTURE.
    *--------------------Declaration of Internal table------------------*
    DATA: ITAB_EMPDATA LIKE TABLE OF PERSON.
    DATA: ITAB_DATA LIKE TABLE OF PERSON WITH HEADER LINE.
    DATA:  P_CONNECT_INFO LIKE TABLE OF TOAV0 WITH HEADER LINE.
    DATA:  P_DOCUMENT_TYPE LIKE TOAV0-RESERVE.
    DATA:  URL(255) TYPE C.
    DATA:  HANDLE TYPE I.
    DATA:  PPERNR TYPE PA0001-PERNR.
    *----------------------Start of Selection Screen----------------------*
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE text-099.
    SELECTION-SCREEN SKIP 2.
    SELECTION-SCREEN COMMENT 40(25) TEXT-010  .
    SELECTION-SCREEN SKIP 1.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-002 FOR FIELD PERNR.
    PARAMETERS PERNR TYPE PA0001-PERNR.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-008 FOR FIELD ENAME.
    PARAMETERS ENAME TYPE PA0001-ENAME.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-003 FOR FIELD PERSG.
    PARAMETERS PERSG TYPE PA0001-PERSG.
    SELECTION-SCREEN COMMENT 45(15) TEXT-009 FOR FIELD WERKS.
    PARAMETERS WERKS TYPE PA0001-WERKS.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-004 FOR FIELD PERSK.
    PARAMETERS PERSK TYPE PA0001-PERSK.
    SELECTION-SCREEN COMMENT 45(15) TEXT-005 FOR FIELD KOSTL.
    PARAMETERS KOSTL TYPE PA0001-KOSTL.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-006 FOR FIELD ORGEH.
    PARAMETERS ORGEH TYPE PA0001-ORGEH.
    PARAMETERS ORGEHTXT TYPE PERSON-ORGEH_TXT .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 20(15) TEXT-007 FOR FIELD PLANS.
    PARAMETERS PLANS TYPE PA0001-PLANS.
    PARAMETERS PLANSTXT TYPE PERSON-PLANS_TXT .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN SKIP 2.
    SELECTION-SCREEN END OF BLOCK B1.
    *AT SELECTION-SCREEN OUTPUT.
    AT SELECTION-SCREEN OUTPUT .
      LOOP AT SCREEN.
        IF SCREEN-NAME = 'ENAME'
        OR SCREEN-NAME = 'PERSG'
        OR SCREEN-NAME = 'PERSK'
        OR SCREEN-NAME = 'KOSTL'
        OR SCREEN-NAME = 'WERKS'
        OR SCREEN-NAME = 'ORGEH'
        OR SCREEN-NAME = 'PLANS'
        OR SCREEN-NAME = 'ORGEHTXT'
        OR SCREEN-NAME = 'PLANSTXT'.
          SCREEN-INPUT = '0'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    LOOP AT SCREEN.
        IF SCREEN-NAME = 'ORGEHTXT'
        OR SCREEN-NAME = 'PLANSTXT'.
          SCREEN-OUTPUT = '1'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    PERFORM GET_PIC.
    *AT SELECTION-SCREEN .
    AT SELECTION-SCREEN .
      PPERNR = PERNR.
      CALL FUNCTION 'HR_GET_EMPLOYEE_DATA'
        EXPORTING
          PERSON_ID             = PPERNR
          SELECTION_BEGIN       = SY-DATUM
          SELECTION_END         = SY-DATUM
        IMPORTING
          PERSONAL_DATA         = ITAB_DATA
        EXCEPTIONS
          PERSON_NOT_FOUND      = 1
          NO_ACTIVE_INTEGRATION = 2
          OTHERS                = 3.
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      ENAME = ITAB_DATA-ENAME.
      PERSG = ITAB_DATA-PERSG.
      PERSK = ITAB_DATA-PERSK.
      ORGEH = ITAB_DATA-ORGEH.
      PLANS = ITAB_DATA-PLANS.
      KOSTL = ITAB_DATA-KOSTL.
      WERKS = ITAB_DATA-WERKS.
      ORGEHTXT = ITAB_DATA-ORGEH_TXT.
      PLANSTXT = ITAB_DATA-PLANS_TXT.
    *Function Module To check Existance of Image
      CALL FUNCTION 'HR_IMAGE_EXISTS'
        EXPORTING
          P_PERNR        = PPERNR
        IMPORTING
          P_CONNECT_INFO = P_CONNECT_INFO
        EXCEPTIONS
          OTHERS         = 2.
         P_DOCUMENT_TYPE = P_CONNECT_INFO-RESERVE.
    *Function Module To Get the URL of Image
      CALL FUNCTION 'SCMS_DOC_URL_READ'
        EXPORTING
          STOR_CAT    = SPACE
          CREP_ID     = P_CONNECT_INFO-ARCHIV_ID
          DOC_ID      = P_CONNECT_INFO-ARC_DOC_ID
          COMP_ID     = 'DATA'
          DP_URL_ONLY = 'X'
        IMPORTING
          URL         = URL
        EXCEPTIONS
          OTHERS      = 10.
      IF SY-SUBRC <> 0.
      ENDIF.
    *Method To load Image from URL
      CALL METHOD PICTURE->LOAD_PICTURE_FROM_URL_ASYNC
        EXPORTING
          URL = URL.
      IF SY-SUBRC NE 0.
      ENDIF.
      IF PPERNR NE PERNR.
    *Function Module To Reset Image
        CALL FUNCTION 'HR_IMAGE_RESET'
          EXPORTING
            HANDLE         = HANDLE
          EXCEPTIONS
            INVALID_HANDLE = 1
            OTHERS         = 2.
        IF SY-SUBRC <> 0.
        ENDIF.
      ENDIF.
    *& Form Get_Pic
    FORM GET_PIC.
      DATA: REPID LIKE SY-REPID.
      REPID = SY-REPID.
      IF PICTURE IS INITIAL.
    *Object To Create the Custom Container
        CREATE OBJECT PICTURE
          EXPORTING
            PARENT = DOCKING_CONT.
        CHECK SY-SUBRC = 0.
    *Method To Set Position of Image
        CALL METHOD PICTURE->SET_POSITION
          EXPORTING
            HEIGHT = 47
            LEFT   = 610
            TOP    = 25
            WIDTH  = 70.
    *Method To Set Display Mode Fit to Container
        CALL METHOD PICTURE->SET_DISPLAY_MODE
          EXPORTING
            DISPLAY_MODE = CL_GUI_PICTURE=>DISPLAY_MODE_FIT.
      ELSE.
    *Function Module To Reset Image
        CALL FUNCTION 'HR_IMAGE_RESET'
          EXPORTING
            HANDLE         = HANDLE
          EXCEPTIONS
            INVALID_HANDLE = 1
            OTHERS         = 2.
        IF SY-SUBRC <> 0.
        ENDIF.
      ENDIF.
    ENDFORM. "Get_pic

  • Flagging the Date based on the Next Value

    Hello Everyone
    I Have a Condition where i need to compare the Date Column and the Date should be in Ascending Order and if not i need to Flag the Column
    Can anyone help how to do this or just give me an idea that would be very greatful
    Thanks
    Srix

    The Date should be in Ascending order and if there is any Discripency i should Flag it
    Here is the Sample Data,
    Final Protocol Date 13-Mar-2001 13-Mar-2001 13-Mar-2001
    Final CRF/ecrf 30-Sep-2004 30-Sep-2004 30-Sep-2004
    Initial TIA Approval 07-May-2004
    First Site Initiated 05-Sep-2001 05-Sep-2001 22-Jun-2001 --this date needs flaged
    First Subject First Visit 23-Apr-2001 23-Apr-2001 23-Apr-2001 --this date needs flaged
    First Subject Randomized/Treated 23-Apr-2001 23-Apr-2001 23-Apr-2001 --this date needs flaged     
    Last Subject First Visit 03-Nov-2006 03-Nov-2006
    Last Subject Last Visit 1 8-Dec-2006 18-Dec-2006 08-Mar-2007
    Database Lock 23-Apr-2007 23-Apr-2007 23-Apr-2007
    CSR Approved 14-Sep-2007 07-Feb-2008 11-Feb-2008
    Is there any way of doing it in BI Publisher or we should write an external Function/Procedure for this ?
    Appreciate your help

  • How to fetch data based on this selection screen

    Hi Friends:
       I've a selection screen which contains these 3 fields:
    company code (t001-bukrs)
    material division (mara-spart)
    posting date  (bkpf-budat)
    based on the above fields, I've to fetch the following:
    ekpo-bukrs
    mara-spart
    mseg-werks
    mseg-lgort
    bseg-hkont
    bseg-kostl
    bseg-hkont
    skat-txt50
    mseg-mblnr
    mseg-zeile
    bseg-belnr
    bkpf-bktxt
    mseg-insmk
    bkpf-monat
    bkpf-budat
    mseg-bwart
    mbew-matnr
    makt-maktx
    mseg-menge
    mseg-meins
    mbew-stprs
    mseg-dmbtr
    bseg-pswsl
    ausp-atwrt
    mara-matkl
    mara-mtart
    mbew-bklas
    mbew-bwtar
    mkpf-vgart
    mcha-charg
    mseg-ebeln
    aufk-aufnr
    mseg-ummat
    vbak-vbeln
    likp-vbeln
    bkpf-usnam
    Please help me with the logic . I want to ask that in which order I should start fetching data.How to relate it from selection screen. Which table I should fetch first based on the selection screen.how to relate mseg/bseg/mara/mbew/vbak/bkpf  etc.
    Please help.
    Thanks for your time.

    Hi,
    I dont think you need EKPO to fetch your bukrs. It is available in BKPF too.
    Use inner join to join MKPF, BKPF, MAKT, fetch all the related entreis.
    Use Inner join on MBEW, MCHA for all entries from above query.
    use inner join on AUSP for all entries from above query.
    Use may use separate queries or inner joins for LIKP and VBAK with for all entries.
    Use separate for all entries for BSEG and MSEG. Do not use any JOIN on BSEG as it is a pooled table.
    As per the need you may change the queries..
    Regards,
    Subramanian

  • Grouping and sorting the data based on the parameter

    Hi,
    I need to display the total of item Cost i.e sub total based on parameter in Excel format
    if value = 1 then (Subtotal by Manufacture) and sorting by Manufacture, Receipt Date, Organization, Item Code
    if value = 2 then (Subtotal by Organization ) and sorting by Organization, Item, Serial Number
    and at the end of report need to display full total
    is it possible in excel output using the below xml , please guide me if i need to change the way of getting XML ouput or can be acheived using this.
    Please find the xml , thanks in advance
    <?xml version="1.0"?>
    <!-- Generated by Oracle Reports version 6.0.8.27.0 -->
    <ASWRECDTREP>
    <LIST_G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>10</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
    <SERIAL_NUMBER>90699100802262</SERIAL_NUMBER>
    <ITEM_CODE>OM906LA.007</ITEM_CODE>
    <DESCRIPTION>MERCEDES SERIES 900 OFF HWY ENGINE 205 KW 0852</DESCRIPTION>
    <MANUFACTURER>MER</MANUFACTURER>
    <APPLICATION>INDL</APPLICATION>
    <ITEM_COST>15009.09</ITEM_COST>
    <MATERIAL_COST>685.25</MATERIAL_COST>
    <PO_NUMBER>1001395</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>22-MAY-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>EUR</CURRENCY_CODE>
    <PO_UNIT_PRICE>7431.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>10</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
    <SERIAL_NUMBER>90699100802285</SERIAL_NUMBER>
    <ITEM_CODE>OM906LA.007</ITEM_CODE>
    <DESCRIPTION>MERCEDES SERIES 900 OFF HWY ENGINE 205 KW 0852</DESCRIPTION>
    <MANUFACTURER>MER</MANUFACTURER>
    <APPLICATION>INDL</APPLICATION>
    <ITEM_COST>15009.09</ITEM_COST>
    <MATERIAL_COST>685.25</MATERIAL_COST>
    <PO_NUMBER>1001395</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>22-MAY-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>EUR</CURRENCY_CODE>
    <PO_UNIT_PRICE>7431.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>30</ORGANIZATION_CODE>
    <ORGANISATION_NAME>Melbourne</ORGANISATION_NAME>
    <SERIAL_NUMBER>6520107896</SERIAL_NUMBER>
    <ITEM_CODE>3500.010</ITEM_CODE>
    <DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E018179</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>11126.11</ITEM_COST>
    <MATERIAL_COST>664.23</MATERIAL_COST>
    <PO_NUMBER>971515</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>14-APR-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>8063.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>30</ORGANIZATION_CODE>
    <ORGANISATION_NAME>Melbourne</ORGANISATION_NAME>
    <SERIAL_NUMBER>6510869062</SERIAL_NUMBER>
    <ITEM_CODE>3200.010</ITEM_CODE>
    <DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E017944</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>11853.57</ITEM_COST>
    <MATERIAL_COST>707.66</MATERIAL_COST>
    <PO_NUMBER>982120</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>12-MAY-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>8251.6</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>40</ORGANIZATION_CODE>
    <ORGANISATION_NAME>Brisbane</ORGANISATION_NAME>
    <SERIAL_NUMBER>D6002 G6003</SERIAL_NUMBER>
    <ITEM_CODE>520 SERIES.002</ITEM_CODE>
    <DESCRIPTION>KONRAD 520 SERIES MARINE STERN DRIVE</DESCRIPTION>
    <MANUFACTURER>OTH</MANUFACTURER>
    <APPLICATION>MARI</APPLICATION>
    <ITEM_COST>9296.95</ITEM_COST>
    <MATERIAL_COST>482.91</MATERIAL_COST>
    <PO_NUMBER>1009062</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>24-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>6939.29</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>40</ORGANIZATION_CODE>
    <ORGANISATION_NAME>Brisbane</ORGANISATION_NAME>
    <SERIAL_NUMBER>ABC123</SERIAL_NUMBER>
    <ITEM_CODE>GM20541-KP1.001</ITEM_CODE>
    <DESCRIPTION>KOHLER GENSET</DESCRIPTION>
    <MANUFACTURER>KOH</MANUFACTURER>
    <APPLICATION>PGEN</APPLICATION>
    <ITEM_COST>756.83</ITEM_COST>
    <MATERIAL_COST>.78</MATERIAL_COST>
    <PO_NUMBER>1015156</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>14-OCT-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>AUD</CURRENCY_CODE>
    <PO_UNIT_PRICE>20</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>40</ORGANIZATION_CODE>
    <ORGANISATION_NAME>Brisbane</ORGANISATION_NAME>
    <SERIAL_NUMBER>ABC124</SERIAL_NUMBER>
    <ITEM_CODE>GM20541-KP1.001</ITEM_CODE>
    <DESCRIPTION>KOHLER GENSET</DESCRIPTION>
    <MANUFACTURER>KOH</MANUFACTURER>
    <APPLICATION>PGEN</APPLICATION>
    <ITEM_COST>756.83</ITEM_COST>
    <MATERIAL_COST>.78</MATERIAL_COST>
    <PO_NUMBER>1015156</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>14-OCT-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>AUD</CURRENCY_CODE>
    <PO_UNIT_PRICE>20</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>06R1017763</SERIAL_NUMBER>
    <ITEM_CODE>6062HK30.005</ITEM_CODE>
    <DESCRIPTION>DETROIT SERIES 60 MARINE ENGINE 615 KW 2949322</DESCRIPTION>
    <MANUFACTURER>MDD</MANUFACTURER>
    <APPLICATION>MARI</APPLICATION>
    <ITEM_COST>99125.34</ITEM_COST>
    <MATERIAL_COST>2028.31</MATERIAL_COST>
    <PO_NUMBER>883339</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>05-MAR-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>63768</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310935001</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1000221</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>01-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310935002</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1000221</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>01-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310935003</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1000221</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>01-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6510876301</SERIAL_NUMBER>
    <ITEM_CODE>T350R.004</ITEM_CODE>
    <DESCRIPTION>ALLISON TORQMATIC ON HWY TRANSMISSION</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>9465.69</ITEM_COST>
    <MATERIAL_COST>597.33</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>6936.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6510876302</SERIAL_NUMBER>
    <ITEM_CODE>T350R.004</ITEM_CODE>
    <DESCRIPTION>ALLISON TORQMATIC ON HWY TRANSMISSION</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>9465.69</ITEM_COST>
    <MATERIAL_COST>597.33</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>6936.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6510876303</SERIAL_NUMBER>
    <ITEM_CODE>T375R.002</ITEM_CODE>
    <DESCRIPTION>ALLISON TORQMATIC ON HWY TRANSMISSION</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>10224.19</ITEM_COST>
    <MATERIAL_COST>645.19</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>7433.3</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310940354</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310940355</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310940356</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>6310940357</SERIAL_NUMBER>
    <ITEM_CODE>2500.003</ITEM_CODE>
    <DESCRIPTION>ALLISON 2000 SERIES ON HWY TRANSMISSION E016189</DESCRIPTION>
    <MANUFACTURER>ATD</MANUFACTURER>
    <APPLICATION>ONHY</APPLICATION>
    <ITEM_COST>4855.33</ITEM_COST>
    <MATERIAL_COST>306.39</MATERIAL_COST>
    <PO_NUMBER>1005777</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>23-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>3574.9</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    <G_ASW_REC_DATE>
    <ORGANIZATION_CODE>70</ORGANIZATION_CODE>
    <ORGANISATION_NAME>NDC - PRODUCT</ORGANISATION_NAME>
    <SERIAL_NUMBER>5272003543</SERIAL_NUMBER>
    <ITEM_CODE>T1637K33.002</ITEM_CODE>
    <DESCRIPTION>DETROIT SERIES 4000 INDUSTRIAL ENGINE 1865 KW 2456291</DESCRIPTION>
    <MANUFACTURER>MDD</MANUFACTURER>
    <APPLICATION>MNIG</APPLICATION>
    <ITEM_COST>420083.16</ITEM_COST>
    <MATERIAL_COST>3785.85</MATERIAL_COST>
    <PO_NUMBER>921170</PO_NUMBER>
    <TRANSACTION_RECEIPT_DATE>30-JUN-09</TRANSACTION_RECEIPT_DATE>
    <VENDOR_LOT_NUM></VENDOR_LOT_NUM>
    <CURRENCY_CODE>USD</CURRENCY_CODE>
    <PO_UNIT_PRICE>301549</PO_UNIT_PRICE>
    </G_ASW_REC_DATE>
    </LIST_G_ASW_REC_DATE>
    </ASWRECDTREP>
    Best Regards,
    Mahi

    Hi Vetri,
    I tried to implement the solution you have given and i am getting error,
    I tried to see the output by loading the xml to the template given in BIP Blog in the following Link,
    http://blogs.oracle.com/xmlpublisher/2007/05/left_up_down_right_group.html
    I am getting the same error,Please help me how to overcome this.If possible send me the template that was working for you.
    The error log is as follows:
    ConfFile: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdoconfig.xml
    Font Dir: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts
    Run XDO Start
    Template: C:\Users\MAHESH\Desktop\Grouping.rtf
    RTFProcessor setLocale: en-us
    FOProcessor setData: C:\Users\MAHESH\Desktop\EmployeeListing.xml
    FOProcessor setLocale: en-us
    java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
         at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
         at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
         at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
         at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
         at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
         at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
         at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
         at RTF2PDF.runRTFto(RTF2PDF.java:629)
         at RTF2PDF.runXDO(RTF2PDF.java:439)
         at RTF2PDF.main(RTF2PDF.java:289)
    Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
         at oracle.xdo.parser.v2.XSLTContext.peekExprValue4Grouping(XSLTContext.java:871)
         at oracle.xdo.parser.v2.XPathFunctionCall.evaluate(XPathFunctionCall.java:536)
         at oracle.xdo.parser.v2.XPathFunctionCall.evaluate(XPathFunctionCall.java:583)
         at oracle.xdo.parser.v2.XSLVariable.getValue(XSLVariable.java:205)
         at oracle.xdo.parser.v2.XSLVariable.processAction(XSLVariable.java:117)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
         at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
         at oracle.xdo.parser.v2.XSLTemplate.processAction(XSLTemplate.java:191)
         at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:512)
         at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:489)
         at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:271)
         at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:155)
         at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:192)
         ... 15 more
    Best Regards,
    Mahi

  • How to split the data based on one column

    Dear All,
    I have the table data like this.
    type quantity revenue_mny count country
    a 10           10          2 India
    a 20          12          3 India
    b 30          15          1 India
    a 35          20          2 US
    b 20          10          1 US
    b 60          15          1 US
    I woulkd like to split the date based on type column.
    For each country, for Type "a" get the sum of revenue count quanity ans same for b
    and all shuld come in on row for each country.
    output should be like
    country revenue_mny(For a) quantity(for a) count(For a) revenue_mny(for b) quantity(for b) count(For b)
    India 22 30 5 15 30 1
    US 20 35 2 25 80 2
    I tried the below query . its not splittng the date for each country in one row.
    select country,
    sum(case when type='a') then revenue_mny else 0 end ) revenue_mny_a,
    sum(case when type='b' then revenue_mny else 0 end ) revenue_mny_b
    sum(case when type='a' then quantity else 0 end) quantity_a,
    sum(case when type='b' then quantity else 0 end) quantity_b from
    test
    group by country
    Please need your helo

    Like this?
    with t as
    select 'a' type, 10 quantity, 10 revenue_mny, 2 cnt, 'India' country from dual union all
    select 'a', 20, 12, 3, 'India' from dual union all
    select 'b', 30, 15, 1, 'India' from dual union all
    select 'a', 35, 20, 2, 'US' from dual union all
    select 'b', 20, 10, 1, 'US' from dual union all
    select 'b', 60, 15, 1, 'US' from dual
    select country,
    sum(case when type='a' then revenue_mny else 0 end ) revenue_mny_a,
    sum(case when type='a' then quantity else 0 end) quantity_a,
    sum(case when type='a' then cnt else 0 end) cnt_a,
    sum(case when type='b' then revenue_mny else 0 end ) revenue_mny_b,
    sum(case when type='b' then quantity else 0 end) quantity_b ,
    sum(case when type='b' then cnt else 0 end) cnt_b
    from t
    group by country;result:
    COUNTRY  REVENUE_MNY_A QUANTITY_A CNT_A REVENUE_MNY_B QUANTITY_B CNT_B
    India    22            30         5     15            30         1
    US       20            35         2     25            80         2Or you can do it with a decode instead of case. The result will be the same:
    with t as
    select 'a' type, 10 quantity, 10 revenue_mny, 2 cnt, 'India' country from dual union all
    select 'a', 20, 12, 3, 'India' from dual union all
    select 'b', 30, 15, 1, 'India' from dual union all
    select 'a', 35, 20, 2, 'US' from dual union all
    select 'b', 20, 10, 1, 'US' from dual union all
    select 'b', 60, 15, 1, 'US' from dual
    select country,
    sum(decode(type,'a',revenue_mny,0)) revenue_mny_a,
    sum(decode(type,'a',quantity,0)) quantity_a,
    sum(decode(type,'a',cnt,0)) cnt_a,
    sum(decode(type,'b',revenue_mny,0)) revenue_mny_b,
    sum(decode(type,'b',quantity,0)) quantity_b,
    sum(decode(type,'b',cnt,0)) cnt_b
    from t
    group by country;(I changed tablename from TEST to T and columnname from COUNT to CNT, because you should not use reserved words as tablename or columnname.)
    Edited by: hm on 09.10.2012 06:17

  • Setting only the TO field on the Created on Field in Selection screen to Current date

    Hello,
    We have a requirement to Set only the To date in the Created on Field in Selection screen to the Current date, I have tried through Dynamic variable option to set the Date calculation but I am able to see Options to set the Current date to From or From and To Created on Date fields instead of setting the Current date only to To created on Field.
    We are in 4.7 and are not supported with user defined variables, Appreciate your inputs on this.
    Thanks and Regards
    Mohammed Roshan

    >
    sunitha j wrote:
    > Hi ,
    >
    > It would br gr8..if u could give some more info about the usage of this class..i mean if i hav to implement it in my program....wat is the necessary data that needs to b copied...
    >
    > Thanx,
    > Sunitha
    what Text field you want to change.
    Since you are working with Dynpros , you have to split the screen in two parts, and one for the Showing differenet fonts and other your normal Dynpro information.
    you need to use the Method ADD_TEXT Did you check the program DD_STYLE_TABLE.

  • How to select the data efficiently from the table

    hi every one,
      i need some help in selecting data from FAGLFLEXA table.i have to select many amounts from different group of G/L accounts
    (groups are predefined here  which contains a set of g/L account no.).
    if i select every time for each group then it will be a performance issue, in order to avoid it what should i do, can any one suggest me a method or a smaple query so that i can perform the task efficiently.

    Hi ,
    1.select and keep the data in internal table
    2.avoid select inside loop ..endloop.
    3.try to use for all entries
    check the below details
    Hi Praveen,
    Performance Notes
    1.Keep the Result Set Small
    You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
    Using the WHERE Clause
    Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
    When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
    Using the HAVING Clause
    After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
    Effect
    If you use the WHERE and HAVING clauses correctly:
    • There are no more physical I/Os in the database than necessary
    • No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
    • The CPU usage of the database host is minimize
    • The network load is reduced, since only the data that is required by the application is transferred to the application server.
    Minimize the Amount of Data Transferred
    Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
    To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
    Restrict the Number of Lines
    If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
    If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
    Restrict the Number of Columns
    You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
    Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
    Use Aggregate Functions
    If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
    Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
    Following an aggregate expression, only its result is transferred from the database.
    Data Transfer when Changing Table Lines
    When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
    When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
    In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
    Multiple Operations Instead of Single Operations
    When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
    Avoid Repeated Access
    As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
    Avoid Nested SELECT Loops
    A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
    However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
    ABAP Dictionary Views
    You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
    Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
    The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
    Joins in the FROM Clause
    You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
    The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
    The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
    Subqueries in the WHERE and HAVING Clauses
    Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
    Using Internal Tables
    It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
    Using a Cursor to Read Data
    A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
    You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
    Database Indexes
    Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
    The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
    If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
    You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
    Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
    If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
    Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that column’s selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
    If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
    Formulating Conditions for Indexes
    You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
    Check for Equality and Link Using AND
    The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
    Use Positive Conditions
    The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
    If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
    Using OR
    The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
    Using Part of the Index
    If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
    Checking for Null Values
    The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
    Avoid Complex Conditions
    Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
    Reduce the Database Load
    Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
    Buffer Tables on the Application Server
    You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
    Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
    • Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
    • Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
    • Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
    When you read from buffered tables, the following happens:
    1. An ABAP program requests data from a buffered table.
    2. The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
    3. If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
    4. The database server passes the data to the application server, which places it in the table buffer.
    5. The data is passed to the program.
    When you change a buffered table, the following happens:
    1. The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
    2. All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
    3. Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
    You should buffer the following types of tables:
    • Tables that are read very frequently
    • Tables that are changed very infrequently
    • Relatively small tables (few lines, few columns, or short columns)
    • Tables where delayed update is acceptable.
    Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
    The SELECT statement bypasses the buffer when you use any of the following:
    • The BYPASSING BUFFER addition in the FROM clause
    • The DISTINCT addition in the SELECT clause
    • Aggregate expressions in the SELECT clause
    • Joins in the FROM clause
    • The IS NULL condition in the WHERE clause
    • Subqueries in the WHERE clause
    • The ORDER BY clause
    • The GROUP BY clause
    • The FOR UPDATE addition
    Furthermore, all Native SQL statements bypass the buffer.
    Avoid Reading Data Repeatedly
    If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
    Sort Data in Your ABAP Programs
    The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
    Use Logical Databases
    SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
    Work Processes
    Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
    Structure of a Work Process
    Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
    Each work process contains two software processors and a database interface.
    Screen Processor
    In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
    ABAP Processor
    The actual processing logic of an application program is written in ABAP - SAP’s own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
    Database Interface
    The database interface provides the following services:
    • Establishing and terminating connections between the work process and the database.
    • Access to database tables
    • Access to R/3 Repository objects (ABAP programs, screens and so on)
    • Access to catalog information (ABAP Dictionary)
    • Controlling transactions (commit and rollback handling)
    • Table buffer administration on the application server.
    The following diagram shows the individual components of the database interface:
    The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
    Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
    Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
    Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
    The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
    Types of Work Process
    Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
    Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
    The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
    The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
    Dialog Work Process
    Dialog work processes deal with requests from an active user to execute dialog steps.
    Update Work Process
    Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
    Background Work Process
    Background work processes process programs that can be executed without user interaction (background jobs).
    Enqueue Work Process
    The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
    Spool Work Process
    The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
    The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
    You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
    ABAP Application Server
    R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
    Structure of an ABAP Application Server
    The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
    The following diagram shows the structure of an application server:
    The individual components are:
    Work Processes
    An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
    Dispatcher
    Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
    Gateway
    Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
    The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
    Shared Memory
    All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
    The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
    Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
    Database Connection
    When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
    Dispatching Dialog Steps
    The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
    The following diagram is an example of how this might happen:
    1. The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
    2. The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
    3. While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
    4. After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
    5. While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
    From this example, we can see that:
    • A dialog step from a program is assigned to a single work process for execution.
    • The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
    • A work process can execute dialog steps of different programs from different users.
    The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
    Dispatching and the Programming Model
    The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
    As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
    A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
    Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
    These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
    However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
    The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
    Happy Reading...
    shibu

  • How i can show the selection screen input field in the top of page in alv

    hi ,
              how i can show the selection screen input field in the top of page in alv  grid output.
    tell me the process

    Hi,
    excample from my program:
    FORM topof_page.
      DATA: l_it_header   TYPE TABLE OF slis_listheader WITH HEADER LINE,
            l_info        LIKE l_it_header-info.
      DATA: l_it_textpool TYPE TABLE OF textpool WITH HEADER LINE.
      DATA: l_key LIKE l_it_textpool-key.
      READ TEXTPOOL c_repid INTO l_it_textpool LANGUAGE sy-langu.
      DEFINE m_selinfo.
        if not &1 is initial.
          clear l_it_header.
          l_it_header-typ   = 'S'.
          l_key = '&1'.
          translate l_key to upper case.
          read table l_it_textpool with key key = l_key.
          if sy-subrc = 0.
            shift l_it_textpool-entry left deleting leading space.
            l_it_header-key = l_it_textpool-entry  .
          endif.
          loop at &1.
            case &1-option.
              when 'EQ'
                or 'BT'
                or 'CP'.
                write &1-low to l_it_header-info.
              when others.
                write &1-low to l_it_header-info.
                concatenate &1-option
                            l_it_header-info
                       into l_it_header-info
                       separated by space.
            endcase.
            if not &1-high is initial.
              write &1-high to l_info left-justified.
              concatenate l_it_header-info
                          l_info
                     into l_it_header-info
                     separated by space.
            endif.
            if &1-sign = 'E'.
              concatenate ']'
                          l_it_header-info
                     into l_it_header-info.
            endif.
            append l_it_header.
            clear: l_it_header-key,
                   l_it_header-info.
          endloop.
        endif.
      END-OF-DEFINITION.
      m_selinfo: s_trmdat,
                 s_trmext,
                 s_trmint,
                 s_fkdat,
                 s_delno,
                 s_vbeln,
                 s_deact,
                 s_kdmat.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
           EXPORTING
                it_list_commentary = l_it_header[].
    ENDFORM.
    I hope, this will help you.
    Regards
    Nicole

  • In AP invoice i need to make "Terms date " field to calculate the date automatically when i select the payment terms

    In AP invoice i need to make "Terms date " field to calculate the date automatically when i select the payment terms.
    How can i do this?

    Hi,
    You can select the Payment Term at PO Header Level.
    When you book an invoice, that Payment Term will automatically defaulted to Invoice.
    You can define Payment Term in AP.
    Payment terms have one or more payment terms lines, each of which creates one scheduled payment. Each payment terms line and each corresponding scheduled  payment has a due date or a discount date based on either a specific day of a month, such as the 15th of the month, or a number of days added to your terms date, such as 14 days after the terms date.
    Payment Terms (Oracle Payables Help)

  • Is it possible to find the  table based on the Date ?

    Dear Team ,
    Is it possible to find the table based on the Date ?
    I have created an table ,But forgot the Table Name .
    Is it possible to find the Tables created on particular Date .
    Regards ,
    Augustine

    as date is record the time also below query will work.
    select * from user_objects
    where
    object_type = 'TABLE' and
    to_date(created,'DD-MON-YYYY') =to_date('<your date value in DD-MON-YYYY format>','DD-MON-YYYY');
    Edited by: shaileshM on Feb 24, 2010 9:39 PM

  • Is it possible to rearrange the order of SAP STD Selection Screen?

    Hi.
    Is it possible to rearrange the order of SAP STD Selection Screen?
    Example:
    IW69 has Location data selection at bottom of screen. 
    Is it possible to move that to top of the selection screen?
    We are on ECC6.0.
    Thank you,
    Brett.

    Hello Brett
    You may try to use GuiXT:
    [Adjusting Transactions Using GuiXT|http://help.sap.com/saphelp_sm32/helpdata/en/89/91b9db194f11d5b3a30050dae02d7c/content.htm]
    Regards
      Uwe

  • How to pick the data based on customer number

    Hi All ,
    greets....
    i have a requirement to select  the data based on customer number and then do furthur processing .
    example:
    this is some 10 dcouments in customer nr:v1000
    and 20 documents in customer v2000 in a internal table how to select that,
    thank s in advance.

    thier is an internal table which is having some 1000records.
    and their is 6 customers.
    in which i should pick the data based on customer number.
    how to write a code for that?

Maybe you are looking for

  • What are all database monitering tools available in oracle

    what are all database monitering tools available in oracle

  • More problem with JFormattedTextField

    Here is the code where I want size and input validation for JFormattedTextField MaskFormatter f10=new MaskFormatter("***************"); f10.setValidCharacters("0123456789"); t4= new JFormattedTextField(f10); It's behaving in funny way. It allows me o

  • Why is my iPad 2 no longer able to screen share to external monitor?

    I used to connect my ipad 2 to various shared displays via HDMI and VGA converter cords quite frequently. The other day I connected and no signal is found...tried multiple screens, projector and different cords. Convinced its my iPad. Fixable? Hardwa

  • Connecting replacement ipod to old itunes

    so here's the thing: last week my ipod broke so they replaced it. now i got a new ipod, but it wont show up on my itunes. i tried downloading the new ipod software, but it still wont show up on my itunes! i dont want to reinstall my itunes, b/c i don

  • Can not buy Photoshop + Lightroom offer

    Hi, for the past 4 days, I have been trying to subscribe to the Photoshop + Lightroom temporary offer, which ends today. Every time I enter my CC details, the system returns an error message "cannot be processed at the moment, please try again later.