Hi Konrad/Vikas,
Indeed.
The "appendSeqNumToDupSet" at the run time its set false by default.
So it doesnt append the incrementing value.
But this is bit confusing when i look into the the B2BIC.
Thanks for the help!
Regards,
Aarti
↧
Re: ISSUE with Plain to XML conversion while using B2B cockpit integration.
↧
Re: SAP PI B2B Add-On - X.400 to Telekom
I have imported CA certificate in wrong place now it is working fine. even I am bale to connect from two Systems to one Telebox with same user 
↧
↧
Re: B2B-Addon X.400-Sender-Adapter field attachment number?
Hello Christian,
I got the solution to work like described above. The trick was that I had to enter the attachment number 0. My reply to Nidrin was just to try to understand, how the system works in detail. Unfortunately I still don't understand it, but it works :-).
What exactly is your spefici issue?
Best regards,
Joerg
↧
EDI Separator Splitting the Message while using Plain as message protocol
Hi Experts,
I am currently using B2B addon.
And using EDI separator adapter.
My flow is like
Sender system (Plain message)->PI(SFTP)->PI EDI-Separator(Receiver)->PI EDI-SeparatorSender(with message protocol PLAIN)->PI(IDOC_AAE)->R/3(Receiver System)
I have configured this scenario, but the issue coming is EDI Separator Sender is splitting the message and each record is getting splitted.
If you select message protocol as Plain, enter the values for the filter parameters as described in the table below:
| Component | Parameter | Description |
| Filter | Message Type | This parameter allows you to define appropriate plain message type. The adapter without splitting the message dispatches it to the appropriate channel.You can define a parameter using regular expressions in the field. |
But its actually splitting the message 
.
Do i need to set any parameter ?
Thanks in advance!
Regards,
Aarti
↧
Re: B2B-Addon X.400-Sender-Adapter field attachment number?
Hi Jörg,
I have configured a generic polling Adapter with Content-based Sender Determination. This also works for us with attachment no. 0
For each of the table entries I've to build an iflow with an appropriate x.400 Senderchannel inclunding SenderSystem/SenderPartner. My first attemp was to use the EDI Seperator to reduce the configuration objects. Second I try to use SOAP Sender due to less of configuration mandatory.
Nothing of above works. I'm only allowed to use X.400 channels for the Partner and there also have to configure the X.400 box / polling Intervall etc. That's a lot of confusion because the message is already polled.
Perhaps I'm missing something?
I would be glad if you can give me your configuration Details of the whole scenario
Best regards
Christian
↧
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Aarti,
the EDI separator sender channel splits always.
Maybe you change your scenarios to a direct processing, e.g. SFTP->IDoc, or you will convert the plain message and then filter it for the specific scenarios.
However the right solution depends on the process. E.g. if you need to create a single IDoc for every single plain message, then you need a collecting scenario. If not, then you are fine with the direct scenario above.
Kind regards
Konrad
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Konard,
I have been trying to resolve the issue.
Yes, you are right EDI Separator always splits but not in the case of Message protocol as : Plain
I see the actual culprit is generated XSD in B2BIC .
In principle when you have <Header>Repeat in the table , XSD should generate Occurence like :
minOccurs="1" maxOccurs="unbounded,
But its actually generating:
minOccurs="1" maxOccurs="1" ,
I dont know how its Changed ,when i exported the XSD generated i saw maOccurs : "unbounded"
Now i am trying to import the XSD with unbounded occurence. Its not allowing andsaying incorrect file import.
Its pretty strange behaviour or its a bug.
I dont know how to proceed.
Regards,
Aarti
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Aarti,
I usually export the xsd and change the cardinality for using them in the mapping. The plain converter does not check any cardinality. E.g. in Edifact Converter you can easily create messages with multiple UNH segments just by playing with the edifact-xml.
The import function of xsd is not working all the time. I think you need to open an incident. 
Kind regards
Konrad
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Same as you both are facing.
I open XSD with some editor and change the occurence to unbounded.
And the import xsd doesn't work many a times and says it is an invalid file. I am not sure about occurrence part but importing xsd is for sure a bug.
Regards,
Vikas
↧
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Konard/vikas,
I would want to to stick with the flow which I mentioned for the uniformity of the PO implementation.
I have an option of collecting the message and then send to IDOC(Solution given by you.. )
But I am still looking for the solution where I have to avoid the extra config.
Because as per the SAP help doc . EDI separator doesnt split the message incase of Plain.
I am not getting much probs when I am using other EDI like ANSI and Edifact but with Plain I am getting handful of issues.. 
Regards,
Aarti
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Vikas,
Do you have some idea to resolve your issue?
Aarti
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Aarti,
It can't be done with EDISeparator channel that is what I can tell you.
We need to find some workaround for this. First of all raise SAP ticket and then work on workaround.
I can tell you one idea if the file will contain multiple plain messages (but all plain messages should be same for eg. you file should have 5 EDI852 plain files but it can't have 1 EDI 852, 1 EDI 856 etc.)
Then in mapping with java map, BPM etc. you have to split them. Other than this I do not see anyway.
You see logically the splitting happens at receiver EDISeparator and the splitted msg gets picked up at respective EDISeparator Channel. SAP has given the receiver channel tabs for EDIFACT, ANSI X12 etc which means already programmed it to identify those messages but no way to identify a Plain message ( a plain converter is like an FCC it can be anything even not an EDI)
Sorry to say no straight solutions.
Regards,
Vikas
↧
Receiver Soap adapter error
Hi All,
I have one sample scenario that is IDOC--to--SOAP. version SAP PO 7.4 Single stack.
Client provided one target url .so i need to test weather we are able to post the data or not.
I config sample test scenario Idoc--to--soap.
here i am facing the error like below
Please give some idea for resolveing that error
Thanks
Kavitha
↧
↧
Re: Receiver Soap adapter error
Please give some suggestions to solve that error.
my scenario is asynchronous only.
↧
Re: Receiver Soap adapter error
Did you try posting the same request message using SOAP UI ?
The error may be due to the request message which you are posting to webservice.
↧
Re: Receiver Soap adapter error
Hi Manoj,
i tried with normal way .i was tigger the IDOC to SOAP(web service).
They didnt give any wsdl for me.they said just test weather we able to place the data or not.
and one more thing i tested the client URL in chrome and IE but i got the message like below.
↧
Re: Receiver Soap adapter error
Kavita,
If possible test it with SOAP UI .
By testing the URL in browser you can check only connectivity .
But the error which you are getting is not due to connectivity is is may be due to wrong format of data which you are sending to web service.
So SOAP UI would be more helpful here to analyze further.
Br,
Manoj
↧
↧
Re: Receiver Soap adapter error
I am new to soap UI tool.can you plz guide me how to test using client url
↧
Re: Receiver Soap adapter error
You can check this link on how to test webservice with soap UI :
https://www.soapui.org/SOAP-and-WSDL/getting-started.html
Alternatively you can try these blog to test :
↧
Re: EDI Separator Splitting the Message while using Plain as message protocol
Hi Vikas,
Thank you very much for analyzing the issue so closely.
And yes I do have to raise ticket to SAP because ideally there should not be splitting in case of plain.
Meanwhile, with lots of trial and error method I come up with the workaround:
Receiver-EDI _Separator- Enable Default- (Send message AS_IS)
Sender-EDI_Separator- Select Default message protocol
- Add the Converter module in the module (“localejbs/PlainConverterModule)
- Configure B2BIC for the ETOX(Plain to XML)
EDI-Receiver looks which channel is configured with default and then B2BIC looks which Message type is alike the emessage structure.
Regards,
Aarti
↧