Adv between base table &control block

wat is the adv of control block give some tips to proceed with CB

Hello,
It is really dependent on your requirement as to why you need a control block or a database block.
Things which are ready made in database block needs to be coded in a control block if you are going to do data manupulation using a control block,but again as I said before it really dependent on your requirement
Regards
Mohan

Similar Messages

How to perform 'block selection' in table control?

Hi,
I'm looking for an easy way to implement block selection in a table control (i.e. select one line, hit 'block select' button, select a second line, hit 'block select' button again, and all lines between first and last are selected).
I'm currently with a customer who is on 4.0b, so I can't use the wizard, it didn't exist back then.
I hope someone knows
regards,
rs

Rob,
I generated a quick screen with wizard doing the multiple select. This is the code chucks it generated
in _TOP first part is my definition of the table to be displayed and the one column on it.
TABLES:   zsd_act_salespr.
DATA:
BEGIN OF wk_rec.
        INCLUDE STRUCTURE zsd_act_salespr.
DATA:
    sel    TYPE c,
END OF wk_rec,
it_wk   LIKE STANDARD TABLE OF wk_rec.
   controls: TBLCLT_MAIN type tableview using screen 0100.   " Table Control on screen
in I01
*&spwizard: input modul for tc 'TBLCLT_MAIN'. do not change this line!
*&spwizard: mark table
module TBLCLT_MAIN_mark input.
data: g_TBLCLT_MAIN_wa2 like line of IT_WK.
if TBLCLT_MAIN-line_sel_mode = 1.
     loop at IT_WK into g_TBLCLT_MAIN_wa2
       where SEL = 'X'.
       g_TBLCLT_MAIN_wa2-SEL = ''.
       modify IT_WK
         from g_TBLCLT_MAIN_wa2
         transporting SEL.
     endloop.
endif.
modify IT_WK
    from WK_REC
    index TBLCLT_MAIN-current_line
    transporting SEL.
endmodule.
in the screen workflow
PROCESS BEFORE OUTPUT.
*&spwizard: pbo flow logic for tablecontrol 'TBLCLT_MAIN'
module TBLCLT_MAIN_change_tc_attr.
*&spwizard: module TBLCLT_MAIN_change_col_attr.
loop at   IT_WK
       into WK_REC
       with control TBLCLT_MAIN
       cursor TBLCLT_MAIN-current_line.
*&spwizard:   module TBLCLT_MAIN_change_field_attr
endloop.
PROCESS AFTER INPUT.
*&spwizard: pai flow logic for tablecontrol 'TBLCLT_MAIN'
loop at IT_WK.
    chain.
      field WK_REC-SPNUM.
    endchain.
    field WK_REC-SEL
      module TBLCLT_MAIN_mark on request.
endloop.
*&spwizard: module TBLCLT_MAIN_change_tc_attr.
*&spwizard: module TBLCLT_MAIN_change_col_attr.
in the O01
*&spwizard: output module for tc 'TBLCLT_MAIN'. do not change this line!
*&spwizard: update lines for equivalent scrollbar
module TBLCLT_MAIN_change_tc_attr output.
describe table IT_WK lines TBLCLT_MAIN-lines.
endmodule.
in the F01 nothing
Edited by: Paul Chapman on Apr 24, 2008 4:56 PM

Assigning a Value to a Base Table BLock Field

hi,
I have a form in which a block is a base table block . i need to change the value of a field. currently it shows the value of a field from the Table on which the block is based . I need to change the value of that field to display some other value of another table.
i have a written select statement like this
select name into vname from ws_emp where ecode = 101
then i have assigned to this base table field
:bt_person.ti_v_name := vname;
this i have created in the base table blocks Post query
but it is not assigning value
pls correct me and suggest me if there is any other better method to do this
Sarav

That SHOULD work in the Post-Query trigger of the block, but doing that is never a good idea. By replacing a base-table field with any value, it causes Forms automatic processing to lock the row immediately, so no other person running your form can call up the same data. And it causes Forms to think you need to update the record, so the record's status is changed to 'CHANGED' from 'QUERY'.
It would be better to create a non-base-table field in the block, and put the name into that field.

