Problem in importing idoc metadata

Hi all,
i have problem in loading metadata in idx2. idoc details are AFS/ORDERS05/ZADIORDCONF port: SAPAGS client 003 . i could see an idoc metadata with name ORDERS05 under the corresponding sap system (SAPAGS with client 003) but with out any extension.
now i tried to create another with idoc type : ORDERS05
Extension: ZADIORDCONF
and Source port:SAPAGS
it is giving error msg Extension ZADIORDCONF is not assigned to basic type OREDERS05.
wat could be the reason , please help to solve it
Thanks and Regards
Jhansi

Hi,
There is no need to add anything to idx2. You could delete the existing metadata from idx2 and reimport it.
In some cases even this would not work. In that case, you could refresh the entire metadata by running report IDX_RESET_METADATA. However, use this report only if the above option does not work, since this report will reset your entire metadata.
Thanks,
Bhavish
Reward points if comments helpful

Similar Messages

Problem in import of MetaData file in Oracle Warehouse Builder 9.2

My Problem is Related to Oracle WareHouse Builder.My system's configuration is following :-
Machine : P4
Operating System :Windows XP
ORacle : Version 9.2
Oracle WareHouse Builder 9.2
Ram :1GB
SGA Size :Approximately 650M
I have 2 MetaData files which I have to import into OWB.
First file's size is 9M.It got imported properly in 4 minutes without any error.
2nd File's Size is 30M.when
I start importing this MEtaData file.It goes upto 35% in Progress Bar.But after that it does not show any improvement.
I have left the machine running with this option upto 24 hours.
But nothing happened .It still shows only 35%.
I have checked log file/Trace file/Alert log files ,but there is no error in these files.
If any body have any solution about it,Please reply ASAP.I am stucked in this problem from last 7-8 days.
Waiting for reply
Thanks & Regards
Harvinder Singh

Thanks for your reply Igor.
As posted the OWB 10.1.0 software is running against a 9.2.0.8.0. database, so OWB still uses DBMS_JOB instead of DBMS_SCHEDULER in this database. In addition I already tested scheduling a simple job to run an OS command as suggested in note 365539.1 , and job scheduling is working fine.
There are no invalid objects in this database.
Yasmin

Problem With Uploading IDOC Metadata using IDX2

Hi Experts,
While i am uploading IDoc metadata using IDX2 it is showing
"I::000" information.
Anybody please help me why i am getting this problem?

Hi Bhuvan,
Basicall this problem arises when user Id being used in the SM59 to trigger the IDoc's from the R3 system , i,e , the XI user id being used in SM59 of R3 does not have the authorizations to post the Idoc.
Note : 837595 describes the authorizations needed to post and Idoc. Make sure that the user id has the authorizations in this note.
Activate the authorization check in transaction ST01.
And also it may be due to insufficient roles for the user which ur using in RFC connection to SAP system.
Check with the port in IDX1 whether u have configured corectly.
Check this link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
PAGE - 11
Regards,
Vinod.

Unable to import IDOC metadata from 4.6C based R/3 system

As part of a project we are trying to import IDOC interface definition into XI3.0 from our 4.6C based R/3 System. I have gone through the pre-requisites mentioned at
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
One of the OSS notes 672745 in the above pre-requisites talks about applying basis component patch SAPKB46C46. Our current R/3 System is on the basis patch SAPKB46C39. Is there a way to import just the required function modules without applying the whole patch so that we can
continue with the projet ?
cheers.
Ramesh Babu

There is no SM59 RFC destination involved.
Go to SM59 of the XI box and check, the R/3 system for which XI is having RFC destinations.
And before importing, hope you have given R/3 system IP address, client , user id and Password correctly in the Software componenet version.
Is there a workaround for this?. I remember reading in this forum, that there are other ways of importing IDOC message and interface objects as XSD files directly instead of using import wizard.
>> For this you need to download the Idoc Schema from the R/3 system and then import this schema in the External Definition as a xsd type.
But you need to connect to R/3 system and import the Idoc, Because in the directory, you are going to use Idoc itself as an Message Interface. So the xsd used for changing the occurence of the Idoc type, so that you can post mulitiple idocs.
Hope this helps,
Regards,
Moorthy

