Sender AS2 adapter

Hello All,
i am doing scenario where edi document from external party goes into sap system as an idoc (i.e. edi to idoc scenario).
i done all configuration party. when i am testing my interface through configuration test it is working successfully. but it is failing in sxmb_moni saying "No receiver could be determined".
Eventhough i create proper recevier determination and recevier agreement.
could you please answer my question.

Hi,
there are many possibilities for the receiver determination error.
1) Configuration mistake
Receiver determination depends upon:
a) Sender business system
b) Sender Interface
c) namespcae under which sender interface is configured in ESR
Check for the values in MONI and compare them with the config (Receiver determination) in ID.
The above values should match in MONI and ID.
So please check each and everything.
2) Cache refresh (please check cache notifications in ID)
3) When the business system not found in SLD.

Similar Messages

Error in Sender AS2 adapter

Hi Expert,
I have configured sender AS2 adapter as per the sap guide. and share our url and AS2 name.Now when the partner is trying to send the file from their side they are gettting the following error message and in SAP PO we have not received any file via AS2 sender adapter.
We have checked the fire walls and its working fine.
2014.04.09
01:15:03:128 0326030999 PHDR OK HTTP Response-Line = (HTTP/1.1 302 Found)
2014.04.09 01:15:03:128
0326030999 PHDR ERR Trading Partner rejected the transaction
2014.04.09 01:15:03:128 0326030999 HPOS ERR Requested synchronous receipt not
returned
2014.04.09 01:15:03:128 0326030999 HPOS ERR One or more errors occurred with
this transaction. m_nErr=(2103)
Regards
Kasturika

Hi Harish,
I have change the as2 url from http://<host>:<port>/AS2 to http://<host>:<port>/AS2/B2B and now are partner is facing differnt error
2014.04.22
03:06:04:400 0637647174 PHDR OK HTTP Response-Line = (HTTP/1.1 401
Unauthorized)
2014.04.22 03:06:04:400 0637647174 PHDR ERR Trading
Partner rejected the transaction
I had checked with my partner to use the http authentication and share our user id and password. but they said that they are not using http authentication.
we also shared our public key certificate and import theirs in our nwa- certificates and keys .
Please share if anything more i need to configure.

Seeburger Sender AS2 adapter

We have a customer who purchased Seeburger AS2 Adapter. They have WAN setup with Inovis which is having AS2. Now we are in the process of setting up the AS2 using seeburger for them. if we use Seeburger AS2 adapter, then trading partners have to send their documents to the following path
http://<Server Name> :50000/SeeburgerAS2/AS2Server
Seeburger AS2 adapter will receive the documents posted to the above URL & Process them using XI
The problem we are facing is the Sender Seeburger AS2 adapter doesnt have a mechanism to Poll the Inovis AS2 Mailbox and receive the documents.
Does any one have a solution to Poll & fetch the documents from Inovis AS2 mailbox.
With Regards
K.Varadharajan

HI,
The message which are coming to XI will be picked up based on two things:
1) AS2 ID of the partner which is dicussed above and the second one is
2) Message subject :
Message Subject
This subject will be compared with the subject in the received message. This is used to find the correct channel for the inbound message. Wildcards are allowed.
There is a defined order in which the matching inbound channel is looked up. First the adapter looks for a sender channel with a message subject configured.
If there is one channel with a matching subject configured, the channel is used for forwarding the received payload to the XI system.
If there is no channel configured with an matching subject the received payload is rejected.
If there is one channel configured with a matching subject and another channel with a wildcard both channels will match. In this case the received payload is forwarded to the channel without wildcard configured.
If there is more than one channel configured with a matching subject, the payload is rejected.
I hopw it has answered ur question.
Thanks and regards,
Chirag
Reward points for helpful answers.

Sender AS2 Adapter Setup

Hi,
I am trying to send an EDIFACT file to IDOC through AS2 Adapter (sender). Can you please tell me how to configure the sender AS2 Channel.I have configured it, but it is giving me the following error in Channel Monitoring.
Alert: Maximum number of retries reached. Retry 20. Message initiation failed: Adapter call failed. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order;, failed to lookup CPA cache: Couldn't retrieve outbound binding for the given P/S/A values: FP=B2B_Certipost;TP=B2B_PH_BE;FS=B2B_SND;TS=B2B_RCV;AN=MI_E_ORDERS_D96A_oa;ANS=urn:novartis.com:pi:ph:be:OM_DD_750_LBE_L0X:Order; [4/30/09 4:19 PM]
Please share your valuable inputs.
Thanks,
Amit..

