Error while creating the Generic Connector for flatfile

Hi All,
I was trying to create the Generic connector for the flat file reconciliation. But i was throwed into errors. I'm using 11.1.1.3 OIM and as well as SOA also. I have been following the OIM 9 document to create the GENERIC connector.
i'm copying the error i got
<Mar 14, 2012 3:48:12 PM IST> <Warning> <XELLERATE.SERVER> <BEA-000000> <readme.txt is not a valid connector resource file.>
<Mar 14, 2012 3:48:12 PM IST> <Warning> <XELLERATE.SERVER> <BEA-000000> <readme.txt is not a valid connector resource file.>
<Mar 14, 2012 3:48:12 PM IST> <Error> <XELLERATE.WEBAPP> <BEA-000000> <Class/Method: CreateConnectorAction/imageScreen encounter some problems: >
java.lang.NullPointerException
at oracle.iam.platform.utils.OIMMessageResourcesUtil.getConnectorResourcesFromFile(OIMMessageResourcesUtil.java:964)
at oracle.iam.platform.utils.OIMMessageResourcesUtil.getConnectorResourceBundle(OIMMessageResourcesUtil.java:778)
at oracle.iam.platform.utils.OIMMessageResourcesUtil.getConnectorResources(OIMMessageResourcesUtil.java:764)
at com.thortech.xl.webclient.util.tcMessageResourcesUtil.getConnectorResources(tcMessageResourcesUtil.java:215)
at com.thortech.xl.webclient.util.tcMessageResourcesUtil.getMsgFromConnectorRes(tcMessageResourcesUtil.java:238)
at com.thortech.xl.webclient.util.tcMessageResourcesUtil.getLocalizedText(tcMessageResourcesUtil.java:66)
at com.thortech.xl.webclient.util.UIFacade.getUserDefLocalizedLabels(UIFacade.java:3024)
at com.thortech.xl.webclient.actions.CreateConnectorAction.imageScreen(CreateConnectorAction.java:1250)
at com.thortech.xl.webclient.actions.CreateConnectorAction.goNext(CreateConnectorAction.java:521)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(tcLookupDispatchAction.java:133)
at com.thortech.xl.webclient.actions.tcActionBase.execute(tcActionBase.java:894)
at com.thortech.xl.webclient.actions.tcAction.execute(tcAction.java:213)
at com.thortech.xl.webclient.actions.CreateConnectorAction.execute(CreateConnectorAction.java:135)
at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:260)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.XSSFilter.doFilter(XSSFilter.java:103)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.CSRFFilter.doFilter(CSRFFilter.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:115)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:100)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
i'm just using a flat file which contents are normal.
#GTC Trusted Source
login,firstName,lastName,eMail,organization
RDUDE,Robert,Dude,[email protected],Xellerate Users
Can somebody help where i have done wrong for this. All my deployment is in oracle linux 4.5
Thanks,
Venkatesh

Follow the doc for 11g, guide you might be missing something:
http://docs.oracle.com/cd/E17904_01/doc.1111/e14309.pdf
Highlevel configuration steps (not all and exact) are:
-> Give it Name
-> select Reconciliation
-> Select Transport Provider and format provides
-> select Trusted Source Reconciliation
->provide flat file details
-> Source reconciliation staging and mapping
->finish
regards,
GP

Similar Messages

BI : Error While Creating the Generic DS

Hi Experts,
I would like to know that while creating the generic data for Journal entry i am getting the below error. Kindly advise.
"Field FRATH with reference field WAERS: ZOXTCD0017 is to replace reference table T001".
thanks & regards,
M.S

Hi,
WAERS is refrence filed for FRATH taken from T001 .
Field FRATH is not existing in T001 .T001 is having only WAERS Field.
What you can do use create view on T001 &BKPF.BURKS key field in both the tables.So create custom view on these tables.Then u r problem will be resolved.
Regards
Ram.
Edited by: Ramakanth Deepak Gandepalli on Dec 17, 2009 12:30 PM

Error while creating the generic datasource

Hi gurus,
i am creating the generic data source by using the table KONP when i am saving the data source at RSO2 it is giving the error like
Field KBETR with reference field KONWA: reference table RV13A is replaced by ZOXTRD0145.
Then giving the error
invalid extract structure template KONP of datasource.
can anyone help me on this issue,
Thanks and regards,
Suresh.

Hi Gurus,
actually the table KONP is reffering some fields from RV13A like below
MXWRT     MXWRT     CURR     RV13A     KONWA
GKWRT     GKWRT     CURR     RV13A     KONWA
PKWRT     PKWRT     CURR     T001     WAERS
FKWRT     FKWRT     CURR     T001     WAERS
RSWRT     RSWRT     CURR     T001     WAERS
KWAEH     KWAEH     CUKY
UKBAS     UKBAS     CURR     RV13A     AWEI1
KBRUE     KBRUE     CURR     RV13A     BKONW
the issue is here RV13A is an structure not the table, so no key fields are present,
so how i can made the view for these
points will be assign to correct answer
Thanks & Regards
Suresh

