Sequence of SPList.Fields

Dear Friends,
I'm trying to get the list of fields of a SharePoint list using SPList.Fields property. What is the sequence it returns the fields? It is different from environment
to environment.
Thanks,
Dilip

The sequence is based on the ascending date of addition, that is a field which is added first is first in the sequence and the field which is added last is last in the sequence. You can use following Server Model Object code to confirm it.
using (SPSite site = new SPSite("yoursite"))
SPWeb root = site.RootWeb;
SPList list = root.Lists["List1"];
SPFieldCollection fields = list.Fields;
foreach(SPField field in fields)
if (!field.FromBaseType)
Console.WriteLine(field.Title);
Console.Read();
Note that, the above code will not show the built-in fields like Title, Created, Modified etc because of the condition if (!field.FromBaseType)
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

Similar Messages

How to specify multiple sequence for multiple fields in a primary key!

Hi,
i have a table which has about 15 fields, one of the field is primary key and i am able to specify the sequence for it using toplink and when the object is created through toplink the sequence get generated automatically, which is fine.
Now i have to add another sequence generated field to the table this field is not nullable and
i am looking for a way in toplink to specify the sequence for this field too, so that when we create objects through toplink the value for the field is automatically generated instead of us fetching the next value from sequence using a sql statement and then using the set method for the field.
is there a way i can specify a sequence for another field through toplink, while keeping the sequence settings for the primary field untouched.
thanks for your help!
-

