Abap/4 Driver

Hi,
What are ABAP/4 Drivers and why are they used?
Regards,
Nimisha

Hi,
Hope this link is helpful
http://help.sap.com/saphelp_nw04/helpdata/en/89/45aad99715462abdf09ec503e151e7/frameset.htm
Regards
Shankar

Similar Messages

RFC Destination using ABAP / 4 driver

hi all
i want to create RFC Destination using ABAP / 4 driver (Transaction-SM59) so do anyone have detailed steps/any blog/code regarding that. Plz forward it.
Regards
Martin

Martin,
Hope this link is helpful
http://help.sap.com/saphelp_nw04/helpdata/en/89/45aad99715462abdf09ec503e151e7/frameset.htm
Regards
Kavitha

Abap query driver

Hi Friends,
Pls can any one tell me what is 'ABAP QUERY DRIVER '
Thanks in advance.
Thanks & Regards,
Ramnaresh.P.
Edited by: ramnaresh porana on Dec 23, 2008 4:44 AM

ABAP/4 Query is a powerful tool to generate simple reports
without any coding. ABAP/4 Query can generate the following
3 simple reports: Basic List: It is the simple reports.
Statistics: Reports with statistical functions like Average,
Percentages. Ranked Lists: For analytical reports. - For
creating a ABAP/4 Query, programmer has to create user group
and a functional group. Functional group can be created
using with or without logical database table. Finally,
assign user group to functional group. Finally, create a
query on the functional group generated.
for further details go throw this link
http://www.bbi.ch/bi/sap/info/Seagate%20Software%20SAP%20ABAP%20Query%20Driver.pdf

Will there ever be another downloadable ABAP Test Drive?

Unlike having to do a test-drive in the cloud, having a locally installed test drive system is much easier to administer, and is easier to access, especially if you are behind a firewall.
Will there ever be a testdrive (Linux or otherwise) of 7.40, specifically?

Only Apple could say and they never preannounce. But it would seem unlikely. iOS 3.1.3 is probably the last version that will run on the 1st-gen iPod touch.

Service Desk Configuration (Raising message from R3 system)

Hi,
I want to configure my R3 system, so that when I create a support Message it is reflected in Solution Manager.
I have done the following steps, in R3 system
1) Use transaction SM30 and modify BCOS_CUST table.
Entries in this table are
Col 1: OSS_MSG
Col 2: W
Col 3: SOLUTION_MANAGER (Not sure, what is the right entry for this column)
Col 4: CUST620
Col 5: 1.0
I am confused over the entry for Col 3:
In some postings I have seen that the value is SM_<sysid>CLNT<client>_TRUSTED, so assuming my Solution Manager SID is SL3 and Client is 100, the value for Col3 must be
SM_SL3_CLNT100_TRUSTED
Is the above assumption right?
2) Is it necessary to make entries for RFC destination in my R3 system using transaction SM59.
Also while creating the RFC Connection using transaction SM59 in the R3 system, it asks about the type of connection.
Which type of the connection, should be chosed.
Type :: Short text
I :: Connection to application server with same database
3 :: Connection to R/3 System
2 :: Connection to R/2 System
T :: Start an external program via TCP/IP
L :: Reference entry (refers to another destination)
S :: Start an external program via SNA or APPC
X :: RFC via special ABAP/4 driver routines
M :: CMC connection
H :: HTTP Connection to R/3 System
G :: HTTP Connection to External Server
Hope you can help..
Regards,
Vikas

Hi,
The third one is RFC destination which is a way of linking two systems providing there ip and login credentials.
When you create RFC in sm59 tcode you have to provide ip address and login credentials and a name,This name you have to provide in se11 bcos_cust table third field.
You have to create an R/3 or abap connection.check this for creating rfc connection.
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/content.htm
Check the following .
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
in short first of all go to tcode sm59 create a r/3 connection to your server and provide a name to it.
secondly go to bcos_cust table and provide this name in the third field.
Please reward points if it helps.
Message was edited by:
Prakhar Saxena

IDOC - See Beyond - SAP R/3

Hi All,
we are going to receive IDOC via See Beyond middleware.
Scenario as Follows:
R/3 - A -> See Beyond (then) See Beyond -> R/3-B.
I am responsible for INBOUND & OUTBOUND processing of IDOC, Can some one please tell me if I want to configure RFC destination to See Beyond from my R/3 system, what should be the connection type I have to select among the following ?
R/3 CONNECTIONS
Internal Connections
Logical destinations
TCP/IP Connections
Connection via ABAP/4 driver
Appropriate suggestions appreciated.
Regards,
Sridhar