Error While Creating The Generic Data Source.

Hi Gurus,
I am trying to create a Generic Data Source (ZGG_TEST) on a View (ZV_TEST1)
View as Follows:
Table1 has the Following Fields
Field Type
MANDT CLNT
RECNO NUMC
STATUS CHAR
LMODF CHAR
Table2 has Fields
Fields Type
MANDT CLNT
RECNO NUMC
PHCOS QUAN
MATNR CHAR
EQSFS QUAN
MEINS UNIT
In Table2 under Currency and Quantity Field tab
For Field PHCOS The Reference table is MSEG and Reference Field is MEINS
For Field EQSFS the Reference Table is MSEG and reference field is MEINS
View Description
Tables:
Table1
Table2
MSEG
Join condition For the View is
TABLE2-MANDT=TABLE1-MANDT
TABLE2-RECNO=TABLE1-RECNO
TABLE2-MANDT=MSEG-MANDT
TABLE2-MATNR=MSEG-MATNR
The Problem is While saving the Data Source it is Giving an Error as Follows
Invalid extract structure template ZV_TEST1 of DataSource zgg_test
Message no. R8359
Diagnosis
You tried to generate an extract structure with the template structure zgg_test. This operation failed, because the template structure quantity fields or currency fields, for example, field PHCOS refer to a different table.
Procedure
Use the template structure to create a view or DDIC structure that does not contain the inadmissible fields.
Please help me In Solving this Issue
Thanks in advance
Santosh

n Table2 under Currency and Quantity Field tab
For Field PHCOS The change Reference table to TABLE2 For Field EQSFS the change the Reference Table to TABLE2
ref field MEINS ...
This works ..
Priya
Edited by: Priya on Dec 31, 2007 1:30 PM

An error occured while creating the original attribute for message no26 296

Hi All,
I am new to DMS , we are trying to store PM documents on content server , created a storage category and while assigning files to storage category then on saving the document i get the below error :
An error occured while creating the original attribute for
Message no. 26 296
Diagnosis
An error occured while creating an original in the Knowledge Provider.
System Response
The original could not be created.
Procedure
Contact the systems administrator and check the log file (transaction Evaluate application log, object SDOK).
Please let me know what configs i am missing ...
Thanks in advance
regrds
pushpa

Hi Pushpa,
Which enhancement package are you on currently? This is observed in cases where originals in DIR's are invisible and sometimes error message 26296 occurs in transaction CV01n. Hence,please check your entries in the table SDOKPROP to avoid such a problem in your system.
Further,suggest you explore if the below resolutions can be adopted in your case.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=10321987
http://wiki.sdn.sap.com/wiki/display/PLM/OriginalsinvisibleafterEHP3or+EHP4
Regards,
Pradeepkumar haragoldavar

An error occured while creating the original attribute for

Hi All,
We encounter this error in "An error occured while creating the original attribute for " DMS very often when a user edits a file & tries to check in.
I searched the forums & realized that this is caused by the inconsistencies in the KPRO & DMS server and removing these
inconsistencies will repair this issue.
I have been deleting the inconsistencies using DMS reports DMS_KPRO_READ & DMS_KPRO_CHECK1 and it resolves the error
so the file is unlocked. But I haven't been able to figure out the ROOT cause of this issue.I couldn't find any information on the root cause of this issue. What can be done to fix this error permanently.
Regards
-Neha

Hi Neha,
Please go to transaction SE16 and enter 'SDOKPROP' as table. Then enter 'DMS*' in the field PROP_NAME and press F8. Now all DMS related entries should be displayed to you. Please compare them with the following entries displayed in the attached screenshot and maintain the missing entries.
DMS_ACTIVE_VERSION 00 Active Version
DMS_APPLICATION 00 Logical application
DMS_CHECKOUT_USER 00 Checkout User
DMS_CREATE_AUDIT 00 Generate new version of the original
DMS_DEFAULT_LANGUAGE 00 Default Language
DMS_DELETEABLE 00 PHIO deletable
DMS_DOC_KEY 02 IWB_DMS01 DMS_DOCKEY Document info record
DMS_DOC_VERSION 00 Version of relevant document
DMS_DRAW_APPNR 00 Application number from DRAW
DMS_DRAW_DTTRG 00 Data carrier from DRAW
DMS_DRAW_FILEP 00 File name from DRAW
DMS_FILE1 00 File name(firstpart)
DMS_FILE2 00 File name(secondpart)
DMS_FILE3 00 File name(thirdpart)
DMS_FILE_ID 00 GUID that points to table DMS_PHIO2FILE
DMS_FRMTXT 00 Format description, ID of additional file
DMS_MUP_CAT 00 Markup category
DMS_MUP_FLAG 00 Markup flag
DMS_ORDER 00 Sequence of additional files
DMS_STATUS 00 Document status
DMS_STATUSNR 00 Number in status protocol
DMS_STATUSNR_X 00 References to Status Log
Please pay attention that all entries are typed well and that there are no spelling errors. If all these values are maintained correctly in table SDOKPROP the dump and the error message should no longer appear.
For further information you can also see the corresponding SDN WIKI page under
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/plm/error26296in+CV01N
Regards,
Ravindra

