Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

Similar Messages

Why IDoc Sender Channel Used in Outbound Scenario's

Hi Team,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
Can you give me clear idea on it / suggect any blogs.
Thanks.
Drumi

HI,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
thanks,
Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

IDOC Sender Adapter and Receiver Adapter

Hi,
Why we don't require IDOC Sender Adapter to communicate with PI and why IDOC Receiver Adapter is required to communicate with SAP ?
Regards,
J Augastine

Hi,
>>>Why we don't require IDOC Sender Adapter to communicate with PI
you're talking about sender and receiver agreements right ?
as this adapter is based on abap stack - with new functionalities of IDOC adapter
require sender agreement
>>>and why IDOC Receiver Adapter is required to communicate with SAP ?
as we need to put the RFC to the destination system somewhere...
Regards,
Michal Krawczyk

OC4J Configuration issue Oracle 11g R2 Windows XP and Windows 7

Hallo!I have installed Oracle Database 11.2.0.1.0 on both Windows XP and Windows 7 on 2 different machines.
Before installing on both OSs,I had installed Microsoft Loopback Adapter and had set hostname as JOEY-PC and IP address 192.168.0.X.Once the installations were complete and I restarted the machines,I could not start OEM and the error below appears
C:\Documents and Settings\JOEY>emctl start dbconsole
OC4J Configuration issue. C:\app\JOEY\product\11.2.0\dbhome_1/oc4j/j2ee/OC4J_DBConsole_JOEY-PC_orcl not found.
When I went to the C:\app\JOEY\product\11.2.0\dbhome_1\oc4j\j2ee directory,I found the folder OC4J_DBConsole_localhost_orcl instead of OC4J_DBConsole_JOEY-PC_orcl.
I assumed that by using Microsoft Loopback Adapter,I would avoid the error above and that the OC4J_DBConsole folder would permanently remain as OC4J_DBConsole_JOEY-PC_orcl instead of OC4J_DBConsole_localhost_orcl.
Why is this folder changing its name and how can I resolve this issue?
Thanks.

Pl post the contents of the file C:\WINDOWS\System32\drivers\etc\hosts on both servers
What steps did you take to set the hostname to JOEY-PC ?
Srini

Issue with ORERS05 IDOC sending immediately after Purchase Order creation.

Hello,
When output mode of an outbound partner profile was setup as Transfer
immediately then when ever EDI output is generated in Purchase Order then
system creates IDOC and sends immediately out of system. But middle
ware has received only control record and whole data records were missing in IDOC file received by middle ware and we were receiving status 29 back from middle ware.
Right now we changed outbound partner profile, output mode was set to
Collect IDOC's and we are running RSNAST00 program in background to send those IDOC's but we
were looking into go for first option to send idoc out of system as soon EDI output is generated in Purchase Order.
Is there any way of fixing this issue.
Thanks in advance.
Regards
Prasad

Yes, I'm facing with PO IDOC only and as I said it is not issue with middle ware as they were receiving only IDOC control record.
If I resend same idoc by setting status back to 30 they were able to receive whole IDOC and more over if we set partner profile to Collect IDOC and schedule back ground job every 5mins then middleware was bale to get whole idoc.
Looks like it is SAP issue as this the message I got from SAP.
The problem only exists if the messages are supposed to be output by
means of transmission time-spot
4, that is 'immediately' (during the saving of the application).
With the output of the change message, the change documents are read for the purchasing document (all as of the last successful transmission).
With the transmission time-spot 4, it can occur that the change
documents do not physically exist on the database yet. No change message can be generated in this case and the system generates message ME140 or ME760 in the message log.

Configuration issue with ISMBP_CREATE IDOC

Hi Experts,
Currently my client is creating Business Partners through BP transaction.
The issue now we have is that create and changes made using a BAPI for creation BAPIBUSISM007_CREATEFROMDATA and change BAPIBUSISM007_CHANGE.
For both bapis i have find message type and basic types.
BP creation: Message type ISMBP_CREATE and basic type ISMBP_CREATE01
BP change :Message type ISMBP_CHANGE adn basic type ISMBP_CHANGE01
Now i am using existed partner profiles, partner profile LS -> added message type and basic types in outbound parameters.
Then i have added this BAPI IDOC details in distribution model Add BAPI using the old distribution model.
Now i am creating BP using Bapi in my system business partners are creating but IDOCs are not triggering.
Please help me.
Thanks,
Anji

Hi,
I got solution my self.
By doing below steps we can get it work.
Business Partner IDOCs will be generate in the both create and change time, for this we have to call BAPIBSUISM007_SAVEPROXIES. The input of this function module is business partner only.

