FIELD RELATING TABLES

can anyone give me the fields relating EBAN, EKKO and EKPO

EBAN- it's the purchase requisition table
when u create a purchase requisition using ME51N it's saved to this table.
EKKO- Purchasing Doc Header
EKPO- Purchasing Doc Item
When u create a purchase order using ME21N, data go to these 2 tables.
as per relation is concerned if u generate a PO with respect to a PR then there is a relation between EBAN & EKPO
EKKO - EKPO mapped with EBELN
EKPO - EBAN mapped with BANFN & BFNPO
Reward if useful

Similar Messages

Screen field related table information

Hi all,
In SAP standard transaction most of the screen fields will reffer to some dictonary field or some table field. I know that if a screen field refers to dictionary table field that screen field value will save in that dictionary table field. My doubt is that is there any way to find out in which table field the data we are entering on the screen field will go be saved if the screen field refers to a dictionary structure field . The only solution is to look through the code ? please kindly help
Regards,
Kasi S

to which transaction u need this info
for sales order va01 or va02 it is T180 .
for purchasing or me21 /me22 it is t160 "just check once.
i think we dont have a specific generic table where the contents of the screen field data pertaining to transactions are stored .
we need this info only at the time of user exits for screen processing.
regards,
vijay

Select Distinct Fields from non related table

Hi Experts,
I have to fetch Distinct Fields from table zdcxy along with the fields from the table zvend but there is no primary key forigen key relationship also if I wanted use join condition. I need to move fields from both the table into output file and 1 part I implemented but I am unable to do second part plz any body can help me its argent. below I pasted part of code along with two requirements.
1.Select all data (Location - LIFNR, Descr u2013 ZPLTNAMEC, CJI_CUSTOMER u2013 CJI customer flag) from ZVEND table.
2.Select all distinct DCs and BUs from zdcxy table.
SELECT * FROM ZVENDPLT INTO CORRESPONDING FIELDS OF TABLE IT_VENDPLT.
*select distinct zdc from zdcxy into corresponding fields of table it_map.
*select distinct zbu from zdcxy into corresponding fields of table it_map.
IF SY-SUBRC = 0.
    LOOP AT IT_VEND.
      MOVE : IT_VENDPLT-LIFNR              TO IT_TAB-FIELD1,
              IT_VENDPLT-ZPLTNAMEC          TO IT_TAB-FIELD2,
              IT_VENDPLT-CJI_CUSTOMER       TO IT_TAB-FIELD3,
       CONCATENATE :IiT_TAB-FIELD1   IT_TAB-FIELD2   IT_TAB-FIELD3   IT_TAB-FIELD4
INTO IT_LOAD-RECORD SEPARATED BY SEPARATOR.
      TRANSFER IT_LOAD TO OUT_FILE.
ENDLOOP.
Can any body explain me hw to fetch DC and Bu from the table zdcxy and keep in the same loop of   it_vend.
Second thing is that I need to give information about records into second output file hw to do that means I opened one more file and I am unable to move the record history there plz help me.
Thanks in advance

Plz any body can help me it's argent.
Thanks
Basu

Field and Table for PGI status updation

Hi All,
I want to know in which field and table the PGI status will get updated.
i.e. once we do the PGI for a delivery in which table will this PGI status gets updated.
Thanks in advance for help.
Harini

Hi Harini,
In Table VBUK you 3 different status related fields for sales documents.
Over all status field name GBSTK ( here it gives the total status of praticular sales document) here you see options
A Not yet processed      ( This means its complete open)
B Partially processed     ( This means the sales doc is partially processed)
C Completely processed ( This means the sales doc is completly processed)
Delivery status and over all delivery status field name LFSTK and LFGSK respectively, these 2 fields will be same always ( here it gives the total status of praticular sales document) here you see options
A Not yet processed      ( This means its completly open)
B Partially processed     ( This means the delivery doc is partially processed)
C Completely processed ( This means the delivery doc is completly processed)
So overall status can be different then delivery or overall delivery status.
If sales document has 100 quantity for 1 material, if delivery is done for 50 quantity.
Then over all status field name GBSTK will be B Partially processed and delivery and overall delivery will be C Completely processed .
Regards
vK

Where can i get SALES ORGANIZATION FIELD and TABLE

Can anybody tell me where can i get FIELD and TABLE Name OF " sales organization "

Dear Sandeep,
u will find VKORG is the Sales Organisation .
u will find this Field in every related SD Module Table...
Like ...VBAP,BKPF ..etc..
Hope it helps...!!!
Pls reward if Helpful...!!!

