IDoc Adapter error / oss note 856266

Hi all,
Has anyone else run into and successfully fixed the error described in oss note 856266? We ran into exactly this issue. Found the note by searching on the error message, downloaded and applied the correction instructions, all the while feeling pleased it was such an easy fix...
Nothing changed whatever though after the correction instructions were implemented. So either we did something dumb or the fix is not working for our system. Just wondered if anyone had similar experiences?
We are on Win2k/SQLServer/SP13
Cheers,
Chris

One LAST suggestion. Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS). Try authorization group 'SS' (without quotes). So:
Object: S_TABU_DIS
Activity: 03
Auth. Group: SS
I recall now that a customer recently had this issue and (for them), this helped.
Jin

Similar Messages

Metadata EDISDEF not maintained - Idoc adapter error

hi,
In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
Any ideas or suggestions.
Thanks
Pandari

One LAST suggestion. Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS). Try authorization group 'SS' (without quotes). So:
Object: S_TABU_DIS
Activity: 03
Auth. Group: SS
I recall now that a customer recently had this issue and (for them), this helped.
Jin

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

IDOC Adapter error while load balancing

Folks,
I am facing an issue when I am switching on Load balancing button in RFC destination while sending IDOC in sender system . The sender system shows this error in SM58
IDoc adapter inbound channel: Error Error when rea
Thanks,
Manish

Hi Manish...
This is from F1 on Traget host field in SM59..Check part in bold..
Name of target host
 Name of the target host as displayed by the UNIX command 'hostname'.
 If you are using load balancing, the target host must be the host name
 of the message server of the SAP System. This is defined in the profile
 parameter 'rdisp/mshost' of the target system. If you have any further
 questions, consult your system administrator. 
 You can specify host names as
 - Normal host names
 - Host names in DNS format (if DNS available)
 - IP addresses
 - SAProuter names (in the form /H/.../S/.../H/.../S/... )
Notes
 If you enter the host name (for example, hs0311) as the target host in
 an RFC destination, its IP address is stored internally in the database
 table RFCDES (destination administration). This speeds up the RFC
 connection initiation, since the host name does not need to be converted
 into its IP address.
 However, problems occur if the IP address of the target host changes.
 For this reason, you must adjust the RFC destinations if the IP address
 of the target host changes.
 If you specify the host name as a SAProuter name (/H/hs0311 instead of
 hs0311), it is not converted into its correspondidng IP address.
 Instead, it is stored in its SAProuter form in table RFCDES.

EJB adapter errors are not catched by the composite fault handler

