Escolar Documentos
Profissional Documentos
Cultura Documentos
<HTML>
<HEAD>
<TITLE> Welcome to Web Programming </title>
</HEAD>
<BODY>
WEB APPLICATION PROGRAMMING
<INPUT TYPE="TEXT" NAME="A" SIZE="10">
</BODY>
</HTML>
import com.sap.mw.jco.*;
public class Example1 {
public static void main(String[] argv)
{
JCO.Client client = null;
try {
System.out.println("\n\nVersion of the JCO-library:\n" +
"---------------------------\n" + JCO.getMiddlewareVersion());
// All done
System.out.println("\n\nCongratulations! It worked.");
}
catch (Exception ex) {
System.out.println("Caught an exception: \n" + ex);
}
finally {
// do not forget to close the client connection
if (client != null) client.disconnect();
}
}
}
JCO.Client : Is the class used to establish the connection between Java systems with
SAP systems.
Note : java / vb / non sap systems can't use any query to communicate with SAP systems.
Only FunctionModules of SAP can be accessed by Non SAP Systems.
JCO.MetaData : Is the class used in JSP to Set Required Data type for the Function
Module to be sent as arguments.
* Configuring SAP JCO with Weblogic Server. To do this copy "sapjco.jar" into
following paths.
1) C:\bea\weblogic81\samples\server\examples\build\clientclasses\sapjco.jar
2) C:\bea\weblogic81\samples\server\examples\build\examplesWebApp\WEB-
INF\lib\sapjco.jar
JCO.Client : Is one of the class used in JSP to connect with SAP Systems.
This class is defined under a package called as "com.sap.mw.jco.*". By default JSP
applications can't use above package classes, So Internally JSP Says Syntax Errors. To
avoid the Syntax errors import the classes into JSP using Following Syntax.
%>
Web Reporting:
Data existing In SAP to be accessed by Web Applications for Reporting.
VBAK
VBELN
ERDAT
ERNAM
KUNNR
VBAP
VBELN
MATNR
WERKS ( Plant )
LGORT ( Storage Location)
Becaule of "ERM" ( Entity Relational Model) SAP is very Faster While Inserting or
Updating. But as the data is stored in Many table in EMP, causes delay while gerating
reports.
To avoid This delay of time for reporting We migrate the data from SAP R/3 into BW
system. AS bw Maintains the data in MDM ( Multi Dimensional Model) Reporting is
very very Faster.
Lock Objects
Naming convension is should start with "EZ/EY".
Exclusive lock
The locked data can be read or processed by one user only. A request for another
exclusive lock or for a shared lock is rejected.
Shared lock
Several users can read the same data at the same time, but as soon as a user edits the data,
a second user can no longer access this data. Requests for further shared locks are
accepted, even if they are issued by different users, but exclusive locks are rejected.
Exclusive but not cumulative lock
Exclusive locks can be requested by the same transaction more than once and handled
successively, but an exclusive but not cumulative lock can only be requested once by a
given transaction. All other lock requests are rejected.
Navigations:
SE11 -> SELECT Object type as "Lock Objects" -> Name the Lock Object ( EZlock91 )
-> Click on Create -> Opens an interface -> Enter Short Text ( any ) -> Click on tables
tabbutton -> Name the table to be locked ( KNA1) -> Set the lock mode ( Exclusive/
Shared/Execlusive But not Cumulative) -> If required to add Secondary tables to be
locked which are related to Primary table , click on Add pushbutton from Secondary table
list -> opens the List of tables -> select any required table from the list -> click on
Continue -> Click on Lock parameters , by default all key fields of the tables are locked
by sap, if MANDT field is locked , only one client can use the table other client can't. If
Mandt field is deselected then Many client can access the table but under one client
locking concepts are applied -> Save the Object Under a package -> Activate.
Locking is by default applied only for specified transaction. As soon as transactions are
completed then Locks are released.
Application Administration , User Administration and Client Administration etc are under
BASIS module of SAP Administration.
CA : WORKFLOW
"SWDB" is the code for Creating Workflows ( Workflow Builder ). This tool depends on
TASKs in SAP.
PFTC_INS -> Select Object type as "standard task" -> Click on Create From Application
toolbar -> Opens another Interface -> Enter Abbrivation for task -> Name the task ( task
for Inquiry ) -> Specify work Item text ( SAPMV45A ) { name of the application to be
added to the task } -> Click on Description -> Click on Change Text Pushbutton -> Enter
description for task in SAP Script Editor -> come back -> Save the task ( If Prefix
number is missing for the client, data can't be saved. To rectify this problem HR Module
of SAP should be Configured ) -> come back.
Project
1. Extracting ( Data Modeling ).
data maintained in Flat Files in three Formats
Where Pattern table first Field need to have a relation with Entry table of the First Field.
( Foreign key should be generated for first field in pattern table with primary key field
of Entry table ).
SQ : Data is maintained in With Field Name as "SQ" and Continuation data with
BLANK field id.
2. Reporting.