TopLink only supports a single sequence field in its' mappings. There should be an API you can use to get another sequence number from an event, but I could not find an easy one (please log a bug for this on EclipseLink). The following code might work if you define the other sequence in TopLink, but you could also just execute the raw SQL as you are doing.
i.e. something like,
preInsert(DescriptorEvent event) {
MyObject object = (MyObject) event.getObject();
object.setOtherId(event.getSession().getDatasourcePlatform().getSequence("MY_OTHER_SEQ").getGeneratedValue(event.getSession().getAccessor(), event.getSession()));
-- James : http://www.eclipselink.org

SAP Query column sequence for Totalling fields

Hi all
We have a custom query in 4.6C in which the output displays only the total of Totaling fields maintained in the sequence Amount > Withholding Tax > Net Amount (all currency related fields).
However after upgrade to ECC 6.0, we notice that we are no longer able to sequence the output list to Amount > Withholding Tax > Net Amount
Though we maintain the Totaling fields in the sequence Amount > Withholding Tax > Net Amount , the list is generated in the sequence Amount > Net Amount > Withholding Tax and the sequence is changed accordingly in the Basic List after a test display of the Output.
Is anyone aware if the sequencing control is removed in ECC based for the Totaling Fields?
Kindly help share.
Thanks in Advance
Vinodh S

Hi Faheem,
After changing the column sequence i clicked configuration button and click save button and again clicked Configuration and selected Administrative button there i can see the column sequence change and clicked activate button .now if i close and reopen the transaction my column sequence is same with out changes that i made .
you asked me to save the changes where i can do exactly ? Could you please tell in briefway from scratch so that i can trace where i done mistake.
Thanking you in advance.
Regards,
narasimha.

Regarding the sequence of the fields in Marketing Documents.....

Dear

Dear All,
I want to set the fields in the marketing documents as per the clients requirements means , in the
sequece as they want .
For example, the fields must be in the following seuquece when the user entering the data into the
marketing department:
1.Item No. 2. Item Description 3. Unit Price 4. Quantity 5. UDF1 6.UDF2 7.Tax Code etc,,,,
But System takes that fields in the sequece automatically so please let me know how i can arrange the
fields in the sequence that the user required....
Thanks.....
Regads,
Manohar

Trying to create a sequence, from 3 fields

I need to come up with a mechanism to generate the primary key for a table.
the table looks something like
Co | Permit | Episode | a | b | c | Co2 | Permit2
the co2 and permit2 are foreign keys to another table. Co and Permit are just copies of Co2 and Permit2. So then I am adding another field "Episode" to create the primary key.
so I would have something like
1-00001-1 a b c 1-00001
1-00001-2 a b c 1-00001
1-00002-1 a b c 1-00002
1-00002-2 a b c 1-00002
1-00002-3 a b c 1-00002
1-00003-1 a b c 1-00003
I wanted to use a seq to generate this, but since it is multiple fields it is not a continues number where a 1 or multiple needs added on. Do I use a sequence here? Trigger?
Any suggestions?

John,
I am not necessarily saying that this is the way to go, but am just providing you with what you originally asked for, as an option to consider. The following trigger would insert numbers into the episode column in the manner that you specified:
CREATE OR REPLACE TRIGGER episode_trigger
BEFORE INSERT ON table_name
FOR EACH ROW
BEGIN
SELECT MAX (temp_max)
INTO :NEW.episode
FROM (SELECT 1 temp_max
FROM DUAL
UNION
SELECT MAX (episode) + 1 temp_max
FROM table_name
WHERE co = :NEW.co
AND permit = :NEW.permit);
END episode_trigger;
null

Fields sequence in the select statement

experts, help needed
itab has following fields,
vbeln posnr erdat erzet vkorg vtweg
kunnr posnr matnr bmeng status.
i have written like this
SELECT avbeln aerdat aerzet avkorg a~vtweg
akunnr bposnr b~matnr
FROM vbak AS a INNER JOIN vbap AS b
ON avbeln = bvbeln
INTO TABLE itab1
FOR ALL ENTRIES IN itab
WHERE a~vbeln = itab-vbeln.
endif.
but my internal table fields sequence are different. so i changed the posnr field in the select query to the second place.
SELECT avbeln bposnr aerdat aerzet avkorg avtweg
akunnr bmatnr
FROM vbak AS a INNER JOIN vbap AS b
ON avbeln = bvbeln
INTO TABLE itab1
FOR ALL ENTRIES IN itab
WHERE a~vbeln = itab-vbeln.
endif.
so in above two select statements which one is right , according to coding standards,?
in this case do i need to use the into corresponding fields addition because i am not selecting bmeng , status fields into the itab?

Hi,
Of the two select statements,
SELECT a~vbeln b~posnr a~erdat a~erzet a~vkorg a~vtweg
a~kunnr b~matnr
FROM vbak AS a INNER JOIN vbap AS b
ON a~vbeln = b~vbeln
INTO TABLE itab1
FOR ALL ENTRIES IN itab
WHERE a~vbeln = itab-vbeln.
is the better one. I,e specifyiig the field sequence exactly as you have in the internal table. Even according to standards, this is better.
If you are chaning the sequence of select fields, then you have to use the INTO CORRESPONDING FILEDS OF TABLE addition, so that the system itself finds the relevant order of fields and fill them automatically.
This is a additional work which has to be performed by the compiler.
Thus its better to use INTO CORRESPONDING FILEDS OF TABLE only when you are using select * , or when you are not sure of the field sequence inthe table.
Regards,
Vik

OLMRLIST MIRO Chance Sequence of Fields in Table Control

Hello Guys,
Do you know exactly how I can change the sequence of the fields on the Item-Level-Table-Control in MIRO. I am using a Z* transaction variant which I choose in MIRO, this works fine.
I checked T-Codes OLMRLIST and SHD0, but I dont see there a chance to change the sequence. Can you indicate me the excatly path to follow.
For your help .... best regard.
BR
Manuel

Hi Manuel,
You can do the sequence change in OLMRLIST transaction itself.
first create the variant as Z* then go to the MIRO screen there change the sequence of the columns as per the requirement on the MIRO screen.Then system will ask you the copy the settings with screen name and description enter the details there you need to select the check box Adopt column sequence and if you want Adopt column width also in the table control TC_MR1M. Then Press Exit and save system will ask the object check with company objects which will be available from technical guys. then save this variant for MIRO transaction.
when ever you select this Z* Variant you will find your changed column sequence as per you settings.
Hope you find the solution.Check & confirm
rgds
Chidanand

Deinterlace with sequence field

Hi everybody,
somebody told me that if I put some interlaced footage in a sequence with "none" field in the settings, Final Cut automatically deinterlace my footage exporting a progressive video.
Is it true?

deadom wrote:
I always thought that I had to deinterlace the interlaced footage before to put it in a sequence with "none" fields, to get a progressive video.
What you are doing when you put a clip in a non-matching sequence is that you are forcing FCP to render. Try it out: create a new sequence with field order "none" and drop an interlaced clip in it. The render bar will appear. Then render and export as self-contained QT movie with current settings. Open in QT 7 and hit Cmd+I. What does it say in the Inspector window?
mish

Tuning Select Statement . field sequence and where clause

Hi All
Are there any general guidelines how to write select < field sequence >where clause < field sequence ? Is that shuld be in order of the field sequence in tables?
And how to use this when we have a view or a inner - join . Is that separate from normal select statement that is using FOR ALL ENTRIES.
Please let me know any general guidelines available on this,
Amol

Hello Amol,
I have another hint:
The statement FOR ALL ENTRIES will package the select statements for every five entries in the internal table. So in comparison to the following code sequence...
LOOP AT itab.
   SELECT * FROM table WHERE key = itab-key.
ENDLOOP
the number of select statements is reduced to 20% with
SELECT * FROM table INTO TABLE ...
     FOR ALL ENTRIES IN itab
     WHERE key = itab-key
If I'm expecting a <i>huge</i> amount of data a go a step further and create my own packages by building a range table with around 100-500 entries and execute a select there...
LOOP AT itab.
   IF counter < 500.
      APPEND itab-key TO range-tab.   " just code example
   ENDIF.
   IF count >= 500.
      SELECT * FROM table APPENDING TABLE ...
         WHERE key IN range_tab
   ENDIF.
   " adjust and calculate counter
ENDLOOP.
* Don't forget last select statement after loop
Best wishes,
Florin

Fields not in Order ..?

When I display data on the DSO or Cube the fields are not in order as compared to once in extract checker - datasource.
Why so?
On what does the sequence depend?
It makes Reconcilation really tough.

I guess... Sequence of the Fields in DSo Contents display will depends on the Sequece of DSO Creation(IO Sequece while creating DSO).
Nagesh Ganisetti.
assign points it helps.

How to create a sequence for an particular item in my apex form

Hi friends,
I created an database application, of a form with a report, and it is working fine...
But in my form, i have a requirement....The below are the existing fields in my form
issue no
created by
start date
status
priority
due date
Among these fields in my form i need to create a 'Sequence' for my field "issue no",
So that whenever i opened the form the 'issue number' must generate automatically like 1 for the first time, 2 for the second time and so on..
For that i created a sequence
CREATE SEQUENCE "ORDERS_SEQ"
MINVALUE 1
MAXVALUE 999999999999999999999999999
INCREMENT BY 1
START WITH 1000
NOCACHE
NOCYCLE;
But for validation where i need to write the sequence query for the particular item 'issue no'....i dont have any idea of where to write the validation query for the sequence..
please tell where i need to write in step wise manner..please help me friends...
As the below is my validated sequence query for item 'issue no'
'select seq.issue_id.nextval into issue_no'
This is my above validation query whether the query that i mentioned is right..if not let me know the validation query..
And also i need where to apply this validation query in steps..
Thanks in advance
Regards,
Harry...

Harry,
Rik is on the right track. Here is a sample insert trigger: Would need to substitute you sequence ORDERS_SEQ with my sequence las_log_seq, how you define or use timestamps is up to you.
DROP TRIGGER LASDEV.BINS1_LAS_LOG_TBL;
CREATE OR REPLACE TRIGGER LASDEV."BINS1_LAS_LOG_TBL"
   BEFORE INSERT
   ON las_log_tbl
   FOR EACH ROW
BEGIN
   -- Description: Insert log_seq, creation_dt, creation_id,
   --              lst_updt_dt and lst_updt_id.
   -- Maintenance:
   -- Date        Actor          Action
   -- ====        =====          ======
   -- 07-Sep-2010 J. Wells       Create.
   :new.creation_id := nvl( v( 'app_user' ), user );
   :new.creation_dt := SYSDATE;
   :new.lst_updt_dt := :new.creation_dt;
   :new.lst_updt_id := :new.creation_id;
    SELECT las_log_seq.NEXTVAL
      INTO :new.las_log_seq
      FROM DUAL;
END bins1_las_log_tbl;
/Heff

Field Catalogs in ALV

Hi Friends,
Please help me out, I am new to ABAP.
Please anybody explain me the functionality of Field catalogs in ALVs?
How many methods are there to pass data to ALVs, i.e., in how many ways?
Hope u will help me.

hi,
this will be very helpful for ALV REPORTING.....
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.
The commonly used ALV functions used for this purpose are;
1.     REUSE_ALV_VARIANT_DEFAULT_GET
2.     REUSE_ALV_VARIANT_F4
3.     REUSE_ALV_VARIANT_EXISTENCE
4.     REUSE_ALV_EVENTS_GET
5.     REUSE_ALV_COMMENTARY_WRITE
6.   REUSE_ALV_FIELDCATALOG_MERGE
7.   REUSE_ALV_LIST_DISPLAY
8.     REUSE_ALV_GRID_DISPLAY
9.     REUSE_ALV_POPUP_TO_SELECT
The different steps used for getting the above function modules into use are:
Step 1
DATA DECLARATION
Sap standard type pools: SLIS , KKBLO .
Sap standard tables types taken from the type pools are: SLIS_LAYOUT_ALV ,
                                         SLIS_T_FIELDCAT_ALV,
SLIS_T_LISTHEADER,
SLIS_T_EVENT,
SLIS_SELFIELD.
Internal tables to used in the program declared based on the above table types
DATA: I_LAYOUT TYPE SLIS_LAYOUT_ALV,
            I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
           I_HEADING TYPE SLIS_T_LISTHEADER,
I_EVENTS TYPE SLIS_T_EVENT.
TYPES: KKBLO_SELFIELD TYPE SLIS_SELFIELD.
Step 2 (Optional)
SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)
The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.
Sample code:
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            i_save     = variant save condition ( A=all, U = user-specific )
       CHANGING
            cs_variant = internal table containing the program name (and the default variant---optional )
       EXCEPTIONS
            not_found = 2.
