Error in Oubound message using Seeburger Adapter

Hi,
I'm getting this error on the Adapter engine when trying to generate an outbound EDI message with Seeburger adapter:
2007-01-24 13:33:29      Error      Unable to forward message to JCA adapter. Reason:
Fatal exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException:
Entry rejected due to error in resource management: null, Entry rejected due to
error in resource management: null
2007-01-24 13:33:29      Error      MP: exception caught with cause
javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null
2007-01-24 13:33:29      Error      Exception caught by adapter framework: Fatal
exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry
rejected due to error in resource management: null, Entry rejected due to error
in resource management: null
2007-01-24 13:33:29      Error      Delivery of the message to the application using
connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null: javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null.
Any ideas?
Rgds,
Yves

Yves,
I think there is some problem in invoking the seeburger adapter. Have you installed the adapter? Also after installing you have to import the metadata. Check this document for further help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
---Satish

Similar Messages

INVALID_QUEUE_NAME : Error while scheduling message using qRFC

Hello SDNers
We are currently performing our PI 7.1 upgrade and one of our scenario uses a Sender SOAP of the type EOIO. We tried executing this scenario in PI 7.1 XID environment and in it worked fine without any errors but in our PI 7.1 QA environment it is giving the following errors
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SCHEDULE_ERROR</SAP:Code>
<SAP:P1>XBQOC___*</SAP:P1>
<SAP:P2>INVALID_QUEUE_NAME</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while scheduling message using qRFC (queue name = XBQOC___*, exception = INVALID_QUEUE_NAME)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please exaplian what could be the issue we are facing.
Thanks.
Kiran
Edited by: Kiran Sakhardande on Oct 22, 2008 4:08 PM

HI Kiran,
Have gone throgh the following link?
INVALID_QUEUE_NAME
Regards
Sridhar Goli

Enveloping using Seeburger adapter

For the ones using Seeburger adapters...
How are you coding you envelope tempate (ISA/GS envelope template) using Seeburger adapter as EDI tool. Do you code each and every one of your transaction type / trading partner?
And how do you, for example, send or configure 1 transaction per envelop used for 820s or 100 transactions per envelop for 814s?
Can one you tell how are accomplishing these functions?
Thank you,
Pam

reposting....
Thanks, Pam

Read Object Message using JMS Adapter

Hi,
My JMS queue receives an object message.I want to read that object message using JMS adapter.Currently the JMS Adapter payload type is given options to read only 'TextMessage','BytesMessage','MapMessage'.How to read ObjectMesage using this adapter?Please help me on this?

Hi,
As far as i know, JMS Object Messages is not supported by XI JMS adapter.
you need to have the JMS provider to transform the message to bytes messages.
(Refer to SAP note 856346)

Without using Seeburger Adapter can we convert EDI 864 TC to XML

Hello Friends,
Can we convert 864 Transaction code (Text Message) to XML with out an External adapter like Seeburger Adapter? I mean can we write a code in JAVA for conversion? If so, what should i use in that Java code?

Hi
These blog can help u....
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Already discussed thread:
EDI Conversion
Re: Seeburger Splitter adapter!!
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Conversion of Non-Standard X12 message with Seeburger Adapter

Hello,
we are using the Seeburger Adapter. Our reqirement is to receive a X12 850 order and convert it to an IDoc.
Problem now is that some additional fields are required in the X12 message that are beyond standard X12. For example we have some additional classification for order types that are used for additional classification of orders.
Would the Seeburger Adapter be able to do this additional conversion?
Or should we use some already existing fields that we use for additional information?
What would be a recommended approach here?
Thank you very much for your information

>
Prateek Raj Srivastava wrote:
> My reply was for X12 to X12 xml mapping only. The BIC MD mapping refer to this mapping. Adapter can handle only the standard structures and any change in structure should have corresponding custom mappings.
> X12 XML to IDoc mapping is what you perform in XI mapping options (graphical, java, xsl, abap).
>
> Regards,
> Prateek
Internal Mapping from X12 to IDoc is no problem.
Is BIC MD mapping available for PI adapter too or is this only part of BIC?