Data from 2 database blocks insert into the same base table?

Hello,
I have canvas C_NEW. On this canvas, items from 3 blocks are usable by the user.
1. Block NEW_HEAD: 3 items say X1,X2,X3
2. Block NEW : multi record text fields say Y1 thru Y10. Also a scrollbar.
3. Block NEW_ACTION: 6 buttons say B1 thru B6 (One of them is N_OK which is the item in question)
both the blocks NEW, NEW_HEAD are db blocks and have the same base table say BT. When the users click on the N_OK (after filling out the data in the NEW_HEAD block and then NEW in that order) I need the data from both the NEW, NEW_HEAD to go into the BT. Currently only the data from the NEW is going into BT. Fields in the BT table which correspond to the fields X1,X2,X3 in the NEW_HEAD remain null after clicking the N_OK button. I put commit_form in the N_OK code since both the blocks are db blocks( and as suggested by folks, it is easier to issue a commit_form than do a lot more work in writing my own SQL).
How can I achive this?
Thanks,
Chiru

I tried doing what you suggested by putting the following code in the program unit which gets called when_button_pressed.
PROCEDURE P_SAVE IS
v_lc_no number;
v_lc_seq number;
v_dmg_allow number;
BEGIN
Go_Block('B_new_head');
v_lc_no:= :B_new_head.N_LC_NO;
v_lc_seq:= :B_new_head.N_LC_SEQ;
v_dmg_allow:= :B_new_head.N_LC_DMG_ALLOW;
Go_Block('B_new');
FIRST_RECORD;
LOOP
     emessage('before insert'||v_lc_no||'-'||v_lc_seq||'-'||:B_new.order_no);
INSERT INTO ct_lc_import(
    LC_NUMBER,
    LC_SEQ,
    DAMAGE_ALLOWANCE,
    ORDER_NO,
    QTY_SHIPPED,
    UNIT_PRICE,
    DRAFT_AMOUNT,
    TICKET_DEDUCTION,
    SHIPMENT_PENALTY,
    TOTAL_DEBIT,
    DEBIT_DATE)
    VALUES (v_lc_no,
            v_lc_seq,
            v_dmg_allow,
            :B_new.order_no,
            :B_new.qty_shipped,
            :B_new.unit_price,
            :B_new.draft_amount,
            :B_new.ticket_deduction,
            :B_new.shipment_penalty,
            :B_new.total_debit,
            :B_new.debit_date);
   commit;
NEXT_RECORD;
   if :SYSTEM.LAST_RECORD='TRUE' then
         emessage('last record');
         EXIT;
   end if;
--NEXT_RECORD;
END LOOP;
EXCEPTION
   when FORM_TRIGGER_FAILURE then
      raise;
   when OTHERS then
      emessage(SQLERRM);
      raise FORM_TRIGGER_FAILURE;
END;But I can't see the records in the table eventhough the message pops up with the values before inserting the 1st record. It then exits. I would think it would atleast insert the very first record into the the table at the least.
Thanks,
Chiru

Difference between ALV and Table control

Hi folks,
i want to know the major differences between AlV and table controls.
i know that table control is designed in screen painter, but i want to know the major diff between Table control and ALV.
helpful answers will be rewarded.
Regards,
Naveen

Hi Naveen,
Basically ALV is a way to display the output and Table Control is designed in screen painter through which you can get entries in Table Control, can delete some records etc for further processing and its not use only for Display.
ALV is Application List viewer:-
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.
TABLE CONTROL:-
ABAP offers two mechanisms for displaying and using table data in a screen. These mechanisms are table controls and step loops. Table controls and step loops are types of screen tables you can add to a screen in the Screen Painter.
Rewards if useful.
Regards,
Shilpi

Marking block of rows in table control