The user can also choose from the list of existing variants using the function module REUSE_ALV_VARIANT_F4.
Step 3
DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG
A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).
A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.
The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
1.     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
2.     all fields in this structure are to be output
3.     The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
The different possible attributes are:
     Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
                     Value set: 0, 1 3
     Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display.       The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.
Value set: 0, 1 60
     Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
Value set: internal output table field name (required parameter)
     Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
                     Value set: SPACE, internal output table name.
     Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the        Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
    Value set: SPACE, Data Dictionary field name.
     Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field.        This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Value set: SPACE, name of a Data Dictionary structure or table
Link to currency unit
     Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
Value set: SPACE, output table field name
     Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Value set: SPACE, output table field name.
        Link to measurement unit
     Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
Value set: SPACE, output table field name.
     Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Value set: SPACE, output table field name.
     Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
Initial = column width is the output length of the referred Data Dictionary field (domain).
N = column width is n characters.
      Value set: 0 (initial), n.
     Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
      Value set: SPACE, 'X'.
     Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.
The key column sequence cannot be changed interactively by the user. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
Value set: SPACE, 'X'.
     No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.
            'X' = field is not displayed in the current list.
        Value set: SPACE, 'X'.
     Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
                    'X' = technical field.
       Value set: SPACE, 'X'.
     Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).
'X' = column is colored with the default column highlight color.
                    'Cxyz' = column is colored with a coded color:
                  - C: Color (coding must begin with C)
                 - X: color number
                  - Y: bold
                   - Z: inverse
     Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
         Value set: SPACE, 'X'.
                    'X' = column cells are output as hotspots.
     Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.
                     Value set: SPACE, 'X'.
        'X' = column fixed (does not scroll horizontally).
     Do_sum (sum over column): the user can also call this function interactively.
                  Value set: SPACE, 'X'.
'X' = a sum is calculated over this internal output table field.
     No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
         Value set: SPACE, 'X'.
     Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
                    Value set: SPACE, 'X'.
                     'X' = column contents to be output as an icon.
     Symbol: The internal output table column must be a valid symbol character.
Value set: SPACE, 'X'
                    'X' = column contents are to be output as a symbol.
     Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
Value set: SPACE, 'R', 'L', and C.
       ' ' = Default justification for this data type
       'R' = right-justified output
       'L' = left-justified output
       'C' = centered output.
     Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
                   Value set: SPACE, 'X'.
                    'X' = output with leading zeros.
     No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.
    Value set: SPACE, 'X'.
           'X' = value output without +/ sign.
     No_zero (suppress zeros): Only relevant for value fields.
             Value set: SPACE, 'X'.
                    'X' = suppress zeros.
     Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.
           Value set: SPACE, template.
