Difference between Delta "Change Log" and "Active Table (Without Archive)"?

In BI7.0 environment, we perform our Delta loads (the DTP settings under the Extraction tab, there is a field called Extraction Mode and it's value is selected as "Delta") every day among all our DSOs.
There is a section called "Delta Init. Extraction From..." under the same tab in DTP, there are four radio buttons:
Active Table (With Archive)
Active Table (Without Archive)
Archive (Full Extraction Only)
Change Log
Then what is the difference between "Change Log" and "Active Table (Without Archive)" if both Extraction Mode is "Delta" for two Delta loads?
Thanks!

Hi ,
The new options SP16 has are:(Chk Note 1096771)
Active Table (with Archive)
The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
Active Table (Without Archive)
The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
Archive (Only Full Extraction)
The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
Change Log
The data is read from the change log of the DataStore object.
Delta will always be picked from change log table.Only during intialization you can choose between getting data from change log or active table.If you are doing the load first time and are initializzing delta in subsequent data targets, then pulling data from active table will get lesse volume of data then it would have got from change log table....All subsequent deltas will be picked up from the change log. And when we need to reload data into the data target (which would be a full load) - we use active table.
From change log : you can take below ones as targets
1) Cube 2) DSO with Addition as the update for the Keyfigures
From Active table: you can take below ones as targets
1) Cube ,if and only if, the records are never changes in the source once after creation
2) DSO with Addition as the update for the Keyfigures ,if and only if, the records are never changes in the source once after creation
3) DSO with Overwrite as the update for the Keyfigures ( incase deletions is not happening in the source system)
Pls check this link
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/e8c56ecd313c86e10000000a42189c/frameset.htm
Regards,
CSM Reddy

Similar Messages

Difference between the Field Group and Internal Table.

Hi all,
Can anybody tell me the difference between the Field group and Internal table and when they will used?
Thanks,
Sriram.

Hi
Internal Tables: They are used to store record type data in tabular form temporarily in ABAP programming. Or we can say, it stores multiple lines of records for temporary use in ABAP programming.
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
Regards
Ashish

Difference between on change of and at end of :

Hi Can any one explain me what is the exact difference between on change of and at end of .
I know the basic differences.
But i would like to know in which case we can use the above two statemetns.
Suppose :
Matnr   plant       sloc       movementype      date                          qty
12       001          002           261                12/11/08                    10
12      001          002            261               12/11/08                      11
12      002          003            261               12/11/08                      12
Here i need to add the quantity based up on the material,
If the materials is maintained in different plants then it should give the total for for that particular plant.
Please help me how to build logic to this :
Regards,
Vinay.

ok sure i will give it to u.
MATNR       PLANT          SLOC            BWART           BUDAT         QTY1           QTY2           QTY3             QTY4            QTY5
127874     2501     3025     200906     201     0.000     0.000     0.000     0.000     0.000
                     QTY6           QTY7             QTY8             QTY9           QTY10         QTY11            QTY12
     0.000     0.000     0.000     0.000     0.000     0.364     0.000
127874     2501     3025     200905     201     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     7.000     0.000     0.000
127874     2501     3025     200905     202     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     1.000     0.000     0.000
127874     2501     3025     200905     261     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     35.000     0.000     0.000
127874     2501     3025     200905     551     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     5.000     0.000     0.000
Here i need to write the logic for that material usage :
This material usage will be caliculated based upon the movement types in that particular month :
The formula is :
AT END OF BUDAT.
     FINAL_VALUE_WA-KWMENG12 =   ( W_QTY261 -   W_QTY262 ) + ( W_QTY201 - W_QTY202 ) + ( W_QTY551 - W_QTY552 ).
      CLEAR : W_QTY261,W_QTY262,W_QTY201,W_QTY202,W_QTY551,W_QTY552.
    ENDAT.
Here iam writting the logic as at end of the month iam caliculating.
But what my question is if we have same material in different plant and the usage is in the same month
then i think this query is going to fail.
Edited by: vinay raj on Jul 6, 2009 2:02 PM
Edited by: vinay raj on Jul 6, 2009 2:03 PM

Difference between a Change-run and Activate master data

