OrgChart: Missing Tables from Default Configuration?
Hi,
I'm just configuring the basic Nakisa OrgChart tool and am having issues displaying data.
I have configured the extractor and have managed to extract data successfully to the SQL server database.
However whenever I try to configure the Organisational Structure Hierarchy (in administrator console-Org Chart, via Hierarchies-Organisation Structure) I come across an error.
The Data Table field in the Data Connection config step is pre-populated with the table 'OrgUnitHierarchy', however this does not seem to exist and comes back with an error if I try and save.
Also in the Hierarchies-Organisation Structure-Position config settings, the Data Table in the Data Connection Config step is pre-populated with 'PositionEmpHierarchy' and again this table does not seem to exist.
I have bypassed the first issue by using 'HierarchyTable' however this is causing display issues later on( as viewed in the log).
I would have thought that the standard install would already create and load these tables (as it has done with all the others.
My question, should I be doing some extra config to enter in the table details? If so where?
Have I missed a step? The downloadschema.xml does seem to try and populate thse tables, however whenever I publish and try to view the details I get errors in the log saying the table does not exist.
Any help would be much appreciated. Please let me know if you'd like me to explain something further
Cheers
Andrew
Hi,
The following is a small extract from the join statements in the downloadschema.xml . It seems to reference the four tables but I can't see where they are created and my setup doesn't seem to recognise them.
<joinConfiguration>
<subGroup name="DropTables">
<desc>Dropping the Tables if they are previously been downloaded.</desc>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Drop Table OrgUnitHierarchy]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Drop Table PositionEmpHierarchy]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Drop Table EmpDetailsCombined]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Drop Table EmpStructure1]]></joinStatement>
</subGroup>
<subGroup name="OrgHierarchyTables">
<desc>Generating Tables for Orgnizational Hierarchy..</desc>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Select * INTO Temp1 from HierarchyTable where ObjectType = 'S']]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Select * INTO Temp2 from HierarchyTable where ObjectType = 'P']]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Select Temp1.*, Temp2.ObjectId[Pernr], Temp2.ShortText[EmpAbbr], Temp2.LongText[EmpName]
INTO Temp3
from Temp1 left join Temp2
on Temp1.ObjectId = Temp2.ParentNo]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Select * INTO Temp4 from PositionRelations where SCLAS = 'S' and SUBTY = 'A002']]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[SELECT Temp3.*, Temp4.SOBID[PositionParent],
Temp4.SUBTY[Subty], Temp4.PROZT[Prozt]
INTO TempPosEmp
FROM Temp3 left join Temp4
ON Temp3.ObjectId = Temp4.OBJID]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[Select TempPosEmp.*, PositionVacancy.Vacan,PositionVacancy.Status
INTO PositionEmpHierarchy
From TempPosEmp left join PositionVacancy
ON TempPosEmp.objectId = PositionVacancy.POSITIONID]]></joinStatement>
<joinStatement ignoreErrors="True" dbType="all"><![CDATA[ALTER TABLE PositionEmpHierarchy ADD ChiefOf VARCHAR(2)]]></joinStatement>
Similar Messages
-
How to exclude tables from default scheduled stats job in 10.2.0.4
I am using Oracle default stats job GATHER_STATS_JOB in my database. But i need to exclude stats gathering for few tables as part of my business requirement.
Welcome to the forums.
As I am sure you read the docs on DBMS_STATS at tahiti.oracle.com what was it about the method for addressing it in the docs that you don't think will work for you.
Hint: The correct answer to my question is not "I didn't read the docs because I thought someone here would read them for me." ;-) -
Missing ActiveSync from Bluetooth Configuration
Hi,
I know this is partly my fault ....
I had bluetooth active sync with my smartphone for a while. But then it stopped working. In trying to troubleshoot, I thought I'd delete the active sync servie and reinstall it.
So, I pressed the delete button - but there's no add functionality.
I've uninstalled the enhanced bluetooth program from the control panel, and then reinstalled it with the latest download from the Lenovo site. I still can't find the active sync service anywhere though. What have I got to do to get it back?
I'm running a T400 (6474-R1U) with Windows XP.
Thanks.Hi,
I know this is partly my fault ....
I had bluetooth active sync with my smartphone for a while. But then it stopped working. In trying to troubleshoot, I thought I'd delete the active sync servie and reinstall it.
So, I pressed the delete button - but there's no add functionality.
I've uninstalled the enhanced bluetooth program from the control panel, and then reinstalled it with the latest download from the Lenovo site. I still can't find the active sync service anywhere though. What have I got to do to get it back?
I'm running a T400 (6474-R1U) with Windows XP.
Thanks. -
Insert old missing data from one table to another(databaase trigger)
Hello,
i want to do two things
1)I want to insert old missing data from one table to another through a database trigger but it can't be executed that way i don't know what should i do in case of replacing old data in table_1 into table_2
2)what should i use :NEW. OR :OLD. instead.
3) what should i do if i have records exising between the two dates
i want to surpress the existing records.
the following code is what i have but no effect occured.
CREATE OR REPLACE TRIGGER ATTENDANCEE_FOLLOWS
AFTER INSERT ON ACCESSLOG
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
DECLARE
V_COUNT NUMBER(2);
V_TIME_OUT DATE;
V_DATE_IN DATE;
V_DATE_OUT DATE;
V_TIME_IN DATE;
V_ATT_FLAG VARCHAR2(3);
V_EMP_ID NUMBER(11);
CURSOR EMP_FOLLOWS IS
SELECT EMPLOYEEID , LOGDATE , LOGTIME , INOUT
FROM ACCESSLOG
WHERE LOGDATE
BETWEEN TO_DATE('18/12/2008','dd/mm/rrrr')
AND TO_DATE('19/12/2008','dd/mm/rrrr');
BEGIN
FOR EMP IN EMP_FOLLOWS LOOP
SELECT COUNT(*)
INTO V_COUNT
FROM EMP_ATTENDANCEE
WHERE EMP_ID = EMP.EMPLOYEEID
AND DATE_IN = EMP.LOGDATE
AND ATT_FLAG = 'I';
IF V_COUNT = 0 THEN
INSERT INTO EMP_ATTENDANCEE (EMP_ID, DATE_IN ,DATE_OUT
,TIME_IN ,TIME_OUT,ATT_FLAG)
VALUES (TO_NUMBER(TO_CHAR(:NEW.employeeid,99999)),
TO_DATE(:NEW.LOGDATE,'dd/mm/rrrr'), -- DATE_IN
NULL,
TO_DATE(:NEW.LOGTIME,'HH24:MI:SS'), -- TIME_IN
NULL ,'I');
ELSIF V_COUNT > 0 THEN
UPDATE EMP_ATTENDANCEE
SET DATE_OUT = TO_DATE(:NEW.LOGDATE,'dd/mm/rrrr'), -- DATE_OUT,
TIME_OUT = TO_DATE(:NEW.LOGTIME,'HH24:MI:SS'), -- TIME_OUT
ATT_FLAG = 'O'
WHERE EMP_ID = TO_NUMBER(TO_CHAR(:NEW.employeeid,99999))
AND DATE_IN <= (SELECT MAX (DATE_IN )
FROM EMP_ATTENDANCEE
WHERE EMP_ID = TO_NUMBER(TO_CHAR(:NEW.employeeid,99999))
AND DATE_OUT IS NULL
AND TIME_OUT IS NULL )
AND DATE_OUT IS NULL
AND TIME_OUT IS NULL ;
END IF;
END LOOP;
EXCEPTION
WHEN OTHERS THEN RAISE;
END ATTENDANCEE_FOLLOWS ;
Regards,
Abdetu..INSERT INTO SALES_MASTER
( NO
, Name
, PINCODE )
SELECT SALESMANNO
, SALESMANNAME
, PINCODE
FROM SALESMAN_MASTER;Regards,
Christian Balz -
Missing PRCTR from Number Range Table
Hi There,
I need to find out all the the available profit centre which not created yet ie no profit centre available in CEPC from the number range table NRIV.
I tried the FM number_get_next but nothing happened.
Details given below:
In the NRIV table I have got say following details :
Object From Number To Number etc etc
Y_PC 0000000001 0000000100
Y_PC 0000000101 0000000150
Y_PC 0000000160 0000000200
Profit Centre Created Available in CEPC say
In the no range 1 to 100
0000000001
0000000002
0000000003 (Not created)
0000000004
5 ,6 & 7 missing
0000000008
In the no range 101 to 150
0000000101
0000000102
0000000103
0000000104 (Not created)
0000000105
6,7....upto 149...(Not created)
0000000150
Similarly in other ranges few nos missing
My requirement is to read the NRIV table take all from number and to number into an internal table and for those nos find the missing nos from the CEPC table .
Appreciate your help.
Regards.
SunandaResolved by myself !!
Cheers. -
Hi SAP Gurus,
I noticed on our SAP business warehouse (BW) system (NetWeaver 7.0 based on AIX/Oracle 11g) in transaction DB02 => Diagnostics => Missing Tables and Indexes under Secondary indexes, 26 indexes, in package $tmp:
The indexes are defined, but they don't have been created on the database.
When I try to create them via the database tool, I am getting the warning:
Does the warning raise up, because they where defined in the $tmp package?
I was looking in SAP notes for a solution for this "warning" concerning the /BIC/F-Indexes but I didn't found yet anything helpful ...
Thanks for your help and ideas ...
Best regards
CarlosHi Carlos,
These are secondary indexes created during process chains in BI to improvise performance.
You may refer below SCN blogs on creation of these indices in BI.
Secondary Index - Improving DSO insert/read performance
How to Create Secondary Index on DSO in SAP BW
Hope this helps.
Regards,
Deepak Kori -
Crystal Report - More than one table from MySql
Hello, I am in need of help big time.
I have am using Visual Studio 2010 and Crystal Report 10.
The problem that I am incounting is that I am unable to retreive data from more than one table from a MySql database. I have been stuck on this for too long and need to hjump the hurdle.
I am using a MySql connection string, a dataset and a crystal report which is based on the dataset.
The main error that I am having is, the browser opens and a form appears saying "The report you requetsed requires further information" With the Server name: DataSetPropertiesDetials, while the User name and Password fields are then enabled.
I am guessing I am missing something in my code.
When I retreive data from one table the report is fine, but when I try to use more than one table it throws the error.
My Code is below and also attached:
Imports System.Data.SqlClient
Imports System.Configuration
Imports MySql.Data.MySqlClient
Imports CrystalDecisions.ReportSource
Imports CrystalDecisions.Web
Imports CrystalDecisions.CrystalReports.Engine
Imports CrystalDecisions.Shared
Public Class _Default
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
Dim con As MySqlConnection
Dim rpt As New CrystalReport3()
Dim myReport As New ReportDocument
Dim myData As New DataSet
Dim cmd As New MySqlCommand
Dim cmdUser, cmdProperty, cmdBranch As New MySqlCommand
Dim daBranch, daProperty, daUser As New MySqlDataAdapter
con = New MySqlConnection()
'Connection String
con.ConnectionString = "Server=****;Database=***;UID=***;Password=****"
Try
con.Open()
cmdBranch.CommandText = "SELECT branch FROM tblbranch"
cmdBranch.Connection = con
daBranch.SelectCommand = cmdBranch
daBranch.Fill(myData)
cmdProperty.CommandText = "SELECT ref, keys_held, key_no, keys_out, no_name, address_line1, address_line2,key_label FROM tblproperty"
cmdProperty.Connection = con
daProperty.SelectCommand = cmdProperty
daProperty.Fill(myData)
cmdUser.CommandText = "SELECT known_name FROM tbluser"
cmdUser.Connection = con
daUser.SelectCommand = cmdUser
daUser.Fill(myData)
myReport.Load("REPORT LOCATION")
myReport.SetDataSource(myData)
myReport.Database.Tables(0).SetDataSource(myData.Tables(0))
CrystalReportViewer1.ReportSource = myReport '
Catch myerror As MySqlException
MsgBox(myerror.Message)
End Try
End Sub
End ClassHi,
You have 3 SQL commands but you are calling SetDataSource only once. You need to look through for each of the SQL Commands.
Good luck,
Brian -
Setting Default Configuration in 1.4.2
Previous versions of Java Web Start had a default configuration file javaws.cfg which contained the default preferences. When JWS was installed on PCs in our intranet, we could switch the cfg file to one which, amongst other things, set the proxy correctly and disabled shortcut creation. Then when any other user logged on to the PC, they would get a copy of this cfg file.
But in JWS 1.4.2 there no longer seems to be a default cfg file. When a user logs on they get defaults which are incorrect for our environment. This is a problem when several different users share the same PC. Whenever a new user logs on to the PC and uses Java Web Start, we must set up the preferences manually.
Our users are in a call center and are not capable of setting preferences themselves. In fact in the past we have removed the JWS icon from the desktop because we don't want them to even know it exists. All they know how to do is click a link (to a jnlp document) on a web page.
Is there some way to set the default preferences at install time that I've missed?
Thanks,
Simon.Educated guesswork mostly; read over the JavaOne "whats new with web start" to get a feel for the changes yourself (http://servlet.java.sun.com/javaone/sf2003/conf/sessions/display-1486.en.jsp). Several things here will lead to internal changes. While it's location isn't likely to change (they're in the right place now - in the user profile dir) the contents, structure and config files certainly will.
Biggest single change is the unification of Java Plugin and Web Start, according to the slides this includes the merging of the applet & web start caches and configuration dialogs (it's not a big leap to assume this means merging their config files also). The new 1.5 Jar Hyper Compression format will also doubtless come into play changing the very format of the Jars getting cached. The other big change is to the security system - both opening up the sandbox model and a new central administration system will mean that the preferences on a users machine may be overridden at any time by the administrator. The cache structure itself undergos a big change with the new 'System Cache' - given that users cannot read from another users profile, this system cache will need to be stored in some shared directory elsewhere. A move that will split normal operation into a pair of active caches further obfuscates assumptions about the internal structure somewhat. This only scratches the surface here - needless to say, big changes ahead.
For the 'system cache' It'll be interesting to see how the web start team get around the default privileges assigned to a domain user under XP typically doesn't allow writing to a directory outside of their user profile folder (default privs are restricted). Similarly I'd like to see how well the new JNLP file associations work out in a similar scenario. Adding a file association requires writing to the registry; this again is typically a prohibited operation requiring local administrator rights to the machine. I hope the web start team have come up with answers to these problems and not just take the Java update line of only working while the user is logged on as a local administrator (http://www.javadesktop.org/forums/thread.jspa?threadID=184&tstart=0). This severely limits your user base to non-networked single user machines (home users), the network admins machine and windows 98 & me boxes which don't share the security model.
Finally it's not a good idea to make any assumptions about the internal layout and contents of any of Sun's undocumented services, it's always going to be prone to change without warning. Developers make changes to these at their own peril and only have themselves to blame when their code suddenly stops working.
- Richard -
Union tables from multiply data srouces in OBIEE
Hi Pros,
Recenetly I am doing a POC about union the same structure table from multiply data sources through OBIEE, uptill now I still can't make that out, I have tried below ways :
Precondition: I have configured those two tables under one physical folder with two connection pool
1. When do the union in physical level, can not implement since either can not create a view union two tables or using SQL.
2. When do the union in Logical level, can not implement also
I know that this kind of data integration should be done before we import into OBIEE model, but there is some policy that we can't integrate, so I just wondering whether OBIEE has this functionlity that can union data from different data source. Please advise.
thanksHi Srinivas
After a second thought, I am wondering what you mean in the post, but the situation is that there are two tables in different data sources, Table-A and Table-B in the Physical layer, they are not yet integrated into one table(let's say Table-C), you mean add a data source indictor column into a table in BMM layer, I want to know how can we integrate data (UNION), because from my perspective, if TABLE-A have bleow column ID,NAME,ADDRESS, while the TABLE-B have the same, the difference is the data bwtween them, even we create a logicl table in BMM, drag those those columns, we only get ID,NAME,ADDRESS,ID#,NAME#,ADDRESS#, but the table structure is different.
The problem is how to create a logic table like TABLE-D (ID,NAME,ADDRESS) which have the data both from TABLE-A and TABLE-B in Physical Layer. While no need to filter by prompt about the data sources. We need to show the data altoghter.
Please advise if I missing you point.
thanks
Edited by: Henry He on Dec 28, 2010 3:21 PM -
Create a table from a spreadsheet
Hi All,
I know you can load data to a table from a spreadsheet using sqlldr, sql developer, toad, etc.. My only knowledge is loading a table from the spreadsheet, but first the table must exist.
Is there any utility that enable you to create and loada table from a spreadsheet? i.e. without having to create the empty table first.
Regards,
kpI found my script. This should work on a csv format file from 1-15 columns. It creates an external table called csv data. You can then query against it and run reports or load into other tables.
CREATE OR REPLACE DIRECTORY &1 as '<directory_path>';
grant read on directory &1 to public;
alter session set current_schema=&1;
--drop table csv_data;
CREATE TABLE csv_data
col1 VARCHAR2(250),
col2 VARCHAR2(250),
col3 VARCHAR2(250),
col4 VARCHAR2(250),
col5 VARCHAR2(250),
col6 VARCHAR2(250),
col7 VARCHAR2(250),
col8 VARCHAR2(250),
col9 VARCHAR2(250),
col10 VARCHAR2(250),
col11 VARCHAR2(250),
col12 VARCHAR2(250),
col13 VARCHAR2(250),
col14 VARCHAR2(250),
col15 VARCHAR2(250)
ORGANIZATION EXTERNAL
( TYPE ORACLE_LOADER
DEFAULT DIRECTORY &1
ACCESS PARAMETERS
(RECORDS DELIMITED BY newline
NOBADFILE
NODISCARDFILE
NOLOGFILE
SKIP 0
FIELDS TERMINATED BY ","
OPTIONALLY ENCLOSED BY '"'
RTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
col1 CHAR, col2 char,col3 char,col4 char,col5 char,col6 char,col7 char,col8 char,col9 char,
col10 char,col11 char,col12 char,col13 char,col14 char,col15 char
LOCATION (&1:'csv_data')
REJECT LIMIT Unlimited
NOPARALLEL
NOMONITORING
grant select on &1 .csv_data to public
/ -
Export Missing table on 11GR2 ?
I'm observing this mystery on our 11.2.0.1.0 system running under Solaris about mysterious missing tables that really exist on the database.
Here is the log of my session trying to export an existing table and export cant seem to find it .
-bash-3.00$ . oraenv
ORACLE_SID = [oracle] ? HR90
The Oracle base for ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome01 is /u01/app/oracle
-bash-3.00$ sqlplus system
SQL*Plus: Release 11.2.0.1.0 Production on Thu Sep 9 11:35:43 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> set lines 200
SQL> column object_name format a30
SQL> select object_name,owner,object_type
2 from dba_objects
3 where object_name = 'PSCLASSDEL' ;
OBJECT_NAME OWNER OBJECT_TYPE
PSCLASSDEL PUBLIC SYNONYM
PSCLASSDEL SYSADM TABLE
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
-bash-3.00$
exp sysadm tables=PSCLASSDEL file=PSCLASSDEL.dmp
Export: Release 11.2.0.1.0 - Production on Thu Sep 9 11:41:51 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
EXP-00011: SYSADM.PSCLASSDEL does not exist
Export terminated successfully with warnings.
Even a full export of the schema does not include these "missing" table at all.
Has anyone encounteed this on 11gR2
Thanks.Thanks . This seems to be a new parameter in 11gR2 . It just got me by surprise that Oracle set it to true by default changing the old behaviour . Inserting records is really not an option but there are modules in the system that does check these table's existence after an import restore. I'm going to be using expdp to get these tabs back. Anyway all seems well . Thanks to all who responded.Have a great day .
Edited by: jodsum on Sep 9, 2010 12:36 PM -
Access 2013 crashed when I export a table from the access
Hi!
Access 2013 always crashed when I export a table from the access to the Database Symfoware.
1、The conditions of the Access 2013 crashed are the follows.
1)Create a table in the Access 2013.
2)Using the ODBC driver of the Database Symfoware to export the table from the access to the Database Symfoware.
2、The Environments are the follows.
1)Access 2013 X64(Version:15.0.4420.1017)
2)Win2008R2 X64
3)Symfoware V11.1 X64
3、The Application log from the Win2008R2 are follows.
ログの名前: Application
ソース: Application Error
日付: 2014/04/18 16:21:06
イベント ID: 1000
タスクのカテゴリ: (100)
レベル: エラー
キーワード: クラシック
ユーザー: N/A
コンピューター: WIN-29UTU2AIK6J
説明:
障害が発生しているアプリケーション名: MSACCESS.EXE、バージョン: 15.0.4420.1017、タイム スタンプ: 0x50674523
障害が発生しているモジュール名: ACECORE.DLL、バージョン: 15.0.4420.1017、タイム スタンプ: 0x506742b7
例外コード: 0xc0000005
障害オフセット: 0x0000000000171f36
障害が発生しているプロセス ID: 0xb6c
障害が発生しているアプリケーションの開始時刻: 0x01cf5ad638668c5b
障害が発生しているアプリケーション パス: C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE
障害が発生しているモジュール パス: C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL
レポート ID: 00e87957-c6ca-11e3-ad2c-0050568d2ced
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-18T07:21:06.000000000Z" />
<EventRecordID>3442</EventRecordID>
<Channel>Application</Channel>
<Computer>WIN-29UTU2AIK6J</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>15.0.4420.1017</Data>
<Data>50674523</Data>
<Data>ACECORE.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>506742b7</Data>
<Data>c0000005</Data>
<Data>0000000000171f36</Data>
<Data>b6c</Data>
<Data>01cf5ad638668c5b</Data>
<Data>C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE</Data>
<Data>C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL</Data>
<Data>00e87957-c6ca-11e3-ad2c-0050568d2ced</Data>
</EventData>
</Event>
4、When the access crashed,I got the dump file .Then I use the Windbg got some information from the dump files.
The detailes are follows.
FAULTING_IP:
+58872faf03d6dd84
00000000`00000000 ?? ???
EXCEPTION_RECORD: 00000000001723c0 -- (.exr 0x1723c0)
ExceptionAddress: 000007fee3951f36 (ACECORE+0x0000000000171f36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD: 00000000000010b8
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: MSACCESS.EXE
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ACECORE
FAULTING_MODULE: 0000000076eb0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 506742b7
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
MOD_LIST: <ANALYSIS/>
CONTEXT: 0000000000171ed0 -- (.cxr 0x171ed0)
rax=0000000001be3598 rbx=0000000000000000 rcx=01cf5d1b0f402a5c
rdx=0000000009cfad30 rsi=0000000006688ef0 rdi=0000000001be35d0
rip=000007fee3951f36 rsp=0000000000172490 rbp=00000000001727a0
r8=0000000009b409d0 r9=0000000006688ef0 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000001be19f0
r14=0000000009cfad30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
ACECORE+0x171f36:
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12 ds:00000000`00000000=????????????????
Resetting default scope
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000007fee395c095 to 000007fee3951f36
STACK_TEXT:
00000000`00172490 000007fe`e395c095 : ffffffff`ffffffff 00000000`00000000 00000000`01bddaa2 ffffffff`ffffffff : ACECORE+0x171f36
00000000`001727b0 000007fe`e388f8eb : 000007fe`e399dc10 000007fe`e399dc30 000007fe`e399dc50 00000000`000000f9 : ACECORE+0x17c095
00000000`00172b50 000007fe`e388f590 : 00000000`06688ef0 00000000`00000004 00000000`000000f9 00000000`00000000 : ACECORE+0xaf8eb
00000000`00172ba0 000007fe`e388f406 : 00000000`00000004 00000000`000000f9 00000000`11cb1130 00000000`000000f9 : ACECORE+0xaf590
00000000`00172c30 000007fe`e391aee7 : 00000000`00000000 00000000`00173198 00000000`06688ef0 00000000`11cb0998 : ACECORE+0xaf406
00000000`00172c70 000007fe`e3933a72 : 00000000`00400100 00000000`00000002 00000000`00000001 00000000`06688ef0 : ACECORE+0x13aee7
00000000`00172e50 000007fe`e384e5b1 : 00000000`00000000 00000000`11cb0020 00000000`06688ef0 00000000`00000001 : ACECORE+0x153a72
00000000`00172e90 000007fe`e38358d1 : 00000000`000007ff 00000000`06688ef0 00000000`01bd99f0 00000000`00000000 : ACECORE+0x6e5b1
00000000`00173280 000007fe`e38718eb : 00000000`000007ff 00000000`06688ef0 00000000`11cb0000 00000000`00000000 : ACECORE+0x558d1
00000000`00173340 00000001`3f3b0cd2 : 00000000`0a0945c0 00000000`000000fe 00000000`000007ff 00000000`00000000 : ACECORE+0x918eb
00000000`00173430 00000001`3f3b0b9b : 00000000`00173730 00000000`001741e0 00000000`065e5b00 00000000`00000100 : MSACCESS!CreateIExprSrvObj+0x16af32
00000000`00173630 00000001`3f3afcea : 00000000`00173730 00000000`00000000 00000000`00000000 00000000`065e5b00 : MSACCESS!CreateIExprSrvObj+0x16adfb
00000000`001736a0 00000001`3f983140 : 00000000`00174401 00000000`0a3235e0 00000000`0a319aa0 00000000`00179fc8 : MSACCESS!CreateIExprSrvObj+0x169f4a
00000000`00174290 00000001`3f3aabeb : 00000000`00000000 00000000`00000000 00000000`00179f38 00000000`00000000 : MSACCESS!FUniqueIndexTableFieldEx+0x26ab4
00000000`00174530 00000001`3f3a9670 : 00000000`001778e0 00000000`00179f38 00000000`00000031 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x164e4b
00000000`00177870 00000001`3f3a8c1b : 00000000`00000010 00000000`108c5990 003d0044`00570050 00000000`74ac3f69 : MSACCESS!CreateIExprSrvObj+0x1638d0
00000000`001779d0 00000001`3f5450df : 00000000`0a0945c0 00000000`0000009c 00000000`0a0945c0 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x162e7b
00000000`00179e30 00000001`3f64e915 : 00000000`43ed8000 00000000`00000000 00000000`3f800000 00000000`00000000 : MSACCESS!FillADT+0x5830b
00000000`0017c450 00000001`3f33b172 : 00000000`00000000 00000000`0006075e 00000000`0017e370 00000000`00000000 : MSACCESS!IdsComboFillOfActidIarg+0xaddf1
00000000`0017d730 00000001`3f33a9ef : 00000000`0017e0a0 00000000`00000b86 00000000`00000000 00000000`0fea0000 : MSACCESS!CreateIExprSrvObj+0xf53d2
00000000`0017d790 00000001`3f33a20c : 00000000`06620400 00000000`00000000 00000000`00000001 00000000`0017e420 : MSACCESS!CreateIExprSrvObj+0xf4c4f
00000000`0017e400 00000001`3f6019cd : 0071023b`007a000a 00000000`00374a30 00000000`00000005 00000000`0000000c : MSACCESS!CreateIExprSrvObj+0xf446c
00000000`0017e850 00000000`06706fd5 : e2504700`aa00ee81 00005d1b`0f2363ea 00000000`0017e9e0 00000001`3f200000 : MSACCESS!IdsComboFillOfActidIarg+0x60ea9
00000000`0017e8f0 00000000`0a30c378 : 00000000`00000000 00000000`00000008 00000000`067069ac 00000000`00000000 : 0x6706fd5
00000000`0017e960 00000000`00000000 : 00000000`00000008 00000000`067069ac 00000000`00000000 00000000`00000008 : 0xa30c378
FOLLOWUP_IP:
ACECORE+171f36
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ACECORE+171f36
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ACECORE.DLL
STACK_COMMAND: .cxr 0x171ed0 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_ACECORE.DLL!Unknown
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/MSACCESS_EXE/15_0_4420_1017/50674523/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1
Followup: MachineOwner
5、Where the access crashed I used the ODBC trace to get the trace log of the ODBC API.
The ODBC API called by Access before it crashed are the follows.
I also ansysised the log,and I did not find any Abnormal.
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
6
SWORD
-8 <SQL_C_WCHAR>
PTR 0x00000000002C1F20 [
12] "LENGTH"
SQLLEN 62
SQLLEN * 0x00000000002C1E38 (12)
Test 1174-10f0
ENTER SQLGetData
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38 (-1)
Test 1174-10f0
ENTER SQLFetch
HSTMT 0x0000000009F7C490
Test 1174-10f0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0x0000000009F7C490
Test 1174-10f0
ENTER SQLFreeStmt
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
Test 1174-10f0
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
6、I also did the test with the Access 2010,and with the Sql Srever/Oracle.
The results are the follows.
1) With the Access 2010(X86 or X64) and Access 2013 X86,it successes when I export the table to the DB Symfoware.But only with the Access 2013 X64,the Access crashed.
2)With the Access 2010(X86 or X64) and Access 2013(X86 or X64),using the Sql Srever/Oracle,it always successes .
According to all the descrived above, I wonder if it a bug of the Access2013 .
Could anyone can help me ?
Thanks for any help.George Zhao
Thank you for your help.
I have already install
the latest patches of the Office 2013.But it doesn't work.It is down also too. And ODBC
drive of Database Symfoware is the newest driver of the Database Symfoware. Now I wonder that
if it si a bug of the ODBC
drive of Database Symfoware,I should fix the bug,but I have analysised the odbc trace log and I do not find any wrongs ,so I think maybe it is a bug of the Access .
I have see many situations about the Access down on the internet . -
Importing internal table from one program to another program
Hi everybody,
i have one small doubt.
i am using submit statement and passing the values from this program to another program selection screen. in that program logic is written.In that program one internal table values are being exported to the memory id of that program. now i have to import that internal table values into my program by using import statement. i am using the following syntax
import itab from menory id 'program name'.
but i am getting an error saying program name is unknown.
what is the exat syntax for this .
thanking you,
giri.hi,
check these statements.
IMPORT - Get data
Variants:
1. IMPORT obj1 ... objn FROM DATA BUFFER f.
2. IMPORT obj1 ... objn FROM INTERNAL TABLE itab.
2. IMPORT obj1 ... objn FROM MEMORY.
3. IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.
4. IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.
5. IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
6. IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
7. IMPORT obj1 ... objn FROM LOGFILE ID key.
8. IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
9. IMPORT (itab) FROM ... .
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. For more details, see Storing Cluster Tables.
Variant 1
IMPORT obj1 ... objn FROM DATA BUFFER f.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... ACCEPTING PADDING
4. ... ACCEPTING TRUNCATION
5. ... IGNORING STRUCTURE BOUNDARIES
6. ... IGNORING CONVERSION ERRORS
7. ... REPLACEMENT CHARACTER c
8. ... IN CHAR-TO-HEX MODE
9. ... CODE PAGE INTO f1
10. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See You Cannot Use Implicit Field Names in Clusters.
Effect
Imports the data objects obj1 ... objn from the data buffer declared. The data buffer must be of type XSTRING . The data objects obj1 ... objn can be fields, structures, complex structures, or tables. The system imports all the data that has been stored in the data buffer f using the EXPORT ... TO DATA BUFFER statement and is listed here. It also checks that the structure used in the IMPORT statement matches the one in the EXPORT statement.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. The contents of all the objects remain unchanged.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is stored in the field f.
Addition 3
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end
of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 4
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR
fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 5
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is
relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Addition 6
...IGNORING CONVERSION ERRORS
Effect
This addition prevents the system from triggering a
runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.
Addition 7
... REPLACEMENT CHARACTER c
Effect
The replacement character is used if a particular
character cannot be converted when the character set is converted.
This addition can only be used in conjunction with addition 6.
Addition 8
... IN CHAR-TO-HEX MODE
Effect
Not all character-type fields are converted. To convert
a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.
You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters.
Moreover, you cannot use this addition in conjunction with the additions 3, 4, 5, 6, or 7.
Addition 9
... CODE PAGE INTO f1
Effect
The code page of the exported data is stored in the
character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.
Addition 10
... ENDIAN INTO f2
Effect
The byte order (LITTLE or BIG) of the
exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.
Variant 2
IMPORT obj1 ... objn FROM INTERNAL TABLE itab.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... ACCEPTING PADDING
4. ... ACCEPTING TRUNCATION
5. ... IGNORING STRUCTURE BOUNDARIES
6. ... IGNORING CONVERSION ERRORS
7. ... REPLACEMENT CHARACTER c
8. ... IN CHAR-TO-HEX MODE
9. ... CODE PAGE INTO f1
10. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See No implicit field names in cluster.
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from the specified internal table itab. The first column in the internal table must be of the predefined type INT2 and the second must be type X. To define the first column you must refer to a data element in the ABAP Dictionary that has the predefined type INT2.
All data that was stored in the internal table itab using EXPORT ... TO INTERNAL TABLE and listed, is imported. The system checks that the EXPORT and IMPORT structures match.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the specified data cluster were imported, the rest remain unchanged (it is possible that no data object was imported).
SY-SUBRC = 4:
The data objects could not be imported.
The contents of all listed objects remain unchanged
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
Places the object in the field f.
Addition 3
... ACCEPTING PADDING
Effect
This addition allows you to add new fields to the ends
of structures, even to substructures and internal tables (the additional fields are filled with initial value during the IMPORT). It also allows you to increase the size of existing fields (C, N, X, P, I1, and I2) and to map Char fields to STRING type fields or byte fields to XSTRING type fields.
Addition 4
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR
field or omit the last component on the highest level (till Release 4.6 this was possible without specifying an addition).
Addition 5
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the page order is
relevant, that is any substructures match. With this addition, the system also ignores alignment changes arising from the Unicode conversion (for example, due to subsequent insertion of named includes).
This addition rules out any subsequent structural enhancements (addition 3) or structural shortening (addition 4) because with this addition it is the structural limits and include limits that are to be ignored.
As from Release 6.10, the include information will also be stored in the dataset, so that it is possible to also check whether the includes match, that is substructures and includes (named or unnamed) are treated the same. When importing data that was exported in a Release lower than 6.10, the includes are not checked.
Addition 6
...IGNORING CONVERSION ERRORS
Effect
This addition has the effect that an error in the
character set conversion does not cause a runtime error. The system uses "#" as a replacement character.
Addition 7
... REPLACEMENT CHARACTER c
Effect
The system uses the specified replacement character if a
character cannot be converted during a character set conversion. If this addition is not specified, the system uses "#" as a replacement character.
This addition can only be used in conjunction with addition 6.
Addition 8
... IN CHAR-TO-HEX MODE
Effect
No character type fields are converted. For this you
must create a field or structure that is identical to the exported field or exported structure, except that all character type fields must be replaced with hexadecimal fields.
This addition, which is only allowed in programs with a set Unicode flag, allows you to import binary data disguised as single byte characters. This addition cannot be used in conjunction with additions 3, 4, 5, 6, and 7.
Addition 9
... CODE PAGE INTO f1
Effect
The codepage of the exported data is stored in the
character-type field f1 (for example, to be able to analyze the data imported with the addition IN CHAR-TO-HEX MODE).
Addition 10
... ENDIAN INTO f2
Effect
The byte order (LITTLE or BIG) of the
exported data is stored in the field f2 (for example, to be able analyze the data imported using the addition IN CHAR-TO-HEX MODE). The field f2 must be of type ABAP_ENDIAN, defined in type group ABAP. You must therefore include the type group ABAP in the ABAP program with a TYPE-POOLS statement.
Variant 3
IMPORT obj1 ... objn FROM MEMORY.
Extras:
1. ... = f (for each object to be imported) 2. ... TO f (for each object to be imported)
3. ... ID key
4. ... ACCEPTING PADDING
5. ... ACCEPTING TRUNCATION
6. ... IGNORING STRUCTURE BOUNDARIES
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See You Must Enter Identification and Cannot Use Implicit Field Names inClusters
Effect
Imports data objects obj1 ... objn (fields, structures, complex structures or tables) from a data cluster in the ABAP memory (see EXPORT). Reads in all data without an ID that was exported to memory with "EXPORT ... TO MEMORY.". In contrast to the variant IMPORT FROM DATABASE, it does not check that the structure matches in EXPORT and IMPORT.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because the ABAP memory was empty.
The contents of all objects remain unchanged.
Note
You should always use the addition 3 (... ID key) with the statement. Otherwise, the effect of the variant is not certain (EXPORT statements in different parts of a program overwrite each other in the ABAP memory), since it exists only for reasons of compatibility with R/2.
Additional methods for selecting and deleting data clusters in the ABAP memory are provided by the system class CL_ABAP_EXPIMP_MEM.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Addition 3
... ID key
Effect
Imports only data stored in ABAP memory under the ID key.
Notes
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Addition 4
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 5
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR field, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 6
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Related
EXPORT TO MEMORY, DELETE FROM MEMORY, FREE MEMORY
Variant 4
IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.
Extras:
1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)
3. ... CLIENT g (before ID key)
4. ... TO wa (after itab(ar) or ID key )
5. ... ACCEPTING PADDING
6. ... ACCEPTING TRUNCATION
7. ... IGNORING STRUCTURE BOUNDARIES
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See You Cannot Use Implicit Field Names in Clusters and You Cannot Use Table Work Areas.
Effect
Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from shared memory. The data objects are read using the ID key from the area ar in the table itab - c.f. EXPORT TO SHARED MEMORY). You must use itab to specify a database table although the system reads from a memory table with the appropriate structure.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. You may have used the wrong ID. The contents of all the objects remain unchanged.
Notes
The table dbtab named according to SHARED MEMORY must be declared using TABLES (except in addition 2).
The structure of fields (field symbols and internal tables) to be imported must match the structure of the objects exported in the dataset. The objects must be imported under the same names as those under which they were exported. Otherwise, they will not be imported.
The key length consists of: the client (3 digits, but only if tab is client-specific); area (2 characters); ID; and line number (4 bytes). It must not exceed 64 bytes - that is, the ID must not be longer than 55 characters, if the table is client- specific.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the shared memory are provided by the system class CL_ABAP_EXPIMP_SHMEM.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is stored in the field f.
Addition 3
... CLIENT g (before ID key)
Effect
The data is imported from client g (provided the import/export table is tab client-specific). The client, g must be a character-type data object (but not a string).
Addition 4
... TO wa (after itab(ar) or ID key)
Effect
You need to use this addition if user data fields have been stored in the application buffer and are to be read from there. The work area wa is used instead of the table work area. The target area must correspond to the structure of the called table tab.
Addition 5
... ACCEPTING PADDING
Effect
This addition allows you to: append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 6
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 7
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 4 (enlarge structure) or addition 5 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Related
EXPORT TO SHARED MEMORY, DELETE FROM SHARED MEMORY
Variant 5
IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.
Extras:
1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)
3. ... CLIENT g (before ID key)
4. ... TO wa (last addition or after itab(ar))
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See Cannot Use Implicit Fieldnames in Clusters und Cannot Use Table Work Areas.
Effect
Imports data objects obj1 ... objn (fields or
tables) from the cross-transaction application buffer. The data objects are read in the application buffer using the ID key of the area ar of the buffer area for the table itab (see EXPORT TO SHARED BUFFER). You must use dbtab to specify a database table although the system reads from a memory table with an appropriate structure.
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this means that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Example
Import two fields and an internal table from the application buffer with the structure INDX:
TYPES: BEGIN OF ITAB3_LINE,
CONT(4),
END OF ITAB3_LINE.
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',
F1(4),
F2(8) TYPE P DECIMALS 0,
ITAB3 TYPE STANDARD TABLE OF ITAB3_LINE,
INDX_WA TYPE INDX.
Import data.
IMPORT F1 = F1 F2 = F2 ITAB3 = ITAB3
FROM SHARED BUFFER INDX(ST) ID INDXKEY TO INDX_WA.
After import, the data fields INDX-AEDAT and
INDX-USERA in front of CLUSTR are filled with
the values in the fields before the EXPORT
statement.
Notes
You must declare the table dbtab, named after DATABASE using a TABLES statement.
The structure of the fields, structures, and internal tables to be imported must match the structure of the objects exported to the dataset. Moreover, the objects must be imported with the same name used to export them. Otherwise, the import is not performed.
The maximum total key length is 64 bytes. It must include: a client if the table is client-specific (3 characters); an area (2 characters); identification; and line counter (4 bytes). This means that the number of characters available for the identification of a client-specific table is 55 characters.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the cross-transaction application buffer are provided by the system class CL_ABAP_EXPIMP_SHBUF.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in the field f
Addition 3
... CLIENT g (after dbtab(ar))
Effect
Takes the data from the client g (if the import/export table dbtab is client-specific). The client g must be a character-type data object (but not a string).
Addition 4
... TO wa (as the last addition or after itab(ar))
Effect
You need to use this addition if you want to save user data fields in the application buffer and then read them from there later. The system uses a work area wa instead of a table work area. The target area must have the same structure as the table tab.
Example
DATA: INDX_WA TYPE INDX,
F1.
IMPORT F1 = F1 FROM SHARED BUFFER INDX(AR)
CLIENT '001' ID 'TEST'
TO INDX_WA.
WRITE: / 'AEDAT:', INDX_WA-AEDAT,
/ 'USERA:', INDX_WA-USERA,
/ 'PGMID:', INDX_WA-PGMID.
Variant 6
IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.
Extras:
1. ... = f (for each object to be imported)
2. ... TO f (for each object to be imported)
3. ... CLIENT g (before ID key )
4. ... USING form
5. ... TO wa (last addition or after dbtab(ar))
6. ... MAJOR-ID id1 (instead of ID key)
7. ... MINOR-ID id2 (with MAJOR-ID id1 )
8. ... ACCEPTING PADDING
9. ... ACCEPTING TRUNCATION
10. ... IGNORING STRUCTURE BOUNDARIES
11. ... IGNORING CONVERSION ERRORS
12. ... REPLACEMENT CHARACTER c
13. ... IN CHAR-TO-HEX MODE
14. ... CODE PAGE INTO f1
15. ... ENDIAN INTO f2
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Fieldnames in Clusters and Cannot Use Table Work Areas.
Effect
Imports data objects obj1 ... objn (fields, structures, complex structures, or tables) from the data cluster with ID key in area ar of the database table dbtab (see EXPORT TO DATABASE).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that not data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.
Example
Import two fields and an internal table:
TYPES: BEGIN OF TAB3_TYPE,
CONT(4),
END OF TAB3_TYPE.
DATA: INDXKEY LIKE INDX-SRTFD,
F1(4), F2 TYPE P,
TAB3 TYPE STANDARD TABLE OF TAB3_TYPE WITH
NON-UNIQUE DEFAULT KEY,
WA_INDX TYPE INDX.
INDXKEY = 'INDXKEY'.
IMPORT F1 = F1
F2 = F2
TAB3 = TAB3 FROM DATABASE INDX(ST) ID INDXKEY
TO WA_INDX.
Notes
You must declare the table dbtab, named after DATABASE, using the TABLES statement (except in addition 5).
The structure of fields, field strings and internal tables to be imported must match the structure of the objects exported to the dataset. In addition, the objects must be imported under the same name used to export them. If this is not the case, either a runtime error occurs or no import takes place.
Exception: You can lengthen or shorten the last field if it is of type CHAR, or add/omit CHAR fields at the end of the structure.
The key, key, must be a character-type data object (but not a string).
Additional methods for selecting and deleting data clusters in the database table specified are provided by the system class CL_ABAP_EXPIMP_DB.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Addition 3
... CLIENT g (before the ID key)
Effect
Data is taken from the client g (in client-specific import/export databases only). Client g must be a character-type data object (but not a string).
Example
DATA: F1,
WA_INDX TYPE INDX.
IMPORT F1 = F1 FROM DATABASE INDX(AR) CLIENT '002' ID 'TEST'
TO WA_INDX.
Addition 4
... USING form
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Effect
Does not read the data from the database. Instead, calls the FORM routine form for each record read from the database without this addition. This routine can take the data key of the data to be retrieved from the database table work area and write the retrieved data to this work area. The name of the routine has the format <name of database table>_<name of form>; it has one parameter which describes the operation (READ, UPDATE or INSERT). The routine must set the field SY-SUBRC in order to show whether the function was successfully performed.
Addition 5
... TO wa (after key or after dbtab(ar))
Effect
You need to use this addition if you want to save user data fields in the cluster database and then read from there. The system uses the work area wa instead of a table work area. The target area entered must have the same structure as the table dbtab.
Example
DATA WA LIKE INDX.
DATA F1.
IMPORT F1 = F1 FROM DATABASE INDX(AR)
CLIENT '002' ID 'TEST'
TO WA.
WRITE: / 'AEDAT:', WA-AEDAT,
/ 'USERA:', WA-USERA,
/ 'PGMID:', WA-PGMID.
Addition 6
... MAJOR-ID id1 (instead of the ID key).
Addition 7
... MINOR-ID id2 (with MAJOR-ID id1)
This addition is not allowed in an ABAP Objects context. See Cannot Use Generic Identification.
Effect
Searches for a record the first part of whose ID (length of id1) matches id1 and whose second part - if MINOR-ID id2 is also declared - is greater than or equal to id2.
Addition 8
... ACCEPTING PADDING
Effect
This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.
Addition 9
... ACCEPTING TRUNCATION
Effect
This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).
Addition 10
... IGNORING STRUCTURE BOUNDARIES
Effect
This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.
You cannot use this addition with either addition 8 (enlarge structure) or addition 9 (shorten structure), since it specifies that structure and include boundaries are to be ignored.
From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.
Addition 11
...IGNORING CONVERSION ERRORS
Effect
This addition prevents the system from triggering a runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.
Addition 12
... REPLACEMENT CHARACTER c
Effect
The replacement character is used if a particular character cannot be converted when the character set is converted. If you do not use this addition, '#' is used as a replacement character.
This addition can only be used in conjunction with addition 11.
Addition 13
... IN CHAR-TO-HEX MODE
Effect
All character-type fields are not converted. To convert a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.
You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters. Moreover, you cannot use this addition in conjunction with the additions 8, 9, 10, 11, and 12.
Addition 14
... CODE PAGE INTO f1
Effect
The code page of the exported data is stored in the character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.
Addition 15
... ENDIAN INTO f2
Effect
The byte order(LITTLE or BIG) of the exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.
Variant 7
IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.
This variant is not allowed in an ABAP Objects context. See Cannot Use Clusters in Files
Note
This variant is no longer supported and cannot be used.
Variant 8
IMPORT obj1 ... objn FROM LOGFILE ID key.
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Extras:
1. ... = f (for each field f to be imported) 2. ... TO f (for each field f to be imported)
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Field Names in Clusters
Effect
Imports data objects (fields, field strings or internal tables) from the update data. You must specify the update key assigned by the system (with current request number) as the key.
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).
SY-SUBRC = 4:
The data objects could not be imported. An incorrect ID may have been used.
The contents of all objects remain unchanged.
Addition 1
... = f (for each object to be imported)
Addition 2
... TO f (for each object to be imported)
Effect
The object is placed in field f.
Variant 9
IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
Extras:
1. ... CLIENT g (after dbtab(ar)) 2. ... TO wa (last addition or after dbtab(ar))
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Table Work Areas.
Effect
Imports an object directory stored under the specified ID with EXPORT TO DATABASE into the table itab. The internal table itab may not have the type HASHED TABLE or ANY TABLE.
The key, key, must be a character-type data object (but not a string).
The Return Code is set as follows:
SY-SUBRC = 0:
The directory was successfully imported.
SY-SUBRC = 4:
The directory could not be imported, probably because an incorrect ID was used.
The internal table itab must have the same structure as the Dictionary structure CDIR (INCLUDE STRUCTURE).
Addition 1
... CLIENT g (before ID key)
Effect
Takes data from the client g (only with client-specific import/export databases). Client g must be a character-type data object (but not a string).
Addition 2
... TO wa (last addition or after dbtab(ar))
Effect
Uses the work area wa instead of the table work area. When you use this addition, you do not need to declare the table dbtab, named after DATABASE using a TABLES statement. The work area entered must have the same structure as the table dbtab.
Example
Directory of a cluster consisting of two fields and an internal table:
TYPES: BEGIN OF TAB3_LINE,
CONT(4),
END OF TAB3_LINE,
BEGIN OF DIRTAB_LINE.
INCLUDE STRUCTURE CDIR.
TYPES END OF DIRTAB_LINE.
DATA: INDXKEY LIKE INDX-SRTFD,
F1(4),
F2(8) TYPE P decimals 0,
TAB3 TYPE STANDARD TABLE OF TAB3_LINE,
DIRTAB TYPE STANDARD TABLE OF DIRTAB_LINE,
INDX_WA TYPE INDX.
INDXKEY = 'INDXKEY'.
EXPORT F1 = F1
F2 = F2
TAB3 = TAB3
TO DATABASE INDX(ST) ID INDXKEY " TAB3 has 17 entries
FROM INDX_WA.
IMPORT DIRECTORY INTO DIRTAB FROM DATABASE INDX(ST) ID INDXKEY
TO INDX_WA.
Then, the table DIRTAB contains the following:
NAME OTYPE FTYPE TFILL FLENG
F1 F C 0 4
F2 F P 0 8
TAB3 T C 17 4
The meaning of the individual fields is as follows:
NAME:
Name of stored object
OTYPE:
Object type (F: Field, R: Field string / Dictionary struc -
How can I hide a field a table from SE16
Hi all,
I have an urgent requirement, can anyone help me? How can I hide or mask any field of a table from SE16. Also how can I restrict the user not to put a restriction on a particular field of a table so that this field should not be accessed for SQVI/SQ01.
Awaiting for reply.
Useful answers will be rewarded immediately with full points.
Tnx.You could hide the column, by using the standard functinoality of the ALV output, you would need to hide the column, and save a default layout. This way the next time you come into this display, the column will not be there.
Regards,
Rich Heilman -
How can I filter a table from Data Control without enter query
I have a table from a web service data control based on WSDL.
I want to filter the table without input query at filter text box. Without filter text box, each would filter the table with a hardcoded query internally.
For example, when user click A menu button then it filters the table where type = '1' and B menu button filters the table by type='2' and C menu button filters the table by type=' ' .
How can I filter the table without enter query?
Could anyone point me to a solution please.
Thanks.
jdev 11.1.5
Edited by: 893364 on Oct 26, 2011 12:15 PM
Edited by: 893364 on Oct 26, 2011 12:21 PMHi,
when you created the table, did you try selecting the "filter" option. Select the table and go to the Property Inspctor. In the tool bar of the Property Inspector there is an icon to change the configuration. Its adding filter filter fields for the user to search in.
Option 2: The data of the Web Service actually is held in the iterators. If you wanted to filter the WebService query, I would not use the WS DC but a JAX-WS proxy in a POJO to fetch the WS Data. Then have the Data Control created from the POJO. You could have a method exposed on the POJO that allows you to filter the internally held data
Frank
Maybe you are looking for
-
Windows software support in Boot Camp
I cant seem to get this to work at all- I have downloaded the Windows support software and burned to a cd. Windows 7 is loaded onto the hard disc and set up and running. I put my CD into the slot and it is seen as a blank CD. I have rebooted in OSX a
-
how do i get the accent marks over the vowels when using my keyboard? It used to work using option + e then the letter but it doesn't do it anymore.
-
How to print a digital edition book I just purchased?
How do I print a digital edition book I just purchased? The print icon is inactive/disabled on the pdf in reader?
-
Help importing 25'000 pictures into phootshop elements 8
I have 25'000 plus jpegs, neff files etc in one folder on hard drive . I want to import into eleements and using elements auto file into new location on hard drive in "date shot" folders. If i transfer a batch of files to SD or CF disc photoshop will
-
My iweb 08 is no longer saving!
When I open iweb my it doesn't save my last updates. On the blog everything is saved however when I update my other pages and click on FILE/SAVE it's supposed to save right??? So I close the program... a few days later the updates I did are gone. Any