Hi All,
I have an requirement to mark block of rows (Like 2 to 5, 7 to 11 or 3 to 15 ) in table control to delete from the table control. This functionality is available in SM30 (Table maintenance generator) and my users want same functionality for customized dialog program.
Can any one any have an idea how to write the code for marking block of entries in table control.
Thanks in advance,
Chandra

Hi,
Assign a internal table field to table control place holder , whenever you select a row in the table control , internal table field value set to 'X'.
so delete the rows from the internal table where row value set to 'X'.
Sample code :
CASE OK_CODE.
WHEN 'DELETE'.
DELETE I_TAB WHERE CHK = 'X'.
ENDCASE.
check these demo programs:
RSDEMO_TABLE_CONTROL
DEMO_DYNPRO_TABLE_CONTROL_1
DEMO_DYNPRO_TABLE_CONTROL_2
RSDEMO_TABLE_CONTROL
RSDEMO02
if you want to mark the records through code , first assign a internal table field to table control first column (say buttons which we will use to select a row)
then do like this :
case sy-ucomm.
when 'MARK'.
loop at i_tab.
i_tab-chk = 'X'.
modify i_tab.
endloop.
endcase.
Regards
L Appana
Message was edited by:
L Appana

Updating a Base Table Block Record

We have a form where there is a multi array base Table block. this is used for generating employee number for various depts. the columns are like this with some sample data
Dept Start No end No Start Date End Date
sales 1001 1100 01-Jun-2009 31-12-2050
Accts 2001 2100 01-Jun-2009 31-12-2050
HR 3001 3100 01-Jun-2009 31-12-2050
and the data is populated from its table. These Data were created at the backend while implementation and is not modified for some long time. Now the client wants to modifiy the data . i.e they want to add new set of Start nos and End nos for the existing Dept So they will add at the bottom of the Block
like this
sales 1101 1200 01-Apr-2011 31-12-2050
when they add this the end date of the existing record should get modified with sysdate as they add the new records. at any time they can add new set of numbers of any number of depts.
can u please guide me how to do this ?

If I understand correctly, you need to take the following data:
Dept Start No   end No   Start Date   End Date
sales 1001       1100     01-Jun-2009 31-12-2050
Accts 2001       2100     01-Jun-2009 31-12-2050
HR    3001       3100     01-Jun-2009 31-12-2050and change it so it is like this:
Dept Start No   end No   Start Date    End Date
sales 1101       1200     01-Apr-2011   31-12-2050
when they add this the end date of the existing record should get modified with sysdate as they add the new records.First, I will assume you are using Oracle Forms (since your question was in the Forms forum) but you didn't specify a version. In Forms, you could easily put this logic in the Block Pre-Inser t Trigger. You'll have to set the SYSDATE through DML rather then requery the block after changes are saved. This is easier than trying to find the existing record in the block and setting the SYSDATE.
at any time they can add new set of numbers of any number of depts.Is this data used for anything more than just reference? If so, what is the key value and how does making changes like this affect the existing data and relationships?
Just from the small description you gave, the process sounds very closed - meaning it is not easily changed. If this is true, than you probably need more than just "Use a Pre-Ins Trigger" answer. You also need to know how to update all of the related records that just changed because of the new department number and for this answer we'll need more information. ;)
Craig...

Non DB item in a base table block, gives frm-40202 error.

Dear All,
We are using forms6i as a front end. To simulate the error, consider the following example.
1.Create a multirecord emp block.
2.Add a non database item in the base table block.
3.Assign any value to the non database item, in the when new record instance trigger.
4.When i say F7 or F8, my block asking me like, field must be entered. Which means, my record status changed to Insert. But there is no change in base table record, since i modified only in the non base table item.
Please validate, whether i am doing anything wrong in my technique.
Regards,
Balaji

If you have a value to be used as the default value then you can use "Initial Value" property in the item level for the Non Database Item. If you do this it wont give you any problem during the query. If you create a new record then the value which you have put as the default will come automatically.

How to handle Table control in BDC? Difference between BDC & LSMW?