Hi experts,
Could you tell me what is the difference between making a change-run on a masterdata (rsa1 --> Tools --> Apply Hierarchy/Attribute Change...), and making a right-click on this masterdata and click on "Activate master data" ?
The result seems to be the same, all rows in version M (Revised) are changed in version A (Active)...
Thanks for your help.
Tempka.

Hi
Change run will update the master data changes in Aggregates and update the object master data as well.
Activate master data will only activate the new records and it will not update the aggregates.
check out the below thread
Attribute Change Run VS Master data activation
Regards,
Vekatesh

In Request type, what is the difference between action 'Change user' and 'Assign object'

Dear All,
I have used only 'Assign Object' for my 'Change User' request type. But the standard request type has 'Change user'. So, could you suggest , what additional purpose does Change Object serve
Regards
Plaban

HI Plaban
not sure if you answered your own question here?
Change User - by itself would allow update of address data, user parameters, defaults, etc
Assign Object - as you mentioned roles and profiles.
However, if assigning, I think you need to have both actions: change and assign
I recall (ages ago) that change was only the user details and not the role or profiles. As a result, there were a few threads where people had to update the action for the request type of provisioning would not occur.
This is something you could test
Regards
Colleen

Actual difference between a standard , sorted and hashed atble

hi ,
1. what is the actual difference between a
standard,sorted and hashed table ? and
2. where and when these are actually used and applied ?
provide explanation with an example ....

hi
good
Standard Internal Tables
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Internal Tables
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Internal Tables
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
THANKS
MRUTYUN

In Reports what is the difference between the AT NEW and ON CHANGE Event

Hi,
Could you tell the differences of AT NEW and ON CHANGE events in Repors

Hi raghava,
The Major Difference is :
a) When AT NEW occurs,
the alpha-numeric fields have ******* in their value,
b) where as in case of ON CHANGE,
the alpha-numeric fields have their corresponding value,
of that particular record,
where the Event gets fired.
Other differences are :
ON CHANGE OF can be used any where in the program..
on change of differs from at new in the following respects:
1.It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
2.A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
3.When used within a loop, a change in a field to the left of the control level does not trigger a control break.
4.When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
5.You can use else between on change of and endon.
6.You can use it with loop at it where . . ..
7.You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
8.Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
while
AT NEW can be used only within a loop of an INTERNAL TABLE..
5. Sample program to get the taste of it
(just copy paste)
6.
REPORT ABC.
DATA : BEGIN OF ITAB OCCURS 0,
bukrs like t001-bukrs,
f1(10) type c,
end of itab.
itab-bukrs = '1000'.
itab-f1 = '1111111'.
append itab.
itab-bukrs = '1100'.
itab-f1 = '3333333'.
append itab.
itab-bukrs = '1200'.
itab-f1 = '555555'.
append itab.
AT NEW
loop at itab.
at new bukrs.
write :/ itab-bukrs , itab-f1.
endat.
endloop.
AT ONCHANGE
loop at itab.
ON CHANGE OF ITAB-BUKRS.
write :/ itab-bukrs , itab-f1.
ENDON.
endloop.

Difference between delta queue and unserialized v3 update - lo cockpit

Hi guys,
What is the difference between delta queue and unserialized v3 update.
How does sm13 come into picture. During system outages, how is setup table affected.
Edited by: zsl05 on Apr 22, 2009 11:29 PM

Hi,
In BW there are basically 3 types of delta queue mechanisms
1) Direct Delta: In this, as soon as the data is posted in the application tables, it is transfered to the RSA7 delta queue.
2) Queued delta: In this, as soon as the data is posted, it is first transferred to the Extractor Queue(LBWQ) and then via V3 Collective job to the delta queue periodically. The transfer sequence is the same as the sequence in which the data was created
3) Unserialized V3 : In this,when data is posted to the application table, it is posted into the Update queue first(SM13). It is then transferred to the Extractor queue (LBWQ) and then via V3 jobs to the Delta queue (RSA7). The difference lies in the fact that the sequence in which data was posted in the application table does not matter.
Hope this helps.
Regards.

Difference between Delta download and Initial download

Hi friends
what is the difference between Delta download and Initial download
what Tcodes are used for Delta download and what tcodes used for initial download
regards
krishna v