Socket Schema Translation Error when trying to use Socket Adapter in BPEL

Hi,
I am trying to use Socket Adapter in BPEL.
I made 2 SOA Projects
SOA Application Project 1: Socket Server (Inbound Synchronous Request/Reply). The option for ‘Native Format translation is not required(Schema is Opaque)’ is unchecked .i.e. XSD is given for both request/reply
SOA Application Project 2: Socket Client (Outbound Synchronous Request/Reply). The option for ‘Native Format translation is not required(Schema is Opaque)’ is unchecked .i.e. XSD is given for both request/reply
Socket Client which is exposed as Web Service invokes Socket Server.
1. <summary>Exception occurred when binding was invoked. Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'OutboundRequestReply' failed due to: Socket Schema Translation Error. Socket Schema Translation Error. Error while trying to translate from native. Please ensure that the schemas are set up with native annotations and comply with the output XML. Contact Oracle support if error is not fixable. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
<part name="detail">
<detail>Read timed out</detail>
</part>
Has anybody faced this issue?

Hi guys:
I got exactly the same error. I recently installed BPEL Process Manager for Developers 10g Release 2 (10.1.2) in windows XP.
The default setting for BPEL VM memory is Xms512m -Xmx512m -Xmn300m. I tried to set maximum size to 1024 but I had this error.
Error occurred during initialization of VM
Could not reserve enough space for object heap
if any body can suggest a solution will be great .
Thanks.
Message was edited by:
user533906
Message was edited by:
user533906

Batching different messages using Seeburger BIC

Hi Experts
I have an interesting requirement. I need to batch different messages e.g. ORDERS, ASN & Controls into a single Interchange. They are all EDIFACT messages and we are using Seeburger & BIC.
Any idea on how to do this?
regards

reject that nightmare requirement because it would be very difficult for the monitoring team to find error causes in such a message. Imagine BIC conversion will give some the infamous conversion errors because some string is too long. Now if you have dozens of messages in the same document, good luck
CSY

EDI Integration---Using Seeburger Adapter

Hi All,
I have a below requirement.
EDI----->XI--
>SAP and vice versa.
I am new to EDI integration,i would like to know the procedure steps to do the above scenario.
Thanks in advance,
AVR

Hi,
How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005
http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
Handling EDI interfaces using Seeburger BIC modules
Regards,
Priyanka

Scheduling of message using HTTP Adapter.

Hi All,
The scenario is SAP ECC to SAP PI to SAP MII, and we are using HTTP adapter on the receiver side.
The requirement is that, the messages should be sent to MII in the order in which ECC sends it to PI.
Can anyone please help me on how this can be achieved.
Thanks and Regards,
NehaSingh

Hi Neha,
If it is IDOC to HTTP scenario and you use EOIO also you will face a big problem.
It will not work. I have faced the same problem.
Suppose at a same time ECC genaretes 100 IDOC then then in intregration engine it may not reach at same sequecnce as IDOC no.
You can go with IDOC packageing in this case in ECC.
In ECC send the IDOCs as packages.
Also in PI create one Sender IDOC channel with package size.
then before your actual mappinng create a simple mapping program to sort the IDOC based on IDOC number. Then do the actual mapping.
Dont forget to create an Unbounded IDOC structure as source side in Mapping,
Edited by: Debashish on Jul 1, 2011 2:29 PM

Message error ORA-00936 when using JDBC adapter

Hi all,
I'm using the folow scenario:
RFC --> XI --> JDBC
RFC <-- XI <-- JDBC (response)
It's a SYNCHRONOUS interface.
RFC call without COMMIT WORK:
CALL FUNCTION 'Y_TESTE_NEI'
    DESTINATION 'RFC_XI'
EXPORTING
   DATE_FROM       = v_data_from
   DATE_TO         = v_data_to