Getting error while creating the variable of Schema Element type

Hi everybody,
For creating a variable of schema element type I am doing the following steps...
Select 'Variables' after right clicking on bpel process. IN this window, go to 'Create VAriable' then select 'Element' type. Now in Type Choose, I expanded the my imported schema files. And selected a element type, then click ok to create this variable... I am getting the message...
IN ORDER TO SAVE IMPORTED WSDL/SCHEMA FILES, YOU MUST HAVE A PARTNER LINK LOCATED UNDER THE CURRENT PROJECT DIRECTORY.
What is mean by that.
I have imported the schema files in project. AFter that I have imported them into the WSDL also. Now why I am getting error while creating the variable. However I can create variable directly in .BPEL file then everything is fine. And it is working also. But what is mean with the above error? Why I am not able to create variable through GUI?
Thanks.

Hi,
I have this same problem this morning, and I was going crazy, until I found this webpage on the internet:
[http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process|http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process]
The idea is that the jdeveloper is not very good working with directories with spaces on the directory name. If you move all your work to a directory without spaces, it will work smoothly. At least, it had worked for me.
Regards,
Nacho

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

Error while creating the structure

hello friends,
i have two doubts
1)
i am getting the error while creating the structure in se11.
well i am creating the structure in the following way
in component i am giving the values as bom and in component type i am giving the value as meins.
i am getting the status warning message as the below
'field name does not agree with the proposed name base_bom for bapi table'
2)
and more over can we create the structure as the follwing in se11.
component = f1 and
component type = tablename-fieldname
when i am doing in the second way i am getting the error as the following table is not active though the table is active

hi guru,
just component name as --- your field name.
where as component type as give just data element k.
no need to give tablenme-fieldname k.
component component type .
f1 matnr----
data element
thanks anji.
Moderator message: please do not use SMS speak, what does that "k" mean, short for "OK"? please get your act together, these are professional forums.
Edited by: Thomas Zloch on Nov 15, 2010 9:10 AM

Error while creating the 'LOV' type parameter in Siebel 8.1.1.5

Hi,
One of my Customer is facing the below error while creatting the parameter of type 'LOV' in Parameter applet in Siebel 8.1.1.5
Runtime Error!
Program: C:\Program Files\Internet Explorer\iexplorer.exe
This application has requested the Runtime to terminate it in an usual way. Please contact the application’s support team for more information
Could some please let me know what would be the reason for this issue?
Thanks in advance for your help.
Thanks,
Ravi

Please close this thread...it appears that the error occurs when the report involves a big set of records. I tried trying to filter only one record and was able to produce the pdf

Getting error while creating the Shopping cart.

Hi ,
I am getting error while creating the Shopping cart.
a.Error in account assignment for item 1 (Item Testing SC )
b.Duplicates of Cost Centre T10063 are defined in SRM (Item Testing SC )
Kindly provide the solutions.
Thanks,
Dev

Try the following in the ERP backend system:
Standard Hierarchy Inconsistencies
Issue: one Cost Center is repeating in more than one node in Cost Center Standard Hierarchy.
Update from SAP Global support, the following was the email received:
in transaction KSH3 please run both the ambiguity and completeness check(Menu -> Extras -> Check and Help functions).
If you think that your standard hierarchy is inconsistent you can check that as following:
Run transaction Extras -> Hierarchy - Master data -> Test. The result shows you if there are in consistencies. If that is the case run also Extras -> Hierarchy - Master data -> Comparison.
Alternatively, you can run the report 'RKCORRH1' (TN SE38).
Run both the Hierarchy->Master data->test and the
Hierarchy->Master data->comparison.
As stated above inconsistency message showed after Test. Run the comparison and you get a similar message.
Once the above two are run, again when you go to test, the inconsistency disappears.

Error while creating the document

