Loading flat idoc via report RSEINB00 into integration server fails

Hi,
we have PI/700.
We get idocs (in flat format NOT XML) via filesystem from an external partner.
Now I try to load these idocs with the report RSEINB00 into my integration server.
My problem is, that the report says that the sender port + client(of the idoc control segment) is not a service in the integration directory.
E.g.: SAPWR3 and client 550 (this WR3 is the system + client of the external partner who exports the idocs to filesystem).
For testing I changed the idoc control segment and inserted an existing business system + a correct client (of our SAP-System) instead of the SAP-port used by the external partner.
--> It worked!!!
Do I have to enter the SAP-System of the external partner in my SLD?
If yes - as a SAP-System (including client,...) or a third party system or...?
Any ideas?
Thanks for your help!
Regards
Wolfgang

HI,
Regd. Party config etc , you can refer this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
More -
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
When I enter the sender-system of the external idocs into my SLD, do I have do insert it as a third party system or a SAP System?
>>SAP system.
Hope this helps,
Regards,
Moorthy

Similar Messages

Flat-Idocs via the IDOC-adapter

Hi All,
I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
I am looking in to the principle of tunneling, but that will involve some ABAP coding.
Cheers,
Frank

Hi Bhavesh,
I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
test if idoc is in tunnel-payload-format
 l_content_type = l_payload->getcontenttype( ).
 IF l_content_type = if_xms_resource=>mimetype_idoc.
 l_idoc_resource ?= l_payload->getdata( ).
 l_tunnel_flag = 'X'.
 ELSE.
and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
Cheers,
Frank

Upload Flat-IDocs via WE16 fails - where is log-file for this upload

Hi,
we are using ERP2005 and we wanna upload large Flat-IDocs (exported by a customer, > 100MB) via WE16.
Now we are getting the error "...error in converting while reading file ..." (a translation of the german error message
Is there a log file for this upload process?
regards
Wolfgang Hummel

The following Oracle Forms objects did not generate successfully: gl forms/ZHS GLXJEENT.fmxadpatch log will tell you worker which was processing this fmb.....mark that worker number.....in same directory find ad*worker_num*.log and see that log file.
You can find adworker,adpatch,adworker log at:-
Application Tier-- adpatch log - $APPL_TOP/admin/<SID>/log/
Thanks,
JD

Problem while deploying ear into integration server of JCAPS 5.1.1

hi all,
when i'm trying to deployinag an ear file into JCAPS 5.1.1 integration server i'm getting the follwing error and i am not able to deploy the project.
javax.servlet.ServletException: Cannot find message resources under key org.apache.struts.action.MESSAGE
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:872)
org.apache.jasper.runtime.PageContextImpl.access$1100(PageContextImpl.java:114)
org.apache.jasper.runtime.PageContextImpl$12.run(PageContextImpl.java:792)
java.security.AccessController.doPrivileged(Native Method)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:790)
SeeBeyondISDeployer.pages.ManageApplications_jsp._jspService(ManageApplications_jsp.java:1155)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:141)
javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:318)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
java.security.AccessController.doPrivileged(Native Method)
edu.yale.its.tp.cas.client.filter.CASFilter.doFilter(CASFilter.java:635)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:318)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:261)
root cause
can any body help me out to resolve this problem.
Thanks In Advance

First check is Java stack is running ?
make sure J2EE_ADMIN user not locked.
Ans please check password in secure area. check password in secure store should be correct.
may be you can try with restart of SAP and DB.
All the best
regards
nag

IDOCs are queued up In Integration Server

Folks ,
I am not able to process the iDOCS as they are choked up in Integration server with following trace , can anybody help me out
 <?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>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:TimeSent>2006-04-19T18:43:47Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>BS_STG_R3_902_NA</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>B4ydE1e/NPq9tEnsDcj7vA==</SAP:ObjectId>
