LDB error

*& Report  ZPV003HR_ANIV_EMP                                          
REPORT  zpv003hr_aniv_emp  .
TABLES: pernr.
INFOTYPES: 0002,
           0001.
DATA: age TYPE d,
      serv TYPE d,
      curdate TYPE d.
DATA: years TYPE d,
      enddate TYPE d .
DATA: BEGIN OF int_empinfo OCCURS 0,
        pernr LIKE p0002-pernr,
        nachn LIKE p0002-nachn,
        vorna LIKE p0002-vorna,
        gbdat LIKE p0002-gbdat,
        begda LIKE p0001-begda,
        emp_age   TYPE d,
        emp_serv  TYPE d,
      END OF int_empinfo.
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME TITLE text-001.
PARAMETERS: 5_years RADIOBUTTON GROUP g1  DEFAULT 'X',
            10_years RADIOBUTTON GROUP g1,
            15_years RADIOBUTTON GROUP g1.
*curdate type d DEFAULT '00050101' .
SELECTION-SCREEN END OF BLOCK block1.
START-OF-SELECTION .
  IF 5_years = 'X'.
    curdate = '00050101'.
  ELSEIF 10_years = 'X'.
    curdate = '00100101'.
  ELSEIF 15_years = 'X'.
    curdate = '00150101'.
  ENDIF.
GET pernr.
When I compile above piece of code, it says "PERNR" is not defined for the current logical databse.How to go about this.

Hi,
       In the attributes of the PROGRAM, have you mentioned the LDB as PNP or PNPCE.
        Mention LDB as PNP/PNPCE.
Just try with this.

