Quantcast
Channel: SCN: Message List - B2B Integration with SAP Process Orchestration
Viewing all 2291 articles
Browse latest View live
↧

Re: AS2 mdn on application acknowledgement

February 10, 2015, 1:52 am
$
0
0

We use SAP PI B2B add-on, and Wal-Mart use Sterling Integrator as AS2 software.

 

I have tried to send AS2 to WM and did get  MDN back.

But WM send AS2, can't get MDN from PI, error in AS2 sender adapter :

Cannot send MDN: com.sap.httpclient.exception.NoHttpResponseException: The server 161.165.202.30 is not responding.

 

I have test all scenario with Mendelson client with PI, sync or async, send or receive, all succeed.

 

Then I'm wondering it is compatible issue?  or network problem.

 

I can't figure out why.

And the support is based in China, but the WM server is in USA. He can't do anything more.

 

How can I prove if it is network problem?

Our network guy said they already open the internet of PI with no firewall.

I  have also raised message  to the SAP support site.


Any help?

↧
Search

Re: AS2 mdn on application acknowledgement

February 10, 2015, 5:28 am
$
0
0

I am assuming that you can receive the AS2 request from their end:

 

It doesn't need to be synchronous interface for you to send back the MDN.

 

Try this:

 

Tick Sign MDN:

  • Configure your own AS2 ID (public and private)

Send Options:

  • Immediate

 

Are you using proxy server in sending outbound requests? If YES, tick the "proxy server" and put the your proxy server info (host and port).

 

Cheers,

 

R-jay

↧
↧

Re: Seeburger classifier module after PGP decryption

February 10, 2015, 5:56 am
$
0
0

Hi,

 

Let me include Stefan Hilpp in this conversation

He's aware of specific Seeburger items.

 

Kind regards,

Dimitri

↧

Re: Seeburger classifier module after PGP decryption

February 10, 2015, 6:09 am
$
0
0

Thanks Dmitri,

no need to.

issue was wrong value in one of the classifier module configuration

↧

Re: SAP PI 7.31 / Sender SOAP Channel Issue with XML tag Main/@versionMajor has incorrect value 000; expected value is 003

February 10, 2015, 1:26 pm
$
0
0

Hi...

 

 

May Be... I'm came a little bit late.... but surely, may help to someone else

 

 

I Had the same problem

According to this note:  1349125

 

Add following two Module parameters for XISOAPAdapterBean Module        in SOAP(XI) adapter sender side:


ignoreDuplicate true

generateSysAck true



This, you have to do in the SOAP Sender -> XI 3.0 Protocol.

Error_PI.jpg

 

It works for me.

 

Regards.

↧
↧

Re: AS2 mdn on application acknowledgement

February 10, 2015, 4:31 pm
$
0
0

We did sign MDN   and choose Immediate.

no proxy.

When We use domain (or not overide MDN URL ):http://gem.wal-mart.com:5080/  goes to another IP  161.168.228.14.

when we use one static IP, got same error.

↧

Re: AS2 mdn on application acknowledgement

February 11, 2015, 12:54 am
$
0
0

Can you ask your network team to trace the url and IP if it resolves with the partner details that was provided? I'm not sure as well if your partner already opened their inbound firewall with respect to your details.

 

Base from your information above, you can do a request to their end. And they can do request from their end to your AS2 path as well. Correct?

↧

Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 4:24 am
$
0
0


Hi guys,

 

I am working on a 997 Ack message using the Seeburger Split997 adapter type.

My scenario is as followed:

  • File is getting picked up from an FTP site.
  • The PI Sender File channel will perform:
    • Decrypt
    • split to 997 in a standalone implementation (no split for STs messages)

 

I have configured the module sequence of the sender channel as seen in screenshot 1.

I have configured the Split in the SEEBURGER Dashboard.as seen in screenshot 2.

I have defined a 997 channel with sender agreement.

No Bic configuration was done.

I am working exclusively with Seeburger's provided documentation.

 

The process completes with no errors but the channel reports that there is no attachment to split (see in the log texts below).

Do I need to add Bic modules in the 997 adapter?am I missing here something?

