In the first IFlow there is no mapping
1st Iflow ->
AS2 to EDISeparator (Dummy Flow)
2nd Iflow ->
EDISeparator to IDOC (Generic Converter used in the EDISeparator sender adapater, after which mapping is added)
Please suggest.
Thanks,
Nidhi Srivastava
Hi Experts,
We need to use PHBEST ORDERS type in SAP PI to create Orders in SAP system for one of our partners. As per our understanding, it will create ORDERS in SAP system. Not sure about the PHBEST messate/transaction type. Want to know whether it's a standard type in EDIFACT or do i need to go for custom message in EDIFACT. Please guide me on this.
Attached the sameple file from our partner.
Hi,
Did you load the SAP content into the B2B Integration Cockpit? If yes, is the message type available?
If the Message Type is available, use it.
If not, create it or take another message type and modify it.
Also, check https://scn.sap.com/thread/3428496
Kind regards,
Hi Experts,
If I send EDI 997 transaction with more than one ST segment (bulk 997), only the first ST is processing correctly, it is ignoring the rest.
1st iflow(Dummy) have entire data but
ISA*00* *00* *ZZ*PARTNER1 *ZZ*060321B *160906*1034*U*00401*111001272*0*P*>
GS*FA*PARTNER1*060321B*20160906*1029*480*X*004010
ST*997*6532
AK1*IN*202
AK2*810*11185406
AK5*A
AK2*810*11185407
AK5*R
AK2*810*11186590
AK5*A
AK9*A*3*3*3
SE*10*6532
ST*997*6533
AK1*IN*203
AK2*810*11186593
AK5*A
AK9*A*1*1*1
SE*6*6533
GE*2*480
IEA*1*111001272
2nd iflow sender(Main-having mapping) has only first ST segment data.
ISA*00* *00* *ZZ*PARTNER1 *ZZ*060321B *160906*1034*U*00401*111001272*0*P*>
GS*FA*PARTNER1*060321B*20160906*1029*480*X*004010
ST*997*6532
AK1*IN*202
AK2*810*11185406
AK5*A
AK2*810*11185407
AK5*R
AK2*810*11186590
AK5*A
AK9*A*3*3*3
SE*10*6532
GE*1*480
IEA*1*111001272
Please guide on this issue.
Regards,
Nidhi Srivastava
Hi Nidhi,
That would be because the 997 that you have included in the first example is invalid. See the reference to the x12 standard for the 997 transaction here where it indicates that the maximum is one ST segment on page 4. I have put strikethrough in some segments that should be removed and adjusted values based on the specification that is in the link. The proper 997 based on the data that you shared would be the following:
ISA*00* *00* *ZZ*PARTNER1 *ZZ*060321B *160906*1034*U*00401*111001272*0*P*>
GS*FA*PARTNER1*060321B*20160906*1029*480*X*004010
ST*997*6532
AK1*IN*202
AK2*810*11185406
AK5*A
AK2*810*11185407
AK5*R
AK2*810*11186590
AK5*A
AK9*A*3*3*3
SE*10*6532
ST*997*6533
AK1*IN*203
AK2*810*11186593
AK5*A
AK9*A*1*1*1
SE*13*6532
GE*1*480
IEA*1*111001272
Regards,
Ryan Crosby
Hi,
PHBEST is an edi "standard" in the German pharmaceutical industry. It has elements like EDIFACT (UNB, UNZ, UNT, UNH segments). However it has more in common with ODETTE messages.
If you compare an PHBEST message with an ODETTE and an EDIFACT you will get the differences between them:
PHBEST: UNH+4711+PHBEST:2::PH'
ODETTE: UNH+4711+ORDERR:2::OD'
EDIFACT: UNH+4711+ORDERS:D:96A:UN'
This is why the Edifact converter will have problems to find the "right" tables - even if you create an PHBEST message within the Edifact message editor with the PHB, PHT and PHP segments. PHBEST has simply the version in the wrong field for the Edifact tables.
Unfortunately b2b addon has not a message editor for Odette.
So one way is to create the PHBEST message within the odette tables. CAUTION: Please edit the tables only if you know what you are doing! Even experienced b2b addon developers make mistakes there and malform complete tables. If you try this, backup often.
In one of my projects I used an adapter module before the EdifactConverterModule and exchanged the PHBEST:2::PH' pattern with PHBEST:2:PHB:PH' . I created an edifact message called PHBEST with the PHB,PHT and PHP segments with the message version PHB. The converter was working fine with this.
Disadvatage is, that we did not integrate the original message due the changes of the StringReplacementModule.
Third alternative would be the PlainConverterModule with several tricky problems to use the composites and the field separators.
So you have three ways to integrate PHBEST with the b2b addon.
The fastest way is the combination of the EdifactEditor and a string replacement module.
The most accurate and detailed way would be the editing of the odette tables.
Kind regards
Konrad
Hi Ryan,
Thanks for your reply.
Few more points noticed while analysing -
1) For some of our partners this is working fine. We are getting 2-3 ST segments and it is working fine perfectly.
2) This is the issue with all the IDOC receiver scenario. If we are using MAIL adapter(812 EDI) it is working fine, but for IDOC_AAE(850) we are facing this issue.
3) ST segment is mapped to the IDOC node in the mapping and both the occurrences are 1..unbounded. Is this correct.
Please help.
Thanks,
Nidhi Srivastava
Hi Expert,
I want directory path of my imported archive object. How can i see where my (.jar/.xsl)file gets saved after activating the imported archive.
Regards,
Rahul
Hi Nidhi,
Are you still referring to the 997 issue you mentioned initially or something else? The ST segment makes sense to map directly to the IDoc node and that is what we do in our 850 scenario. The mapping for the inbound IDoc however should not affect how the 997 is generated by the system though.
Regards,
Ryan Crosby
Hi
I am receiving asynchronous mdn from partner but the status of mdn is always stayting in "In Process".
Could you please advise if I need to set any parameter ?
Hi,
If you are seeing that status then that indicates you are either not receiving MDNs from your partner or it could be that the URL is incorrect too. Which URL are you giving for the asynchronous MDN?
Here is the format for the URL that should be given as per the SAP Help page:http://host:port/AS2/<path>/mdn
Regards,
Ryan Crosby
Hello,
we are using B2B AddOn 1.0 SP4 (Change Number 560615) and would like create a new message in the Plain Message Editor (B2B Integration Cockpit -> EDI Content Manager -> Tab "Plain" -> Editor -> Message Editor.
However when pushing button "create" in the dialog box just an empty browser window shows up. The behavior is the same on different browsers (Chrome, Internet Explorer). The same behavior also happens when trying to create a new Set.
When following the same steps on another B2B AddOn installation B2B AddOn 1.0 SP4 (Change Number 556305) it works fine.
Is this a known issue for the above mentioned release?
Thank you for your support!
Hi Helmut,
Sharing would be great, but if that takes too long, you can always create them yourself.
Kind regards,
Dimitri
Hi Dimitri,
I know. But this is a very time consuming job, especially for the big messages like INVOIC, etc. Even if you copy it over from an existing one, you have to compare each single segment, segment group, composite, data element with it's occurrence, field lengths, mandatory/optional, ...
Maybe this has been done already by someone before ;-)
Regards
Helmut
Absolutely right. It takes time to do it right.
hopefully, someone can help you out. Fingers crossed!
Hi Helmut,
afaik "SPORTA" is not even an eancom message. You will be fine with the standard edifact converter here.
INVOIC96A (EANCOM) SPORTA -->Standard Edifact tables
INVRPT96A (EANCOM) SPORTA -->Standard Edifact tables
ORDRSP96A (EANCOM) SPORTA -->Standard Edifact tables
ORDERS96A (EANCOM) SPORTA -->Standard Edifact tables
INVOIC93A (EANCOM) EAN008 -->Copy SAP-EANCOM EAN007 to your custom EANCOM-Key with EAN008 subversion
ORDRSP96A (EANCOM) EAN007 -->Copy SAP-EANCOM EAN006 to your custom EANCOM-Key with EAN007 subversion
REMADV96A (EANCOM) EAN003 -->Copy SAP-EANCOM EAN002 to your custom EANCOM-Key with EAN003 subversion
INVOIC901 GBAS01
TAXCON901 GBAS01
Bad news here. I recommend to create the message from bottom to top. Because of pre-93a-content, it will appear as Version "1" instead of "93A".
It will take you or a "working student" 6 hours for the complete message.
I once made the mistake to copy an INVOIC-911 to INVOIC-901. I end up in hours of cleaning the differences for the used test-messages. One trick is for the duplicate UNS segments to use a custom segment group, e.g. SG99 for the last UNS segment in SG99. Otherwise the converter will ignore the last UNS - or failing to convert - depending on integration direction.
CONTRL 2 EAN002
ORDRSP 2
Kindly check, if these messages are odette messages. CONTRL-2 definetly exists in the odette tables.
Kind regards
Konrad
Hi Konrad,
thanks for all the tips. I will consider them. But one question about SPORTA, allow me to post here one example header:
UNA:+.? '
UNB+UNOB:2+<hidden>:14+<hidden>:14+160707:1611+1111111528389+++++EANCOM'
UNH+1111211528389+ORDRSP:D:96A:UN:SPORTA'
BGM+231+<hidden>+9'
For me, the UNB is indicating me that we talk about EANCOM messages, looking like a special copy of EAN00X Subset to SPORTA, it's used by all Scandinavian partners. So my assumption is to use better one of the subsets in EANCOM of 96A as a copy template, shouldn't I ?
Regards
Helmut
Hi Helmut,
in my experience the edi guys copy these specifications not asking why there is a field filled with "EANCOM" for instance.
My guess is that they are searching for a useful edi standard and find it with eancom. And then start replacing field values and then decide to use it as an "own" standard just by replacing EAN007 with SPORTA.
So it depends on the original source of inspiration how these messages are built in detail. 
Try to convert the message with the eancom converter -just replace SPORTA with EAN005. If it is working fine, then they really use the standard eancom definitions -- if not, then it is a pseudo eancom message using edifact definitions. Like stated here: No ruleset for Control key/Message Type/Message... | SCN
Kind regards
Konrad
Konard,
Even we found that CONTROL 2 was missing in edifact and raised and OSS , but now i checked in odette its present thanks 
.
So is this CONTROL an Edifact or and Odette EDI message ? do i need to use now Odette conversion (odette conversionmodule) ? is there any possibility to use Edifact conversion and use the XSD from odette.
Br,
Manoj
Manoj,
well you need to check if it is really an odette message.
In edifact authentification & control we use CONTRL-3 & CONTRL-4 messages - which are real edifact messages. Most of the CONTRL-2 messages I have seen are odette messages - others complete custom stuff. 
And no: There is no way to edifact conversion for odette messages in general. In some cases this accidently worked.
Kind regards
Konrad