Hi Experts,
When i create the document in CV01N transaction and while i try to check in the document in "DMS_C1_ST" i am getting the error message as * An error occured while creating the original attribute for PDF*.
Kindly let me know how to resolve this issue.
Regards,
Bhanu

Hi Bhnau,
could you please check the following link and made sure that the mentioned entries in table SDOKPROP are maintained correctly in your system.
http://wiki.sdn.sap.com/wiki/display/PLM/Error26296in+CV01N
Best regards,
Christoph

Error while creating the product group by MC84

Hello Friends,
I am creating the product group by MC84, and in product group field i have given the product group name i.e P2345, and its description i.e product group for waluj, plant i.e cw01 and Base unit i.e KG.Now when i press enter system is throwing the error"The field is defined as the required field;it doesnot contain an entry."Message no.MG144.And with this error system is placing the cursor on product group field.As i have already given product group name than also system is throwing the error.
Though i know the alternative method to create product group by MMO1 and selecting the material type PROD, then also i want to know why system is throwing the error while creating the product group by MC84.
Please guide.

Dear,
This message says that you have not entered a mandatory field.Enter proper values for all mandatory fields and then you will not get this error.
Try to create the product group as material of material type"PROD"
Then you go on adding the memebers in SOP Transaction.
In some of the versions of SAP it is the problem.
I have also faced this problem in some versions.
Regards,
R.Brahmankar

Serial number error while creating the production order

Hello frds,
I am getting the following error while creating the production order.
"Item 000000 requires exactly 100 serial numbers for the asset".
If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
I have tried using the new serial number profile also, but it is giving same error.
Kindly guide.
Regards,
Narendra Bora

Dear Narendra
Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
Procd Procedure description Ser.Usage
PPRL PP order release 02
since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
Regards
Soundar

Datamover error while creating the peopletools system database

i am using
os=suse linux 12.2
database = db2 9.72
peopletools = 8.53
i am getting the following error while running the datamover script for the peopletools system databse. i have attached the following error for your view plz help me........
db2inst1@linux2:~/PT853/bin> ./psdmtx -CT DB2UNIX -CD SL290101 -FP /home/db2inst1/PT853/scripts/sl290101dbx.dms
PeopleTools 8.53 - Data Mover
Copyright (c) 2013 PeopleSoft, Inc.
All Rights Reserved
Started: Tue Feb 26 13:12:25 2013
Data Mover Release: 8.53
Database: SL290101 (ENG)
Input file: /home/db2inst1/PT853/data/ptengs.db (ENG)
Commit done at end of record
Importing ACCESS_GRP_LANG
Import ACCESS_GRP_LANG 0
SQL Error. Error Position: 0 Return: -2300 - End of fetch (SQLSTATE PS001)
RUN STATISTICS FOR TABLE (PS_ACCESS_GRP_LANG,LOW)
Error: SQL execute error for %UpdateStats(PS_ACCESS_GRP_LANG)
Error: Import Record name ACCESS_GRP_LANG
Ended: Tue Feb 26 13:12:30 2013
Unsuccessful completion

thanks for reply anygma,
datamover script created the PS_ACCESS_GRP_LANG table in an back end so i think no need to create that record in an application designer....
And also i edit that datamover script as set start after ACCESS_GRP_LANG now its again return the same error for the next table but in back end the table are created.......
db2inst1@linux2:~/PT853/bin> ./psdmtx -CT DB2UNIX -CD SL290101 -FP /home/db2inst1/PT853/scripts/sl290101dbx.dms
PeopleTools 8.53 - Data Mover
Copyright (c) 2013 PeopleSoft, Inc.
All Rights Reserved
Started: Wed Feb 27 03:17:03 2013
Data Mover Release: 8.53
Database: SL290101 (ENG)
Input file: /home/db2inst1/PT853/data/ptengs.db (ENG)
Commit done at end of record
Searching ACCESS_GRP_LANG ... please wait
Found ACCESS_GRP_TBL
Restart record ACCESS_GRP_TBL
Importing ACCESS_GRP_TBL
Creating Table ACCESS_GRP_TBL
Import ACCESS_GRP_TBL 58
Building required indexes for ACCESS_GRP_TBL
SQL Error. Error Position: 0 Return: -2300 - A table or view could not be found (SQLSTATE PS601)
RUN STATISTICS FOR TABLE (PS_ACCESS_GRP_TBL,LOW)
Error: SQL execute error for %UpdateStats(PS_ACCESS_GRP_TBL)
Error: Import Record name ACCESS_GRP_TBL
SQL Spaces: 0 Tables: 1 Triggers: 0 Indexes: 1 Views: 0
Ended: Wed Feb 27 03:17:14 2013
Unsuccessful completion

Error while creating the Generic Connector for flatfile

Similar Messages

Maybe you are looking for