CRMT_BW_DS_ACTIVITY- Field and table origin

Hi Guys,
I am working with this extractor CRMT_BW_DS_ACTIVITY. I am trying to find the origin table and the origin field for each of the fields in this extractor.The sap help document is of no use, for example the first field i look at in the help is ACTIVITY_PARTNER (extract stucture field), the sap help says the origin table is PARTNER and origin field is PARTNER_NO. But in the CRM system there is no table called PARTNER. Can some one shed light on this please.
Thank you and points for useful replies

hi,
add CRMD_ ...
you can try BWA1 and give datasource name,
tab 'mapping', add CRMD_ to value in column Segmentname.
e.g field ACTIVITY_PARTNER, table name is CRMD_PARTNER
How to find out the tables related to CRM datasources?
hope this helps.

What is the field and Table for "Batch Class" and "Class Type" in QM.

Hi All,
What is the field and Table for "Batch Class" and "Class Type" in QM.
Thanks,

Hi,
For batch class the class type value is '023' . This you can find from KLAH table and the fileld for class type is KLART..
And also all the data related to batch class are found in tables INOB, KLAH,KKSK and for the characeteristics of batch materials you can refer AUSP table.
In INOB table, for batch class, you need to give 023 in KLART field and value MCH1 in OBTAB filed.
Please check this and let me know if this you need any more details?

Want field and table name for RESERVED coloum in MMBE

Hi ,
        There is a RESERVED coloum in MMBE and     I want this   * RESERVED* coloum in MB52   .
       I got to know that Field related to this RESERVED coloum is BDMNG coming from table RESB .
       To confirm the field and table I checked the value in BDMNG by putting join on MARA and RESB where MATNR = BAUGR.
        But I got value in BDMNG is 50 and in MMBE it is .228 for that material.
           Please tell me field and table name for RESERVED coloum. and hoe to join MARA and RESB to get exact result.
Thanks and Regards,
Ranu

Hi,
Mara-matnr is not equal to Resb-matnr and it shows no record if i do like this.
But Mara-matnr is equal to Resb-baugr, and it gives me 1 record .But porblem is that i dint get BDMNG field matching with mmbe RESEVERD coloum.

Stock related tables

Sir,
i want table name to see stock on date basis for stock register. If any one hvaing alv report on stock register with date & storage location wise please help me.
Actually, MB5B report is also very good but i am not getting ALV LIST storage location wise.
thanks & regards
Manoj.

Hi,
the stock related tables are....
MKPF-> header
MSEG-> Item
Here MENGE is the stock field.....And DMBTR is the Value of that stock....Also there is a field SHKZG (Debit/credit indicator) where
H     Credit
S     Debit
Check the stock manually with respect to this field....
LOOP AT it_mseg1 INTO wa_mseg1.
    wa_mseg2 = wa_mseg1.
    IF wa_mseg1-shkzg EQ 'H'.
      sum = sum - wa_mseg1-menge.
    ELSEIF wa_mseg1-shkzg EQ 'S'.
      sum = sum + wa_mseg1-menge.
    ENDIF.
    AT END OF matnr_bwtar.
      wa_mseg3-matnr_bwtar = wa_mseg2-matnr_bwtar.
      wa_mseg3-matnr = wa_mseg2-matnr.
      wa_mseg3-menge = sum.
      wa_mseg3-werks = wa_mseg2-werks.
      wa_mseg3-meins = wa_mseg2-meins.
      wa_mseg3-ebeln = wa_mseg2-ebeln.
      wa_mseg3-bwtar = wa_mseg2-bwtar.
      APPEND wa_mseg3 TO it_mseg2.
      CLEAR: wa_mseg3,sum.
    ENDAT.
    CLEAR: wa_mseg2,wa_mseg1.
ENDLOOP.
Arunima
Edited by: Arunima Rudra on Dec 16, 2008 12:37 PM

How to trigger a 'delete' across different related tables in ABAP?

Hello All,
I am creating database tables for storing different values of features coming under different countries. I have eight tables in my design and there are fields repeating in different tables, which i am connecting through foreign key relationship.
After entering values to all my tables, if i need to delete a particular field value which is repeating in more than two tables, is it possible to trigger a delete event by which if am deleting the field value in a particular table, all the related field values also get deleted from the respective tables?
For example, if i have a PRODUCT field in three tables, and if one of the PRODUCT is deleted from a particular table, can i trigger a delete event by which i can delete all the values related to that particular PRODUCT from all the related tables? The PRODUCT is a primary keyfield, and i have maintained proper foreign key relations also.
I have tried deleting entries using the views and using the database table itself, but only that particular table value is being deleted.
Is there any function module for triggering a delete?
Can anyone help me with some solution?Sample code will be helpful.
Thanks in Advance,
Shino