The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.
If the user changes the column width interactively, the column header text with the appropriate length is always used.
The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
     The 'long field label' is also used in display variant definition,
        Sort, etc. Popup.
     seltext_l (long field label)
     seltext_m (medium field label)
     seltext_s (short field label)
     reptext_ddic(header) Analogous to the Data element main header
     Ddictxt (specify text) : You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Value set: SPACE, 'L', 'M', and S.
Sample code:
Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).
DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV.     Local variable to hold the parameters
for a particular field of the field catalog
CLEAR L_FIELDCAT.
L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
L_FIELDCAT-FIELDNAME = 'EBELN'.
L_FIELDCAT-KEY = 'X'.         The PO no is made the key field,
                      Colored and non scrollable
L_FIELDCAT-HOTSPOT = 'X'.     The po no becomes a hotspot
L_FIELDCAT-SELTEXT_S = P.O No.
L_FIELDCAT-SELTEXT_M = 'P order No'.
L_FIELDCAT-SELTEXT_L = 'Purchase order No'.
APPEND L_FIELDCAT TO I_FIELDTAB.
CLEAR L_FIELDCAT
L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
L_FIELDCAT-FIELDNAME = 'EBELN'.
L_FIELDCAT-KEY = 'X'.         The po item no is made the key field,
                           Colored and non scrollable
L_FIELDCAT-SELTEXT_S = 'Item No'.
L_FIELDCAT-SELTEXT_M = 'Item No`.
L_FIELDCAT-SELTEXT_L = 'PO Item No'.
APPEND L_FIELDCAT TO I_FIELDTAB.
CLEAR L_FIELDCAT
Thus the catalog for the report output is prepared.
Step 4
The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.
A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.
The function module contains following import and export parameters.
IMPORTING PARAMETERS: I_LIST_TYPE
This parameter has possible values from 0-4.
The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .
EXPORTING PARAMETERS: I_EVENTS table.
This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.
The table structure contains the fields:
     I_EVENTS-NAME: Name of the Callback event.
I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.
Only events with a form routine name are processed.
The I_EVENTS table returns with the following possible constants:
1.     Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.
2.     Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to       be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that    entries are not repeated in the item table.
    RS_SELFIELD is initial in this case.
3.     Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
Is called at the beginning of the function module to make special settings. It is not usually used.
4.     Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
As this is a frequently-used Callback event, the form routine can also be passed        directly in the interface by passing the user command in the IMPORTING parameter           I_CALLBACK_USER_COMMAND.
5.     Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
   Equivalent to the list processing TOP-OF-PAGE event.
6.     Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.
The selection information and list status are output together (if they exist) on a separate page by default
7.     Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.
Analogously to TOP_OF_COVERPAGE the user can add other information
to the information output by ALV (selection information, list status) at this event.
8.     Slis_ev_foreign_top_of_page TYPE slis_formname VALUE FOREIGN_TOP_OF_PAGE'.
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
9.     Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
10.     Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a          template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
11.     Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
                                         R_INDEX LIKE SY-TABIX
                                         R_INDEX_ITEM LIKE SY-TABIX
                                         R_INDEX_SUM LIKE SY-TABIX.
12.     Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.
Information output at the start of the list
13.     Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
Information output at the end of a page. This is only called for printing.
14.     Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.
Information output at the end of the list
15.     Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
16.     Slis_ev_before_line_output TYPE slis_formname VALUE   'BEFORE_LINE_OUTPUT'.
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
17.     Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.
This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
Sample code :
FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.
DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
           I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = I_EVENTS.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
CLEAR L_I_EVENT.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
This will prepare the events table for the report.
The report will contain three forms for the above events:
1.     FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc
Using the function module REUSE_ALV_COMMENTARY_WRITE, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.
2.     FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc
3.     FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection
Step 5
A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).
Output list description structure.
     The parameters are described under the following heads:
     Display options
     Exceptions
     Totals
     Interaction
     Detail screen
     Display variants (only for hierarchical-sequential lists)
     Color
     Other
The layout table is of type slis_layout_alv_spec and has the following fields:
Display options
1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.
Value set: SPACE, 'X'
'X' = optimizes the column width so that all contents are displayed completely.
2. No_colhead(1) TYPE c : This parameter suppresses the column headings
Value set: SPACE, 'X'.
'X' = column headers are not output
3. No_hotspot(1) TYPE c : The heading of the report output are not output as hotspot.
Value set: SPACE, 'X'.
'X' = column headers are not output as hotspot
4. Zebra(1) TYPE c : The report is output in the striped pattern.
Value set: SPACE, 'X'.
'X' = striped pattern (e.g. for wide lists)
5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines. It is not relevant for: hierarchical-sequential lists and multiple-line lists.
Value set: SPACE, 'X'.
'X' = columns separated by SPACE
6. No_min_linesize(1) TYPE c : The report line size is equal to the width of the list. It is not relevant for block lists.
Value set: SPACE, 'X.
'X' = line size depends on list width
' ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .
7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.
Value set: 0, 10 - 250
If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).
8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.
Value set: 0, 80 - 1020
9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.
           10. No_uline_hs(1) TYPE c.
Exceptions
11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.
                  Output table field code: '1' = red traffic light
                                '2' = yellow traffic light
                                     '3' = green traffic light Fieldname for exception
     Value set: SPACE, internal output table field name.
12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.
.     Value set: SPACE, internal output table name.
13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.
Value set: SPACE, data element name.
           14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each
           Subtotal that includes this record is also output with 'red traffic light'.
           Value set: SPACE, 'X'
           'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.
