System restart error in Module pool

Hi Experts,
I have created one modulepool Prgram with Table control it is working fine for Display, whenever i want to try to Save i am getting system error System Restarted;Session terminated. i am attatching the screen shot of that..

Hi Vishwanath,
You can use the following coding to check with your coding part.This may help you to clear your problem.
module USER_COMMAND_0100 input.
case sy-ucomm.
when 'SAVE'.
modify ztable from ztable.
if sy-subrc = 0.
message 'record updated succesfully' type 'S'.
endif.
Endcase.
endmodule.

Similar Messages

Runtime Error in Module Pool

Hi,
I am developing a module pool, i have to update the transaction through my module pool, so i am using call transaction method . first i have written the perform with recording steps .. but when i tried to activate the main program i am getting an error saying that
Include ZMPPMTR_INCL
Incorrect nesting: Before the statement "FORM", the structure
introduced by "IF" must be concluded with "ENDIF". .
but in my program there is no if ..endif statement , why i am getting this error can any one giv me a solution for this?
waiting for ur reply...
Regards
Srinath

hi,
in module pool the mail program contains top include and possibly other includes along with screen,
so save all the components of the main program and come to main program and then activate then the system recognizes all the components and activates accordingly.
try the following
use pretty printer to show the indentations.
double click on the error message it will take you to where the error occured.
try to find the if or endif or form or endform.
hope this will serve your purpose.
Thanks and regards
Ramchander Rao.Krish

Runtime errors in module pool programming

HI all,
I have done a module pool program for invoice tracking level wise.
I am encountering a runtime error, LIST_TOO_MANY_LPROS, while execution ie., for two and more than two updations of the database.
The error analysis says that "At present, the maximum permitted number of nested screen levels is restricted to 50".
Short Text :- "No further list processing possible".
Can anyone please come out with a solution for this problem.
regards
samarendra.
Edited by: samarendra penugonda on Nov 5, 2008 5:03 AM

Hi
U should replace the comand CALL SCREEN with LEAVE TO SCREEN.
The command CALL SCREEN create an internal mode to link the calling screen to called screen automatically: in this way when it needs to back to calling screen it doesn't need to specify the screen number but only to use:
- LEAVE TO SCREEN 0.
or
- SET SCREEN 0. LEAVE SCREEN.
Now if you use LEAVE TO SCREEN, u need to indicate the screen when it needs to back to calling screen:
- Go from 100 to 200
LEAVE TO SCREEN 200. (Instead of CALL SCREEN 200)
- Back to 100.
LEAVE TO SCREEN 100. (Instead of LEAVE TO SCREEN 0)
Max

Error in module pool program

Hi All,
I have created 1 module pool program with screen no. 0100. But the statement CALL SCREEN 0100 is not getting executing its showing error i.e ' statement cannot be accessable' even i have created and activated the sceen 0100.
Thanks...
kiran

Hi kiran,
Open you program in se38 menu bar -> GOTO -> ATTRIBUTES and check wheather it is executable program or module pool program.
if it is exeutable program then u can call the screen 0100 as ur intial screen. if not ur given type as module pool then u have to create a transaction in SE93 and give the screen name in that and prgoram name then it will display the screen which u hv created .
if you want to show the screen 0100 as ur initial sceen in module pool program without using transaction it is not possible so use either executable program and use the stament call screen 0100.
<b>reward if useful </b>
Regards,
sunil kairam.

Using FM DD_POPUP_TO_CONFIRM_CANCEL giving error in module pool program

HI,
I am using FM DD_POPUP_TO_CONFIRM_CANCEL in my module pool program.
But when the cursor comes to the FM it is throwing error like
*CALL SCREEN (not modal) in modal dialog box not allowed.*
i am using the below code.
CALL FUNCTION 'DD_POPUP_TO_CONFIRM_CANCEL'
       EXPORTING
            textline1    = 'UFN Preprint record created!'
            textline2    = 'Proceed to Add more States ?'
            title        = 'Confirmation'
            start_column = 25
            start_row    = 15
            defaultpos   = 'C'
       IMPORTING
            answer       = lv_answer.
Regards
Jai