Hi
How to handle Table control in BDC? Difference between BDC & LSMW?
Regards,
Raghu

Hi ,
the diff b/w normal BDC and with table control is that with table control u can enter as many lineitems as u want..so during recording if u r entering 3 line items..then the program will show (1), (2) and (3) with that.
chane that fixed no to variable.
check that sample code.
in this for new customer...any no of items can be entered.
LOOP AT t_cusdata.
    REFRESH t_bdcdata.
    ON CHANGE OF t_cusdata-kunnr.
initial screen.
      PERFORM bdc_dynpro      USING 'SAPMV10A' '0100'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                              'MV10A-VTWEG'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                              '/00'.
      PERFORM bdc_field       USING 'MV10A-KUNNR'
                              t_cusdata-kunnr.
      PERFORM bdc_field      USING 'MV10A-VKORG'
                              t_cusdata-vkorg.     "'HCL'.
      PERFORM bdc_field       USING 'MV10A-VTWEG'
                              t_cusdata-vtweg.     "'HL'.
      DATA: fnam(20) TYPE c,
            fnam1(20) TYPE c,
            idx(2) TYPE c.
      MOVE 1 TO idx.
      LOOP AT t_matdata WHERE kunnr = t_cusdata-kunnr.
        PERFORM bdc_dynpro      USING 'SAPMV10A' '0200'.
        CONCATENATE 'MV10A-KDMAT(' idx ')' INTO fnam.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      fnam.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                       '/00'.
        CONCATENATE 'MV10A-MATNR(' idx ')' INTO fnam1.
        PERFORM bdc_field       USING fnam1
                                      t_matdata-matnr.      "'FIN50'.
        PERFORM bdc_field       USING fnam
                                      t_matdata-kdmat. "'ABCD'.
        idx = idx + 1.
      ENDLOOP.
      PERFORM bdc_dynpro      USING 'SAPMV10A' '0200'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                              'MV10A-MATNR(01)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                              '=SICH'.
      CALL TRANSACTION 'VD51' USING t_bdcdata MODE 'A' .
                                    UPDATE 'S' MESSAGES INTO t_err_mes.
Regards,
Sonika

Ordering a block by a non-base table field

Hello,
I have heard you can order your block by a
non-base table field by using a stored function. Does anyone know how to do this?
Lisa

In a WHEN-VALIDATE-ITEM user have to press ENTER or TAB key too !!
anyway he have to press something.
KEY-NEXT-ITEM and KEY-PREVIOUS-ITEM is a good choice.
You can create a timer who fire each second, verify that user enter something new in the field (by comparing old and new value), then do execute_query

How to control the name of custom field in data base table, added by AET

Hi,
I have added the one custom field by Application Enhancement Tool (AET).
The name of custom field has been added in the data base table as ZZFLD000004 by AET.
I need to add the some meaningful name like that ZMYPROB.
How can I control the name of custom field in the database field through AET?
Thanks,
Amit

Got the answer.
Need to click on the Enable Expert mode, then custom field name will be editable.

Transfer elements between 2 base table forms.

Environment
OS: WinXP
Oracle 10g (9.0.4.0.0) Developer suite
Scenario:
2 base table forms
Form1 is based on table1 and has 10 elements
Form1 has a button which when triggered, causes 5 of the 10 elements to be inserted in table2
Form2 is based on table2 and has 10 elements 5 of which are obtained from Form1
When I do a query-execute in Form2 to pull all the records, only records that were entered through Form2 show up. The transferred elements (record) from Form1 are not pulled up.
When I do a query->enter and search for records in Form2 that were transferred from Form1, I receive a FMR-40301 Query caused no records to be retrieved. Re-enter.
However the records transferred from Form1 are pulled up if I run a sql in the Database.
Please advice.
Here is the code that is triggered when button is pressed in Form1 to transfer elements to form2.
DECLARE
     raiDate               RAI_PROPOSAL.STAMP1%TYPE;
     raiTime RAI_PROPOSAL.STAMP2%TYPE;
     sPropNo               RAI_PROPOSAL.PROP_NO%TYPE;
     selRec               RAI_PROPOSAL%ROWTYPE;
     CURSOR getProp(propNo IN RAI_PROPOSAL.PROP_NO%TYPE) IS
          SELECT      *
          FROM          RAI_PROPOSAL
          WHERE          RAI_PROPOSAL.PROP_NO = propNo;