Hi,
follow the below steps;
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
-S

Sender AS2 adapter settings for Asynchronous MDN

Hello,
I need to configure the settings for AS2 sender adapter for Asynchronous MDN.
In order to configure the asynchrounous MDN Settings which parametrs i need to fill in the channel from below
1) Use Proxy
2) Proxy Server
3) Proxy Port
4) Proxy User
5) Proxy Password
6) Proxy Realm
7) Proxy Protocol
8) Server Certificate (Keystore)
9) Private Key for Client Authentication
Thanks
Srinivas

Hi,
The MDN asynchronous mode is for the AS2 receiver adapter and not sender.
If you want to use a proxy server, then only you would need to provide the details that you have mentioned and if you are using encryption, you would need to provide the encryption certificate in the corresponding receiver agreement where the comm channel is used.
Also, for asynchronous MDN, you would need to configure a report channel (AS2 sender adapter with message protocol reports) and sender agreement. You need this even if Refer to XI system option is disabled in the AS2 receiver adapter.
Regards

Message subject in seeburger sender AS2 adapter

Hi Experts,
I read few fourms regarding message subject in seeburger and in those below forum is related to my problem
AS2 Sender adapter.. How we can receive 2 messages from same partner??
like how we can identify different message types when we receive from partner
A) using AS2 ID and message subject
If we give message subject as * it will receive all the message but how to identify them as our partner is not providing message
subject.
I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter

Hi,
> Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter
When message comes to PI, initially it goes to seeburger workbench, here based on the EDI type (ANSI X12 or EDIFACT or...), EDI Version (4010 or 4020 or...) and Signal (850 or 810 or ....) it determines the respective mapping (E2X or X2E) program, this is done by Classifier.
When we are sending outbound scenarios and using MDN option then message subject plays an important role. Once we send the outbound signal we can get the ack(997) signal, based on AS2ID and message subject it identifies the respective 997 inbouns scenario.
> I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Seeburger is used if you are handling the EDI data but here you are using XCBL so you no need to use the seeburger adapters.
Regards,
Venkata Ramesh

Connectivity from Customer to sender AS2 adapter

Hi Guys,
My scenario is EDI to File, to send the data we provided our HTTP IP, port and URL to customer, here URL is https://<host_name>:<port> by using this URL we are able to receive the message upto our network, so how to get that data from network to PI System?
Any other thing we need to add to the URL path like https://<host_name>:<port>/AS2 ID or ..... ?
If yes how exactly we know we need to add AS2 or EDI or ......
Please advice me.
Thanks
Ramesh

Hi Sanju,
If we are getting the 405 error means it is success (In one of Seeburger documentation they mentioned).
My scenario is EDI to file, next file to FCC at the same time send 997 to sender, who sends the actual data.
I am able to get the message to my network (ports are open, firewall allows the data), but not getting to PI or Seeburger system.
Any one please suggest me the possible ways to trouble shoot that error.
Thanks
Ramesh

Seebuger AS2 adapter for XI as sender for multiple messages

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent. What is the name of the module? Is it specified in your sender AS2 adapter with parameters? Is it wrapped as an adapter? How do you configure the module to split and pass specific messages etc... Any help on this would be much appreciated.
Thx,
Pete

Hi Rudy,
the Classifier/BIC/Splitter - Solution is mainly designed for EDI-Messages that cannot be handled directly by XI.
IF you use pure XML-messages you should be able to handle it with XI-basic-functionality since this is what XI can handle itself.
Depending on how different your XML-Messages are, the effort will be very small or a little bit bigger.
In the ReceiverDetermination it should be possible for you to check whether certain XML-TAGs are existing or what the content for certain TAGs is BAsed on this information you can route the messages in a correct way.
(Of course you might have to create your own XSD for this containing the important TAGs of each message, so you can setup your Conditions)
Btw. the Seeburger BIC-Adapter can provide also this functionality, but this also needs to be customized)
Greetings
Stefan