Sums
15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up
Only by fieldcatalog.
Value set: SPACE, 'X'
'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.
16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.
Value set: SPACE, 'X'
'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.
17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.
Value set: SPACE, 'X'
'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.
18. No_subtotals(1) TYPE c : No subtotals possible
Value set: SPACE, 'X'
'X' = no subtotals.
19. Numc_sum(1) TYPE c : Totals only possible for NUMC-Fields.
20. No_unit_splitting TYPE c: No separate total lines by inh.units
21.totals_before_items TYPE c: Display totals before the items
22. Totals_only(1) TYPE c : Show only totals
Value set: SPACE, 'X'
'X' = only total records are output.
23. Totals_text(60) TYPE c : Text for 1st col. in totals
Value set: SPACE, string (max.60)
' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.
'String = The string passed is output after the total indicated by '*', if the column is wide enough.
24. Subtotals_text(60) TYPE c : Texts for subtotals
Value set: SPACE, string (max.60)
' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.
'String = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.
Interaction
25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.
Value set: SPACE, internal output table field name
26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.
Value set: SPACE, internal output table name.
27. Box_rollname LIKE dd03p-rollname: rollname for checkbox
28. Expand_fieldname TYPE slis_fieldname: fieldname flag expand. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event        'ITEM_DATA_EXPAND'.
29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.
30. No_input(1) TYPE c : The fields are only display fields.
      Value set: SPACE, 'X'
'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')
31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.
                  => LAYOUT-F2CODE = '&ETA'.
Value set: SPACE, function code
32. Confirmation_prompt: confirm. Prompt when leaving
Value set: SPACE, 'X'
'X' = if one of the functions Back (F03)', Exit (F15)' or Cancel (F12)' occurs, a confirmation prompt appears.
33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.
Value set: SPACE, 'X'.
34. Reprep(1) TYPE c : report report interface active.
35. Group_buttons(1) TYPE c : group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.
Value set: SPACE, 'X'.
36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.
Value set: SPACE, 'X'.
' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.
'X' = key columns not fixed
37. Get_selinfos(1) TYPE c : To read selection screen.
Value set: SPACE, 'X'.
If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.
38.     group_change_edit(1) TYPE c : Settings by user for new group
Value set: SPACE, 'X'
'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).
39.     No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.
Value set: SPACE, 'X'.
40. Expand_all(1) TYPE c : Expand all positions
Detailed screen
40.     Detail_popup(1) TYPE c : show detail in popup.
Value set: SPACE, 'X'
' ' = List record detail display in full-screen mode, with top-of-page.
'X' = list record detail display in popup (without top-of-page).
41. Detail_initial_lines(1) TYPE c : show also initial lines
Value set: SPACE, 'X'
' ' = Only fields whose contents are not initial are output in the detail view.
'X' = initial field contents are also output in detail.
41.     detail_titlebar(30) type c : Titlebar for detail screen
Value set: SPACE, string (max.30)
` ' = ' Detail: Display' is output as the title of the detail window.
              'String = the string passed is output as the title of the detail window.
Display variants
42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
Value set: SPACE, CHAR (20)
' ' = The header table field pushbutton text is 'Header' by default.
CHAR (20) = header table field pushbutton text.
43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
Value set: SPACE, CHAR (20)
' ' = The pushbutton text for the item table fields is 'Item' by default.
CHAR (20) = item table field pushbutton text.
44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.
     Value set: SPACE, 'X'
' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.
'X' = the item table fields are displayed by default in the display variant Definition Popup.    The user can switch to the header table fields interactively.
Colour
45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.
Value set: SPACE, internal output table field name
The internal output table field must be of type CHAR(3).
The code must have the following syntax: 'Cxy':
        C = color (all codes must start with 'C')
        X = color number ('1'-'9')
        Y = bold ('0' = off, '1' = on)
46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.
Others
47. List_append(1) TYPE c : no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.
Example code :
       I_LAYOUT-f2code       = ws_fcode.
       I_LAYOUT-zebra        = 'X'.
I_LAYOUT-colwidth_optimize = 'X'.
I_LAYOUT-no_keyfix = 'X'.
I_LAYOUT-get_selinfos = 'X'.
I_LAYOUT-no_hotspot = 'X'.
       I_LAYOUT-no_input = 'X'.
I_LAYOUT-hotspot_fieldname = FIELDNAME.
I_LAYOUT-no_input          = X.
I_LAYOUT-no_vline          = `X.
I_LAYOUT-no_colhead        = .
I_LAYOUT-lights_condense   = ` `.
I_LAYOUT-totals_text       = ` `.
I_LAYOUT-subtotals_text    = ` `.
I_LAYOUT-totals_only       = ` `.
I_LAYOUT-key_hotspot       = X.
I_LAYOUT-detail_popup      = X.
I_LAYOUT-group_change_edit = X.
I_LAYOUT-GROUP_BUTTONS     = X.
Step 6
This step is required to get the selection screen information in the report output.
The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.
The parameters to be passed in the IS_SEL_HIDE table are:
o mode:              'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES
Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.
'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.
o t_entries:         Selection info table
o t_entries-mode:   'A' = output the selection info for the current table record in the info popup.
'D' = do not output select option or SELNAME parameter selection info in   the popup.
o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.
The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.
     t_entries-field: DDIC field name of the field for which selection information is to be output.
     t_entries-table: DDIC table names of t_entries-field.
     t_entries-stext: Field name in info popup.
     If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.
     t_entries-valuf: Selection condition 'from' value (external format)
     t_entries-valut: Selection condition 'to' value (external format)
     t_entries-sign0: (I)nclusive (E)xclusive
     t_entries-option: All values of the select options Option field allowed.
