Delete BP in solution manager
Dear friends,
i have a small problem. there are so many unnecessary business partners have been created in solution manager. now i want to to delete them but there is not an option to delete in the program. please tell me how can i delete BP in solution manager.
thanks a lot.
You may run report BUPA_TEST_DELETE without any option.
Prerequisite: Business Partner is not used in any crm documents/transactions.
/cheers
Similar Messages
-
Retrieving Deleted Documents in Solution Manager
Hello
Some documents where deleted via the DELETE ROW button under the Configuration Tab in tcode SOLAR02. However, we want to know if there is a way to retrieve these delete documents.
Also i want to know which table stores these documents. Please respond soon.
Regards
BalarkaBalarka
First goto transaction
Solar01 and from the SAP menu Business Blueprint->Find document.
Enter the name in the query for the lost document or directly press enter( also,can remove project name from selection criteria).
You wil get the list of all documents present.The doc which are removed from project can also be seen here.
Can switch on trace for getting the table.
Remember if you have press Minus button doc wil be there in knowledge warehouse and listed here.
But if you have Press Delete symbol it means it is permanently deleted.
Hope it helps
Regards
Prakhar -
Deletion of Business partner in Solution Manager
Hi
We have created the Business partner in solution Manager not able to
delete the Business partner.In transaction BUPA_DEL, when we select
Test run Check only, system gives the message like Business partner can
be deleted,but when we select other fields and execute,we get message
like No business partner deleted.
Regards
CharanHi charan,
Just in case if u have missed any of the below notes...
Note 835936 - Business partner cannot be deleted/archived
Note 415007 - Deletion of business partners
Let us know if u have any help from these....
VBr,
Sri
Award points for helpful answers -
Archiving/Deleting Test Messages in SAP Solution manager
Hi,
We have configured Service Desk in our solution manager 7.0 with EHP1 system.
We have created test messages to test the configuration.
We need to delete these test messages which are appearing in T Code CRM_DNO_MONITOR.
We run the report "CRM_ORDER_DELETE" but the output is
Deletion of CRM Documents
The following document could not be deleted: 8000000259
Not possible to delete, a reference exists to a subsequent document
Number of documents deleted: 0
Number of documents not deleted: 1
So
We have followed the "Note 1329247 - Archiving Solution Manager Service Desk messages".
1)
a)Call transaction DNOTIFWL and set the deletion flag for the Service Desk message. The deletion flag corresponds to the system status I1076 (deletion flag).
b) Execute the report Z_DELETE_BASIC_NOTIFICATIONS
The above step we have executed successfully.
2)
In CRM
You cannot delete a service process in CRM. The service process must be archived.
Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
a) Initial run Report CRM_ARC_SERORD_CHECK
b) Write run Report CRM_ARC_SERORD_SAVE
c) Delete run Report CRM_ARC_SERORD_DELETE
in SARA T Code we have typed archiving object CRM_SERORD.
After this what to do??? How to proceed further.
Can any body suggest us the step by step procedure to archive these test messages.
Regards,
Raj> In CRM
> You cannot delete a service process in CRM. The service process must be archived.
> Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
> a) Initial run Report CRM_ARC_SERORD_CHECK
> b) Write run Report CRM_ARC_SERORD_SAVE
> c) Delete run Report CRM_ARC_SERORD_DELETE
>
> in SARA T Code we have typed archiving object CRM_SERORD.
> After this what to do??? How to proceed further.
You need to schedule a BGD job to execute this. You can do this from the SARA screen itself, clicking on the 'Job' button. Please refer:
http://help.sap.com/saphelp_crm50/helpdata/en/e6/c66f3b6c980c3be10000000a11402f/content.htm
Rajeev -
How to delete Job Documentation in JSM Solution Manager
Hi,
I am trying to define some job documentation in "JSM Solution Manager", how can I delete unwanted Job Documantation there.
Don't see any remove button.
Thanks for help
sahmadHello,
We too are facing same issue. Can you please share your solution.
Regards,
Mudasir. -
Solution Manager delete option
Dear friends,
I am working in Solution Manager 4.0. In SOLAR01, under "project documentation" tab, we are having two delete options.
They options are:
1. Delete row
2. Delete
Assume that, i have uploaded one document in "project documentation' tab.
I can restrict the deletion of that document by second option (Delete), in authorization object S_IWB.
But the user can delete the document by using first option (delete row).
Could any one suggest, which authorization object holds the authrization for restricting "delete row"?
Even i have tried with authorization object S_GUI. In this object(S_GUI) i could not find "delete" activity.
Please guide me, how to arrest both deletion options for a particular document.
Thanks
SenthilHi Kumar,
As per my knowledge as of now, you can not just restrict the delete option in your project from Proj Documentation tab.
There is a workaround still available. It may not sound very good option but you will get the required result of control on delete in <i><b>General Documentation</b></i> tab instead of <i><b>Proj Documentation</b></i> tab.
1. Create a template project first. And add the documentation in its General Documentation tab in SOLAR01 transaction.
2. Use this template project for you implementation project.
3. In the Implementation project, the documents from Gen Documentation tab can not be edited or deleted. If it is required to edit, there is an
option of Copy/Link to Proj Docu tab for the selected document. Hence you can restrict to change the original document.
Hope this helps you.
PS If the answer solves your query, plz close the thread by marking it Solved & rewarding each reply.
Regards -
Mass Delete of Solution Manager Documents
Hi
We have a requirement in our project to mass delete documents ( some 4000+ ) . Is it possible
Ideally I would like to filter them with SOLAR_EVAL based on attributes and then do mass delete.
Any pointers will really be appreciated and rewarded
Regards
JagHi Jagmohan,
Sorry I dont have a direct answer myself.
However, all I can say is there is no such direct facility available in SolMan.
The procedure for mass document deletion should be much similar to the need for mass upload and perhaps met only by ABAP development.
[This|Mass Upload documents to Solution Manager; thread could help you to some extent.
Best regards,
Srini -
Early watch Report deletions from archive queue in Solution Manager
Hi Experts ,
I am working on Solution manager EHP1 (SP24). Here more than 100 satellite systems are connected .
and every week approximately 100 Early watch reports are getting generated into the system .
Is there any way to delete the early watch reports from the archive queue of the system which are 6 months
older.
A quick help is highly appreiciable
Thanks,
Kamal Kumar>
Kamal Kumar wrote:
> I am working on Solution manager EHP1 (SP24). Here more than 100 satellite systems are connected .
> and every week approximately 100 Early watch reports are getting generated into the system .
>
> Is there any way to delete the early watch reports from the archive queue of the system which are 6 months
> older.
Hi Kamal,
Have you already tried report RDSMOPREDUCEDATA
It offers the deletion of service session, documents and download data.
Best regards,
Ruediger -
Delete the old CUA and build a new CUA on the Solution Manager
Hello together,
I'm about to delete the old CUA and build a new CUA on the Solution Manager.
The users are in multiple systems almost the same.
This raises the following questions:
If I export the printers from the old CUA in a file and import into the new CUA (Solution Manager, then the printer can be administered directly in Solman?
Furthermore, if I depended on the second or third child System and attached to the new CUA, the user description data are not overwritten, as bsp: with the description data of the last-connected system?
By delete the CUA child system in which users are blocked. Can you handle it?
I thank you in advance
Mirsad> If I export the printers from the old CUA in a file and import into the new CUA (Solution Manager, then the printer can be administered directly in Solman?
-->the assignment of printers, not the printers themselves of course....
> Furthermore, if I depended on the second or third child System and attached to the new CUA, the user description data are not overwritten, as bsp: with the description data of the last-connected system?
If you mean adress data, already existing adresses are not overwritten. Such users will show up in scug as 'identical' or different' and can be handled accordingly.
> By delete the CUA child system in which users are blocked. Can you handle it?
Users without assignement to the central system get a global lock if the cua is removed in the central system. They still exist in usr02 in the central system, but with the global lock flag as indication, that they existed only for adminstrative means. The local lock flags in the child systems stay untouched. So if you take over these users into the new CUA they get the correct lock flag form the child system.
b.rgds, Bernhard -
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
PaulHi 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. -
Setting up EarlyWatch in Solution manager
Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1. Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2. Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3. Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4. Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5. This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6. I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors SYNTAX_ERROR
Date and Time 24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr = po_ctnode->versnr.
2117
ls_stdparameter-grp = po_ctnode->grp.
2118
ls_stdparameter-id = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp = pf_grp.
2124
ls_stdparameter-versnr = pf_versnr.
2125
ls_stdparameter-reference_grp = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event = pf_event ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number = ls_actrel-action
2140
importing
2141
pf_form_name = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod. "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event ne space )
2157
or exec_time = gf_exec_time_1
2158
or exec_time = gf_exec_time_2
2159
or exec_time = gf_exec_time_3
2160
or exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLDSVAS_PROC LDSVAS_PROCCD0 2146
EXECUTE
10 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2025
LCL_SESSION=>EXECUTE
5 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1995
LCL_SESSION=>EXECUTE
3 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 303
DSVAS_PROC_SESSION_OPEN
2 METHOD CL_DSMOP_SOLUTION=============CP CL_DSMOP_SOLUTION=============CM01P 184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT RDSMOPBACK_AUTOSESSIONS RDSMOPBACK_AUTOSESSIONS 72
START-OF-SELECTION
Chosen variables
Name
Val.
No. 11 Ty. FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION 00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 10 Ty. METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION 00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store = 0x807E0D3E |
| ext1 = 0x00000000 |
| shmId = 0 (0x00000000) |
| id = 1911 (0x77070000) |
| label = 3668 (0x540E0000) |
| fill = 1 (0x01000000) |
| leng = 44 (0x2C000000) |
| loop = -1 (0xFFFFFFFF) |
| xtyp = TYPE#000007 |
| occu = 16 (0x10000000) |
| access = 4 (ItAccessHashed) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 1 (ItUnique) |
| keyKind = 3 (user defined) |
| cmpMode = 8 (cmpManyEq) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0xC0AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x78F10D3E |
| shmTabhSet = 0x00000000 |
| id = 2504 (0xC8090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 16 (0x10000000) |
| lineAlloc = 16 (0x10000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = Not allocated |
| collHook = Not allocated |
| ext2 = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No. 8 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 7 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store = 0x68550D3E
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1919 (0x7F070000)
label = 3674 (0x5A0E0000)
fill = 26 (0x1A000000)
leng = 8 (0x08000000)
loop = 384 (0x80010000)
xtyp = TYPE#000029
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB0B10D3E
pgHook = 0xF0882E3E
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 2508 (0xCC090000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No. 6 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No. 5 Ty. METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store = 0x90C50D3E |
| ext1 = 0x30F3DE3D |
| shmId = 0 (0x00000000) |
| id = 1920 (0x80070000) |
| label = 3670 (0x560E0000) |
| fill = 1 (0x01000000) |
| leng = 100 (0x64000000) |
| loop = 264 (0x08010000) |
| xtyp = TYPE#000094 |
| occu = 1 (0x01000000) |
| access = 1 (ItAccessStandard) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 2 (ItUniqueNon) |
| keyKind = 1 (default) |
| cmpMode = 2 (cmpSingleMcmpR) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0x08AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x00000000 |
| shmTabhSet = 0x00000000 |
| id = 2505 (0xC9090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 1 (0x01000000) |
| lineAlloc = 1 (0x01000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = 0xB0F0BE3D |
| collHook = 0x00000000 |
| ext2 = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No. 4 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No. 3 Ty. FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USERPlease replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur. -
Error while installing solution manager 7.1
Hi All,
I am installing SAP Solution Manager 7.1 SR1 i am facing below issue ,any one please suggest me how to proceed further.I am new to sybase .
An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > SAP ASE > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS.
import_monitor.java log:
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.016)
SAP Java Server VM (build 4.1.016 1.6-b03, Dec 31 2011 00:41:53 - 41_REL - optU - windows amd64 - 6 - bas2:164914 (mixed mode))
Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
import_monitor Log:
INFO: 2014-07-01 10:49:48
Import Monitor is started.
CONFIG: 2014-07-01 10:49:48
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 10:49:48
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 10:49:48
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 10:49:48
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 10:49:48
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 10:50:18
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 10:50:18
1 error(s) during processing of packages.
INFO: 2014-07-01 10:50:18
Import Monitor is stopped.
INFO: 2014-07-01 11:09:16
Import Monitor is started.
CONFIG: 2014-07-01 11:09:16
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 11:09:16
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 11:09:16
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 11:09:16
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 11:09:16
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 11:09:46
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 11:09:46
1 error(s) during processing of packages.
INFO: 2014-07-01 11:09:46
Import Monitor is stopped.
NOTE:
The same issue has been solved in SCN Thread http://scn.sap.com/thread/3360385. As suggested in that note i am trying to look into the sap note
Note 1716201 - SYB:Update control.xml files for installation: Sybase ASE
in service market place but it is displaying as Document not released.
Kindly can any one help me in provind the above mentioned note or help me how to resolve this issue.
Regards,
SURYA.HI Divyanshu,
Below is the SAPNTAB.log:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1680
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL SAPNTAB.TSK SYB -l SAPNTAB.log
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job completed
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1904
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) INFO: SVERS created
(IMP) INFO: import of SVERS completed (1 rows) #20140630211544
(DB) INFO: SVERS~0 created
(DB) INFO: DDNTF created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF~0 created
(DB) INFO: DDNTF_CONV_UC created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC~0 created
(DB) INFO: DDNTT created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211555
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701104948
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2304
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701104959
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701110916
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2056
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701110927
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701120231
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2288
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701120242 -
Questions on "FAQ - SAP Solution Manager for VARs"
Hi,
I just got through the FAQ - SAP Solution Manager for VARs, but have some further questions:
For me it is not quite clear which connections are necessary for which VAR scenrio.. currently we have setup the service desk in our solman. Customer's aren't linked to the solman yet - we have saprouter-saprouter connections. Connecting them via SAP support backbone is an interesting option, especially for incident management. To get this working we should follow note 1124718 right?
But what about the other scenarios like maintenance optimizer and ewa monitoring? I guess for that we definitly need to build up RFC connections to each relevant customer system (~300+x)?! I think it will be hard to handle so many connections - just consider if a customer is cancalling the maintenance contract, everything needs to be removed again... best would be to have a central communication point...
For MOPZ we need up-to-date system information. So everyone is talking about SLD. Do you also recommend this option? There we need again a connection (direct to SolMan SLD or via external SLD on customer side).
According to the FAQ there is a workaround for ewa monitoring for customers with security doubts.. is this also working for non-ABAP components? We need SMD and WI for generating ewas for JAVA systems...
With regards to Enterprise Support contract: ewa only need to be monitored for productive systems? Can a customer be charged if they want to have ewas monitored for other sytems too? How long do we need to keep the ewas (1 month, 3 months, half year) before they are deleted? Are there any specific requirements?
All the work to get these scenarios working.. is this covered within the Enterprise Support contract? Can the customer be charged for work thats done by the VAR in their system (e.g. RFC connections, SDCCN, SLD,...)?
Sorry for this long text.. hope you have some helpful ideas!
Regards,
RichardHello Richard,
(1) regarding network connections see document [Draft:Technical Support Network Connections for VAR Scenario|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000880802009E] as overview and with a lot of detailed information.
(2) yes, you have to setup once all your customer connections at the beginning but then only add/remove with customer contract changes
(3) the workaround by sending by email can handled a anexception. EWA has to be done for productive systems like nowadays done by SAP. Additional EWA services could meas additional business case for a VAR - that's contract between VAR and customer.
(4) whatever you think may be a business to sell - do it ! (and get a monetary bonus from your boss
Kind regards
Heinrich -
How to maintain a common document in solution manager
Gurus ,
we are in the process of configuring service desk . One major type of support message we receive is user creation /modification .
currently we maintain these details in an common excel sheet . if a new requirement is made they take the latest modified excel sheet and mark the changes in them .
But now what we need in , we need to maintain this document is solution manager server .
and the users can access the document , make changes , save it and upload it back to the server .
any of you have any suggestions on implementing the sameHello Susin,
User Creation / Deletion / Modification is a Change in the system. It cannot be handled via a standard central document like a Excel on a datshare.
Solution Manager is not a content repository to be used for storing such documents. There is no way that you can acheive it as a standard process.
Probably what you can do is as follows :
- Create a table structure in Solution Manager and assign it colums as needed.
- Then write a ABAP Code to access and maintain this table Structure.
- Assign a transaction code to the ABAP Code so that it can be accessed by different users.
I hope that the reply helps.
Regards
Amit -
Dump (Raise exception) in Solution Manager
Hi experts ,
We are getting dumps from Satellite system into the Solution manager system. And the user respossible for the dump
is ALERT_<SID of Satellite System>. All the RFC have been checked . Central Auto reaction methods are assigned from
Solution manager to Satellite system. And checked that Auto reaction methods are not responsible for dump
SOLMAN_CEN_ALERT Destination is also checked in Satellite system.
Please assist
DUMP Details :
A RAISE statement in the program "CL_ABAP_TYPEDESCR=============CP" raised the
| exception
| condition "TYPE_NOT_FOUND".
| Since the exception was not intercepted by a superior
| program, processing was terminated.
User and Transaction
| Client.............. 100
| User................ "ALERT_SID"
| Language Key........ "E"
| Transaction......... " "
| Transactions ID..... "XXXXXXXXXXXXXXXXXXXXXXX"
| Program............. "CL_ABAP_TYPEDESCR=============CP"
| Screen.............. "SAPMSSY1 3004"
| ScreenLine.........2
| Information on caller of Remote Function Call (RFC):
| System.............. "SID"
| Database Release.... 700
| Kernel Release...... 700
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
| Call Type........... "synchron and transactional (emode 0, imode 0)"
| Inbound TID.........." "
| Inbound Queue Name..." "
| Outbound TID........." "
| Outbound Queue Name.." "
| Client.............. 100
| User................ "WF-BATCH"
| Transaction......... " "
| Call Program........."SAPLSALRT_CREATE_LOCAL"
| Function Module..... "SALERT_CREATE"
| Call Destination.... "SOLMAN_CEN_ALERT"
| Source Server....... "Satellite System hostname"
| Source IP Address... "XX.XX.XX.XX"
Source Code Extract
|Line |SourceCde
| 53| read table admin_tab from admin_tab_line into admin_tab_line.
| 54| if sy-subrc = 0.
| 55| p_descr_ref ?= admin_tab_line-ref->get( ).
| 56| if p_descr_ref is bound.
| 57| return.
| 58| endif.
| 59| delete table admin_tab from admin_tab_line.
| 60| endif.
| 61|* create new descr object
| 62| case admin_tab_line-kind.
| 63| when kind_elem.
| 64| raise event create_elemdescr
| 65| exporting xtype = admin_tab_line-xtype.
| 66| when kind_ref.
| 67| raise event create_refdescr
| 68| exporting xtype = admin_tab_line-xtype.
| 69| when kind_struct.
| 70| raise event create_structdescr
| 71| exporting xtype = admin_tab_line-xtype.
| 72| when kind_table.
| 73| raise event create_tabledescr
| 74| exporting xtype = admin_tab_line-xtype.
| 75| when kind_class.
| 76| raise event create_classdescr
| 77| exporting xtype = admin_tab_line-xtype.
| 78| when kind_intf.
| 79| raise event create_intfdescr
| 80| exporting xtype = admin_tab_line-xtype.
| 81| when others.
| 82|* all others are erros
|>>>>>| raise type_not_found.
| 84| endcase.
| 85| endcase.
86
| 87| create object admin_tab_line-ref exporting oref = returning_ref.
| 88| insert admin_tab_line into table admin_tab.
| 89| p_descr_ref = returning_ref.
| 90| clear returning_ref.
91
| 92|endmethod.
KamalHi Kamal,
I recommend to open a ticket for SAP with the runtime error attached.
Best regards,
Andreas
Maybe you are looking for
-
Unable to extract data from an AS/400 system.
Hello experts. We are trying to extract data from an AS/400 system but not having any success until now. I´ll write down you the stepts that we have followed until now: 1.- Create a DB Connect between both systems 2.- Create a Source System from AS40
-
Hello. After hooking up my ipod to my stereo, it has now begun to have muffled sound and static noises when the wire is twisted. It is not a bent headphone pin issue as there was no trauna to induce such. Could I have a fried sound processor, or some
-
Oracle tables to store the data for Run Depreciation in Fixed Assets
Hi All, When we do Run Depreciation without closing the period, what backend tables store this information that the Depreciation is run without closing the period. I have to apply a logic in one of my package, which would be applied only if prelimina
-
Hello I am looking to deploy a NAC device in our office and currently have an ACS server that handles wireless authentication. I would like to know if the ACS is capable of authenticating users on a LAN with both 802.1x and device detection (such as
-
Enlazar diferentes pdf interactivos
Hola, estoy creando un libro interactivo en indesign. Mi problema es el siguiente, tengo archivos separados por capítulo. El primer archivo es donde encontramos el índice, este me tiene que redireccionar a cada uno de los capítulos, pero cuando inten