Hi Sridhar,
Please check this links on how to setup TCP/IP connection.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9831750a-0801-0010-1d9e-f8c64efb2bd2
http://help.sap.com/saphelp_nw04/helpdata/en/42/821640b7b6dd5fe10000000a155106/content.htm
Regards,
Ferry Lianto
Please reward points if helpful.

Related to previous post..

Hi realted to my previous question, I was looking at standard ABAP SAPCript driver program PSFCOBJL.
I see something like follwoing inside include LCODRINC:-
Import .....
FROM MEMORY ID 'PPT'.
IMPORT ITAB
 ITAB_TDR FROM MEMORY ID 'PPI'.
IMPORT PRLST_TMP FROM MEMORY ID 'PPS'.
What does memory ID' PPT', 'PPI' and 'PPS' signify.
Is this the place from where we can ftech the initail data field(Explained in my previous post)
Tushar.

SAP and ABAP/4 Memory
There is a difference between the cross-transaction SAP memory and the transaction-specific ABAP/4 memory.
SAP memory
The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.
ABAP/4 memory
The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units). You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.
Please consult Data Area and Modularization Unit Organization documentation as well.
and
Memory Structures of an ABAP Program
IMPORT - Reading Data
Variants:
1. IMPORT obj1 ... objn FROM MEMORY.
2. IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
3. IMPORT obj1 ... objn FROM LOGFILE ID key.
4. IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
5. IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
6. IMPORT obj1 ... objn FROM SHARED BUFFER dbtab(ar) ID key.
7. IMPORT (itab) FROM ... .
Variant 1
IMPORT obj1 ... objn FROM MEMORY.
Additions:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... ID key
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See ID must be specified and Implicit Field Names not Allowed inClusters
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from a data cluster in ABAP memory . All data exported to ABAP memory using EXPORT... TO MEMORY without ID is read. Unlike the IMPORT FROM DATABASE variant, the sytsem does not check whether the structures used in EXPORT and IMPORT correspond.
The return code is set as follows:
SY-SUBRC = 0:
Data objects imported.
SY-SUBRC = 4:
Unable to import data objects.
The ABAP memory was probably empty.
The contents of all listed objects remain unchanged.
Notes
You should always use addition 3 /... ID key) with this statement. Variants that do not use this addition have unpredictable effects ( EXPORT statements in different parts of programs can overwrite each other's data in ABAP memory. These variants only exist for the sake of compatibility with R/2.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object you want to import)
Addition 2
... TO f (for each object you want to import)
Effect
Places the object in the field f.
Addition 3
... ID key
Effect
Only the data stored in ABAP memory under the key key is imported.
The return code is set as follows:
SY-SUBRC = 0:
Data objects imported.
SY-SUBRC = 4:
Data objects could not be imported.
You may have used an incorrect ID.
The contents of all listed objects remain unchanged.
Related
EXPORT TO MEMORY, FREE MEMORY
Variant 2
IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
Additions:
1. ... = f (for each object you want to import)
2. ... TO f (for each object you want to import)
3. ... CLIENT g (before ID key )
4. ... USING form
5. ... TO wa (as last addition or after dbtab(ar))
6. ... MAJOR-ID id1 (instead of ID key)
7. ... MINOR-ID id2 (together with MAJOR-ID id1)
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Implicit field names not allowed in clusters and Table work areas not allowed.
Effect
Imports data objects obj1 ... objn (fields, structures, complex structures, or tables) from the data cluster with the ID key in area ar of the database table dbtab (compare EXPORT TO DATABASE).
The return code is set as follows:
SY-SUBRC = 0:
Data objects imported.
SY-SUBRC = 4:
Data objects could not be imported.
You may have used an incorrect ID.
The contents of all listed objects remain unchanged.
Example
Importing two fields and an internal table:
TYPES: BEGIN OF TAB3_TYPE,
 CONT(4),
 END OF TAB3_TYPE.
DATA: INDXKEY LIKE INDX-SRTFD,
 F1(4), F2 TYPE P,
 TAB3 TYPE STANDARD TABLE OF TAB3_TYPE WITH
 NON-UNIQUE DEFAULT KEY,
 WA_INDX TYPE INDX.
INDXKEY = 'INDXKEY'.
IMPORT F1 = F1
 F2 = F2
 TAB3 = TAB3 FROM DATABASE INDX(ST) ID INDXKEY
 TO WA_INDX.
Notes
You must have named the table dbtab listed in DATABASE in a TABLES statement (except in addition 7).
The structure of the fields, structures, and internal tables that you want to import must correspond to the objects exported to the dataset. Furthermore, the objects must be imported with the same names with which they were exported. If you do not do this, the import will fail, and a runtime error may occur.
Exception: The last field may be longer or shorter, as long as it has type CHAR. Likewise, you can add or remove CHAR fields at the end of the structure.
Addition 1
... = f (for each object you want to import)
Addition 2
... TO f (for each object you want to import)
Effect
Places the object in the field f.
Addition 3
... CLIENT g (before ID key)
Effect
The data is taken from client g (only for client-specific import/export databases).
Example
DATA: F1,
 WA_INDX TYPE INDX.
IMPORT F1 = F1 FROM DATABASE INDX(AR) CLIENT '002' ID 'TEST'
 TO WA_INDX.
Addition 4
... USING form
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Effect
The data is not read from the database. Instead, the subroutine form is called for each data record that would have been read from the database. This routine can use the key fields of the records that would have been read from the work area of the database table and write the procured data into the work area. The routine has the name <database table name>_<subroutine name>. It has one parameter that describes the operation mode (READ, UPDATE, or INSERT). The routine must set SY-SUBRC to indicate whether the function has been executed successfully.
Note
Runtime errors: Various runtime errors can occur, depending on the operands you use to import data:
Addition 5
... TO wa (last addition or after dbtab(ar))
Effect
Use this addition when you want to read user data fields that have been strored in the database. Instead of the table work area, the statement uses the specified work area wa. The target area must have the structure of the corresponding table dbtab.
Example
DATA WA LIKE INDX.
DATA F1.
IMPORT F1 = F1 FROM DATABASE INDX(AR)
 CLIENT '002' ID 'TEST'
 TO WA.
WRITE: / 'AEDAT:', WA-AEDAT,
 / 'USERA:', WA-USERA,
 / 'PGMID:', WA-PGMID.
Addition 6
... MAJOR-ID id1 (instead of ID key)
Addition 7
... MINOR-ID id2 (together with MAJOR-ID id1)
This addition is not allowed in an ABAP Objects context. See Generic ID not allowed.
Effect
Searches for a record with an ID whose first part corresponds to id1 and (if you also specify MINOR-ID id2) whose second part is greater than or equal to id2.
Variant 3
IMPORT obj1 ...objn FROM LOGFILE ID key.
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Additions:
1. ... = f (for each field f you want to import)
2. ... TO f (for each field f you want to import)
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Implicit field names not allowed in clusters
Effect
Imports data objects (fields, structures, or internal tables) from the update data. You must specify the update key assigned by the system (with the serial request number).
The return code is set as follows:
SY-SUBRC = 0:
Data objects imported.
SY-SUBRC = 4:
Data objects could not be imported.
You may have used an incorrect ID.
The contents of all objects listed in the statement remain unchanged.
Addition 1
... = f (for each object you want to import)
Addition 2
... TO f (for each object you want to import)
Effect
Places the object in the field f.
Variant 4
IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
Additions:
1. ... CLIENT g (before ID key)
2. ... TO wa (last addition or after dbtab(ar))
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Table work areas not allowed.
Effect
Places a directory of the objects stored under the specified ID using EXPORT TO DATABASE in the internal table itab. itab may not have the type HASHED TABLE or ANY TABLE.
The return code is set as follows:
SY-SUBRC = 0:
Directory imported.
SY-SUBRC = 4:
Unable to import directory.
You may have used an incorrect ID.
The internal table itabmust have the same structure as the ABAP Dictionary structure CDIR (INCLUDE STRUCTURE).
Addition 1
... CLIENT g (before ID key)
Effect
Takes the data from client g (only if the import/export database is client-specific).
Addition 2
... TO wa (last addition, or after dbtab(ar))
Effect
Uses the specified work area wa instead of the table work area. The table dbtab specified after DATABASE does not, in this case, have to be declared in a TABLES statement. The specified target area must have the same structure as dbtab.
Example
Directory of a cluster consisting of two fields and an internal table.
TYPES: BEGIN OF TAB3_LINE,
 CONT(4),
 END OF TAB3_LINE,
 BEGIN OF DIRTAB_LINE.
 INCLUDE STRUCTURE CDIR.
TYPES END OF DIRTAB_LINE.
DATA: INDXKEY LIKE INDX-SRTFD,
 F1(4),
 F2(8) TYPE P decimals 0,
 TAB3 TYPE STANDARD TABLE OF TAB3_LINE,
 DIRTAB TYPE STANDARD TABLE OF DIRTAB_LINE,
 INDX_WA TYPE INDX.
INDXKEY = 'INDXKEY'.
EXPORT F1 = F1
 F2 = F2
 TAB3 = TAB3
 TO DATABASE INDX(ST) ID INDXKEY " TAB3 has 17 entries
 FROM INDX_WA.
IMPORT DIRECTORY INTO DIRTAB FROM DATABASE INDX(ST) ID INDXKEY
 TO INDX_WA.
DIRTAB subsequently has the following contents:
NAME OTYPE FTYPE TFILL FLENG
F1 F C 0 4
F2 F P 0 8
TAB3 T C 17 4
Meanings of the individual fields:
NAME:
Name of the object
OTYPE:
Object type (F: field, R: structure / ABAP Dictionary structure, T: internal table)
FTYPE:
Field type (C: character, P: packed, ...)
Structures and internal tables have type C.
TFILL:
Number of filled lines in an internal table
FLENG:
Length of the field in bytes
For internal tables: Length of the header line.
Variant 5
IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
This variant is not allowed in an ABAP Objects context. See Clusters not allowed in files
Note
Do not use this variant.
Note
Catchable runtime errors
The following catchable runtime errors can occur with this variant:
EXPORT_DATASET_CANNOT_OPEN: The EXPORT/IMPORT statement could not open the file.
OPEN_DATASET_NO_AUTHORITY: No authorization to access a file.
Variant 6
IMPORT obj1 ... objn FROM SHARED BUFFER dbtab(ar) ID key.
Additions:
1. ... = f (for each object you want to import)
2. ... TO f (for each object you want to import)
3. ... CLIENT g (before ID key)
4. ... TO wa (last addition or after dbtab(ar))
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See No implicit field names allowed in clusters and Table work areas not allowed.
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from the cross-transaction application buffer. The data objects are read from table dbtab using the ID key from area ar (see EXPORT TO SHARED BUFFER).
The return code is set as follows:
SY-SUBRC = 0:
Data objects imported.
SY-SUBRC = 4:
Unable to import data objects.
You may have used an incorrect ID.
The contents of all data objects listed in the statement remain unchanged.
Example
Importing two fields and an internal table from the application buffer with the structure indx:
TYPES: BEGIN OF ITAB3_LINE,
 CONT(4),
 END OF ITAB3_LINE.
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',
 F1(4),
 F2(8) TYPE P DECIMALS 0,
 ITAB3 TYPE STANDARD TABLE OF ITAB3_LINE,
 INDX_WA TYPE INDX.
Import data
IMPORT F1 = F1 F2 = F2 ITAB3 = ITAB3
 FROM SHARED BUFFER INDX(ST) ID INDXKEY TO INDX_WA.
After the import, the fields before CLUSTR
(INDX-AEDAT and INDX-USERA) are filled with the
values they had before the corresponding EXPORT
statement.
Notes
The table dbtab specified after DATABASE must be declared under TABLES (except in addition 2).
The structures of the fields, structures, and internal tables you want to import must be the same as those fo the objects you exported. The EXPORT and IMPORT statements (unlike IMPORT FROM DATABASE statement) does not check that they are the same. If the structures are not the same, a runtime error may occur if invalid assignments are attempted during the operation. The objects must also be imported using the same name as that with which they were exported. Otherwise, nothing is imported.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each field you want to import)
Addition 2
... TO f (for each field you want to import)
Effect
Places the object in field f.
Addition 3
... CLIENT g (before ID key)
Effect
Takes the data from client g (if the import/(export table dbtab is client-specific).
Addition 4
... TO wa (as last addition or after dbtab(ar))
Effect
Use this addition if the application buffer contains user data fields that you want to read. Instead of the table work area, the system uses the specified work area wa. The target area you specify must have the same structure as dbtab.
Example
DATA: INDX_WA TYPE INDX,
 F1.
IMPORT F1 = F1 FROM SHARED BUFFER INDX(AR)
 CLIENT '001' ID 'TEST'
 TO INDX_WA.
WRITE: / 'AEDAT:', INDX_WA-AEDAT,
 / 'USERA:', INDX_WA-USERA,
 / 'PGMID:', INDX_WA-PGMID.
Variant 7
IMPORT (itab) FROM ... .
Effect
Specifies the objects you want to import in the internal table itab. You can use this variant instead of the static object list in the following variants: " ... FROM MEMORY", "... FROM DATABASE ", " ... FROM DATASET" und "... FROM SHARED BUFFER". Any additions that are valid in the static cases can also be used here. The table itab may not have the type HASHED TABLE or ANY TABLE.
Note
Structure of the internal table itab:
The first column of the table contains the object name in the data cluster (corresponds to obj1 ... objn from the static case. The second column contains the different name in the program (if necessary), and corresponds to f in the FROM f addition. If the table has only one column, or the second column contains only blanks, the statemeht is the equivalent of a static IMPORT with no TO addition. Both the first and the second columns should have the type character.
Example
TYPES: BEGIN OF OBJ_LINE,
 CLUSTERNAME(30),
 PROGRAMNAME(10),
 END OF OBJ_LINE,
 BEGIN OF B_LINE,
 FIELD_1 TYPE I,
 FIELD_2(1) TYPE N,
 END OF B_LINE.
DATA: OBJ_TAB TYPE STANDARD TABLE OF OBJ_LINE,
 OBJ_WA TYPE OBJ_LINE,
 B_PROG TYPE STANDARD TABLE OF B_LINE,
 B_WA TYPE B_LINE,
 A(10),
 C_PROG LIKE SYST.
MOVE: 'A' TO OBJ_WA-CLUSTERNAME.
APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.
MOVE: 'B' TO OBJ_WA-CLUSTERNAME,
 'B_PROG' TO OBJ_WA-PROGRAMNAME.
APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.
MOVE: 'C' TO OBJ_WA-CLUSTERNAME,
 'C_PROG' TO OBJ_WA-PROGRAMNAME.
APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.
IMPORT (OBJ_TAB) FROM MEMORY ID 'ABCD'.
The dynamic EXPORT statement corresponds to the static IMPORT statement.
IMPORT A = A B = B_PROG C = C_PROG FROM MEMORY ID 'ABCD'.
Places the single field A in field A, the internal table B in the internal table B_PROG, and the structure C in the structure C_PROG.
Note
Runtime errors:
DYN_IMEX_OBJ_NAME_EMPTY: The object name in the cluster (that is, the contents of the first column of obj_tab) is empty.
DYN_IMEX_OBJ_NAME_TWICE: An object name (in the cluster) occurs twice in the first column of the internal table.
DYN_IMEX_OBJ_NOT_FOUND: The data object in the program (the object whose name appears in column 2, if this is not empty, otherwise in column 1) does not exist.
The return code is set as follows:
SY-SUBRC is set in the same way as for the static IMPORT.
Note
General notes about catchable runtime errors
The variants
IMPORT obj1 ... objn FROM MEMORY,
IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key,
IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key,
IMPORT obj1 ... objn FROM SHARED BUFFER dbtab(ar) ID key,
IMPORT (itab) FROM ... ,
can cause the following catchable runtime errors:
CONNE_IMPORT_WRONG_COMP_LENG: A component in the dataset has an incorrect length
CONNE_IMPORT_WRONG_COMP_TYPE: A component in the dataset has an incorrect type
CONNE_IMPORT_WRONG_FIELD_LENG: A field in the dataset has the wrong length
CONNE_IMPORT_WRONG_FIELD_TYPE: A field in the dataset has the wrong type
CONNE_IMPORT_OBJECT_TYPE: Type conflict between a simple and a structured data type
CONNE_IMPORT_WRONG_STRUCTURE: Type conflict between structured objects
IMPORT_ALIGNMENT_MISMATCH: Same sequence of components in different structures
IMPORT_TYPE_MISMATCH: Only with IMPORT...FROM MEMORY | FROM SHARED BUFFER...

Cannot connect to db after WAS 6.40 Sneak Preview Install

At one time I had the 6.20 ABAP test Drive and the 6.30 Java NW Dev. Stuio installed on my system. All was fine, and they lived in harmony. Windows services showed services for SAPDB: J2E and BSP (and a bunch of other SAPDB: servoces, too: CSAPxxxxx, e.g.). I am now trying to insatll the 6.40 ABAP stack.
I uninstalled the Java 6.30 NW DS system. (I see that the SAPDB J2E services are still there - what's up with that?)
I installed the 6.40 ABAP stack with no problems whatsoever. I secured a license from Walldorf, and now I'm trying to install it. When I run saplicense - install from a CMD window, I get the following error:
DBSlConnect error - RC = 99
SQL Error 709
This error occurs whether I've started the NSP system ID in SAPMMC or not. (When I start the NSP server, it's all green, except for two red lightning bolts, under
Current Status\R3Services\Background\Utilization 5%
Current Status\R3Services\Background\Aborted_Jobs Job SAP_RSICFDLT (count 18310201) aborted
I have not yet downloaded SAPGUI 6.40, so I'm not really out of business. I would like to know, however, what's causing the license install problem. I saw some other posts that are similar, but not exactly, to this problem, so I thought I'd go to the community for some guidance.
Thanks!

My temporary license on NSP WAS 6.40 is expired and I requested a new one. System runs and I can call the logon screen via sapgui but logon to the system is not possible because of the expired license and via CMD (dos box) I receive the following error:
SAPLICENSE (Release 700) ERROR ***
 ERROR: Connect to database failed
 DETAILS: DbSlConnect failed with return code 99
SQL-ERROR -10709 (check DB manual for explanation)
My WAS 6.20 BSP on another partition runs very well and there I had never a problem. Also the DATABase Manager of maxdb shows no problems and can connect to NSP.
I found many remarks about this problem but no solution is working.
Also the saplicense -test pf=<profile> runs until the connect to the db:
Protocol saplicense test:
Read sapsytem name
 ok, sapsytem name = NSP
Read message server host
 ok, host = xpsap02
Read message server service port
 ok, service port = sapmsNSP
Connect to message server
 ok, connect done
Read hardware key from message server
 ok, got hardware key
Detach from message server
 ok, detached
Check hardware key
 ok, hardware key = XYZA.......
Connect to database
SAPLICENSE (Release 700) ERROR ***
 ERROR: Connect to database failed
 DETAILS: DbSlConnect failed with return code 99
SQL-ERROR -10709 (check DB manual for explanation)
May be that someone had the same problems and has a quick solution.
Installation of NSP is on drive D (sapdb\programs and usr\sap.. The database is on drive F:\sapdb\NSP
Last remark: The system worked fine after installation on (23/1/2006) until I had to enter the first license.
Thanks
Michael Woidt

Help on XI installation..

Hello,
I am looking for help on XI installtion. I have enough RAM, but 50GB HD is good enough or it will be slow with 50GB. I don't have much data on my DB.
Also, I would like to know What is the sequence of installation. Hope DB(MaxDB), WEBAS ABAP+JAVA is enough to work with XI.
Is there anything else installation do i need to take care to work on.
Thanks in advance for ur help.
Srini

Hi Sri,
<how maxDb installation will happen>
Total space occupied by XI3.0 after installation is 23 to 25 GB (it covers everything, except os).
<do i need to install that first and give the DB details while installing WEBAS ABAP+JAVA. What are the other netweaver components do i need to install>
Steps for installation.
Note: while installing you have to select the drive manually with max space (in your case it will be selected by default since you will be having only 2 partitions)
1. Install win server 2000 with service pack 4 or higher. (C: drive)
2. Install Java1.4.2_10 (C: drive)
3. Install Oracle9 (D: drive)
4. Install WAS ABAP (D: drive)
5. Install J2EE (D: drive)
6. Install Netweaver Components (i don't remember but you have to chose first option inside netweaver components) (D: drive)
7. Do post configuration
Suggestion: Always give same password everywhere otherwise it will be difficult to manage it later on. )
That's it.
Regards,
Sarvesh

Error while installing NW7.3 ABAP for DB2 on z/OS Install DB CLI driver

Dear Experts,
i'm installing for the first time NW7.3 ABAP for DB2 on z/OS with AIX application server. Central Services was installed succesfull but next step Install Database on AIX stoped with error (establishConn.log):
db2radm (release: "720", patch level: "000", version: "Jan 14 2012") begin:28.02.2012 10:54:39
This is db2radm release: "720", patch level: "120", version: "Jan 14 2012".
This is db2radm setting up DB2 Connect.
Message file is /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log.
db2radm called as: /usr/sap/DW8/SYS/exe/uc/rs6000_64/db2radm -m db2i -P 456 -L DW8DDF -S DW88 -H s10d1 -u SAPADM -p ******** -W primary_only -l /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log
Adjusting environment
dbs_db2_ssid=DW88
SAPDBHOST=s10d1
dbs_db2_user=SAPADM
dbs_db2_schema=SAPADM
dbs_db2_schema8=1
dbs_db2_pw=********
Checking environment
DB host = s10d1
SSID = DW88
SAPSYSTEMNAME = DW8
DB2Trc: 000000 CLI_ALLOC_ENV 1
connect.ini file used: 'connect.ini.for.db2radm'
Fail over connection list of this application server:
NAME = DW88_on_s10d1
USER = SAPADM
PASSWORD = <***>
SCHEMA = SAPADM
PS = SAP0907U
LOCATION = DW8DDF
SSID = DW88
HOST = s10d1
PORT = 456
RETRY_CNT = 3
SLEEP_TIME = 0
DB2Trc: trace level of dbdb2cli set to 1
COLLECTION ID used is "SAP0907U"
DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL
use lib_dbsl for DB2 version V9.
Callback functions for dynamic profile parameter registered
DbSl library successfully loaded.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
SQL DRIVER VERSION is "09.07.0003"
DB2Connect driver identified as THIN CLIENT
Now I'm connected to DW88_on_s10d1
DB2 DBMS version 09.01.0005
DB2 LOCATION name DW8DDF
(HYB): Info: Using OLD dbsl support.
DB2 connect shared library loaded successfully.
09.07.0003DB2Connect driver identified as THIN CLIENT
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
connection profile /usr/sap/DW8/SYS/global/connect.ini opened.
>>>>>> dump of connection profile
ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
[DEFAULT_GROUP]
CON1=DW88_on_s10d1
[DW88_on_s10d1]
SSID=DW88
HOST=s10d1
PORT=456
LOCATION=DW8DDF
<<<<<< end of dump of connection profile
ssid DW88 found in connection profile, section DW88_on_s10d1.
>>> analyse line: * ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
>>> analyse line: [DEFAULT_GROUP]
>>> analyse line: CON1=DW88_on_s10d1
>>> analyse line:
>>> analyse line: [DW88_on_s10d1]
section DW88_on_s10d1 found.
>>> analyse line: SSID=DW88
>>> analyse line: HOST=s10d1
>>> analyse line: PORT=456
>>> analyse line: LOCATION=DW8DDF
>>> analyse line: section DW88_on_s10d1 found and data matches.
backup connection profile /usr/sap/DW8/SYS/global/connect.ini .
switch connection profile /usr/sap/DW8/SYS/global/connect.ini .
check for adapted connection profile.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
ssid DW88 found in connection profile, section DW88_on_s10d1.
check for adapted connection profile passed.
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|
DBSLHA:--|||||||||-|---|
GetHaProfile: GetHaProfile: found 1 connections in connection profile.
GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile
WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
DBSLHA: Using new Failover Support
DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.
DBSLHA:
DBSLHA:Connection List
DBSLHA:
DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|
DBSLHA:--|||||||||-|---|
DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|
DBSLHA:--|||||||||-|---|
SQL DRIVER VERSION is "09.07.0003"
DB2Connect driver identified as THIN CLIENT
DB2Trc: 00 000000 cli_get_cli_driver_bld_level 1 s101006
SQL DRIVER NAME is "libdb2.a"
SQL DBMS NAME is "DB2"
SQL DBMS VERSION is "09.01.0005"
DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
The bind is skipped since collection for ssid DW88 is already bound.
To force the bind, use option "-B force".
DB2TRC: 0000000000 00 000000 CLI_DISCONNECT
DB2TRC: 0000000000 00 000000 CLI_FREE_DBC 1
DB2TRC: 0000000000 00 000000 CLI_FREE_ENV 1
DB VERSION is 09.01.0005.
Starting Grants .
DB2Trc: 000000 CLI_ALLOC_ENV 1
COLLECTION ID used is "SAP0907U"
DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL
Connecting to <DW88_on_s10d1> on connection 0 ...
Now I'm connected to DB2 (09.01.5)
SQL DRIVER NAME is "libdb2.a"
SQL DBMS NAME is "DB2"
SQL DBMS VERSION is "09.01.0005"
DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
New functions of DB2 V9 are switched on
Profile parameter dbs/db2/cli_trace_dir is not set
dbdb2dic.c 1709 INFO Profile: SDB2_DEBUG=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: sdb2_debug=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: SDB2_DEBUG=<UNSET>
DB2 Call 'CLI_EXECUTE' Error: sqlcode = -204 : [IBM][CLI Driver][DB2] SQL0204N "SAPADM.#LOBU" is an undefined name. SQLSTATE=42704
dbdb2dic.c 2251 INFO rc=103,sqlcode=-204: ExeRead
dbdb2dic.c 1709 INFO Profile: dbs/db2/max_retry=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: DB2_MAX_RETRY=<UNSET>
dbdb2dic.c 1709 INFO Profile: dbs/db2/retry_on_924=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: DB2_RETRY_ON_924=<UNSET>
dbdb2dic.c 1709 INFO Profile: dbs/db2/no_retry_on_10=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: dbs_db2_no_retry_on_10=<UNSET>
dbdb2dic.c 1733 INFO Envrmnt: DBS_DB2_NO_RETRY_ON_10=<UNSET>
DB2 Call 'SQLEndTran' Error: sqlstate = 08003 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
[dbdb2dic.c 1873:rc=99: COMMIT WORK failed]
dbdb2dic.c 1873 ERROR rc=99: COMMIT WORK failed
[dbdb2dic.c 2019:rc=99,sqlcode=268435455: ExecDDL failed (DB error)]
dbdb2dic.c 2019 ERROR rc=99,sqlcode=268435455: ExecDDL failed (DB error)
DB2 Call 'SQLEndTran' Error: SQLCODE = -99999 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
ROLLBACK failed with SQL error '-99999'
ERROR: couldn't connect to DB
rc = 99
error message returned by DbSl:
rc=99,sqlcode=268435455: ExecDDL failed (DB error)
DB2RADM EXITCODE: 12
db2radm finished (0012)
db2radm stop:28.02.2012 10:54:39
i've patched db2radm and sapinst to the latest version.
May be i should manually create "SAPADM.#LOBU"?
Please help to solve these issue.
Best regards,
Alexander V

Hi ,
Please check if Note 1581637 - Installing a System with DB2CODEPAGE other than the default is useful.
Award points if useful.
Thanks,
Ravi

Problem Installing ABAP Engine of SAP WAS 6.20(TEST DRIVE VERSION)

Hi
I am trying to install ABAP Engine of SAP WAS 6.20(TEST DRIVE VERSION) which I got with the official ABAP Reference book of SAP press.
It is installing upto 91% and giving the following errors:
RC code form SyCoprocessWait = -2 .
Error: DBR3LICENSECREATE ExecuteCheck 2 718
Exit code from C:\MiniWAS\saplicense: -2.
Error: DBR3LICENSECREATE InternalInstallationDo 2 718
Phase failed.
Error: DBR3LICENSECREATE InstallationDo 2 718
Phase failed.
Error: Main {} 2 718
Installation aborted.
I am trying to learn ABAP and need to practise it. Could someone please help me in this matter.

Restart the install and search this forum for "MiniWAS", "Mini Was", "620 install" and you'll find half a dozen people who had the same problem.

Adobe Forms in ABAP Image upload from a local drive

Hello,
Can anybody suggest me the procedure, how to upload the image field dynamically of an employee which is existing in PA30 to SAP interactive forms (SFP). I have gone through many forums but could not able to find any right solution on it.. and hence my development is required to design the layout and call this not through WDP but using ABAP report SE38 in order to generate the employee CV, the programming logic completed till downlaoding the employee photo to local drive from PA30 and I need the same to upload the picture which is downloaded earlier by my driver program into adobe form. Can anyboby help me on this mentioned issue will be appreciated.
Thanks in advance.
Regards,
Murali.

Thanks Kittu for your speedy response, I have already checked the link which was sent by you...But I couldn't able to find any helpful solution to my requirement. Can you please suggest me any new procedure to solve my problem.

ABAP HR: BADI for payroll driver

Hi Experts,
The requirement is to create the badi/user exit in payroll driver. Can any one please list the names of badis and user exits available for RPCALCU0. I am working on ecc 6.0.
Thanks.
Irfan

Hi Irfan,
Business Add - ins
                                                                                PC10_PAY0001 User exit for base_wages in a gross up calculation
PC10_PAY0002   Exit to determine if negative taxables should be allowed
PC10_PAY0003   Exit to determine if distribution calc should be allowed
PC10_PAY0004   Work Tax Area Override Add-In: Activation
PC10_PAY0005 Work Tax Area Override Add-In: Default proration of wages
PC10_PAY0006    User exit for additional ESS W4 (PZ10) fields; before output
PC10_PAY0007   User exit for PZ10 and IT0210 fields; after input
PC10_PAY0008   More than 99 exemptions for US payroll withholding tax calc
Enhancement
HRUSRCU0     Enhancement for Customer Exit for RPCTRCU0.
Regards,
IFF

How to browse through System drives in ABAP

Hello Experts,
I want to search the system drives for pdf files...Could you please help me with tyhe approach or with the code??
Actually i want to save a file as .PDF so i want that user will have the facility to browse through his/her hard drives & save it in desired position.
Please Help..
Anupam..

use fm
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
* DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = ' '
 IMPORTING
 FILE_NAME = P_FILE1.
or
CALL METHOD cl_gui_frontend_services=>file_save_dialog
 CHANGING
 filename = fname
 path = fpath
 fullpath = flpath
 EXCEPTIONS
 cntl_error = 1
 error_no_gui = 2
 not_supported_by_gui = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Regards,
Sumit Nene.
Edited by: Sumit Nene on Jul 20, 2009 2:22 PM

SAP NW7.01 ABAP trial version installation on Windows Vista. Error message

Hi gurus,
I am installing SAPNW7.01 ABAP trial version.. getting following Error nessage ..ANy idea?
The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag.
I have WINDOWS VISTA with 32bit..I read in document for SAPNW7.01 ABAP trial vesrion, it can be installed on windows vista also..
Any one has any idea? I suspect it is error bcz of Java files..but I am not sure..
Thanks in advance..

Hi Sanjeeva,
At first see where java is installed i.e JDK directory, as per as my knowledge it will be in WINDOWS directory like C drive.
For setting environmental variable (i.e JAVA_HOME,PATH), please follow the below link
http://www.astahost.com/info.php/Change-Windows-User-Environment-Variables_t19560.html
Thanks
Debdeep

Abap/4 Driver

Similar Messages

Maybe you are looking for