Hi,
Please try to use FM: 'POPUP_TO_CONFIRM'.
Cheers,

How to throw error in Module pool

Hi Experts,
I have one probelum in Module pool Programm and i need you solution,
i have 10 input fields in module pool, and the first field is land1,
when i will give input in land1 as "US" so it should throw error "not allowed"
and all the field should be enable. should not be disable
please help me out.
thanks
Vikash

Hi Vikas,
try this,
if LAND1 EQ 'US'.
MESSAGE 'No Data can be found!' TYPE 'S' DISPLAY LIKE 'E'.
LEAVE LIST-PROCESSING.
endif.
Regards,
Venkat.

Strange Syntax Error in module pool table control........

Hi Techies ,
In module pool am not able to validate the checkbook field that i have included in the table control screen .
i was able to pass the other field defined in the same structure where checkbox field is declared .

Hi MAX and Glen ,
Thanks for ur answers .
i was not the one developing and i didnt had much touch in TBCL.
Anyways issue resolved , it was sitting outside of TBCL hence i deleted and created new and included the CHK .
now its working .
Positive and quick gestures from you both .

Error in Module pool:Function code

Hi All,
I am using IW52 transacion for which I have activated the Screen exit and inserted table control on it.
The table control entries has to be deleted for which I have added a Delete button with function Code 'DELE'.
When trying to delete the entry the system throws an error message saying that 'The function code DELE is not available here'.However after pressing enter the entries are deleted.
I have debugged for the error and could find that the table T185F is being checked in the function module screen sequence.
Could someone please let me know how to customize the table with the function code I have added.
Thanks.
Arvind

Hi Neha,
The link says that we cannot enter Custom User command in the SAP Screen exit.But I think there is a way to maintian T185* table in VFBS transaction.
I tried the same and now not getting the error message that "Function code XXX is not available here".
The problem is now that the system is always keeping the OLD sy-ucomm value.That is when I press delete records I get a confirm prompt message ( custom ) and record gets deleted.After this I again press enter the pop up comes again.
I checked in de bugging and found that the sy-ucomm was not cleared.I tried to clear sy-ucomm values but the main program of the transaction again resets the Sy-ucomm.
Please let me know if you or anyone has any solution to deal with this.
Thanks.
Arvind
Edited by: Arvind Soni on Jan 19, 2009 11:34 AM
Edited by: Arvind Soni on Jan 19, 2009 11:34 AM

Error Invalid field format (screen error) in module pool

Hi
experts i am doing module in whichi had many check boxes on screen and each check box has function code means i want to do some thing else . but as i click the first or any other check box i get a error message
INVALID FIELD FORMAT (SCREEN ERROR).
Can anyody help me with this asnwers will be rewarded points .
regards

Dear Farukh,
can you please let me know how have you declared you check boxes.
how did you handle the click or the function codes in the user command module in your PAI.
The declaration of your fucntion codes can be done when you create your screen fields and then they need to be handled in the user command module i.e what you want to do when suppose you click on that particular check box.
Thanks
venugopal

Error in module pool

hii frnds
well i am geting a dump when i am scrolling down the output of my program
the dump message is
A conversion error occurred while the program was trying to
display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. When attempting to
display the date on the screen, an error will occur that triggers the
error message.
              Screen name.............. "SAPMZCFORM"
              Screen number............ 9001
              Screen field............. "WA_ZCFORM-NETWR"
              Error text............... "FX015: Sign lost."
can anybody help me wid this
thanking u
rohit

Hi,
curiously enough, exactly today I encountered the same problem (short dump) while trying to show a negative value in the INPUT/OUTPUT screen field of type DEC.
Thanks, Naimesh, your proposal to put 'V' in the place of the last "_" in the format options of the filed helps me to avoid dump.
Thanks,
Ivaylo

Error in Module pool/Screen while passing value as Decimal value

Hi Experts,
We have designed one customized screen with CHAR as input option to pass on Tax Percentage. We have defined as CHAR in screen logic as well as program also.
Where as while we enter value with decimals like 2.5 or 5.4 its throwing a error message "Entry is too long for the field". But when I pass on Integer values like 2 or 4 then its working fine.
Can you pls suggest on this how to rectify this error.
Thanks in advance.
VJ

