JMS to IDOC error

I am doing a JMS to IDOC scenario...
i am getting an error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_ECC_TTG_CREATE_:
RuntimeException in Message-Mapping transformatio~
Before it was working fine...
i dont why this is happening...

Hi PSRK,
It looks like it is a message mapping error.
take the raw payload from SXMB_MONI and run in the test tab of the message mapping. To know the exact issue.
Regards,
ravi

Similar Messages

JMS - PI - IDoc scenario: possible to disable check for duplicate JMS message ID?

Dear all,
we have a scenario JMS - PI - IDoc. We are on 7.4 SP 7 AEX.
Once and again we get this error in PI Logs
com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(MessageFilterContext filterCtx)
Duplicated and already processed JMS message with JMSMessageID ID:414d512053415050523120202020202053f0f4852000fb39 and XI message id b0beffdbcee64c2605779eaacf27b335 detected.
We are currently investigating the error and it seems that the duplicate message IDs already exist on the JMS (MQ) side. The messages with the same ID reside in the same queue but have different payloads, so really are different messages
While it's certainly true that we need to get rid of those duplicate IDs in the long run, I'd like to ask if it is possible to tackle the problem from both sides.
My sender JMS Adapter looks like this:
Transactional JMS Session = Checked
Set PI Message ID (MessageID) to = GUID
Set PI conversation ID (ConversationID) to = No Value
Enable Duplicate Handling = Unchecked
Prefix Channel ID = Unchecked
--> Is there any way to tell PI to just ignore the duplicate JMS ID and continue processing?
Many thanks
Kind regards
Jens

Hi Jens - Please have a look at the below note if it helps.
If you want the duplicate messages received from different channels (that is JMS Messages with the same Message ID) to be processed as a distinct JMS messages and not as duplicate messages, select Prefix Channel ID to JMS Message ID
Reference :
Configuring the Sender JMS Adapter - Advanced Adapter Engine - SAP Library

IDOC Error with STATUS 51

HI,
I has a JMS-XI-IDOC Scenario where i has used BPM to get the response from RFC wehre the RFC input is the message from JMS.
The Response Message from RFC is mapped to IDOC .The Scenario is working and the IDOC is getting created in SAP System Iam getting the Error with Status = 51 and the required field LIFNR not found.
Request you to please provide the suggestion whether i need to make any settings to resolve this.
Thanks & Regards,
Y.Raj.

Hi !
Status 51 in most cases is because of lock occured in R3, you can check the kind of error in BD87. If it is a lock error then you can directly say process all
also check in the last page of this URL
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/frameset.htm
Thanks
Edited by: Abhishek Agrahari on Sep 22, 2008 9:54 AM

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

How to implement this Scenario(JMS to IDOC)

Hi Frnds,
I am working on one scenario JMS to IDOC .based on JMS Message my XSLT Mapping will genarate Multiple Idocs(max 3) or 2 or one.
I have to send this IDOCS based on some conditions,the conditions mentioned below.
xslt mapping genarats one message ,but this contains 3 IDOCS or 2 or 1.(Order Create , Order Change and Order Response),
what is the best approach to implement this scenario
1)f Order Create segment exists (new PO), first check SAP to see if PO does actually exist using RFC Z_BBPR46_GET_PO_FROM_FPA ,If it does not exist, pass Order Create idoc to SAP to create new purchase order
If it does exist, retrieve PO details from RFC and pass Order Change idoc to SAP to update existing purchase order
2)If Order Change segment exists (change PO), retrieve PO details using RFC Z_BBPR46_GET_PO_FROM_FPA and pass Order Change idoc to SAP to update existing purchase order
3)If Order Response segment exists (goods movement), retrieve PO details using RFC Z_BBPR46_GET_PO_FROM_FPA and pass Order Response idoc to SAP to create goods movement.
Above logic i implemented in one mesage mapping Source is XSLT Mapping Output and Receiver message in message mapping is Multimapping selected 3 IDOCS.
Regards,
raj

thanks

PI 7.0 SP15 alerts JMS Duplicate message error

Hi all,
We have a scenario where in we receive BAPI calls to R/3 from web through MQ and XI.
WEB -> MQ->XI->R/3 (Request / Response send back similarly)
We have modular configuration in the channel.
All these BAPI messages are queries needed to build an order for example product information / customer information etc.
We have PI 7.0 SP15
Sometimes we receive the error ' Duplicate JMS message with JMS ID##### detected.Duplicate will be ignored' in the sender JMS channel.Because of this error XI is not able to process subsequent messages and the channel keeps on throwing the same error.We need to clear the queue and then restart the channel to make it work.
Can any one please tell me what is the reason for occurence of this error..?
Is this ID generated in JMS or in XI?If so how this could be handled without clearing the queue's..?
When we analyzed the messages in the queue we found out same xml messages been send twice which i would imagine the query been send twice(which is a possiblity from the web) would that have caused this JMS duplcate message error??!!
Also because of this error XI is throwing multiple alert messages at the rate of 3 per second which is causing the huge performance hit as the alert inbox gets filled up..We did put the suppress multiple alert check..but before somebody reacts to these alerts there are numerous of them created..any suggestions on this is much appreciated..
Thanks for your help in advance
Larry

Larry,
Is that alert rule is generic or interface specific? If it is generic then please make it interface specific.
Thanks,
Sunil

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

How to reduce processing time in case of jms to idoc scenario

hi all,
i am doing jms to idoc scenario.
in this i'm using xslt and graphical mapping.
while perfroming E2E testing the messages are taking lot of time to get processed.
please tell me as how can i reduce this processing time or in short how can i overcome this problem.this is a critical issue in production.
regards
madhu