Using dynamic configuration to modify parameter in sender channel?

Hi,
I would like to be able to set the filename in an SFTP sender communication channel (based upon a name determined at runtime, which is read from another file).
My understanding is that parameters set in dynamic configuration can only be set as part of mapping therefore I cannot see how to set these before my sender communication channel is invoked.
Please can someone confirm if there is a method of achieving this requirement.
Thanks,
Alan

Hi,
>>>My understanding is that parameters set in dynamic configuration can only be set as part of mapping therefore I cannot see how to set these before my sender communication channel is invoked.
they can be set anywhere in the message flow - in adapter modules too for example
>>>I would like to be able to set the filename in an SFTP sender communication channe
you cannot set it before the adapter starts polling from anything else
what you can do is to create a file -> java proxy (sftp) - anything flow
read this another file first -> call SFTP from a java proxy in a sync way to fetch the second file using the name from the first one -> do anything else what you need
you can also do the same with one adapter - axis (put the file fetching and sftp call inside one class)
but it requires some java knowledge - but it would work in one sender adapter in this case
Regards,
Michal Krawczyk

RFC Sender Channel Issue : STFC_CONNECTION

Hi All,
There has been an issue with the RFC sender channels. When SAP triggers the data, we see an error in the RFC sender channel as below
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService '<ServiceName>', toParty '', toService '', interface 'STFC_CONNECTION', NS 'urn:sap-com:document:sap:rfc:functions' for channel '<ChannelName>' (channelId 7f84f67e7efe39949dc12a2f569236fb)
But the data gets processed at the very next moment.
Program ID used in the channel is same as the ID registered in SAP. Is there some configuration missing either at SAP PI or SAP R/3 system?
Regards,
Prajeet

Hi Prajeet,
please refer this wiki [link |https://wiki.sdn.sap.com/wiki/display/XI/RFC+Faqs?showChildren=false]Q19,hope this helps.
Check if you are using the same program ID in multiple scenarios. May be if you keep different the program ID names in different RFC adapters, it should resolve the error.
also check here :/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
Regards,
Srinivas

HR Employee Address Change BAPI - CONFIGURATION ISSUE

Dear HR Gurus,
I have a typical issue in BAPI_ADDRESSEMPUS_CHANGE:
I am trying to change/update employee address using the above bapi from non-SAP application. I have tested this scenario on 4 different SAP instances. The BAPI work fine on 2 different instance 1) 4.6C and 2) 4.7
And It doesn't work on the other two instances 1) 4.7 and 2) 5.0 . I get : [Mesg: Processing in SAP failed. BAPI returned message: Type: "E", Number: "055", Text:"Make an entry in all required fields".], Even though i am entering the same values as i enterd while testing with other two instances.
I guess, If this is a bug SAP would have fixed it in 4.7 or 5.0 at least, since one of our 4.6C instance works fine. I believe it's a CONFIGURATION ISSUE.
Any one of you encountered this problem ever? Any thoughts on this would highly appreciated.
Thanks
Madan

Hi Madan,
You are right, it looks like a configuration issue. Config dictates which screens and which fields of those screens are required, optional or not displayed. From your description, it looks like the config on two of them matches with your input and in the other two, it does not. Check the config. Here is the path.
Implementation Guide for R/3 Customizing (IMG)
-->Financial Accounting
   -->Accounts Receivable and Accounts Payable
      -->Customer Accounts
         -->Master Records
            -->Preparations for Creating Customer Master Records
               -->Define Account Groups with Screen Layout (Customers)
               -->Define Screen Layout per Company Code (Customers)
               -->Define Screen Layout per Activity (Customers)
Srinivas

IDOC COmmunication Channel

Hi
i have created a receiver idoc communication channel, and when i want to check whetehr its working fine or not in Runtime Work Bench , when giving the receiver communication channel name it is saying " Communication Channel" does not exist??
plz help me

Hi,
As you said you have created the receiver idoc communication channel and if you are monitoring the idocs in IDX5 for the same then the idoc will be outbound and not inbound....
if you are confused with directions then check with out giving the directions in filter criteria....
Also are you sure that the idocs have generated successfully in PI for sending..check the interface message in MONI for the same...
Hope this clears you
Regards
Rajesh

Mass change in file sender channel.

Hi,
I want to do change in all my file sender channel and want to add following parameter.
Parameter Name : clusterSyncMode
Parameter Value : lock
I have approx 300 file sender channel.
So is ther anything by which I can perform mass change at the same time and can add parameter to it ?
Please suggest if anything like this.