BEGIN
     sPropNo := :RAI_PROPOSAL.PROP_NO;
     /* Open cursor and fetch selected row */
     IF( NOT (getProp%ISOPEN) )THEN
          OPEN getProp(sPropNo);
     END IF;
     FETCH getProp INTO selRec;
     CLOSE getProp;
     /* Get date and time of transfer */
     raiDate := sysdate();
     raiTime := TO_CHAR(sysdate(), 'hh24:mi:ss');
/* list all elements being transferred - all have values so NOT NULL fields are taken care of*/
MESSAGE(selRec.cdfa_no || ', ' || selRec.con_sub || ', ' || selRec.cs_amt || ', ' || selRec.cs_source || ', ' || selRec.dept_prdir || ', ' || selRec.dept_proj2 || ', ' || selRec.dept_proj3 || ', ' ||
selRec.human_subj || ', ' || selRec.initials || ', ' || selRec.prime_agre || ', ' || selRec.prodir_fn || ', ' || selRec.prodir_ln || ', ' || selRec.prodir2fn || ', ' || selRec.prodir2ln || ', ' || selRec.prodir3fn || ', ' || selRec.prodir3ln || ', ' ||      selRec.proj_type || ', ' ||     selRec.prop_date || ', ' || selRec.prop_no || ', ' ||
selRec.prop_title || ', ' || selRec.propr_info || ', ' || selRec.school || ', ' || selRec.sol_no || ', ' || selRec.spon_typ || ', ' || selRec.sponsor || ', ' || raiDate || ', ' || raiTime || ', ' || selRec.vert_anm);
     /* Insert selected proposal into award table */
     INSERT INTO
     RAI_AWARD(CDFA_NO, CON_SUB, CS_AMT, CS_SOURCE,
               DEPT_PRDIR, DEPT_PROJ2, DEPT_PROJ3,
               HUMAN_SUBJ, INITIALS, PRIME_AGRE, PRODIR_FN, PRODIR_LN,
               PRODIR2FN, PRODIR2LN, PRODIR3FN, PRODIR3LN, PROJ_TYPE,
               PROP_DATE, PROP_NO, PROP_TITLE, PROPR_INFO, SCHOOL,
               SOL_NO, SPON_TYP, SPONSOR, STAMP1, STAMP2, VERT_ANM)
     VALUES(selRec.cdfa_no, selRec.con_sub, selRec.cs_amt, selRec.cs_source,
          selRec.dept_prdir, selRec.dept_proj2, selRec.dept_proj3,
          selRec.human_subj, selRec.initials, selRec.prime_agre, selRec.prodir_fn,
selRec.prodir_ln, selRec.prodir2fn, selRec.prodir2ln, selRec.prodir3fn, selRec.prodir3ln, selRec.proj_type, selRec.prop_date, selRec.prop_no, selRec.prop_title, selRec.propr_info, selRec.school, selRec.sol_no, selRec.spon_typ, selRec.sponsor, raiDate, raiTime, selRec.vert_anm);
     MESSAGE ('INSERTED');
     /* Commit the data inserted */
     FORMS_DDL('COMMIT');
END;

Hi,
Do you have radio buttons, a check box or a list item on your form?
I have seen this before. If the value queried from the database does not match the allowable values, the record is "silently rejected" and is not queried into the form. You say your records are in the database if you query table2 via SQL, but Forms is rejecting the records.
Look up the Forms Help for the topics "Creating a Record Group", or "Mapping of Other Values", or Search for the word "silently". It will say something like:
"Leave the Mapping of Other Values property blank to indicate that other values are not allowed for this item. Any queried record that contains a value that does not match one of the values associated with an element in the List is silently rejected. Any attempt to assign an other value is disallowed."
HTH.