Hi,
The CRM middleware allows the following two methods for replication.
-Initial loads:
Launched manually (tcode R3AS), the objects (customizing or business) are replicated between SRM and R/3, according to the filters you've put on the object (R3AC1 for Business objects like MATERIAL, R3AC3 for customizing objects like DNL_CUST_PROD0 and 1).
-Delta loads:
This option is only possible for Business objects, which is the case of MATERIAL.
With this option a daemon is launched between the 2 servers. Every modification made on an object on SRM or R/3 is transfered as soon as this object is contained in the filter retrictions (creation and/or modification). this is done through transaction R3AC4.
BR,
Disha.
Do reward points for useful answers.

What is the difference between Delta Upgrade and Supplementary Upgrade

What is the difference between Delta Upgrade and Supplementary Upgrade?
thanks
druva

Hi,
Delta Upgrade - means installing the different add-on release on the same BASIS release.
ex: If you have add-on ERECRUIT 600 on SAP_BASIS 700 and want to upgrade to ERECRUIT 603 on SAP_BASIS 700, then its called Delta- Upgrade
Supplementary Upgrade - means installing the different add-on release on the different BASIS release.
ex: If you have add-on ERECRUIT 300 on SAP_BASIS 640 and want to upgrade to ERECRUIT 603 on SAP_BASIS 700, then its called Supplementary Upgrade.
Regards,
Mahesh
ps: close the thread so that it wil be helpful for others later

What is the Difference between Delta Queue and Extractor Queue?

What is the Difference between Delta Queue and Extractor Queue?

Hi,
please have a look at:
DELTA QUEUE&EXTRACTION QUEUE
Hope this helps.
Regards,
Andrew van Schooneveld
Assigning Points is the way of saying thanks

Difference Between OTL Retro Entry and Salary Change Retro Entry in Payroll

Hi Everyone,
We are developing a custom interface from Payroll to Projects which will post all the entries from OTL.
OTL->Payroll->Projects
We are stuck with identifying the Difference Between OTL Retro Entry and Salary Change Retro Entry when we process Retropay in Payroll.
After retropay, we come we would see the retro element entries for both them with same name and creator_type is either EE or RR for both them.
In our interface we have to treat retro entries through OTL and Salary Change in differentway.
Has anyone can give some suggestions on this please asap as we are heading towards UAT very soon.
Thanks in Advance..!!
Anand

Hi Anand,
Element with creator_type RR are created/generated by Retropay.
Elements with creator_type EE are regular element entries.

Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database.

Hello Team,
We are configuring Change Request management in Solution manager.
Activation of BC sets ends with warning.Activation log shows below error.
'Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database. Check values'
There errors like "
Field Not Copied
Difference between BC Set and Table"
We are through with note :903527 which suggest "2) Create a new transport request (Transaction SE09) in the source client of your Solution Manager system. Unpack the file Piecelist_Change_Management_Init.zip, which is attached to this note. Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request. Use Transaction SCC1 to import the transport request into your Solution Manager client"
But how to "Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request"?
Please let me know if you have any hint.
Best Regards,
Tushar

status/action??
when u click action tab in maintenance transaction the status updated auomatically.
have u checked the errors shown in error tab....after u removed the errors....
thn u choose up 'update maintenance cycle' action press save button the status will be same but error button wiil be green
Then u have action Next phase"'in dev with release"
If it is not appearing even there is no error........Pls ck the action profile or ask solman consultant to chk the same
Hope it clarifies
Regards
Prakhar

What are differences between the target tablespace and the source tablespac

