CX_XMS_SYSERR_PERSIST dump coming in XI production system

hi,
we are having SAP PI 7.0 EHP 1 for NW7.0 with SP level 7.  from the last 3 weeks, we are getting too many CX_XMS_SYSERR_PERSIST dumps in our xi prd system. moreover we have seen some lookups not performing ok and giving dummy values if target value is not found even though target value exists. Please suggest what is the cause of this error and how to rectify it.

Hi,
Sometimes this is  happening due to  database issue.
Check your Short dump thru Tcode- ST22
Also try to activate the cache in IE and  CPA cache on the J2ee engine.
t might be the case that XI environment is on a SP that is non compatible.Just chk this issue .
It might be of because of a patch issue. take help of SAP Notes 864542 & 865467.
Apply the SP14 to resolve this issue  as this is resolved in that .
Regards,
Rohit

Similar Messages

  • Stopping idocs coming into XI production system

    Hi Frndz,
    We have XI production for the maintenance purpose, we have to stop only the idocs coming into and going out of the SAPXI system.
    So how to stop the idocs coming into the system keeping SAPXI system running(other traffic related FILE, JDBC, JMS etc....) ???
    <removed by moderator>
    Regards
    Sai Ganesh
    Edited by: Mike Pokraka on Jul 24, 2008 1:17 PM

    Hi,
    Adding to the Michal post, You can also do
    If you dont want to Push the Idocs to XI in future means, In R/3 We20--Change the Port( create dummy file port and assign it)
    If u want to post the Idocs to Xi means follow Michal Reply
    And also In reverse case while posting the Idocs to R/3, change the RFC Destination name in IDoc Receiver Adapter.The messages will be stay in XI in Errored state
    Afterwards if u want to push the Idocs From XI to R/3 means, change the RFC Destination name in Idoc receiver adapter and say Restart.
    Regards
    Seshagiri

  • Short dump "EXSORT_NOT_Enough_MEMORY" in production system

    Hi,
    "EXSORT_NOT_Enough_MEMORY" dump occuring in production system,Could any one please tell me how to fix this dump.
    Please refer the error message below
    What happened?
        The current ABAP program had to be terminated because the
        ABAP processor detected an internal system error.
        The current ABAP program "RSBPCOLL" had to be terminated because the ABAP
        processor discovered an invalid system state.
    Error analysis:
        The current ABAP/4 program was meant to sort a dataset (internal table
        or extract). For reasons of capacity, this was not possible due to
        insufficient main storage space. Therefore, the
        external sort was called and resulted in the following error:
        the following error:
        SAP runtime system internal error.
                   Last error logged in SAP kernel
        Component............ "EM"
        Place................ "SAP-Server cambsvr15_PEC_00 on host cambsvr15 (wp 12)"
        Version.............. 37
        Error code........... 7
        Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
        Description.......... " "
        System call.......... " "
        Module............... "emxx.c"
        Line................. 1886
    and i see that background job  "SAP_COLLECTOR_FOR_JOBSTATISTIC" job being failed with  below error.
    Job started
    Step 001 started (program RSBPCOLL, variant , user ID BACKGROUND)
    ABAP/4 processor: EXSORT_NOT_ENOUGH_MEMORY
    Job cancelled
    Please help me to correct this error.
    Best Regards,
    Vinod

    Hi Bhaskar,
    yes, I have checked the Wp status and it looks fine.I'm getting this error on My PRD system on regular basis since 1 week.
    We have tried to restart the server but no luck.
    Here are the ST02 values and background job SAP_COLLECTOR_FOR_JOBSTATISTIC also being failed with this error.
      Buffer              Hitratio    Allocated       Free space          Dir. size      Free directory        Swaps      
                              [%]         [kB]           [kB]      [%]      Entries       Entries    [%]                  
    Program                   99.11       400,000        1,481     0.38      100,000      90,774    90.77       36,307
    CUA                       99.31         3,000          264    10.53        1,500       1,263    84.20       14,934
    Screen                    98.45         4,297           27     0.82       10,000       9,653    96.53         645
    Calendar                  99.76           488          359    75.10          200          48    24.00         0
    OTR                      100.00         4,096        3,439   100.00        2,000       2,000   100.00         0
    SAP memory              Current use      Max. use  In memory   On disk
                            [%]      [kB]       [kB]       [kB]       [kB]
    Roll area              1.45      3,808     7,680    262,144         0
    Paging area            3.40      8,904     13,056       0        262,144
    Extended Memory        9.05    389,120    812,032  4,299,776
    Swaps
            0
       21,249
            0
       16,399
       36,307
       14,934
          645
            0
            0
          272
            0
      210,742
            0
    Please let me know if you require further information.
    Thanks & Regards,
    Vinod

  • Dump in production system :Incorrect status in pricing

    Hi All,
    We have patched out SRM5.5 server system recently with  15 and  16 patch.
    After the patch we are getting  many dums in production system.
    When i check in the ST22 ,the error syaing that
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
        therefore caused a runtime error.
        The reason for the exception is:
         *Incorrect status in pricing*
    How to correct the error
        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:
        "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
        "SAPLBBP_PDH" or "LBBP_PDHU08"
        "BBP_PD_ABORT"
        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
    and  i have checked the IPC ,it is also active only,.
    We have got his issue all of suddenlly,
    Can any one tell us what could be the issue.
    Regards
    cb

    Hi All,
    thanks a lot for your response ,
      I have done the  Simulation which shows everything is fine  and i have chcked with BBP_CND_CUSTOMIZING_CHECK  t-codes even that is also correct  only .
    we are plannning for rasing the issue with SAP.
    Besides that the system might have activated the BADI simple pricing active (or something like that). This would give trouble as well with the IPC (they can't both be active).
    @Robin which the badi we can check.
    once agina thanks a lot for your replys.
    Regards
    cb

  • Short dump in Production system !!!

    Hi Experts,
        We have getting a short dump for all actions in Production system. Suppose if we use se38 and tried to press display it shows a short dump error. Despite when we tried to use tcodes or using LSMW or try to execute a program or like this all type of actions its throws a short dump error. Dont know what is the reason behind that since the short dump is not the defined the reason for the dumb. Have any of you experts got this type of experience?. Pls give your ideas. Thanks in advance.

    Hello Kavi,
    Contact your basis team. SNAP is a table which holds all ABAP dump. It looks like SNAP table is full and cannot accomodate new entries.
    In any production enviornment, the SNAP entires will be deleted regularly and only dumps for the last 8 days will be available
    Check if any job(SM36 or table tbtcp) is running for this program RSSNAPDL in your production system.
    Thanks

  • Production system showing 40 Dumps with "MEMORY_NO_MORE_PAGIN"

    Hi All,
    My production system suddenly showing  around 40 dump with the below name "MEMORY_NO_MORE_PAGIN"
    Plz. Let me know in details how to resolve this issue.
    Runtime Errors         MEMORY_NO_MORE_PAGING                                     
           Occurred on     05/02/2007 at 14:06:35                                                                               
    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 50 of different IDs.                                                                               
    Please note:                                                                     
    To facilitate error handling, the ABAP/4 memory was                              
    deleted.
    Thanks & Regards,
    Kishore Reddy

    Hi Juan/All
    ST02
    Program Swaps  :   21,000 
    rest fine
    Memory
    SAP memory        Current     use      Max. use  In memory   On disk
    Roll area                  0.28      1,470     39,128    262,144    262,144
    Paging area             16.08    126,497    786,424    524,288    262,144
    Extended Memory     6.80    570,368  7,844,864  8,388,608
    Heap Memory                   0    206,430
    Thanks & Reg,
    Kishore Reddy

  • Very Urgent : Dumps Generated in Production System, reason unknown

    We are getting ABAP Dumps every second for some reason on the production system. The error analysis message is as follows :
    Error analysis
    The data type "MCVBAPB" was reloaded from the database while the program
    was running.
    However, the system found a version of the type that was newer than
    the one required.
    Any pointers to the reason for this will be helpful.
    Kindly contribute.

    Hi Booma,
    Probably structure MCVBAPB was changed (either directly or by importing a transport from the QA system). These structures are stored in buffers and users already logged on will work with these buffered structures. After the change/import the system will notice a difference between the structure in the buffer and the actual one and will dump.
    Normally this should only happen once for each user currently logged on. Any user logging on after the change should  not have this dump.
    Regards,
    John.

  • RFC_NO_AUTHORITY ABAP dumps coming very frequently

    Hello
    We are getting abap dumps in Production system and the details are below :
    RFC_NO_AUTHORITY
    ABAP dumps RFC_NO_AUTHORITY are coming very frequently in the Production system. The dumps are occurring for user ID "SOLM_REMOTE" in DBCI only. This dumps comes every hour from Sep to till date. Also in the short text it has mentioned, User "User "SOLM_REMOTE" has no RFC authorization for function group "TMW_TRACKING". The termination occurred in the ABAP/4 program "SAPLTMW_TRACKING " in "TMW_VERSION_TEST". The main program was "SAPMSSY1 ".
    Provided the RFC authorization for function group "TMW_TRACKING" for the user SOLM_REMOTE.
    The user SOLM_REMOTE has all the authorizations.From the authorization perspective everything seems to be fine.
    But still we are getting many RFC_NO_AUTHORITY abap dumps frequently in production system.
    Please help me in this regard.
    Many thanks in Advance.
    Regards
    Sreedhar Reddy.

    Hai,
    Please check the below link, it might help you.
    http://help.sap.com/saphelp_nw04/helpdata/en/4f/b541d812aea34695d54758cec0796f/frameset.htm
    Regards,
    Yoganand.V

  • Create a Support Message in Production system showing up in Solution Manage

    Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
    I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
    Thanks
    Paul

    Hi Paul
    The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
    Make sure your RFC's are trusted and that you have SAP ALL during config.
    I hope this will help:
    Setup Service Desk
    Steps to follow while configuring support desk.
    1) Implement the note 903587 .
    2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
    3) Check all the objects in the table BCOS_CUST using transaction SM30.
    Appl : OSS_MSG
    + :W
    DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
    + :CUST 620
    + :1.0.
    *4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
    4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
    4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
    4.3) Activation of the following components has to be done by replicating the previous steps
    3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
    3.2) SOLMAN40_SDESK_ACTIONLOG_001
    3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
    3.4) SOLMAN40_SDESK_TEXTTYPES_001
    *Depends upon the number of inactive BC set objects that we have after the upgrade.
    4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
    5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
    Number ranges for ABA notifications
    5.1) create an internal and external number range using transaction DNO_NOTIF.
    5.2) assign number range intervals to groups internal and external.
    5.3) SLF1 is the internal number range group
    5.4) SLF2 and SLF3 is the external number range interval
    5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
    5.51) Go to transaction DNO_CUST01
    5.52) From the GOTO menu select the menu item DETAILS
    5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
    The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
    Number ranges for Support Desk notification
    5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
    5.6) Then assign both the external and internal numbering
    5.61) Go to SPRO and then to SAP Solution Manager
    5.62) Then select General Settings and then select Transaction types
    5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
    5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
    5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
    6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
    6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
    6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
    7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
    8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
    8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
    8.2) Select the item Service Desk and then to general settings.
    8.3) Execute the category u2018Define Transaction Typesu2019.
    8.4) Select the transaction type as SLFN
    8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
    9) Activate the partner/ Organization
    9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
    9.2)Find the entries starting with HRALX
    HRALX-HRAC WITH VALUE 'X'.
    HRALX-OBPON WITH VALUE 'ON'.
    HRALX-PBPON u2018ONu2019.
    HRALX-MSGRE u2013 u20180u2019.
    9.3) If entries are not found create it.
    10) Generate Business partner screens
    10.1) Go to transaction BUSP.
    10.2) Execute the report with the following parameters
    CLIENT - Client in which business partners should be created (solution manager client)
    APPLICATION OBJECT-
    SCREEN - *
    Generate all/ selected screens - All screens.
    delete sub screen containers -
    11) implement SAP note 450640.
    11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
    11.2) Execute it with test mode box unchecked.
    If a new relationship is to be created then steps 12 and 13 has to be followed
    12) To create a relationship category
    12.1) Go to transaction BUBA
    12.2) Select the entry CRMH00: Undefined relationship
    12.3) click on copy
    12.4) Rename CRMH00 to ZCRMH00.
    12.5) CREATE A RELATIONSHIP CATEGORY.
    IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
    ' FROM BP2 : IS A PART OF ATTUNE
    13) Add the relationship category to the support team partner function
    13.1)Use SPRO
    IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
    -> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
    13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
    13.3) In the field relation ship category, Select the newly created relationship category and save.
    14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
    15) Create a new access sequence for the support team determination
    15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Configuration ->
    -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
    ->Define Access Sequence
    15.2) Click on New Entries
    15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
    15.4) Create an new Individual Access with the following value:
    u2022 Batch Seq: 10
    u2022 Dialog Seq : 10
    u2022 Source : Business Partner Relationship.
    u2022 Detail on the source:
    u2022 Partner Function : Reported By (CRM)
    u2022 Mapping/restrictions
    u2022 Flag Mapping/definition for partner being Searched
    u2022 Partner Function in Source: Support Team (CRM).
    Save it.
    This Access Sequence will give us the Partner which has the relationship assigned
    to the Support Team in the Reported By partner data.
    16) Adapt the partner determination schema/Function
    16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
    -> Partner Determination Procedure -> Define Partner Determination Procedure.
    16.2) The two options to adapt partner determination schema are
    16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
    16.22) select the line starting with SLFN0001 or the newly created procedure.
    16.23) Double Click on Partner Function in Procedure.
    16.24) Select the Partner Function "Support Team", and click Details.
    16.25) in the detail view only change the Partner Determination/access Sequence to
    the one we've just created. Save your entry.
    17) Create a root organizational model.
    17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
    17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
    17.3) enter the organizational unit, the description and save it.
    18) Create the support team organization
    18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
    19) Create the business Partners.
    19. 1) Key users- End user (Business Partner General) ,Address should be specified.
    19.2) go to the transaction BP.
    19.3) create a new Person, Select the role: Business Partner (Gen).
    For Identification of the key user
    19.31) click on the identification tab
    19.32) enter a line in the identification number formatted as follows
    IDTYPE : CRM001.
    Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
    eg: USER NAME : USER1.
    CLIENT : 100.
    SID : ER1.
    INSTALL NUMBER : 123456789.
    IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
    20) Message Processors- Support Team members .
    20.1) they should be created first as the users in the corresponding client of the solution manager.
    20.2) As business partners they will have the role 'EMPLOYEE'.
    20.3) Go to transaction BP .
    20.4) Create New Person with the role employee.
    20.5) In the Identification tab you should enter the user name in the employee data/User Name.
    eg: username: proc1
    enter proc1 in the field User name.
    21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
    22) Assign the business partners (Message Processors) to the previously created support team.
    22.1) Go to transaction PPOMA_CRM.
    22.2) Select the support team 1.
    22.3) Click on create
    22.4) select position
    22.5) call it 'MPROC_T1/Message Processors for team 1
    22.6) Replicate it for the other support teams.
    22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
    choose owner/Business Partner find and select the business partner
    22.8) Validate and Save it.
    22.9) If the assignment of business partner is not possible then implement the note 1008656
    Or 997009
    23) Create the iBase component
    23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
    23.2) or use the transaction IB51 to create the installed base.
    23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
    24)Assign Business Partners to iBase Components
    IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
    -> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
    *--optional--
    If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
    Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
    Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
    Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
    now to assign the partner Function "System Administrator".
    25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
    26)Define the transaction variant for the message processors
    Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
    Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
    27) Go to transaction PFCG
    27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
    27.2) Give a description Message Processor role and save it.
    27.3) Go to the menu tab and choose add report
    27.4) select the report type : ABAP Report
    27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
    27.6) Enter the previously created variant.
    27.7) flag the skip initial screen box.
    27.8) flag the SAPGUI for windows.
    27.9) Create a new transaction with tcode starting with Y or Z.
    27.10)Display this transaction and check the values at the bottom of the screen
    in the subscreen Default Values, you should have the following parameters:
    u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
    u2022 D_SREPOVARI-NOSELSCRN = X
    And also all the user should have the correct role.

  • Fetch data from a table present in production system

    Hello Gurus,
    I want to get data from a table which is present on production system. And i cannot create RFC. Can anybody tell me any other way of getting the data?
    Thanks in advance!!
    Regards,
    Kumail

    Hi,
    if it's just a one time requirement to get the data from the table into an excel sheet e.g. for some error analysis or for making a development decision, why bothering with development? Just run se11 or se16 display the whole content and save it as excel sheet via the menu. This would be the fastest solution in my opinion.
    If you do not have the permissions to see the table in production ask a admin or super user. Creating a program to dump data from the system you are not really allowed to see usually brings you in a lot of trouble :o).
    Kind Regards
    Roman

  • Early Delta Initialization option in Production system

    Hi Experts,
    I have seen some threads related to Early Delta initialization in this forum. I have a question regarding this option.
    To minimize the downtime/block users in the R/3 production system during set up tables fillup I would like to use the Early delta option. Please give your suggestions on the following procedure:
    For Sales Orders, billing and Deliveries
    1. Initialize Early delta in the BI system.
    2. Go and fill setup tables
    3. Do a full load to BI
    4. Run delta job in R/3 (LBWE)
    5. Run delta job in BI Info package
    Do we miss any documents in this process for e.g. during set up tables fill up changes to existing documents or newly created sales orders.
    I feel we won't miss. All changes will be reflected in Delta queue. And even newly created orders also will be coming to delta queue.
    Please let me know if I am wrong.
    Thank you.

    Need Clarification on this thread,
    According to my understanding, during the filling of set up table if a user does any posting, then the data available in BW will be incorrect.
    am i right?
    In your sequence the 4th step
    4. Run delta job in R/3 (LBWE),     this means you are using queued or unseriallized v3 update.
    Early delta iniliazation essentially of no advantage because, as conventional initialization procedures, you can readmit document
    postings after successfully filling the setup tables.
    can anybody clear my doubt. is it possible during setup table filling user can post a document.
    I know the documents will be collected in the queue. But the data loaded to bw will be incorrect right?
    Regards,
    Anand.
    Edited by: araj123 on May 26, 2010 11:41 AM

  • IDOCs error in Production System

    Hi Gurus,
       In Production system, there is a CRM oppertunities process chain is running on hourly basis, the data was updated to DSO successfully, but for the past one week it was not updating to further processing InfoCube, there is an error.
    error:  Idoc Ready to be transferred to application.
    Please update me step by step procedure.
    Thanks

    Hi,
    Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
    See Dumps in ST22, SM21 also.
    Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
    You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
    S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
    And also check the following things.
    1.Connections from BW to ECC and ECC to BW in SM59
    2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
    3.Check Dumps in ST22, and SM21.
    4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
    5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
    See in SDN
    Re: Loading error in the production  system
    Thanks
    Reddy

  • Data cleanup for customtables in production system.

    Hai,
    My requirement is  a list of custom tables data should be deleted in production system based on some selection-criteria.
    Any one can suggest how we can achive this.
    Shall I write any Zprogram or any other way.
    I have written code for one table .
    Reprot ZTesdel.
    Tables :  YDCS_COMP_CR.
    DATA itab1 type STANDARD TABLE OF YDCS_COMP_CR.
    SELECT * FROM YDCS_COMP_CR INTO TABLE ITAB1.
    DELETE YDCS_COMP_CR from table ITAB1.
    Please any one can tell the same code will work for deleting records from YDCS_COMP_CR or any other piece of needs to added?
    Regards,
    Krishna

    Depending on the nature of the data, there might be a legal retention period to be observed.
    Also check for dependencies to other tables, foreign keys, so you don't end up with a corrupt database.
    If it is data in the GB range, don't delete in one chunk, or the redo buffers might overflow. Instead fetch packages of x records, delete them and do a commit work before reading the next package. Use OPEN CURSOR WITH HOLD and function DB_COMMIT for this purpose.
    Thomas
    Edit: just saw this is a continuation of
    custom tables data deletion (data cleanup)
    zprogram to custom table data deletion
    Please now work with the information provided so far before coming back with more questions.

  • Problem with Delta IP on 0TCT_DS23 in Production system

    Hi all,
    I'm encountering a quite tricky problem: I'm currently working on the 0TCT_DS23 Datasource, with the technical content cube.
    I can run an init infopackage on our 3 environments, Dev, Quality and production. Same for full packages. But when I try to run a delta IP, it is failing on the production system, with a dump of the extractor.
    Looking at ST22, it's saying that there is
    a syntax error in program "/BI0/SAPLQI0TCT_DS23 ".
    Causes
        Error in the ABAP Application Program
        The current ABAP program "SAPMSSY1" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "/BI0/SAPLQI0TCT_DS23 " in
         include "/BI0/LQI0TCT_DS23$02 " in
        line 7:
        "A FUNCTION already exists with the name "/BI0/QI0TCT_DS23"."
        The include has been created and last changed by:
        Created by: "SAP* "
        Last changed by: "******"
    When browsing the program, it's really the case, in the include   /BI0/LQI0TCT_DS23UXX, there are 3 includes,
    *   THIS FILE IS GENERATED BY THE FUNCTION LIBRARY.             *
    *   NEVER CHANGE IT MANUALLY, PLEASE!                           *
    INCLUDE /BI0/LQI0TCT_DS23U01.
                        "/BI0/QI0TCT_DS23
    INCLUDE /BI0/LQI0TCT_DS23U02.
                        "/BI0/QI0TCT_DS23
    INCLUDE /BI0/LQI0TCT_DS23U03.
                        "/BI0/QI0TCT_DS230001
    The U01 and U02 are containing the same function, so it's failing.
    Do you ever have encountered the same problem, and if yes, how to solve it ? It already tried to reactivate the DS, but no way.
    Thanks in advance
    Frederic

    Hi, Ralf
    Thanks ! It worked ! I had to repair the function module. I assigned the points
    Edited by: Frédéric GAUTHIER on Jan 29, 2010 11:12 AM

  • SAP Production Systems Database backup failed

    Dear Guru,
    I have been facing a problem with our SAP Production system's oracle database backup for last three days. Our back up goes through TSM server. At night 10 pm we have schedule backup for whole offline + redo log backup,  11 pm check and update optimizer statistic and at 11:30 pm Check Database. For last three days above mentioned backup getting failed and we are not able to get such a details log by which i can understand the issue. But Our Development server and Quality server's backup which are scheduled at 12 am and 2 am, the both backup schedules finish successfully. And in morning all schedule backups of Production systems finish without any errors. The issues is coming only with Whole database backup + redo log Backup which schedule at night 10 pm. I have mentioned the log whatever i have got in below:
    07.02.2012     07:30:06     Job started
    07.02.2012     07:30:06     Job has exceeded its latest start date
    07.02.2012     07:30:06     Job cancelled after system exception ERROR_MESSAGE
    Above mentioned logs are showing 1day advance log where i have mentioned yesterdays log. That means it should shows 06.02.2012 instead of 07.02.2012 and time should be 22:00:00 instead of 07:20:06.
    Our Oracle version is 10.2.0.4.0/ kernel release 701/BRBACKUP 7.00 (40)
    Please Guide me.
    Regards,
    Samrat Chakraborty

    OK,
    this has nothing to do with brbackup or TSM.
    You batchjob starts at 07:30 !!!
    Means before that, you do not have any action at all.
    Then the job crosschecks it has passed its intended startdate and terminates,
    which is correct, since you do not like brbackup to shut down your DB at 07:30!
    No brbackup is started at all, which is why you get no log and no tsm connect takes place.
    I assume,  you misconfigured some operationmodes and at 07:30 an OP-modeconfiguration
    with batchjobs switches back in place so that the jobs do start too late.
    Check RZ04 and the OP mode timetable
    If it is not this, it has to be something else with the batch scheduler causing delay
    or may be all BTC processes are busy, but this seems unlikely with a start at 07:30 sharp..
    Volker

Maybe you are looking for