Hi,
My friend it is not advisable to delete any field from a database table bcoz it's creats incosistance data for all the other related tables, but there r few Function Modules that provide u this functionality.
Such As:
G_REPORT_DELETE_ADDFLD_ENTRY
G_CATT_DELETE_TABLE_ENTRY
RKE_DELETE_FIELDS_FROM_TABLE
Regards

Display read only field in table / form from another vo

i came across couple of scenarios where i had to bring a field in a table / from from other vo than on which most fields in table / form were based. in all cases i had to display the field from another vo as read only and there was only one record in other vo which was related to previous vo in table / form. for this i created a view accessor and created a soc with model driven lov. the problem with this is that first element alwasy shows blank in soc. how can i display the filled soc with first element populated and read only in this scenario. i tried alternatively with groovy expressions but other people in team said it is not good practice to use groovy expressions to fill fields in one VO from other VO. how can i acheive this requirement with soc component / lov / view accessors. is there any other alternative as well. jdev 11 1 1 5

1) in the attribute of the VO select the 'List of values' node and edit the list attribute you see there; in the dialog select the UI Hints tad and make sure the checkmark for the 'Include "no Selection Item' is off.
2) you can base a VO on to EO which are then joined via one or more attributes (association)
Timo

How to provide F4 help for a field in table control

Hi Friends,
I have requirement like below.
1.Create one custom transaction code with header and item information.
2.In item level, we will be designed table control to enter/display the data.
3.Table controls first field will be material number and next DOT number (Material may have many DOT numbers) and so on.
4.First user will enter material number in the table controls first rows first field and go to DOT number field.
5.DOT number has drop down option. If user selects drop down box of DOT number, he gets all the DOT numbers available in database. User selects one DOT number and double clicks on it then it will be populated in DOT number field box.
But for point number 5, business wants like when ever user enters material number in table control first field then select DOT numbers drop down then they want to see the particular materials DOT numbers only in the drop down list for selection. Not all DOT numbers available in data base. Same thing should happen for all item lines in table control.
Please see below example.
Assume data base table has 10 DOT numbers. But material number has only 2 DOT numbers. When ever user enters material number in item level table control and selects DOT numbers drop down then it should show only 2 DOT numbers which are related to particular material number. Not all 10 DOT numbers.
Could you please suggest me, how can we achieve this?

Hello,
Check this :-
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. The module <mod> is defined in the ABAP program like a normal PAI module. However, the contents of the screen field <f> are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
CARRID TYPE SPFLI-CARRID,
CONNID TYPE SPFLI-CONNID,
END OF VALUES.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
DYNNUM LIKE SY-DYNNR,
DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
TABNAME = 'DEMOF4HELP'
FIELDNAME = 'CARRIER1'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = PROGNAME
DYNUMB = DYNNUM
TRANSLATE_TO_UPPER = 'X'
TABLES
DYNPFIELDS = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
FROM SPFLI
INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'CONNID'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CONNECTION'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH------------
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> [MODULE <mod>] WITH <num>.
After PROCESS ON HELP-REQUEST, you can only use FIELD statements. If there is no PROCESS ON HELP-REQUEST keyword in the flow logic of the screen, the data element documentation for the current field, or no help at all is displayed when the user chooses F1. Otherwise, the next FIELD statement containing the current field <f> is executed.
If there is screen-specific data element supplement documentation for the field <f>, you can display it by specifying its number <num>. The number <num> can be a literal or a variable. The variable must be declared and filled in the corresponding ABAP program.
You can fill the variables, for example, by calling the module <mod> before the help is displayed. However, the FIELD statement does not transport the contents of the screen field <f> to the ABAP program in the PROCESS ON HELP-REQUEST event.
For further information about data element supplement documentation, refer to Data Element Supplements.
Calling Help Texts from Dialog Modules
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON HELP-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F1 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. However, the contents of the screen field <f> are not available in the module <mod>, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. The field help should not be dependent on the user input.
The module <mod> is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
VAR(4),
INT TYPE I,
LINKS TYPE TABLE OF TLINE,
FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
WHEN 1.
VAR = '0100'.
WHEN 2.
VAR = '0200'.
INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
EXPORTING
DOKLANGU = SY-LANGU
DOKTITLE = TEXT-002
CALLED_FOR_TAB = 'DEMOF1HELP'
CALLED_FOR_FIELD = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
EXPORTING
DOKCLASS = 'TX'
DOKLANGU = SY-LANGU
DOKNAME = 'DEMO_FOR_F1_HELP'
DOKTITLE = TEXT-003
TABLES
LINKS = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Regards,
Deepu.K

