Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

please answer urgent >>>>>>>>>

Former Member
0 Kudos

1. what is CHAIN AND ENDCHAIN, where is it used.

2. how to make pageup, pagedown, first page, last page,

previous page, next page and how to insert new row in table control.

8 REPLIES 8

Former Member
0 Kudos

Hi

Chain endchain is used in PAI event. Between chain endchain, only field keyword can be used. This is to make more than one input fields ready for input when any warning or error message is given.

2. To insert new line in table control, add 1 to <tablecontrol>-lines.

about the pageup and page down, i think you can use the buttons in standard toolbar.

regards

Navneeth

Message was edited by: Navneeth Saraogi

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

1) Chain and EndChain are using in the screen flow of a dynpro(screen). You use it to link fields together for validation. For example, say you have material number and plant on the screen. You wan to validate that the user has entered a valid material number and plant combination. You would use CHAIN, this way both fields will be ready for input if there is an error, user will be able to change the Material number or plant during the error processing.

CHAIN.

Field: MATNR, WERKS.
Module check_matnr_werks.


ENDCHAIN.

2) These functionalities of the table control will come automatically for you when using the table control wizard. Just make the appropriate selections during the wizard.

REgards,

Rich Heilman

Former Member
0 Kudos

Hi Baleeq

You have asked quite a few Q's and all have been answered. Please reward points and close those post.

Regards

Navneeth

Former Member
0 Kudos

Hi Ahmed,

CHAIN AND ENDCHAIN it comes in TRANSACTIONS.

when u use CHAIN AND ENDCHAIN and u give field in between CHAIN AND ENDCHAIN that means if the user enters any wrong values in that particular field then that particular field will be in enable mode and it gives a chance to enter once again or else if u dont write field in between CHAIN AND ENDCHAIN then that field will in disable mode.

Thanks

Vikranth Khimavath

abdul_hakim
Active Contributor
0 Kudos

hi ahmed.

CHAIN and ENDCHAIN is used for validating multiple fields.

You could use this in PAI event.

for eg.

CHAIN.

FIELD:F1,F2.

MODULE VALIDATE_F1_F2.

ENDCHAIN.

Pageup,down etc will be automatically available when you create table control with wizard.

Cheers,

Abdul Hakim

Mark all useful answers..

0 Kudos

suppose u have a screen with 3 fields on it,

u enter a wrong value in an obligatory field, it will grey out all the fields on the screen which will not allow u to go further , so to avoid that we use chain end chain

http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbaa4735c111d1829f0000e829fbfe/content.htm

Former Member
0 Kudos

Hi Baleeq,

If you want to ensure that more than one field is ready

for input following an error dialog, you must

list all of the relevant fields in the FIELD statement,

and include both that and the MODULE statement in a

CHAIN … ENDCHAIN block.

The FIELD statement does not only make the field ready

for input again; it also means that field contents

changed during the current PAI processing are only

visible if the field was also included in the FIELD

statement of the current CHAIN block.

check this example DEMO_DYNPRO_ON_CONDITION

These functionalities of the table control will come

automatically for you when using the table control

wizard.

Eg of table Control:

http://members.aol.com/_ht_a/skarkada/sap/table_control/

table_control.htm

1) Screen tables

A table can be created in transaction. These tables,

when designed on the screen are called as SCREEN

TABLES.

These are of two types.

Table Controls and Step loops

These tables are treated as Loops.

2)Steps for creating table control

Declaration of table control in module pool program.

Designing of table controls on the screen.

Passing data to table control in flow logic.

4)Declaration of TC in MPP

syntax:

controls <name of table control> type tableview using

screen <‘screen no.’>.

5)Designing Table control on screen

Click on Table in Control bar and place it on the

screen. You can adjust the length and width of the

Table Control.

Name the table control.(same name as given in data

declaration).

From dictionary object OR from program fields select

the fields and place them in the table control

6)Passing data to table control

Usually transfer of data from program to screen is

automatic.

In case of TC, you need to explicitly transfer the data

to table control.

ABAP/4 provides Loop statement, which is associated

with flow logic to transfer the data.

7)Passing of data contd.

PBO.

Loop at <name of internal table> with control <name of

table control> cursor <scroll variable>.

module…….

Endloop.

PAI.

Loop at < name of internal table>.Endloop.

8)Scroll variables

Top_line : the row of table where the screen display

starts.

Current_line : the row currently being processed inside

a loop.

9)Transfer of data from prg to TC.

With ‘Loop at …’ statement, the first row is placed in

the header of internal table.

If any module is specified between Loop and End loop, it

will be executed. In this module, generally we will be

assigning this internal table fields to table control

screen fields.

The row in internal table is transferred to the TC as

stated in the ‘Loop at…..’ statement.

The system encounters the ‘Endloop’ statement and

control is passed back to the next line of internal

table.

In the same way all the records of the internal table

are passed to the TC.

Reward points if helpful,

Rgds,

Sumana

Former Member
0 Kudos

HI

GOOD

Flow Logic

It is the code that processes a screen in SAP. The various event blocks of flow logic are as follows

· Process Before Output PBO

Code that is executed before the current screen is displayed

· Process After Input PAI

Code to be executed when the user does any interaction with the screen. At the end of PAI the system goes to the PBO of the next or the current screen

· Process on Help-Request POH & Process on Value-Request POV

Code to be executed when the user presses F1 or F4 respectively. At the end the system continues with the processing of the current screen

Syntax of the flow logic statements is similar to ABAP, but all ABAP key words can not be used in the flow logic. The following keywords can be used with the event blocks

· Module Calls a dialog module

· Field Indicates when screen field contents are transported

· On Used with Field

· Values Used with field

· Chain Start of processing of chain of fields

· Endchain End of processing of chain of fields

· Call Calls a subscreen

· Loop Start of processing of screen table

· Endloop End of processing of screen table

To summarize

A Transaction is a collection of screens and ABAP routines, controlled and executed by a dialog processor. Only one module pool can be associated with a transaction.

A module pool is a collection of screens, which are invoked in a pre-defined sequence to complete the task that needs to be performed.

Now we will learn the concepts described above through an example ...

-

-


Checking Fields Repeatedly

You may sometimes need to include the same field in more than one FIELD or CHAIN statement. If one of the corresponding modules sends a warning or error message, PAI processing resumes with the value that the user corrected. However, in this case, processing cannot simply resume at the corresponding FIELD or CHAIN statement if the field in question has already been included in an earlier FIELD or CHAIN statement.

Instead, all of the FIELD and CHAIN statements containing a field in which an error occurred are repeated. PAI processing resumes at the first FIELD or CHAIN statement containing a field in which an error occurred and that the user changed the last time the screen was displayed.

Example:

PROCESS AFTER INPUT.

FIELD f1 MODULE m1.

FIELD f2 MODULE m2.

CHAIN.

FIELD: f1, f2, f3.

FIELD: f4, f5, f1.

MODULE m3.

MODULE m4.

ENDCHAIN.

CHAIN.

FIELD: f6.

MODULE m5.

ENDCHAIN.

CHAIN.

FIELD f4.

MODULE m6.

ENDCHAIN.

If module M6 contains a warning or error message, the screen is displayed again, after which processing resumes with the first CHAIN statement and module M3, since this is the first occurrence of the field F4.

-

-


2->

TABLE CONTROL -

http://www.geekinterview.com/Interview-Questions/SAP-R-3

thanks

mrutyun