<SAP:SWCV>U0Q4sKe1Edqe7daFZAcBUQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <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="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>44452091-7B42-40B7-E100-000064070151</SAP:MessageId>
<SAP:Info>FIDCC2.0000000018113400:20060419144347</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS">is.61.sun081</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
- <SAP:Branch>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
</SAP:Branch>
- <SAP:Branch>
<SAP:MessageId>4445B42B-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_R1D_201_IE</SAP:Service>
</SAP:Branch>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>902</SAP:MANDT>
<SAP:DOCREL>31I</SAP:DOCREL>
<SAP:DOCNUM>0000000018113400</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>FIDCCP01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>FIDCC2</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPST4</SAP:SNDPOR>
<SAP:SNDPRN>ST4-902</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>A000000015</SAP:RCVPOR>
<SAP:RCVPRN>R3DCLNT950</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20060419144347</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2006-04-19</SAP:CREDAT>
<SAP:CRETIM>14:43:47</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocInbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20060419</SAP:Date>
<SAP:Time>144347</SAP:Time>
<SAP:Host>sun081</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>61</SAP:SystemNr>
<SAP:OS>SunOS</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>012</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAPPL</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>5DC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:PipelineService>
<SAP:QIdInternal>XBTOD___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:ParentId ChildNo="0" ChildTotal="0">444520917B4240B7E100000064070151</SAP:ParentId>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="401">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">6407015140B8444684E320CC</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">6407015E1C50444684E39DF5</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>18029</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>18029</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>24</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.424552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.443929</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.443977</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.613713</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.616273</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.625803</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.626241</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.634135</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.634561</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.645671</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.645716</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPST4</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">ST4-902</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000015</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">R3DCLNT950</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">FIDCC2</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">FIDCCP01</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />
</SAP:DynamicConfiguration>
- <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="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIAPPL</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">Correct Version from 2 to 3: 3.X-Data to 4.x-Data</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPST4</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 444520917B4240B7E100000064070151</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOD___0000</Trace>
<Trace level="1" type="T">Persisting split kid = 4445B42A672D40B8E100000064070151</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">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>