TABLES
    t_return        = t_dados.
I'm not using KEY in JDBC message, because for test I want to get entiry table, and I set the communication channel JDBC to KEY not mandatory.
I'm not having mapping error, in SXMB_MONI I can see the two messages of interface, but both with SYSTEM ERROR.
In JDBC adapter in Runtime Workbench apears the follow message error:
com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 't7_productionorder' (structure 't7_productionorder'): java.sql.SQLException: ORA-00936: missing expression
And DUMP in function call in R/3: CALL_FUNCTION_REMOTE_ERROR
Could anyone help me about this problem ?
Thanks in advance.
Regis Ferrato

Hi Regis,
I did the same scenario just now. The error you get is, you need to check whether the fields you are entering into the database have correct datatypes.
Check out your database structure with your structure in XI, and also test in Message Mapping, to make sure you are sending correct values.
In my case I was sending date like this '10-12-06', but my DB accepts only '101206'. So I removed the '-'. It was fine .
The Dumping error is not due to your ABAP, due to the DB operation.
Let me know Whether I am correct.
Raj.

EDI Message in Seeburger adapter

Hi All,
is there any posibilities to see the signed EDI message (encrypted format) in seeburger module
please guide me the procedure
by
Boopalan

Hi Prateek Raj,
s i have done all config in Sender communication chennel & Sender Agreement
s custumer need MDN, which they can receive successfully
the same process which we did for anoterher customer its working fine
in AS2 Adapter Guid they mentioned the solution for the error Error while parsing AS2 message: AUTHENTICATION_ERROR is Check the authentication certificate settings.
but using the same certificate we can able to send & customer can able to decrypt the EDI Message
where the problem could be..?
by
boopalan

How to post multiple message using file adapter in XI2.0

We have to post multiple IDOCS.We have scenario as below.
We will have file structure like as shown below.
VKORG,VTWEG,SPART,BSART,PARVW,PARTNER,BSTDK,MATNR,MENGE,VSART,BSTZD,POLINE,BSARK
BE10;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
BE10;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
BE30;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
For this we want that 2
messages should be created.In first message there will be first 2 records
with VKORG BE10 and in second message there will be last record with VKORG BE30.
We can do it through FILE2XMBWITHSTRUCTURECONVERSION and using some options.
I am sending the configuration that I have done for my adapter.
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
mode=FILE2XMBWITHSTRUCTURECONVERSION
#mode=FILE2XMB
XMB.TargetURL=http://20.60.53.36:8000/sap/xi/engine?type=entry
XMB.ReceiverBusinessSystem=sapdev210
#XMB.ContentKind=B
XMB.ContentKind=T
#XMB.ContentType=application/xml
XMB.ContentType=text/xml
#XMB.ContentType=text/plain
XMB.QualityOfService=EO
##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
xml.recordsetStructure=IDOC,*
xml.recordsetName=SALESDATA
xml.recordsetsPerMessage=1
xml.documentName=SALESDATA
#xml.fieldFixedLengths=
xml.IDOC.processFieldNames=fromConfiguration
xml.IDOC.fieldNames=VKORG,VTWEG,SPART,BSART,PARVW,PARTNER,BSTDK,MATNR,MENGE,VSART,BSTZD,POLINE,BSARK
xml.keyFieldName=VKORG
xml.keyFieldType=CaseSensitiveString
xml.IDOC.keyFieldValue=BE10.
xml.IDOC.fieldSeparator= ;
What I have tried is hardcoding 2 in xml.recordsetStructure=IDOC,2.It works fine
Since I already knew this.
Butin real scenario we wont be knowing this that is why I have given * in configuration , and
given
xml.keyFieldName=VKORG
xml.keyFieldType=CaseSensitiveString
xml.IDOC.keyFieldValue=BE10.
With this it should identify on key field and its value and put first 2 records in one message
and last record in second message.
It is not giving any error when we start adapter but no XML message is created.Can u plz help me
for the above problem.
My datatype in repository is like
SALESDATA
    IDOC
         VKORG
         VTWEG
