Answer me pls.

[Former Member]

Hi,

1)what is import and export parameter will do?

2)without table can u write function module?

3)Difference between set screen and call screen?

4)what is partner profile t.code? then what u will do in that?

5)what is the difference between okcode and sy_ucomm?

6)how u will fix the default size in table control

7)where program will store and which table?

[Former Member]

Hi,

here are my answers..

1)what is import and export parameter will do?.

Import parameter is like the input to the function module and exporting is like the output parameter to the function module.

2)without table can u write function module?

Yes. You can create a table type in SE11..Then use that in your importing or exporting parameters.

3)Difference between set screen and call screen?

call screen will back to the calling program.

4)what is partner profile t.code? then what u will do in that?

WE20 is the partner profile tcode.

Thanks

Naren

[Former Member]

Hi,

In addition to the above answers,

<i>5)what is the difference between okcode and sy_ucomm?</i>

OKCODE is ususally a variable of type SY-UCOMM

SY-UCOMM is the field into which user commands get stored on

some action performed.

<i>7)where program will store and which table?</i>

Programs created in SE38 Editor get stored in

table TADIR and TRDIR ( only the entry and not the whole

source code ).

if you want to access source code then use the

READ REPORT statement.

Regards,

Samson Rodrigues.

[Former Member]

HI

<b>1)what is import and export parameter will do?</b>

Import : These are the Values passed from Program to FM

Export : These are the Values returned from FM to Program

Changing: These are bi directional

Tables: These are internal Tables and also bi directional

<b>2)without table can u write function module?</b>

Yes we can write the FM with TABLE

<b>3)Difference between set screen and call screen?</b>

<b>SET SCREEN</b>

SET SCREEN dynnr.

This statement sets thescreen with the screen number specified in dynnr, as the next screen for processing of the current screen. For dynnr, a data object of type n and length 4 is expected. It must contain either the screen number of a screen in the main program of the current program group or the value 0, otherwise a non-catchable exception will be triggered. The specified next screen overwrites the previously-set next screen.

The next screen is automatically called when the system finishes the PAI processing of the current screen. If the screen number of the next screen is 0, the current next screen is ended.

One next screen is always set during the processing of a screen. After you call a screen, the next screen whose characteristics are defined statically, applies; this next screen can be overwritten with the SET SCREEN statement for the duration of the actual next screen processing.

<b>

CALL SCREEN</b>

CALL SCREEN dynnr

This statement calls the dynpro with the dynpro number specified in dynnr. For dynnr, a data object of type n and length 4 is expected. The call starts a new dynpro sequence, which is embedded into the current dynpro sequence. The dynpro with dynpro number dynnr is the initial dynpro of the dynpro sequence. In a dynpro sequence started by a transaction code, you can nest up to 50 other dynpro sequences.

The called dynpro sequence is terminated as soon as one of the involved dynpros branches to a next dynpro with number 0. The program continues after CALL SCREEN.

The statement CALL SCREEN accesses the dynpros of the relevant main program of the current program group and these use the global data and dialog modules of the main program. Except when calling a dynpro in an externally called subroutine, the main program usually is the current program. If the specified dynpro does not exist in the main program of the program group, an untreatable exception occurs.

By default, the screens of all dynpros of the called dynpro sequence are displayed in the current window. Use addition STARTING AT to open a modal dialog window.

Use addition STARTING AT to open a new popup level and to display all screens of the called dynpro sequence in a modal dialog window. The upper left corner of the dialog window is determined by the values col1 and lin1 for column and line. The values refer to the window with popup level 0. The lower right corner is set automatically or you can use col2 and lin2 to specify it after ENDING AT. For col1, lin1, col2 and lin2, data objects of type i are expected. The values of col1, lin1 should be smaller than those of col2, lin2, because otherwise the behavior is undefined. The maximum popup level is 9.

The called dynpro should not be a selection screen. To call a selection screen, use the statement CALL SELECTION-SCREEN.

When nesting dynpro sequences and creating popup levels, remember that usually during the program execution, you are already within a (nested) dynpro sequence and that the system itself can also create other dynpro sequences or popup levels (for example, field or input help or messages in dialog windows). For this reason, you should never use the maximum values of 50 dynpro sequences or 9 popup levels within a program to capacity.

If during the processing of a modal dialog window a new dynpro sequence is called, it must be started in another popup level. You cannot use the statement CALL SCREEN without addition STARTING AT in this case.

When calling a dynpro in a dialog window, specify the window as a modal dialog window in its properties and set an appropriate GUI status beforehand. We recommend that a dynpro sequence in a modal dialog window consists of one dynpro only.

<b>4)what is partner profile t.code? then what u will do in that?</b>

You need to maintain partner profile (transaction: WE20) to exchange EDI documents with the business partners. So in the profile you define a partner number, partner type(customer/vendor), EDI message exchanged (for eg. 850, 810).

<b>5)what is the difference between okcode and sy_ucomm?</b>

sy-ucomm is for doing the functions what the user wishes to do at that particular event. You use it in menus and other place . this mainly in using <pfstatus>

ok_code is generally used in screen as of I have used. You will define the function in the screen. and you can use it in the main program.

ok_code acts just as a temporary variable that stores the value of sy-ucomm.

When user interacts with the screen elements, the function code that you have assigned is filled in the sy-ucomm field which is turn gets reflected in OK_CODE.

In your ABAP programs, you should work with the OK_CODE field instead of SY-UCOMM. There are two reasons for this: Firstly, the ABAP program has full control over fields declared within it, and secondly, you should never change the value of an ABAP system field. However, you should also always initialize the OK_CODE field in an ABAP program for the following reason:

In the same way that the OK_CODE field in the ABAP program and the system field SY-UCOMM receive the contents of the corresponding screen fields in the PAI event, their contents are also assigned to the OK_CODE screen field and system field SYST-UCOMM in the PBO event. Therefore, you must clear the OK_CODE field in the ABAP program to ensure that the function code of a screen is not already filled in the PBO event with an unwanted value. This is particularly important when the next PAI event can be triggered with an empty function code (for example, using ENTER). Empty function codes do not affect SY-UCOMM or the OK_CODE field, and consequently, the old field contents are transported.

<b>6)how u will fix the default size in table control</b>

If you use below code for your VA42 ,then table controls number columns will not vary from pc to pc :

data: f_option type ctu_params,

f_option-updmode = 'S'.

f_option-defsize = 'X'.

f_option-dismode = 'N'.

call transaction 'VA42' using bdcdata options from f_option messages into bdcerror.

I know your requirement ,screen resolution will not solve your problem

Check the below link :

http://web.mit.edu/sapr3/dev/newdevstand.html

http://web.mit.edu/ist/org/admincomputing/dev/abapstds/current/devstand8.html

<b>Reward if usefull</b>