How to display internal table content to table control

hi experts
 I am very new to dialog programming
 I have the Internal table in a report program containing data that needs to be displayed in table control.
 Can you explain in step by step.
 Thanks in advance.
Regards
Rajaram

Hi Raja
Dialog-driven programs, or any program started using a transaction code, are known as SAP transactions, or just transactions. The term "transaction" is used in several different contexts in the IT world. In OLTP (Online Transaction Processing), where several users are working in one system in dialog mode, the term "transaction" stands for a user request. In conjunction with database updates, it means a change in state in the database.
Programs with type M can only be started using a transaction code, in which an initial screen is defined. Programs with type 1 can be started either using a transaction code, or by entering the program name in one of the transactions SE38 or SA38. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for dialog modules, and are therefore known as module pools. Type 1 programs, or function modules can also switch to dialog mode by calling screens using the CALL SCREEN statement. The program code of the corresponding executable program or function pool must then contain the corresponding dialog modules.
Programs that are partially or wholly dialog-driven cannot be executed in the background. They are therefore sometimes referred to as dialog programs.
Transaction code
The transaction code starts a screen sequence. You create transaction codes in the Repository Browser in the ABAP Workbench or using Transaction SE93. A transaction code is linked to an ABAP program and an initial screen. As well as using a transaction code, you can start a screen sequence from any ABAP program using the CALL SCREEN statement.
Screens
Each dialog in an SAP system is controlled by one or more screens. These screens consist of a screen mask and its flow logic. Since the flow logic influences the program flow, screens are sometimes referred to as "dynamic programs". You create screens using the Screen Painter in the ABAP Workbench. Each screen belongs to an ABAP program.
The screen has a layout that determines the positions of input/output fields and other graphical elements such as checkboxes and radio buttons. The flow logic consists of two parts:
Process Before Output (PBO). This defines the processing that takes place before the screen is displayed.
Process After Input (PAI). This defines the processing that takes place after the user has chosen a function on the screen.
All of the screens that you call within an ABAP program must belong to that program. The screens belonging to a program are numbered. For each screen, the system stores the number of the screen which is normally displayed next. This screen sequence can be either linear or cyclic. From within a screen chain, you can even call another screen chain and, after processing it, return to the original chain. You can also override the statically-defined next screen from within the dialog modules of the ABAP program.
GUI status
Each screen has a GUI status. This controls the menu bars, standard toolbar, and application toolbar, with which the user can choose functions in the application. Like screens, GUI statuses are independent components of an ABAP program. You create them in the ABAP Workbench using the Menu Painter.
ABAP Program
Each screen and GUI status in the R/3 System belongs to one ABAP program. The ABAP program contains the dialog modules that are called by the screen flow logic, and also process the user input from the GUI status. ABAP programs that use screens are also known as dialog programs. In a module pool (type M program); the first processing block to be called is always a dialog module. However, you can also use screens in other ABAP programs, such as executable programs or function modules. The first processing block is then called differently; for example, by the runtime environment or a procedure call. The screen sequence is then started using the CALL SCREEN statement.
Dialog modules are split into PBO modules and PAI modules. Dialog modules called in the PBO event are used to prepare the screen, for example by setting context-specific field contents or by suppressing fields from the display that are not needed. Dialog modules called in the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
Passing Data Between ABAP Programs and Screens
How are fields from ABAP programs displayed on the screen? And how is user input on the screen passed back to the ABAP program? Unlike in list programming, you cannot write field data to the screen using the WRITE statement. Instead, the system transfers the data by comparing the names of screen fields with the names of the ABAP fields in the program. If it finds a pair of matching names, the data is transferred between the screen and the ABAP program. This happens immediately before and immediately after displaying the screen.