Hi,
I got a serious problem in soa suite 11g ps3 that ejb adapter failures are not catched by the soa suite fault framework.
for example when I do a persist of an entity on a EJB session bean and I dont provide all required fields I get a rollback error when the BPEL component is finished.
Instance ID bpel:142089
The transaction was rolled back. The work performed for bpel instance "142089" was rolled back, but the audit trail has been saved for this instance
Error Code: 1400
Call: INSERT INTO INFORMATIELEVERINGEN (ID, DATUM_BEWAREN_TOT, BEWAARTERMIJN_IN_DAGEN, GEBRUIKER, ADRES_WAARNAAR_VERSTUURD, OUTPUTPRODUCT_TYPE, INTERMEDIAIR_PRODUKT, INHOUD_VERSTREKKING, RIN_ID, DETAIL_3, DETAIL_1, DETAIL_2, KETEN_OBJECT_TYPE, ORG_ID, TIG_ID, DATUM_SAMENSTELLING, KETEN_OBJECT_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [314, null, null, null, test, null, null, null, null, null, null, null, null, 1, 1, 2011-09-27, 42]
Query: InsertObjectQuery([email protected])
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Error committing transaction:; nested exception is: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("VSG"."INFORMATIELEVERINGEN"."OUTPUTPRODUCT_TYPE")
what I did is to set idemponent = false on the partnerlink but then the invoke fails instead of the bpel ( same error ) and still no compensate or catch in bpel.
Added the fault policies to the composite and rethrowed the error to BPEL. Still no luck.
But then replaced the EJB adapter with the db adapter which does the same insert as the EJB and I got a nice bpelx:bindingFault which I can catch and handle.
thanks

Here is the total error message
[2011-09-29T19:33:28.316+02:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: 4af4f9da03d6b2c4:-1e444ff3:132b61dbaea:-8000-0000000000000312,0:1:100000005] [APP: soa-infra] failed to handle message[[
java.sql.SQLIntegrityConstraintViolationException: ORA-01400: Kan geen NULL invoegen in ("HR"."INFORMATIELEVERINGEN"."OUTPUTPRODUCT_TYPE").
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
 at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
 at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
 at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
 at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
 at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
 at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1079)
 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
 at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
 at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3887)
 at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1508)
 at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:172)
 at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:788)
 at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:863)
 at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:583)
 at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:526)
 at org.eclipse.persistence.internal.sessions.AbstractSession.executeCall(AbstractSession.java:980)
 at org.eclipse.persistence.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:131)
 at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:206)
 at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:192)
 at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:341)
 at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:162)
 at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:177)
 at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:465)
 at org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
 at org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
 at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:290)
 at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
 at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:740)
 at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:643)
 at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
 at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2908)
 at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1291)
 at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1273)
 at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1233)
 at org.eclipse.persistence.internal.sessions.CommitManager.commitNewObjectsForClassWithChangeSet(CommitManager.java:224)
 at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:123)
 at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3348)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1422)
 at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:610)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1527)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3181)
 at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:332)
 at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:157)
 at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
 at weblogic.transaction.internal.ServerSCInfo.doBeforeCompletion(ServerSCInfo.java:1239)
 at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1214)
 at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:116)
 at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1316)
 at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2132)
 at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:272)
 at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
 at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:622)
 at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:455)
 at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:52)
 at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
 at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
 at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
 at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
[2011-09-29T19:33:28.332+02:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: 4af4f9da03d6b2c4:-1e444ff3:132b61dbaea:-8000-0000000000000312,0:1:100000005] [APP: soa-infra] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Error committing transaction:; nested exception is: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: Kan geen NULL invoegen in ("HR"."INFORMATIELEVERINGEN"."OUTPUTPRODUCT_TYPE").
Error Code: 1400
Call: INSERT INTO INFORMATIELEVERINGEN (ID, DATUM_BEWAREN_TOT, BEWAARTERMIJN_IN_DAGEN, GEBRUIKER, ADRES_WAARNAAR_VERSTUURD, OUTPUTPRODUCT_TYPE, INTERMEDIAIR_PRODUKT, INHOUD_VERSTREKKING, RIN_ID, DETAIL_3, DETAIL_1, DETAIL_2, KETEN_OBJECT_TYPE, ORG_ID, TIG_ID, DATUM_SAMENSTELLING, KETEN_OBJECT_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
 bind => [7, null, null, null, test, null, null, null, null, null, null, null, null, 1, 1, 2011-09-29, 42]
Query: InsertObjectQuery(nl.justid.verstrekkingen.model.entity.Informatielevering@2499c09)
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Error committing transaction:; nested exception is: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: Kan geen NULL invoegen in ("HR"."INFORMATIELEVERINGEN"."OUTPUTPRODUCT_TYPE").
Error Code: 1400
Call: INSERT INTO INFORMATIELEVERINGEN (ID, DATUM_BEWAREN_TOT, BEWAARTERMIJN_IN_DAGEN, GEBRUIKER, ADRES_WAARNAAR_VERSTUURD, OUTPUTPRODUCT_TYPE, INTERMEDIAIR_PRODUKT, INHOUD_VERSTREKKING, RIN_ID, DETAIL_3, DETAIL_1, DETAIL_2, KETEN_OBJECT_TYPE, ORG_ID, TIG_ID, DATUM_SAMENSTELLING, KETEN_OBJECT_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
 bind => [7, null, null, null, test, null, null, null, null, null, null, null, null, 1, 1, 2011-09-29, 42]
Query: InsertObjectQuery(nl.justid.verstrekkingen.model.entity.Informatielevering@2499c09)
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:207)
 at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
 at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:887)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
 at java.lang.Thread.run(Thread.java:662)
]]