Hi Manish,
but you have to register the queues
go to SXMB_ADM and register queues option
it's one of the installation/configuration steps
you have to do it for any kind of message message exchange (if the person who installed XI didn't do it)
register the queues and restart the messages
or F6 at the queue entry
Regards,
michal

Connection Integration Server failed. Status: HTTP/1.0 401 Unauthorized

Hello everybody,
I know, that this topic is discuss several times, but I couldn't find a satisfied solution. Sorry for the questions again.
Question:
Scenario: We have to realize a proxy connection between BW 3.5 and SAP XI 3.0. SLDCHECK works fine. But we have trouble with the http - Connection. We create a destionation via TA SM59:
. Target Host : Hostname SAP XI Integration Server
- Service No: <Port>
- Path Prefix: /sap/xi/engine?type=entry
- User: XIAPPLUSER
(this destionation works fine in another Sender systems)
If we try to test the connection. We get an Logon Prompt for the SAP XI Web Application Server back. Funny is, if we put the same User / Password from SM59 in, we get no error message back. But we couldn't put any logon / user information in the proxy area. What can we do ?
I did/checked follow:
- SAP XI: The User XIAPPLUSER, has the right password and authorizations,
- SAP BW: The Destionation is created and the System - Role (sxmb_adm) ist maintained.
- SAP BW: we compare the configuration with other Sender - Systems
- SAP BW: we create the Destionation with RFC - Typ H
Remark:
I created the same Destionation in other Sender-Systems: Works fine, we didn't get any logon promp, if we test the http Destination via SM59.
Thanks for your help
Regards
Stephan

Hello Sandro,
I execute the report, but the solution was in both systems the same:
Result:
In Exchange Profile: http:<hostname:Port>/rep
In Table SPROXSET : <blank>
Status: OK: Address maintained
I also tried follow reports:
SPROX_CHECK_IFR_CONNECTION
Result: Integration Builder server functioning correctly. Data unterstood
SPROX_CHECK_HTTP_COMMUNICATION
Result: HTTP communication functioning
SPROX_CHECK_IFR_RESPONSE
Result: I get a list of xml - entries back
Remark:
I thought the cache information was obsolete. I start a full cache refresh on SAP XI site, without success.
Remark 2:
I checked the system area, and I found out, that the Sender System with the problem is a non UNICODE and our SAP XI is a Unicode. Is this a reason, we have a http connection problem ? And when yes, what can we do.....
Thanks

Log into mail server fails

How do I read mail from my Yahoo! Mail Account using Mac OS 10.5.7 Mail client?

If you really want to delete it, (all Mail in that account will likely be erased), then Mail>Preferences>Accounts, highlight the Account you want gone forever, click the little minus icon below.

How to load Matrix report data into basic table data using ODI

Hi,
How to load Matrix report data into basic table data using oracle Data Integrator ?
Requirement Description:
Following is the matrix report data:
JOB DEPT10 DEPT20
ANALYST 6000
CLERK 1300 1900 Need to convert it into below format:
JOB Dept Salary
ANALYST DEPT10
ANALYST DEPT20 6000
CLERK DEPT10 1300
CLERK DEPT20 1900
 Thanks for your help in advance. Let me know if any further explanation is required.

Your list seems to be a little restrictive, you can do a lot more with ODI procedures.
If you create new procedure, and add a step. In the 'command on source' tab set you technology and schema as per your source database. Use the unpivot functionality as described in the link, please, rather than using 'SELECT *' use the appropriate column names and alias them for eg:
SELECT job as job,
deptsal as deptsal,
saldesc as saledesc
FROM pivoted_data
UNPIVOT (
deptsal --<-- unpivot_clause
FOR saldesc --<-- unpivot_for_clause
IN (d10_sal, d20_sal, d30_sal, d40_sal) --<-- unpivot_in_clause
Then in your 'command on target' tab set the technology and schema to your target db, then put your INSERT statement for eg:
INSERT INTO job_sales
(job,
deptsal,
saledesc
VALUES
:job,
:deptsal,
:saledesc
Therefore you are using bind variables from source to load data into target.
Obviously if the source and target table are in the same database, then you can have it all in one statement in the 'command on target' as
INSERT INTO job_sales
(job,
deptsal,
saledesc
SELECT job as job,
deptsal as deptsal,
saldesc as saledesc
FROM pivoted_data
UNPIVOT (
deptsal --<-- unpivot_clause
FOR saldesc --<-- unpivot_for_clause
IN (d10_sal, d20_sal, d30_sal, d40_sal) --<-- unpivot_in_clause
also set the log counter as 'Insert' on the tab where your INSERT statement is, so you know how many rows you insert into the table.
Hope this helps.
BUT remember that this feature only came out in Oracle 11g.

Loading complex report data into a direct update DSO using APD

Dear All,
Recently, I had a requirement to download the report data into a direct update DSO using an APD. I was able to perform this easily when the report was simple i.e it has few rows and columns. But I faced problems If the report is a complex one. Summing up, I would like to know how to handle the scenarios in each of the following cases:
1.   How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
      key fields of DSO and the remaining to the data fields? Correct me.
2.   What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
      system and then include these in the DSO data fields to accommodate the extracted data ?
3.   How do I handle the Free Characteristics and Filters ?
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
     use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
     shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
I would appreciate if someone can answer my questions clearly.
Regards,
D. Srinivas Rao

Hi ,
PFB the answers.
1. How should I decide the key fields and data fields of the direct update DSO ? Is it that the elements in ROWS will go to the
key fields of DSO and the remaining to the data fields? Correct me.
--- Yes , you can use the elements in the ROWS in the Key fields, but in case you get two records with same value in the ROWS element the data load will fail. So you basically need to have one value that would be different for each record.
2. What if the report contains the Restricted KFs and Calculated KFs? Do I have to create separate infoobjects in the BI
system and then include these in the DSO data fields to accommodate the extracted data ?
Yes you would need to create new Infoobjects for the CKF's and RKF's in the Report and include them in your DSO.
3. How do I handle the Free Characteristics and Filters ?
The default filters work in the same way as when you yourself execute the reoprt. But you cannot use the Free characterisitics in the APD. only the ROWS and cloumns element which are in default layout can be used.
4. Moreover, I observed that if the report contains selection screen variables, then I need to create variants in the report and
use that variant in the APD. So, if I have 10 sets of users executing the same report with different selection conditions, then
shall I need to create 10 different variants and pass those into 10 different APDs, all created for the same report ?
--- Yes you would need to create 10 different APD's. Its very simple to create, you can copy an APD. but it would be for sure a maintance issue. you would have to maintain 10 APD's.
Please revert in case of any further queries.

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

Integrating SQL server reporting services into java

Hi all,
Has anybody integrated server reporting services into the java web application .I have tried to search google but very few resources are their.If any one knows any additional resource links or some code samples,please share with me.
Thanks

i also want the same.. pls anyone if know abt this .. post some material or approach .. that will be helpful....

Interface used in loading flat file data into bw

what is the interface used in loading flat files into the bw system.

HI Flat file load is its own interface. It leverages the S-API (Service API), the standard interface that is used to load data in the BI system.
Start from this point:
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03450525ee517be10000000a1553f6/frameset.htm
Thanks for any points you choose to assign.
Regards -
Ron Silberstein
SAP

Load flat file data into ODS in BI

Dear Gurus,
How to load flat file data into ODS?. Please share the article if you have.
advance wishes
Thanks
Venkadesh

Please search the forums before posting :
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60debae1-84dd-2b10-e7bf-bdedf1eabdf9
http://wiki.sdn.sap.com/wiki/display/BI/Beginner+Section

Uregnt - How to Load Flat File into BW-BPS using Web Browser

Hello,
We have followed the 'How to Load Flat File into BW-BPS using Web Browser' guide to build BSP web front-end to upload flat file. Everything works great but we have a requirement to populate the Planning Area Variables based on BSP drop down list with values. Does anyone know how to do this? We have the BSP coded with drop down list all we need to do now is populate variables. We can populate the variables through the planning level (hardcoded) but we need to populate them through the web interface.
Thanks,
Gary

Hello Gary,
We have acheived the desired result by not too a clean method but it works for us.
What we have done is, we have the link to load file in a page where the variables can be input. The user would then have the option to choose the link to load a file for the layout in that page.
By entering the variable values in the page, we are able to read the variables for the file input directly in the load program.
Maybe this approach might help.
Sunil

Loading flat idoc via report RSEINB00 into integration server fails

Similar Messages

Maybe you are looking for