Dump in production system

Hi Experts,
I got following error description in ST22.plz can anyone tell m
what will be the probable reason for this dump. How should i correct it?
Where i need to check?
Errore run-time DBIF_REPO_PART_ALREADY_EXISTS
Analysis:
Internal problem: You attempted to insert a program which already
exists partially at least. This is probably due to an inconsistency in the database tables.

hi Sheetal,
What happened is your Basis guy might have not imported this TR properly.
I will tell what would have been your scenario. There is a program in production.
You deleted that program in developement and recreated the same and you moved it to production under one TR. Correct me if I am wrong in any of above.
Just ask your Basis to import this TR with overwrite option checked.
Reward all useful answers.
Regards,
Atish

Similar Messages

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

Too many abap dumps in production system

gurus ,
i have a doubt . there was around 56 abap dumps by a single user .
i just want to know whether having these much of abap dumps in the production will hit performance system in a way or other ?
if so i can make alert them on the criticality of running a report in production .

"the problem is , most of the dumps are SYNTAX_ERROR which are generated by the customized reports created by the users"
Good! I much prefer them to the "there is something wrong with your system" type dumps.
"these people make a direct attempt in production directly resulting in lot of dumps .
we have a quality client with the latest production datas , but they dont do their first .
i am not sure whether this practice will really hit any performance issue .
if so then i can insist them the importance of being alert before making an attempt in production"
Bad, bad, bad practise.
As you have mentioned a QA system, I'm assuming that you have at least a 3 tier landscape ... tell the developers to use it!
p.s - the problem isn't so much that the users are running the reports directly in Prod, it's that the reports haven't been tested properly before they reach the Prod system !

Getting Dump in Production system

Hi,
we are getting dump in one customise program due to missing include program.
how to transport this missing program.?
regards,
Ramesh

Hi,
run tcode SE10 in DEV system.
click on create -> select workbench request -> enter description of request -> enter
now double click on request -> click change end enter following
In first row
Program ID: R3TR
Object Type: PROG
Object Name: name of include. press enter
in second row
Program ID: LIMU
Object Type: REPS
Object Name: name of include. press enter
then click on release.
import this request in PRD system.
regards,
kaushal

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

TSV_TNEW_PAGE_ALLOC_FAILED Dump in Production BW 3.5 system

Hi Basis Gurus,
In our production BW 3.5 system we are getting dump in ST22.
The dump is TSV_TNEW_PAGE_ALLOC_FAILED
Please let me know what could be the reason for this dump and why we are getting it.
I tried searching in service market place and there we can find lot of things related to this dump.But not sure which one is specificaly related to this dump.
Our system details are as follows
BW 3.5
Solaris OS
Oracle Database.
Please help me in resolving this dump.
Regards,
Anil.

Hello Anil,
what is the frequency of these dumps.
If the dump once in a while,you can simply ignore it
If frequency is more....you will need to reasrch a bit before increasing the paging memory as suggested previously
Just check what program is causing the dump,is it SAP standard program or a z program created by your developers.
If it is a SAP standard program just search on market place and look if any new version of the program exists which is tuned better and which consumes less memory
If it is a z program ask your developer to tune the program(this can be a highly cause of this dump as programs created usually consume a lot of memory due to which this dump occurs)
If none of these help,go for increase in the paging memory as previusly suggested
Rohit

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.

Short Dumps in BW Production System

Hi BW Experts,
When iam loading the PCA data (0PCA_C01), i am getting the following Short Dumps in my Systems.
DBIF_RSQL_SQL_ERROR
RAISE_EXCEPTION
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TABH_POOL_NO_ROLL_MEMORY
TSV_TNEW_OCCURS_NO_ROLL_MEMORY
SYSTEM_NO_ROLL
Today i got 131 Short Dumps in my System.
Please can anyone tell me the solution for this Short Dumps.
Thanks in advance
Regards,
Anjali