TNS-12560: TNS:protocol adapter error listener not starting up.

Hi all
we came to an issue where we have to move our server from one data centre to another after unplugging the machine and re-plugging the server
1) Operating system (OEL 5.1) started.
2) Database 11gR2 started.
3) Listener Failed to Start.
[oracle@yam01 tmp]$ lsnrctl start lsn_yscc12
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-OCT-2012 07:57:58
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Starting /u01/app/oracle/product/11.2.0/bin/tnslsnr: please wait...
TNS-12537: TNS:connection closed
TNS-12560: TNS:protocol adapter error
TNS-00507: Connection closed
Linux Error: 29: Illegal seek
[oracle@yam01 tmp]$
When checked in sqlnet.log we found.
[oracle@yam01 log]$ cat sqlnet.log
Directory does not exist for read/write [u01/app/oracle/product/11.2.0/log] [u01/app/oracle/product/11.2.0/log/diag/clients]
[oracle@yam01 log]$
/u01/app/oracle/product/11.2.0/log
/u01/app/oracle/product/11.2.0/log/diag/clients --> here under diag folder client folder was missing.
drwxrwxr-x 3 oracle oinstall 4096 Sep 30 12:59 /u01/app/oracle/product/11.2.0/log/diag/
*[oracle@yam01 log]$ cd /u01/app/oracle/product/11.2.0/log/diag/clients*
-bash: cd: /u01/app/oracle/product/11.2.0/log/diag/clients: No such file or directory
*[oracle@yam01 log]*
[oracle@yam01 diag]$ mkdir clients
[oracle@yam01 diag]$ ls -ltr
total 12
drwxr-x--- 3 oracle oinstall 4096 Sep 30 12:59 rdbms
-rw-r----- 1 oracle oinstall 15 Oct 2 07:43 adrci_dir.mif
drwxr-xr-x 2 oracle oinstall 4096 Oct 2 08:27 clients
[oracle@yam01 diag]$
and added *"SUBSCRIBE_FOR_NODE_DOWN_EVENT_lsn_yscc12=OFF"*
and then when started all the listener it started successfully.+_
[oracle@yam01 ~]$ lsnrctl status lsn_yscc12
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-OCT-2012 08:40:19
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=100.100.50.199)(PORT=1603)))
STATUS of the LISTENER
Alias lsn_yscc12
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 02-OCT-2012 08:28:09
Uptime 0 days 0 hr. 12 min. 9 sec
Trace Level admin
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/yam01/lsn_yscc12/alert/log.xml
Listener Trace File /u01/app/oracle/diag/tnslsnr/yam01/lsn_yscc12/trace/ora_10095_3086223040.trc
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=100.100.50.199)(PORT=1603)))
Services Summary...
Service "YSCC12.YAMAMACEMENT.COM" has 1 instance(s).
Instance "yscc12", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@yam01 ~]$
Thanks all for Reading this post
hope if you came across this issues this may work for you.
Best Regards
Kaleem.

Welcome to OTN
Thank you For you sharing :)

HTTP Adapter error description not showing in alert

I have created a alert thru alertcatdef & created a rule in administartion, when we have a issue with http adapter, I get the alert as follows
Subject: HTTP Adapter Error
Importance: High
Alert ID: ##06488##
HTTP Adapter Error - Possible Tracs Interface issues
Please Review details here below:
Time: 10/23/2008 - 13:56:58 - DPI -HP-UX DPI 700
Messages_ID:
Rulename:
Error Category:
Error Code:
Sender Info:
Service:   Interface: Namespace:
Receiver Info:
Service: Interface:   Namespace:
Adapter Type:
Adapter Error:
there is no error description when this alert generated, is there anything I missing on the alert, can some throw some suggestions
thanks
ramesh nallapu

