Help needed in Dialog programming

Hi,
I am in a module pool program. This contains a subscreen which has a tablecontrol. Based on one of the entry in the table control. I need to stop the user to change the value.
So I have coded like the below.
If i_tc-value = 0.
v_scrno = sy-dynnr.
leave to screen v_scrno.
endif.
But the above code gives an ABEND error with message
SET SCREEN not allowed in subscreen (screen: <Program name> <Screen nbr>)
Please help to solve the above issue. User must make the entry in the table control. How to stop the user for changing the entry?

Hi Murphy,
I don't know on wot entry you want to stop the user to changes , i hope for stoping your user you may have some condiation once that condation pass make use screen properties to make that field into display mode such that the user again not able to edit.
Thanks,
saleem.

Similar Messages

Hi friends plz help me with dialog programming

hi,
i have developed a screen with flow logic.it has few mandatory fields , radiobuttons,check boxes and pushbuttons such as Create,Save,Display,Back. after entering the values and save i have no problem but when taking back or display it is asking for mandatory field i need not give values for those field to take back.plz provide me with very quick response.
and how do i save data from selected checkboxes or from radiobuttons to ztables and how do i retrieve data back to radiobutton in selected format .
kindly help rewarded for answers.

Hi Sirisha,
Goto menu painter and give given status for ur program-> go to standard tool bar and double click on BACK and select Function type = E.
or
double click on ur PF status and do the same.
once you give function type E, write one module under PAI like below.
PROCESS AFTER INPUT.
MODULE BACK AT EXIT-COMMAND.
code for Module BACK
IF ok_code = 'BACK' OR ok_code = 'EXIT'.
CLEAR: ok_code.
LEAVE TO SCREEN 100." This is the screen where u want to come back
ENDIF.
ENDMODULE.
This module BACK is executed wherever u write under PAI when Function type E is defined for Screen Element.
for more details on this topic. please have a look.
[http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaa9535c111d1829f0000e829fbfe/content.htm|http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaa9535c111d1829f0000e829fbfe/content.htm]
I hope that it helps you ..
Regards,
Venkat.O

2 Layout's for 2 screens different F4 Help needed for same program

Hi Friends,
I have 2 layouts in the selection screen the first layout is for screen 1 and the second layout is for screen 2.
I save the layouts when I run the report.
Now when I do F4 Help for the first layout it shows me all the layouts available for the program and the same thing
for Second layout too.
Is there a way for the first layout I need to get only the layouts for the first screen when I hit the F4 button
and for the second layout I need to get only the layouts for the second screen when I hit the F4 button. in order to choose
I am using REUSE_ALV_VARIANT_F4 and passing report name to is_variant and i_save = 'X'.
Thanks,
chaithanya.

I think this is not possible.
Variant names get stored on Report Name as key.
a®

Help needed in report programming

Hi All
I am processing some data on first screen of a report transaction and an output is displayed on second screen. My requirement is that when I press back, I have to come to SAP initial screen.
I have tried all options with 'LEAVE'. Problem is that control doesnt come even once in report, it goes into some standard code so I am unable to make changes..
Kindly help.
Thanks
Dinesh
<LOCKED BY MODERATOR - USE APPROPRIATE TITLES>
<LOCKED BY MODERATOR - URGENT, PLEASE HELP OR SIMILAR ARE FORBIDDEN>
Edited by: Alvaro Tejada Galindo on Aug 18, 2008 5:17 PM

Hi,
Since it is a report program. U have to set PF status in ur output page (either ALV or any other output format).
In GUI status, triger the function code for BACK.
Then, inside the event AT USER-COMMAND, code LEAVE PROGRAM for the BACK function.
If it is an ALV output, the PF-status and User-command event should be called in the ALV function module.
Regards,
Prem

Help needed regarding Dynamic Programming

Hi,
While doing dynamic programming , we bind the context variable with two types of
values .
1 . ddic
2 . extern
My doubt is in which case we should use ddic and where to use extern .
Can anybody help me out regarding this.
Thanks a lot.

Hi Ki,
Predefined, Web Dynpro UI-specific, and user-defined Dictionary types all have the
prefix ddic:.
wdContext.getNodeInfo()
.addAttribute(
"Visibility",
"ddic:com.sap.ide.webdynpro.uielementdefinitions.Visbility")
Logical Dictionary types from Adaptive RFC models have the prefix extern:.
Check this links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9214b1e5-0601-0010-fdb0-ec32d43b06e0
/people/dipankar.saha3/blog/2007/05/31/how-to-create-dynamic-approval-process-using-conditional-loop-block-in-guided-procedure
Regards,
Mithu

Help needed for compactrio programming

Hello all,
I am very new to LabVIEW programming.I've an application where it's required to acquire temprature data at a perticular duration from a heater.Depending upon the differance between current temp (process varible)and set temprature,heater has to make ON and OFF in a controlled way to reach the set value.
I have made a loop where i am acquireing temp data at every 30 sec interval and depending upon temprature diff between set value and present value ,am genarting a pulse (for eg. 22 sec on period and 8 sec off period).Inside that loop I am driving the "True" value to DIO of CompactRIO for ON period to make the heater ON .Problem what I am facing is the heater is not gaetting ON at Exact 0 to 22 sec and not OFF from 22 sec to 30 sec.
i have tried to use separate loop for acustion ,analysis and control but not able to synchonise all.Heater is getting ON and OFF randomly.Please help.
thanks
tapasm