Hi,
Increase the length of the character field in the screen as well as in the program declaration.
Example;
DATA gv_tax(10) type C.
Regards
Karthik D

Error in editing table control in module pool

Hello Abap experts,
I am working on module pool.
When I am editing row in table control if table control has only one row to edit(By clicking edit push button) then I am getting error as "Dynpro_Field_Conversion error" in module pool.
Error is showing in PBO 'module fill table control'.
But if there are more than 1 rows in table control it doesn't give any error and run successfully.
So please help me on that.
Thanks!
Abhay.
Edited by: abhayjoshi01 on Sep 29, 2010 12:12 PM

Hi,
Can you explain in detail what field(is it quantity, currency etc) you are trying enter and what data.
If you are getting any runtime error can you provide the runtime details.
Regards,
Kranthi

How to write module pool program

hai,
what is the module -pool program ?
what are the procedures to write the module-pool program.
plz give the simple program for module-pool programs?
regards
surender

Hi
This component though is not attached to the screen painter, plays important role in transaction. Normally, for reports, on line executable programs are written but for transaction, Module Pool Programs are written. The module pool program contains only modules to handle various events associated with screen and data declaration statements.
System divides the module pool program into several include program. These are global field, PBO modules, and PAI modules. It is entirely users decision whether to use these modules or write directly into main program.
Creation of Module Pool Program
You can create module pool program either through
Object browser
System automatically creates the module pool program and for these program which are created through object browser, system creates the include modules.
Or
ABAP/4 editor
It is similar to normal program creation. Type of program should be given M and is not created by system.
Communication between Dynpro and Module Program
For each screen, the system executes the flow logic, which contains corresponding events. The control is passed to Module Pool Program. Module Pool Program handles the code for these events and again passes back control to the flow logic and finally to screen. Unlike on line program, in this case, the control remains with flow logic. The switching of control between flow logic and module pool program and back is common process when user executes transaction.
Creation of a Complete Transaction
Steps involved to create a complete transaction
     Create module pool program.
     From screen painter create screens.
     Write flow logic for each screen.
     Write code for all the events in module pool program.
     Check for any error in screen and flow logic.
     Generate each and every component of screen i.e. flow logic and screen.
     Single screen can be tested using Screen Painter.
     Create transaction code through object browser.
     Generate the transaction code.
     User can execute the transaction by entering the transaction code in the command field.
Handling Function Code
The function code or OKCODE is the last field of Field list. Function code can be handled as follows:
During the Designing of the screen, a function code is assigned to pushbutton.
     In field list, developer needs to specify OKCODE as last field.
     In module program it is a global field and can be evaluated in the PAI event.
     A function code is treated in the same way, regardless it comes from pushbutton, menu item or any other GUI element.
When the user clicks on the Display button, you want to display details of sflight, with corresponding carrid and connid (which is entered by the user).
Module pool program to handle this particular screen is as follows:
Program YVTEST7.
TABLES: SFLIGHT.
DATA: OKCODE (4).
MODULE INPUT1 INPUT,
CASE OKCODE.
   WHEN DISP.
     SELECT * FROM SFLIGHT
            WHERE CARRID = SFLIGHT CARRID AND
                           CONNID = SFLIGHT CONNID.
     ENDSELECT.
     LEAVE TO SCREEN 200.
   WHEN EXIT. LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.               INPUT1 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
WHEN BACK. LEAVE TO SCREEN 100.
ENDCASE.
ENDMODULE.                    USER_COMMAND_0200 INPUT
When the user clicks on display, control is transferred to screen no. 200 on which you display sflight details & on the same screen, when user clicks on BACK button, he comes back to main screen.
Flow logic for screen 100 is as follows:
PROCESS AFTER INPUT.
MODULE INPUT.
Flow logic for screen 200
PROCESS AFTER INPUT.
USER_COMMAND_0200.
MODULES: Modules are handled in module pool program.
You need to write flow logic for screen 200 and design screen 200.
In case of transaction transfer of data from program to screen is automatic i.e. you need not transfer the data from program to screen explicitly. The fields, which you define in the screen receives the data from program and displays the same.
The Field Checks
As already mentioned Transaction is the only method, which SAP recommends to update the database tables. Data entered in the database table should be valid and correct. Data entered is validated at each and every point. ABAP/4 offers various methods to validate data and those are as follows:
     Automatic field checks
     Checks performed in the flow logic
     Checks performed in the ABAP/4 module pool program