Problem in importing idoc

Hi Friends,
Im using XI 7.0 , While importing an idoc into a SWCV from connected R3 system i get the following error :
" Problem to reach R3 system "
Detailed error message says " Attempt to import the application component hierarchy failed " CAN_NOT_BUILD_AKH.
I checked that IDX1, rfc destinations etc . are all ok
Message server details were also correct.
Can you help.
regards
Prasenjit

Hi,
Make sure your user id has the proper authorizations as described in the following article on the XI/R3 boxes (if they are separate)
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
Thanks.

Problem in importing idoc? help needed

Hi all,
I am trying the file-xi- idoc scenario.I have created logical system,port,pprofile, rfc destination( using XIAPPLUSER id and password) in respective
sap system.
In sap xi side, using transaction idx1, created rfc destination to sap system and created a port.
In i.repository, when i tried to import the idoc type, i am getting the error like 'unable to establish connection to R/3 system'. I have defined the receiver sap system in SLD asboth technical and as well as business sytem.
Any help???
Rgds,
SR.

Hello SR,
There could be various reasons ... one of them could be your definition in the Integration Repository. Check if you have given correct server address & Group name etc on the screen where you create NameSpace. Also check that the user has sufficient authorization in the SAP system from where you are importing the IDoc schema.
Let me know how it goes.
Regards,
Homiar.

Problem in importing idoc structure into repository

Hi experts,
I am trying to import an IDOC structure (ORDRSP.ORDERS03) from an R/3 system into the repository. But I am getting the following error:
" **Ready for import**
Import started...
ORDRSP.ORDERS03:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: IDoc Type ORDERS03 | urn:sap-com:document:sap:idoc:messages is already locked in another change list by user rajash
Import failed with 1 error
If i still continue, i see the idoc imported in the left hand pane, but when i double click it, i don't see the structure of the IDOC in the right hand pane.
Also, when i press the XSD/WSDL tabs, i get this message:
"Object IDoc Type ORDERS03 | urn:sap-com:document:sap:idoc:messages not found".
Can somebody guide me how to get around this issue?
Thanks and regards,
Ravi Kanth Talagana

Hi Ravi,
Go to user rajash 's change list and activate it. Also ask him to release the IDOC.
cheers,
Prashanth
P.S Please mark helpful answers

Refresh Idoc Metadata in PI 7.31 Java Only

Hello experts,
We are facing issue to refresh the Idoc metadata every time when we change Idoc structure in ECC for Idoc outbound scenario.
We have imported the latest Idoc structure in ESR and assigned that to MM,OM and IFolw. Still in message monitoring we can see the old Idoc structure.
Is there anywhere else to import Idoc metadata like it used to be in Dual Stack idx2 ??
Regards,
Suman

Hi Suman,
If you are new with Idoc in PI you try with the sap.help documentation: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
Regards

Error when importing IDOC structure from SAP - Control record missing

Hi!
We are hitting problems when importing IDOCs from SAP into the Integration Builder. The import ends successfully but when we drill into the IDOC structure we get a message: Schema for type EDI_DC40.ASN_OUT.DELVRY01.Z1DELVRY (category Data Type) not found. This is only happening for one specific IDOC type only. We have checked all we can think of but cannot get this to work. Any help would be very much appreciated. Of course, points awarded for any good ideas. Thx, Duncan

Hi Duncan,
Taka a look at these threads which address similar issues:
Error during import of FIPARQ01 Idoc
Error during IDoc Import
Importing idocs:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/78/21753251ce11d189570000e829fbbd/content.htm
Hope these help!.
Cheers,
Chandra
Message was edited by: chandravadhana gopalakrishnan

Idoc metadata

hi
why should we import idoc metadata while using idoc adapter and what do we mean by metadata.even in mapping idoc structure why we assign segment and begin to constant values and disable cntrol record field.
regards
raghu