Hi,
1. To reduce the processing time for JMS -> IDOC scenario, try to get the Average processing time taken by JMS adapter, IE, IDOC adapter for the messages that are processed so far by going thro the Adapter Audit logs, SXMB_MONI race and Time in WE02 in R/3 system. Calculate this for 5 - 10 messages at different time to get the clear idea of which step is consuming more time. Then it will be helpful to focus on tuning that specific step. If you are using BPM, check the processing time taken by PE.
2. Check the Inbound and Outbound queues used by this interface, if required try to configure Prioritized Queue with more time allocated for this interface in Integration Engine.
3. Check the load on the Integration Server when this Interface messages are getting processed, to understand/ isolate the interfaces which are consuming more processing time and system resources.
4. If this is not in Production try to perform the Mapping/ transformation in graphical mapping itself, it will be helpful to minimise use of XSLT mapping to get better performance.
5. Check if the Archive and Delete jobs are running successfully in the Integration Server, since this will free up the occupied resources in the system.
6. If possible post seperate Forum questions for issues in different Interface scenarios, it will be easy to understand the problem for all of us.
Hope this will be helpful,
Regards,
S.Santhosh Kumar

Incoming IDOC Error "No batch input data from the screen SAPMV45A 4001"

Hello ,
The Incoming IDOC with Message type 'ORDERS' is triggering the error message "No batch input data from the screen SAPMV45A 4001" with message no 00344 . There is an SAP note 785000 to handle this type of error message which has been already implemented. Still we are encountering few IDOC error's at the time of sales order creation. The IDOC reaches status 51 throwing the error which is again reprocessed through BD87 .
We are unable to replicate the similar scenerio in Development & Testing systems as it works fine.
Can any one kindly advise how to eliminate the error "No batch input data from the screen SAPMV45A 4001" message at the time of Incoming IDOC processing.
Thanks in advance.
Best Regards
Sateesh

Dear Sateesh
Check this link where the same topic was discussed
[ VA01/VA02: batch-input error in IDoc processing|http://www.sapfans.com/forums/viewtopic.php?f=21&t=313032]
thanks
G. Lakshmipathi

IDOC error while receiving

Hi Friends,
In my scenario, I have to receive P.O. message from partner in to my R/3 system.
I am using PI 7.1
When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
I tried to find solution on sdn, and I got 2 related foroum,
Idoc Error
Re: No receiver could be determined. (File to Idoc)
But from this also I am not sure hw can i solve this error.
Please Suggest.
Thanks & Regards,
Brijesh Soni

Hi
For Error Only asynchronous processing supported for IDoc adapter outbound
IDOC adapter support asynchronous only,
Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
This thread had same problem and resolved :
Re: No receiver could be determined. (File to Idoc)
In Your case QOS is BE. Plz check in your CC if and BE is by default..
If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

JMS -- PI -- IDOC Party Communication

Hi,
I have a scenario JMS --> PI --> IDOC and vice-versa. JMS is an external system, so using PARTY communication. SAP System is within customer landspace.
My doubt is - I have to import a Business System in ID for the IDOC (SAP system). Now where should I import this Business System? Should I import the SAP Business System under Party or under Without Party?
If I am not wrong Business Component for JMS will come under the Party; have a doubt about the Business System.
Thank you,
Pankaj.

If this is in another landscape then use Party..
Ok. So nowI have imported the Business System (SAP ECC) under Without Party and will create the Business Component for JMS under Party.
Thank you,
Pankaj.

JMS-204: An error occurred in the AQ JNI layer

Approach 1) works fine but not 2).
Approach 1
=================
// Use the DriverManager to get the DB Connection
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
java.sql.Connection dbConnection = DriverManager.getConnection("the url" , "the uid", "the pwd");
javax.jms.QueueConnection queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
Approach 2 (doesn't work)
=================
// Use the JNDI Lookup to get the DB Connection
Context ctx = get the context;
DataSource dataSource = (DataSource)ctx.lookup("datasoruce jndi");
dbConnection = dataSource.getConnection();
queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
Please note that I'm able to get the Queue Connection. But when I try to send the message, I get the exception.
Exception: JMS-204: An error occurred in the AQ JNI layer
Linked Exception: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[java.rmi.MarshalException: failed to marshal setORAData(ILoracle.sql.ORAData;); nested exception is:
java.io.NotSerializableException: oracle.jms.AQjmsTextMessage_C]
App Server: WebLogic 8.1
Any thougts...
Thanks in advance.

It is complaining about the AQjmsTextMessage not being serialized. I have seen errors with not using the actual oracle connection directly. Usually the datasource has some wrapper database connection. However, i would expect a different error. I will have to experiment with this.

Thousands of IDOC Errors

Hi there,
I have recently configured workflow using SWU3 - Now suddenly there are about 10 000 new work items in everyones inbox - All related to IDOC errors.
I have made sure that the workflow administrator is set to a specific user, and in WE46, the IDOC administrator is also set.
Most of the wor-items are back-dated to about a year ago, way before the workflow was configured.
Firstly, why are all these appearing now?
Secondly, how can I get rid of them, or at least isolate them into only one persons inbox?
This is on our test system, so there is no need to investigate any idoc errors...

This is happening because you have made some program run in background while configuring SWU3 most probably the deadline program.
You can get rid of them by checking the Workflow Log and then investigating from where agents are getting determined and accordingly changing the agents to a particular user Id.
Reward points if useful

JMS to IDOC error

Similar Messages

Maybe you are looking for