Step 6
The Table IT_SORT is populated with the sort criteria for the different fields.
The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.
This internal table has the following fields:
     o spos : Sort sequence
     o fieldname : Internal output table field name
     o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
     o up : 'X' = sort in ascending order
     o down : 'X' = sort in descending order
     o subtot : 'X' = subtotal at group value change
     o group : '* ' = new page at group value change ,'UL' = underline at group value change
                         Step 7
The final step in the output of the report is the use of two ALV functions modules.
1.     REUSE_ALV_FIELDCATALOG_MERGE
2.     REUSE_ALV_LIST_DISPLAY
The first function module is used to pass the field catalog to the report output and merge it with the internal output table.
FUNCTION reuse_alv_fieldcatalog_merge.
""Lokale Schnittstelle:
* IMPORTING
*"             VALUE(I_PROGRAM_NAME) LIKE SY-REPID OPTIONAL
*"             VALUE(I_INTERNAL_TABNAME) TYPE SLIS_TABNAME OPTIONAL
*"             VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
*"             VALUE(I_CLIENT_NEVER_DISPLAY) TYPE SLIS_CHAR_1
*"                             DEFAULT 'X'
*"             VALUE(I_INCLNAME) LIKE TRDIR-NAME OPTIONAL
*"       CHANGING
*"             VALUE(CT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV
*"       EXCEPTIONS
*"              INCONSISTENT_INTERFACE
*"              PROGRAM_ERROR
Import parameters
I_PROGRAM_NAME: Program in which the internal output table is declared and populated
I_INTERNAL_TABNAME: Internal output table name
I_STRUCTURE_NAME: Structure name (structure, table, and view)
I_CLIENT_NEVER_DISPL: Hide client fields default X
I_INCLNAME: Data declarations include name
CHANGING parameter
CT_FIELDCAT: Field catalog with field descriptions
The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
1.   Performance is affected since the code of the table definition must always be read and interpreted at runtime.
2.   Dictionary reference are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
Step 8
The other function module is used to display the internal output table with the contents
FUNCTION reuse_alv_list_display.
""Lokale Schnittstelle:
* IMPORTING
*"             VALUE(I_INTERFACE_CHECK) DEFAULT SPACE
*"             VALUE(I_CALLBACK_PROGRAM) LIKE SY-REPID DEFAULT SPACE
*"             VALUE(I_CALLBACK_PF_STATUS_SET) TYPE SLIS_FORMNAME
*"                             DEFAULT SPACE
*"             VALUE(I_CALLBACK_USER_COMMAND) TYPE SLIS_FORMNAME
*"                             DEFAULT SPACE
*"             VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
*"             VALUE(IS_LAYOUT) TYPE SLIS_LAYOUT_ALV OPTIONAL
*"             VALUE(IT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV OPTIONAL
*"             VALUE(IT_EXCLUDING) TYPE SLIS_T_EXTAB OPTIONAL
*"             VALUE(IT_SPECIAL_GROUPS) TYPE SLIS_T_SP_GROUP_ALV
*"                             OPTIONAL
*"             VALUE(IT_SORT) TYPE SLIS_T_SORTINFO_ALV OPTIONAL
*"             VALUE(IT_FILTER) TYPE SLIS_T_FILTER_ALV OPTIONAL
*"             VALUE(IS_SEL_HIDE) TYPE SLIS_SEL_HIDE_ALV OPTIONAL
*"           VALUE(I_DEFAULT) DEFAULT 'X'
"             VALUE(I_SAVE) DEFAULT SPACE
"             VALUE(IS_VARIANT) LIKE DISVARIANT
"                             STRUCTURE DISVARIANT DEFAULT SPACE
"             VALUE(IT_EVENTS) TYPE SLIS_T_EVENT OPTIONAL
"             VALUE(IT_EVENT_EXIT) TYPE SLIS_T_EVENT_EXIT OPTIONAL
"             VALUE(IS_PRINT) TYPE SLIS_PRINT_ALV OPTIONAL
"             VALUE(IS_REPREP_ID) TYPE SLIS_REPREP_ID OPTIONAL
"             VALUE(I_SCREEN_START_COLUMN) DEFAULT 0
"             VALUE(I_SCREEN_START_LINE) DEFAULT 0
"             VALUE(I_SCREEN_END_COLUMN) DEFAULT 0
"             VALUE(I_SCREEN_END_LINE) DEFAULT 0
"       EXPORTING
"             VALUE(E_EXIT_CAUSED_BY_CALLER)
"             VALUE(ES_EXIT_CAUSED_BY_USER) TYPE SLIS_EXIT_BY_USER
"       TABLES
"              T_OUTTAB
"       EXCEPTIONS
"              PROGRAM_ERROR
Import parameters
I_INTERFACE_CHECK: Interface consistency check log output.
I_CALLBACK_PROGRAM: Name of the calling program
I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.
I_CALLBACK_USER_COMMAND: EXIT routine for command handling
I_STRUCTURE_NAME: Internal output table structure name
IS_LAYOUT: List layout specifications
IT_FIELDCAT: Field catalog with field descriptions
IT_EXCLUDING: Table of inactive function codes
IT_SPECIAL_GROUPS: Grouping fields for column selection
IT_SORT: Sort criteria for first list display
IT_FILTER: Filter criteria for first list output
IS_SEL_HIDE     : Selection information modification
I_DEFAULT:      Initial variant active/inactive logic
I_SAVE: Variants can be saved
IS_VARIANT     : Variant information
IT_EVENTS: Table of events to perform IT_EVENT_EXIT : Standard fcode exit requests table
IS_PRINT: Print information
IS_REPREP_ID: Initialization keys for Re/Re interface
I_SCREEN_START_COLUMN: Coordinates for list in dialog box
I_SCREEN_START_LINE: Coordinates for list in dialog box
I_SCREEN_END_COLUMN: Coordinates for list in dialog box
I_SCREEN_END_LINE: Coordinates f

