Runtime error SAPSQL_CURSOR_ALREADY_OPEN during extraction - 0CO_OM_CCA_9

Greetings,
I'm getting the following runtime error: SAPSQL_CURSOR_ALREADY_OPEN during extraction of infoSource: 0CO_OM_CCA_9.
Runtime Errors         SAPSQL_CURSOR_ALREADY_OPEN
Date and Time          23.05.2011 11:10:44
Short text
     Attempt to open a database cursor which was already open.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLBWOMR" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An OPEN CURSOR statement established that the cursor
     was already open. This means that it was not closed in the previous
     processing with CLOSE CURSOR.
I Checked OSS notes for my infosource error with no luck.
Could you help in that matter?
Thanks
-Roula

Have a look on following note:
[1373960 - BW extractor: Runtime error SAPSQL_CURSOR_ALREADY_OPEN|https://service.sap.com/sap/support/notes/1373960]

Similar Messages

  • Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED during extraction

    Hi,
    Anyone knows what the solution is to this problem:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    |Short text                                                                                |
    |    No more storage space available for extending an internal table.                              |
    |What happened?                                                                                |
    |    You attempted to extend an internal table, but the required space was                         |
    |    not available
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" could               |
    |     not be further extended. To enable                                                           |
    |    error handling, the table had to be delete before this log was written.                       |
    |    As a result, the table is displayed further down or, if you branch to                         |
    |    the ABAP Debugger, with 0 rows.                                                               |
    |                                                                                |
    |    At the time of the termination, the following data was determined for                         |
    |    the relevant internal table:                                                                  |
    |                                                                                |
    |    Memory location: "Session memory"                                                             |
    |    Row width: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "xxx"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    The error reported by the operating system is:                                                |
    |    Error number..... " "                                                                         |
    |    Error text....... " "                                                                         |
    |How to correct the error                                                                          |
    |    The amount of storage space (in bytes) filled at termination time was:                        |
    |                                                                                |
    |    Roll area...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    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:                                                                                |
    |                                                                                |
    |    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Short text
    No more storage space available for extending an internal table
    |What happened?
    |    You attempted to extend an internal table, but the required space was
    |    not available.
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" could
    |     not be further extended. To enable
    |    error handling, the table had to be delete before this log was written.                       |
    |    As a result, the table is displayed further down or, if you branch to                         |
    |    the ABAP Debugger, with 0 rows.                                                               |
    |                                                                                |
    |    At the time of the termination, the following data was determined for                         |
    |    the relevant internal table:                                                                  |
    |                                                                                |
    |    Memory location: "Session memory"                                                             |
    |    Row width: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "SAP-Server XXXX"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    The error reported by the operating system is:                                                |
    |    Error number..... " "                                                                         |
    |    Error text....... " "                                                                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |How to correct the error                                                                          |
    |    The amount of storage space (in bytes) filled at termination time was:                        |
    |                                                                                |
    |    Roll area...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    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:                                                                                |
    |                                                                                |
    |    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

  • Error occured during extraction from APO to BI 7.0

    Hi Experts,
    I am in the process of extracting data from SCM(APO-Demand Planning) to BI .I have selected the relevant planning area 9ADP01 and given Generate Export DS in APO system and replicated the same in BI.But before scheduling the InfoPackage,when i checked for the DS 9A0APO_DP_ORDERANALYTICS_1,it displays "Error occured during extraction".I do have a doubt whether I should activate the DS in RSA5 before replication (but am not able to find the DS under DP in RSA5)
       I have checked the forums but solutions mentioned did not resolve my issue.
    Thanks,
    Meera

    Hi,
    The issue is resolved...
    Regards,
    Meera

  • Acrobat PDFMaker Office COM Addin for Microsoft Office 365 does not work. When I check the cox for COM Add-ins, it unchecks it. "A runtime error occurred during the loading of the COM Add-in." I use Adobe X Professional. The Add-in worked fine in Office 2

    I recently upgraded to Microsoft 365 Home and use Outlook 2013. The Acrobat PDFMaker Addin worked fine in Office 2010. Now, I get an error message: Not loaded. A runtime error occurred during the loading of the COM Add-in.
    I use Adobe Acrobat X Professional.
    I have restarted Outlook, restarted my computer, and nothing changes.
    Does anyone have a solution?
    Steve

    I do not think that AA X is compatible with the newest versions of OFFICE and such. Your only choice is to print to the Adobe PDF printer or use the MS plugins to create PDFs.

  • Errors occurred during extraction of the existing UDC Connect sources

    HI ALL,
    I try to create a DataSource with UD Connect on BW 3.5,
    i choose a RFC destination, but after of to choose UD connect source appear the next error message "Errors occurred during extraction of the existing UDC Connect sources".
    The RFC destination is OK.
    In the CCMS Monitor the Java Connectors and Enterprise Java Beans are available.
    Help me please!
    regards!

    Hi, me again, I change some parameters and now is working but wrong!!!!! when I try to select a UD connect, in the match code i get the next list:
    6B偡浡彏啔䐠††††††††††#############
    #########†††††彏啔†††††###########
    ††††††††††#############偡浡彏啔偡浡彏啔
    please if anyone knows what is going on help me...!!
    tnx

  • Errors occured during extraction at RSA3

    hi
    i am giving these datasource and get data at rsa3, its  giving error like error occured during extractions?
    can u please let me know what could be the reason?
    0CO_PC_PCP_03
    0CO_PC_PCP_04

    Hi,
    Check the Log in RSA3, youca n find log and see it and correct it.
    Steps:
    1. Inastall DS in RSA5
    2. Check in RSA6.
    3. Extract in RSA3.
    Thanks
    Reddy

  • Errors occurred during extraction of UD Connect object field- table not fou

    Hi,
    In BI 7.0 system I can't select any UD Connect source object on the "Extraction" tab page of  the DataSource maitenance screen. If I type the table name (which is "UDITEST") into it and then hit the "Proposal" tab page, I get the following error:
    Errors occurred during extraction of UD Connect object field-list: Errors occurred during extraction of UD Connect object field-list: UDCADAPTERROR::RSSDK|200|Table: uditest not found|
    Message no. RSDS_ACCESS036
    Analysis:
    1) We have tested the BI JDBC Connector using the URL:
    http://xxxabcdev03:50000/TestJDBC_Web/TestJDBCPage.jsp
    We got the list of tables displayed (UDITEST table is also displayed)=> connector is configured properly.
    2) When we are trying to configure the Source system in rsa1->modelling->source systems-> UD connect -> create,
    a) RFC Destination: We are using an RFC Connection that is already in place of type 'T'   between the J2EE engine and BI ABAP engine. We tested this connection from SM59 -> TCP/IP connections and it is working fine.
    How do we test whether the RFC between J2EE engine and BI ABAP engine is a 2 way RFC connection?
    b) Logical System Name: We have manually typed in free text 'UDC_local'. Could you please clarify do we need to type in manually or select the logical system name from the F4 help?
    Which logical system name should we enter here exactly.. pls clarify.
    Do we have a seperate logical system name for the J2EE server...?
    c) Type of Connector : JDBC
    d) name of connector: SDK_JDBC
    e) Source system name: SDK_JDBC
    f) Type and Release : blank
    Thanks to any answers in advance!
    Best regards,
    Syam

    Hi,
    Tried to give the Logical System Name in uppercase ie: UDC_LOCAL.
    Now, when I click on the F4 of 'UD Connect Source Object' in Extraction tab, I get the message as below:
    "Extraction of existing UD Connect data source objects".
    But no list of tables is being displayed. When I entered the table name (UDITEST) manually, it gives the same error as :
    " Errors occurred during extraction of UD Connect object field- table not found"...
    Could you please specify from where is the UD Conenct source object fetched from?
    Rgds
    Syam

  • ERRORS OCCURED DURING EXTRACTION USING RSA3

    Dear Folks,
    I have an error in production client & that is when i am doing test extraction for standard datasource using RSA3 i am geting following error:ERRORS OCCURED DURING EXTRACTION.
    I checked the log and message is extraction program failed as it is called by an invalid infosource or object 0crm_lead_h.
    note:0crm_lead_h is the DS
    Any help
    Thanks

    Hi ,
    Please follow below thread , it will solve ur problem.
    Errors occurred during the extraction, Message nos. RJ012 & R3009
    Hope this will help you...
    Thanks,
    Jitendra

  • RSA3: error occured during extraction hierarchy

    Hi,
    I have created 2 sets using tcode cxsa, ZAAA and ZBBB. Table that used for this set is FIMC and the field is RBUNIT. After that, i create generic hierarchy datasource using tcode BW07, enter the table name and field,then execute (custom data source with name 'ZFIECCS_HIER_CONS_UNIT' created). I don't use option 'Hierarchies of Sets with Compounding' here.
    After that i try to use tcode RSA3, enter the datasource = ZFIECCS_HIER_CONS_UNIT, enter HIENAME = ZAAA or ZBBB but i get message error 'Error occured during extraction'.
    I try to debug this extractor and find error happen in FM GSBH_HIERARCHY_TRANSFER_SETS,  this happen because i_s_hiebas-hclass <> i_s_hiersel-hclass.
    Then i try to execute program RSA1HCAT using tcode SE38. I enter my datasource and execute. I found that ZAAA and ZBBB not in list of hierarchy that can be accessed.
    Anyone can help my problem?
    Regards,
    Satria Budiman

    Hi,
    Go to RSA6 and see if data source is using the correct version or not.you can select the data source and click on chek option on the top and see if its any error.
    If it is dump then there is no other option but to retransport it again.
    try to see if the extract struture used by this data source is active or not??
    See if you are getting the error in the test systems also or not.
    Issue could be with the reallignment also where a controlling master data is changed.
    Thanks
    Ajeet

  • 0PM_PRM_PLCS_1 error occured during extraction

    Dear gurus ,
    i have make entry im pm_c05 table and extract the data first time ,it works fine .when i again try to load data it give me error .i have checked in rsa3 and while extraction it is giving error " Error occured during extraction " . our bi is is on 7.0 and erp 0n ehp 6.4 .i have implemented the sap note 0001243299 but again gettinng the same error.please help me out

    Hi Faisal:
       I've found a long list of SAP Notes that might be applicable to your environment, even though it is not mandatory to implement all of them to solve the issue you're facing right now, please consider the convenience of installing them on your system to fix some potential problems in advance.
    Note 1344048 - "0PM_PRM_PLCS_1: Delta upload does not work as expected"
    Note 1285238 - "0PM_PRM_PLCS_1: Errors during extraction, poor performance"
    Note 1323965 - "0PM_PRM_PLCS_1: Calculation for services"
    Note 1338093 - "0PM_PRM_PLCS_1: Execution factor not taken into account"
    Note 1339189 - "0PM_PRM_PLCS_1: Error occurs for alternative indicator"
    Note 1340188 - "0PM_PRM_PLCS_1: Revision of the calculation module"
    Note 1312783 - "0PM_PRM_PLCS_1: Implementing additional fields"
    Note 1314158 - "0PM_PRM_PLCS_1: Incorrect result during extraction"
    Note 1356256 - "0PM_PRM_PLCS_1: Poor system performance with strategy plans"
    Note 1416214 - "Overlap of records due to key constraints in 0PM_DS07"
    Note 1446484 - "Planned costs, costing, ECP: Incorrect message KI 217"
    Note 1508442 - "ECP, extractor 0PM_PRM_PLCS_1: error ME024 or ME025"
    Regards,
    Francisco Milán.

  • Not Loaded. A runtime error occurred during the load of the COM add-in.

    Hey All!
    I am relatively new to Hyperion, and need some help. I recently purchased a new laptop, and I am trying to reinstall Smart View 11.1.2.1 on my home system, but I continue to run into difficulties. I launch the Smart View installer by right-clicking and selecting "Run as Administrator," and everything seems to install successfully. However, when I open Excel or any Microsoft Office product, the Smart View tab is unavailable, and when I Manage my COM add-ins, the pop-up box reads "Load Behavior: A runtime error occurred during the loading of the COM add-in."
    I have looked into my registries, and everything seems to be in order. I have changed my load behavior back to 3 as well. Any ideas? Are there any compatibility issues I need to consider? Thanks for your help!
    Craig

    PLEASE do not do this! You are storing up trouble for the future that will be so much harder to unpick.
    1. It does not solve the problem. Whatever the problem was, this is not the solution! If the issue is multiple DLLs, you need to delete the duplicates and register the correct ones, not make even more copies. If the problem is permissions, you need to sort that one out.
    2. If it appears to solve the problem, then the problem (something to do with permissions) needs to be solved at source, not kludged round like this.
    3. If there is an unresolved problem on the system, it is more likely that the next upgrade will not go well.
    4. Uninstaller cannot remove the copies you made manually. The same thing applies to upgrades! You risk getting mixed versions afterwards.
    My first steps to resolve this problem would be:
    1. Uninstall the SmartView client. You must be an administrator to do this -- try to be the same administrator that installed it.
    2. Clean up. Make sure the files are all deleted. Search the whole box for old files (HsTBar.xla, HsAddin.dll etc.) possibly left over from an old installation -- you might have upgraded into a different location at some time in the past and left orphaned files hanging around. Get rid.
    3. Reboot. Log in as a local administrator.
    4. Open Excel and visit the Add-Ins dialog and remove any entries for SmartView.
    5. Install SmartView client from a local copy of SmartView.exe -- make sure you have the correct version.
    That solves 99% of problems like this. If you have to register the DLLs manually, it suggests that your 'administrator' account doesn't have the full rights you think it has. DON'T kludge it by copying DLLs into your profile!
    Thanks.

  • Error occurred during extraction in r/3 ( loans data sources)

    Hi,
    for Data source 0CML_Delta
    Iam getting 0 records when i check the extraction checker in RSA3. i have used Delta Update mode.
    Even in BI it shows 0 records for delta load.
    i have done the change pointer activation and even updated the dynamic infosource as suggested in SDN threads.
    but still shows 0 records.
    For full load iam getting 'Error During Extraction'.
    Is there any specfic procedure to follow for this?
    Can any one suggest me the correct procedure?
    regards

    Hi
    Try Extracting data in debugging mode and check whether there is nay data getting filled in the tables. If not then probably check out the logic written once again,it is also possible that there may be no new data.
    Regards
    Raj

  • Runtime error "DBIF_RSQL_INVALID_RSQL" during unicode preconversion SPUMG

    Hi experts,
    I was performing the unicode preconversion with spumg on ECC 5.0. The system environment is HP-UX 11.31 and Oracle 10g.
    During  the scan lever 2: tables without language info, there's always an error when scan table "VBSEGK", meanwhile the runtime error "DBIF_RSQL_INVALID_RSQL" raised in ST22. Below is some information regarding to this error.
    Runtime error:
    Runtime Error          DBIF_RSQL_INVALID_RSQL
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          30.05.2011 05:44:42
    Error in ABAP application program.
    The current ABAP program "UMG_SCANNER" had to be terminated because one of the statements could not be executed.
    This is probably due to an error in the ABAP program.
    An exception occurred. This exception is dealt with in more detail below
    .The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was neither caught nor passed along using a RAISING clause, in the procedure "FETCH_NEXT"
    "(METHOD)".
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    The data read during a SELECT access could not be inserted into the
    target field.
    Either conversion is not supported for the target field's type or the
    target field is too short to accept the value or the data are not in a
    form that the target field can accept.
    Thanks and Regards,
    Kevin Yu

    Hi Kevin,
    this is probably caused by one or more incorrect / corrupt  entries in table VBSEGK.
    UMG_SCANNER reads the content of this table and is unable to do so for a specific  entry.
    Now it is necessary to find out, which entry causes this issue ...
    Maybe your colleagues from the according application (FI-GL-GL-X) can help you ?
    Best regards,
    Nils Buerckel

  • Error occured during extraction

    Hello Experts,
    I am using datasource 0HR_PY_PP_1 to load data into DSO 0PY_PP_C1.while loading data into DSO, I was getting error.
    When I checked data in extractor for 0HR_PY_PP_1, I got error messange "Errors occurred during the extraction"
    what would be an issue? do i need to do any setup before extracting data from extractor.
    Regards,
    Nirav Shah

    HI,
    Actually the data source you are talking about have some functional intricacies concerned with it , so if you could go through the below link for more information on it.
    [http://sap.ittoolbox.com/groups/technical-functional/sap-bw/extraction-error-for-0hr_py_pp_1-1376478]
    Check weather a valid source system exist for the concerned extractor RSA13 (Monitor icon), try replicating the data source again for the possible error conditions include specification of DataSources unavailable in the source system and changes in the DataSource setup or the extraction process that have not yet been replicated to the SAP BW system.
    Extractor checker will only let you check for the extraction of specific values in rsa3, try reactivating the extractor or check "For the short dump error if any" may be there is an "Enhancement of data source " while the extractor is not properly activated.
    Hope this will be expedite.
    Thax & Regards
    Vaibhave Sharma

  • Error occur during extraction

    Hi All,
    i am activate the bussiness content RSA5 : 0job_attr & ojob_text, but check in RSA6 warning error occur. check the data in RSA6 found : Errors occurred during the extraction.
    Check in log found that :The application program for the extraction of data was called up using
    the invalid InfoSource/invalid InfoObject 0JOB_ATTR.
    another error i am found : shortext medium text longtext non maintain language 'E'
    Regards
    Priya

    Hi,
    This problem is relted to HR Module ?
    RSA6 Delete the object. Again go to RSA5 bussiness content select 0JOB_ATTR ;> transfer datasource. before goto RSA5 , inform to the Functional consultant they maintain the shortext medium text longtext non maintain language 'E' for 0JOB_ATTR. becuse DE is maintain for the object before.
    Regards
    Sangram sutar

Maybe you are looking for

  • Can i filter my calendar?

    Is it possible to filter my calendar by anything other than the calendar list on the left? For example, I'm using this calendar to schedule and keep track of classes at different schools. So, I have a calendar for each school so that I can look at th

  • How to control RS232 Interface through LABView?

    Does LABView have the ability to control RS232 Interface? If it does, what version of LABView has this capability? The LABView versions that we have in the company are 7.2 and 8.1 only. The operating systems that we have are Windows and Linux.

  • How to import a *.dmp file (exported from 10g) to 8i database?

    Hi everybody! Could anybody tell me how to import a *.dmp file (exported from 10g) to 8i database? I have tried but it seemed to be error "wrong version". Thanks a lot!

  • Table disaster in Pages

    Pages 2 has a problem with tables, simple calculations work but can't be saved without a sintaxis error after reopening the document. Am I doing something wrong or is it terrible software iMac Intel   Mac OS X (10.4.5)  

  • XI Server Proxy Or Enterprise Service

    I need to call a BAPI in R/3  using XI. Possible Approaches:  1) Using RFC Adapter :  Performance Inferior (I do not want to discuss this) 2) Using Server Proxy  and calling the BAPI inside the method. 3) Exposing the BAPI as ES and consuming that us