Automatic Field Checks
These checks are based on the field information stored in the dictionary. These checks are performed by the system automatically when the user enters the data for the screen field. System performs these checks before PAI event is triggered. Types of field checks performed by system are as follows:
     Required input
While designing the screen, for particular screen field if you click the Req. Entry checkbox, the field becomes mandatory. When the transaction is executed if user leaves this particular field blank, the system displays error message. User cannot proceed until the user enters some data.
     Proper Data Format
Each field has its own data format whether it is table field or screen field. Whenever data is entered, system checks for the proper format of the data. For example date. Each user has its own format for date, which is defined in the user master record. If the date defined in the user master record is in the format DD/MM/YYYY, if the user enters the date, say, in YY/DD/MM, the user displays the error message. System also checks for the value of month or days. For example if month entered is greater than twelve then the error message is displayed.
     Valid Value for the Field
In data dictionary two tables are related by Primary key-Foreign key relationship. Whenever the user enters the data, the system checks for the check table values.   Also in Domain, if you have fixed values, then the system checks for these values.
Automatic field checks are repeated each time the user enters the data.
About at Exit Command
Automatic field checks can be avoided by AT EXIT-COMMAND, which works exactly the same way as Cancel works on application tools bar. In the R/3 screen, if you want to quit the processing of that particular screen without entering the mandatory fields, user can click the Cancel button. Same functionality can be incorporated in the user-defined transaction by using AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks and it goes without saying that before PAI event. Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows:
In Flow Logic
Process After Input.
Module exit AT EXIT-COMMAND.
         In module pool program.
Module exit.
Case okcode.
When Exit.
Leave to screen 0.
To achieve this kind of functionality a pushbutton or menu item should be assigned a function type E. It tells the system to process this particular module before carrying out any field checks.
Flow Logic Validations
Consider the case where you want user to enter only LH and SQ for sflight-carrid. In this case, you are restricting value of a screen field. This cannot be achieved by automatic field check. Hence there is a need of additional validation. It can be done in flow logic by using following statement:
Field -
Values
Syntax
PAI.
Field sflight-carrid values (LH).
For multiple values
PAI.
Field sflight-carrid values (LH SQ).
Field sflight-price values (between 1000 and 2000).
In this case when the user enters the value, PAI is triggered and field is checked for that particular value. If the value entered happens to be wrong, that field is enabled for user to enter. If you have multiple Field statements in your flow logic, it is sequential execution.
Consider the following case:
PAI.
Module assign.
Field sflight-carrid values (LH SQ).
In ABAP/4
Module assign.
Data: carrid1 like sflight-carrid.
Carrid1 = sflight-carrid.
Endmodule.
In this case, Sflight-carrid is used in the flow logic before the field statement. The system will give invalid value or some previous value as the field sflight-carrid is used in module before it is checked i.e., field statement is after the module in which sflight-carrid is being used. The field is not available to the system unless it executes the field statement. Field statement transfers the values to the program and is done only once. If you dont have Field statement in your flow logic, transfer of values takes place in PAI event.
Consider one more case where you have multiple field statement
PAI.
Field Sflight-carrid values (LH).
Field Sflight-connid values (0400 0500).
In this case if the user enters only carrid wrong, then this particular field is enabled and rest of the fields are disabled for user to input. Many times if the user enters wrong value for one field, then you might want to give option to user to enter all the fields, which is not possible by using Field statement only. This functionality can be achieved by CHAIN ENDCHAIN.
Syntax
Chain.
Field sflight-carrid value (LH).
     Field sflight-connid values (between 200 and 500).
Endchain.
Field sflight-price values (100 1000).
In this case, if the user enters wrong value only for carrid, both the fields i.e. carrid and connid are enabled as they are grouped together in the Chain statement. The field price will be disabled for input. Usually, logically related fields are grouped together with Chain-Endchain statement.
Module Pool Program Validations
Checking fields ABAP/4 program includes
     Field statement in flow logic.
     Module statement in ABAP/4 module pool Program.
