BCS Release Request Short dump
Hello,
I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
The description is as follows:
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: " ").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
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:
"OBJECTS_OBJREF_NOT_ASSIGNED" " "
"CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
"UGMD_EXTRACT_SID_2"
Information on where terminated
Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
in "UGMD_EXTRACT_SID_2".
The main program was "RDDM0001 ".
In the source code you have the termination point in line 62
of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
Source Code Extract
Line SourceCde
32 FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
33 FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
34 FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
35 * FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
36
37 ASSIGN io_itab->rd_wa->* TO <ls_wa>.
38 IF i_value_sid IS NOT INITIAL.
39 ASSIGN COMPONENT i_value_sid
40 OF STRUCTURE <ls_wa>
41 TO <ld_vsid>.
42 CHECK sy-subrc = 0.
43 ELSE.
44 CREATE DATA lr_sid.
45 ASSIGN lr_sid->* TO <ld_vsid>.
46 CLEAR <ld_vsid>.
47 ENDIF.
48
49 IF NOT i_fieldname_sid IS INITIAL. "Start hah160603.1
50 ASSIGN COMPONENT i_fieldname_sid
51 OF STRUCTURE <ls_wa>
52 TO <ld_fsid>.
53 CHECK sy-subrc = 0.
54 ELSE.
55 CALL METHOD ugmd_get_fieldname_to_table
56 EXPORTING
57 i_tabname = i_datainfo-tabname
58 IMPORTING
59 e_fieldname = ld_fieldname.
60 lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
61 ld_fieldname ).
62 >>>>> ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
63 ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
64 ENDIF. "End hah160603.1
65
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 1
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY TDR_FULL
SY-UCOMM REFR
SY-TITLE Transport organizer: ordens
SY-MSGTY I
SY-MSGID FINB_TR
SY-MSGNO 009
SY-MSGV1 &
SY-MSGV2 &
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080904
SY-UZEIT 200112
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
Will award points for valuable help.
Thank you
Hi Ricardo,
You tried to transport the BCS' configuration, right?
If in the request was the full set of settings from the start of the project, the it will definitely fail.
There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
"For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
During the transport of a new consolidation area, the following settings should be transported in the following sequence:
1. Data basis
2. Consolidation area
3. Special versions
After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
I usually transport the BCS setting in a little transport requests in this order:
- all BW objects and settings
- data basis (with source DB)
- cons area
- special versions
- versions
- master data
...etc.
Hope this helps.
Similar Messages
-
BCS Short Dumps after Upgrade (3.5 to BI7)
Hi SDN,
We have recently upgraded our dev system from BW3.5 to BW 7 (SEM BW 6) and following the upgrade none of the queries based on the BCS virtual info provider(Remote Cube) ZVBCS01 are working or the listcube transaction on cube ZVBCS01 in RSA1.
Both the queries and listcube short dump with DATREF_NOT_ASSIGNED (Details "DATREF_NOT_ASSIGNED" "SAPLUCR0" "LUCR0U08" "PROVIDE_SEM_DATA_TABLE_3")
We have raised a call with SAP OSS they recommended to activate the InfoObject 0BCS_REPMOD from business content and regenerate the data basis. We did all this but still experience the short dumps. (We havenu2019t assigned 0BCS_REPMOD to any Infoproviders or the data basis)
We will be unable to upgrade to BI7 unless we can resolve this issue so any help would be appreciated.
Kind regards,
Jamie FlaxmanThanks for the responses, we have managed to get BCS working now following the upgrade.
Following the activation of the business content, I had to regen the Data Basis but the way I did it originally wasnu2019t enough to force a regeneration. So I had to make a small change to the data basis (move of field names and back again) which was enough to do the re-gen.
We have experienced quite a few issues with the upgrade from SEM 4 to 6.
Thanks for the help.
Jamie Flaxman -
Short dump while reconstructing request in ODS
Hi
I had loaded a request into a few ODS, but later found i had to do some changes to the PSA manually, so i deleted the request from all the ODS and modified the records in the PSA.
Now when i try reconstruction it gives a short dump in one of the ODS with message "Exception condition "NOT_EXIST" raised. ".
Data from this ODS was further loaded to a few other targets as delta and while deleting the request it gave a message saying the delta will be deactivated, I said Ok and the request was deleted.
I was able to reconstruct the request in all the other ODS and cubes without any issues.
what could be the problem???
Regards
SujaiHi
I am doing PSA to ODS. The data is available in PSA. the reconstruction went thru fine in the other targets. but when i try it in the ODS that i want it goes for a dump. This is where the error occurs.. shown in the dump..
select * from rsreqicods into table l_t_rsreqicods where
tabname = i_dta and
typ = 'I' and
odssid = i_odssid.
if sy-subrc <> 0.
raise not_exist. -----> Error in this line
exit.
endif.
Regards
Sujai -
SEM-BCS Short Dump while executing Manual Posting Task
Hi SEM-BCS Colleagues,
I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
Have any of you faced similar problem and help me please?Hello,
I am also getting short dump during data collection in BCS.
we recently upgraded the system to SP20. Is it anyway related to upgrade.
I also checked the MYSELF as a source system, but not found one.
Could you please let me know how you have solved this issue.
short dump:
Runtime Errors PERFORM_TOO_MANY_PARAMETERS
Exception CX_SY_DYN_CALL_PARAM_NOT_FOUND
Date and Time 04.12.2009 05:21:11
Short text
Too many parameters specified with PERFORM.
What happened?
In a subroutine call, there were more parameters than in the
routine definition.
Error in the ABAP Application Program
The current ABAP program "SAPLRSDRI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
not caught in
procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(FUNCTION)", 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:
A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
"GPD1S8520HM8UV0U2XBDVPADF03".
This routine contains 7 formal parameters, but the current call
contains 10 actual parameters. -
Short Dump Error in deleting the Init request
Hi Gurus,
i am loading master data from sap r3 by init update.
now due to some requirement i have to delete the init request , but when i try to delete the request
it goes to short dump and gives the error message as
Runtime Errors MESSAGE_TYPE_X
Date and Time 01/05/2009 01:54:15
Short text
The current application triggered a termination with a short du
What happened?
The current application program detected a situation which real
should not occur. Therefore, a termination with a short dump wa
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Error when opening an RFC connection
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "Error when opening an RFC connection"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Last error logged in SAP kernel
Component............ "SAP-Gateway"
Place................ "SAP-Gateway on host sapdev / sapgw00"
Version.............. 2
Error code........... 631
Error text........... "max no of gateways exceeded (100)"
Description.......... " "
System call.......... " "
Module............... "gwxxrd.c"
Line................. 8438
The error reported by the operating system is:
Error number..... " "
Error text....... " "
Trigger Location of Runtime Error
Program SAPLRSSM
Include LRSSMF03
Row 1,627
Module type (FORM)
Module Name DEL_SOURCE_SYSTEM_INIT
1624 communication_failure = 1 message l_msg_text
1625 system_failure = 2 message l_msg_text.
1626 if sy-subrc <> 0.
>>>>> message x051(rsar) with l_msg_text(50) l_msg_text+50(50) '' ''.
1628 endif.
Please help me on this as untill it will not be deleted, I will be unable to load the data.
suitable answer will get Full points.
Thanks.Hi Saurabh,
PLEase go through these notes:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383837393039%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383934313030%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393738303738%7d -
Message_type_x short dump while deleting request from infocube
Hi,
While deleting one of the erroneous requests from some infocubes,
system is resulting in short dump "MESSAGE_TYPE_X".
This is happening only with respect to some infocubes.
Description of short dump:
Short text of error message:
System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-5- (see long text)
Can any one of you please help with this?
Regards,
Nilima RodriguesHi NILIMA,
I got same problem with my InfoPackage last month with same error msg.
that error come due to data inconstancy in data base table.
in my case i am unable to open my InfoPackage and after double clicking it was giving dump with same error.
If u know abap then just change the sy-subrc value from 4 to 0 before dump line code it will resolve your problem.
for this on dump screen click on debugger button then it opens your code and shows line on which u getting dump with table name check your entry in table ok
if u unable u find table then do one thing just put break point before dump line and open fresh rsa1 and go to same cube and double click it will stop on your debugger point just press f5 button it shos sy-subrc 4 convert it to 0 and press edit button and press f8 .
Regards
Ankit -
Getting short dumps while reading bulky data from excel sheet
Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "nhbho930"
Network address.......... "192.168.0.30"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone). -
Short dump: : OBJECT_NOT_STRUCTURED
Hi,
We are getting the shortdump in BWP, ERROR MESSAGE :OBJECT_NOT_STRUCTURED.
due this the user are not able to see the reports.
This for the infocube : 0RPA_C01
Message no: RSBK257
Short dump
Runtime Errors OBJECT_NOT_STRUCTURED
Date and Time 21.12.2008 03:02:52
Short text
Invalid operand type for the MOVE-CORRESPONDING statement.
What happened?
Error in the ABAP Application Program
The current ABAP program "/RTF/CL_KYF_TRANSFORM=========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The MOVE-CORRESPONDING statement can only be used on operands with a
structured type.
In the case at hand, this condition is not fulfilled: Operand "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... "ndflapp7"
Network address...... "192.168.4.38"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4v"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 18
Shortdump setting.... "full"
Database server... "ndflbwp"
Database type..... "DB6"
Database name..... "BWP"
Database user ID.. "SAPBWP"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Feb 3 2008 21:08:24"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "DB6_81 "
Patch level. 146
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 2713920
EM...... 0
Heap.... 39801136
Page.... 24576
MM Used. 42159048
MM Free. 235944
User and Transaction
Client.............. 700
User................ "BWREMOTE"
Language key........ "E"
Transaction......... " "
Transactions ID..... "494D622862192FB7E1000000C0A80426"
Program............. "/RTF/CL_KYF_TRANSFORM=========CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "/RTF/CL_KYF_TRANSFORM=========CP" -
in "CALCULATE_KEYFIGURE_DS".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 29
of the (Include) program "/RTF/CL_KYF_TRANSFORM=========CM004".
The program "/RTF/CL_KYF_TRANSFORM=========CP" was started as a background job.
Job Name....... "BIDTPR_9161_1"
Job Initiator.. "BWREMOTE"
Job Number..... 03023200
Source Code Extract
Line SourceCde
1 method calculate_keyfigure_ds.
2
3 field-symbols: SINGLE_REF
F0000000
F0000000
/RTF/CL_KYF_TRANSFORM=>S_MONITOR+148(100)
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
/RTF/CL_KYF_TRANSFORM=>S_MONITOR
000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
0
0
2
0
SY
#######ᗹ###################A###P#################<#############################T#######䵘 C####
0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
%_EXCP
F0000000
F0000000
%_DUMMY$$
0000
0000
2222
0000
/RTF/CL_KYF_TRANSFORM=>HLP_STRUC_DS
C0000000
F0000000
<L_STRUC>
SYST-REPID
/RTF/CL_KYF_TRANSFORM=========CP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2554244545455544544543333333334522222222
F246F3CFB96F421E36F2DDDDDDDDDD3000000000
LT_APPL_MONITOR
Table[initial]
No. 7 Ty. METHOD
Name LCL_TRANSFORM=>COMPUTE_14_1
REQUEST
DTPR_4C872RDREWJJFKCBYOIXF7GVA
000000000000000000000000000000
000000000000000000000000000000
455553433354545444444544543454
4402F4387224257AA6B329F9867761
DATAPACKID
000001
000000
000000
333333
000001
SOURCE_FIELDS
1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333
1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
RESULT
000000000
00000000C
MONITOR
Table[initial]
IS_S_FIELDS-BASEQUANTITY
000000000
00000000C
SOURCE_FIELDS-BASEQUANTITY
0000000
000000C
IS_S_FIELDS-DISTDISC
000000000
00000000C
SOURCE_FIELDS-DISTDISC
00000000
0000000C
IS_S_FIELDS-DISTTAX
000000000
00000000C
SOURCE_FIELDS-DISTTAX
00000000
0000000C
IS_S_FIELDS-DISTTENDER
000000000
00000000C
SOURCE_FIELDS-DISTTENDER
00000000
0000000C
IS_S_FIELDS-REDUCTIONAMOUNT
000000000
00000000C
SOURCE_FIELDS-REDUCTIONAMOUNT
00000000
0000000C
IS_S_FIELDS-TAXAMOUNT
000000000
00000000C
SOURCE_FIELDS-TAXAMOUNT
00000000
0000000C
IS_S_FIELDS-COMMAMOUNT
000000000
00000000C
SOURCE_FIELDS-COMMAMOUNT
00000000
0000000C
IS_S_FIELDS-TENDERAMOUNT
000000000
00000000C
SOURCE_FIELDS-TENDERAMOUNT
00000000
0000000C
RS_C_TRUE
X
0
0
5
8
IS_S_FIELDS-LINEITEMCOUNT
000000000
00000010C
SOURCE_FIELDS-LINEITEMCOUNT
1
0000
0001
IS_S_FIELDS-TOTALSALESAMOUNT
0.0.0.0.0.0.1. #
000000020
00000010C
SOURCE_FIELDS-TOTALSALESAMOUNT
0.0.0.0.0.1. #
00000020
0000010C
IS_S_FIELDS-REDUCTIONAMOUNTN
000000000
00000000C
SOURCE_FIELDS-REDUCTIONAMOUNTN
00000000
0000000C
IS_S_FIELDS-REDUCTIONAMOUNTG
000000000
00000000C
SOURCE_FIELDS-REDUCTIONAMOUNTG
00000000
0000000C
SY-REPID
GP4AQKW51YXT96BMBCFL1TYQBS6
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4534545335553344444435554532222222222222
70411B751984962D236C14912360000000000000
CS_TARGET-FIELDNM
BASE_QTY
000000000000000000000000000000
000000000000000000000000000000
445455552222222222222222222222
2135F1490000000000000000000000
SYST-REPID
GP4AQKW51YXT96BMBCFL1TYQBS6
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4534545335553344444435554532222222222222
70411B751984962D236C14912360000000000000
%_SPACE
0
0
2
0
IS_S_FIELDS
000 00001000120081219172957##### ###################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000C00000C00000000C00000
3332222222222222222222222222222222222222222222333333333333333333333330000020000000000000000000
00000000000000000000000000000000000000000000000000100012008121917295700000000000000C00000000C0
CS_TARGET
BASE_QTY ##################
000000000000000000000000000000000000000000000000
0000000000000000000000000000000000C00000000000C0
445455552222222222222222222222000000000000000000
2135F149000000000000000000000000000000C000000000
%_DUMMY$$
0000
0000
2222
0000
No. 6 Ty. METHOD
Name LCL_TRANSFORM=>EXECUTE
I_MASTER_DATA_EXIST
0
0
2
0
I_R_INBOUND
80000007
B0000004
I_R_LOG
3000000C
2000004D
I_R_REQUEST
0000000F
B0000064
I_R_TRFN_CMD
D0000002
B0000004
E_R_OUTBOUND
3000000C
3000004C
LSSUPP-_13
0
0
2
0
RS_C_FALSE
0
0
2
0
RSJOBINFO
00000000000000 ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
CURRRULE-RULEID
917760
00
0E
SCREEN
%_17NNS0000026337_%_%_%_%_%_%_
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30000026337F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
CURRRULE-STEPID
16777248
0
1
LSSUPP-_14
0
0
2
0
LTMSG
Table[initial]
G1-BASE_QTY
000000000
00000000C
ME
0000000F
C0000063
L_REQUEST
DTPR_4C872RDREWJJFKCBYOIXF7GVA
000000000000000000000000000000
000000000000000000000000000000
455553433354545444444544543454
4402F4387224257AA6B329F9867761
I_R_INBOUND->N_DATAPAKID
000001
000000
000000
333333
000001
<_YS_SC_1>
1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333
1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
LSMSG
000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
0
0
2
0
No. 5 Ty. METHOD
Name CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
I_R_INBOUND
80000007
B0000004
I_R_LOG
3000000C
2000004D
I_R_SELSET
F0000000
F0000000
I_R_FILTER
F0000000
F0000000
E_R_OUTBOUND
3000000C
3000004C
ME->IF_RSBK_CMD~N_REQUID
9161
002C
0039
L_R_REQUEST_MAIN
F0000000
B0000004
%_DUMMY$$
0000
0000
2222
0000
L_R_REQUEST
0000000F
B0000064
SYST-REPID
CL_RSTRAN_TRFN_CMD============CP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4455555445554454443333333333334522222222
3CF23421EF426EF3D4DDDDDDDDDDDD3000000000
LR_EXE
0000000F
C0000063
ME->C_METH_EXECUTE
EXECUTE
0000000
0000000
4544554
5853545
ME->N_CHECK_ONLY_SIDS
0
0
2
0
ME
D0000002
B0000004
ME->N_TH_BP
Table IT_475[0x24]
DATA=N_TH_BP
Table reference: 164
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 000000A4000001DB0000000000000018FFFFFFFF
TABH+ 40(16) = 04000114000004700010839401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 164 (0x000000A4)
label = 475 (0x000001DB)
fill = 0 (0x00000000)
leng = 24 (0x00000018)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000009
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
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 = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 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
L_S_BP
000000000000
000000000000
000000000000
333333333333
000000000000
SY-REPID
CL_RSTRAN_TRFN_CMD============CP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4455555445554454443333333333334522222222
3CF23421EF426EF3D4DDDDDDDDDDDD3000000000
RSTR_STEPTYPE
NO_UPDATE INITIAL DIRECT CONS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
4455544542222222222222222222224445444222222222222222222222224454452222222222222222222222224445
EFF5041450000000000000000000009E9491C000000000000000000000004925340000000000000000000000003FE3
RSTR_STEPTYPE-DIRECT
DIRECT
000000000000000000000000000000
000000000000000000000000000000
445445222222222222222222222222
492534000000000000000000000000
I_R_INBOUND->N_DATAPAKID
000001
000000
000000
333333
000001
SY-SUBRC
4
0000
0004
SPACE
0
0
2
0
L_SEGID
0000
0000
0000
3333
0000
RSAWC_C_TFC-DISPLAY
DISPLAY
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
4455445222222222222222222222222222222222222222222222222222222222222222
4930C19000000000000000000000000000000000000000000000000000000000000000
No. 4 Ty. METHOD
Name CL_RSBK_PROCESS=>PROCESS_REQUEST
SY-REPID
CL_RSBK_PROCESS===============CP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
ME
F0000000
E0000001
ME->N_S_CURSOR_R-NODE
-2
FFFF
FFFE
ME->P_R_LOG_STEP
3000000C
2000004D
%_DUMMY$$
0000
0000
2222
0000
ME->P_R_INBOUND
80000007
B0000004
ME->P_R_OUTBOUND
3000000C
3000004C
L_R_TRANSFORM
D0000002
B0000004
ME->N_S_CURSOR_R+36(8)
D0000002
B0000004
SPACE
0
0
2
0
SY
#######ᗹ###################A###P#################<#############################T#######䵘 C####
0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
ME->N_R_DP
C0000003
D0000002
No. 3 Ty. METHOD
Name CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
I_PARAMETER
ÿ#######4102##########(##########################P#R#O#C#E#S#S«#####(ª######ª######ª######ª###
F0000080333300000000002000800000000000000000000005050404040505A000002A000000A000000A000000A000
F6111200410200005F00008005A70000000000000000000000020F03050303BF00008A800004A60000CA800004A800
E_RETURN
E_T_MSG
Table[initial]
RSBTC_C_STATUS-OK
@08@
0000
0000
4334
0080
%_FSREG_001
SY-XFORM
CONVERSION_EXIT
000000000000000000000000000000
000000000000000000000000000000
444545544454545222222222222222
3FE65239FEF5894000000000000000
SYST-REPID
CL_RSBK_PROCESS===============CP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
ME
F0000000
E0000001
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_PRINT
001RSBATCH_EXEC X8##A
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333554454454544222222222222222222222222222222222222222222222222222222222222222222222253004
00000012321438F5853000000000000000000000000000000000000000000000000000000000000000000000088001
%_VIASELSCR
0
4
L_R_ERROR
F0000000
F0000000
No. 2 Ty. FUNCTION
Name RSBATCH_EXECUTE_PROCESS
ID
DTPR_9161_1
000000000000000000000000000000
000000000000000000000000000000
455553333532222222222222222222
4402F9161F10000000000000000000
I_DIALOG_DEBUG_MODE
0
0
2
0
PROCESS
3
0000
0003
G_T_SERVER_100
00
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222332
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_S_CTRL-LANGU
E
0
0
4
5
SY-LANGU
E
0
0
4
5
SYST-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
SPACE
0
0
2
0
G_NUM3
000
000
000
333
000
%_DUMMY$$
0000
0000
2222
0000
SY-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
L_MODULE_NAME
CL_RSBK_PROCESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4455544555444552222222222222222222222222
3CF232BF02F35330000000000000000000000000
%_SPACE
0
0
2
0
%_CX_TABLEVIEW_ID
2
0000
0002
L_S_CTRL-PROCESS_TYPE
DTP_LOAD
0000000000
0000000000
4555444422
440FCF1400
%_CX_TABSTRIP_ID
3
0000
0003
L_S_CTRL-BATCH_ID
DTPR_9161_1
000000000000000000000000000000
000000000000000000000000000000
455553333532222222222222222222
4402F9161F10000000000000000000
%_CX_TABLEVIEW_VERSION
0
0
0
3
0
L_S_CTRL-BATCH_PROCESS
3
0000000000
0000000000
2222222232
0000000030
%_CX_TABSTRIP_VERSION
0
0
0
3
0
L_PARAMETER
ÿ#######4102##########(##########################P#R#O#C#E#S#S«#####(ª######ª######ª######ª###
F0000080333300000000002000800000000000000000000005050404040505A000002A000000A000000A000000A000
F6111200410200005F00008005A70000000000000000000000020F03050303BF00008A800004A60000CA800004A800
L_R_BATCH_EXECUTE
F0000000
E0000001
L_RETURN
L_T_MSG
Table[initial]
CTRL_200_VAL-CX
No. 1 Ty. EVENT
Name START-OF-SELECTION
SYST-REPID
RSBATCH_EXECUTE_PROZESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5544544545445545554545522222222222222222
2321438F5853545F02FA53300000000000000000
L_T_CTRL
Table[initial]
SCREEN
%_17NNS0000026337_%_%_%_%_%_%_
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30000026337F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
L_S_CTRL
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_LINES
0
0000
0000
L_S_CTRL-BATCH_PROCESS
0000000000
0000000000
2222222222
0000000000
L_S_PAR-WP_NO
000
000
222
000
ID
DTPR_9161_1
000000000000000000000000000000
000000000000000000000000000000
455553333532222222222222222222
4402F9161F10000000000000000000
L_PROCESS
3
0000
0003
%_DUMMY$$
0000
0000
2222
0000
L_S_HEADER-HOLD_PAR_PROCS
0
0
2
0
%_SPACE
0
0
2
0
SYST
#######ᗹ###################A###P#################<#############################T#######䵘 C####
0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
PROCESS
3
0000
0003
L_S_HEADER-PROCESS_TYPE
DTP_LOAD
0000000000
0000000000
4555444422
440FCF1400
RSBTC_C_PROCESS-DTP_LOAD
DTP_LOAD
0000000000
0000000000
4555444422
440FCF1400
Internal notes
The termination was triggered in function "ab_jmvco"
of the SAP kernel, in line 1521 of the module
"//bas/700_REL/src/krn/runt/abmvco.c#6".
The internal operation just processed is "MVCO".
Internal mode was started at 20081221030232.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
DoStack2 ( 0x106186020, 0xffffffff7fff9eb0, 0x10054b9a4, 0x0, 0x14, 0x1034d8af0 ), at 0x10054b
CTrcStack2 ( 0x106186020, 0x0, 0x19c00, 0x103547870, 0x101e1c9a4, 0x1034d8af0 ), at 0x10054b54
__1cQrabax_CStackSave6F_v_ ( 0x103775c00, 0x3775c00, 0x103edabe0, 0x1023314de, 0x100000000, 0x
ab_rabax ( 0x0, 0x0, 0x2000000, 0x100000000, 0x3ed9800, 0x3547800 ), at 0x100cd53b0
__1cIab_jmvco6F_v_ ( 0xffffffff7fffafbc, 0xfffffffe319fc20c, 0x600000000000000, 0x1069d1ca4, 0
__1cIab_extri6F_i_ ( 0x100000000, 0x62cac00, 0x548, 0x1, 0x0, 0xa9 ), at 0x10076ecf8
__1cJab_xevent6FpkH_i_ ( 0x0, 0x0, 0x0, 0x0, 0x4c, 0x106186800 ), at 0x100a4f6f0
__1cIab_trigg6F_i_ ( 0x106109f20, 0x106189968, 0x100a4f038, 0x4, 0x0, 0x0 ), at 0x100a4f174
ab_run ( 0x106a1adb8, 0x106189400, 0x102335bac, 0x0, 0x10618685c, 0x0 ), at 0x100d3d254
dynpmcal ( 0x10690c420, 0x6, 0xc, 0x103a0eec8, 0x100577d80, 0x103547864 ), at 0x1005703ac
dynppai0 ( 0x10690c420, 0x10690da2c, 0x0, 0x1035478c8, 0x0, 0x1061a6894 ), at 0x10056d608
dynprctl ( 0x10690c420, 0x0, 0x1035317c0, 0x1300, 0x1, 0x128c ), at 0x10056bc4c
dynpen00 ( 0x10682df80, 0x10690c420, 0x10690c420, 0x102c30000, 0x2c30000, 0x100000000 ), at 0
TskhLoop ( 0xffffffff7108b230, 0x103530000, 0x3f36, 0xffffffffffffe080, 0xffffffff70007d38, 0
ThStart ( 0x1, 0x2a7400, 0x1002a7400, 0x100000000, 0x1, 0x0 ), at 0x1002a7f0c
DpMain ( 0x3c7bc00, 0x3530000, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001d9698
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg RSBATCH_EXECUTE_PROZESS 0 09.07.2008 04:18:32 39936 E
1 Prg SAPMSSY0 1 08.07.2008 17:53:04 92160 E
2 Prg SAPMSSYD 1 05.09.2006 14:20:30 21504 E
3 Prg SAPFSYSCALLS 1 07.03.2005 18:01:13 8192 E
4 Prg RSDBRUNT 0 08.07.2008 18:16:58 254976 E
5 Prg SAPLSPRI 5 08.07.2008 18:48:22 342016 E
6 Typ PRI_PARAMS 0 27.10.1998 15:01:35 5120
7 Typ ARC_PARAMS 0 08.08.1997 14:45:20 5120
8 Typ PRI_LAYOUT 0 04.09.2002 14:38:36 3072
9 Typ PRIPAR_EXT 0 03.06.2004 11:20:21 3072
10 Typ PRIPAR_EX2 0 01.02.2001 17:17:24 2048
11 Typ PRIPAR_EX3 0 03.06.2004 11:20:21 3072
12 Typ TPRI_DEF 0 01.02.2001 17:50:49 5120
13 Typ USR01 0 08.07.2008 17:43:16 4096
14 Typ TSP1D 0 02.02.1998 15:00:56 5120
15 Prg SAPLSPOO 15 08.07.2008 18:46:51 152576 E
16 Prg SAPLRSPOLSTDRV 16 18.11.2005 14:39:34 57344 E
17 Typ TSPOPTIONS 0 06.12.1996 16:09:18 2048
18 Typ TSP03 0 13.08.1998 16:56:08 6144
19 Prg SAPCNVE 19 07.03.2005 18:01:13 8192 E
20 Prg SAPLSPOC 20 08.07.2008 18:48:51 137216 E
21 Typ RSPOCHECK 0 14.07.1997 13:01:20 4096
22 Typ TSP03A 0 10.06.1997 01:43:11 3072
23 Typ DEVPAR 0 01.02.2001 17:10:21 3072
24 Typ RSPOATTR 0 19.01.2000 18:34:33 2048
25 Typ RSSCR 0 23.11.1999 09:24:41 5120
26 Prg RSDBSPBL 0 07.03.2005 18:01:13 72704 E
27 Prg SAPDB__S 0 07.03.2005 18:01:13 19456 E
28 Typ VARID 0 11.04.1997 18:32:23 7168
29 Typ SSCRFIELDS 0 02.05.1997 13:16:39 5120
30 Prg %_CSYDB0 0 07.03.2005 18:01:13 36864 E
31 Prg RSDBSPVA 0 08.07.2008 16:32:53 133120 E
32 Typ RSVAMEMKEY 0 16.12.1996 19:31:50 2048
33 Prg RSDBSPMC 0 05.09.2006 14:14:08 79872 E
34 Typ DDSHDESCR 0 28.11.1997 16:26:30 4096
35 Typ SPPARAMS 0 07.03.1997 14:48:48 2048
36 Prg SAPLICON 36 08.07.2008 18:16:58 27648 E
37 Prg %_CICON 36 08.07.2008 18:16:57 107520 E
38 Typ ICONT 0 05.09.2006 14:14:08 2048
39 Prg SAPLSABE 39 07.03.2005 18:01:13 13312 E
40 Prg SAPLSECU 40 08.07.2008 17:43:16 87040 E
41 Typ RSSUBINFO 0 22.11.1999 21:15:17 3072
42 Prg RSDBSPVD 0 08.07.2008 13:55:28 88064 E
43 Typ DFIES 0 19.12.2004 17:28:52 10240
44 Typ VARI 0 16.12.1996 19:38:11 6144
45 Typ RSDSFIELDS 0 16.12.1996 19:31:30 3072
46 Prg %_CRSDS 0 07.03.2005 18:01:13 10240 E
47 Typ RSDSEXPR 0 16.12.1996 19:31:30 3072
48 Typ RVARI 0 18.06.1999 11:23:08 4096
49 Prg SAPLSVAR 49 08.07.2008 18:48:35 766976 E
50 Typ VARIS 0 14.03.1997 19:25:50 2048
51 Typ RSVARKEY 0 16.12.1996 19:31:51 2048
52 Prg SAPLSSEL 52 08.07.2008 18:16:58 1155072 E
53 Typ RSCONVERT 0 01.02.2001 17:18:21 4096
54 Prg RSDBSPDS 0 08.07.2008 18:16:57 56320 E
55 Typ RSEXFCODE 0 18.07.1997 17:04:17 2048
56 Prg SAPLDSYA 56 08.07.2008 17:48:56 45056 E
57 Prg SAPFSDS1 56 07.03.2005 18:01:13 53248 E
58 Typ TDCLD 0 14.07.1998 14:53:43 5120
59 Prg SAPLSDOD 59 23.01.2006 17:31:16 46080 E
60 Typ DOKIL 0 07.04.1997 18:29:04 3072
61 Prg SAPLLANG 61 08.07.2008 13:44:44 10240 E
62 Typ T002 0 08.07.2008 13:44:44 2048
63 Prg SAPFSPOR 0 08.07.2008 20:08:30 15360 E
64 Typ RSPARINT 0 10.03.1995 17:53:00 2048
65 Prg SAPLSTUP 65 08.07.2008 17:39:04 74752 E
66 Prg SAPLCNDP 66 08.07.2008 16:30:09 195584 E
67 Prg SAPLSCNT 67 07.03.2005 18:01:13 30720 E
68 Prg SAPSHDTV 67 07.03.2005 18:01:13 33792 E
69 Prg SAPFGUICNTL 1 07.03.2005 18:01:13 24576 E
70 Prg SAPLOLEA 70 08.07.2008 14:26:43 96256 E
71 Prg SAPLSGUI 71 08.07.2008 17:53:04 84992 E
72 Prg SAPLSTTM 72 18.11.2005 14:35:29 69632 E
73 Prg SAPLSBDC 73 08.07.2008 17:40:32 44032 E
74 Prg SAPLSFES 74 08.07.2008 18:48:19 261120 E
75 Prg SAPLTHFB 75 08.07.2008 18:47:19 394240 E
76 Typ WPINFO 0 08.02.1999 14:18:32 6144
77 Prg SAPLURFC 77 08.07.2008 17:49:18 22528 E
78 Prg SAPLSPLUGIN 78 07.03.2005 18:01:13 8192 E
79 Typ SWCBCONT 0 07.10.1997 12:13:50 3072
80 Typ OLE_VERBS 0 09.02.1995 13:23:37 2048
81 Typ OLE_PA 0 13.01.1995 11:06:59 2048
82 Typ SSCRTEXTS 0 15.08.1997 14:15:15 3072
83 Typ RSBATCHHEADER 0 23.01.2006 19:24:22 6144
84 Prg SAPLRSBATCH 84 09.07.2008 03:46:40 595968 E
85 Typ RSBATCHDEBUG 0 14.06.2004 17:15:14 4096
86 Typ BAL_S_MSG 0 01.02.2001 17:04:55 7168
87 Prg /1BCDWBEN/SAPLREN0002 87 23.11.2005 13:29:42 237568 E
88 Prg SAPLSENA 88 08.07.2008 14:29:56 33792 E
89 Typ RSBATCHCTRL 0 17.09.2004 14:15:41 5120
90 Typ RSBATCHDATA 0 18.04.2005 09:27:49 6144
91 Prg SAPLBTCH 91 08.07.2008 18:48:44 1871872 E
92 Prg SAPLRSSM 92 23.11.2005 13:29:30 1007616 E
93 Prg SAPLSYDB 93 08.07.2008 16:32:36 63488 E
94 Prg CL_RSBK_PROCESS===============CP 94 09.07.2008 03:32:34 94208 E
95 Typ RSBK_S_CMD_R 0 14.06.2004 17:14:04 3072
96 Typ RSBKCMDPROP 0 18.11.2005 16:13:41 5120
97 Prg IF_RSBATCH_CALLBACK===========IP 84 09.07.2008 04:09:32 9216 E
98 Prg IF_RSBATCH_EXECUTE============IP 84 07.03.2005 18:01:13 8192 E
99 Typ RSBK_S_PROCESS 0 19.04.2005 14:56:01 3072
100 Typ RSBK_S_CMD_MEMENTO 0 17.09.2004 14:15:27 2048
101 Prg CL_RSBK_REQUEST===============CP 101 09.07.2008 04:16:32 161792 E
102 Prg CL_RSBK_REQUEST_GENERAL=======CP 102 09.07.2008 04:16:32 35840 E
103 Prg SAPLRRSI 103 09.07.2008 04:21:08 246784 E
104 Typ RSD_S_COB_PRO 0 09.07.2008 02:12:20 23552
105 Prg CL_RSR========================CP 105 09.07.2008 04:03:31 154624 E
106 Typ RSR_S_CHANM 0 12.09.2003 11:33:26 2048
107 Typ RSD_S_DTA 0 09.07.2008 02:12:21 27648
10check the status of the background job , if job has faild
the reasion may be because of chaing in the extract structure in the source system.
so we can replicate the data source to resolve this issue.
And also make a check with extract structure using the T.coad RSA3, to find
no of records and to find out any chainges in the structure . -
How to keep short dumps for a longer time
Hi All,
I need to write a program to fetch all the below mentioned fields from the system dump tables and insert into a user defind table. Please help me with the code. Thanks in advance....
PROBLEM DESCRIPTION
ABAP runtime errors (also known as short-dumps) are kept in the system only for two days, mainly because every short-dump can use a lot of disk space depending on short-dump type. Problem is that this reduced time frame (two days) is not allowing us to focus in solve the more frequent ones and we do not have any statistic about:
how many are we getting
how often
repetitive ones
PROPOSED SOLUTION
We need a program to be executed in a daily job right after midnight which will take the basic information of all todays short-dumps and store it in a custom table.
Information to be kept:
DATE
TIME
HOST
USER
SYSTEM
CLIENT
ERROR ID
TRANSACTION
PROGRAM NAME
PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
SCREEN
SCREEN LINE
MAIN PROGRAM NAME
MAIN PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
MAIN PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
PROGRAM LINE NUMBER AT TERMINATION
SAP RELEASE
SAP KERNEL
PATCH LEVEL
DATABASE VERSION
The program must have archiving capabilities implemented. In the month end run it will also perform the table house-keeping accordingly with a parameter like this:
ERROR-ID
MONTHS TO KEEP
We need to have the possibility of defining different retention periods for different kind of errors, for example our friend GETWA_TOO_MANY_SEGMENT could be stored for a year and a simple CONVT_NO_NUMBER only for a month. One of the parameters should be the default one, something like
ERROR-ID **************
MONTHS TO KEEP 01.Aruna,
Following may be the action points for your requirements.
1. Create Custom table with all fields you required.
2. Create ABAP program to extract the data from SAP standard table where runtime error information is stored.
Like: select * from snap_beg into wa_snap_beg
where seqno = '000'
and datum in s_datum
and uzeit in s_uzeit
and ahost in s_ahost
and uname in s_uname
and mandt in s_mandt.......
So SNAP_BEG is a table where you can find dump information.
After extracting the data from this table insert it into a Custom table which you have created in Step 1.
Use INSERT statement for this.
3. Create transaction for this report.
4. Schedule this program every day so that you will get all data into custom table.
I hope this will help you.
Regards,
Amey -
Short Dump TSV_TNEW_PAGE_ALLOC_FAILED
Hi All,
I am facing the short dump "TSV_TNEW_PAGE_ALLOC_FAILED" problem in my PRD system.
Please find ST22 log and suggest the solution:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 18.11.2009 12:12:09
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
or analysis
The internal table "\FUNCTION-POOL=EL40\DATA=GL_NODETAB[]" could not be further
extended. To enable
Error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 2160
Number of rows: 1782088
Allocated rows: 1782088
Newly requested rows: 4 (in 1 blocks)
to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 4419712
Extended memory (EM)........... 2002743520
Assigned memory (HEAP)......... 2000049152
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... " "
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLEL40" or "LEL40U11"
"ISU_ELWEG_HIERARCHY_BUILD"
Please help me out to resolve the issue.
Regards,
Nitin SharmahI cHANDRU,
tHANKS FOR YOUR RESPONSE:
pLEASE FIND BELOW MENTIONED DETALS:
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SVPSAPECP01"
Database type..... "MSSQL"
Database name..... "ECP"
Database user ID.. "ecp"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Nov 18 2008 22:53:36"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 185
Patch text.. " " -
ST22 Short Dump STORAGE_PARAMETERS_WRONG_SET
Hi
We have a NW04 BW 350 system running on Windows 2003 32 Bit/MS SQL 2000 32 Bit.
When I go into RSA --> Monitoring --> PSA it says 'constructing administrators workbench' then fails with the short dump:
<b>STORAGE_PARAMETERS_WRONG_SET</b>
The shortdump reccommends increasing parameters abap/heap_area_dia and
abap/heap_area_nondia, I would have thought you would want to avoid using HEAP memory as this locks the memory into a single work process ?
Looking at the memory consumption in the shortdump :
<b>Memory usage.............
Roll..................... 1709536
EM....................... 108964960
Heap..................... 406948064
Page..................... 57344
MM Used.................. 495709152
MM Free.................. 17059832
SAP Release.............. "640"</b>
EM has only been used for about 100 MB, then it go's to HEAP memory.
Looking at ST02 the system has 4GB EM and only 1.7GB used at 42%, so why would the process only use 100 MB of EM?
ztta/roll_extension is set to default 2GB so it appears EM memory should be utilised more by the work process before going to HEAP memory.
What parameters affect the usage of EM before entering HEAP usage?
Thanks for any advice.Dear friend
kindly see the folowing rsdb/ntab/entrycount Number of nametab entries administrated 20000 30000
rsdb/ntab/ftabsize Data area size for field description buffer 30000 60000
rsdb/ntab/irbdsize Data area size for initial records buffer 6000 8000
rtbb/buffer_length Size of single record table buffers 16383 60000
zcsa/table_buffer_area Size of generic table buffer 64000000 120000000
zcsa/db_max_buftab Directory entries in generic table buffer 5000 30000
zcsa/presentation_buffer_area Size of the buffer allocated for screens 4400000 20000000
sap/bufdir_entries Maximum number of entries in the presentation buffer 2000 10000
rsdb/obj/buffersize Size of export/import buffer 4096 40000
rsdb/obj/max_objects Max. no. of exporting/importing objects 2000 20000
Parameters Description Current value Recommended value
em/initial_size_MB Size of extended memory pool 4096 8192
em/global_area_MB Size of SAP Extended Global Memory (see SAP Note 329021) 96 255
ztta/roll_area Maximum roll area per user context 3000000 16773120
rdisp/PG_SHM Paging buffer size in shared memory 8192 32768
Parameters Description Current value Recommended value
rdisp/wp_ca_blk_no Work process communication blocks 300 1000
rdisp/appc_ca_blk_no Buffer size for CPI-C communications 100 2000
gw/max_conn Max. number of active connections 500 2000
rdisp/tm_max_no Max. number of entries in array tm_adm 200 2000
rdisp/max_comm_entries Max. number of communication entries 500 2000
gw/max_overflow_size Max. swap space for CPIC-requests in the gateway 5000000 100000000
gw/max_sys Max. number of connected clients 300 1000
shailesh -
Short dump with the transaction CJ02
Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors MESSAGE_TYPE_X
Occurred on 20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
During processing of a routine called using PERFORM ... ON COMMIT,
the system attempted to call PERFORM ... ON COMMIT again. Nesting
of this is not allowed.
System Response
Procedure
The program indicated after "Caller:" must be changed. This is the
program that calls the routine indicated after "Form:" during
COMMIT processing. This routine is part of the program indicated
after
"Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk -
LOAD_PROGRAM_NOT_FOUND Short dump in R/3
Hi frnds,
I am facing some short dump problem while loading the data from R/3 BW, its a master data.
The short dumps are LOAD_PROGRAM_NOT_FOUND and RAISE_EXCEPTION in R/3.
Not able to find the exact problem and please suggest some OSS Notes.
Thanks
Harihi Hari,
check if helps oss note 899405-Master data extrctn: LOAD_PROGRAM_NOT_FOUND in source system
Symptom
You are loading master data in delta mode from an SAP source system. The DataSource uses generic extraction in the process.
The request is displayed in the monitor as being incorrect. The status indicates that the extraction process has probably terminated with a runtime error.
In the source system, you find the runtime error LOAD_PROGRAM_NOT_FOUND with the exception CX_SY_PROGRAM_NOT_FOUND. The point of termination is in the function module RSA3_GEN_GET_DATA.
The short dump occurs only if there is no data available for the delta.
Other terms
OLTP, extractor, data extraction, DataSource, service API, SAPI, dump, SAPLRSA3, LRSA3U03, RSAPTM2, EXTRACTOR_FETCH, EXTRACTOR_INIT, NO_MORE_DATA
Reason and Prerequisites
This is caused by a program error.
When you implemented Note 853001, calls for function modules were relocated to subroutines. This changed the query for the exception NO_MORE_DATA in such a way that it is not caught when the extractor is initialized. The extraction process then tries to start the program, but the program has not been generated because data is missing. The system issues the short dump.
Solution
After you have implemented the correction specified below, you must reactivate the transfer rules for the affected DataSource. It is only by doing this that the correction is also implemented in the generated program for the extraction process.
To correct the problem, you need to have Support Package 07 in the relevant source system Service API 7.00. The attached composite note informs you of the software components that contain Service API 7.0 and specifies the corresponding Support Packages for these components.
As an alternative, you can also implement the advance correction from the attachment.
You must implement the correction in the BW system only if it is affected in its role as a source system for itself (myself connection) or for another BW system.
Note: Service API is an internal component. It is not delivered separately, but as part of other software components: PI, CRM, PI_BASIS and a number of others. For this reason, a composite note has been created which tells you in which Support Packages of the above-mentioned software components the SAP correction note is contained. However, the composite note is not released until the release date of the corresponding SAPI Support Package. Different SAPI versions are delivered for Basis Releases 3.1I, 4.0B, 4.6D, 6.20 and 6.40. The version for 4.0B is also valid for R/3 Releases 4.6B and 4.6C. -
Programme going for short dump
HI FRIENDS
WHENEVER OUR PRG TRIES TO RETRIEVE MORE THAN 20000 RECORDS ITS GIVING DUMP WITH
Storage_parameters_wrong_set
abap/heap_area_dia/ndia value 2gb.
APPRECIATE YOUR RESPONSE.
Regards,
Mir.Hi Tim,
The short dump info is :
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
Date and Time 23.05.2006 17:11:25
ShrtText
&INCLUDE INCL_INSTALLATION_ERROR
What happened?
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 456137504 bytes from the operating
system with 'malloc' when the operating system reported after a
further memory request that there was no more memory space
available.
What can you do?
Make a note of the actions and input which 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.
Set the system profile parameters
- abap/heap_area_dia
- abap/heap_area_nondia
to a maximum of 456137504. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
abap/heap_area_nondia and abap/heap_area_dia:
Set smaller than the memory achieved for each process
with 'malloc' and smaller than abap/heap_area_total
You should also check whether the available memory (file system
swap and main memory) is sufficient for the started program
and its data.
Error analysis
When the program was running, it was established that more
memory was needed than the operating system is able to provide savely.
To avoid a system crash, you must prevent this
situation.
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server hstnd1_DV1_00 on host hstnd1 (wp 2)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1878
How to correct the error
Report the error to the group responsible for installing your
R/3 System.
System environment
SAP Release.............. "640"
|
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 2
Short dump setting....... "full"
|
Database type............ "MSSQL"
Database name............ "DV1"
Database owner........... "dv1"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Nov 4 2004 23:26:03"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "43"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 700176
EM....................... 385999584
Heap..................... 456137504
Page..................... 57344
MM Used.................. 729325096
MM Free.................. 108201024
Appreciate your help..
Regards,
Mir. -
Hi,
We are facing short dumps very regularly for some particular ODS and cubes.
Every time we have to go for reconstruction or manual update.
I have some questions in mind:
1. Why do we encounter short dump? Is this an ABAP issue or BASIS issue
2. If its an issue with ABAP programs, how come the load is successful when I do reconstruction or manual update from PSA?
Thnks & rgds
APHi AP,
Apart from the Above mentioned errors.
Common Errors:
Few of them are here:
1) RFC connection lost.
A) We can check out in the SM59 t-code
RFC Des
+ R/3 conn
CRD client (our r/3 client)
double click..test connection in menu
2) Invalid characters while loading.
A) Change them in the PSA & load them.
3) ALEREMOTE user is locked.
A) Ask your Basis team to release the user. It is mostly ALEREMOTE.
2) Password Changed
3) Number of incorrect attempts to login into ALEREMOTE.
4) USE SM12 t-code to find out are there any locks.
4) Lower case letters not allowed.
A) Uncheck the lower case letters check box under "general" tab in the info object.
5) While loading the data i am getting messeage that 'Record
the field mentioned in the errror message is not mapped to any infoboject in the transfer rule.
6) object locked.
A) It might be locked by some other process or a user. Also check for authorizations
7) "Non-updated Idocs found in Source System".
8) While loading master data, one of the datapackage has a red light error message:
Master data/text of characteristic ZCUSTSAL already deleted .
9) extraction job aborted in r3
A) It might have got cancelled due to running for more than the expected time, or may be cancelled by R/3 users if it is hampering the performance.
10) request couldnt be activated because there is another request in the psa with a smaller sid
A)
11) repeat of last delta not possible
12) datasource not replicated
A) Replicate the datasource from R/3 through source system in the AWB & assign it to the infosource and activate it again.
13) datasource/transfer structure not active.
A) Use the function module RS_TRANSTRU_ACTIVATE_ALL to activate it
14) ODS activation error.
A) ODS activation errors can occur mainly due to following reasons-
1.Invalid characters (# like characters)
2.Invalid data values for units/currencies etc
3.Invalid values for data types of char & key figures.
4.Error in generating SID values for some data.
Help on "Remedy Tickets resolution"
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
https://forums.sdn.sap.com/click.jspa?searchID=678788&messageID=1842076
Production Support
Production support issues
Hope This Helps.
Regards,
Ravikanth.
Maybe you are looking for
-
Video corruption during installation...
Hi all. I'm attempting to install Arch onto my desktop and I'm encountering an issue, which is odd because I've never had an issue when I installed Arch onto the machine before. The issue is that the video output at the install console is quite corru
-
Is it possible to populate listbox/dropdownlist items using loadXML method?
Is it possible to populate listbox/dropdownlist items using loadXML method? (If I have xml data in some string variable) Any sample? Thanks
-
Anybody know about Contact Forms
Anybody on here know how to configure a contact form from a template i am working on. I can email you the files that i am worknig on, jsut drop me a pm with your email address. Lee Thank you in advance
-
SharePoint 2010 List - Append Changes to Existing Text - multiline text fields being duplicated
Hello! SharePoint 2010 - I have this same problem for all Lists that use the combination of 1) Multi-line text column; 2) Column is set to "Append Changes to existing text"; 3) Text choice = Plain Text or Rich Text or Enhanced Rich Text. 4) List item
-
Why wont PS CS5 open NEF files from a Nikon D600
I have PS CS5 and I recently updated my camera to a Nikon D600. I shoot in RAW and when I tried to open photos to edit, PS said I needed to update my Camera Raw plugin. I found the most recent plugin for CS5 and photos still won't open What do I need