I am receiving the following Run time error in a Process Chain
Name of the runtime: System_NO_ROLL
*Information on where terminated*
     The termination occurred in the ABAP program "GP45O123XOQKIU82AMIR5C27RCN" in
      "ROUTINE_9998".
     The main program was "SAPMSSY1 ".
     The termination occurred in line 3255 of the source code of the (Include)
      program "GP45O123XOQKIU82AMIR5C27RCN"
     of the source code of program "GP45O123XOQKIU82AMIR5C27RCN" (when calling the
      editor 32550).
Source Code Extract
Line     SourceCde
3225     *delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3226     *** Move data package to internal table******************************
3227     *it_package[] = DATA_PACKAGE[].
3228     *SORT it_package ASCENDING BY CRM_ACGUID.
3229     *DELETE ADJACENT DUPLICATES FROM it_package
3230     *     COMPARING CRM_ACGUID.
3231     *ilookup[] = it_package[].
3232     *SORT ilookup ASCENDING BY CRM_ACGUID.
3233     ** if abort is not equal zero, the update process will be canceled
3234     * ABORT = 0.
3235
3236     * New code to get the Interaction id for Quick Close
3237     DATA : it_package like STANDARD TABLE OF DATA_PACKAGE.
3238
3239     delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3240
3241     it_package[] = DATA_PACKAGE[].
3242
3243     DELETE it_package where crm_prctyp <> 'Z260'
3244            AND crm_preotp <> 'BUS2000126'
3245            AND crm_predoc is INITIAL.
3246     SORT it_package ASCENDING BY crm_predoc.
3247
3248     DELETE ADJACENT DUPLICATES FROM it_package
3249         COMPARING crm_predoc.
3250
3251     SELECT CRM_ACGUID CRM_OBJ_ID FROM /BIC/AZ0SAL_D100 INTO TABLE ilookup
3252            FOR ALL ENTRIES IN it_package
3253            WHERE CRM_ACGUID = it_package-crm_predoc.
3254
>>>>>     SORT ilookup ASCENDING BY CRM_ACGUID.
3256
3257
3258

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.

CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test

Hello,
I'm getting the follwoing short dump in production when I run the program which writes the data to application server. I have open data set and close data set. Same program when I in development and test I do not get any short dump. Can any know what could be cause for this.
CX_SY_FILE_OPEN_MODE
Copy paste of error analysis from ST22 short dump -
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
     caught in
    procedure "DATA_UPLOAD_APP_SERVER" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    When accessing the file "/bw/FTPOUT/BPR/OTHER/test.csv", the system recognized
     that this file is
    not open. Therefore, the file cannot be accessed.

The file could not be OPENed in your production system for a variety of reasons - no authorization, file doesn't exist etc. You should have check sy-subrc right after OPEN DATASET and if not zero, yous should not TRANSFER or READ the file and instead you should have given a message with sy-msgid and sy-msgno which would give you the reason. The dump here is simply saying that OPEN is unsuccessful, so any subsequent READ or TRANSFER would throw runtime dump, if done after an unsuccessful OPEN.

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

Dump in production

hi floks,
We have created one new DSO and moved to Production system. When we did data load and try activating the request we are getting a short dump. The screen shots are attached here with.
We did not face any problems in D and Q systems. Please let me know if you need any other information on this.

Hi,
may be the data volume is high and also due to non availability of background process. Try reactivating the request in Prod.
Mostly it will occur due to no background process availability.
Let us know the details.
Reg
Pra

Dump in Production due to CALL_FUNCTION_OPEN_ERROR???

Hi all,
I am getting lot of dumps in Production with following details
What happened?
Error in ABAP application program.
The current ABAP program "SAPLOLEA" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An error occurred when executing a Remote Function Call.
"Protocol error when communicating with SAPGUI."
Status of connection.... "RFC DRV=GUI INPUT"
Internal error code.... "RFC_IO20"
When communicating with SAPGUI, a protocol error was detected.
Any have Idea for this ?

Dear Vipin
That is a very complicated error, difficult to analyze.
First I would recommend an update of the SAP GUI onto the newest patch
level. Additionally please update the SAP kernel to the latest patchlevel and the RFC libraries!
If that all should not help, deeper analyses are to be made so in your system.
For that you should then create a support message.
Best regards
Sven

Dump in production system

Similar Messages

Maybe you are looking for