Field Attributes
For all screen fields of a dialog screen, field attributes are defined in the Screen Painter. If a field name in the screen corresponds to the name of an ABAP Dictionary field, the system automatically establishes a reference between these two fields. Thus, a large number of field attributes for the screen are automatically copied from the ABAP Dictionary. The field attributes together with data element and domain of the assigned Dictionary field form the basis for the standard functions the screen executes in a dialog (automatic format check for screen fields, automatic value range check, online help, and so on).
Error Dialogs
Another task of the screen processor is to conduct error dialogs. Checking the input data is carried out either automatically using check tables of the ABAP Dictionary or by the ABAP program itself. The screen processor includes the error message into the received screen and returns the screen to the user. The message may be context-sensitive, that is, the system replaces placeholders in the message text with current field contents. In addition, only fields whose contents is related to the error and for which a correction may solve the error can accept input. See also Messages on Screens.

Data Consistency
To keep data consistent within complex applications, ABAP offers techniques for optimizing database updates that operate independent of the underlying database and correspond to the special requests of dialog programming. See also Programming Database Updates.
TRANSACTION CODES
MENU PAINTER : SE 41.
SCREEN PAINTER : SE 51 .
BOTH : SE 80 .
 ONLY EXISTING PROGRAMS CAN BE VIEWED IN SE 41 , SO USE SE 38 .
CONCEPT :
STEPS :
1. GIVE TRANSACTION CODE SE 38 , CREATE A REPORT NAMED
" ZVRPRDIALOGTEST2 " . SAVE , CHECK , ACTIVATE IT .
2. THEN GIVE CODE SE 51. GIVE SAME PROGRAM NAME AS SE38 .
GIVE SCREEN NUMBER , PRESS CREATE .
3. GIVE SHORT DESCRIPTION . THEN CLICK ELEMENT LIST .
4. THE SCREEN COMES , TYPE " OKCODE " .
5. CLICK FLOW LOGIC , THE SCREEN COMES .
6. one screen will come.
7. SAVE . CHECK , ACTIVATE .
8. CLICK LAYOUT . SCREN PAINTER SCREEN COMES .
9. PRESS " F6 " . TYPE TABLE NAME , PRESS ENTER . THE SCREEN COMES .
10 . TO SELECT THE DESIRED FIELDS , CLICK THE " TO SELECT " AREA IN
EACH ROW , PRESS ENTER .
11 . AFTER CLICKING , PRESS ENTER .
12. THE FINAL SELECTION WIL COME
13 . GIVE THE NESSARY BUTTONS IN THE SCREEN PAINTER .
14 . DOUBLE CLICK IN EACH BUTTON GIVE LABLE , FUNCTION CODE .
15 . THE FINAL SCREEN WIL COME
16 . SAVE . CHECK .ACTIVATE. TO CHECK SCREEN PRESS F8.
17 . TO WRITE CODING : PRESS FLOW LOGIG .
18 . THE SCREEN COMES .
19 . DOUBLE CLICK FIRST EVENT ( MODULE STATUS _ 3000 ).
20 . PBO MODULE WINDOW COMES , PRESS TICK MARK .
21 . EDITOR COMES . SAVE .
TYPING PROGRAM IN THE EDITOR
Steps :
THE EDITOR WILL BE AS SHOWN ABOVE , NOW TYPE THE FOLLOWING CODE .
NOTE :
BEFORE TYPING CODE : TAKE COMMENTS FROM , THEN TYPE LIKE :
SET PF_STATUS ' PRSTATUS '
SET TITLEBAR 'PRTITLE' .
*& Module STATUS_3000 OUTPUT
* text
TABLES : ZVTIKFS.
DATA BEGIN OF INT_TAB OCCURS 0.
INCLUDE STRUCTURE ZVTIKFS.
DATA END OF INT_TAB.
DATA OKCODE LIKE SY-UCOMM.
DATA INDEX TYPE I VALUE 1.
* MODULE STATUS_3000 OUTPUT *
MODULE STATUS_3000 OUTPUT.
SET PF-STATUS 'PRSTATUS'. "COMMENTS TOOK
SET TITLEBAR 'PRTITLE1'. " COMMENTS TOOK
SELECT * FROM ZVTIKFS INTO TABLE INT_TAB.
READ TABLE INT_TAB INDEX INDEX.
ZVTIKFS-NAME = INT_TAB-NAME.
ZVTIKFS-ADDRESS = INT_TAB-ADDRESS.
ZVTIKFS-PHONE = INT_TAB-PHONE.
ZVTIKFS-AREA = INT_TAB-AREA.
ENDMODULE. " STATUS_3000 OUTPUT
*& Module USER_COMMAND_3000 INPUT
* text
MODULE USER_COMMAND_3000 INPUT.
CASE OKCODE.
WHEN 'INS'.
INSERT ZVTIKFS.
WHEN 'DEL'.
DELETE ZVTIKFS.
WHEN 'PRE'.
INDEX = INDEX - 1.
IF INDEX < 1.
INDEX = 1.
ENDIF.
WHEN 'NEX'.
INDEX = INDEX + 1.
IF INDEX > SY-DBCNT.
INDEX = SY-DBCNT.
ENDIF.
WHEN 'EXI'.
LEAVE PROGRAM.
ENDCASE.
ENDMODULE. " USER_COMMAND_3000 INPUT
NEXT :
SAVE , CHECK , ACTIVATE .
TO COME TO DESIGN MENU
STEPS :
1 . TRANSACTION CODE : SE 80 . OBJECT NAVIGATOR WINDOW COMES .
NOTE : IF YOUR REOORT DOSENOT COME DO THE FOLLOWING PROCESS
Vey useful link:http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Other links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d40358411d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
For Screens
http://help.sap.com/saphelp_47x200/helpdata/en/e4/2adbef449911d1949c0000e8353423/content.htm
Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f5f2b9911d2954f0000e8353423/content.htm
Processing Screens
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f682b9911d2954f0000e8353423/content.htm
Complex Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/fd/02da2a61d811d295750000e8353423/content.htm
DIALOG Programming
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://sap.mis.cmich.edu/sap-abap/abap09/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://sap.mis.cmich.edu/abap-00/
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com
http://www.sapgenie.com/abap/example_code.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.sapbrain.com/TUTORIALS/default.html
http://www.sappoint.com/abap/spmp.pdf
http://sappoint.com/abap.html
http://www.sap-img.com/abap.htm
http://sap.ittoolbox.com/code/archives.asp?i=10&t=450&a=t
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/abap/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://www.sappoint.com/faq/faqdiapr.pdf
http://www.allsaplinks.com/dialog_programming.html
Reward all helpfull answers
Regards
Pavan