Hi Raghu,
What is Metadata:
IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types .This metadata is just a description of available structures
and fields.Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.Thus it can be loaded in two ways:
1. During the runtime
2. Before the actual message flow.
To find out what metadata has already been loaded, call the transaction Metadata Overview for IDoc Adapter (IDX2).The system displays a screen with the directory of all systems connected with the IDoc adapter (including a description) for which metadata has already been loaded. Choose Port Maintenance in IDoc Adapter () to call the corresponding transaction and to create additional ports.
Why to Import:
To process an IDocs in the form of an IDOCXML
message, an IDocs metadata must be loaded into
the Integration Server so that SAP XIs IDoc adapter can
change the native IDoc format into the XML representation.
All IDocs are created according to specific rules: This is the general structure (the record types) of every IDoc. Special rules affect the different IDoc types.
Segment:
Segment is like a container which strores all administration information for technical processing, as well as the actual application data.of an IDOC.
Fields :
A segment comprises segment fields as the smallest unit of the Idoc which contains the actual values and information.
control record :
The control record is identical for all IDocs and contains the administration information, for example, sender, recipient and message. Note that the control record also contains the last processing status ( STATUS field).
If you disable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the system information not from the payload as:
1. From XI sender service, configuration in Integration Directory, System Landscape Directory
2. Constant LS
3 . From XI receiver service, configuration in Integration Directory, System Landscape Directory
If you enable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the IDoc-XML payload.
**Pls: Reward points if helpful **
Regards,
Jyoti

Problem with import of IDOC fromSAP 3.1i to PI 7.0

Hi ,
I have an IDOC as ZXYZ.ORDERS01 in SAP R/3 3.1i System, I am unable to import the IDOC in PI7.0
Let me know the process to import that idoc.
( I am Doing IDOC to File and file to IDOC Scenario )
Regards,
Edited by: TomShey on Sep 22, 2010 6:27 PM

Hi,
We also had same problem of unable to import IDOC structures automatically from SAP 3.1I to XI/PI, as the support of this feature as mentioned by SAP starts from version >= 4.0.
Please find the prerequisite as mentioned in help.sap.com
Prerequisites
The SAP system from which you want to import the RFCs or IDocs must contain function modules for calling metadata. You can import RFCs and IDocs from SAP Release 4.0 and higher. The table below gives an overview of the required support packages:
(http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm)
So as per my experience, I could identify three options after indepth investigation.
1. Recreate the IDOC structures in another SAP system which is of latest version >= 4.0 may be IDES, and then import the structure in IR for further developments. This is the option we are using for our developments now.
2. Get WSDL of the IDOC structure by creating manually the structure using XML Enterprise edition using the complete syntax or xpath and import as external definitions and use it in mapping.
3. Re-create the IDOC structure in XI system itself and try to use it.
Let me know if this helped you.
Regards,
Bindu

Problem importing idoc to XI integration repository

I have deleoped a custom IDOC and released in SAP/R3. Next I have imported it to XI using transaction IDX2 without problems.
However, when I try to import the metadata to the integration repository, I can't find it in the list of available IDOcs. I have tried to refresh the catches, and even restartet the XI server, but i doesn't help.
Any suggestions ?

Hi Henrik,
See if these threads help :
importing IDOC in XI for interface mapping
IDOC in IDX2 is not visible in while importing into XI Design Component.
Settings in XI side to receive IDOC from application server
Check this link to know minimum authorizations required for a user to import RFC/Idocs.
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm

IDX2 Idoc metadata import error

Hi
When i tried to import the Metadata in IDX2, the metadata is updating, it s populating old and new fields
As i deleted the one field in IDoc but when i imported the metadata in IDX2 the deleted field is also populating.
I tried couple of times by deleting and reimporting the metadata,
any ideas why its populating old values
Thanks

Hi
There may be any program error if the structure doesn't come up properly [SAP Note 565083|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d353635303833%7d]
Please see more details at help link , you may get a complete idea and solve your issue.
http://help.sap.com/saphelp_nw04/helpdata/EN/8a/b8b13bb3ace769e10000000a11402f/frameset.htm
Regards,
Srinivas