Your ideas will be most appreciated.

 

 

2015 14:06:05.263 Information Send binary file  "Test1test297670902.intchg.pgp" from FTP server "xxxxxxxxxxxx", size 2924 bytes with QoS EO

11.02.2015 14:06:05.264 Information MP: processing local module localejbs/PGPDecryption

11.02.2015 14:06:05.264 Information PGPDecryption Module: Decryption started

11.02.2015 14:06:05.264 Information PGPDecryption Module: Looking for a fitting own private key with ownPrivateKeyName=xxxxxx.gpg and keyRootPath=xxxx

11.02.2015 14:06:05.264 Information PGPDecryption Module: Message arrived in PGP Decryption Module

11.02.2015 14:06:05.264 Information PGPDecryption Module: Module Parameters have been read

11.02.2015 14:06:05.264 Information PGPDecryption Module: Parsed ASCII-Armor

11.02.2015 14:06:05.291 Information PGPDecryption Module: Algorithm used for encryption: TWOFISH (10)

11.02.2015 14:06:05.291 Information PGPDecryption Module: Own private key found: xxxxxxxxxxxx

11.02.2015 14:06:05.316 Information PGPDecryption Module: Decompression started

11.02.2015 14:06:05.316 Information PGPDecryption Module: Decryption started

11.02.2015 14:06:05.319 Information MP: processing local module localejbs/SeeClassifier

11.02.2015 14:06:05.319 Information PGPDecryption Module: Decrypted content was set to XI message

11.02.2015 14:06:05.320 Information SEEBURGER/CLASSIFIER: Successfully read message and configuration data. The analysing and classifing starts now

11.02.2015 14:06:05.321 Information SEEBURGER/CLASSIFIER: encoding -> Cp1252

11.02.2015 14:06:05.322 Information MP: processing local module localejbs/Seeburger/MessageSplitter

11.02.2015 14:06:05.322 Information SEEBURGER/CLASSIFIER: exiting SeeClassifier successfully

11.02.2015 14:06:05.322 Information SEEBURGER/CLASSIFIER: type -> AnsiX12

11.02.2015 14:06:05.323 Information SEEBURGER/MessageSplitter: Creating CCI Interaction

11.02.2015 14:06:05.323 Information SEEBURGER/MessageSplitter: Trying to establish CCI Connection to Message Splitter Adapter

11.02.2015 14:06:05.324 Information MP: processing local module localejbs/CallSapAdapter

11.02.2015 14:06:05.324 Information SEEBURGER/MessageSplitter: Finished splitting.

11.02.2015 14:06:05.324 Information SEEBURGER/MessageSplitter: Message Splitter Module is exiting succesfully.

11.02.2015 14:06:05.324 Warning SEEBURGER/MessageSplitter: There is no attachment to split. So there is nothing to do.

11.02.2015 14:06:05.325 Information Trying to put the message into the send queue

11.02.2015 14:06:05.325 Information Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System

11.02.2015 14:06:05.331 Information Message successfully put into the queue

11.02.2015 14:06:05.331 Information The application sent the message asynchronously using connection File_http://sap.com/xi/XI/System. Returning to application

11.02.2015 14:06:05.337 Information The message was successfully retrieved from the send queue

11.02.2015 14:06:05.342 Information Message status set to DLNG

11.02.2015 14:06:05.343 Information File "Test1test297670902.intchg.pgp" deleted after processing

11.02.2015 14:06:05.397 Information Message was successfully transmitted to endpoint http://SAPPID.xxxxxx.com:5xxxx/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System

11.02.2015 14:06:05.400 Information Message status set to DLVD

11.02.2015 14:06:05.660 Information Message was received by the messaging system. Protocol: XI URL: http://sappid.xxxxx.com:5xxxx/MessagingSystem/receive/AFW/XI Credential (User): PIISPID

11.02.2015 14:06:05.662 Information Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue

11.02.2015 14:06:05.670 Information Message successfully put into the queue

11.02.2015 14:06:05.674 Information The message was successfully retrieved from the receive queue

11.02.2015 14:06:05.678 Information Message status set to DLNG