Sequence number different in DB than from assignSequenceNumber()

I am using TopLink 10.1.3 DP4 (I think - inside JDev build 3565). I am attempting to use a sequence in a schema that I DO NOT OWN - I cannot make modifications tot he database sequence because there are other applications in place running against it.
The database sequence is in a 10g database, with an interval of 1 and a cache of 20.
My object uses the value of the sequence as the sole element of its primary key. I am creating a new object, registering it with a UnitOfWork using registerNewObject(obj). It seems that this does not make a clone, since the object returned by this method is the same identity as the object passed in.
My project sequencing policy is set as follows:
<project-sequencing-policy>
<sequencing-policy>
<preallocation-size>1</preallocation-size>
<sequencing-type>Use native sequencing</sequencing-type>
<name-field-handle>
<field-handle/>
</name-field-handle>
<counter-field-handle>
<field-handle/>
</counter-field-handle>
<sequencing-policy-table></sequencing-policy-table>
</sequencing-policy>
</project-sequencing-policy>
Platform is 10g
<platform-name>Oracle10g</platform-name>
The sequence is accessed through a synonym (since JDev couldn't seem to reference a sequence in a different schema from a user's login).
<sequence-number-name>EVENT_SEQ_SYN</sequence-number-name>
<uses-sequencing>true</uses-sequencing>
When I commit my new object, I can see the insert statements in the log claiming a value of 'x' for the primary key. The row in the database actually has a primary key of 'y', where 'x = y - preallocation size' and 'y = sequence last number - preallocation size'. I think I would get the right number if I could set the preallocation size to 0 (performance problems understood) but TopLink chokes on this at run-time.
Is this problem familiar to anyone?
Failing using native sequencing, I tried to write custom SQL for the insert statement, but I couldn't find any decent examples anywere on how to do that. I found in a deep google search an example that showed you could use hash (#) to reference the value of a property, but what if the value that needs to be inserted in the database is held in an indirect referenced object? For example, if I was trying to write an insert sql for a Pet object with an indirect reference (valueHolder) to its owner, and I needed to put the owner id in the row - how would I write that insert statement in the 'custom sql' pane in workbench?
Thanks for your help.
Dave

Very strange case.
I tried to reproduce it using TopLink Employee example - and couldn't.
Here's the code:
    // to get debug info
    session.setLogLevel(SessionLog.ALL);
    session.login();
    UnitOfWork uow = session.acquireUnitOfWork();
    Employee emp = new Employee();
    emp.setFirstName("sequencingTest");
    uow.registerNewObject(emp);
    uow.assignSequenceNumber(emp);
    uow.commit();
    System.out.println("firstName = "+emp.getFirstName() +"; id="+ emp.getId());And here's the log:
[TopLink Info]: 2006.01.26 04:49:05.734--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--TopLink, version: Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060116)
[TopLink Config]: 2006.01.26 04:49:06.171--DatabaseSessionImpl(18)--Connection(19)--Thread(Thread[main,5,main])--connecting(DatabaseLogin(
     platform=>Oracle9Platform
     user name=> "test"
     datasource URL=> "jdbc:oracle:thin:@localhost:1521:orcl"
[TopLink Config]: 2006.01.26 04:49:10.140--DatabaseSessionImpl(18)--Connection(39)--Thread(Thread[main,5,main])--Connected: jdbc:oracle:thin:@localhost:1521:orcl
     User: TEST
     Database: Oracle Version: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
     Driver: Oracle JDBC driver Version: 10.1.0.4.0
[TopLink Finest]: 2006.01.26 04:49:10.625--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--sequencing connected, state is Preallocation_NoTransaction_State
[TopLink Finest]: 2006.01.26 04:49:10.718--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--sequence PROJ_SEQ: preallocation size 1
[TopLink Finest]: 2006.01.26 04:49:10.718--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--sequence ADDRESS_SEQ: preallocation size 1
[TopLink Finest]: 2006.01.26 04:49:10.718--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--sequence EMP_SEQ: preallocation size 1
[TopLink Info]: 2006.01.26 04:49:11.453--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])-- login successful
[TopLink Finer]: 2006.01.26 04:49:11.703--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--acquire unit of work: 48
[TopLink Finest]: 2006.01.26 04:49:11.703--UnitOfWork(48)--Thread(Thread[main,5,main])--Register the new container bean Employee: sequencingTest
[TopLink Finest]: 2006.01.26 04:49:11.734--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--Execute query ValueReadQuery()
[TopLink Fine]: 2006.01.26 04:49:11.750--DatabaseSessionImpl(18)--Connection(39)--Thread(Thread[main,5,main])--SELECT EMP_SEQ.NEXTVAL FROM DUAL
[TopLink Finest]: 2006.01.26 04:49:12.328--DatabaseSessionImpl(18)--Thread(Thread[main,5,main])--sequencing preallocation for EMP_SEQ: objects: 1 , first: 3,469, last: 3,469
[TopLink Finest]: 2006.01.26 04:49:12.328--UnitOfWork(48)--Thread(Thread[main,5,main])--assign sequence to the object (3,469 -> Employee: sequencingTest )
[TopLink Finer]: 2006.01.26 04:49:12.328--UnitOfWork(48)--Thread(Thread[main,5,main])--begin unit of work commit
[TopLink Finer]: 2006.01.26 04:49:12.421--DatabaseSessionImpl(18)--Connection(39)--Thread(Thread[main,5,main])--begin transaction
[TopLink Finest]: 2006.01.26 04:49:12.437--UnitOfWork(48)--Thread(Thread[main,5,main])--Execute query InsertObjectQuery(Employee: sequencingTest )
[TopLink Finest]: 2006.01.26 04:49:12.625--UnitOfWork(48)--Thread(Thread[main,5,main])--Assign return row DatabaseRecord(
     EMPLOYEE.VERSION => 1)
