Re: B2B Add on - Party configuration using B2B - AS2 Aadapter
Hi Saurabh , Under the Identifier tab , What would be the expected value for Agency & Scheme. Can you help with that ,
View ArticleRe: Classifier mapping to read Sender & Receiver Identification Number from...
As we are using custom XML (GS1 XML). How do we identify the sender and Receiver using B2B add-on. Can anyone help me on this.
View ArticleRe: B2B Add on - Accepted /Partially Accepted using EDI Seperator.
Expert Team , I did configure a Sender EDI Separator Channel of CONTRL message type to read the Control Ackn sent from EDI Sep Receiver Channel. But this channel is not able to find any CONTRL...
View ArticleClik here to view.
Re: B2B Add on - Party configuration using B2B - AS2 Aadapter
Hi Mithali, http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?QuickLink=index&… Under Sender Agency; put <your Business Service / System /...
View ArticleRe: B2B Add on - Party configuration using B2B - AS2 Aadapter
Hi Saurabh , We are actually looking forward for Inbound scenario. What parameters do we pass then.
View ArticleRe: B2B Add on - Party configuration using B2B - AS2 Aadapter
Hi Mithali, Can you send the configuration screenshots to saurabhakumbhare@outlook.com or share here. ThanksSaurabh
View ArticleRe: EANCOM message : Separate channel per message sub-version
Hi Saurabh, If you cannot achieve the segregation by standard EDI Sender channel, I could think of below option. Have a single sender interface (with the XSD of subversion having superset of fields)...
View ArticleRe: EANCOM message : Separate channel per message sub-version
Hello Sudharshan, Can you please elaborate more on "Have a single sender interface (with the XSD of subversion having superset of fields) and communication channel for both EAN sub versions." please. I...
View ArticleRe: Message could not be forwarded to the JCA adapter. Reason: String index...
Hi, We were able to fix this issue by upgrading the adapter. Please refer to Note 1975469. Regards,Pranay Aitha
View ArticleRe: EANCOM message : Separate channel per message sub-version
Hi Saurabh, Key for this approach is to do the comparison between EAN 0008 and EAN 0010 structures. You can do the comparison in B2B Cockpit -> Compare Messages. If the differences seem to be just...
View ArticleClik here to view.
Re: EANCOM message : Separate channel per message sub-version
Hello Sudharshan Aravamudan, Thank you very much for thinking it accross For my current requirement, i compared the differences between EANCOM-ORDERS-96A-EAN008 and EANCOM-ORDERS-93A-EAN007, i saw many...
View ArticleRe: B2B Add on - Accepted /Partially Accepted using EDI Seperator.
Hi Mithali, Please help by pasting the error in this blog. This should be a very common error.Make sure the Sender EDISeprator channel is configured correctly. Also check the control key association in...
View ArticleRe: EANCOM message : Separate channel per message sub-version
Hi Saurabh, Ideally yes. Subversion would be handy in terms of EANCOM messages. But, I was under the impression that the major version was the same. But if its different as in your case Orders 93 A and...
View ArticleClik here to view.
Re: EANCOM message : Separate channel per message sub-version
Hi Sudarshan, Yes, I agree. For 96A and 93A, I should classify based on main version. And for one of the cases that I have, 96A-EAN008 and 96A-EAN009, i see that there is no difference in both the...
View ArticleRe: EDI Seperator Adapter Issue for Inbound EANCOM Scenario
Hi Dimitri, As per your advice raised another... http://scn.sap.com/thread/3597980 Kindly help me RegardsAmarsrinivas Eli
View ArticleRe: B2B CockPit - Plain to XML Convertor Issue
HI Amar, SAP is coming up with B2B Add On SP4 which will have a dedicated Message editor for Plain messages just like EDIFACT and X12. But you might need to wait for 3-4 months for that. Until then you...
View ArticleRe: B2B CockPit - Plain to XML Convertor Issue
Hi Ruchir,Thanks for immediate response.We are using SP3. In the mean time can you put here parameters to be configured as per above given example?B2B_PLA_CTRL_MSGRegardsAmarsrinivas Eli
View ArticleClik here to view.
TPM : Inbound : Maintenance of multiple messages for same partner
Hello Experts, I am facing one strange issue. I have this below partner maintained already for Message direction = Inbound. But when I try to add one more message ( 93A-EAN007 ) for the same Sender...
View ArticleClik here to view.
Re: EDI Seperator Issue for INbound EDI Scenario
Hi Amar, You always need to make key associations. In that case, the system knows what message enters the system. This is needed for the conversion EDI <-> XML. Kind regards,Dimitri
View Article
