Dear All
I have Created Release strategy in Development server
It is working fine in development server.
Also as you all are aware that while creating characteristic system does not generate any request
Only at the time of applying strategy system generates the request.
So we have transferred this request in Quality and Production server.
But while creating Characteristic in Quality and Production server system is not alowing me to create the Characteristic
I am getting Message as
Express document "Update was terminated" received from author "MMCONFIG"
In in box the message is as follows
"
Update was terminated
System ID.... BRQ
Client....... 400
User..... MMCONFIG
Transaction.. CT04
Generated.... 15.11.2008, 21:42:22
Completed.... 15.11.2008, 21:42:22
Error Info... LB 163: Use of proportion units or product units was deactivated
"
in st22 Error analysis
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "SAVE_DATA" "(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:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
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:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"SAPLCTVB" or "LCTVBF58"
"SAVE_DATA"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
Can anybody guide me what can be the possible reason and what is the solution for this problem
Regds
shailesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.