DBIF_RSQL_TABLE_UNKNOWN occured. P1=ABAP-gen

Hi There
Could anybody assist. We are busy doing a OS/DB migration and the following is info on our servers.
Source system info:
OS/ Windows 2008 R2
DB: Oracle 11.3
SAP: ECC6 EHP 7 non-unicode
Kernel 740: patch 37
DBSL Patch 051
Tagert system:
OS: Windows 2012
DB: Sybase 15.7
SAP: ECC6 EHP 7 unicode
Patch 740 patch 68
The export with conversion to unicode completed successfully.  The import stopped toward the end as user DDIC password was not correct. Now we are trying to login to the system so that we can fix user DDIC. When we try to login via SAPGUI we get error DBIF_RSQL_TABLE_UNKNOWN occured. P1=ABAP-gen.
We see the following on log files:
A  Generating ABAP Program RSPOWP00                                .
A  Source ???????????????????????????????????????? Line 0.
A  Error Code DBIF_RSQL_TABLE_UNKNOWN.
A  Module  $Id: //bas/740_REL/src/krn/abap/gen/scsyenh.c#2 $ SAP.
A  ** RABAX: level LEV_RX_SET_ALERT completed.
A  ** RABAX: level LEV_RX_COMMIT entered.
A  ** RABAX: level LEV_RX_COMMIT completed.
A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A  ** RABAX: level LEV_RX_RESET_PROGS entered.
A  ** RABAX: level LEV_RX_RESET_PROGS completed.
A  ** RABAX: level LEV_RX_STDERR entered.
A  ** RABAX: level LEV_RX_STDERR completed.
A  ** RABAX: level LEV_RX_RFC_ERROR entered.
A  ** RABAX: level LEV_RX_RFC_ERROR completed.
A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
A  ** RABAX: level LEV_RX_IMC_ERROR entered.
A  ** RABAX: level LEV_RX_IMC_ERROR completed.
A  ** RABAX: level LEV_RX_APC_ERROR entered.
A  ** RABAX: level LEV_RX_APC_ERROR completed.
A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
M  RmCleanUpResources3: hdr/tbl/ext_tbl/free/keep = 000000000E0B7118/0000000000000000/0/0/1
M  RmCleanUpResources3: no resources registered
A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A  ** RABAX: level LEV_RX_END entered.
A  ** RABAX: level LEV_RX_END completed.
Can anybody assist.
Regards,
Prince

Hi Deepak
I uninstalled everything and started the import again. Now only 7 out of 190 failed.
I logged a call with SAP but I only got one response and after that they went dead silent for days.
All that are failing are DDNTT .
(RFF) ERROR: no entry for table "DDNTT_CONV_UC" in "G:\Dev_eport13May2014\ABAP\DATA\DDNTT_CONV_UC~2.TOC"
(RFF) ERROR: no entry for table "DDNTT" in "G:\Dev_eport13May2014\ABAP\DATA\DDNTT~2.TOC"
(RFF) ERROR: no entry for table "DDNTF_CONV_UC" in "G:\Dev_eport13May2014\ABAP\DATA\DDNTF_CONV_UC~2.TOC"
(RFF) ERROR: no entry for table "DDNTF" in "G:\Dev_eport13May2014\ABAP\DATA\DDNTF~2.TOC",
Regards,
Prince

