Hi All,
we are migrating PI 7.1 to PO 7.4 single stack where all Seeburger B2B scenarios have been changed to SAP B2B.
Below are the output comparisons of both
In SAP B2B add-on I'm getting additional characters "++", any impact with these special characters or can we remove these characters from file??
Can anyone suggest the solution for this ASAP.
Regards,
Sateesh
Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
| 09.06.2014 17:52:18.709 | Information | Message is encrypted with 1.3.14.3.2.7 algorithm |
| 09.06.2014 17:52:18.778 | Information | AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm |
| 09.06.2014 17:52:18.779 | Information | AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ] |
| 09.06.2014 17:52:18.784 | Information | AS2 document size is 350 Bytes |
| 09.06.2014 17:52:18.784 | Information | Payload charset converted from ISO-8859-15 to ISO-8859-15 |
| 09.06.2014 17:52:18.785 | Information | B2B EdifactConverterModule : EDI format detected as EANCOM |
| 09.06.2014 17:52:18.785 | Information | B2B EdifactConverterModule: Message will be read as ISO-8859-1. |
| 09.06.2014 17:52:18.785 | Information | MP: processing local module localejbs/EdifactConverterModule |
| 09.06.2014 17:52:18.785 | Information | 0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false" |
| 09.06.2014 17:52:18.786 | Information | 0}: The module-paramteter "eancom..audit" is not set. Using default value "false" |
| 09.06.2014 17:52:18.791 | Information | MP: processing local module localejbs/CallSapAdapter |
| 09.06.2014 17:52:18.791 | Information | Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2 |
| 09.06.2014 17:52:18.792 | Information | Trying to put the message into the send queue |
| 09.06.2014 17:52:18.831 | Information | Message successfully put into the queue |
| 09.06.2014 17:52:18.831 | Information | The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application |
| 09.06.2014 17:52:18.836 | Information | MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm. |
| 09.06.2014 17:52:18.838 | Information | The message was successfully retrieved from the send queue |
| 09.06.2014 17:52:18.843 | Information | Message status set to DLNG |
| 09.06.2014 17:52:18.845 | Information | MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm |
| 09.06.2014 17:52:18.859 | Information | Trying to put the message into the send queue |
| 09.06.2014 17:52:18.912 | Information | Message successfully put into the queue |
| 09.06.2014 17:52:18.913 | Information | The message was successfully retrieved from the send queue |
| 09.06.2014 17:52:18.918 | Information | Message status set to DLNG |
| 09.06.2014 17:52:18.961 | Information | Trying to put the message into the send queue |
| 09.06.2014 17:52:19.001 | Information | Message successfully put into the queue |
| 09.06.2014 17:52:19.001 | Information | The message was successfully retrieved from the send queue |
| 09.06.2014 17:52:19.006 | Error | MP: exception caught with message No configuration / default adapter specified for EDISeparator |
| 09.06.2014 17:52:19.006 | Information | Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator |
| 09.06.2014 17:52:19.006 | Information | Message status set to DLNG |
| 09.06.2014 17:52:19.009 | Error | Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator |
| 09.06.2014 17:52:19.010 | Error | Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator |
| 09.06.2014 17:52:19.015 | Information | The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014 |
| 09.06.2014 17:52:19.015 | Information | Message status set to WAIT |
Hi all,
We have an AS2 receiver communication channel to a trading partner.
We use a Proxy host /port to send out data to the target URL.
However, we get the following error while trying to send data out:
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Message cannot be delivered: java.net.SocketException: Connection reset
1) We have verified that the Firewall is Open on our side and there are no issues.
2) There is no firewall on the partner side.
As per their network logs, they say that we are "Resetting" the connection after 4 or 5 seconds.
Feb 18 13:44:44 gafw1 %ASA-6-302013: Built inbound TCP connection XXXXXXXXXXXX for Outside:XXX.XX.XXX.XX/XXXXX (XXX.XX.XXX.XX/XXXXX) to Open:YYY.YYY.YYY.Y/ZZZZ (YYY.YYY.YYY.Y/ZZZ)
Feb 18 13:44:44 gafw1 %ASA-6-302014: Teardown TCP connection XXXXXXXXXXXX for Outside:XXX.XX.XXX.XX/XXXXX (XXX.XX.XXX.XX/XXXXX) to Open:YYY.YYY.YYY.Y/ZZZZ (YYY.YYY.YYY.Y/ZZZ) duration 0:00:00 bytes 0 TCP Reset-O
We are not sure what is causing this "resetting" of the connection.
Any ideas?
Best Regards,
Ravikanth Talagana
Hi,
I have a AS2 sender channel to receive AS2 messages from our trading partner. I would like to use context property AS2Filename in the ICO for the receiver determination.
However, I notice the receiver determination only takes last activated ICO details. For example, I have two ICO, one is filtered by TEST_A*.txt and the other is filtered by TEST_B*.txt. There is always one of two ICO is failing due to receiver determination error.n Last activated ICO works as expected. Any ideas?
I'm using SAP PI 7.31 Java Only and B2B add on 1.0
I need to convert SWIFT format to XML using B2B Add on . Can any one help me if there is any Std Module available in B2B Add-on for this conversion .
Hi Folks,
I have successfully tested the Inbound EDI AS2 message transfer to SAP PO from mendelson using AS2 sender adapter. But I am having issues trying to send the message from Receiver AS2 adapter to mendelson using the procedure described in the following blog.
Easy-to-use AS2 software - part IV
The receiver channel which carries the message doesn't go into error but stays in the following status indefinetely; seems like its continuously trying to access the server but never reachable.
I also tried another alternative by using the IP address of my system for the recepient url as http://<mylaptopIP>:8080/as2/HttpReceiver
but I am having the same issue as above.
When I try the computer name inplace of IP, it doesn't even recognize the host and fails at the channel.
FYI, all the following url work when accessed from browser but none of them process the message to mendelson from PO
http://testas2.mendelson-e-c.com:8080/as2/HttpReceiver
http://<mylaptopIP>:8080/as2/HttpReceiver
http://<mycomputername>:8080/as2/HttpReceiver
Regards
Kalyan.
Hi Guys,
We send back a 997-Return receipt message for all the messages we received from one of our supplier over AS2.
But we send also 997 Messages out for return receipt messages from our Supplier when we sent them a message, means we send out a return receipt message to a return receipt message 997 from the supplier, which makes no Sense!
Could you please share or let me know your thoughts on how to overcome this issue?
Thanks in Advance.
Hi,
I tried to extract the UNB interchnage control number using EDISearchParametersModule when sending out EDI messages. I put the module right after the GenericConversionModule that converts the XML into the EDI raw data.
However I can't find any correlations that I expected in the DynamicConfiguration. (like ReceiverId, SenderId, CorrelationId and InterchnageControlNumber). Does this work for inbound only or am I doing something wrong ?
Kind regards
Markus
Dear SCN forum users,
We have the following scenario
IDoc > PO > AS2 and asynchronous MDN is requested to our target partner.
We success to receive messages from partner using CC_S_AS2 channels for other AS2 > PO > IDoc scenarii. (For that we impose a dedicated URL : auth/<partner name>)
We also success to send messages to partner but MDN are not accepted back.
We have set up a dedicated CC_S_AS2_MDN channel with option AS2 MDN XML on the same party/component on which is defined related CC_R_AS2 channels.
On CC_R_AS2 channels, we set MDN URL with same URL auth/<partner name>
We find following error in “Channel Independent Logs” section
| Log |
|---|
Incoming request for auth/<partner> from user@127.0.0.1; AS2From yyy, AS2To
No channel matches incoming request for |
As we have no possible configuration parameters in CC_S_AS2_MDN channel, what should be
the URL that must be pushed to partner as MDN URL ?
Cannot be the same than inbound messages ?
What is missing so that PO can make the link with sender MDN channel ?
Thank you very much for your potential help.
Jean-Charles
Hi Team,
Please help in forming regular expression for Filename in SFTP adapter.
I tried with [a-zA-Z0-9_], [a-zA-Z0-9_].*, [a-zA-Z0-9_].txt ...etc, which didn't worked.
The following are the different type of files available in same directory
CPT_PO_TEXT_%02-06-09%_%15-28-50%.txt
P20120927060000.xls
APZ_20120927_T05D.csv
AIMS_POL_151209_1741.TXT
The numeric values change day by day and have configured 4 sender comm channels.
Please let me know what pattern can be used to pick above mentioned files along with its extensions.
Hi All,
I have B2B Add-On SP04 downloaded with me. Now we know the SP04 is compatible with -
PI 711 >= SP11
PI 730 >= SP9
PI 731 >= SP7
PI 740 >= SP2
PI 750 >= SP1
Now SP04 got released on Sep 2014. Please tell me if I have a PI 7.30 -Sp11 and PO 7.4 >SP2, both licensed before sep 2014, will the PI B2B add-on be supported on those versions.
Regards,
Vikas
Hello experts,
I have a requirement where we have to send an Idoc to different trading partners using van.
On the receiver side AS2 adapters will be used.There are many trading partners here.Can someone guide me through? ..
The entire scenario will be done in SAP PO 7.4
Breaking the entire scenario in the following parts---
1)IDoc on sender side--What will be partner profile type? Will it LS or any other (BP, GP or KU??)
2)AS2 configuration details---AS2 adapter is available in the dropdown of adapter list.What are the config details for AS2?
3)Trading partner mechanism-How this can be achieved?..what this essentially achieves ? any step by step guide available? Does it take care of sending the Idoc only to VAN or sending Idoc to different trading partners directly bypassing VAN?
4)Is using NWDS suggestible?--Is it convenient?
Any help/step by step blog will be of great help.
If I miss anything in the entire scenario, please let me know
Thanks
Ayan Chaudhuri
Hi Experts,
We have configured an AS2 sender communication channel to be able to receive EDI files from one of our EDI partners.
We have selected the option of sending the MDN "Immediately".
During the testing, we see that the message has been successfully processed .
However, when we check the Communication channel monitoring, we see that there is an error while trying to send the MDN.
The error says :
"Cannot send MDN: Remote server returned response code 400 and error message Bad Request"
The error logs from the NWA has some more detail:
"Exception is fetching property: mdn.client.auth exception: com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name mdn.client.auth not available ".
We have a similar set up with another B2B partner, where there is no issue.
Can someone let me know what is the error about?
Best Regards,
Ravikanth Talagana
Hi All,
I have B2B Add-On SP04 downloaded with me. Now we know the SP04 is compatible with -
PI 711 >= SP11
PI 730 >= SP9
PI 731 >= SP7
PI 740 >= SP2
PI 750 >= SP1
Now SP04 got released on Sep 2014. Please tell me if I have a PI 7.30 -Sp11 and PO 7.4 >SP2, both licensed before sep 2014, will the PI B2B add-on be supported on those versions.
Regards,
Vikas
Hello,
I have a scenario from File to proxy.
The file is in a SFTP server with a UCS-2 format.
In the message mapping it appears this message:
"BaseRuntimeException:An invalid XML character (Unicode: 0x0) was foundin the element content of the document."
As charset i have put UTF-8, UTF-16, ISO-8859-9, but with all of them it shows the same error.
Any idea?
Thanks
Hi All,
our scenario is Sender->SFTP to Receiver->SFTP(file).
How to use the functionality of File Content Conversion in sftp adapter?
But is a option called file content conversion in sftp ,PO 7.4
When i use FCC,in communication Channel it showing Message sent to Module Processor
but i used Standard MessageTransformBean for CC ,
i am getting the problem Sender Side while Seeing Payload Structure is Different form Sender Structure
Sender Structure
<FileHeader>
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
</FileHeader>
Payload Structure
<FileHeader>
<S_No/>
<CODE/>
<STATUS/>
</FileHeader>
Here is my Module configuration Parameters
any Clues on this Issue
Thanks in Advance
Umesh
Dear Experts,
We've followed the blog http://wiki.sdn.sap.com/wiki/display/XI/Generating+SSH+Keys+for+SFTP+Adapters+-+Type+2 to generate the SFTP keys for PI server. We've successfully generated the SFTP Public and Private keys for our SFTP Sender Adapter and could refer the Private Key View SFTP_TEST and the associated private key sftp_key in the SFTP sender adapter. Private Key is also uploaded at /usr/sap/P1D/SYS/global/SFTPKeys (Notsure if this is really required as the keys are already mentioned in NWA key store)... and we've shared our public key to our SFTP vendor to upload it on the SFTP server (uploaded successfully there as well)
But, when I activate the sender SFTP communication channel, its failing with the error 'Exception Received: com.jcraft.jschException: Auth cancel'
Is this due to the key upload path issue - bcoz Keys are not matching? Is there any other bean or param I need to mention in the sender SFTP channel? Please guide.
Thanks
Dear SCN forum users,
We have the following scenario
IDoc > PO > AS2 and asynchronous MDN is requested to our target partner.
We success to receive messages from partner using CC_S_AS2 channels for other AS2 > PO > IDoc scenarii. (For that we impose a dedicated URL : auth/<partner name>)
We also success to send messages to partner but MDN are not accepted back.
We have set up a dedicated CC_S_AS2_MDN channel with option AS2 MDN XML on the same party/component on which is defined related CC_R_AS2 channels.
On CC_R_AS2 channels, we set MDN URL with same URL auth/<partner name>
We find following error in “Channel Independent Logs” section
| Log |
|---|
Incoming request for auth/<partner> from user@127.0.0.1; AS2From yyy, AS2To
No channel matches incoming request for |
As we have no possible configuration parameters in CC_S_AS2_MDN channel, what should be
the URL that must be pushed to partner as MDN URL ?
Cannot be the same than inbound messages ?
What is missing so that PO can make the link with sender MDN channel ?
Thank you very much for your potential help.
Jean-Charles
Hi Experts,
In the standard EANCOM version for INVOIC(01B) we have sub version "EAN010" and "EAN011"
Need to add a new sub version "EAN008" in EANCOM for INVOIC(01B) meaagse.
Regards,
Vikas
Hello Experts,
My requirement was to enable B2B integration for 93A EAN006 message. However, since the 93A EAN006 is not delivered I copied 96A EAN006.
So,
was copied to
So now i have
My ICo looks like this :
And the control key association looks like this :
Still, can you help me with the below error
| 17.10.2014 13:45:16.754 | Error | MP: exception caught with cause java.lang.RuntimeException: Can not find Segment Elements for messageVersion 93A, message subversion EAN006, message agency UN, segment S_UNB, newFirstlevelElement C_S001, currentIndexLevel1 0 |
| 17.10.2014 13:45:16.758 | Error | Exception caught by adapter framework: Can not find Segment Elements for messageVersion 93A, message subversion EAN006, message agency UN, segment S_UNB, newFirstlevelElement C_S001, currentIndexLevel1 0 |
| 17.10.2014 13:45:16.759 | Error | Transmitting the message to endpoint <local> using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.RuntimeException: Can not find Segment Elements for messageVersion 93A, message subversion EAN006, message agency UN, segment S_UNB, newFirstlevelElement C_S001, currentIndexLevel1 0 |
Thanks
Saurabh