IDOC created with errors!

Hello All,
I am sure that I am not posting this in the right forum. But I did this because, I get more responses in this compared to others. Sorry if this has caused any trouble.
I had extended a standard idoc with 2 customer segments and procesed the idoc file. An idoc got created witht he following error message.
EDI: Syntax error in IDoc (mandatory segment missing)
Message no. E0072
Diagnosis
The segment E1EDK14 has the attribute 'Mandatory' in the syntax description of the basic type /IRM/CHGBACKS01 (customer enhancement ). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.
Procedure
Please check the IDoc or the syntax description of the basic type /IRM/CHGBACKS01 (customer enhancement ).
When we insert new segments, where should we insert? How important is the segment number? Why is this error message even though that mandatory segment is there in the idoc?
Please help.
Thanks,
Lavanya

Hi,
I got the following error message.
Basic type ZCHGBCK does not exist
Message no. EA447
Diagnosis
IDoc type ZCHGBCK could not be found.
Procedure
Please enter an IDoc type that exists.
Srinivasan,
I had tested this with the standard idoc and it was perfect. i am having these issues after extension only.
Thanks,
Edited by: Lavanya Boora on Jun 2, 2008 10:55 PM

Similar Messages

IDoc created with status 03 checked via we02, but couldnt find in XI

Hi all:
Could you please do me a favor? implement a idoc to idoc issue. it has been created successfully .
as It is found that the idoc created with status of 03 -
data dispatched to port ok (rather than 12 dispatch ok). however, I couldn't find it via SXMB_MONI on XI, there must be something wrong . coudl you please give me a hint ?
Thank you very much!!!

hi,
you need to check transaction SM58 (remove the user from it) and F8
it might be the reason that you didn't create a port in IDX1 on XI/PI
but you will see that in SM58
Regards,
Michal Krawczyk

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

ORA-39083: Object type TRIGGER failed to create with error:

i m getting these two error when i import data using impdp.
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
i have exported (expdp) data from production db, when i importing (impdp) the dump file to the test db i m geting the above two errors.
example:
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
CREATE TRIGGER "NEEDLE"."CC_BCK_TRG" BEFORE INSERT OR UPDATE
ON NIIL.cc_bck_mgmt REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
DECLARE
w_date DATE;
w_user VARCHAR2(10);
BEGIN
SELECT USER,SYSDATE INTO w_user,w_date FROM DUAL;
IF INSERTING THEN
:NEW.cretuser :=w_user;
:NEW.cretdate :=w_date;
END IF;
IF UPDATING THEN
:NEW.modiuser :=w_user;
:NEW.modidate :=w_date;
END IF;
END;
status of the above trigger in pro db is valid. and source table also exist even though i m getting error when i import
please suggest me...

perhaps you don't have table... (impdp created trigger before create table)
check about "NIIL.cc_bck_mgmt" table.
and then create it (trigger) manual ;)
Good Luck.

File to IDoc scenario - IDoc received with Errors

Hi,
I tried to send send IDoc from a file to SAP R\3. The communication channels are working fine, and I get the IDocs in R\3 but with status 56. When I examine the received IDoc structure in transaction "WE19", I see that the receiver port(SAP + SID of sap server) is blank with no values. I tested the IDoc adding the receiver port, and the IDoc got successfully posted...
I wonder why the receiver port that I specified in payload file content, does not reflect during runtime. I'm using the downloaded MATMAS IDoc structure with sender and receiver details as the input from file....
Please help me out!
Thanks!!
-Ajitha

Rodrigo/Sarvesh/Ravi/Haseeb,
Thanks for the inputs!! I have checked in IDX1 and the port name is the same. Also "Apply control records values from payload" checkbox is selected. I guess there was some problem with cache. It started working fine, when I started a new session
Thanks for your time and inputs!!!

How can i find the IDoc's with errors

Hi gurus,
How to find the errors in Idocs and How to solve it?How can i rectify the errors?
Thanks in advance.
kumar.

Hi Kumar,
You can goto WE02 T'code and give the IDOC number (check date range). Click on Status Records. It shows the exact error.
If IDOC fails it is gives your the status 51 otherwise it gives you the status 53.
Assign points if useful
~Rajesh

Trigger created with errors