Getting problem in import the repository metadata into to OWB ( Sun solris)

HI ,
Actually as discussed before in this forum I am trying to import all metadata of repository ( exported as mdl file from window environment) into unix(sun solaris environment). After completion like 100% its giving a error.
I am trying this from my local m/c have client of owb ,which is conneted with owb of sun solaris environment .
error report is shown here.
Import started at Apr 1, 2009 4:36:58 PM
Project "HDFC_ODS_DEV"
Configuration "DEFAULT_CONFIGURATION"
Location Specific Configuration "DEFAULT_DEPLOYMENT"
Calendar Module "ODS_SCHEDULES"
Calendar "WONDERS_SCHEDULE"
Oracle "HDFC_ODS_SOURCE"
Warning: MDL3002: Location <PUBLIC_PROJECT.ODS_SOURCE_LOC> not found for LOCATIONUSAGE <HDFC_ODS_DEV.HDFC_ODS_SOURCE.ODS_SOURCE_LOC>
Map "M_STG_P2_M_CMP_CHNL_SRC_V_1"
Map "M_STG_P2_M_CMP_COMM_MODE_V_1"
Map "M_STG_P2_M_CMP_COM_MOD_PRC_V_1"
Map "M_STG_P2_M_CMP_CUST_CHNL_V_1"
Map "M_STG_P2_M_CMP_CUS_CNL_PRC_V_1"
Map "M_STG_P2_M_CMP_FRM_V_1"
Map "M_STG_P2_M_CMP_FUNCT_AREAS_V_1"
Map "M_STG_P2_M_CMP_FUN_ARS_PRC_V_1"
Map "M_STG_P2_M_CMP_ISSUES_V_1"
Map "M_STG_P2_M_CMP_REP_TPS_PRC_V_1"
Map "M_STG_P2_M_CMP_RESP_TYPES_V_1"
Map "M_STG_P2_M_CMP_RET_SLS_REG_V_1"
Map "M_STG_P2_M_CMP_SRC_PRC_V_1"
Map "M_STG_P2_M_CMP_SRC_SEARCH_V_1"
Map "M_STG_P2_M_CMP_SRC_V_1"
Map "M_STG_P2_M_CMP_SUB_ISSUES_V_1"
Map "M_STG_P2_M_COUNTRIES_V_1"
Map "M_STG_P2_M_PAYMENT_MODE_V_1"
Map "M_STG_P2_M_REIN_NMS_V_1"
Map "M_STG_P2_M_REV_ELAPSED_RSN_V_1"
Map "M_STG_P2_M_REV_EVAL_DCSNS_V_1"
Map "M_STG_P2_M_REV_EVL_DNS_STP_V_1"
Map "M_STG_P2_M_RLTNS_V_1"
Map "M_STG_P2_REVIVALS_V_1"
Map "M_STG_P2_REV_CED_OPN_V_1"
Map "M_STG_P2_REV_DCMNTS_KEPT_V_1"
Map "M_STG_P2_REV_DCMNTS_V_1"
Map "M_STG_P2_REV_DSCN_HIST_V_1"
Map "M_STG_P2_REV_EXCPTNS_V_1"
Map "M_STG_P2_REV_KEPT_V_1"
Map "M_STG_P2_REV_MLSTN_HIST_V_1"
Map "M_STG_P2_REV_REQ_TYPES_V_1"
Map "M_STG_P2_REV_SERV_V_1"
Map "M_STG_P2_REV_STATUS_HIST_V_1"
Map "M_STG_P2_REV_UW_V_1"
Map "M_STG_PLCY_SERV_V_1"
Map "M_STG_PLCY_STATUS_HIST_V_1"
Map "M_STG_PROC_INDEX_V_1"
Map "M_STG_PROPOSALS1_V_1"
Map "M_STG_PROPOSALS_V_1"
Map "M_STG_PRPSL_ALTS_V_1"
Map "M_STG_PRPSL_ALT_CTGRYS_V_1"
Map "M_STG_PRPSL_CLIENTS_KEPT_V_1"
Map "M_STG_PRPSL_KEPT_V_1"
Map "M_STG_PRPSL_STATUS_HIST_V_1"
Map "M_STG_SALFLDGHSL_UPDATE_V_1"
Map "M_STG_SALFLDGHSL_V_1"
Map "M_STG_SSRFACC_V_1"
Map "M_STG_SSRFADD_V_1"
Map "M_STG_SSRFANV_V_1"
Map "M_STG_SSRFBKA_V_1"
Map "M_STG_SSRFCNV_V_1"
Map "M_STG_SSRFCVD_V_1"
Map "M_STG_SSRFMSC_V_1"
Map "M_STG_UW_COMMENTS_V_1"
Data Profile "DP1"
Data Rule Folder "DERIVED_DATA_RULES"
Process Flow Module "HDFC_ODS_PROCESS"
Warning: MDL3002: Location <PUBLIC_PROJECT.HDFC_ODS_PROCESS_LOC> not found for LOCATIONUSAGE <HDFC_ODS_DEV.HDFC_ODS_PROCESS.HDFC_ODS_PROCESS_LOC>
Warning: MDL3002: Location <PUBLIC_PROJECT.HDFC_ODS_PROCESS_LOC> not found for LOCATIONUSAGE <HDFC_ODS_DEV.HDFC_ODS_PROCESS.HDFC_ODS_PROCESS_LOC_M>
Process Flow Package "LASIA"
Process Flow "CLAIM_ACTYMEMO"
Process Flow "POLICY_AMOUNT_DD_M1_TRAC"
Process Flow "P_LIFE_ASIA_TEMP"
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P57_AGNTCONTBENECOMMDTL> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P57_AGNTCONTBENECOMMDTL>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P62_COVERAGE> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P62_COVERAGE>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P52_ACTIVITYRELATRIONSHIP> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P52_ACTIVITYRELATRIONSHIP>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P38_EXTERNALUNIT> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P38_EXTERNALUNIT>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P65_LIFE_DETAILS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P65_LIFE_DETAILS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P58_AMTDTLRTRN> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P58_AMTDTLRTRN>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P40_INDIVIDUAL> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P40_INDIVIDUAL>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P61_AGENT_DETAILS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P61_AGENT_DETAILS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P43_ENTENTCLASSASSOC> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P43_ENTENTCLASSASSOC>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P39_ORGANIZATHIST> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P39_ORGANIZATHIST>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P54_ENTITYADDHIST> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P54_ENTITYADDHIST>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P47_ACTVITYMISS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P47_ACTVITYMISS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P49_RECEPTBALDD> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P49_RECEPTBALDD>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P41_HELTHPROREQFEE> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P41_HELTHPROREQFEE>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P26_CONTRACTMISS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P26_CONTRACTMISS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P55_ADDCHANEL> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P55_ADDCHANEL>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P42_ENTITYCERTHIST> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P42_ENTITYCERTHIST>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P66_OTHERS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P66_OTHERS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P46_AGNTDMOGRPHIC> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P46_AGNTDMOGRPHIC>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P44_ENTITYBANKDETLS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P44_ENTITYBANKDETLS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P59_ENT_ENT_REL_HIST> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P59_ENT_ENT_REL_HIST>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P29_POLICYAMOUNTDD> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P29_POLICYAMOUNTDD>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P58_AMTDTLOT> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P58_AMTDTLOT>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P37_EXTERNALIDENTHIST> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P37_EXTERNALIDENTHIST>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P36_ENTITYMISS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P36_ENTITYMISS>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P56_BENEFIT> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P56_BENEFIT>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P60_CLIENT> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P60_CLIENT>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P58_AMTDTLLE> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P58_AMTDTLLE>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P45_ENTYBALDD> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P45_ENTYBALDD>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P48_ACTIVITYENTITY> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P48_ACTIVITYENTITY>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P51_CONTRACTACTIVITY> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P51_CONTRACTACTIVITY>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P58_AMTDTLLA> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P58_AMTDTLLA>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P50_FINANCIALACTIVITY> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P50_FINANCIALACTIVITY>
Warning: MDL3002: CopyOf <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LIFE.P53_ADDCHNLMISS> not found for SUBPROCESS <HDFC_ODS_DEV.HDFC_ODS_PROCESS.LASIA.P_LIFE_ASIA_TEMP.P53_ADDCHNLMISS>
Process Flow Package "LIFE"
Process Flow "P10_CLAIM"
Process Flow "P11_PROPOSAL"
Process Flow "P12_TELPHADDRESS"
Process Flow "P13_ELECTADDRESS"
Process Flow "P14_DEMOGRAPHIC"
Process Flow "P15_CHILD"
Process Flow "P16_BENEFIT"
Process Flow "P17_CONTRACTENTITY"
Process Flow "P18_PROPOSALENTITY"
Process Flow "P19_CONTINSURENTITY"
Process Flow "P1_DESC"
Process Flow "P20_PROPINSUREDENTITY"
Process Flow "P21_CONTREINENTITY"
Process Flow "P22_PROPCONTBENE"
Process Flow "P23_ENTITYCLAIM"
Process Flow "P24_CLAIMCOVERAGE"
Process Flow "P25_CLAIMMISS"
Process Flow "P26_CONTRACTMISS"
Process Flow "P27_CONTRACTSTATHIST"
Process Flow "P28_CONTRACTCURRENCY"
Process Flow "P29_POLICYAMOUNTDD"
Process Flow "P2_DESC"
Process Flow "P30_INSURACECONTRACT"
Process Flow "P31_INSURANCECONTHIST"
Process Flow "P32_PRPOSALMISS"
Process Flow "P33_PROPOSALSTSTHIST"
Process Flow "P34_PROPOSALAMTDD"
Error occurred importing from file "C:\Documents and Settings\sreelals\Desktop\186 HDFC ODS DATABASE DOC\owb_metadat-186\HDFC_ODS_DEV-20090115_1634.mdl".
oracle.wh.util.Assert: Repository Connection Error: The connection to the repository was lost, because of the following database error: Closed Connection Exit OWB without committing.
 at oracle.wh.util.Assert.owbAssert(Assert.java:51)
 at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:186)
 at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:156)
 at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:152)
 at oracle.wh.util.SQLExceptionHandler.handle(SQLExceptionHandler.java:65)
 at oracle.wh.repos.pdl.foundation.CacheMediator.abort(CacheMediator.java:2179)
 at oracle.wh.repos.pdl.transaction.TransactionManager.abortGlobalTransaction(TransactionManager.java:328)
 at oracle.wh.repos.pdl.transaction.TransactionManager.abort(TransactionManager.java:471)
 at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1916)
 at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
 at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
 at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.internalRunImport(MDLUpgradeImportTransaction.java:218)
 at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.run(MDLUpgradeImportTransaction.java:319)
