Copy LDB's

Hi,
Is it suggestable to make a copy of LDB's and do the changes in HR..?
please let me know the reasons..?
Regards,
Anil

I want to take some of the content and add into a movie/slide show I am making but I can not get it into a file or form that will let me save it and then add it to my movie.
Is it possible? Yes but I don't recommend re using content that was burned to DVD even if it isn't copy protected and here's why ..... Video already burned to DVD-R is highly compressed into mpeg 2 normally and there will be some loss in quality when converting it back to QT for use with i-apps (which may be possible with such 3rd party apps as visual hub, mpeg streamclip, and Dvdxdv (see links below):
http://www.dvdxdv.com/NewFolderLookSite/Products/DVDxDV.products.htm
http://www.apple.com/downloads/macosx/video/mpegstreamclip.html
http://www.techspansion.com/visualhub/
http://docs.info.apple.com/article.html?artnum=42724
http://discussions.apple.com/thread.jspa?messageID=6384941&#6384941
Hope this helps but if not just come on back.
Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in this topic. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information above at your own discretion.
Message was edited by: SDMacuser

Similar Messages

  • Help on copying LDB

    hi all,
              there is a tcode gr55 for which there is a std program and it uses a LDB .now the problem is can a report program with LDB copied from one client to other,if yes wat problems can b arised?
    any help wud be gratefull.

    Hi Naren,
    Chek with the [Copy Logical Database|Logical data base copy].
    hope it helps you.
    Regards!

  • Facing Problem while Debugging a custom report using LDB

    Hi Gurus,
    I have requirement to modify a custom report program related to FI. This program used Logical database ZDF ( Copied original DDF) for data fetching.
    when i am trying to see the data in debugging mode, its not allowing to check in start-of-selection event. only in the initialization & end-of-selection i could able to debug.
    when i put breakpoint in initialization, it is allowing to see the flow till a Get Event occurs in the code, once a Get event occur the debugger is coming out and displaying the report.
    If anybody faced this kind of problem when debugging a report using LDB, please share how you resolved it. If there are any other ways to debug a program of this kind please help me.
    Thanks,
    Nanda

    Hi Amith,
    I checked that way also, i put break point in database program of the copied LDB, but its not allowing to check the flow in that program also.
    Please suggest any other ways.
    Thanks,
    Nanda

  • LDB short-dump

    Hi,
    My requirement is as below.
    We need to combine 3 multilevel reports into one multilevel report. The 3 multilevel reports transactions are 1)IL07 2)IW30 3)IE07
    So I have copied IL07 report into our Z report and then copying the other multilevel reports into the same Z report . Each standardreport has LDB(Logical database) maintained. In the LDB, nodes are created for Main objects and sub objects.
    If we see LDB name called "TPI" , it has Functional location at main level and remaining objects at sublevel. Now in functional location we have Notification as sub object. And for Notification we have other LDB called QMI in which Notification is maintained at Mianlevel and other objects are at sublevel. Now I need to combine these LDBs into one. So I have copied LDB into z LDB and then adding the same nodes for notification that are in QMI ldb .
    we have partner maintained for Both Functional Location and Notification at their respective level. And I have check boxes for the sub objects on the selection screen so that I user can select whichever he wants to view.
    The problem is If I select both the partners ( I mean for functional Location and Notification) then it is giving dump. If I select only one of them then it is not giving dump. and data is getting printed under their respective nodes.
    The DUMP I am getting is MESSAGE_TYPE_X .
    Please help if you have worked on LDBs.
    Note that : I have installed latest GUI patch levels and all . This is not related to any GUI upgrade or some thing , I am sure. So please dont give GUI related solutions.
    Regards,
    Nageswar

    Also check on AT SELECTION-SCREEN OUTPUT. You`re not selecting any of them too...
    Checkout this code ..
    I declare PNP in attributes and AT SELECTION-SCREEN OUTPUT.
      PNPTIMR5 = ' '.
      PNPTIMR3 = 'X'. ( Just comment it or give error message )
    its giving short dump ,if I try to do the same thing you describe in your post !
    Hope this’ll help you
    Thanks
    Saquib

  • Facing Problem while Displaying Russian words using HTP.TableData

    Hi,
    We are storing russian words in DB.While displaying these words, it is not displaying proerly.we are using "HTP.TableData" to display russian characters in the front end.Please suggest the solution to display russian words proeprly

    Hi Amith,
    I checked that way also, i put break point in database program of the copied LDB, but its not allowing to check the flow in that program also.
    Please suggest any other ways.
    Thanks,
    Nanda

  • COPY OF MD47 BUT NO LDB

    HI There.
    I need to make a copy of the Transaction MD47 and in the process make changes to the selct paarmeters and include some more and code corespodingly.
    but the LDB involved happens to ahve no structure! And i cannot find the selection screen absolutely anywhere?
    can anyone guide me on how to go about it?
    i ahve tried looking at the forums already but somehow didnt come across this:)
    let me know.

    Did you think about doing a modification rather than a copy of that transaction? I know a modification is something you shouldn't do unless absolutely necessary and it also depends on the amount of changes you plan to do. But copying a complete transaction will cause your copy to be no longer supported by SAP. Meaning any Note or fix in a support package will only fix the problems in the original transaction but those errors will still exist in your copy. And with the modification assistant even a support pack application is not really a big problem, just some work needed during the SPAU adjustment.
    You can also check, if there are enhancements points available in the coding that you could hook into which wouldn't be a modification either.
    Regards,
    Michael

  • Access DB (& .ldb file) does not close after crystal reports

    Post Author: mgold
    CA Forum: Crystal Reports
    Access DB (& .ldb file) does not close after crystal reports
    Hi! We have a VB application using Crystal Reports 6 that has worked successfully on hundreds of systems for over 10 years. Now, on one network, the application and access database does not close. It seems to hang on the [.Close] command.
    When we open the application an peruse the screens without opening up a report (using crystal reports), the application and access db closes fine. But as soon as we run a report and then close the report and try to close the application, the access db does not close. Many of the screens open the db and grab data from the access db, but it's only after running crystal reports that we have this problem. (Please see more information below.)
    Setup: Application and data (access 97 db) reside on a server in the same folder, but application shortcut is kicked off on client PC. Kicking off the shortcut on the client PC means that the image/process runs on the client PC (not on the server). In this problem case, the application shortcut is on a Windows XP Pro Version 2002 SP2 PC with the app & data on a Windows 2003 server. Users are local Admins on their PCs with "Full Control"over the directory and files on the server where the data (access 97 db) resides. This type of setup is typical and has worked without any problems for clients.
    The application is written in Visual Basic, using Crystal Reports 6 (using DAO). We close the recordset, set it to zero and then it hangs on closing the db (.Close command).
    A few key pieces of information:
    - The application closes fine if the app & data (access 97 db) are on a local PC. This includes closing fine if the application is run directly on the Windows 2003 server where the data is stored.
    - It worked on this client's network until sometime in the last few weeks.
    - One thing that changed is that the company is using VMWare on its servers. Not sure if they started using VMWare at the same time as it started failing. This may be unrelated. Possibly other things changed, but can't get any more information ... yet.
    - It works fine running the application from a Windows Vista PC with a user who is a domain admin.
    - The access db and application hang for about 10-20 minutes and then eventually closes. It appears that somehow
    Crystal Reports is keeping the db open, but I'm not sure why.The application doesn't quit and the database doesn't close even if I try to end the task with the Task Manager.
    - The Crystl32.ocx version being used is 8.0.0.4 (if that matters).
    - I copied 6 month old program files and database files to a test folder on the Windows 2003 server. It fails using these files that worked fine 6 months ago.
    Any ideas or help would be greatly appreciated! If you know of another good place to post this, please let me know.
    Thanks!
    - Mark

    Crystal doesn't support tables in HTML interpretation. 
    You can probably work your way around this by doing Replace() calls on the relevant tags.
    See:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233313337333033383334%7D.do
    The supported HTML tags are:
    " html
    " body
    " div (causes a paragraph break)
    " tr (causes only a paragraph break; does not
    preserve column structure of a table)
    " span
    " font
    " p (causes a paragraph break)
    " br (causes a paragraph break)
    " h1 (causes a paragraph break, makes the font bold
    & twice default size)
    " h2 (causes a paragraph break, makes the font bold
    & 1.5 times default size)
    " h3 (causes a paragraph break, makes the font bold
    & 9/8 default size)
    " h4 (causes a paragraph break, makes the font bold)
    " h5 (causes a paragraph break, makes the font bold
    & 5/6 default size)
    " h6 (causes a paragraph break, makes the font bold
    & 5/8 default size)
    " center
    " big (increases font size by 2 points)
    " small (decreases font size by 2 points if it's 8
    points or larger)
    " b
    " i
    " s
    " strike
    " u
    The supported HTML attributes are:
    " align
    " face
    " size
    " color
    " style
    " font-family
    " font-size
    " font-style
    " font-weight

  • 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

  • Want to have own selection screen  in HR-ABAP report using LDB

    Hi experts,
            I am working on HR-ABAP report using LDB pnp and infotypes..But, here we get the built in selection criterion..but I want my own selection screen to be displayed..whats the solution for this??? Is it possible to create my own selection screen instead of default one..and how???
    Please help me..its very urgent..

    Hi,
    chk this out:
    Create Report Categories                                                                               
    In this step, you define the report categories and determine the layout
       of the standard selection screen for these report categories. You can 
       create report categories for programs or queries that are based on the
       PNP or PNPCE logical databases.                                                                               
    The definition of report categories is divided into two sections:                                                                               
    o   In the Change Report Category view, you define general attributes 
           such as sort order, input fields for date, and so on.                                                                               
    o   In the Change Selection Criteria view, you define which selection 
           fields of the logical database should be avaliable on the selection
           screen.                                                                               
    Example                                                                               
    You want to set up your system so that your employees can only start  
       evaluation reports for Payroll if they use a payroll area. Within a   
       payroll area, you should be able to select according to personnel     
       number. Additional selection criteria should not be possible and you  
       should not be allowed to enter a sort sequence.                       
    Standard settings                                                                               
    The standard system already contains report categories. You can find the 
    attributes of the report categories in the table.                                                                               
    Note the following five report categories in particular:                                                                               
    o   Report category ' ' is the SAP default report category for     
        programs that are based on the PNP logical database.                                                                               
    o   Report category PNPCE is the SAP default category for programs that  
        are based on the PNPCE logical database.                                                                               
    o   Report category '00000000' is the customer-specific default category 
        for programs that are based on the PNP logical database.                                                                               
    o   Report category '0PNPCE' is the customer-specific default category   
        for programs that are based on the PNPCE logical database.                                                                               
    o   Report category __X2001 is the default category for Queries  that    
        are based on an InfoSet of the PNP LDB.                                                                               
    o   Report category QUEPNPCE is the default category for queries that    
        are based on an InfoSet of the PNPCE LDB.                                                                               
    The default report categories are used when a report is called if    
        the report has not been assigned a report category.                  
    Parameters and Options for Report Categories of the LDB PNP and PNPCE  
    Parameters and Options in Screen Area General Data                     
       If you activate this parameter, you can only enter data on the data
       selection period if you use reports that have been assigned. The   
       same date entries are then used for the person selection as for the
       date selection.                                                                               
    o   Matchcode allowed                                                  
       If you activate this parameter, you have use of a Matchcode        
       pushbutton (search help) if you use reports that have been assigned.
       This pushbutton enables you to perform the person selection.                                                                               
    o   Sort allowed                                                       
       If you activate this parameter, you have use of a Sort pushbutton if
       you use report that have been assigned. This pushbutton enables you
       to define a sort order before you execute the report.                                                                               
    o   Organizational structure allowed                                   
       If you activate this parameter, you have use of an Org.Structure   
       pushbutton if you use reports that have been assigned. This        
       pushbutton enables you to perform the person selection.            
       Note:                                                              
       For more information about these options, see the online           
       documentation under this path:                                     
       SAP Library -> Human Resources -> Reporting in Human Resources     
       Management -> Standard HR Reports -> Report Selection Screen in    
       Human Resources Management.                                                                               
    Parameters and Options in Screen Areas Data Selection Period/Person    
    Selection Period/Payroll Area/Period/Year                                                                               
    o   Options for data selection period and person selection period (key 
        date and so on)                                                    
        Here you define which options for date and person selection are    
        available for reports that have been assigned.                                                                               
    o   Options for payroll area/period/year                               
        Here you define which options for selection using payroll          
        area/period/year are available for reports that have been assigned.                                                                               
    Parameters and Options in Screen Area Selection View                                                                               
    o   Type/Name                                                          
        This parameter enables you to use selection views to define report 
        categories. You use the selection view selected here to determine  
        which fields are available in the Dynamic Selectionsy.                                                                               
    Note:                                                              
        You create selection views for the PNP and PNPCE logical databases 
        in the Object Navigator (SE80):                                    
        1. Start the Object Navigator (SE80)                               
        2. Choose Workbench -> Edit Object.                                
        3. Choose the More... tab page and the Selection view on this tab  
        page.                                                              
        4. Choose Create.                                                  
        5. In the Create Selection View dialog box, choose the For any     
        tables option.                                                     
        6. In the Name of view field, enter a name for your selection view.
        7. In the Tables dialog box, enter the name of the table from which
        you want to use fields.                                            
        Note:                                                              
        When you enter the table name, observe the naming convention in    
        Personnel Administration:                                          
        Infotype number: nnnn -> table name: PAnnnn                        
        8. Choose Continue.                                                
        9. In the Functional groups area, define functional groups by      
        assigning a name and a number.                                     
        10. Assign fields from the selected tables to the functional groups
        by entering the number of the desired functional group in front of 
        each field.                                                        
        11. Save your entries.                                                                               
    For more information about adjusting the dynamic selections using 
    your own selection views, see the online documentation under the  
    following menu path:                                              
    SAP Library -> Human Resources -> Reporting in Human Resources    
    Management -> HR Standard Reports -> Report Selection Screen in   
    Human Resources Management -> Enhancing the Selection Screen -    
    Dynamic Selections.                                                                               
    If you do not want to offer dynamic selections, make the following
    settings:                                                                               
    -   LDB PNP: In the Selection view field, enter PNP_NO_FREE_SEL.  
    -   LDB PNPCE: Leave the Selection view field empty.                                                                               
    Parameters and Options in Screen Area Data Selection Period/Person   
    Selection Period/Payroll Area/Period/Year                                                                               
    o   Available input parameters, date or period entry (today, key date,
       all, and so on), and standard value.                             
       Using the Standard value option, you define which of the selected
       options is shown.                                                                               
    Parameters and Options in Screen Area CE Selection Fields                                                                               
    o   CE selection fields (external person ID, grouping reason, grouping
       value)                                                           
       Using the options in this area, you define whether the external  
       person Id, grouping reason, or grouping value are available on the
       selection screen.                                                
       Note:                                                            
       These parameters are only relevant for you if you implement      
       Concurrent Employment (see also note 517071).                                                                               
    Parameters and Options in Screen Area Selection view                                                                               
    o   Dynamic selections as dialog box                                  
        If this switch is set, you can call the dynamic selections as a   
        dialog box.                                                                               
    o   Dynamic selections active                                         
        If this switch is set, the dynamic selections of the logical      
        database are active at the start of the report.                                                                               
    Note that the following combinations are possible for the last two
        options mentioned:                                                                               
    Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/inactive         
        Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/active           
        Dyn.Sel. as dialog box/Dyn.Sel. active: active/inactive                                                                               
    Activities                                                                               
    1.  Choose Edit -> New entries.                                                                               
    2.  Enter an abbreviation and a long text for the report category.         
        The customer name range for report categories is 0-9.                                                                               
    3.  Select the For the PNPCE logical database checkbox, if you want to     
        create a report category for a program or for queries of the PNPCE     
        logical database.                                                                               
    4.  In the General Data screen area, choose the desired options.           
        If you want to use selection IDs, you must have first created and      
        grouped selection Ids. The IMG path to do this is given in the         
        parameter description section.                                                                               
    5.  In the Data selection period/person selection period or Selection      
        period screen area, choose the desired options.                                                                               
    6.  In the Selection view screen area, choose the desired options.                                                                               
    7.  In the CE selection fields screen area, choose the desired (only       
        possible for report categories of the LDB PNPCE).                                                                               
    8.  Save your entries.                                                                               
    9.  Choose the subactivity Permitted selection criteria.                                                                               
    10. Choose Edit -> New entries.                                                                               
    11. In the Select option field, use the input help to select each field    
        that should be available on the selection screen.                                                                               
    12. Select the checkbox in the 1.page column, if you want this selection   
        field to be available directly when you call the selection screen.                                                                               
    Further notes                                                                               
    13. If you want to copy entries, you still have to enter the selection     
        parameters again in the subsequent screen.                                                                               
    o   If you create the report category '000000000', a selection screen is   
        generated according to report category '00000000'for all reports for   
        which a report category has not explicitly been assigned.                                                                               
    Assign Report Categories                                                                               
    In this step, you assign a report category to your reports.                                                                               
    Example                                                                               
    You have created your own report, for example ZPCTEST1, and would like
        it to have the selection screen that corresponds to that of the       
        evaluation report for Payroll, which is assigned to report category   
        '__M00001'.                                                           
        Assign report category '__M00001' to the report.                                                                               
    Requirements                                                                               
    You must have defined the Report Categories.                                                                               
    Standard settings                                                                               
    SAP Standard Reports:                                                                               
    In the standard system, reports are assigned a report category. If you
        want to override these assignments, perform the activities described  
        here. If you want to assign report categories to standard reports using
        SE38, this represents a modification.                                                                               
    Customer-Specific Reports:                                                                               
    For reports you have developed yourself, you can either assign report 
        categories by performing the activities described here or directly in SE38.
    Recommendation                                                                               
    Only assign a report category if you have created your own reports or if  
    the selection screens in the standard system do not meet your             
    requirements.                                                                               
    Activities                                                                               
    1.  Choose Edit -> New entries.                                                                               
    2.  Perform the required assignment using the Program name and Report     
       category fields.                                                                               
    3.  Save your entries.                   
    reward if helpful
    regards,
    madhumitha

  • LDB selection screen Change

    hi i have a unusual requirement
    Presently in one of my HR reports I am using 'PCH' LDB.
    In the selection screen we have the object ID which is defined in standard program with no-intervals like this.
    SELECT-OPTIONS:
    PCHOBJID FOR OBJEC-OBJID VALUE-REQUEST              "ObjektId
                             MODIF ID $OB NO INTERVALS.
    Now in my program I want to have it as regular select option. Can we change this in anyway.
    I was able to modify the rest of the fields by using AT-SELECTION-SCREEN OUTPUT EVENT.
    Please help me with this, points guaranteed

    Hi rhaul,
    1. I don't  we can directly do as per ur requirement.
    2. Bcos No-Intervals cannot be modified using Loop at screen.
    3. Another option is to copy the standard Ldb and use it.
    regards,
    amit m.

  • Modifying selection screen of LDB

    Hi,
         I copied a standard report (RFCLLIB04) in a Z Report. This Report uses a logical database BRF. I have to put a check box on the selection screen in between the fields provided by Logical Database BRF i.e i have to put a check box after the field 'Ledger'.
    How can i achieve this ?
    Thanks,
    Ibrahim

    Hi,
    You can not add a chec box in between the selection screen of a LDB but you can add as an extra field at the bottom. If the user dont want to add in this way you can also look for the other selection screen whic may have the fields like you wanted.
    To achieve this goto --> attributes >  Report category> search for the required category here. It will change the selection screen. Other wise you need to create one customisex report category.
    thanks,
    Preetham

  • Asset Reporting - Copying Logical Database ADA

    Can you please assist with the following query?  I’m trying to include the following standard R3 ffields within standard R3 reports AR01 (Asset Balances) & AR18 (Depreciation Simulation):
                                    Table            Field Name            Data Element
    Serial Number            ANLA            SERNR                AM_SERNR
    Inventory Number       ANLA            IVNR                   INVNR_ANLA
    To date I have been unsuccessful in my endeavours.
    I have been discussing with an ABAPer and have been discussing the creation of Z transactions to give me the information I’m looking for.
    I’m looking for help, assistance and expertise whether the following would be recommended or even technically feasible.
    ·     Is it possible to copy logical database ADA to say ZADA (if yes how would I or the ABAPer go about this)?
    ·     Is there a way to link existing R3 reports to the new logical database
    As the majority of the R3 reports appear to be linked to ADA the aim is to amend this once and not require creating lots of Z reports.
    Any help you could provide would be greatly appreciated
    Best regards,
    Paul

    Hi Paul,
    this is strange, what release are you on?
    I have just checked AR01 on ECC 6.0, and it offers everything you need. On the selection screen of AR01, you can add selection criteria on both Serial number and Inventory number. Plus, you can display both fields in the ALV list.
    The data may be stored on table ANLA physically, but the logical database ADA is using a structure (ANLAV) instead. Both SERNR and INVNR are available in that structure. On the selection screen, you have to use the Dynamic selections button. And in the ALV list, you simply add the 2 columns, best idea wold be to save it as a variant for future use.
    Anyway, logical databases can be copied in SE36, you simply have to press the Copy button   The more critical issue is how to link standard reports to the new LDB. The answer is, no way. Instead, you should copy some of your favorite standard reports, and change the LDB in the copies.
    But, I really do not think you need this, as ADA can provide you with the information required out of the box.
    Hope that helps, points welcome
    Csaba

  • 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.

  • Logical data base copy

    Hi friends,
       Iam using one report with Logical database in 4.7 Version.
       I want copy the same report with same Logical databse..
       How can i copy the LDB without changing anything in ECC6 from 4.7..
       please suggest me..
    Thanks in Advance,
    Sampath..

    Hi!
    If you are using standard SAP LDB, then it must be in your ECC6 also, as it is in your 4.7
    Is it changed?
    Regards
    Tamá

  • Purchase order specific to copy function

    Hi All,
    We have new requirement for one of our client. During PO creation or change,  user has the option to copy with reference of existing PO items. However by doing that, the PO will default certain values/info that are no longer valid of which may not be apparent to the user at the point in time, such as the following:-
    Fiield Value: Payment Term
    After Copy:Payment term is being inherited
    Refresh Thorugh:Is there a trigger to effect the update?
    Remarks:Applicable to those vendor master with new payment term maintained subsequently
    ERS Indicator
    Fiield Value: ERS indicator status is being inherited
    Refresh Thorugh:Is there a trigger to effect the update?
    Remarks:Applicable to those vendor master with ERS activated subsequently
    Fiield Value :Price Date
    After Copy:Price date is at current date but net price inherited
    Refresh Thorugh:Click Update to carry out new pricing (at item level)
    Remarks:Any option to prevent user from saving the PO prior to triggering the respective refresh?
    Fiield Value:BOM
    After Copy:BOM inherited
    Refresh Thorugh:Click Explode BOM to reflect latest BOM (at item level)
    Refresh Thorugh:Any option to prevent user from saving the PO prior to triggering the respective refresh?
    Please help me, are there any options available that can help to minimize invalid PO information being created

    In include program FDEPL00_SHOW line 18, call the alv function module.The out put internal table is gt_data.I think you can debug the program and add find the right position to add new field to the gt_data table.
    But i found include program FDEPL00_READ use LDB method to get the vendor information.So i think it is not very easy to add code in FDEPL00_READ.
    Maybe you can add code before call alv function.
    Regards Chris.

Maybe you are looking for