You can change the parameter as a Service Property, applying to all communication channels at once. Please check the note below (for 7.1+, you must change it on NWA instead of VisualAdmin)
[ Note 1259515 - 'clusterSyncMode' is available as service property|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1259515]

How to re-use one SOAP Sender Channel for two different messages?

Hi!
I have an XI Proxy to SOAP Sync Scenario. 5 messages uses only 2 channels - cc_XI_Sender and cc_SOAP_Receiver. All messages comes from one Sender Channel and goes to one Receiver channel, and it works fine.
When I make the same for SOAP to XI Proxy Sync Scenario, I've got a problem. For example I have 2 different messages (mi_so_MSG_ONE and mi_so_MSG_TWO), so it works, if I had a two different sender channels (cc_SOAP_R1 and cc_SOAP_R2).
If I set the same Sender Channel in both Sender Agreements (cc_SOAP_R1), only one message (mi_so_MSG_ONE) goes without errors. When I send a second message (mi_so_MSG_TWO), in SXMB_MONI this message comes from Business System (BS_TEST) as message type one (mi_so_MSG_ONE), and then in stage of transformation in Interface Determination goes to message mapping program for other kind of messages (MM_MSG_ONE_to_XI_PROXY). And then - error in message mapping.
I try many URLs for both messages:
1) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=&Interface=
2) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=*
3) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=...MyNameSpace...mi_so_MSG_TWO
Message in payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<MSG_TWO xmlns="urn:xxx:yyy:MyNameSpace" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">... some fields... </MSG_TWO>
But in SOAP Header I see that is NOT second message!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
< !-- Inbound Message   -->
<SAP:Main>
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>93233F70-3E2F-11DF-8CD3-00237D301CD6</SAP:MessageId>
<SAP:TimeSent>2010-04-02T08:13:09Z</SAP:TimeSent>
<SAP:Sender>
    <SAP:Service>BS_TEST</SAP:Service>
    <SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Sender>
<SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Main>
Is it correct that many kinds of messages cannot goes through one Sender Channel ? If not... How can I reuse one SOAP Sender Channel for both this messages?
Thanks for helping.

Thanks for answers!
It means a webservice application will be deployed and exposed in PI using the associated Message Interface and its namespace information in the SOAP Sender channel.
It means only one Sender Channel per one pair of names (name of Message Interface and name of namespace). And it will fail if I change something. And question is: why URL for sending SOAP message contains parameter "Interface"?
"backward compatibility" or "for future use only"?
Nothing happens when I change this parameter, seems that name of Interface comes from first of founded Sender Agreements.
If the structures are the same
No. Structures are different.
Making one structure per all SOAP incoming messages looks workable, but... looks strange (in fact I have a lot of SOAP messages, more than 100 Sender channels).
I found an information, that I can use one Sender channel per many messages with different structures only if I make this messages like different Operations in one Service Interface (in PI 7.1).
But in this case in list of messages in SXMB_MONI I will see only a one name of Service Interface for all my messages and it's not so comfortably for supporting: to take a name of operation that fails I need to goes inside.
In older version of XI (prior 7.1) using one sender channel per many messages allowed without any hints.

No Sound from Auxillary if Send Channel is Muted

I use aux/buss channels a lot and will often mute the channel I'm sending from and then only use the buss channel in the mix. Something weird happened recently- if I mute the channel I'm sending from no sound goes to the buss. Previously I could mute it and it would still send. Now the only way to get the channel to send (and without hearing volume from it) is to take the fader all the way down (I'm using the pre-fader option). Now I have old mixes where I can't hear anything until I go back, unmute all the send channels, and take the volume of all of them down.
Anyone have any idea about what might have happened, could I have accidentally changed a preference or setting to make this happen? Apologies if the above is unclear.

All the sudden I got the similar problem with Logitech Z-5500 with optical out...test with THX Consol and no sound coming out of rear Speakers instead front R and L.......update to latest driver but problem remains....

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Idoc Sender Configurations

Hi,
Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
regards,
Kishore

Hi Kishore,
Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
also i give a quick checklist, chk it out.
1)Create an RFC destination to XI in the sender SAP system using SM59
2)Create a transactional port to XI using the RFC destination created in the above step
3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
4)Create a logical system using transaction bd54 for the partner agreement created in the above step
5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
6)Create an RFC destination to the Sender SAP system using SM59
7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
8)Create SLD entries(technical and business system) for the sender SAP system.
In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 2:44 PM

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Similar Messages

Maybe you are looking for