The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
Why create so many errors?
How to avoid these errors?
What are differences between the target tablespace and the source tablespace?
Is this datapump action really successfull?
Thw following is the log output:
[oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
. . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
. . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
. . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
. . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
. . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
. . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
. . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
. . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
. . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'USER1' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01917: user or role 'EXAM_03' does not exist
Failing sql is:
GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
Processing object type TABLE_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
BEGIN
SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
Justin

Difference between ECC 6.0 and earlier versions

Hi,
one of the difference between ECC 6.0 and earlier versions is that instead 'WS_UPLOAD' and 'WS_DOWNLOAD' in ECC we should use 'GUI_UPLOAD' and 'GUI_DOWNLOAD' respectively.
(of course SPDD and SPRO tcodes is known by everone i suppose)
Similarly can u all put down some differences here, atleast one entry by each, I think we can make a good docu. I have searched the net for the differences but could not get much, so by each of us contributing one each, it would become good docu..for all of us.
Thanx in advance

Unicode Errors Encountered and their Solutions
E1. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified.
     Error:
     OPEN DATASET FILE FOR OUTPUT IN TEXT MODE.
     Solution:
     OPEN DATASET FILE FOR OUTPUT IN LEGACY TEXT MODE.
E2. In Unicode, DESCRIBE DISTANCE can only be used with the IN BYTE MODE or IN
      CHARACTER MODE addition.
     Error:
     DESCRIBE DISTANCE BETWEEN T_KOMK AND T_KOMK-HIEBO01 INTO BPOS.
     Solution:
DESCRIBE DISTANCE BETWEEN T_KOMK AND T_KOMK-HIENR01 INTO BPOS
IN CHARACTER MODE.
E3. u201CUSR02-UFLAGu201D must be a byte-type field (Typ X or XSTRING )
     Error:
     IF USR02-UFLAG O YULOCK.
     Solution: Since the data type of USR02-UFLAG is type INT and is compared with data type
                X u2013 Hence the error. So we define a new variable ZULOCK and assign the
                value of USR02-UFLAG to ZULOCK.
              New variable
              DATA: ZULOCK(1) TYPE X.   "APBRP00
              Assign value
                            ZULOCK = USR02-UFLAG.
        Compare -
               IF ZULOCK = YULOCK.   u201Creplace IF USR02-UFLAG O YULOCK.
E4. HT cannot be converted to a Character type field
Error :
WRITE ht TO t_data+10(2).
Solution : Since the data type of ht is a type u2018Xu2019 and the data is been transfer to
         t_data which has a data type u2018Cu2019. value of one data type cannot be copy to
         another data type where one of them is type string .Hence the error occur,
         so the data type of ht is been change to Type u2018Cu2019
     OR
           A Tab ( value 09 ) is introduced as part of the row. The value 09 is not converted in Unicode environment. Instead we need to use class
     Error:
          DATA: BEGIN OF ht,
               x(1) TYPE x VALUE '09',
          END OF ht.
     Solution:
              Define Class after the Tables definition.
                   CLASS cl_abap_char_utilities DEFINITION LOAD.
              Data Defination : Comment internal table HT and define a variable HT type C.
       *   Insert + APRIA00 05/02/2007 Unicode project
       *   DATA: BEGIN OF ht,
     *         x(1) TYPE x VALUE '09'
       *   END OF ht.
     *   Insert - APRIA00 05/02/2007 Unicode project
       DATA HT type C.
       Before using HT assign Horizontal tab.
                 Ht = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
E5. In Unicode programs the u201C#u201D cannot appear in names, as it is does here in the name    u201C#LINESu201D
     Error :
     #LINES                 TYPE I,
     Solution : Since the # is used in the start of name, it is not allowed. We need to
              remove it.
     Solution for the above
     V_LINES                 TYPE I,
E6. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified as well as the addition was required FOR OUTPUT,FOR INPUT, FOR APPENDING OR FOR UPDATE was expected.
     Error:
     OPEN DATASET PATH_NAME IN TEXT MODE.
     Solution:
     Download =     OPEN DATASET PATH_NAME FOR OUTPUT IN LEGACY TEXT MODE.
     Upload        = OPEN DATASET AUSZUG-FILE IN TEXT MODE FOR INPUT ENCODING DEFAULT.
E7. u201CTABu201D must be a character-type data object( data type C,N, D, T or String). Field string)
     Error:
            data: begin of tab,                   "Excel Parameter Split at TAB
        t type x value '09',          "Tabulator
       end of tab.
            concatenate 'Material' 'Package Status'
                into z_download-line separated by tab.
            ( In the above command the two field are to be separated with a horizontal Tab. The earlier      way of assigning the tab value u201809u2019 will not work in Unicode environment.
     Solution:
     Define a class just after the Table defination.
          CLASS cl_abap_char_utilities DEFINITION LOAD.
            Define variable Tab as shown below :
          Data : TAB           TYPE C.
     Before the concatenate statement assign the value of Tab using pre-defined attributes.
          TAB = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
E8. Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not Unicode-
      enabled; use the class cl_gui_frontend_services
     Error-1: Function WS_DOWNLOAD is obsolete in Unicode environment.
            call function 'WS_DOWNLOAD'
                 exporting
                      filename = zfilename
                 tables
                      data_tab = z_download.
     Solutions-1: Instead of WS_DOWNLOAD use GUI_DOWNLOAD.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
*   BIN_FILESIZE                  =
    FILENAME                      = zfilename
TABLES
    DATA_TAB                      = z_download.
E9. The "/" character is reserved for identification of namespaces. It must be entered twice.
        The name of a namespace must be at least 3 characters long.
     Error :
                 U/N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
     Solution :
     * Special character can not be used to define a data variable
     *      U/N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
              U_N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
     * Insert - APSUS02 07/02/2007 Unicode Project
E10. "LP_TAB" and "CS_TAB" are not mutually convertible. In Unicode programs,
         "LP_TAB" must have the same structure layout as "CS_TAB", independent of the length
         of a Unicode character.
     Error : This error is encountered when data from one internal table is copied to another
                         internal table which different structure. In this case its LP_TAB & CS_TAB.
                 LP_TAB[] = CS_TAB[].
     Solution :
          * Replace + APSUS02 07/02/2007 Unicode Project
*   LP_TAB[] = CS_TAB[].
              move-corresponding CS_TAB to LP_TAB.
          * Replace + APSUS02 07/02/2007 Unicode Project
E11. Could not specify the access range automatically. This means that you need a RANGE
          addition.
     Error : Range need to be specified as an addition to the command.
            DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1).
           Solution :
            DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1)
          * Insert + APSUS02 07/02/2007 Unicode Project.
                                                      RANGE ABCD+0(4).