Similar Messages

  • FTP Upload problem on Dreamweaver 8

    Hi, I'm new to Dreamweaver and I've created my site which
    uploads successfully except fot a couple of MS Access database
    files which I need for password protection of my site.
    To me it looks like a permission problem for the localhost
    folder on my PC.
    I've followed all the steps for enabling relevant permissions
    for the Internet Guest Account (which appears in the Security Tab
    of that folder's Properties dialogue box).
    I've saved the MS Access database files in the 2003 version
    (instead of MS Access 2007).
    Operating System: Windows XP pro Service Pack 3
    Dreameaver 8
    Below is the error message.
    Connections\myhealthnetwork.asp - Put operation successful
    _private\myhealthnetwork.ldb - error occurred - An FTP error
    occurred - cannot put myhealthnetwork.ldb. Access Denied. The file
    may not exist, or there could be a permission problem.
    _private\myhealthnetwork.mdb - error occurred - An FTP error
    occurred - cannot put myhealthnetwork.mdb. Access Denied. The file
    may not exist, or there could be a permission problem.
    File activity incomplete. 2 file(s) or folder(s) were not
    completed.
    Files updated: 1
    Files with errors: 2
    _private\myhealthnetwork.ldb
    _private\myhealthnetwork.mdb
    Finished: 07/07/2008 10:02

    Hi, I'm also using Dreamweaver 8 and have encountered this
    problem before. I'm a little limited on my technical expertise
    however I have found either of the following solutions helped.
    1. Delete the corresponding files on your remote server and
    FTP again using the 'Put' function rather than the 'Syncronise'
    function.
    2. Alternatively, if using 'Cpanel' initially upload your
    Database using your Cpanel browser and then make subsequent updates
    by DW FTP, this seems to fix the prob by setting or re-setting the
    appropriate permissions.
    Sorry can't be more help
    Altum

  • Error In HR report using PNP LDB

    Hi ,
    I am new to ABAP Hr , while writing a report using LDB pnp it  is giving me an error like
    " In Unicode programs, the "-" character cannot appear in names, as it          
    does here in the name "PNP-SW-IGNORELOCKEDRECORDS".
    Can any one please help me what it is for , and how it can be removed .
    Thanx

    Hi abap,
    1. do not worry,
    2. Its just a warning message (and not an error message)
    regards,
    amit m.

  • Error while using LDB in HR Program

    Hi,
    While accessing ALV output in LDB program, when i press the back button, i am getting an error message as:
    Personnel numbers skipped by the database driver.
    Can someone explain the reason for it and how to rectify.
    Thanks,
    cs

    Please check If UR using GET PERNR event .. if so where
    UR calling the FM to display ALV ..
    it should be in the order ..
    start-of-selection.
    get pernr.
    Populate internal table for ALV ...
    end-of-selection.
    call FM to display ALV ...

  • Infoset with ldb IOC - error in selection parameter

    Hi Expers,
    could any of You pls help me with an issue - creating infoset with ldb, and get error in selection parameter definiton.
    I am about to create an infoset than a query, using IOC logical database, and get a couple of error message related to selecion parameters - such as: error in sel. parameter P_PICK is - Statement concluding with "...TYPE" ended unexpectedly.
    I do not really need this parameter for my selection, so I was to delete - but I could not find it amongst the selection fields in actual infoset. When I tried to create it, I got a message: it has already been created (of course), but where can I find / change it if not amongst listed selection parameters (Extras / Selection)
    I suppose I can not make any changes in DBIOCSEL - because COOIS is also using this ldb - and it might have some unexpected effect there as well.
    Later I started to create a Z*report via SE80, using same ldb, and it works fine.
    So it is not a burning issue any more, but still interesting, why infoset has problem with the sel. parameter which is actually not in use.
    All usefull answer is appreciated
    Br

    Hi,
    the selection screen is coded without a number. Here's the code:
    SELECTION-SCREEN BEGIN OF BLOCK selection WITH FRAME TITLE text-t11.
    SELECTION-SCREEN BEGIN OF BLOCK persdata WITH FRAME TITLE text-t01.
    SELECT-OPTIONS so_pernr FOR ls_pa0017-pernr.
    SELECTION-SCREEN END OF BLOCK persdata.
    SELECTION-SCREEN END OF BLOCK selection.
    SELECTION-SCREEN BEGIN OF BLOCK input WITH FRAME TITLE text-t12.
    SELECTION-SCREEN BEGIN OF BLOCK zeitraum WITH FRAME TITLE text-t02.
    PARAMETERS pa_begda TYPE p0017-begda DEFAULT sy-datum OBLIGATORY.
    PARAMETERS pa_endda TYPE p0017-endda DEFAULT '99991231' OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK zeitraum.
    SELECTION-SCREEN BEGIN OF BLOCK gruppierungen WITH FRAME TITLE text-t03.
    PARAMETERS pa_spebe TYPE p0017-spebe OBLIGATORY DEFAULT '1'.
    SELECTION-SCREEN END OF BLOCK gruppierungen.
    SELECTION-SCREEN BEGIN OF BLOCK zuordnungen WITH FRAME TITLE text-t05.
    PARAMETERS pa_bukrs TYPE p0017-bukrs MATCHCODE OBJECT c_t001 DEFAULT '2000'.
    PARAMETERS pa_gsber TYPE p0017-gsber MATCHCODE OBJECT h_tgsb DEFAULT '0001'.
    SELECTION-SCREEN END OF BLOCK zuordnungen.
    SELECTION-SCREEN END OF BLOCK input.
    SELECTION-SCREEN BEGIN OF BLOCK attributes WITH FRAME TITLE text-t13.
    PARAMETERS pa_test AS CHECKBOX DEFAULT 'x'.
    SELECTION-SCREEN END OF BLOCK attributes.
    Regards
    Mark-André

  • Error while declaring RT_PERSON using pnpce ldb

    when am declaring
    data : RT_PERSON like line of PC2RT_PERSON.
    am getting an error msg that
    "FIELD 'PC2RT_PERSON' is unknown .it is neither in the specified tables, nor in the DATA statement".
    whatz the error .what should i do.
    points will be rewarded.
    thanks in advance.

    declare as :
    data : RT_PERSON like PC2RT_PERSON.

  • How to use LDB PNP with ABAP objects in a program

    Hello,
    I am wondering if anybody has used the HR logical database(LDB) PNP with user defined ABAP objects in a program? I am using the FM- <b>LDB_PROCESS</b> but its not working. Also assigning PNP in the attributes section of the program -- so that I can use predefined fields from the LDB and then invoking the FM doesn't work -- throwing 'Logical database already active' error.
    I suppose even with the ABAP objects and the new FM -- I should still be able to utilize the pre-defined fields of the PNP database -- and also the built in authorizations. I cannot use GET PERNR and REJECT as they give errors. I understand that the use of HR-macros (RP-PROVIDE-FROM-LAST and et al.) are not allowed as they use the table work area -- which is not allowed in ABAP-OOPS.
    I would really appreciate if anyone could show me some insight regarding this. Thank you.
    Kshitij R. Devre

    Hi Kshitij
    It would be really good if we could use both together. But as I know, it is not possible. "GET pernr." is an event-like loop statement and so cannot be used in OO context. And I guess, the same restriction holds for the "LDB_PROCESS" since it uses LDB-specific processing.
    What I suggest you is to use standard and BAPI functions.
    Sorry for giving bad news...
    *--Serdar

  • System Copy(homogenous) Error -Database load phase

    Hello All,
    I am doing System Copy thorugh Export - Import meothed of SAP R/3 4.7 110 on Windows2003-SQL 2000 SP3. Making Copy of Production server with different SID.After taking Export Successfully from Production Server I am Importing it to Target System
    but i am facing error at Database Load Phase getting the same error on almost every process like SAPSSEXE,SAPCLUST,SAPAPPL0,SAPAPPL1 etc. the error is below :
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202046
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe -ctf I C:\EXPORT/DATA/SAPAPPL1.STR C:\EXPORT/DB/DDLMSS.TPL C:\SAPinst MSSQL SAPINST3/SAPAPPL1.TSK MSS -l C:\SAPinst MSSQL SAPINST3/SAPAPPL1.log
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job completed
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808202047
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202053
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst MSSQL SAPINST3/SAPAPPL1.cmd -l C:\SAPinst MSSQL SAPINST3/SAPAPPL1.log -loadprocedure fast
    DbSl Trace: SQLOLEDB Provider Release:08.10.3959
    DbSl Trace: Shared cache sizes: header 52 bytes, 10000 names (13360000 bytes), 1000 dynamic statements (5436000 bytes), total 18796052 bytes
    DbSl Trace: Initializing private procedure name cache.
    DbSl Trace: procedure cache created/attached
    DbSl Trace: Thank You for using the SLOLEDB-interface
    DbSl Trace: Connected to db server : [prdt], dbname: PRT, dbuser: prt
    DbSl Trace: Using dynamic link library 'E:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll'
    DbSl Trace: dbmssslib.dll patch info
    DbSl Trace:   patchlevel   0
    DbSl Trace:   patchno      524
    DbSl Trace:   patchcomment DBDYNPSOURCE/DBDYNPSOURCE~, SHADOW_IMPORT_ALL (578789)
    DbSl Trace: The IRow interface is supported by this OLEDB provider
    DbSl Trace: ParamStmtExec: line 23573. hr: 0x80040e37 Invalid object name 'SVERS'.
    DbSl Trace: HandleOledbError [ParamStmtExec,line 23573]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.
    DbSl Trace: ParamStmtExec failed.  HR 80040e37 DBSL retcode 103. stmt: [SELECT VERSION AS c FROM SVERS ]
    DbSl Trace: Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:12157
    DbSl Trace: DbSlRead - Error 103 (dbcode 208) on open
    DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000001202054>
    DbSl Trace: DbSlRead - Error 103 (dbcode 208) on fetch
    DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000001202054>
    Sat Aug 08 20:20:54 2009
    **LOG BZA=> table SVERS      does not exist on database [dblink#1 @ 1292] [dblink  1292 ]
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "PRTprdt                                                                                "
    (GSI) INFO: vname    = "MSSQL                           "
    (GSI) INFO: hostname = "PRDT                                                            "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "PRDT"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 2"
    (GSI) INFO: machine  = "2x Intel 80686 (Mod 15 Step 2)"
    DbSl Trace: ParamStmtExec: line 23573. hr: 0x80040e37 Invalid object name 'SVERS'.
    DbSl Trace: HandleOledbError [ParamStmtExec,line 23573]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.
    DbSl Trace: ParamStmtExec failed.  HR 80040e37 DBSL retcode 103. stmt: [SELECT VERSION AS c FROM SVERS ]
    DbSl Trace: Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:12157
    DbSl Trace: DbSlRead - Error 103 (dbcode 208) on open
    DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000002202054>
    DbSl Trace: DbSlRead - Error 103 (dbcode 208) on fetch
    DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000002202054>
    Interface access functions from dynamic library dbmssslib.dll loaded.(IMP) INFO: import of /1DF/__GI000 completed (0 rows)
    (IMP) INFO: import of /BDL/BADHOST completed (0 rows)
    (IMP) INFO: import of /BDL/CUSTSES completed (0 rows)
    (IMP) INFO: import of /BDL/INTSESS completed (0 rows)
    (IMP) INFO: import of /BDL/MSGLOG completed (0 rows)
    (IMP) INFO: import of /BDL/NOHOSTS completed (0 rows)
    (IMP) INFO: import of /BDL/SESDEST completed (0 rows)
    (IMP) INFO: import of /BDL/SESS completed (0 rows)
    (IMP) INFO: import of /BDL/STATUS completed (0 rows)
    (IMP) INFO: import of /BDL/TESTSES completed (0 rows)
    (IMP) INFO: import of /BDL/TRHOSTS completed (0 rows)
    (IMP) INFO: import of /SAPDMC/LSOFIL completed (56 rows)
    (IMP) INFO: import of /SAPDMC/LSOFIW completed (0 rows)
    (IMP) INFO: import of /SAPDMC/LSOPRT completed (0 rows)
    (IMP) INFO: import of /SAPSLL/BWHSTR3 completed (0 rows)
    (IMP) INFO: import of /SAPSLL/CUWLAR3 completed (0 rows)
    (IMP) INFO: import of /SAPSLL/KMATWLR3 completed (0 rows)
    (IMP) INFO: import of /SAPSLL/OBJIDX completed (0 rows)
    (IMP) INFO: import of /SAPSLL/OBJSSF completed (0 rows)
    (IMP) INFO: import of /SAPSLL/OBJSYNC completed (0 rows)
    (IMP) INFO: import of /SAPSMOSS/UPDATE completed (0 rows)
    (IMP) INFO: import of /SAPTRX/AOTREF completed (0 rows)
    (IMP) INFO: import of /SAPTRX/APPTALOG completed (0 rows)
    (IMP) INFO: import of /SAPTRX/ASITEMID completed (0 rows)
    (IMP) INFO: import of /SAPTRX/MTOBJLOG completed (0 rows)
    (IMP) INFO: import of /SCMB/DF_DEL_TAB completed (0 rows)
    (IMP) INFO: import of /SCMB/DF_DNET completed (0 rows)
    (IMP) INFO: import of /SCMB/DF_DOC completed (0 rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SCMB/DF_DOC_VAL
    completed (0 rows)
    (IMP) INFO: import of /SCMB/DF_DQTY completed (0 rows)
    (IMP) INFO: import of /SCMB/DF_DVALUE completed (0 rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SCMB/TREEVIEW2 completed
    (0 rows)
    (IMP) INFO: import of /SDF/INDX completed (0 rows)
    (IMP) INFO: import of /SDF/SDBAH completed (0 rows)
    (IMP) INFO: import of /SOMO/JOSCHEDL completed (0 rows)
    (IMP) INFO: import of /SOMO/JOSCHEDLT completed (0 rows)
    (IMP) INFO: import of /SSF/DHEAD completed (1 rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SSF/DTAB completed (18
    rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SSF/PTAB completed (7520 rows)
    (IMP) INFO: import of A055 completed (0 rows)
    (IMP) INFO: import of A056 completed (0 rows)
    (IMP) INFO: import of A064 completed (0 rows)
    (IMP) INFO: import of A065 completed (0 rows)
    (IMP) INFO: import of ABDBG_BPS completed (0 rows)
    (IMP) INFO: import of ABDBG_INFO completed (0 rows)
    (IMP) INFO: import of ACCRPOST completed (0 rows)
    (IMP) INFO: import of ACCTCR completed (7346418 rows)
    (IMP) INFO: import of ACCTHD completed (624272 rows)
    (IMP) INFO: import of ACCTIT completed (3673209 rows)
    (IMP) INFO: import of ACEPSOH completed (0 rows)
    (IMP) INFO: import of ACEPSOI completed (0 rows)
    (IMP) INFO: import of ACEPSOIT completed (0 rows)
    (IMP) INFO: import of ACL_ACE completed (0 rows)
    (IMP) INFO: import of ACL_ACTGR completed (0 rows)
    (IMP) INFO: import of ACL_ACTGRE completed (0 rows)
    (IMP) INFO: import of ACL_ACTGRT completed (0 rows)
    (IMP) INFO: import of ACL_ACTVT completed (0 rows)
    (IMP) INFO: import of ACL_ACTVTT completed (0 rows)
    (IMP) INFO: import of ACL_CACHE completed (0 rows)
    (IMP) INFO: import of ACL_MAIN completed (0 rows)
    (IMP) INFO: import of ACL_OBJTP completed (0 rows)
    (IMP) INFO: import of ACL_OBJTPA completed (0 rows)
    (IMP) INFO: import of ACL_OBJTPG completed (0 rows)
    (IMP) INFO: import of ACL_OBJTPT completed (0 rows)
    (IMP) INFO: import of ACL_OWNER completed (0 rows)
    (IMP) INFO: import of ACRELATION completed (76954 rows)
    (IMP) INFO: import of ACTFLI completed (0 rows)
    (IMP) INFO: import of AD01DLI completed (0 rows)
    (IMP) INFO: import of AD01DLIEF completed (0 rows)
    (IMP) INFO: import of AD01DLISF completed (0 rows)
    (IMP) INFO: import of AD01FILTVAR completed (0 rows)
    (IMP) INFO: import of AD01STRUCTVAR completed (0 rows)
    (IMP) INFO: import of AD01VARMASTER completed (0 rows)
    (IMP) INFO: import of ADATABSIZE completed (0 rows)
    (IMP) INFO: import of ADJT_TRANSACTION completed (0 rows)
    (IMP) INFO: import of ADMI_BUFFC completed (0 rows)
    (IMP) INFO: import of ADMI_BUFFI completed (0 rows)
    (IMP) INFO: import of ADMI_FILES completed (0 rows)
    (IMP) INFO: import of ADMI_JOBS completed (0 rows)
    (IMP) INFO: import of ADMI_RJOBS completed (0 rows)
    (IMP) INFO: import of ADMI_RUN completed (0 rows)
    (IMP) INFO: import of ADMI_SKIP completed (0 rows)
    (IMP) INFO: import of ADMI_STATS completed (0 rows)
    (IMP) INFO: import of ADMI_VARIA completed (0 rows)
    (IMP) INFO: import of ADMI_XDOCS completed (0 rows)
    (IMP) INFO: import of ADMI_XRUN completed (0 rows)
    (IMP) INFO: import of AFAB completed (0 rows)
    (IMP) INFO: import of AFBP completed (0 rows)
    (IMP) INFO: import of AFFH completed (0 rows)
    (IMP) INFO: import of AFFL completed (366118 rows)
    (IMP) INFO: import of AFFT completed (0 rows)
    (IMP) INFO: import of AFFV completed (0 rows)
    (IMP) INFO: import of AFFW completed (7 rows)
    (IMP) INFO: import of AFFWPRO completed (0 rows)
    (IMP) INFO: import of AFIH completed (113 rows)
    The above error are also present in the other Process log files.
    But when i saw the installation logs of the Source system the same errors are also there(but it was still Sucessfull Standard installation).
    there is one difference as well I am SQL SP3 (8.00.780) but existing Production server is SQL SP3(8.00.929).
    My installation is stoppoing here with error While executing Script.
    I've done Homogenous copy on WiN-ORACLE many times but on WIN-SQL i am doing very first time.
    While installation database phase it asked me for EXPORT CD twice first time for standard(which usually we got with SAP Software) and Second time for Migration EXPORT. that is different from ECC5.0 i think.
    Any suggestions?
    Regards,
    Vinay
    Edited by: Vinay Paul on Aug 8, 2009 11:01 PM

    Dear Markus,
    Thanks for the Reply.
    As you Said i am upgrading my kernal (making it same as current kernel using bysource system that is 175).
    Hope this will solve my problem ....Do i have to restart my complete installation now?
    My recent last error was :
    SAPSSRC.LOG
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202048
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe -ctf I C:\EXPORT/DATA/SAPSSRC.STR C:\EXPORT/DB/DDLMSS.TPL C:\SAPinst MSSQL SAPINST3/SAPSSRC.TSK MSS -l C:\SAPinst MSSQL SAPINST3/SAPSSRC.log
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job completed
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808202048
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808221527
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst MSSQL SAPINST3/SAPSSRC.cmd -l C:\SAPinst MSSQL SAPINST3/SAPSSRC.log -loadprocedure fast
    DbSl Trace: SQLOLEDB Provider Release:08.10.3959
    DbSl Trace: Shared cache sizes: header 52 bytes, 10000 names (13360000 bytes), 1000 dynamic statements (5436000 bytes), total 18796052 bytes
    DbSl Trace: Initializing private procedure name cache.
    DbSl Trace: procedure cache created/attached
    DbSl Trace: Thank You for using the SLOLEDB-interface
    DbSl Trace: Connected to db server : [prdt], dbname: PRT, dbuser: prt
    DbSl Trace: Using dynamic link library 'E:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll'
    DbSl Trace: dbmssslib.dll patch info
    DbSl Trace:   patchlevel   0
    DbSl Trace:   patchno      524
    DbSl Trace:   patchcomment DBDYNPSOURCE/DBDYNPSOURCE~, SHADOW_IMPORT_ALL (578789)
    DbSl Trace: The IRow interface is supported by this OLEDB provider
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "PRTprdt                                                                                "
    (GSI) INFO: vname    = "MSSQL                           "
    (GSI) INFO: hostname = "PRDT                                                            "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "PRDT"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 2"
    (GSI) INFO: machine  = "2x Intel 80686 (Mod 15 Step 2)"
    Interface access functions from dynamic library dbmssslib.dll loaded.(IMP) INFO: import of ABTREE completed (39 rows)
    (IMP) INFO: import of AKB_CHKCONF completed (0 rows)
    (IMP) INFO: import of AKB_INDX completed (0 rows)
    (IMP) INFO: import of APTREE completed (1531 rows)
    (IMP) INFO: import of APTREET completed (75 rows)
    (IMP) INFO: import of CAPTREE completed (0 rows)
    (IMP) INFO: import of CAPTREET completed (0 rows)
    (IMP) INFO: import of CCCEXIT completed (44 rows)
    (IMP) INFO: import of CCCINFO completed (15 rows)
    (IMP) INFO: import of CLMCUS completed (0 rows)
    (IMP) INFO: import of CONTCOMP completed (2 rows)
    (IMP) INFO: import of CONTCOMPT completed (4 rows)
    (IMP) INFO: import of CONTCOMPX completed (2 rows)
    (IMP) INFO: import of CONTCOMPXT completed (3 rows)
    (IMP) INFO: import of CROSS completed (1399548 rows)
    (IMP) INFO: import of CUSTDIR completed (0 rows)
    (IMP) INFO: import of CWBMODILOG completed (0 rows)
    (IMP) INFO: import of DBDATA completed (0 rows)
    (IMP) INFO: import of DIRTREE completed (21 rows)
    (IMP) INFO: import of DVSEQDIR completed (0 rows)
    (IMP) INFO: import of DWTREE completed (522 rows)
    (IMP) INFO: import of EUDIAL completed (0 rows)
    (IMP) INFO: import of EUF4VALUES completed (34 rows)
    (IMP) INFO: import of EUFUNC completed (76 rows)
    (IMP) INFO: import of EUIMPORT completed (47 rows)
    (IMP) INFO: import of EUINFO completed (2772 rows)
    (IMP) INFO: import of EUINFOLI completed (0 rows)
    (IMP) INFO: import of FUSEQDIR completed (0 rows)
    (IMP) INFO: import of GUIDIR completed (0 rows)
    (IMP) INFO: import of GUIDIRT completed (3 rows)
    (IMP) INFO: import of GUINODE completed (0 rows)
    (IMP) INFO: import of GUINODT completed (0 rows)
    (IMP) INFO: import of ICON completed (982 rows)
    (IMP) INFO: import of ICONP completed (149 rows)
    (IMP) INFO: import of ICONT completed (3361 rows)
    (IMP) INFO: import of ICO_P completed (0 rows)
    (IMP) INFO: import of LDBS completed (0 rows)
    (IMP) INFO: import of MAPPARAREF completed (0 rows)
    (IMP) INFO: import of MODACT completed (0 rows)
    (IMP) INFO: import of MODATTR completed (0 rows)
    (IMP) INFO: import of MODIDIR completed (0 rows)
    (IMP) INFO: import of MODSAPA completed (2049 rows)
    (IMP) INFO: import of MODSAPT completed (3991 rows)
    (IMP) INFO: import of MODTEXT completed (0 rows)
    (IMP) INFO: import of O2APPL completed (164 rows)
    (IMP) INFO: import of O2APPLT completed (305 rows)
    (IMP) INFO: import of O2PAGCON completed (4120 rows)
    (IMP) INFO: import of O2THEMEREL completed (0 rows)
    (IMP) INFO: import of O2THEMES completed (1 rows)
    (IMP) INFO: import of O2THEMEST completed (0 rows)
    (IMP) INFO: import of O2XMLDESC completed (89 rows)
    (IMP) INFO: import of O2XSLTDESC completed (163 rows)
    (IMP) INFO: import of O2XSLTOTR completed (0 rows)
    (IMP) INFO: import of O2XSLTTEXT completed (385 rows)
    (IMP) INFO: import of OBJ_DIFF completed (0 rows)
    (IMP) INFO: import of OXT_PICTURE completed (146 rows)
    (IMP) INFO: import of PACKCHECK_EXCEPT completed (131 rows)
    (IMP) INFO: import of PRICAT_FIELD completed (172 rows)
    (IMP) INFO: import of PRICAT_FIELDT completed (343 rows)
    (IMP) INFO: import of PROP_ELTYP completed (27 rows)
    (IMP) INFO: import of RLB_DB_LB completed (2 rows)
    (IMP) INFO: import of RLB_DB_LBT completed (4 rows)
    (IMP) INFO: import of RLB_DB_PR completed (31 rows)
    (IMP) INFO: import of RLB_DB_PRT completed (62 rows)
    (IMP) INFO: import of RLIB_CONT completed (0 rows)
    (IMP) INFO: import of RLIB_OBJS completed (1160 rows)
    (IMP) INFO: import of RLIB_TREES completed (5 rows)
    (IMP) INFO: import of RSEUINC completed (588382 rows)
    (IMP) INFO: import of RSEUMOD completed (49 rows)
    (IMP) INFO: import of RSEUTAB completed (0 rows)
    (IMP) INFO: import of RSMPCHECK completed (31 rows)
    (IMP) INFO: import of RSMPCHECKT completed (62 rows)
    (IMP) INFO: import of RSMPTEXTSI completed (0 rows)
    (IMP) INFO: import of RSNORMTXT completed (246 rows)
    (IMP) INFO: import of SDBUSRSET completed (0 rows)
    (IMP) INFO: import of SMODILOG completed (125 rows)
    (IMP) INFO: import of SMODILOGI completed (0 rows)
    (IMP) INFO: import of SMODIPROJ completed (0 rows)
    (IMP) INFO: import of SMODISRC completed (492 rows)
    (IMP) INFO: import of SMODISRCI completed (0 rows)
    (IMP) INFO: import of SMODITRAN completed (0 rows)
    (IMP) INFO: import of SMODIUSER completed (0 rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 22, table "SPROXDAT"
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be usedDbSl Trace: invalid sign in BCD number: 1
    DbSl Trace: Error converting decimal:  000000000200303.0 HEX: 0000000002003031 input variable# 12, proc: ## No proc
    DbSl Trace: invalid sign in BCD number: 1
    DbSl Trace: Error converting decimal:  000000000200303.0 HEX: 0000000002003031 input variable# 14, proc: ## No proc
    DbSl Trace: internal error in decimal conversion.
    (IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 8, table "SPROXHDR"
    (IMP) INFO: import of SPROXINDX completed (0 rows)
    (IMP) INFO: import of SPROXKEY completed (0 rows)
    (IMP) INFO: import of SPROXREG completed (9 rows)
    (IMP) INFO: import of SPROXSET completed (0 rows)
    (IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of SPROXTST completed (0 rows)
    (IMP) INFO: import of SRESETLOG completed (0 rows)
    (IMP) INFO: import of SRESETLOG2 completed (0 rows)
    (IMP) INFO: import of SXC_ATTR completed (1045 rows)
    (IMP) INFO: import of SXC_ATTRT completed (1855 rows)
    (IMP) INFO: import of SXC_CLASS completed (1045 rows)
    (IMP) INFO: import of SXC_COCO completed (0 rows)
    (IMP) INFO: import of SXC_EXIT completed (1449 rows)
    (IMP) INFO: import of SXC_FCODE completed (11 rows)
    (IMP) INFO: import of SXC_FCODET completed (23 rows)
    (IMP) INFO: import of SXC_IMPSWH completed (2551 rows)
    (IMP) INFO: import of SXC_SCRN completed (47 rows)
    (IMP) INFO: import of SXC_TABLE completed (0 rows)
    (IMP) INFO: import of SXC_TABLET completed (0 rows)
    (IMP) INFO: import of SXS_ATTR completed (2093 rows)
    (IMP) INFO: import of SXS_ATTRT completed (4020 rows)
    (IMP) INFO: import of SXS_COCO completed (0 rows)
    (IMP) INFO: import of SXS_FCODE completed (64 rows)
    (IMP) INFO: import of SXS_FCODET completed (128 rows)
    (IMP) INFO: import of SXS_INTER completed (2093 rows)
    (IMP) INFO: import of SXS_MLCO completed (616 rows)
    (IMP) INFO: import of SXS_SCRN completed (80 rows)
    (IMP) INFO: import of SXS_SCRNT completed (141 rows)
    (IMP) INFO: import of SXS_TABLE completed (1 rows)
    (IMP) INFO: import of SXS_TABLET completed (2 rows)
    (IMP) INFO: import of SYS_COMP completed (0 rows)
    (IMP) INFO: import of TBPROGREF completed (251 rows)
    (IMP) INFO: import of TBVIEWER completed (0 rows)
    (IMP) INFO: import of TCG01 completed (9 rows)
    (IMP) INFO: import of TCP11 completed (1 rows)
    (IMP) INFO: import of TCP13 completed (0 rows)
    (IMP) INFO: import of TCP17 completed (0 rows)
    (IMP) INFO: import of TGLIF completed (534 rows)
    (IMP) INFO: import of THELPI completed (0 rows)
    (IMP) INFO: import of TMCRT completed (303 rows)
    (IMP) INFO: import of TMEMO completed (0 rows)
    (IMP) INFO: import of TRANSFDESC completed (0 rows)
    (IMP) INFO: import of TRANSFTEXT completed (0 rows)
    (IMP) INFO: import of TRDIRE completed (32350 rows)
    (IMP) INFO: import of TREELOG completed (15990 rows)
    (IMP) INFO: import of W3HTMLT completed (1138 rows)
    (IMP) INFO: import of W3HTRCT completed (162 rows)
    (IMP) INFO: import of W3JSCRT completed (0 rows)
    (IMP) INFO: import of W3MIMET completed (361 rows)
    (IMP) INFO: import of W3OBJLOINF completed (0 rows)
    (IMP) INFO: import of W3PUBDIR completed (0 rows)
    (IMP) INFO: import of W3SERINTP completed (44 rows)
    (IMP) INFO: import of W3SERINTPT completed (63 rows)
    (IMP) INFO: import of W3SERVICET completed (156 rows)
    (IMP) INFO: import of WBCROSSGT completed (126383 rows)
    (IMP) INFO: import of WBCROSSI completed (5654 rows)
    (DB) INFO: disconnected from DB
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job finished with 2 error(s)
    E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808221726
    Regards,
    Vinay

  • AQ_AD_HOC221 Error while executing the infoset query

    Hi Gurus,
    I have created one infoset using LDB PNPCE and added custom fields to IT 0021 and 0041.
    But when I am going to transaction SQ01 and selecting the selection criteria and including the fields from IT 0021
    in the output. Now when I press on the output push button, I am getting the error mesage no. AQ_AD_HOC221
    "Error when generating the report (see long text)."
    I tried to search the forum for this error. I found out that many people are facing this problem, but could not find any exact solution.  One more point, when I am selecting only one custom field from the IT0021, it is working well. But when I am selecting
    more than one custom fields from IT0021, it is giving me the above error.
    Waiting for your replies since I need to solve it urgently.
    Thanks in Advance,
    Raveesh

    Hi Raveesh;
    Usually this error it's because you have a problem in Query Program (SE38) with parameters.
    For example: Duplicated parameter.
    Check it!!
    Regards,
    Mariano

  • InfoSet Query: Syntax Error while generating the program.

    Dear All,
    I have a Query in CRM system which contains an Infoset based on LDB.
    The InfoSet Query throws up a Syntax error while generating the program.
    So, we are not able to change the Infoset using the Infoset Query through SQ01.
    The error is as follows:-
    Syntax error in program "AQZZ==/SAPQUERY/CRM_ACTMON1 ".
    Error in the ABAP Application Program
    The current ABAP program "CL_QUERY_OUTPUT_DEFINITION====CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "AQZZ==/SAPQUERY/CRM_ACTMON1 "
    in include "AQZZ==/SAPQUERY/CRM_ACTMON1 " in
    line 28:
    ""CRMT_REPORT_LOCATORLIST" must be a flat structure. You cannot use int"
    "ernal tables, strings, references, or structures as components. -"
    Please help me arrive at an solution, so that we are able to change the Infoset through the InfoSet Query.
    Awaiting your reply as soon as possible.
    Thanks and Regards,
    Pankaj.

    There is an error in your query, specifically in the definition of CRMT_REPORT_LOCATORLIST. In the short dump (transaction ST22) you will see more details and the exact location of an error if you just scroll down.
    I can't tell more because this problem is specific to your system, to which I have no access. Read the whole dump and look at all the objects mentioned there.

  • Adhoc Query error AQ_AD_HOC 221

    Hi All,
    I have added 7 fields with char1 as value in th it0077 group in the additional filed. My problem is while using the adhoc query output when i select only the infotype 77 fields i am getting the following error
    Mesage ID: AQ_AD_HOC Message number: 221
    Error when generatimg the report (see long Text).
    but when i select any other infotype fields and also 77 infotype fields then its coming fine. I dont know where i m doing wrong.
    I have used LDB PNPCE, and in the coding part of the additional fields i am using rp_provide_from_last.
    Please let me know where i am going wromg.
    Thanks and Regards,
    Salish Nair

    Hi,
    There may be many reasons for that issue. Can you please debugg the code to more deeper. Put break point in perform generate_report in the Fm AQ_INT_SAVE_QUERY_DEFINITION.
    Procedure
    If the selection screen is too large, you need to reduce the number of your selections.
    Make sure that the assigned InfoSet is correct. The name of the assigned InfoSet is stored in the menu option 'Extras -> Template Information'.
    Output at least one field. Otherwise you will not be able to save or generate reports.
    If you do not have this problem, execute the query using the 'Output' function.
    Otherwise, there is an error in the InfoSet Query.
    Thanks & Regards,
    Sandip Biswas

  • Usage of LDB

    I want to try a report where I can use LDB.So tried as follows
    Report zgldb.
    Nodes:pap.
    When I just compile it says 'PAP is not a node of Logical database _S'..
    what does this mean.How to use LDB in a report?
    Thank you

    Dear Gopi,
    Logical Databases
    Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
    However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this. This is particularly useful for programs with type 1.
    Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area.
    Logical Databases - Views of Data
    A logical database provides a particular view of database tables in the R/3 System. It is always worth using logical databases if the structure of the data that you want to read corresponds to a view available through a logical database.
    There are two ways of using a logical database: Either by linking it with an executable program, or by using the function module LDB_PROCESS in any ABAP program.
    When you link a logical database to an executable program, the user can enter values on the selection screen, and the data read by the logical database is passed back to the program using the interface work areas. If you call the logical database using a function module, the selection screen is not displayed. The calling program does not have to provide interface work areas. Instead, it uses special subroutines called callback routines, which are called by the function module and filled with the required data.
    Linking a Logical DB to an Executable Program
    When you link an executable program to a logical database by entering the name of the logical database in the program attributes, the subroutines of the logical database program and the event blocks of the executable program form a modularized program for reading and processing data. The individual processing blocks are called in a predefined sequence by the runtime environment (see the diagram in the section Logical Databases and Contexts). The runtime sequence is controlled by the structure, selections, and PUT statements in the logical database, and by the GET statements in the executable program.
    Selection Screen
    If you specify a logical database in the attributes of an executable program, this affects the standard selection screen of the program. It contains both the selection fields from the logical database and those from the program itself. You can specify which of the logical database selections are relevant for your program, and should therefore appear on the screen, by declaring interface work areas for the relevant nodes.
    Runtime Behavior
    The following list shows the sequence in which the ABAP runtime environment calls the subroutines of the logical database and the event blocks in the executable program. The runtime environment executes a series of processors (selection screen processor, reporting processor). The ABAP code listed below shows the processing blocks that belong to the individual steps.
    Initialization before the selection screen is processed.
    Subroutine:
    FORM INIT
    This subroutine is called once only before the selection screen is first displayed.
    Event block:
    INITIALIZATION.
    This event occurs once only before the selection screen is first displayed.
    PBO of the Selection screen Initialization before each occasion on which the selection screen is displayed (for example, to supply default values for key fields).
    Subroutine:
    FORM PBO.
    This subroutine is called each time the selection screen is sent (before it is displayed).
    Event block:
    AT SELECTION-SCREEN OUTPUT.
    This event is called each time the selection screen is sent (before it is displayed).
    The selection screen is displayed at the presentation server, and the user can enter data in the input fields.
    Input help (F4) or field help (F1) requests.
    Subroutines:
    FORM <par>_VAL.
    FORM <selop>_VAL.
    FORM <selop>-LOW_VAL.
    FORM <selop>-HIGH_VAL.
    If the user requests a list of possible entries for database-specific parameters <par> or selection criteria <selop>, these subroutines are called as required.
    If the user requests field help for these parameters, the subroutines are called with the ending _HLP instead of _VAL.
    Event blocks:
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR <par>.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR <selop>-LOW.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR <selop>-HIGH.
    If the user requests a list of possible entries for database-specific parameters <par> or selection criteria <selop>, these events are triggered as required.
    If the user requests field help for these parameters, the events with the addition ON HELP-REQUEST occurs instead of ON VALUE-REQUEST.
    PAI of the selection screen. Checks to see whether the user has entered correct, complete, and plausible data. Also contains authorization checks. If an error occurs, you can program a user dialog and make the relevant fields ready for input again.
    Subroutines:
    FORM PAI USING FNAME MARK.
    The interface parameters FNAME and MARK are passed by the runtime environment.
    FNAME contains the name of a selection criterion or parameter on the selection screen.
    If MARK = SPACE, the user has entered a simple single value or range selection.
    If MARK = '*', the user has also entered selections on the Multiple Selection screen.
    Using the combination FNAME = '*' and MARK = 'ANY', you can check all entries at once when the user chooses a function or presses ENTER.
    Event blocks:
    AT SELECTION-SCREEN ON <fname>.
    Event for processing a particular input field.
    AT SELECTION-SCREEN ON END OF <fname>.
    Event for processing multiple selections.
    AT SELECTION-SCREEN.
    Event for processing all user input.
    Processing before reading data.
    Subroutine:
    BEFORE EVENT 'START-OF-SELECTION'.
    The logical database can use this subroutine for necessary actions before reading data, for example, initializing internal tables.
    Event block:
    START-OF-SELECTION.
    First event in an executable program after the selection screen has been processed. You can use this event block to prepare the program for processing data.
    Reading data in the logical database and processing in the executable program.
    Subroutine:
    FORM PUT_<node>
    The logical database reads the selected data of the node <node>.
    Event block:
    GET <table> [LATE].
    This event is triggered by the PUT statement in the above subroutine. This event block allows you to process the data read for <node> in the corresponding interface work area.
    Processing after reading data.
    Subroutine:
    AFTER EVENT 'END-OF-SELECTION'.
    The logical database can use this subroutine for necessary actions after reading data, for example, releasing memory space.
    Event block:
    END-OF-SELECTION.
    Last reporting event. You can use this event block to process the temporary dataset that you have created (for example, sort it).
    If a list was generated during the above steps, the list processor in the runtime environment takes control of the program and displays the list.
    Suppose TABLE1 is the root node and TABLE2 is its only subordinate node in a logical database. The processing steps for reading and processing data would then have the following hierarchical order:
    START-OF-SELECTION.
      FORM PUT_TABLE1.
      GET TABLE1.
        FORM PUT_TABLE2.
        GET TABLE2.
      GET TABLE1 LATE.
    END-OF-SELECTION.
    Authorization Checks in Logical Databases
    It makes sense to use authorization checks using the AUTHORITY-CHECK statement in the following subroutines in the database program or event blocks of the executable program:
    Subroutines in the database program:
    - PAI
    - AUTHORITY_CHECK_<table>
    Event blocks in the executable program:
    - AT SELECTION-SCREEN
    - AT SELECTION-SCREEN ON <fname>
    - AT SELECTION-SCREEN ON END OF <fname>
    - GET <table>
    Whether you place the authorization checks in the database program or in the executable program depends on the following:
    The structure of the logical database.
    For example, you should only check authorizations for company code if you actually read lines containing the company code at runtime.
    Performance
    Avoid repetitive checks (for example, within a SELECT loop).
    The separation of database access and application logic allows you to program all of your authorization checks centrally in the logical database program. This makes it easier to maintain large programming systems.
    Calling a Logical Database Using a Function Module
    From Release 4.5A it is possible to call logical databases independently from any ABAP program. Previously it was only possible to link a logical database to an executable program, in which the processing blocks of the logical database and the program were controlled by the ABAP runtime environment.
    To call a logical database from another program, use the function module LDB_PROCESS. This allows you to use the logical database as a routine for reading data. You can call more than one logical database from the same program. You may also call the same logical database more than once from the same program. In the past, it was only possible to use a logical database more than once or use more than one logical database by calling a further executable program using SUBMIT. These programs had to be linked to the corresponding logical database, and the data had to be passed to the calling program using ABAP memory or a similar technique.
    When you call a logical database using the function module LDB_PROCESS, its selection screen is not displayed. Instead, you fill the selections using the interface parameters of the function module. The logical database does not trigger any GET events in the calling program, but passes the data back to the caller in callback routines. Calling a logical database using LDB_PROCESS thus decouples the actual data retrieval from the preceding selection screen processing and the subsequent data processing.
    There is no need to adapt a logical database for use with LDB_PROCESS, except in the following cases: If you do not adapt a logical database, it is not possible to use the function module to call the same logical database more than once. The PAI subroutine is not called when you use LDB_PROCESS. This means that none of the checks for selections programmed in it are performed. You can work around these restrictions by including the subroutines LDB_PROCESS_INIT and LDB_PROCESS_CHECK_SELECTIONS in the database program.
    Runtime Behavior
    The subroutines in the logical database are called in the following sequence when you call the function module LDB_PROCESS:
    LDB_PROCESS_INIT
    INIT
    LDB_PROCESS_CHECK_SELECTIONS
    PUT <node>.
    None of the subroutines used to process the selection screen when you link the logical database to an executable program are called, neither does the runtime environment trigger any reporting events in the calling program. Instead, the PUT statements in the logical database trigger actions in the function module that call callback routines in the calling program. In other words, the function module catches the events that are otherwise processed by the runtime environment.
    Parameters of LDB_PROCESS
    The function module has the following import parameters:
    LDBNAME
    Name of the logical database you want to call.
    VARIANT
    Name of a variant to fill the selection screen of the logical database. The variant must already be assigned to the database program of the logical database. The data is passed in the same way as when you use the WITH SELECTION-TABLE addition in a SUBMIT statement.
    EXPRESSIONS
    In this parameter, you can pass extra selections for the nodes of the logical database for which dynamic selections are allowed. The data type of the parameter RSDS_TEXPR is defined in the type group RSDS. The data is passed in the same way as when you use the WITH FREE SELECTION addition in a SUBMIT statement.
    FIELD_SELECTION
    You can use this parameter to pass a list of the required fields for the nodes of the logical database for which dynamic selections are allowed. The data type of the parameter is the deep internal table RSFS_FIELDS, defined in the type group RSFS. The component TABLENAME contains the name of the node and the deep component FIELDS contains the names of the fields that you want to read.
    The function module has the following tables parameters:
    CALLBACK
    You use this parameter to assign callback routines to the names of nodes and events. The parameter determines the nodes of the logical database for which data is read, and when the data is passed back to the program and in which callback routine.
    SELECTIONS
    You can use this parameter to pass input values for the fields of the selection screen of the logical database. The data type of the parameter corresponds to the structure RSPARAMS in the ABAP Dictionary. The data is passed in the same way as when you use the WITH SELECTION-TABLE addition in a SUBMIT statement.
    If you pass selections using more than one of the interface parameters, values passed in SELECTIONS and EXPRESSIONS overwrite values for the same field in VARIANT.
    Read Depth and Callback Routines
    When you link a logical database with an executable program, the GET statements determine the depth to which the logical database is read. When you call the function module LDB_PROCESS, you determine the depth by specifying a node name in the CALLBACK parameter. For each node for which you request data, a callback routine can be executed at two points. These correspond to the GET and GET LATE events in executable programs. In the table parameter CALLBACK, you specify the name of the callback routine and the required execution point for each node. A callback routine is a subroutine in the calling program or another program that is to be executed at the required point.
    For the GET event, the callback routine is executed directly after the data has been read for the node, and before the subordinate nodes are processed. For the GET_LATE event, the callback routine is processed after the subordinate nodes have been processed.
    The line type of the table parameter CALLBACK is the flat structure LDBCB from the ABAP Dictionary. It has the following components:
    LDBNODE
    Name of the node of the logical database to be read.
    GET
    A flag (contents X or SPACE), to call the corresponding callback routine at the GET event.
    GET_LATE
    A flag (contents X or SPACE), to call the corresponding callback routine at the GET LATE event.
    CB_PROG
    Name of the ABAP program in which the callback routine is defined.
    CB_FORM
    Name of the callback routine.
    If you pass an internal table to the CALLBACK parameter, you must fill at least one of the GET or GET_LATE columns with X for each node (you may also fill both with X).
    A callback routine is a subroutine that must be defined with the following parameter interface:
    FORM <subr> USING <node> LIKE LDBCB-LDBNODE
                      <wa>   [TYPE <t>]
                      <evt>
                      <check>.
    The parameters are filled by the function module LDB_PROCESS. They have the following meaning:
    <node> contains the name of the node.
    <wa> is the work area of the data read for the node. The program that calls the function module LDB_PROCESS and the program containing the callback routine do not have to declare interface work areas using NODES or TABLES. If the callback routine is only used for one node, you can use a TYPE reference to refer to the data type of the node in the ABAP Dictionary. Only then can you address the individual components of structured nodes directly in the subroutine. If you use the callback routine for more than one node, you cannot use a TYPE reference. In this case, you would have to address the components of structured nodes by assigning them one by one to a field symbol.
    <evt> contains G or L, for GET or GET LATE respectively. This means that the subroutine can direct the program flow using the contents of <evt>.
    <check> allows the callback routine to influence how the program is processed further (but only if <evt> contains the value G). The value X is assigned to the parameter when the subroutine is called. If it has the value SPACE when the subroutine ends, this flags that the subordinate nodes of the logical database should not be processed in the function module LDB_PROCESS. This is the same as leaving a GET event block using CHECK in an executable program. If this prevents unnecessary data from being read, it will improve the performance of your program.
    Exceptions of LDB_PROCESS
    LDB_ALREADY_RUNNING
    A logical database may not be called if it is still processing a previous call. If this occurs, the exception LDB_ALREADY_RUNNING is triggered.
    LDB_NOT_REENTRANT
    A logical database may only be called repeatedly if its database program contains the subroutine LDB_PROCESS_INIT, otherwise, this exception is triggered.
    LDB_SELECTIONS_NOT_ACCEPTED
    Error handling in the subroutine LDB_PROCESS_CHECK_SELECTIONS of the database program can trigger this exception. The error message is placed in the usual system fields SY-MSG....
    For details of further exceptions, refer to the function module documentation in the Function Builder.
    Example
    TABLES SPFLI.
    SELECT-OPTIONS S_CARR FOR SPFLI-CARRID.
    TYPE-POOLS: RSDS, RSFS.
    DATA: CALLBACK TYPE TABLE OF LDBCB,
          CALLBACK_WA LIKE LINE OF CALLBACK.
    DATA: SELTAB TYPE TABLE OF RSPARAMS,
          SELTAB_WA LIKE LINE OF SELTAB.
    DATA: TEXPR TYPE RSDS_TEXPR,
          FSEL  TYPE RSFS_FIELDS.
    CALLBACK_WA-LDBNODE     = 'SPFLI'.
    CALLBACK_WA-GET         = 'X'.
    CALLBACK_WA-GET_LATE    = 'X'.
    CALLBACK_WA-CB_PROG     = SY-REPID.
    CALLBACK_WA-CB_FORM     = 'CALLBACK_SPFLI'.
    APPEND CALLBACK_WA TO CALLBACK.
    CLEAR CALLBACK_WA.
    CALLBACK_WA-LDBNODE     = 'SFLIGHT'.
    CALLBACK_WA-GET         = 'X'.
    CALLBACK_WA-CB_PROG     = SY-REPID.
    CALLBACK_WA-CB_FORM     = 'CALLBACK_SFLIGHT'.
    APPEND CALLBACK_WA TO CALLBACK.
    SELTAB_WA-KIND = 'S'.
    SELTAB_WA-SELNAME = 'CARRID'.
    LOOP AT S_CARR.
      MOVE-CORRESPONDING S_CARR TO SELTAB_WA.
      APPEND SELTAB_WA TO SELTAB.
    ENDLOOP.
    CALL FUNCTION 'LDB_PROCESS'
         EXPORTING
              LDBNAME                     = 'F1S'
              VARIANT                     = ' '
              EXPRESSIONS                 = TEXPR
              FIELD_SELECTION             = FSEL
         TABLES
              CALLBACK                    = CALLBACK
              SELECTIONS                  = SELTAB
         EXCEPTIONS
              LDB_NOT_REENTRANT           = 1
              LDB_INCORRECT               = 2
              LDB_ALREADY_RUNNING         = 3
              LDB_ERROR                   = 4
              LDB_SELECTIONS_ERROR        = 5
              LDB_SELECTIONS_NOT_ACCEPTED = 6
              VARIANT_NOT_EXISTENT        = 7
              VARIANT_OBSOLETE            = 8
              VARIANT_ERROR               = 9
              FREE_SELECTIONS_ERROR       = 10
              CALLBACK_NO_EVENT           = 11
              CALLBACK_NODE_DUPLICATE     = 12
              OTHERS                      = 13.
    IF SY-SUBRC <> 0.
      WRITE: 'Exception with SY-SUBRC', SY-SUBRC.
    ENDIF.
    FORM CALLBACK_SPFLI USING NAME  TYPE LDBN-LDBNODE
                              WA    TYPE SPFLI
                              EVT   TYPE C
                              CHECK TYPE C.
      CASE EVT.
       WHEN 'G'.
          WRITE: / WA-CARRID, WA-CONNID, WA-CITYFROM, WA-CITYTO.
          ULINE.
        WHEN 'L'.
          ULINE.
      ENDCASE.
    ENDFORM.
    FORM CALLBACK_SFLIGHT USING NAME  TYPE LDBN-LDBNODE
                                WA    TYPE SFLIGHT
                                EVT   TYPE C
                                CHECK TYPE C.
      WRITE: / WA-FLDATE, WA-SEATSOCC, WA-SEATSMAX.
    ENDFORM.
    The data structure in a logical database is hierarchical. Many tables in the R/3 System are linked to each other using foreign key relationships. Some of these dependencies form tree-like hierarchical structures. Logical databases read data from database tables that are part of these structures.
    Tasks of Logical Databases
    As well as allowing you to read data from the database, logical databases also allow you to program other tasks centrally, making your application programs less complicated. They can be used for the following tasks:
    Reading the same data for several programs.
    The individual programs do not then need to know the exact structure of the relevant database tables (and especially not their foreign key relationships). Instead, they can rely on the logical database to read the database entries in the right order during the GET event.
    Defining the same user interface for several programs.
    Logical databases have a built-in selection screen. Therefore, all of the programs that use the logical database have the same user interface.
    Central authorization checks
    Authorization checks for central and sensitive data can be programmed centrally in the database to prevent them from being bypassed by simple application programs.
    Improving performance
    If you want to improve response times, logical databases permit you to take a number of measures to achieve this (for example, using joins instead of nested SELECT statements). These become immediately effective in all of the application programs concerned and save you from having to modify their source code.
    A program-specific selection screen is defined at the beginning of the program. This requires the TABLES statement. Next, the required variables are defined for the interface.
    The internal table CALLBACK is filled so that various callback routines are called in the program for the two nodes SPFLI and SFLIGHT. For SPFLI, the routine is to be called for GET and GET_LATE, for SFLIGHT, only at the GET event.
    The internal table SELTAB is filled with values for the node SPFLI from the selection table S_CARR from the program-specific selection screen.
    The program then calls the function module LDB_PROCESS with these parameters.
    The subroutines CALLBACK_SPFLI and CALLBACK_SFLIGHT serve as callback routines. The interface parameter WA is fully typed, so you can address the individual components of the work areas. The events GET and GET LATE are handled differently in CALLBACK_SPFLI.
    Regards,
    Rajesh K Soman
    <b>Please reward points if found helpful</b>

  • Unicode error in program

    I am getting the following error when I do a syntax check when using a PNP logical database with unicode checkbox checked in attributes.  Can someone give me a solution to avoid that.   Thanks in advance
    In unicode programs the - cannot appear in names as it does here in pnp-sw-found
    regards
    srilatha

    Hello Srilatha,
    I just tried this in a unicode system and I got no error at all.
    However as far as I remember this is never an error but if at all a warning. And you can simply ignore it as it comes from the LDB PNP.
    Changing this old variables, structures and macro names is not possible as then ALL customer reports would have to be changed also. And I think this is something SAP will never burden on their customers.
    Regards,
    Michael

  • Syntax error in Logical database created by copying standard PGQ

    Hi guys.
    I created a logical database ZMPQ_PGQ using the copy option from SE36 with the input PGQ (logical database used by QA33).
    But it showing some syntax error Field "PGQ_SP" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement.
    How to resolve this?
    Thanks in advance.

    When checking the syntax of the LDB source code, go to the location of the syntax error (in include DBZMPQ_PGQSXXX), and change all internal table references of PGQ_SP to ZMPQ_PGQ_SP.

  • LDB CMC with LDB_PROCESS FM ?

    Dear All,
    1. I'm calling the Function Module LDB_PROCESS in my Program.
    2. I'm passing CMC LDB to the above FM.
    3. I've built the Necessary params to pass onto the FM.
    4. But my Form is not getting triggered.
    Please let me know the reason !
    Enclosed is the code :
    Data: wa_mastb like mastb.
    SELECT-OPTIONS: s_matnr for wa_mastb-matnr.
    DATA: CALLBACK    TYPE TABLE OF LDBCB,
                CALLBACK_WA LIKE LINE  OF CALLBACK.
    DATA: gt_SELTAB  TYPE TABLE OF RSPARAMS,
                gwa_SELTAB LIKE LINE  OF gt_SELTAB.
    CLEAR CALLBACK_WA.
    CALLBACK_WA-LDBNODE     = 'MASTB'.
    CALLBACK_WA-GET         = 'X'.
    CALLBACK_WA-GET_LATE    = ' '.
    CALLBACK_WA-CB_PROG     = SY-REPID.
    CALLBACK_WA-CB_FORM     = 'CALL_MASTB'.
    APPEND CALLBACK_WA TO CALLBACK.
    gwa_SELTAB-KIND    = 'S'.
    gwa_SELTAB-SELNAME = 'MATNR'.
    Loop at s_matnr.
      MOVE-CORRESPONDING s_matnr to gwa_SELTAB.
      append gwa_SELTAB to gt_seltab.
    endloop.
    START-OF-SELECTION.
    CALL FUNCTION 'LDB_PROCESS'
      EXPORTING
        LDBNAME                           = 'CMC'
    *   VARIANT                           =
    *   EXPRESSIONS                       =
    *   FIELD_SELECTION                   =
    *   DYN_NODE_TYPES                    =
      TABLES
        CALLBACK                          = CALLBACK
        SELECTIONS                        = gt_SELTAB.
    IF SY-SUBRC <> 0.
    Write:/ 'Error in the Call of the LDB FM'.
    ENDIF.
    end-of-SELECTION.
    FORM CALL_MASTB USING PD_NODE LIKE LDBN-LDBNODE
                                                  PD_WORKAREA like mastb
                                                  PD_MODE     TYPE C
                                                  PD_SELECTED TYPE C.
    data: ls_mastb like mastb.
      CASE PD_NODE.
        WHEN 'MASTB'.
          LS_mastb = PD_WORKAREA.
          write:/ ls_mastb-matnr, ls_mastb-werks.
      ENDCASE.
    ENDFORM.
    Regards,
    Deepu.K

    Hi!
    for CMC LDB you must add parameter:
    PARAMETERS :
             datuv LIKE stko-datuv  DEFAULT sy-datum.
    and fill it
    CLEAR gwa_seltab.
    gwa_seltab-kind    = 'P'.
    gwa_seltab-selname = 'DATUV'.
    gwa_seltab-sign    = 'I'.
    gwa_seltab-option  = 'EQ'.
    gwa_seltab-low = datuv .
    APPEND gwa_seltab TO gt_seltab.

Maybe you are looking for

  • Safari on mac pro keeps crashing..

    It crashes whenever I open my school's login webpage....and is totally fine with all other websites.... I've already tried deleting cache in the safari folder, but it made no difference. Thanks a lot!! Process:         WebProcess [505] Path:         

  • Number pad/arrow keys

    I was trying out the arrow keys in the built in laptop keyboard on a program and found that the numlk does not light up but it does on my desktop. Is there a way to use the numlk in the application i am using?

  • DNS, site question

    I am tinkering with Snow Leopard Server as a web/file/vpn server. I am not able to get it working however, and wondered if someone could help me out. I am a noob to mac as a web server, but have some experience in dns and apache hosting in the tradit

  • My itunes telling me to pay for an app that i didnt want, my itunes telling me to pay for an app that i didnt want

    my itu nes keep asking to pay for an app that i didnt want

  • Window views not staying put

    I open a window and set for Icon View, set the size etc., then check Always Open In Icon View (in this example), I reboot and the icon size is bigger or sometimes it's in list view! Repaired permissions, ran Cocktail, dumped the finder prefs, still n