Sender AS2 to SAP PO; 403 forbidden error

Hello Experts,
I am using the AS2 adapter from the B2B Addon.
I am stuck in the scenario Sender AS2 -> SAP PO; with the 403 forbidden error.
Few queries;
1. Is virtual receiver mandatory ?
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
Can you help please.
Thanks
Saurabh

Hi Harish,
Thanks for your quick response.
I have configured with the following details :
Sender Party : ABC ( 009 | GLN | 333333333 )
Sender Component : DEF
Receiver Party : PQR ( 009 | GLN | 111111111 )
Receiver Component : XYZ
Sender AS2 adapter :
Expected URL : http://10.194.35.20:8080/as2/HttpReceiver
Message ID Left : .*
Message ID Right : .*
Sender AS2 name : 333333333
Receivers AS2 name : 111111111
Expected subject : AS2 message
Partners in Mendelson :
Partner 1 :
( Local station )
1. Name : Mendelson_AS2
2. AS2 ID : 333333333
3. Email : [email protected]
MDN tab : http://<Mendelson desktop PC IP>:8080/as2/HttpReceiver
Parnter 2 :
1. Name : PQR
2. AS2 ID : 111111111
3. Email : [email protected]
Receipt URL : http://<PI-Host>:<PI-PORT>/AS2/.*
Payload subject : AS2 message
Error details :
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Transmission failed, remote AS2 server reports "Forbidden".
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: HTTP 403
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Message payload stored to

Error in AS2 adapter. Object not found in lookup of as2.. Its urgent..!!

Hi AS2 experts,
*When i tried sending an xml to partner system using AS2 adapter.. Mapping is succesfull and message is failing in receiver AS2 adapter.
1. I used the following parameters in AS2 Module.
ModuleName                                                       Module Key
localejbs/Seeburger/solution/as2                              solutionid
localejbs/ModuleProcessorExitBean                          exit
ModuleKey    ParameterName         ParameterValue
exit                JNDIName     deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Iam getting the following error.
Success     MP: Processing local module localejbs/Seeburger/solution/as2
Error :   MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2.
Error : Exception caught by adapter framework: Object not found in lookup of as2.
Error : Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of as2.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2..
2. When i tried by removing Modulename "localejbs/Seeburger/solution/as2"
It is showing the below error like AS2ID is missing.. but its there in party configuration.
Error :
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Can anyone has idea what might be wrong.
Kindly suggest me asap.
Thank You.
Regards
Seema.

Hi,
Plesae go through below links
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
and
Check with below configuration
Configuration for AS2 or simple file adapter.
We are using this module configuration for converting EDI D96A format to XML:
1 localejbs/CallBicXIRaBean Local Enterprise Bean bic
2 localejbs/CallSapAdapter Local Enterprise Bean 0
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic logAttID ConverterLog
bic mappingName See_E2X_ORDERS_UN_D96A
bic saveSourceMsg ORIGINAL_EDI
can someone please tell me the module configuration for reverse mapping at receiver end,i.e.,XML to EDI D96A
basically,I need mapping name for this.
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
File receiver:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_X2E_EDIFACT_ORDERS_UN_D93A
ONly the mapping program name changes from E2X to X2E. IN ur case it will be See_X2E_ORDERS_UN_D96A
Thanks
Swarup

How to deal Inhouse files using Seeburger AS2 adapter...!!!

Hi all,
Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries(Which deals with EDI files) which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent.
I have few custom Inhouse files where i need to recieve through AS2 adapter.
I need to differentiate the messages hitting to my communication channel.
ex:
1st message will be having
HDR PICKS
2nd message will be having
HDR PURCH
so based on the second field which has "PICKS" or "PURCH" , i need to pass the message to run the corresponding map.
How i need to configure to acheive these kind of custom Inhouse files through AS2 adapter??
Do i need to use splitter for these as well?? If yes how i need to use?
Is there any setting we can make at Sender AS2 adapter to differentiate each message??
Waiting for the answers.
Kindly reply if anyone knows.
Thanks&Regards
Seema.