-- Can any one help me out on this.
why this error is coming and how to resolve it ?
Dba also not able to understand.
@waiting for best and helpful reply from all of you owb gurus...
Regards
Umesh

Boss ,
I tried 2-3 times still getting same error.
what should check now and do now ?
help me out .
Please reply asap.
--Umesh

Problem in Import of RFC and IDoc interfaces

hi,
i am a beginner in XI. now am following the link given below.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Topic: A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
i don't know how to Import S/W Component and IDoc structure.
my doubt is what should i select from the populated list.
plz help me.
thanks in advance

hi,
Please follow below steps assuming that the Software component is properly created in SLD.
1. open Integration Repository (IR)
2. Goto ---> Tools -
> Trasfer SWCV from SLD
3. Select the Software Component from the pop-up list
4. Press Import
5. It will import the software component in IR
6. Save it and activate.
7. If its for SAP system then give RFC details in SWC
8. Create Namespace in it and save and activate
http://help.sap.com/saphelp_nw04/helpdata/en/9c/7a973ca83a4601e10000000a114084/content.htm
Now it will be ready for further Development.
For importing an idoc structure...
go to imported objects and right click there and select import iDOCs and there give your application system details.This is the way to import your IDOc structure.
Thanks,
Vijaya.

Problem in importing idoc metadata

Similar Messages

Maybe you are looking for