Hi All,
I have created a new trigger but it has compilation errors, I get the error which says SQL command not properly ended when look up in toad.Can you please advise what's wrong in my syntax below.
Also ,inorder for me to rollback the trigger I just created do I need to drop that trigger and run the create or replace trigger statement or the create or replace statement will replace the previous trigger that I created.
Thanks !
create or replace TRIGGER Abcd.lddp_tup
BEFORE UPDATE ON lddp FOR EACH ROW
declare timenow TIMESTAMP;
begin
SELECT CURRENT_TIMESTAMP INTO timenow FROM DUAL
:new.create_sid := :old.create_sid;
:new.create_date := :old.create_date;
:new.saved_date := timenow;
:new.par_num := :old.par_num;
:new.af_id := :old.af_id;
IF
:new.locked_bemsid IS NOT NULL AND :old.locked_sid IS NULL
THEN
:new.locked_date := timenow;
ELSE
:new.locked_sid := :old.locked_sid;
:new.locked_date := :old.locked_date;
END IF;
end;
/

877410 wrote:
Hi ,
can you be more specific how that statement should be altered?can you spell PL/SQL without assistance?
CREATE OR replace TRIGGER abcd.lddp_tup
before UPDATE ON lddp
FOR each ROW
DECLARE
    timenow TIMESTAMP;
BEGIN
    timenow := current_timestamp;
    :new.create_sid := :old.create_sid;
    :new.create_date := :old.create_date;
    :new.saved_date := timenow;
    :new.par_num := :old.par_num;
    :new.af_id := :old.af_id;
    IF :new.locked_bemsid IS NOT NULL
       AND :old.locked_sid IS NULL THEN
      :new.locked_date := timenow;
    ELSE
      :new.locked_sid := :old.locked_sid;
      :new.locked_date := :old.locked_date;
    END IF;
END;
/

IDOC posted with error

Hi
working on File2 IDOC scenario..my idoc posted .. but that is red and green in SXMB_MONI... where should I check for correct the problem?

I am getting error like this :(SXMB_MONI)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me

UTL_SMTP Installation Problem, Package Created with errors

Hi Forum Friend!
I tried to Install UTL_SMTP Package in my Oracle8 Release 8.0.6.1.0. A friend of mine sent me the UtLSMTP.SQL Script and I run from SQL+ connected as SYS. When I check the Package by the Oracle Schema Manager I Notice that UTL_SMTP has errors so the package will not run successfully. The Errors are the following:
PLS-00103: Encountered the symbol "CONNECTION" when expecting one of the following:
:= . ) , @ % default character
The symbol ":=" was substituted for "CONNECTION" to continue.
I have no Idea how to handle this error. I tried to install the Package in my Developing Database But the Production Database is in HPUX(Unix). Could you please send me some recommendation to solve this issue and start executing the package!
Best Regards
Emmanuel Carrillo Trejos
P.D. LNB, Republic of Panama (Central America).

Dear Friends
Well, I think that my Database version is too old to use this package. I think that one time looking for this topic I found something relating sending email using a Host call(I think that using Mail Command from Unix) Does anybody has and Idea how to do it?. Thanks for your time colleagues!
Best Regards
Emmanuel Carrillo Trejos
LNB, Panamà.

Warning: Function created with compilation errors. ???

I created a function with a warning:
Warning: Function created with compilation errors.
I'd like to know more detailed information about this warning, how to find them?
If only with this warning, I don't know how to correct the definition of the function.
BTW, because it is a warning, I just try to run the sql stmt which will call this function:
SQL> select strdiff(ename, 'FOR') from emp;
select strdiff(ename, 'FOR') from emp
ERROR at line 1:
ORA-06575: Package or function STRDIFF is in an invalid state.
/* strdiff is the name of function */
Thanks in advance!

Hi,
I think that your posting may be more suited to the PL/SQL forum.
after the function is created with errors you should try the command:
show err
or
show errors
this should at least give you some idea of what is wrong.
regards Michael

Inbound Delivery Idoc- Create ... help required

Hi,
I'm using DELVRY01 idoc to create deliveries. when i execute using test tool, the idoc gets created with error status 51 with following errors:
Field EXIDV empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field EXIDV in segment 000042.
Field VHILM empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field VHILM in segment 000039
But these errors reflect to handling unit from segment E1EDL37 and its sub nodes which are really NOT required in my case.
Now confused if i'm using a wrong reference of creating inbound delivery. Pls shre some thoughts on it on troubleshooting this issue.