11.02.2015 14:06:05.679 Information Delivering to channel: xxxxx_File_Receiver

11.02.2015 14:06:05.679 Information File adapter receiver: processing started; QoS required: ExactlyOnce

11.02.2015 14:06:05.679 Information MP: processing local module localejbs/CallSapAdapter

11.02.2015 14:06:05.680 Information File Adapter Receiver Channel Palram_File_Receiver: Start processing; party " " / service "File2File"

11.02.2015 14:06:05.684 Information Write to file "\\sappid\PI_Files\xxxxxxx\In\Test1test297670902.intchg20150211-140605-681.pgp" as binary, size 0 bytes

11.02.2015 14:06:05.686 Information File processing finished

11.02.2015 14:06:05.687 Information The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System

11.02.2015 14:06:05.688 Information Message status set to DLVD

↧
Search

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 5:54 am
$
0
0

Hi Nimrod,

 

I remember this from my Seeburger past...

 

When you have an EDI interchange, containing just 1 message, you get this warning.

That is no problem and can be ignored.

 

 

Kind regards,

Dimitri

↧
↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 5:59 am
$
0
0

but there is no 997 message produced in the SXI_MONITOR...

At least I expected to see a 997 with no reciver determination or something..


↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 6:06 am
$
0
0

you have your message splitter enabled in the module configuration.

in that case, Seeburger will try to split EVERY incoming message.

↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 6:17 am
$
0
0

according to documentation I should see now records in the SEEBURGER message monitor and in the RWB communication channel monitoring for the 997 channel.

Nada..

↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 6:28 am
$
0
0

I just checked my documentation from the past and this is how I configured a sender FILE adapter

1.png

Watch out with the classifierMappingID. This is the so called parent mapping.

mappingName is set to AUTO to dynamically determine the mapping.

You do not need this and can use BIC immediately, stating the correct mapping.

 

I guess you also have this adapter defined

2.png

and you configured the Seeburger message splitter configuration in the seeburger workbench?

 

Kind regards,

Dimitri

↧
↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 6:34 am
$
0
0

I am implementing a standalone scenario - just 997 no Bic moduels for other messages.(As mentioned in my original post)

scenario.PNG

↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 10:04 am
$
0
0

You need the BIC module. Classifier is not mandatory.

You need to indicate the mapping and set the splitter to true (my screenshot), in case you want to split up EDI interchanges of course.

 

Besides that, do the message splitter configuration and configure a sender a Split997 adapter (my screenshot).

 

Try that and share your configuration in case you still face problems/errors.

↧
Search

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 2:02 pm
$
0
0

Hi Nimrod,

 

I have taken a look at your screenshot at there a few comments from my side:

 

a) you should always use the combination Classifier/BIC/Splitter, as the only purpose of the Classifier is to help the BIC determine which mapping-rules to execute (e.g. ANSIX12, EDIFACT....)

Without a BIC-Module, you can also leave out the Classifier as it has no effect then,

 

b) in your Splitter-Config you have defined a mapping "See_E2X_ANSIX12_997_allVersions. This means that the Splitter forwards the attachments to the defined SenderAgreement which have been translated by the BIC-Module with the mapping "See_E2X_ANSIX12_997_allVersions".

However without proper Classifier/BIC- COnfiguration, there is no BIC Mapping used and therefor this SPlitter-Entry will never find an attachment that had been processed with this mapping "See_E2X_ANSIX12_997_allVersions..." => and therefor the message "there is no attachment to split".

 

 

Inbound 997s should be processed in the same way as any other Incoming ANSI X12 message (since there are also companies that combine the 997 with other message types under one ISA-Loop and therfor the processing is the same)

 

What you should do is to use the Classifier/BIC/Split-Setup...and then you will get forwarded a 997 in XML-format to the PI (SXMB_MONI) .... you can also keep the original 997 as attachment and use it later on if you want to route it forward.

 

Kind Regards

Stefan

 

 

PS: You can also take a look at this blog that explains the Classifier/BIC/Splitter concept in a real scenario for ANSI X12 messages

Quick Overview - B2B Scenario (End2End) with Seeburger EDI-Adapter

↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 10:40 pm
$
0
0

Thanks Stefan, very informative.

I am trying to use a scenario similar to the one mentioned in the documentation named

a standalone split997 module (in the screenshot). its not clear from your answer whether it is possible.

 

Just to clarify my scenario :

 

  1. Recieving an "EDI mailbag" encrypted.
  2. Decrypt the file.
  3. send back a 997
  4. following scenario (an already running process will handle the STs and Seeburger mappings according to message types.

standalon.PNG

 

Message was edited by: Nimrod Gisis

 

I have removed the classifier, and left the PGP decryption (from PI software componnents) and the splitter moduels. Still, I am getting the "no attachment". maybe it has to do with collusion between SAP PI PGP module and the Seeburger's splitter module?

↧
↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 11, 2015, 11:05 pm
$
0
0

Thanks Dmitri,

I want to keep the interchange intact (not produce other XI messages but the 997).

↧

Re: Warning SEEBURGER/MessageSplitter: There is no attachment to split.

February 12, 2015, 12:39 am
$
0
0

Hi Nimrod,

 

Just to clarify my scenario :

 

  1. Recieving an "EDI mailbag" encrypted.
  2. Decrypt the file.
  3. send back a 997
  4. following scenario (an already running process will handle the STs and Seeburger mappings according to message types.

 

=> so you are receiving a file and want to send back the 997 ?

 

The 997 is a "Functional Acknowledgement" that provides information whether the received file has a correct syntax, which means to send back the 997, the received file has to be verified in the inbound Channel.

You cannot send back a 997 that states if the file is correct or not, if you just route it through the system without verifying it.

 

When the incoming file is translated via the BIC from "EDI-Format" to "XLM-EDI-Format", this syntax check takes place and the result of this Conversion via BIC is that at least 2 attachments are available

 

a) the FunctionalAcknowledgement (that is used to create the 997 that is sent back)

b) the real Payload (in XML-EDI-Format) that can be handled by the PI-Mapping in the following scenario.

 

 

 

I have removed the classifier, and left the PGP decryption (from PI software componnents) and the splitter moduels. Still, I am getting the "no attachment". maybe it has to do with collusion between SAP PI PGP module and the Seeburger's splitter module?

 

 

If you only want to receive data and use the "MesasgeSplitter as a Standalone Tool" that has then just the purpose to route/redirect the received data to another Sender Channel

(that is, how it looks like in your screenshots setuo )... then your setup has two issues which might lead to the error mesage that "there is no attachment to split"

 

a) you have always written "SourceDest , TargetDest" instead of "sourceDest , targetDest".... and since these parameters are case sensitive, they are not recognized,

 

b) your Splitter uses "MainDocumentDecrypted" as source....so to find this attachment, your previous PGP should also specify "MainDocumentDecrypted" as target.... otherwise it will only be the default MainDocument that gets decrypted....

 

 

I am not completely sure if you "want to send the 997 back" like you mentioned or if you receive a 997 and want to move it forward through PI (like your screens/setup suggest) ...but I hope that with giving comments to both possibilities this should help you in solving this issue...

 

 

Kind Regards

Stefan

↧

Re: AS2 mdn on application acknowledgement

February 12, 2015, 12:56 am
$
0
0

Hello,

 

I am not familiar with the B2B Addon but have only worked with the Seeburger As2-Adapter, however there are some general remarks:

I have tried to send AS2 to WM and did get  MDN back.

But WM send AS2, can't get MDN from PI, error in AS2 sender adapter :

 

Usually, the asynchronous AS2-MDN is sent to the same Address/URL as the original data that has been sent to WalMart.

And since you wrote that you were able to send AS2 messages to WalMart and received back the MDN, this indicates that from the Network-Level everything should be fine for sending out data to WM.

 

Also, the URL that is used for "async MDNs" is typically specified by the Sender of the message (WM), so I would assume that they have specified a different/wrong URL in their async MDN request...

 

Or if they use different URLs for the messages and inbound MDNs .... they might not have opened the firewall yet for the MDNs coming from you.

↧
Viewing all 2291 articles
Browse latest View live
Search