Can you post your code?
It would make is so much easier to help.
Tim
Johnson Controls
Holland Michigan

Help needed with basic program

I am working on an assignment for my java class, and I am stuck. This is the 1st programming class that i have taken and am a little confused. I am supposed to write a program that inputs 5 numbers and determines and prints the number of negative numbers, positive numbers, and zeros that were inputed. I have gone about this a few different ways so far... but I'm not really sure what to do...
This is what I have so far on my latest attempt, which I think might be completely wrong..... HELP!!!
import java.util.Scanner;
public class test
 public static void main (String[] args)
 Scanner input = new Scanner (System.in);
 int integer
 int negative = 0;
 int positive = 0;
 int zero = 0;
 int studentCounter = 1;
 while (studentCounter <=5)
 System.out.print("Please enter an integer:");
 integer = input.nextInt();
 if (integer == 0
 zero = zero +1
I also tried something similar using :
 int num1; //first number input
 int num2; //second number input
 int num3; //third number input
 int num4; //forth number input
 int num5; //fifth number input
System.out.print ("Enter first integer:"); //prompts for input
 num1 = input.nextInt();
 System.out.print ("Enter second integer:"); //prompts for input
 num2 = input.nextInt();
 System.out.print ("Enter third integer:"); //prompts for input
 num3 = input.nextInt();
 System.out.print ("Enter forth integer:"); //prompts for input
 num4 = input.nextInt();
 System.out.print ("Enter fifth integer:"); //prompts for input
 num5 = input.nextInt();
but i didn't know what to do next.....

import java.util.Scanner;
ublic class test
 public static void main (String[] args)
 Scanner input = new Scanner (System.in);
int integer
int negative = 0;
int positive = 0;
 int zero = 0;
int studentCounter = 1;
while (studentCounter <=5)
 System.out.print("Please enter an integer:");
 integer = input.nextInt();
if (integer == 0
 zero = zero +1
This looks more or less correct so far. Not ideal, but aside from a missing ) and the fact that you trailed off without finishing, it looks like you're on track.
Start with this, and post details about what specific problems you're having.
When you post code, please use[code] and [/code] tags as described in Formatting tips on the message entry page. It makes it much easier to read.

Help needed in this program!

Hi, i have written a program for solving a power flow question,using Gaussian elimination method to solve for matrices.The program is pretty long,and i have tried breaking the program into smaller modules,but there were errors in the numeric results at the end.
I need some suggests as to how to break the program into smaller modules???
/* Example 10.6 Pg 347 from Bergen.
 Demonstration of Newton-Raphson Iteration.
import java.util.*;
import java.io.*;
import java.lang.Math;
import java.lang.ArrayIndexOutOfBoundsException;
public class NewtonRaphsonIt
 public static void main( String args[])throws ArrayIndexOutOfBoundsException
 int Deg = 360;
 int Loop = 3;
 double pi = 3.141592653589793238;
 double limit = Math.abs(5E-6);
 int i,j,k,u;
 double V1,V2,V3,P2,P3,Q3,deltaP2,deltaP3,deltaQ3;
 double Theta1,Theta2,Theta3;
 double P1,Q1,Q2;
 double P_Loss,Q_Loss,PF;
 double maxi,temp,temp2;
 int tempi=0;
 //values given
 P2=0.6661; P3=-2.8653; Q3=-1.2244;
 V1=1; V2=1.05; Theta1=0;
 //values supposely to be chosen as a rough guess
 Theta2=Theta3=0; V3=1;
 double [][] Y_bus = {{-19.98,10,10},{10,-19.98,10},{10,10,-19.98}};
 double [][] J = new double [3][3];
 double [] fx = new double [3];
 double [] oldx = {Theta2,Theta3,V3};
 double [] x = {Theta2,Theta3,V3};
 double [] V = {V1,V2,Theta1};
 double [] Bus = {P2,P3,Q3};
 double [] delta = new double [3];
 double [] ANS = new double [3];
 int f = fx.length;
 int y = Y_bus.length;
 int z = J.length;
 int c = Bus.length;
 int h = delta.length;
 int e = ANS.length;
 int ox= oldx.length;
 //System.out.println("Arrary size for Ybus is:" +n);
 //output Ybus Matrix
 System.out.println(" Ybus is:");
 System.out.println("---------");
 for ( i=0; i<y; i++)
 for ( j=0; j<y; j++)
 System.out.print(+Y_bus[i][j]+" "+", ");
 System.out.println();
 for ( u=1; u<Loop+1; u++){
 //while(delta[0] < limit){
 //Jacobian matrix
 //deltaP2/deltaTheta2
 J[0][0] = (Math.abs(V[1]))* (Math.abs(V[0])) * Y_bus[1][0] * (Math.cos(x[0]))
 + (Math.abs(V[1]))* (Math.abs(x[2])) * Y_bus[1][2] * (Math.cos(x[0]-x[1]));
 //deltaP2/deltaTheta3
 J[0][1] = -(Math.abs(V[1]))* (Math.abs(x[2])) * Y_bus[1][2] * (Math.cos(x[0]-x[1]));
 //deltaP2/delta|V3|
 J[0][2] = (Math.abs(V[1])) * Y_bus[1][2] * (Math.sin(x[0]-x[1]));
 //deltaP3/deltaTheta2
 J[1][0] = -(Math.abs(V[1]))*(Math.abs(x[2])) * Y_bus[2][0] * (Math.cos(x[1]-x[0]));
 //deltaP3/deltaTheta3
 J[1][1] = (Math.abs(V[0])) *(Math.abs(x[2])) * Y_bus[2][0] * (Math.cos(x[1]))
 +(Math.abs(V[1])) *(Math.abs(x[2])) * Y_bus[2][1] * (Math.cos(x[1]-x[0]));
 //deltaP3/delta|V3|
 J[1][2] = (Math.abs(V[0])) * Y_bus[2][0] * (Math.sin(x[1]))
 +(Math.abs(V[1]))* Y_bus[2][1] * (Math.sin(x[1]-x[0]));
 //deltaQ3/deltaTheta2
 J[2][0] = - Y_bus[2][0] * (Math.abs(x[2])) * (Math.abs(V[1])) *(Math.sin(x[1]-x[0]));
 //deltaQ3/deltaTheta3
 J[2][1] = (Math.abs(x[2]))*(Math.abs(V[0])) * Y_bus[2][0] * (Math.sin(x[1]))
 +(Math.abs(x[2]))*(Math.abs(V[1])) * Y_bus[2][1] * (Math.sin(x[1]-x[0]));
 //deltaQ3/delta|V3|
 J[2][2] = -((Math.abs(V[0])) * Y_bus[2][0] * (Math.cos(x[1]))
 + (Math.abs(V[1])) * Y_bus[2][1] * (Math.cos(x[1]-x[0]))
 + (Math.abs(x[2]))* 2 * Y_bus[2][2]);
 //output Jacobian Matrix
 System.out.println();
 System.out.println(+u+")"+" Jacobian Matrix is:");
 System.out.println("-----------------------");
 for ( i=0; i<z; i++)
 for ( j=0; j<z; j++)
 System.out.print(+J[i][j]+" "+", ");
 System.out.println();
 // variable P2
 fx[0] = (Math.abs(V[1]))*(Math.abs(V[0])) * Y_bus[1][0] * (Math.sin(x[0]-V[2]))
 + (Math.abs(V[1]))*(Math.abs(x[2])) * Y_bus[1][2] * (Math.sin(x[0]-x[1]));
 //System.out.println("P2 is :"+fx[0]);
 // variable P3
 fx[1] = (Math.abs(x[2]))*(Math.abs(V[0])) * Y_bus[2][0] * (Math.sin(x[1]-V[2]))
 + (Math.abs(x[2]))*(Math.abs(V[1])) * Y_bus[2][1] * (Math.sin(x[1]-x[0]));
 //System.out.println("P3 is :"+fx[1]);
 // variable Q3
 fx[2] = -((Math.abs(x[2]))*(Math.abs(V[0])) * Y_bus[2][0] * (Math.cos(x[1]-V[2]))
 + (Math.abs(x[2]))*(Math.abs(V[1])) * Y_bus[2][1] * (Math.cos(x[1]-x[0]))
 + (Math.abs(x[2]))*(Math.abs(x[2])) * Y_bus[2][2]);
 //System.out.println("Q3 is :"+fx[2]);
 //Output f(x)
 System.out.println();
 System.out.println(+u+")"+" Function f(x) is:");
 System.out.println("--------------------");
 for ( k=0; k<f; k++)
 System.out.println(+fx[k]);
 System.out.println();
 //ouput P2,P3,Q3 as a matrix
 System.out.println();
 System.out.println(+u+")"+" Matrix [P2,P3,Q3] is:");
 System.out.println("------------------------");
 for ( k=0; k<c; k++)
 System.out.println(+Bus[k]);
 System.out.println();
 //finding values of deltaP2,deltaP3,deltaQ3
 System.out.println();
 System.out.println(+u+")"+" Matrix [d.P2,d.P3,d.Q3] is:");
 System.out.println("------------------------------");
 for ( k=0; k<h; k++)
 System.out.println(delta[k]= Bus[k]- fx[k]);
 System.out.println();
 //find delta x={deltaTheta2,deltaTheta3,delta|V3|}
 //Gaussian Elimination method
 //solve Ax=b
 //matrix J will be destroyed,solution will be in matrix delta
 if(J[0].length != z)
 System.out.println("Matrix J must be a Square Matrix!");
 return;
 for(j=0; j<z; j++)
 maxi=-1E-12;
 for(i=j; i<z; i++)
 if(Math.abs(J[i][j])> maxi)
 tempi=i;
 maxi=Math.abs(J[i][j]);
 //System.out.println(+tempi);
 if(maxi<1E-12)
 System.out.println
 ("The Set either has mutltiple solutions or no unique solution!");
 return;
 //Permuting tempi row with the j-th row
 if(tempi != j)
 for(k=j; k<z; k++)
 temp=J[j][k]; //store 1st row into temp space
 J[j][k]=J[tempi][k]; //store last row into 1st row
 J[tempi][k]=temp; //store 1st row back into last row
 temp=delta[j]; //store 1st row into temp space
 delta[j]=delta[tempi]; //store last row into 1st row
 delta[tempi]=temp; //store 1st row back into last row
 //System.out.println("deltatemp:"+delta[j]);
 //Divide j-th row by J[j][j]
 temp=J[j][j];
 delta[j]=delta[j]/temp;
 System.out.println("delta1:"+delta[j]);
 for(k=j; k<z; k++)
 J[j][k]=J[j][k]/temp;
 for(i=0; i<z; i++)
 if(i != j)
 temp=J[i][j];
 temp2=delta;
 for(k=0; k<z; k++)
 J[i][k] = J[i][k]-temp*J[j][k];
 delta[i]= temp2-temp*delta[j];
 System.out.println("delta:"+delta[j]);
 System.out.println("J:"+J[i][k]);
 // values of deltax in radians
 System.out.println(+u+")"+" The solution for AX=b is:");
 System.out.println("----------------------------");
 for(i=0; i<z; i++)
 System.out.println(+delta[i]);
 x[i] = delta[i];
 // values of deltax in degrees
 System.out.println();
 System.out.println(+u+")"+" The solution for deltaX is:");
 System.out.println("------------------------------");
 ANS[0] = x[0] * Deg/(2*pi);
 ANS[1] = x[1] * Deg/(2*pi);
 ANS[2] = x[2];
 for(i=0; i<e; i++)
 System.out.println(+ANS[i]);
 //finding X^1=x^0 + deltax^0
 System.out.println();
 System.out.println(" The solution for X after iteration:"+"("+u+")");
 System.out.println("---------------------------------------");
 for(i=0; i<e; i++)
 x[i] = oldx[i] + ANS[i];
 System.out.println(+x[i]);
 System.out.println();
 //System.out.println("oldx:" +oldx[i]);
 //System.out.println();
 //update the oldx with the new values from x
 for(i=0; i<ox; i++)
 oldx[i] = x[i];
 //System.out.println("oldx:" +oldx[i]);
 //System.out.println();
 //convert to radians for Math.sin/cos()
 x[0] = x[0] * (2*pi)/Deg;
 x[1] = x[1] * (2*pi)/Deg;
 x[2] = x[2];
 }//for loop
 //if (delta[0] == limit)
 // break;
 //}//while loop
 // calcuate P1,Q1,Q2
 P1 = (Math.abs(V[0]))*(Math.abs(V[1])) * Y_bus[0][1]* (Math.sin(V[2]-x[0]))
 + (Math.abs(V[0]))*(Math.abs(x[2])) * Y_bus[0][2] * (Math.sin(V[2]-x[1]));
 System.out.println("P1 is :"+P1);
 System.out.println();
 Q1 = -((Math.abs(V[0]))*(Math.abs(V[1])) * Y_bus[0][1] * (Math.cos(V[2]-x[0]))
 + (Math.abs(V[0]))*(Math.abs(x[2])) * Y_bus[0][2] * (Math.cos(V[2]-x[1]))
 + (Math.abs(V[0]))*(Math.abs(V[0])) * Y_bus[0][0]);
 System.out.println("Q1 is :"+Q1);
 System.out.println();
 Q2 = -((Math.abs(V[1]))*(Math.abs(V[0])) * Y_bus[1][0] * (Math.cos(x[0]-V[2]))
 + (Math.abs(V[1]))*(Math.abs(x[2])) * Y_bus[1][2] * (Math.cos(x[0]-x[1]))
 + (Math.abs(V[1]))*(Math.abs(V[1])) * Y_bus[1][1]);
 System.out.println("Q2 is :"+Q2);
 System.out.println();
 //Power Loss P_Loss = (P1+P2) - P3
 P_Loss = (P1+P2) - P3;
 System.out.println("Power Loss is :"+P_Loss);
 System.out.println();
 System.out.println("P2 is :"+P2);
 System.out.println();
 System.out.println("P3 is :"+P3);
 System.out.println();
 System.out.println("Q3 is :"+Q3);
 System.out.println();
 //Reactive Power Loss
 Q_Loss = (Q1+Q2) - Q3;
 System.out.println("Reactive Power Loss:" +Q_Loss);
 System.out.println();
 System.out.println("Q1 is :"+Q1);
 System.out.println();
 System.out.println("Q2 is :"+Q2);
 System.out.println();
 System.out.println("Q3 is :"+Q3);
 System.out.println();
 //Power factor PF = P/sqrt[(P^2 + Q^2)]
 PF = P3/(Math.sqrt( (P3*P3) + (Q3*Q3)));
 System.out.println("Power Factor is :"+PF);
 System.out.println();

Start off by creating a Matrix class, rather than doing it all with 2d arrays in the main method? (The Matrix class might do little more than be a wrapper around a 2d array, but at least it would be a bit more modular.)

Help needed in jco programming

hi friends
when i try to connect with SAP server using jco i have some probem.
Connection with jco program is working fine. I make it ajava file and run separately).
Now i want do that with jsp.
I am getting error of
Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:848)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781)
org.apache.jsp.barcodeMainP_jsp._jspService(org.apache.jsp.barcodeMainP_jsp:124)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.lang.NoClassDefFoundError
mySAP.JcoTest.createConnection(JcoTest.java:78)
mySAP.JcoTest.<init>(JcoTest.java:8)
org.apache.jsp.barcodeMainP_jsp._jspService(org.apache.jsp.barcodeMainP_jsp:74)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs.
My Program is
My java program
package mySAP;
import com.sap.mw.jco.*;
public class JcoTest {
 public JcoTest() {
 createConnection();
 retrieveRepository();
 closeConnection();
 public StringBuffer fetchData(String Dofrom, String Doto) {
 StringBuffer stringbuffer = new StringBuffer();
 try {
 com.sap.mw.jco.JCO.Function function = getFunction("Z_BC_LABEL");
 System.out.println("SUCC YOU GOT CONN");
 com.sap.mw.jco.JCO.ParameterList listParams = function
 .getImportParameterList();
 System.out.println(listParams);
 listParams.setValue(Dofrom, "DO_FROM");
 listParams.setValue(Doto, "DO_TO");
 theConnection.execute(function);
 System.out.println("SUCC function executed success");
 com.sap.mw.jco.JCO.Table tableList = function
 .getTableParameterList().getTable("ZBAR");
 String s3 = "\t";
 stringbuffer.append("vbeln" + s3);
 stringbuffer.append("uecha" + s3);
 stringbuffer.append("kdmat" + s3);
 stringbuffer.append("lifmg" + s3);
 stringbuffer.append("bstkd" + s3);
 stringbuffer.append("groes" + s3);
 stringbuffer.append("name1" + s3);
 stringbuffer.append("lfdat" + s3);
 stringbuffer.append("posnr" + s3);
 stringbuffer.append("lifmg bstkd " + "\n");
 // stringbuffer.append("\t");
 if (tableList.getNumRows() > 0)
 do {
 com.sap.mw.jco.JCO.Field tabField;
 for (com.sap.mw.jco.JCO.FieldIterator fI = tableList
 .fields(); fI.hasMoreElements();
 stringbuffer.append(tabField.getString() + s3)) {
 tabField = fI.nextField();
 stringbuffer.append("\n");
 } while (tableList.nextRow());
 else
 System.out.println("sorry no records...better luck next time");
 } catch (Exception ex) {
 ex.printStackTrace();
 return stringbuffer;
 private static void createConnection() {
 try {
 theConnection = JCO.createClient("080", "xxxx", "xxxx", "EN",
 "xxx.xxx.xx.xx", "00");
 theConnection.connect();
 } catch (Exception ex) {
 System.out.println("Failed to connect to SAP system");
 private static void closeConnection() {
 try {
 theConnection.disconnect();
 } catch (Exception ex) {
 System.out.println("Failed to connect to SAP system");
 private static void retrieveRepository() {
 try {
 theRepository = new com.sap.mw.jco.JCO.Repository("saprep",
 theConnection);
 } catch (Exception ex) {
 System.out.println("failed to retrieve repository");
 public static com.sap.mw.jco.JCO.Function getFunction(String name) {
 return theRepository.getFunctionTemplate(name.toUpperCase())
 .getFunction();
 private static com.sap.mw.jco.JCO.Client theConnection;
 private static IRepository theRepository;
My JSP calling Program
<%@page language="java"
 import="java.sql.*,java.io.*,mySAP.*,java.net.URL;"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Insert title here</title>
</head>
<body>
<%!StringBuffer stringbuffer = new StringBuffer();
 int testemp;%>
<%
 String dofrom;
 String doto;
 String s;
 String s1;
 dofrom = request.getParameter("DOFrom");
 doto = request.getParameter("DOTo");
 ResultSet resultset;
 String flag = request.getParameter("dall");
 mySAP.JcoTest obj = new mySAP.JcoTest();
 StringBuffer sb = obj.fetchData("one", "two");
 out.println(sb);
 try {
 StringBuffer stringbuffer = new StringBuffer();
 String separator = System.getProperty("file.separator");
 String path = System.getProperty("user.dir") + separator;
 } catch (Exception e) {
 out.println("error%%%%%%%%%" + e);
%>
</body>
</html>

NoClassDefFoundError always means Class Path problem. The classpath of the Servlet is not the same as a normal Java Application. Move any of the necessary dependencies to the Servlet Context's class path (jars in the WEB-INF/lib/ or classes in WEB-INF/classes/).

Help needed in c programming

hi
i am writing a c program using fstream.
can anyone tell me where can i post my questions here in apple discussion board?
i just don't know in which section does my problem fits.

The main developer forum is here:
http://discussions.apple.com/forum.jspa?forumID=727

Help needed with this program

Hello,
I would like to enquire on whether this VI has any error. I need to configure the digital input as a positive limit switch which is a sensor which when blocked, will produce a change in the voltage pulse.
Attachments:
sensor.vi ‏34 KB

Hello,
I could not open. Can you save it for LabView 8.2 or 8.5?
Andy
Best Regards,
Andy
PCI-7356@UMI7764; PCIe-6320@SCB-68; LV2011; Motion Assistant 2.7; NI Motion 8.3; DAQmx 9.4; Win7

HELP NEEDED with videora program

ok...so i am a bit confused. When im converting my movie it says it is 100% complete, yet there is no message or anything...is there supposed to be?...and what do i do after it is comlete?

No, there's no message.
The next step is to find the file that it created for you, and add it to iTunes so that it can be transferred to your Pod.
If you're not sure where it saved the file to, look in the Videora settings and see what is set as the output directory.

Basic Dialog Programming

Hello Everybody and hello World.
I would like to know how to do a basic dialog programming..
Can anyone help me?Please....
give me some advice....Im very eager to learn that dialog programming
Thanks in advance
aVaDuDz

hi
INTRODUCTION TO DIALOG PROGRAMMING
OVERVIEW
There are programs in every domain that require certain amount of user interaction .Such requirements in ABAP are fulfilled with the help of a user dialog and dialog programming which encapsulates the entire logic pertaining to the required user dialog.
One needs to take care that user interactions with the system are comfortable and user friendly along with being logically coherent.

What is a user dialog?
Any kind of user interaction with the system can be called as a user dialog:
1) Entering data on the screen.
2) Clicking a button.
3) Navigation between screens.
Need of dialog programming
In a typical dialog, the system displays a screen on which the user can enter or request information. As a reaction on the user input or request, the program executes the appropriate actions: it branches to the next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the screen. The system either confirms the desired request, that is, the agent can book the flight and the customer travels on the desired day on the reserved seat to the chosen destination, or the system displays the information that the flight is already booked up.
To fulfill such requirements, a dialog program must offer:
A user-friendly user interface
Format and consistency checks for the data entered by the user
Easy correction of input errors
Access to data by storing it in the database.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated above in the dialog programs.
Why dialog programming is also known as module pool?
Dialog Programming consists of screens and corresponding ABAP program. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for these dialog modules, and hence dialog programming is also known as module pools. A module pool program is a program type which is not executable directly. You can not just run by hitting F8 like a report program. You must tie a transaction code to a screen in order to start the program.
VARIOUS COMPONENTS OF A DIALOG PROGRAM
Unlike report, interface or any conversion development which generally entails the creation of one autonomous program which can be executed independently of other objects, dialog program development entails development of multiple objects none of which can be executed on its own. Instead all objects are linked hierarchically to the main program and are executed in a sequence dictated by the Dialog Main Program.
Components of a dialog program
1) Transaction
2) Screen
3) GUI status
4) ABAP program
All these components are explained in detail below.
1) TRANSACTION :
The transaction 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.
2) SCREEN
As a user of an R/3 system, one is always confronted with screens. From the moment one logs on, one can see a screen and one must perform actions on this screen. All those screens are components of ABAP programs. Generally, we define the screens of an ABAP program with the Screen Painter tool of the ABAP.
In the R/3 system, screens are program objects that consist of two parts. First, they have a layout that defines the front end appearance of the window that is presented to the user. Second, they have a flow logic that is executed on the backend by the application server. The screen flow logic is a program layer between the front end and the actual ABAP application program at the backend. The language used to program screen flow logic has a similar syntax to ABAP, but is not part of ABAP itself. Unlike ABAP programs, the screen flow logic contains no explicit data declarations. You define the screen fields by placing elements on the screen mask instead. When you define screen fields by referring to data types in the ABAP Dictionary, the runtime environment automatically creates dialogs for field help, input help, and error handling that depends on the semantics of the data type in the dictionary.
The screen flow logic is similar to an ABAP program in that it contains processing blocks. These processing blocks are event blocks that are triggered by the ABAP runtime environment. The most important event blocks are:
PROCESS BEFORE OUTPUT
The respective event (PBO) is triggered after the PROCESS AFTER INPUT (PAI) processing of the previous screen and before the current screen is displayed.
PROCESS AFTER INPUT
The respective event (PAI) is triggered when the user chooses a function on the current screen.
PROCESS ON HELP REQUEST
This event is triggered when function key F1 is pressed.
PROCESS ON VALUE REQUEST
This event is triggered when function key F4 is pressed.
The main task of these processing blocks is to call ABAP dialog modules using the MODULE statement. During the PBO event, you can call any dialog module in the ABAP program that is marked with the addition OUTPUT. In the PAI event, you can call any dialog module program that is marked with the addition INPUT. The screens of an ABAP program can share the dialog modules of that program. You use the dialog modules called during PBO to prepare the screen and the dialog modules called during PAI to react to the user input.
Each screen of an ABAP program has a unique screen number. The screens of an ABAP program can be combined to form screen sequences. Screen sequences are either built statically by setting the following screen in the Screen Painter or dynamically by overriding the static setting in the ABAP program. The last screen of a screen sequence is always the one where the following screen is set to zero.
HANDLING USER INTERACTIONS
A user can interact in various ways with screens. We distinguish between actions that trigger PAI and those that dont. In general, filling input fields with values does not trigger PAI.
Actions that do trigger PAI include:
Choosing a pushbutton on the screen.
Choosing a specially prepared check box or radio button on the screen.
Choosing a function in the menu, standard toolbar, or application toolbar.
Choosing a function key on the keyboard.
ATTRIBUTES OF SCREEN
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
 Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
 Screen number
A four-digit number, unique within the ABAP program that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
 Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
 Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
 Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program by using SET CURSOR FIELD <f>
 Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
 Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System -> User profile -> Hold data.
VARIOUS SCREEN ELEMENTS
A screen can contain a wide variety of elements, either for displaying field contents, or for allowing the user to interact with the program (for example, filling out input fields or choosing pushbutton functions). We use the Screen Painter to arrange elements on the screen.
We can use the following elements:
 Text fields
Display elements, which cannot be changed either by the user or by the ABAP program.
 Input/output fields and templates
Used to display data from the ABAP program or for entering data on the screen. Linked to screen fields.
 Dropdown list boxes
Special input/output fields that allow users to choose one entry from a fixed list of possible entries.
 Checkbox elements
Special input/output fields that the user can either select (value X) or deselect (value SPACE). Checkbox elements can be linked with function codes.
 Radio button elements
Special input/output fields that are combined into groups. Within a radio button group, only a single button can be selected at any one time. When the user selects one button, all of the others are automatically deselected. Radio button elements can be linked with function codes.
 Pushbuttons
Elements on the screen that trigger the PAI event of the screen flow logic when chosen by the user. There is a function code attached to each pushbutton, which is passed to the ABAP program when it is chosen.
 Frame
Pure display elements that group together elements on the screen, such as radio button groups.
 Subscreens
Area on the screen in which you can place another screen.
 Table controls
Tabular input/output fields.
 Tab strip controls
Areas on the screen in which you can switch between various pages.
 Custom Controls
Areas on the screen in which you can display controls. Controls are software components of the presentation server.
 Status icons
Display elements, indicating the status of the application program.
 OK field
Every screen has a twenty-character OK_CODE field (also known as the function code field) that is not displayed directly on the screen. User actions that trigger the PAI event also place the corresponding function code into this field, from where it is passed to the ABAP program. You can also use the command field in the standard toolbar to enter the OK field. To be able to use the OK field, you need to assign a name to it.
All screen elements have a set of attributes, some of which are set automatically, others of which have to be specified in the Screen Painter. They determine things such as the layout of the screen elements on the screen. You can set the attributes of screen elements in the Screen Painter - either for a single element, or using the element list, which lists all of the elements belonging to the current screen. Some of the attributes that you set statically in the Screen Painter can be overwritten dynamically in the ABAP program.
 3) 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.
4) PROGRAM
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. 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.
DATA TRANSFER BETWEEN SCREEN AND ABAP PROGRAM
During PAI, the system automatically transports all screen fields to identically named global ABAP program fields. At the end of the last PBO module, and before the screen is displayed, all of the data is transported from the ABAP program to any identically named fields in the screen. By standard, all screen data is transported immediately before PAI processing starts. But for the dedicated handling of screen fields for example, to carry out an error dialog you can control the moment at which data is passed from screen fields to their corresponding ABAP fields by using the FIELD statement in the screen flow logic.
regards
navjot
reward points if helpfull

Imp: Module pool Or Dialog programming

Hi ,
I have got a requirement to work on module pool programming.....Please help me with some documents which explains me about it from scratch clearly .
Awaiting for ur reply...........

basics of module pool
OVERVIEW
There are programs in every domain that require certain amount of user interaction .Such requirements in ABAP are fulfilled with the help of a user dialog and dialog programming which encapsulates the entire logic pertaining to the required user dialog.
One needs to take care that user interactions with the system are comfortable and user friendly along with being logically coherent.
What is a user dialog?
Any kind of user interaction with the system can be called as a user dialog:
1) Entering data on the screen.
2) Clicking a button.
3) Navigation between screens.
Need of dialog programming
In a typical dialog, the system displays a screen on which the user can enter or request information. As a reaction on the user input or request, the program executes the appropriate actions: it branches to the next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the screen. The system either confirms the desired request, that is, the agent can book the flight and the customer travels on the desired day on the reserved seat to the chosen destination, or the system displays the information that the flight is already booked up.
To fulfill such requirements, a dialog program must offer:
A user-friendly user interface
Format and consistency checks for the data entered by the user
Easy correction of input errors
Access to data by storing it in the database.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated above in the dialog programs.

Why dialog programming is also known as module pool?
Dialog Programming consists of screens and corresponding ABAP program. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for these dialog modules, and hence dialog programming is also known as module pools. A module pool program is a program type which is not executable directly. You can not just run by hitting F8 like a report program. You must tie a transaction code to a screen in order to start the program.
VARIOUS COMPONENTS OF A DIALOG PROGRAM
Unlike report, interface or any conversion development which generally entails the creation of one autonomous program which can be executed independently of other objects, dialog program development entails development of multiple objects none of which can be executed on its own. Instead all objects are linked hierarchically to the main program and are executed in a sequence dictated by the Dialog Main Program.

Components of a dialog program
1) Transaction
2) Screen
3) GUI status
4) ABAP program
All these components are explained in detail below.
1) TRANSACTION :
The transaction 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.
2) SCREEN
As a user of an R/3 system, one is always confronted with screens. From the moment one logs on, one can see a screen and one must perform actions on this screen. All those screens are components of ABAP programs. Generally, we define the screens of an ABAP program with the Screen Painter tool of the ABAP.
In the R/3 system, screens are program objects that consist of two parts. First, they have a layout that defines the front end appearance of the window that is presented to the user. Second, they have a flow logic that is executed on the backend by the application server. The screen flow logic is a program layer between the front end and the actual ABAP application program at the backend. The language used to program screen flow logic has a similar syntax to ABAP, but is not part of ABAP itself. Unlike ABAP programs, the screen flow logic contains no explicit data declarations. You define the screen fields by placing elements on the screen mask instead. When you define screen fields by referring to data types in the ABAP Dictionary, the runtime environment automatically creates dialogs for field help, input help, and error handling that depends on the semantics of the data type in the dictionary.
The screen flow logic is similar to an ABAP program in that it contains processing blocks. These processing blocks are event blocks that are triggered by the ABAP runtime environment. The most important event blocks are:
PROCESS BEFORE OUTPUT
The respective event (PBO) is triggered after the PROCESS AFTER INPUT (PAI) processing of the previous screen and before the current screen is displayed.
PROCESS AFTER INPUT
The respective event (PAI) is triggered when the user chooses a function on the current screen.
PROCESS ON HELP REQUEST
This event is triggered when function key F1 is pressed.
PROCESS ON VALUE REQUEST
This event is triggered when function key F4 is pressed.
The main task of these processing blocks is to call ABAP dialog modules using the MODULE statement. During the PBO event, you can call any dialog module in the ABAP program that is marked with the addition OUTPUT. In the PAI event, you can call any dialog module program that is marked with the addition INPUT. The screens of an ABAP program can share the dialog modules of that program. You use the dialog modules called during PBO to prepare the screen and the dialog modules called during PAI to react to the user input.
Each screen of an ABAP program has a unique screen number. The screens of an ABAP program can be combined to form screen sequences. Screen sequences are either built statically by setting the following screen in the Screen Painter or dynamically by overriding the static setting in the ABAP program. The last screen of a screen sequence is always the one where the following screen is set to zero.
ATTRIBUTES OF SCREEN
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
 Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
 Screen number
A four-digit number, unique within the ABAP program that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
 Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
 Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
 Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program by using SET CURSOR FIELD <f>
 Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
 Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System -> User profile -> Hold data.
VARIOUS SCREEN ELEMENTS
A screen can contain a wide variety of elements, either for displaying field contents, or for allowing the user to interact with the program (for example, filling out input fields or choosing pushbutton functions). We use the Screen Painter to arrange elements on the screen.
We can use the following elements:
 Text fields
Display elements, which cannot be changed either by the user or by the ABAP program.
 Input/output fields and templates
Used to display data from the ABAP program or for entering data on the screen. Linked to screen fields.
 Dropdown list boxes
Special input/output fields that allow users to choose one entry from a fixed list of possible entries.
 Checkbox elements
Special input/output fields that the user can either select (value X) or deselect (value SPACE). Checkbox elements can be linked with function codes.
 Radio button elements
Special input/output fields that are combined into groups. Within a radio button group, only a single button can be selected at any one time. When the user selects one button, all of the others are automatically deselected. Radio button elements can be linked with function codes.
 Pushbuttons
Elements on the screen that trigger the PAI event of the screen flow logic when chosen by the user. There is a function code attached to each pushbutton, which is passed to the ABAP program when it is chosen.
 Frame
Pure display elements that group together elements on the screen, such as radio button groups.
 Subscreens
Area on the screen in which you can place another screen.
 Table controls
Tabular input/output fields.
 Tab strip controls
Areas on the screen in which you can switch between various pages.
 Custom Controls
Areas on the screen in which you can display controls. Controls are software components of the presentation server.
 Status icons
Display elements, indicating the status of the application program.
 OK field
Every screen has a twenty-character OK_CODE field (also known as the function code field) that is not displayed directly on the screen. User actions that trigger the PAI event also place the corresponding function code into this field, from where it is passed to the ABAP program. You can also use the command field in the standard toolbar to enter the OK field. To be able to use the OK field, you need to assign a name to it.
All screen elements have a set of attributes, some of which are set automatically, others of which have to be specified in the Screen Painter. They determine things such as the layout of the screen elements on the screen. You can set the attributes of screen elements in the Screen Painter - either for a single element, or using the element list, which lists all of the elements belonging to the current screen. Some of the attributes that you set statically in the Screen Painter can be overwritten dynamically in the ABAP program.
Regards
navjot
reward points if helpfull

Need help in dialog programming

Hello gurus,
I have started my career in ABAP and many questions are bothering me.Would need support from all of u there...
I am studying Dialog programming but not able to get the exact flow of how it actually works.I am following a book titled Advanced ABAP by Gareth B ruyn and Lyfareff.
Still it is not getin clear...can someone help me with that...Step by step procedure to do dialog programming...I am learning on version 4.7...
Also, If we have a field name how can we find out in which tables that same field is present..i.e.how can we search for the different tables for the same field...
Thanks in Advance..
Cheers:Jim

Hi Jimmy,
DIALOG Programming
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
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/
Other useful links:
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
Also
From Menu Environment->Examples->ABAP examples
or Using the Tcode ABAPDOCU you can learn Module pool programs.
Reward if useful.
Thanks
Aneesh.

Help needed in Dialog programming

Similar Messages

Maybe you are looking for