and allother remaining fields.
Is this scenario possible in XI 2.0.If yes then will it be done through above approach or something else.
Thanx.
Rekha.

Hi,
I think you can not handle this problem with keyFieldName/keyFieldValue.
In my opinion with keyFieldName/keyFieldValue you can create different substructures of the same XML, but you can not seperate messages with the same substructure.
But I don't know how to handle your problem ;-(
Another point is that I see a dot after xml.IDOC.keyFieldValue=BE10.
My be this is a problem too.
Christoph

EDI on XI without using SeeBurger Adapter

We're about to begin a project to do EDI on XI. We'd like to know about all options we have in addition to just using the recommended SeeBurger EDI adapter. We have a 3rd party middleware tool we could use as well. We'd like to leverage the knowledge we already have in this product. Let me know if this is a feasible architecture.
- XI handles all the SAP communication.
- 3rd party middleware vendor tool handles all EDI mappings, and also handles all communication with partners via AS2, FTP, etc.
- Communication between XI and 3rd party middleware is accomplished thru SOAP/web services or direct HTTP calls.
Under this architecture, i'm not exactly sure what XI buys us as we could communicate directly to SAP without XI but lets leave it as is for now.
Is this a feasible option?? Assume the extra development of the maps is not a major consideration since our business requirements would cause us to modify any out of the box mappings SeeBurger would provide anyway.
Has anyone else implemented EDI via an adapter outside of SeeBurger's??

hello
ur architecture seems to be ok becuase as of now i have'nt heard of XI supporting AS2 features..i guess u can configure a partner in XI in configuration builder and then create a communication channel for the same with the transport protocol as HTTP or SOAP.u can apply security over here by configuring necessary certificates..
regarding XI usage goes what third party middleware ur using..check whether it offers flexible mapping capabilities like XI (with GUI maps, XSLT or Java maps etc) or BPM capabilities (which u may require in future) and message persistence capabilities etc..
also now XI is free with NetWeaver 2004s licence.
Regards
Rajeev

Mapping Error - Dump source message to file adapter comm channel

Hi
Does anyone know of a way to dump the source message to a file adapter comm channel if - and only if - the message fails during mapping. For example, we receive a message from a trading partner that lacks an element that is mandatory during the mapping. When the mapping fails, the source message is sent - as is - to a file adapter comm channel.
I don't need anything more than the source message i.e. no need for any errors etc... to be included.
The kicker.. I would like to do this without using BPM if at all possible.
Any ideas greatly appreciated. Thx, Duncan

Hey Ram,
Go to Integration Directory and open the Receiver Determination for your scenario.
Check the configured receiver services. They are in a table-like area in the middle of the screen.
In this table of configured receiver services for that particular Sender Service/Interface, you should have the system that normally receives that message (your ERP or any other application system) and the service that contains the receiver file comm channel that will receive the message in case of error.
Check help.sap.com for help on condition editor on receiver determinations.
Now, the issue. You can only check whether a field exists, you can't check whether it doesn't exist (There's only a "EXIST" operator, and no negative operator). Thus, you can only do the following: always send messages to File, but you can avoid messages that dont have field from being sent to App System. Yeah, that sucks...
But don't fear, young padawan! There is a possible workaround. =D
In your message mapping, do the following for that particular field:
If field exists (check with Exist and IF standard functions) just bypass the field. Else, map the field with an impossible value (like string "$CREATED$"). Then, in your receiver determination, you will do the following conditions:
for App System: If field =/= $CREATED$
for File Receiver: If field = $CREATED$
Now, if the field doesnt exist, it will have value $CREATED$, thus the message will be sent to File and not to App System. If the field exists, the message will be sent to App and not to File.
Try that out.
Regards,
Henrique.

Error in Oubound message using Seeburger Adapter

Similar Messages

Maybe you are looking for