How to updated matrix into related table?

hi, can anyone help me below coding how to updated matrix into related table?
Thank you.
            For rowNum = 0 To oMatrix.RowCount
                oRecordset.Fields.Item("Code").Value = oMatrix.Columns.Item("DSCode").Cells.Item(rowNum).Specific.Value
                oRecordset.Fields.Item("Name").Value = oMatrix.Columns.Item("DSName").Cells.Item(rowNum).Specific.Value
                oRecordset.Fields.Item("U_RPTC").Value = oMatrix.Columns.Item("DSReport").Cells.Item(rowNum).Specific.Value
                oRecordset.Fields.Item("U_USRC").Value = oMatrix.Columns.Item("DSUser").Cells.Item(rowNum).Specific.Value
                oRecordset.MoveNext()
            Next

For Fast Matrix Loading you can user some thing like this.
        Dim Column As SAPbouiCOM.Column
        Dim Matrix As SAPbouiCOM.Matrix
        Dim Table As SAPbouiCOM.DataTable
        Table = oForm.DataSources.DataTables.Add("Documents")
        Table.Columns.Add("Code", SAPbouiCOM.BoFieldsType.ft_Integer)
        Table.Columns.Add("Name", SAPbouiCOM.BoFieldsType.ft_Integer)
        Table.Columns.Add("U_RPTC", SAPbouiCOM.BoFieldsType.ft_AlphaNumeric, 255)
        Table.Columns.Add("U_USRC", SAPbouiCOM.BoFieldsType.ft_AlphaNumeric, 255)
        Matrix = oForm.Items.Item("MatrixUID").Specific
        Column = Matrix.Columns.Item("Code")
        Column.DataBind.Bind("Documents", "Code")
        Column = Matrix.Columns.Item("Name")
        Column.DataBind.Bind("Documents", "Name")
        Column = Matrix.Columns.Item("U_RPTC")
        Column.DataBind.Bind("Documents", "U_RPTC")
        Column = Matrix.Columns.Item("U_USRC")
        Column.DataBind.Bind("Documents", "U_USRC")
        Table.ExecuteQuery(SQLQuery)
        Matrix.LoadFromDataSource() 'Load The Data to the Matrix
To pull the data form the display back to the Table you can use this
Matrix.FlushToDataSource()

Adding field to Table Control using screen exit

Hi Folks,
I have a requirement of adding a field in Table control of Standard SAP transaction also updating the same in standard SAP database table.
The field is also not existing in the table, it is also added to the table using Append Structure.
Will this be possible using some Screen Exit?
Thanks in Advance.
Punit

Hi Punit,
There are various screen user exits(QQMA0001,QQMA0008,QQMA0010,
QQMA0011,QQMA0012) available for this transaction but all are related to adding a subscreen.So, I am not very sure whether we can modify a table control for this transaction. So, If possible if u r requirement still can be acheived with creation of a subscreen then it would do only if the exits which were mentioned above belongs to u r main screen..
Regards,
Swaroop

Converting Relational Tables to Object Views

We have extra information stored for each
field in a table. We call these Vertical
Tables:
rowid primary key - ties to normal tab
column_name "" - ties to column in ""
text_value the value if text
reliability rating for level of accuracy...
date of entry
Yes there are normal tables that the applications also access if they just need the value of the columns.
So I want to take this to object views. This way, while oracle is learning how to alter objects, we can still maintain our data and old application while converting to the use of objects.
I thought the best solution would be Type(s) based on the orignal data type. A generic type, text65_t could be created to hold every column that is less than 65 characters long:
CREATE TYPE text65_t AS OBJECT
WITH OBJECT IDENTIFIER(row_id) AS
row_id VARCHAR2(30),
value VARCHAR2(65),
reliability NUMBER(1,0),
doe DATE
A view can easily be created of this. The
mapping is one to one.
My problem is the next level. How can I build another view on top of text65_t, integer_t, date_t... that ties all of the
vertical rows back into a normal relational table or object.
Thanks,
bill
null

Hi migration group,
I realize this is kind of off topic for
this discussion group. Where can I ask
questions like this?
thanks
bill

FIELD RELATING TABLES

Similar Messages

Maybe you are looking for