Idoc - sender&reciever

Hi Folks,
could you please let me know weather idoc can act both as sender and reciever.
Thanks in advance

>
> 1) You cannot define sender IDOC channel in ID due to
> the fact that the IDOC Adapter does n't run in J2EE
> AF, but is an "built-in" Adapter
> ou pls more elaborate on this??
All messages are processed by XI in the integration engine. The Idoc is sent from the SAP system directly to the integration engine of XI and so you do not need a Sender IDOC adapter . If the adapter runs on the Adapter Engine / J2EE stack you need a sender adapter and a sendger agreement to fill up the SOAP header so that the message can be sent with correct details to the integartion engine.
> 2) We Cannot add attachment for IDOCs but, with RFC
> we can add 1 attachment/Payload per message.
No, RFC adapters do not support attachements. Take a look at this link to undrstand which adapters support attachements and which do not.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
> Am i Right what i am trying to say??
> For RFC (even IDOCs also), only Receiver
> Communication Channel configuratin is necessary ..
> but, even we can create sender cc also ..(case of RFC
> - XI - File)
RFC adapters run on the J2EE engine and so you do need a Sender RFC adapter as well.
Regards
Bhavesh

Similar Messages

IDOC sender reciever as the same client !

Hi,
If I am using the same client as the sender and the receiver then shall i create the segment types and idoc types
and ztable again in the same client......?
Can i use same configuaration created for the rfc in SM59 for both sender and receiver ?
Please give me idea regarding this when it is to create the idoc with in one client... thnks

Hi,
Check this document for your reference:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d4ce58df-0901-0010-a4be-9ae9eda61107
cheers
Aveek

Idoc is recieved on port but only control data

Hi all,
I hav created a program to send data on file port. Idoc gives status 03. but we we see data on recieving port (when file is generated)then data is abent only control data is recieved . No data records are there.I'm using FM EDI_OUTPUT_NEW to send data
If I send that idoc again directly running The FM EDI_OUTPUT_NEW then then conrol data and data records are recieved successfully.
Plz help me
Regards
Richa

Hi!
The data section is missing mostly in that case, if all the data fields within it is empty. IDoc sending is skipping empty fields.
In WE19, I think you entered all data within the fields.
Check your sender program, you might accidentally clear the IDoc data strucure before the MASTER_IDOC_DISTRIBUTE fm call.
Regards
Tamá

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

Family of 5, all use the same Apple ID/Password/Account. In settings/messages/send recieve you can "check" my email and up to three phone numbers. Essentially allowing all iMessages to be sent

Family of 5, all use the same Apple ID/Password/Account. In settings/messages/send>recieve you can "check" my email and up to three phone numbers. Essentially allowing all iMessages to be copied to shared account numbers. Please help me figure out how to prevent my children from recieving my text correspondence.

On the devices for the members of your family that you DO NOT want to see your iMessagees, go to
Settings App
Messages
Send and Receive
You should see a list of available contacts which would make messages appear. Make certain that each family member has their own individual contact and NOT the same one that you use. I find it useful to have each family member have their own icloud email and use that for iMessaging my kids. My kids do not have iPhones, but if yours do, their phone number should be listed as well. For iPads and iTouches, use icloud email addresses. If you need to send a message to all 3 kids, say, you can just add all three emails to the To box on your iMessage.
Hope that makes sense.

Purpose of adapter specific message atributes at sender,reciever file adapt

hi.
i want know birefly about adapter specific message atributes at sender ,reciever adapters.
and what would be the result if we enable this adpspecmessatb checkbox
waiting for your response.
bye.
regards.
seeta ram.

hi santosh .
thanks for yor your answer.
but when i mapped constant a to the udf and mapped to target and while iam testing i got the error like
10:38:30 Start of test
Compilation of MM_SapIsuTo3rdpartyAccountStatementExtraction successful Runtime exception during processing target field mapping /ns0:MT_SapisuTo3rdpartyAccountStatementExtraction/accstmtdetails/body/status. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._MM_SapIsuTo3rdpartyAccountStatementExtraction_ method filename$[a, com.sap.aii.mappingtool.tf3.rt.Context@421badd8] com.sap.aii.mappingtool.tf3.MessageMappingException: Runtime exception during processing target field mapping /ns0:MT_SapisuTo3rdpartyAccountStatementExtraction/accstmtdetails/body/status. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._MM_SapIsuTo3rdpartyAccountStatementExtraction_ method filename$[a, com.sap.aii.mappingtool.tf3.rt.Context@421badd8] at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:350) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._MM_SapIsuTo3rdpartyAccountStatementExtraction_ method filename$[a, com.sap.aii.mappingtool.tf3.rt.Context@421badd8] at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.getValue(FunctionWrapper.java:56) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:282) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.getValue(FunctionWrapper.java:47) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:282) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:401) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0.execute(MapServiceRemoteObjectImpl0_0.java:301) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0_0p4_Skel.dispatch(MapServiceRemoteObjectImpl0_0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at com.sap.xi.tf._MM_SapIsuTo3rdpartyAccountStatementExtraction_.filename$(_MM_SapIsuTo3rdpartyAccountStatementExtraction_.java:119) ... 26 more RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns0:MT_SapisuTo3rdpartyAccountStatementExtraction/accstmtdetails/body/status. The message is: Exception:[java.lang.NullPointerException] in class com.sap.xi.tf._MM_SapIsuTo3rdpartyAccountStatementExtraction_ method filename$[a, com.sap.aii.mappingtool.tf3.rt.Context@421badd8]
10:38:37 End of test
what would be the reason for this.
waiting for u r response.
bye.
regards.
seeta ram.

IDOC send step not running with exception in BPM?

Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
Dirk

Hello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk

Anonymous login in sender,reciever file adapter

hi all xi's
i dont know what is the need of anonymous login option in sender,reciever file adapter and the other thing is if i use check anonymous login there is no option for
specifing username,pwd,ftp server ip.
early anser will be appreciated.
bye.
regards.
seeta ram.

Hi,
when you configure your FTP server you can opt for anonymous login.
It means anyone can log on to this server just by using the IP address.
No user creation.. so ..No need for user id or pwd. i mean no authentication.
FTP connection parameters.. i.e. server n port will always be there if you are going for FTP.
It wont ask for these if you select NFS.
Being Anonymous only removes the user id n pswd option.
Anonymous login is "Never suggested"..Pretty insecure..
Dont forget to award SDN points Seeta.
Regards
Pushkar
Message was edited by:
pushkar anand

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

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

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

Regarding advenced mode option at sender,reciever file adapters

hi.
can any xi prof tell about the use of advanced mode at sender,reciever file adapters.
and one more thing that i foung difference is at sender adapter advanced mode
there are some options like msecs to wait before modification check and the other one is maximum file size bytes .
waiting for any great response.
u r great answer would be appreciated.
bye.
regards.
seeta ram.

check out this thread
Re: Dynamic file name in Receiver File Adapter
Check these also .
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
/people/michal.krawczyk2/blog/2006/02/23/xi-dynamic-name-in-the-mail-attachment--pseudo-variable-substitution
http://help.sap.com/saphelp_nw04s/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
hope this can help u

Idoc - sender&reciever

Similar Messages

Maybe you are looking for