Syntax
PAI.
Field sflight-carrid module <name>.
This module can be handled in the main program i.e. module pool program.
In ABAP/4 program
Module Check.
Select single * from sflight where carrid = sflight-carrid.
If sy-subrc ne 0.
     Message e001.
Endif.
In this case, field sflight-carrid is checked in the table for its existence.
Dynamically Calling the Screens
About Displaying Next Screen
Transaction is a sequence of screens, which are displayed one after the other. The next screen displayed depends upon the attributes of first screen. In attributes you need to give Next Screen number i.e. if next screen displayed should be 200 screen, then this number should be given in next Screen attributes. These are static attributes of the screen. By default, if nothing is specified in the program, the system branches out to the screen number, which is specified in the attribute screen.
In this case, if user selects MARA pushbutton, then fields from Mara table are displayed. When the user clicks on the MARD, then the fields from MARD table are displayed. Depending upon users selection, the screen is branched out and this has to be done during runtime. This functionality can be achieved by dynamically calling the screen in module pool program.
The screen can branch out to new screen depending upon user selection. Following command in module pool program can do this:
     SET SCREEM
     CALL SCREEN
     LEAVE TO SCREEN <NUMBER>
All these commands override the specifications given in the attributes. This overriding is temporary. The values stored in the attribute are not changed.
Set Screen
Syntax
Set screen <number>.
In module pool program
Case okcode.
     When DISP.
          Set screen 200.
     When LIST.
          Set screen 300.
Endcase.
In this case, the entire processing of current screen takes place and then the system branches out to next screen. If you want to branch out to the next screen without processing the current screen, LEAVE SCREEN should be used along with the SET SCREEN.
For Example:
Case okcode..
     When DISP.
          Set screen 200.
          Leave Screen.
     When LIST.
          Set screen 300.
          Leave Screen.
Endcase.
When SET SCREEN is used, control cannot be transferred to the main screen or previous screen, unless you write code for the same.
Call Screen
Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.
Syntax
Call Screen 200.
Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.
To call screen as pop up screen the syntax is
Call screen starting at <col.no.> <line no>
                     Ending at <col no> <line no>.
In this case window will be popped as window and user can close it by using BACK button.
Leave to screen
To SET a new screen without processing current screen, you need to use the following two statements together:
SET SCREEN 200.
LEAVE SCREEN.
Or a Single statement
LEAVE TO SCREEN 200.

Why this 6509 module reset caused system restart?

I had a 6509 switch recycled power to its 6748-GE-TX module. I like to understand why this module reset caused the system to restart, and what this "system restart" means. Please see the syslog messages (I didn't include all messages).
Thanks
Gary
Mar 16 09:52:49.452 EST: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module experiencing Port asic error)
Mar 16 09:52:49.720 EST: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module experiencing Port asic error) 00:00:04: %SYS-CFC9-5-RESTART: System restarted --
Mar 16 09:53:57.497 EST: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online

Hi Gary,
The message is a bit misleading. The "system restarted" message is coming from the CFC daughter card on the module
"%SYS-CFC9-5-RESTART: System restarted -"
So the entire switch did not restart, but just the module and daughter card. Now, I'm saying that based on the provided messages. You should check the system uptime in the "show ver" and/or the reset logs stored in the NVRAM log "show log" as well.
But, as I said, if the only indication of "System restarted" was in the above syslog, then that's only referring to the CFC.
HTH,
Bobby

Error while transporting modification in module pool of a specific infotype

HI experts,
While transporting some modifications that have be done on the PAI of a module pool of a specific infotype, we have an error with code return = 8, the error is --> Original object R3TRPROGMP900730 must not be changed!!!
Any suggestion .
Tanhks a lot .

Hi ,
Nice to know that your problem is solved. If any of the replies were usefull please acknowledge their work.
And it would be great if you can just put in your remarks about the best solution you had in solving that problem.
It might be useful to other users when they encoutner such problem.
BR,
Vijay.

System restart error in Module pool

Similar Messages

Maybe you are looking for