* Insert - APSUS02 07/02/2007 Unicode Project.
E12 . Processing Terminated Error code: Error in opening /
                                          Path not found when downloading to Unix directory.
     Error : PARAMETER: outfile(92) DEFAULT
              '/CP/interface/NPP/data/MX/cbslaprcpts'
                    LOWER CASE,
               kmxmstrd AS CHECKBOX.
            This error is encountered when the path is missing. The above path is related to CCP.
     Solution: For testing purpose comment the original path and replace it with
                                 /CP/interface/CCD/Unicode_test/
E13.    Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not                                                                       Unicode- enabled; use the class cl_gui_frontend_services
     Error: Function WS_UPLOAD is obsolete in Unicode environment. (During UCCHECK)
               Call function 'WS_UPLOAD'
       Exporting
            Filename                = zfilename
            Filetype                = u2018DATu2019
       Tables
            data_tab                = z_upload
       Exceptions
            Conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_table_width     = 4
            invalid_type            = 5
            no_batch                = 6
            unknown_error           = 7
            gui_refuse_filetransfer = 8
            others                  = 9.
     Solution: Instead of WS_UPLOAD use TEXT_CONVERT_XLS_TO_SAP. Do not use temporary file put the file name as it is.
1) First define a type pool and a variable of type truxs_t_text_data.
TYPE-POOLS: truxs.
DATA: it_raw TYPE truxs_t_text_data.
     2) Use this it_raw in the function module in parameter i_tab_raw_data. Put file name and the internal table in the function module.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
*     I_FIELD_SEPERATOR        =
*      i_line_header            = ' '
      i_tab_raw_data           = it_raw       " WORK TABLE
      i_filename               = zfilename
    TABLES
      i_tab_converted_data     = z_upload[]    "ACTUAL DATA
   EXCEPTIONS
      conversion_failed        = 1
      OTHERS                   = 2.
     Comment u201Ci_line headeru201D. It takes the first/ header line of the file which is to be uploaded.
Put square brackets after internal table as shown above.
E14.    CURSORHOLD may not be converted into a number.
     Error: GET CURSOR LINE CURSORHOLD VALUE CURSOR_HOLD.
     Solution: In the declaration part of CURSORHOLD, one field is of u2018Pu2019 type and one field is of u2018Iu2019 type, which is not allowed in Unicode environment.So change the the type of it to NUMC.

Difference between Delta "Change Log" and "Active Table (Without Archive)"?

Similar Messages

Maybe you are looking for