Table Control + last column

Hello Friends,
i am facing a strange problem. I have created a table control using table control wizard. when I enter the values in table control select the entry and press okey button everything works fine. then I gave the program to user for test, and he came back with following issue:
He entred the data in the table control, and then he press the enter button. then he went to the last column and change the value, press again enter button, the value overwrite again ( which he has entered before ).
I went in debug mode to see what is going on, and surpringly while entring the value in the last column I press enter the control did not went to my module "Z_TAB_CTRL_modify input." rather it went in user_command. module.... and that's why it did not updated the value after user change in last column....
Any idea what I can do to fix this issue...
Regards,

Hi,
CHAIN.
ENDCHAIN.
Effect
The statements CHAIN and ENDCHAIN of the dynpro flow logic define processing chains. Between CHAIN and ENDCHAIN, the statements FIELD and MODULE can be executed. The statements between CHAIN and ENDCHAIN form a processing chain. Processing chains cannot be nested. The CHAIN statement can be specified in the event blocks at PAI and PBO , however, in the event block at PBO it has no effect.
A processing chain allows the joint processing of all the screen fields stated between CHAIN and ENDCHAIN after FIELD statements:
The contents of all screen fields combined to a processing chain by the FIELD statements can be checked in the shared conditions ON CHAIN-INPUT and ON CHAIN-REQUEST of the MODULE statement.

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

Adv between base table &control block

Similar Messages

Maybe you are looking for