Hi,
i have setup a scenario with edifact (different message types) using as2.
first i had to create a mapping using bic.
edifact_xxxx
in: edifact_service
out: functional acknowledgement.
in the mapping code i adjusted the called mapping, standard it will use see* changed it to e2x* (custom mapping)
in your case using flatfiles maybe you should take a look at the VDA structure, these files are also defined under inhouse.
when you define a input file adapter are you getting a classifier message?
like
<classifier><type>Edifact</type><classifierMappingID>XXXX</classifierMappingID><encoding>US-ASCII</encoding><additionalIdentifier></additionalIdentifier></classifier>

IDoc flat file over AS2 adapter to IDoc adapter

Hi,
The scenario is IDoc flat file(.txt) over AS2 adapter to IDoc adapter. Could anyone help on how to convert the IDoc flat file to xml in AS2 adapter to execute the mapping further? we are using PI 7.0.
Thanks in advance!
-zameer

Hi,
Since you are on Pi 7.0, you would not be able to use the modules for this in PI 7.1.
You would need to refer this document for converting from Idoc flat to XML
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a?quicklink=index&overridelayout=true
In your sender AS2 adapter, you can pass the file as is to an abap mapping which will do the conversion to Idoc xml. the output of the abap mapping goes to your message mapping then for conversion.
Another option would be to use a custom adapter module in the sender AS2 adapter to call the Aabap mapping to do the conversion into Idoc xml.
The custom adapter module would do a JCO/RFC call which will do the conversion before passing the data back to the adpter module.
Regards

AS2 adapter-- Module tab configuration to call seeburger std mappings..!

Hi Experts,
Seeburger has been installed and i want to use AS2 adapter to make use the seeburger standard mappings.
When i opened the module tab, its been found that for
Sender AS2 adapter:
Module Name                                     Module Key
localejbs/Seeburger/solution/as2             solutionid
localejbs/CallSapAdapter                         exit
Module configuration
_Modulekey      ParameterName               ParameterValue_
Solutionid           Mappingname               SEE_ORDERS_UN_...
can i use the above steps??
Is solutionid is enough to call the seeburger mapping?
or
do i need to use the Bic module to call the seeburger std mapping like below?
Module Name                                    Module Key
localjbs/CallBicXIRaBean                         bic
Module configuration
Modulekey     ParameterName               Parameter Value
Bic               Mappingname              SEE_ORDERS_UN_...
Kindly let me know.
Regards
Krupa.

HI,
For module configuration for As2 refer the below help.
Sender configuration:
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Refer the below thread which has the same discussion.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Thanks and Regrds,
Chirag

AS2 Adapter EDI scenario - question

I am working on a EDI scenario, involving AS2 adapter.
Could anyone tell me any steps to be done on ABAP engine.
reg

Hi Naveen,
follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
Thnx
Chirag

Sender AS2 MDN XML Channel error

Hi,
I am trying to configure a sender AS2 adapter to receive asynchronous MDN. But as soon as I create the channel ,it goes in error "Channel configuration is erroneous: java.nio.charset.UnsupportedCharsetException: The target charset iso885915 is not supported".
1. I don't see any other option to configure character set once AS2 MDN transport protocol is selected. Am I missing any configuration?
2. Also I am testing from mendelson and as per the mendelson log MDN is sent to PI system but I do not see any MDN in PI. We are using B2B addon SP1 on PI 7.11.
mendelson log :
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Outgoing MDN has not been signed.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: MDN created, state set to [processed].
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Sending async MDN to http://<PI_Host>:50000/AS2/AS2_Sender/mdn.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Message sent successfully (HTTP 200); 791 Byte transfered in 353ms [2.19 KB/s].
[3:27:36 PM] 17ef0d18-1e19-11e4-c6b8-0000004bc76a@PI7: AS2 communication successful, payload 1 has been moved to "C:\Users\Pankaj\Desktop\mendelson\opensource\as2\messages\EDI_Partner\inbox\17ef0d18_1e19_11e4_c6b8_0000004bc76a@PI7".

Hi Pankaj,
This is what I did:
The most important parts of the configuration are
Receiver AS2 communication channel, requesting a synchronous MDN message
Sender AS2 communication channel processing the incoming MDN message
Receiver AS2 communication channel
Sender AS2 communication channel
Within the SAP PO monitoring tools, you see something like this:
Kind regards,
Dimitri

Sender AS2 adapter

Similar Messages

Maybe you are looking for