[TopLink Fine]: 2006.01.26 04:49:12.625--UnitOfWork(48)--Connection(39)--Thread(Thread[main,5,main])--INSERT INTO EMPLOYEE (EMP_ID, L_NAME, F_NAME, GENDER, END_DATE, START_DATE, MANAGER_ID, START_TIME, END_TIME, ADDR_ID, VERSION) VALUES (3469, NULL, 'sequencingTest', NULL, NULL, NULL, NULL, {t '09:00:00'}, {t '17:00:00'}, NULL, 1)
[TopLink Fine]: 2006.01.26 04:49:12.640--UnitOfWork(48)--Connection(39)--Thread(Thread[main,5,main])--INSERT INTO SALARY (SALARY, EMP_ID) VALUES (0, 3469)
[TopLink Finer]: 2006.01.26 04:49:12.781--DatabaseSessionImpl(18)--Connection(39)--Thread(Thread[main,5,main])--commit transaction
[TopLink Finer]: 2006.01.26 04:49:12.796--UnitOfWork(48)--Thread(Thread[main,5,main])--end unit of work commit
[TopLink Finer]: 2006.01.26 04:49:12.796--UnitOfWork(48)--Thread(Thread[main,5,main])--release unit of work
firstName = sequencingTest; id=3469
If I understood correctly, the problem is x showing up in insert as a value to be assigned to PK and y actually inserted into the db. If that's the case could there be a BeforeInsert trigger on the table? To test try inserting through jdbc using concrete pk value.

SQL Server and Database Sequence

I am trying to use the Database Adapter to insert rows into a SQL Server table and have followed the directions in the other post on this topic. Those directions are specific to inserting into an Oracle Database.
If I don't insert the
<sequence-number-field></sequence-number-field>
<sequence-number-name></sequence-number-name>
fields I get an error that you can't insert into an Identity column.
When I add both of the fields in the toplink_mappings.xml file (which having the sequence-number-name for a SQL Server database which doesn't have a separate sequence object) I get this error:
[SQLServer]Invalid object name 'SEQUENCE'. Internal Exception: java.sql.SQLException: [oias][SQLServer JDBC Driver][SQLServer]Invalid object name 'SEQUENCE'. Error Code: 208
Stating that Sequence is not a valid object which makes sense.
So when I remove the sequence-number-name element I get an error when I deploy the process stating that "if you have one of the sequence elements you have to have both".
I must be doing something wrong. Any help is greatly appreciated.

Hi
In a SQL Server database, you can just use an "identity" column. An identity column is automatically populated and incremented. You don't need to put any mapping in the ODI interface. Just keep it blank.
You cannot use the ODI Sequence, because ODI Sequence will be called only 1 time for all you rows (during the "insert rows" step of the IKM), and you'll have the same number for all your rows. Not exactly what you expect for a surrogate key. Actually, it will only work if you're doing a "row by row" loading.
Otherwise, here's a workaround :
- create an ODI variable that get the max ID of your dimension table (select max(row_id) from table_dim_X)
- in your interface mapping, populate the target column with "VARIABLE + ROWNUM"
ROWNUM gives you the number of the row, in oracle database.
In SQL Server, you can use the function ROW_NUMBER()

MT940 format on Statement Number/Sequence Number

Hi Expert,
I have the following EBS source file, which has 2 sequence numbers:
As you can read that the section of :28C is the section of Statement Number/Sequence Number. According to MT940 standard, as follows:
This field contains the sequential number of the statement, optionally followed by the sequence number of the message within that statement when more than one message is sent for one statement. The statement number should be reset to 1 on 1 January of each year.
The sequence number always starts with 001. When several messages are sent to convey information about a single statement, the first message must contain '/001' in Sequence Number.
One SWIFT message may contain up to 2000 characters.
My source file's Statement Number/Sequence Number is correct, which caontains 1 statment (00006) and 2 sequence number which are: 00001 and 00002. But during EBS upload using FF_5, system only managed upload first portion of the source file, and when come to second portion, 00006/00002, it always says ERROR: EBS (00006) already exist.
But, based on MT940 standard, it should be OK.
Therefore, does anyone have any idea why SAP FF_5 cannot handle the EBS source file upload? Any further settings / configuration in order to hanlde Statement Number/Sequence Number?
Thanks in advance
sbmel

Hello,
I have encountered the same issue on MT940 with statement number/sequence number in field 28C.
Our bank sends us MT940 into 17 separate files with sequence number for the same statement number (i.e. 13040/0001, 13040/0002..... and so on) while following the rule as below
intermediate closing balance must have code :62M:
and intermediate opening balance must have code :60M:
finalclosing balance must have code :62F:
and initial opening balance must have code :60F:
However, the upload of first file in FF_5 terminated with error FV151 Termination in statement no.acct .... ; closing record 62F missing and subsequent files are with FV150 missing beginning record 60F.
Would you please share your expertise on how you managed to make FF_5 accept these MT940 files with sequence number?
Thanks in advance for your help on this.
Regards
Taro

Sequence of SPList.Fields

Similar Messages

Maybe you are looking for