Similar Messages

  • Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi - [.....] - RTBUIP_Build_Invoke.vi.ProxyCaller

    Hi all,
    I am on a field campaign with my Labview-controlled instrument. I wanted to make a small change to the code and build it again for uploading to a cFP-2020 Fieldpoint but the application builder stopped with the following error message:
    Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File2.vi -> ABAPI Get Settings From File.vi -> RTBEP_Invoke_Build_Engine.vi -> RTBUIP_Build_Invoke.vi -> RTBUIP_Build_Invoke.vi.ProxyCaller
    This is another computer than the one I used in the lab previously so might have forgotten to install something. I just copied the whole application folder with project file and subfolders
    to the Laptop I am using now. Labview version should be the same though (8.20).
    Any suggestions?
    Olaf

    Hello Olaf,
    This error is usually found when a subVI or a support file (DLL, custom control, etc)
    isn't able to be found by the application builder.  Possible reasons
    for this could include subVIs no longer located in their original
    paths and in need to be relinked, a DLL that isn't included in the build,
    and many other possibilities.
    You wrote that you copied the project from another PC, so it is very possible that some file went missing. Are all VIs in your project executable?
    You could try to mass compile all the VIs in your project and see if that helps.
    Regards,
    Johannes
    AE, NI Germany

  • Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi

    I used to be able to build executable file for my application. However when I upgrade to LV8 and try to build executable file, I got the following message.
    Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  The VI is not executable.
    The vi is perfectly executable in LV enviroment.
    Anyone know what's going on?
    Thanks in advance!

    DGU,
    Unfortunately this is a known bug in LabVIEW 8.0.1. Our R&D department is well aware of the issue and is currently working on the problem. In the mean time there are some possible work arounds
    Check the "Enable debugging"option in the "Advanced Category" of the application executable properties.
    Disable the "Remove Panel" option for all SubVIs containing Shared Variables in the build
    Try Unchecking the "Disconnect type definitions and remove unused polymorphic VI instances" options also in the Advanced category of the executable properties as shown in the attached figure.
    Move shared variables to the top level VIs and pass the data through the SubVI connector
    Downgrade to LabVIEW 8.0.
    I apologize for the problem. Please let us know if these suggestions help out. Thanks!
    Best Regards,
    Chris C
    Applications Engineering
    National Instruments
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect
    Attachments:
    1.gif ‏1 KB

  • XI protocol error occurred in abap proxy scenario- plz

    Scenario is asynchronous
    Http -> XI ->R/3(abap server proxy)
    sender: Through http client
    receiver is abap server proxy
    <u>Repository objects:</u>
    Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
    Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)
    Interface mapping: source=sender_MI, receiver_MI.
    Proxy generated on R/3 client 550 for receiver_MI.
    <u>Configuartion objects:</u>
    Sender: business service, no comm channel since http sender.
    receiver: R/3 business system
    Comm channel: receiver_cc type of XI.
    transport protocol: http
    message protocol : XI 3.0, since both XI and R/3 on webas 6.4
    addressing type: URL
    target host: diamond
    service number: 8005
    path: /sap/xi/engine?type=entry
    Authentiction data:
    user name: user22
    passwrod; correct
    logon client: 400 which is the same client I developed ll the design and config objects.
    Recevr determinaion, interface determination and recevr agrrement looks fine.
    The error iam getting is:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
      <SAP:P1>is.05.diamond</SAP:P1>
      <SAP:P2>IS</SAP:P2>
      <SAP:P3>XI</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>XI protocol error occurred</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    <b>
    Please reply , your help is appreciated.</b>
    Thanks
    KK

    Stefan thanks,
    I tried as you suggesetd putting the info of R/3 for
    server: diamond
    port: 8005
    client: 550
    user id: user05
    pwd: correct
    But I get the below error, suggest me what permission should this userid have?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

  • Termination occured in ABAP Program in  "/SAPAPO/SAPLOM_DELTA_BASIS"

    Information on where terminated                                                                   
        Termination occurred in the ABAP program "/SAPAPO/SAPLOM_DELTA_BASIS" - in                    
         "/SAPAPO/OMB_DELT_REMOVE_TRGUID".                                                            
        The main program was "/SAPAPO/ATP_DELTALIST_DISPLAY ".                                                                               
    In the source code you have the termination point in line 42                                  
        of the (Include) program "/SAPAPO/LOM_DELTA_BASISU05".                                        
        The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred                 
         in                                                                               
    procedure "/SAPAPO/OMB_DELT_REMOVE_TRGUID" "(FUNCTION)", but it was neither                   
         handled locally nor declared                                                                 
        in the RAISING clause of its signature.                                                                               
    The procedure is in program "/SAPAPO/SAPLOM_DELTA_BASIS "; its source code                    
         begins in line                                                                               
    1 of the (Include program "/SAPAPO/LOM_DELTA_BASISU05 ".
    Edited by: Wilian Segatto on Jan 19, 2010 2:07 PM

    Hi,
    I think the only solution for this problem is to upgrade the LCA build to the latest version. The LC upgrade should solve the dump on the program
    "/SAPAPO/SAPLOM_DELTA_BASIS".                
    Please have a look at note 1032677 for more information about the upgrade.
    Regards,
    Tibor

  • I am installing ERP ECC6.0 error occured in"ABAP Import"

    Installation log file follows:SAPAPPLO_2.log
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: Failed to register client info: orc=604
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    DbSl Trace: Failed to register client info: orc=604
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: E071 created #20120629062258
    (IMP) INFO: import of E071 completed (1498292 rows) #20120629062321
    (DB) INFO: E071~0 created #20120629062334
    DbSl Trace: Error 603 in exec_immediate() from oci_execute_stmt(), orpc=0
    DbSl Trace: ORA-603 occurred when executing SQL stmt (parse error offset=26)
    (DB) ERROR: DDL statement failed
    (CREATE  INDEX "E071~1" ON "E071" ( "PGMID" , "OBJECT" , "OBJ_NAME"  ) TABLESPACE PSAPSR3 STORAGE (INITIAL 374357414 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 603)
      error message returned by DbSl:
    ORA-00603: ORACLE server session terminated by fatal error
    (DB) INFO: disconnected from DB
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120629062354
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120630005244
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120630005248
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120630020459
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120630020504
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120630083639
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120630083640
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120630084141
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120630084141
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120630084805
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120630084805
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120701035333
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120701035333
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120701035821
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034
    DbSl Trace: CONNECT failed with sql error '1034'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120701035821
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120701043013
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Jul 17 2007 01:28:45
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: db_connect rc = 256
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
    DbSl Trace: CONNECT failed with sql error '12541'
    (DB) ERROR: DbSlErrorMsg rc = 99
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\MNJ\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120701043017
    Im done j2sdk_1.4.2_12 reinstall and some services also restart but problem is not resolve
    please send me solution for this error

    Hi,
    Check the below steps if this can resolve the issue.
    1.stop sap
    2.goto services.msc stop all oracle services and listener automatic from manual.
    3.Restart the system.
    4.Login to ADM.
    5.Start the service manualy
    i.cmd
    ii.sqlplus "/as sysdba" enter
    iii.in SQL> type start up
    iv. once step back(type exit once).
    v.lsnrctl and enter
    vi.start.
    vii. close command window
    6.goto SAP inst directory start installation in RUN WITH OLD INSTALLATION mode
    Regards,
    Rajesh

  • Error 1 occurred at ABAPI Dist Copy Non-VI Files.vi - ABAPI Dist Build LLB Image.vi - ABAPI Copy Files and Apply Settings.vi - DBEP_Invoke_Build_Engine.vi - DBUIP_Build_Invoke.vi - DBUIP_Build_Invoke.vi.ProxyCaller

    Error compiling a library, Kernel32.dll
    Attachments:
    error LabVIEW82.jpg ‏30 KB

    Hey elnibjo;
    This error seems to be the result of the application builder not being able to find the rc file I suggest you follow the steps listed in the following KB:
    Error Creating Source Distributions Involving rc Files
    (http://digital.ni.com/public.nsf/allkb/833BFD5E9CA0224886257584004DAA4C)
    Alternatively you can change the path information in the CLFN to contain only the DLL name.
    Let me know if this works
    Good luck with your applibation!

  • SAP paging overflow when storing data in the ABAP/4 memory.

    I am trying to create a data source in  BI7.0 in the Datawarehousing Workbench. But along the process when i need to select a view i get an error detailed in the following error file extract: Please go through and assist.
    untime Errors         MEMORY_NO_MORE_PAGING
    Date and Time          06.06.2009 14:21:35
    Short text
    SAP paging overflow when storing data in the ABAP/4 memory.
    What happened?
    The current program requested storage space from the SAP paging area,
    but this request could not be fulfilled.
    of this area in the SAP system profile.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Error analysis
    The ABAP/4 runtime system and the ABAP/4 compiler use a common
    interface to store different types of data in different parts of
    the SAP paging area. This data includes the
    ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
    CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
    macros (specified with DEFINE).
    To store further data in the SAP paging area, you attempted to
    allocate a new SAP paging block, but no more blocks were
    available.
    When the SAP paging overflow occurred, the ABAP/4 memory contained
    entries for 20 of different IDs.
    Please note:
    To facilitate error handling, the ABAP/4 memory was
    deleted.
    How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 8176
    Extended memory (EM)........... 13587912
    Assigned memory (HEAP)......... 0
    Short area..................... " "
    Paging area.................... 40960
    Maximum address space.......... " "
    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
    you can display an overview of the current roll and paging memory
    levels resulting from active users and their transactions. Try to
    decide from this whether another program requires a lot of memory
    space (perhaps too much).
    The system log contains more detailed information about the
    termination. Check for any unwanted recursion.
    Determine whether the error also occurs with small volumes of
    data. Check the profile (parameter "rdisp/PG_MAXFS", see
    Installation Guidelines).
    Is the disk or the file system that contains the paging file
    full to the extent that it cannot be increased, although it has
    not yet reached the size defined in the profile? Is the
    operating system configured to accommodate files of such a
    size?
    The ABAP processor stores different types of data in the SAP
    paging area. These include:
    (1) Data clusters (EXPORT ... TO MEMORY ...)
    (2) Parameters for calling programs (SUBMIT REPORT ...),
    Dialog modules (CALL DIALOG ...) and transactions
    (CALL TRANSACTION USING ...)
    (3) Internally defined program macros (DEFINE ...)
    Accordingly, you should check the relevant statements in a program
    that results in an overflow of the SAP paging area.
    It is critical when many internal tables, possibly with
    different IDs, are written to memory (EXPORT).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MEMORY_NO_MORE_PAGING" " "
    "SAPLWDTM" or "LWDTMU20"
    "TABC_ACTIVATE_AND_UPDATE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

    Hi Huggins,
    Maintenance of the Paging File is owned by your basis team.
    They should increase this in order for your transaction to process successfully.
    Just for your reference, in case the OS used is windows server 2003, paging file value can be checked through;
    Right click in the My Computer&gt;properties.
    Then go to Advance tab;
    Then there should be a performance section, click the settings
    Then Advance tab again. The paging file can be seen from there.
    (and can be adjusted from there also)
    The value of the paging file in general will be dependent with the available RAM from the hardware.
    Hope this helps. Thanks a lot.
    - Jeff

  • Error 7 occurred while building source distribution in labview 8

    I can build exe file and  installer for my project. But while trying to build source distribution i got an error. Error description is as follows:
    Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.

    Hi Andy,
    FYI, initially part of this project was developed in LabVIEW 7.1 and now I have
    converted all the project files to LabVIEW 8.0. This was done by mass compiling and
    saving all the VIs.
    It is possible for me to build source distribution for some other programs. But I got the error while building source distribution for my current project. Same error was generated even while previewing the source distribution. This project contains some dynamic VIs. I had included them under the dynamic VIs and support files while creating EXE file. While building source distribution, i got an error message saying that :
    "Unable to generate preview. An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them  (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
    \\Source code\Controls\Tests\Battery Current Calibration\Battery Current Calibration1.ctl
    <Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine_Preview.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux."
    For this error I rename the control, relink it in the code, and save the VI. Now I got an error message indicating different control. I was totally confused by this behaviour. What is the problem? Why the problem occured? What procedure to follow to avoid these kind of errors in future? I would be thankful, if I can get answers for my questions.
    Thanks in advance.
    Ramasamy.

  • Sending payload in ABAP proxy

    Hi all,
    i have a requirement to send the inbound payload in the mail content when any error occurs in ABAP proxy. How can I achieve this?
    Thanks

    are you looking for this
    The following program fetches the payload for a request message independently of a proxy instance and returns it in the system:
    DATA:
      ls_request          TYPE [Data type of output parameter],
      lo_fault            TYPE REF TO cx_ai_system_fault,
      lo_payload_handler  TYPE REF TO IF_WS_PAYLOAD_HANDLER,
      lo_payload          TYPE REF TO if_ws_payload,
      lt_request_data     TYPE PRX_T_PARAM,
      ls_request_data     TYPE PRX_S_PARAM.
      lo_pointer          TYPE REF TO xstring,
    Fill request data
    request-field1 = '[Value1]'.
    request-field1 = '[Value1]'.
    request-fieldN = '[ValueN]'.
    Use payload handler to get payload independently
    from proxy call:
    TRY.
    Get Payload handler for a proxy method.
    Note: You have to provide the proxy and method name in uppercase.
      lo_payload_handler = cl_proxy_access=>get_payload_handler(
         proxy_name = 'CO_...'
         proxy_method = 'EXECUTE_SYNCHRONOUS' ).
    Pass request data to payload handler
      CLEAR lt_request_data.
      CLEAR ls_request_data.
      ls_request_data-name = 'OUTPUT'.
      GET REFERENCE OF request into ls_request_data-value.
      append ls_request_data to lt_request_data.
      lo_payload =
         lo_payload_handler->get_payload_from_request_data(
            lt_request_data).
    Catch system faults
    CATCH cx_ai_system_fault INTO lo_fault.
      WRITE: / 'System fault'.
      WRITE: / 'Code:', lo_fault->code.
      WRITE: / 'Text:', lo_fault->errortext.
      EXIT.
    ENDTRY.
    Show payload for test purposes
    lo_pointer = lo_payload->get_xml_pointer( ).
    cl_proxy_service=>show_xml_document( lo_pointer->* ).
    <b>Check this</b>
    /people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy
    http://help.sap.com/saphelp_nw04/helpdata/en/31/6c5c3c3806af06e10000000a11402f/frameset.htm
    2 xml documents in 1 payload
    Thanks !

  • Can u explain me how to work with OOPs ABAP

    Hi,
    Can u explain me how to work with OOPS Abap,  If possible pls send me some sample programs regarding OOps concept used in Realtime.
    Thanks.

    hii,
    Please check this online document (starting page 1291).
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCABA/BCABA.pdf
    Also check this links as well.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ce/b518b6513611d194a50000e8353423/frameset.htm
    http://www.sapgenie.com/abap/OO/
    http://www.futureobjects.de/content/intro_oo_e.html
    http://www.sap-img.com/abap/business-add-in-you-need-to-understand-abap-oo-interface-concept.htm
    /people/ravikumar.allampallam/blog/2005/02/11/abap-oo-in-action
    What is Object Orientation?
    Object orientation (OO), or to be more precise, object-oriented programming, is a problem-solving method in which the software solution reflects objects in the real world.
    A comprehensive introduction to object orientation as a whole would go far beyond the limits of this introduction to ABAP Objects. This documentation introduces a selection of terms that are used universally in object orientation and also occur in ABAP Objects. In subsequent sections, it goes on to discuss in more detail how these terms are used in ABAP Objects. The end of this section contains a list of further reading, with a selection of titles about object orientation.
    Objects
    An object is a section of source code that contains data and provides services. The data forms the attributes of the object. The services are known as methods (also known as operations or functions). Typically, methods operate on private data (the attributes, or state of the object), which is only visible to the methods of the object. Thus the attributes of an object cannot be changed directly by the user, but only by the methods of the object. This guarantees the internal consistency of the object.
    Classes
    Classes describe objects. From a technical point of view, objects are runtime instances of a class. In theory, you can create any number of objects based on a single class. Each instance (object) of a class has a unique identity and its own set of values for its attributes.
    Object References
    In a program, you identify and address objects using unique object references. Object references allow you to access the attributes and methods of an object.
    In object-oriented programming, objects usually have the following properties:
    Encapsulation
    Objects restrict the visibility of their resources (attributes and methods) to other users. Every object has an interface, which determines how other objects can interact with it. The implementation of the object is encapsulated, that is, invisible outside the object itself.
    Polymorphism
    Identical (identically-named) methods behave differently in different classes. Object-oriented programming contains constructions called interfaces. They enable you to address methods with the same name in different objects. Although the form of address is always the same, the implementation of the method is specific to a particular class.
    Inheritance
    You can use an existing class to derive a new class. Derived classes inherit the data and methods of the superclass. However, they can overwrite existing methods, and also add new ones.
    Uses of Object Orientation
    Below are some of the advantages of object-oriented programming:
    Complex software systems become easier to understand, since object-oriented structuring provides a closer representation of reality than other programming techniques.
    In a well-designed object-oriented system, it should be possible to implement changes at class level, without having to make alterations at other points in the system. This reduces the overall amount of maintenance required.
    Through polymorphism and inheritance, object-oriented programming allows you to reuse individual components.
    In an object-oriented system, the amount of work involved in revising and maintaining the system is reduced, since many problems can be detected and corrected in the design phase.
    Achieving these goals requires:
    Object-oriented programming languages
    Object-oriented programming techniques do not necessarily depend on object-oriented programming languages. However, the efficiency of object-oriented programming depends directly on how object-oriented language techniques are implemented in the system kernel.
    Object-oriented tools
    Object-oriented tools allow you to create object-oriented programs in object-oriented languages. They allow you to model and store development objects and the relationships between them.
    Object-oriented modeling
    The object-orientation modeling of a software system is the most important, most time-consuming, and most difficult requirement for attaining the above goals. Object-oriented design involves more than just object-oriented programming, and provides logical advantages that are independent of the actual implementation
    http://www.sapgenie.com/abap/OO/index.htm
    http://www.geocities.com/victorav15/sapr3/abap_ood.html
    http://www.brabandt.de/html/abap_oo.html
    Check this cool weblog:
    /people/thomas.jung3/blog/2004/12/08/abap-persistent-classes-coding-without-sql
    /people/thomas.jung3/blog/2004/12/08/abap-persistent-classes-coding-without-sql
    /people/sap.user72/blog/2005/05/10/a-small-tip-for-the-beginners-in-oo-abap
    /people/ravikumar.allampallam/blog/2005/02/11/abap-oo-in-action
    /people/thomas.jung3/blog/2005/09/08/oo-abap-dynpro-programming
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b6254f411d194a60000e8353423/frameset.htm
    http://www.sapgenie.com/abap/OO/
    http://www.sapgenie.com/abap/OO/index.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b5654f411d194a60000e8353423/content.htm
    http://www.esnips.com/doc/375fff1b-5a62-444d-8ec1-55508c308b17/prefinalppt.ppt
    http://www.esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf
    http://www.esnips.com/doc/5c65b0dd-eddf-4512-8e32-ecd26735f0f2/prefinalppt.ppt
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sapgenie.com/
    http://help.sap.com
    http://www.sapgenie.com/abap/OO/
    http://www.sapgenie.com/abap/OO/index.htm
    http://www.sapgenie.com/abap/controls/index.htm
    http://www.esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf
    http://www.esnips.com/doc/0ef39d4b-586a-4637-abbb-e4f69d2d9307/SAP-CONTROLS-WORKSHOP.pdf
    http://www.sapgenie.com/abap/OO/index.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/ce/b518b6513611d194a50000e8353423/frameset.htm
    http://www.sapgenie.com/abap/OO/
    these links
    http://help.sap.com/saphelp_47x200/helpdata/en/ce/b518b6513611d194a50000e8353423/content.htm
    For funtion module to class
    http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5954f411d194a60000e8353423/content.htm
    for classes
    http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b5c54f411d194a60000e8353423/content.htm
    for methods
    http://help.sap.com/saphelp_47x200/helpdata/en/08/d27c03b81011d194f60000e8353423/content.htm
    for inheritance
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/4049c40f4611d3b9380000e8353423/content.htm
    for interfaces
    http://help.sap.com/saphelp_47x200/helpdata/en/c3/225b6254f411d194a60000e8353423/content.htm
    For basic stuff......
    abap oops
    http://esnips.com/doc/5c65b0dd-eddf-4512-8e32-ecd26735f0f2/prefinalppt.ppt
    http://esnips.com/doc/2c76dc57-e74a-4539-a20e-29383317e804/OO-abap.pdf
    http://esnips.com/doc/0ef39d4b-586a-4637-abbb-e4f69d2d9307/SAP-CONTROLS-WORKSHOP.pdf
    http://esnips.com/doc/92be4457-1b6e-4061-92e5-8e4b3a6e3239/Object-Oriented-ABAP.ppt
    http://esnips.com/doc/448e8302-68b1-4046-9fef-8fa8808caee0/abap-objects-by-helen.pdf
    http://esnips.com/doc/39fdc647-1aed-4b40-a476-4d3042b6ec28/class_builder.ppt
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/225b5654f411d194a60000e8353423/frameset.htm
    ABAP Business Development and Service Provisioning/ABAP Objects
    General information
    What is Object Orientation?
    some blogs
    A small tip for the beginners in OO ABAP
    Object Oriented ABAP (OO-ABAP)
    and others wiki OO Abap
    cheers,
    sharad
    Edited by: sharad narayan on Apr 29, 2008 12:19 PM

  • Use of OO ABAP

    Hi all,
    I have recently completed studing OO ABAP.Can some body tell me exactly where these concepts are used.For ex. used in OO ALV.Like this where else its used so that i can decide how much to focus on this concept.
    Thanks.

    In the past, information systems used to be defined primarily by their functionality: data and functions were kept separate and linked together by means of input and output relations.
    The object-oriented approach, however, focuses on objects that represent abstract or concrete things of the real world. These objects are first defined by their character and their properties which are represented by their internal structure and their attributes (data). The behaviour of these objects is described by methods (functionality).
    Objects form a capsule which combines the character to the respective behaviour. Objects should enable programmers to map a real problem and its proposed software solution on a one-to-one basis.
    Typical objects in a business environment are, for example, ‘Customer’, ‘Order’, or ‘Invoice’. From Release 3.1 onwards, the Business Object Repository (BOR) of SAP Web Applicaton Server ABAP has contained examples of such objects. The BOR object model will be integrated into ABAP Objects in the next Release by migrating the BOR object types to the ABAP class library.
    A comprehensive introduction to object orientation as a whole would go far beyond the limits of this introduction to ABAP Objects. This documentation introduces a selection of terms that are used universally in object orientation and also occur in ABAP Objects. In subsequent sections, it goes on to discuss in more detail how these terms are used in ABAP Objects. The end of this section contains a list of further reading, with a selection of titles about object orientation.
    Objects
    Objects are instances of classes. They contain data and provides services. The data forms the attributes of the object. The services are known as methods (also known as operations or functions). Typically, methods operate on private data (the attributes, or state of the object), which is only visible to the methods of the object. Thus the attributes of an object cannot be changed directly by the user, but only by the methods of the object. This guarantees the internal consistency of the object.
    Classes
    Classes describe objects. From a technical point of view, objects are runtime instances of a class. In theory, you can create any number of objects based on a single class. Each instance (object) of a class has a unique identity and its own set of values for its attributes.
    Object References
    In a program, you identify and address objects using unique object references. Object references allow you to access the attributes and methods of an object.
    In object-oriented programming, objects usually have the following properties:
    Encapsulation
    Objects restrict the visibility of their resources (attributes and methods) to other users. Every object has an interface, which determines how other objects can interact with it. The implementation of the object is encapsulated, that is, invisible outside the object itself.
    Inheritance
    You can use an existing class to derive a new class. Derived classes inherit the data and methods of the superclass. However, they can overwrite existing methods, and also add new ones.
    Polymorphism
    Identical (identically-named) methods behave differently in different classes. In ABAP Objects, polymorphism is implemented by redefining methods during inheritance and by using constructs called interfaces.
    Uses of Object Orientation
    Below are some of the advantages of object-oriented programming:
    · Complex software systems become easier to understand, since object-oriented structuring provides a closer representation of reality than other programming techniques.
    · In a well-designed object-oriented system, it should be possible to implement changes at class level, without having to make alterations at other points in the system. This reduces the overall amount of maintenance required.
    · Through polymorphism and inheritance, object-oriented programming allows you to reuse individual components.
    · In an object-oriented system, the amount of work involved in revising and maintaining the system is reduced, since many problems can be detected and corrected in the design phase.
    Achieving these goals requires:
    · Object-oriented programming languages
    Object-oriented programming techniques do not necessarily depend on object-oriented programming languages. However, the efficiency of object-oriented programming depends directly on how object-oriented language techniques are implemented in the system kernel.
    · Object-oriented tools
    Object-oriented tools allow you to create object-oriented programs in object-oriented languages. They allow you to model and store development objects and the relationships between them.
    · Object-oriented modeling
    The object-orientation modeling of a software system is the most important, most time-consuming, and most difficult requirement for attaining the above goals. Object-oriented design involves more than just object-oriented programming, and provides logical advantages that are independent of the actual implementation.
    Further Reading
    There are many books about object orientation, object-oriented programming languages, object-oriented analysis and design, project management for OO projects, patterns and frameworks, and so on. This is a small selection of good books covering the most important topics:
    · Scott Ambler, The Object Primer, SIGS Books & Multimedia (1996), ISBN: 1884842178
    A very good introduction to object orientation for programmers. It provides comprehensive explanations of all essential OO concepts, and contains a procedure model for learning OO quickly and thoroughly. It is easy to read and practical, but still theoretically-founded.
    · Grady Booch, Object Solutions: Managing the Object-Oriented Project, Addison-Wesley Pub Co (1995), ISBN: 0805305947
    A good book about all of the non-technical aspects of OO that are equally important for effective object-oriented programming. Easy to read and full of practical tips.
    · Martin Fowler, UML Distilled: Applying the Standard Object Modeling Language, Addison-Wesley Pub Co (1997), ISBN: 0201325632
    An excellent book about UML (Unified Modeling Language - the new standardized OO language and notation for modeling). Assumes knowledge and experience of object orientation.
    · Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Design Patterns. Elements of Reusable Object-Oriented Software, Addison-Wesley Pub Co (1998), ISBN: 0201634988
    Provides a pattern, showing how recurring design problems can be solved using objects. This is the first big pattern book, containing many examples of good OO design.
    · James Rumbaugh, OMT Insights: Perspectives on Modeling from the Journal of Object-Oriented Programming, Prentice Hall (1996), ISBN: 0138469652
    A collection of articles addressing the many questions and problems of OO analysis and design, implementation, dependency management, and so on. Highly recommended.
    Notes
    If you are new to object-orientation, you should read Scott Ambler’s ‘The Object Primer’ and then acquire some practical experience of your own. You should definitely use the CRC techniques described by Ambler and Fowler for object-oriented analysis and design. After this, you should learn UML, since this is the universal OO analysis and design notation. Finally, you should read at least one book about patterns.
    At the beginning of a large OO project, the question immediately arises as to the sequence in which things should be done, which phases should be finished at what time, how to divide up and organize the development work, how to minimize risks, how to assemble a good team, and so on and so forth. Many of the best practices of project management have had to be redefined for the object-oriented world, and the opportunities that this has produced are significant. For further information about how to use OO in project management, see Grady Brooch’s book ‘Object solutions’, or the chapter entitles ‘An outline development process’ from Martin Fowler’s book.
    There are, of course, many other good books about object orientation. The above list does not claim either to be complete, or necessarily to recommend the best books available.
    Thanks&regards,
    sravani

  • Regarding error occur in business content activation

    Hai experts,
              when i am activating the business content its going to dump analysis the system is going to give me the error like " message_type_x" using st22 i found that error occured in abap program .It is an predefined program.Is there any solution for that one other wise i have  raise this question to service.sap.com.i need emergency.
                                               bye.

    Hi ,
    You have to underastand whether this is happening with all the objects , I mean are you getting this dump for any object you are trying to activate through bi content.
    If this is happening with few objects then you have see whether the method of activation bi content is being performed in the correct method.
    If thisis happening with all the objects then check all the basic settings and at the same time check authorisations.
    Check if you have any thing in SU53 transactions.
    Regards
    Rahul Bindroo

  • Error occurred while building the following file

    hi,
    i get an error while compilating my programm. i did not change the vis listed below, they are standard express vi's...
    An error occurred while building the following file:
    C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\express\express analysis\CurveFittingBlock.llb\subCurveFitting.vi
    Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Rule_Editor.vi -> BUIP_Create_Build_Rule.vi -> EBUIP_Global_OnCommand.vi -> EBUIP_Global_OnCommand.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  The VI is not executable.

    I would recommend to update to at least LabVIEW 8.0.1 (free update) and masscompile the vi.lib folder.
    You can download the update here:
    http://digital.ni.com/softlib.nsf/websearch/4C1209D42320BCFD8625711C005FB25B?opendocument&node=13207...

  • ABAP-oop

    what are object oreiented concept in abap?explain each one any body can help me?

    Object orientation (OO), or to be more precise, object-oriented programming, is a problem-solving method in which the software solution reflects objects in the real world.
    A comprehensive introduction to object orientation as a whole would go far beyond the limits of this introduction to ABAP Objects. This documentation introduces a selection of terms that are used universally in object orientation and also occur in ABAP Objects. In subsequent sections, it goes on to discuss in more detail how these terms are used in ABAP Objects. The end of this section contains a list of further reading, with a selection of titles about object orientation.
    Objects
    An object is a section of source code that contains data and provides services. The data forms the attributes of the object. The services are known as methods (also known as operations or functions). Typically, methods operate on private data (the attributes, or state of the object), which is only visible to the methods of the object. Thus the attributes of an object cannot be changed directly by the user, but only by the methods of the object. This guarantees the internal consistency of the object.
    Classes
    Classes describe objects. From a technical point of view, objects are runtime instances of a class. In theory, you can create any number of objects based on a single class. Each instance (object) of a class has a unique identity and its own set of values for its attributes.
    Object References
    In a program, you identify and address objects using unique object references. Object references allow you to access the attributes and methods of an object.
    In object-oriented programming, objects usually have the following properties:
    Encapsulation
    Objects restrict the visibility of their resources (attributes and methods) to other users. Every object has an interface, which determines how other objects can interact with it. The implementation of the object is encapsulated, that is, invisible outside the object itself.
    Polymorphism
    Identical (identically-named) methods behave differently in different classes. Object-oriented programming contains constructions called interfaces. They enable you to address methods with the same name in different objects. Although the form of address is always the same, the implementation of the method is specific to a particular class.
    Inheritance
    You can use an existing class to derive a new class. Derived classes inherit the data and methods of the superclass. However, they can overwrite existing methods, and also add new ones.
    Uses of Object Orientation
    Below are some of the advantages of object-oriented programming:
    Complex software systems become easier to understand, since object-oriented structuring provides a closer representation of reality than other programming techniques.
    In a well-designed object-oriented system, it should be possible to implement changes at class level, without having to make alterations at other points in the system. This reduces the overall amount of maintenance required.
    Through polymorphism and inheritance, object-oriented programming allows you to reuse individual components.
    In an object-oriented system, the amount of work involved in revising and maintaining the system is reduced, since many problems can be detected and corrected in the design phase.
    Achieving these goals requires:
    Object-oriented programming languages
    Object-oriented programming techniques do not necessarily depend on object-oriented programming languages. However, the efficiency of object-oriented programming depends directly on how object-oriented language techniques are implemented in the system kernel.
    Object-oriented tools
    Object-oriented tools allow you to create object-oriented programs in object-oriented languages. They allow you to model and store development objects and the relationships between them.
    Object-oriented modeling
    The object-orientation modeling of a software system is the most important, most time-consuming, and most difficult requirement for attaining the above goals. Object-oriented design involves more than just object-oriented programming, and provides logical advantages that are independent of the actual implementation.
    This section of the ABAP User’s Guide provides an overview of the object-oriented extension of the ABAP language. We have used simple examples to demonstrate how to use the new features. However, these are not intended to be a model for object-oriented design. More detailed information about each of the ABAP Objects statements is contained in the keyword documentation in the ABAP Editor.

Maybe you are looking for