Hi Prabhu
these two fields are mandatory .. fill below details
E1EDL37-Handling unit header
EXIDV     <XXXXXXXXXXXXX>     External Handling Unit Identification
GWEIT     <LB>             Weight Unit Tare
BRGEW     <000XX>                             Total Weight of Handling Unit
VHILM     <Dummy Packing Material>     Packaging Materials
E1EDL44-IDoc: Handling Unit Item (Delivery)
VBELN     <Delivery nO>     Sales and Distribution Document Number
POSNR     <900004>     Item number of the SD document
EXIDV     <XXXXXXXXXXXXX> External Handling Unit Identification
VEMNG     <00001>     Base Quantity Packed in the Handling Unit Item
Dont forget to create Dummy packing material no...
i think above mapping helps you...
Thanks
Ramesh

Import Schema with error

When i try to import a schema from one oracle to another one (also 11g), it shows the following errors:
Job 999 has been reopened at Wednesday, 12 October, 2011 16:05
Restarting "SYS1"."999":
Processing object type SCHEMA_EXPORT/USER
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'HSS' does not exist
Failing sql is:
CREATE USER "HSS" IDENTIFIED BY VALUES 'S:EFC32883462E172BE4E973549229FAD75D854E3B6E24F44EB8830F6D09C9;F258BD7AE1E5E74B' DEFAULT TABLESPAC
E "HSS" TEMPORARY TABLESPACE "TEMP"
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
ORA-39083: Object type SYSTEM_GRANT failed to create with error:
ORA-01917: user or role 'HSS' does not exist
Failing sql is:
GRANT CREATE VIEW TO "HSS"
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
ORA-39083: Object type DEFAULT_ROLE failed to create with error:
ORA-01918: user 'HSS' does not exist
Failing sql is:
ALTER USER "HSS" DEFAULT ROLE ALL
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema HSS is needed to import this object, but is unaccessible
ORA-01435: user does not exist
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CON
TEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'ORCL', inst_scn=>'1940096');COMMIT; END;
ORA-39083: Object type TABLE:"HSS"."WKS_PROPERTY" failed to create with error:
ORA-01918: user 'HSS' does not exist
Failing sql is:
CREATE TABLE "HSS"."WKS_PROPERTY" ("ID" NUMBER(10,0) NOT NULL ENABLE, "NAME" VARCHAR2(255 BYTE) NOT NULL ENABLE, "VAL" CLOB
NOT NULL ENABLE, "ORD" NUMBER(10,0) NOT NULL ENABLE) SEGMENT CREATION DEFERRED PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING TABLESPACE "HSS" LOB ("VAL") STORE AS BASICFILE ( TABLESPACE "HSS" ENABLE STORAGE IN ROW CHUNK 8192 NOCACHE L
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/VIEW/VIEW
ORA-39083: Object type VIEW failed to create with error:
ORA-31625: Schema HSS is needed to import this object, but is unaccessible
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 6573
ORA-44001: invalid schema
Job "SYS1"."999" completed with 102 error(s) at 16:05:12
Execution errors encountered.
Job state: COMPLETED
Can anyone give me a hand?
Many thanks

thanks after i create the tablespace in destination db the import can process but it still show some error
Job 9 has been reopened at Wednesday, 12 October, 2011 17:46
Restarting "SYS1"."9":
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"HSS" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
ORA-31684: Object type SEQUENCE:"HSS"."LCM-MIGRATION_ID-SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."WKS_IDENTITY_SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."ESS_FAILOVER_RESOURCE_SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."ESS_FAILOVER_LEASE_OWNER_SEQ" already exists
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "HSS"."CSS_ROLE_LOCALES" 1.258 MB 5322 rows
. . imported "HSS"."CSS_ROLE_MEMBERS" 43.88 KB 127 rows
. . imported "HSS"."HSS_COMPONENT_FILES" 23.69 KB 13 rows
. . imported "HSS"."CSS_GROUPS" 8.476 KB 1 rows
. . imported "HSS"."CSS_IDENTITY" 6.484 KB 2 rows
. . imported "HSS"."CSS_MEMBER_TYPE" 5.468 KB 3 rows
. . imported "HSS"."CSS_PROVISIONING_INFO" 14.12 KB 18 rows
. . imported "HSS"."CSS_ROLES" 42.69 KB 174 rows
. . imported "HSS"."CSS_USERS" 10.63 KB 1 rows
. . imported "HSS"."HSS_COMPONENT" 11.07 KB 57 rows
. . imported "HSS"."HSS_COMPONENT_LINKS" 16.93 KB 134 rows
. . imported "HSS"."HSS_COMPONENT_PROPERTY_VALUES" 38.67 KB 434 rows
. . imported "HSS"."HSS_COMPONENT_TYPES" 10.01 KB 143 rows
. . imported "HSS"."PRODUCT" 8 KB 13 rows
. . imported "HSS"."QRTZ_LOCKS" 5.109 KB 5 rows
. . imported "HSS"."SMA_AUDIT_AREA_DIM" 8.015 KB 28 rows
. . imported "HSS"."SMA_CONFIG" 16.31 KB 116 rows
. . imported "HSS"."SMA_FILTER_DIM" 15.40 KB 116 rows
. . imported "HSS"."SMA_GLOBAL_CONFIG_MAP" 15.24 KB 116 rows
. . imported "HSS"."SMA_GLOBAL_SETTING" 7.664 KB 1 rows
. . imported "HSS"."SMA_TASK_DIM" 16.54 KB 116 rows
. . imported "HSS"."CES_ACL_INFO" 0 KB 0 rows
. . imported "HSS"."CES_APPS" 0 KB 0 rows
. . imported "HSS"."CES_AUTO_PROCESS_TASK" 0 KB 0 rows
. . imported "HSS"."CES_MESSAGES" 0 KB 0 rows
. . imported "HSS"."CES_PARTICIPANT" 0 KB 0 rows
. . imported "HSS"."CES_PARTICIPANT_EVENTS" 0 KB 0 rows
. . imported "HSS"."CES_PROCESS_DEF" 0 KB 0 rows
. . imported "HSS"."CES_PUSH_AUTO_PROCESS_TASK" 0 KB 0 rows
. . imported "HSS"."CES_SYSTEM" 0 KB 0 rows
. . imported "HSS"."CES_TASKS" 0 KB 0 rows
. . imported "HSS"."CES_TASKS_RESULT" 0 KB 0 rows
. . imported "HSS"."CES_USERS" 0 KB 0 rows
. . imported "HSS"."CES_WF_INSTANCES" 0 KB 0 rows
. . imported "HSS"."CSS_DELEGATED_LIST" 0 KB 0 rows
. . imported "HSS"."CSS_DELEGATED_MEMBERS" 0 KB 0 rows
. . imported "HSS"."CSS_GROUP_CACHE_DELTA" 0 KB 0 rows
. . imported "HSS"."CSS_GROUP_MEMBERS" 0 KB 0 rows
. . imported "HSS"."CSS_USER_PREFERENCES" 0 KB 0 rows
. . imported "HSS"."ESS_CLUSTER_SERVER_MAPPING" 0 KB 0 rows
. . imported "HSS"."ESS_FAILOVER_LEASE" 0 KB 0 rows
. . imported "HSS"."ESS_FAILOVER_LEASE_OWNER" 0 KB 0 rows
. . imported "HSS"."ESS_FAILOVER_RESOURCE" 0 KB 0 rows
. . imported "HSS"."HDB_SCHEDULED_TASKS" 0 KB 0 rows
. . imported "HSS"."HSS_COMPONENT_TIERS" 0 KB 0 rows
. . imported "HSS"."LCM_MIGRATION" 0 KB 0 rows
. . imported "HSS"."LCM_MIGRATION_TASK" 0 KB 0 rows
. . imported "HSS"."LCM_MIGRATION_TASK_DETAILS" 0 KB 0 rows
. . imported "HSS"."QRTZ_BLOB_TRIGGERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_CALENDARS" 0 KB 0 rows
. . imported "HSS"."QRTZ_CRON_TRIGGERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_FIRED_TRIGGERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_JOB_DETAILS" 0 KB 0 rows
. . imported "HSS"."QRTZ_JOB_LISTENERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_PAUSED_TRIGGER_GRPS" 0 KB 0 rows
. . imported "HSS"."QRTZ_SCHEDULER_STATE" 0 KB 0 rows
. . imported "HSS"."QRTZ_SIMPLE_TRIGGERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_TRIGGERS" 0 KB 0 rows
. . imported "HSS"."QRTZ_TRIGGER_LISTENERS" 0 KB 0 rows
. . imported "HSS"."SMA_APPLICATION_CONFIG_MAP" 0 KB 0 rows
. . imported "HSS"."SMA_AUDIT_ATTRIBUTE_FACT" 0 KB 0 rows
. . imported "HSS"."SMA_AUDIT_FACT" 0 KB 0 rows
. . imported "HSS"."SMA_PROJECT_CONFIG_MAP" 0 KB 0 rows
. . imported "HSS"."SMA_TEMP_LCM_IN" 0 KB 0 rows
. . imported "HSS"."SMA_TEMP_USER_IN" 0 KB 0 rows
. . imported "HSS"."WKS_GROUP" 0 KB 0 rows
. . imported "HSS"."WKS_IDENTITY" 0 KB 0 rows
. . imported "HSS"."WKS_IDENTITY_XREF" 0 KB 0 rows
. . imported "HSS"."WKS_PROPERTY" 0 KB 0 rows
. . imported "HSS"."WKS_ROLE" 0 KB 0 rows
. . imported "HSS"."WKS_SUBJECT" 0 KB 0 rows
. . imported "HSS"."WKS_USER" 0 KB 0 rows
. . imported "HSS"."WKS_VERSION" 0 KB 0 rows
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39083: Object type INDEX_STATISTICS failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'
; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'TRIGGER_NAME'; c(2) := 'TRIGGER_GROUP'; DBMS_METADATA.GET_STAT_INDNAME('HSS','QRTZ_TRIGGERS',c,2,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/VIEW/VIEW
ORA-31684: Object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-31684: Object type VIEW:"HSS"."VW_APPLICATIONS_CLUSTER" already exists
ORA-31684: Object type VIEW:"HSS"."ESS_FAILOVER_ACTIVE_NODE_VIEW" already exists
Processing object type SCHEMA_EXPORT/VIEW/COMMENT
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Job "SYS1"."9" completed with 23 error(s) at 17:46:27
Execution errors encountered.
Job state: COMPLETED

Idoc segment with 1000 char

Hi
I have a custom IDOC created with one of the segments being 1000 char. The data is populated through a custom program.
In WE02 I am unable to see all the 1000 char. Even if I export the IDOC to a spreadsheet or word doc it does not show completely all the characters.
I am able to use FM IDOC_Read_Completely to read the IDOC and view the complete segment but I am looking for a standard transaction.
Any inputs on how the I can view all the data in the segment in a standard trx ?.

hi,
the data in the edid4-sdata is filled with according to Segement field lenght.
you can directly read from table with Idoc number from table EDID4 in se16.
or we05 or we02 or we19 or BD87 transactions.
prabhudas

How to resolve create type error?

Hi all,
I am duplicating the contents of schema1 to schema2 on the same database.
So I used expdp schema1/schema1 .... exporting schema1. Then impdp schema2/schema2 remap_schema=schema1:schema2
These 2 schemas have dba privilege.
Why do I get this error:
ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
Failing sql is:
CREATE TYPE "C1DEVADM"."CMQTNQHT" OID 'AC82C504E18C6A98E044001A4B08907C' AS TABLE OF CMQTNQHF;Thanks a lot,

Hi;
I already done exporting the data :(
I guess it will be ok if I create the object types manually after impdp right?Yes.
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Impdp with error ORA-39083,ORA-00942,ORA-00959,ORA-39112,help!!!

Hi,Friends,
I did import a dump file, should be a schema by data pump.Got these errors:
ORA-39083: Object type TABLE failed to create with error
followed error:
ORA-00942: table or view does not exist
or
ORA-00959: tablespace 'USERS2' does not exist
ORA-39112: Dependent object type %s skipped, base object type %s creation failed ORA-39082: Object type created with compilation warnings
Would anybody here can help me out?Thanks!

Either pre-create the users2 tablespace in the target database, or use remap_tablespace parameter to specify the target tablespace instead of users2.
As usual, complete syntax is in the doc - http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_import.htm#sthref342

IDOC created with errors!

Similar Messages

Maybe you are looking for