In the slg1, I see
Alert was generated in logical system DPICLNT010
Alert is generated on the Central Alert Server
Alert category: HTTP_ADAPTER
Expiry time: 20081024 135658
Recipient from alert category: XIDEV
Recipient from alert category: XISUPPORT
Delivery by e-mail to XIDEV
Delivery by e-mail to XISUPPORT
External ID of alert: 06488
Delivery                                                 1 completed
Alert created. ID: 49008E897C8C5D01E1000000C085E11E
thanks

IDOC Adapter Error

Hi All,
My scenario is JDBC to IDOC, where I am fetching data from Database and posting an IDOC in SAP. My ALE Configuration is correct. I have done the following steps:
In XI:
1. Created RFC destination to connect to ECC system
2. Created Port in IDX1
3. Imported Meta-data in IDX2
In ECC:
1. Defined Logical system
2. Partner Profile settings.
Still, I am getting the below error, not sure why is this occuring...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone help me out with what could be the cause of the error.
Thanks in advance.
Regards,
Amit

Hi Amit,
check this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
OR Check the receiver IDOC setting in my posting on Wiki
for File to IDOC scenario are u missing something
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
copy and paste complete link in URL or click here
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC& then Part3
Sachin
Message was edited by:
Sachin Dhingra

Receiver mail adapter error -mail not going to other domain users

in xi this error is coming in mail adapter -
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server not responding OK to MAIL FROM; Domain of sender address XXXat d rate of XX.XX.com does not resolve
any resolution.upto yday everything was working fine.i crosschecked scot settings they r ok.

Hii,
In SXMB_MONI , its showing successful.
In RWB , its showing error
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server not responding OK to MAIL FROM; Domain of sender address XXXX does not resolve.
I checked mail id is perfect and settings r ok.
Pls let me know wat else we can check and rectify it.

XI- CRM through IDOC adapter - error in outbound status of XI

I have set of messages created today, each of which have 10,000 records as well as same no. of idocs as outbound in XI.
only few messages have status 'messages processed' adn lot of messages are in staus 'Message Recorded (Commit follows)' and 'System Error (Restart Possible)'.
So only the expected idocs are not coming in CRM. But i see the idocs XI. i clicked on IDOC in outbound column of SXMB_MONI.
how can i restart the same message and get the idocs into CRM.
THanks for your help in advance.
Regards,
Jilan Bhasha

hi Agasthuri Doss,
Do you mean to Restart the message?
i tried restarting the message, then prompted with the below message.
Do you want to retain the trace level for the
selected messages (with errors) for the restart
or increase it (maximum level)?
i click on Retain, then the below error appears.
'You cannot restart XML message
E79C4320576611DBBAB10003BAD9E360 with this
status/type'.
Thanks & Regards,
Jilan Bhasha

IDOC Adapter error"ATTRIBUTE_INV_SND_SERV'

I am doing small example like Using HTTP Client to submit Order Response XML from my browser and Converting Order Response XML file to an order response IDOC of type ORDERS05 idoc. I have developed all the necessary objects in Integartion Repository & Integration Directory and posted the Order Response XML file through HTTP client.
I am getting the error message(in SXMB_MONI)like "Unable to convert sender service OrderResponse to an ALE logical system".
Appritiate, if some one help me On this .
Thanks
Sudha

For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Check the following blog.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
regards
Shravan

IDOC Adapter error / ATTRIBUTE_WRONG_INTF

Hi at all,
I have a problem regarding a interface sending IDOCs ( messagetype HRMD_A ) from one R/3 to another R/3 system via XI.
I have created a new Message Interface which has the Message Type of the imported IDOC typ ( HRMD_A06 ).
When the system tries to process the inbound IDOC I get the following message :

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_HR_A_Cas</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_HR_A_Cas</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Where can the problem be located ??
Why can't the IDOC interface be interpreted ?
I hope somebody can give me an advise.
Thanks
Florian

Hi Florian,
my solution:
Create a simple BPM which will handle your situation
BPM:
reveicer step -> check step -> (transformation one or two ) -> send step
in bpm you can use as many message interfaces (abstract idoc ) as you want
Regards,
michal
Message was edited by: Michal Krawczyk

AQ Adapter error: Could not create XML document carrying AQ Headers

I'm having problem with the AQ adapter (ADT) sample that comes with the SOA 10g install.
I am running 10.1.3.4 on XP, using Oracle XE.
I can use the sample sql script to enque and deque. However, when I deploy the sample ADT (BPEL project), I see errors in the opmn log. The BPEL instance is not even created.
I see another post with similar question, Re: Debugging BPEL when using Oracle AQ but no answer.
Any help is greatly appreciated. Thx!
----------------- err log --------------
<2009-07-15 00:04:31,656> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2009-07-15 00:04:32,031> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ctor: Initialized MessageReader for queue CUSTOMER_IN_QUEUE, consumer = null)
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound> MessageReader_ReadMessage: Could not create XML document carrying AQ Headers: [Ljava.lang.StackTraceElement;@e7af3a
<2009-07-15 00:12:15,984> <ERROR> <default.collaxa.cube.activation> <AQ Adapter::Inbound>
java.lang.Exception: java.lang.NullPointerException
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:750)
 at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:261)
 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
 at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseToCache(StatementBCELProxy.java:67)
 at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseTarget(StatementBCELProxy.java:79)
 at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_close(SQLBCELProxy.java:95)
 at oracle.oc4j.sql.proxy.StatementBCELProxy.close(StatementBCELProxy.java:92)
 at oracle.AQ.AQOracleQueue.destroyStmt(AQOracleQueue.java:3099)
 at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1793)
 at oracle.AQ.AQOracleQueue.dequeue(AQOracleQueue.java:1307)
 at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:485)
 ... 4 more
<2009-07-15 00:12:16,203> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Uncaught exception oracle.as.j2ee.transaction.tpc.ProtocolErrorWithNotification in JCA-work-instance:AQ Adapter-0 - cause: Branch [oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740, Branch Id 7c.e5.55.76.00.00.00.00.00.00.00.00.00.00.00.01), oracle.oc4j.sql.xa.EmulatedXAResource@14d9865, state={PREPARED}, exception error code=] in transaction Global Transaction Xid( Global Id 34.5f.1e.a8.ff.ff.ff.ff.cd.b9.38.7d.22.01.00.00.7a.02.00.00.00.00.00.00, Format Id 1330790740), type=orabpel, state=COMMITTING, time in completion or recovering=0)
....

thanks for the reply. I did look into that post, and couldn't found where to set that option either.
However, my PC was rebooted a few times today (I didn't change anything with BPEL), and I just re-ran the test now, that problem disappeared! It is working fine now.

Idoc Error: Could not find code page for receiving system

hi,
I am facing the following error while processing Idocs.
ERROR: Could not find code page for receiving system
Diagnosis
For the logical destination BWFIN, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Can somebody suggest a solution for this. I have verified that the RFC destinations have been created both on the sender and receiver, ports (WE21) have been defined, and partner profiles (WE20) also created. How would I troubleshoot this problem?

Hi,
I did analyse on this issue.It is all because of the Langauge settings in the SM59.This can be done by the BASIS person.The Language field would be empty, but when ever we send the IDoc from the unicode to a non unicode system we have to mention the Langauage used.
If this helps you really award me the points.
~Katty

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

IDoc Adapter error / oss note 856266

Similar Messages

Maybe you are looking for