Hi mimranacc,
Try giving the module parameters as below.
Module Name                    Module Type               Module key
localejbs/SeeClassifier               Local Enterprise Bean          Classifier
localejbs/CallBicXIRaBean                               Local Enterprise Bean          bic
localejbs/Seeburger/MessageSplitter                         Local Enterprise Bean          split
Module Key     Parameter Name               Parameter Value
Classifier     attID                    additionalInfo
Classifier     classifierMappingID                               See
Classifer     destSourceMsg               MainDocument
Classifier     showInAuditLog               true
bic          classifierAttID          additionalInfo
bic          classifierMappingID          additionalInfo
bic          destSourceMSg          MainDocument
bic          destTargetMsg          MainDocument
bic          mappingName          AUTO
bic          split               true
Regards,
Hari.

Similar Messages

What is difference bettwen Seeburger BIC and Seeburger BIS

Hi All,
What is difference bettwen Seeburger BIC and Seeburger BIS.
I know BIC is Business Integration Converter(BIC).What is Seeburger BIS?
Regards,
Srini

Hi,
      Srinivas...BIS (Business Integration Server) is also a kind of integration platform which mainy focuses on B2B kind of integration.Its an EDI subsystem generally deal with EDI formats like ANSI,EDIFACT ,ODETTE and many.Jus like an inbuilt graphical mapping designer we have in XI/PI.SEEBURGER BIS do comes with inbuilt mapping designer (In EDI envionment we all it EDI translator) for mapping purpouse and its called (BIC) Business integration Converter.
   XI like any other requires Format conversion utilities called 'Adapters'.SAP instead of developing their own adapters .Relies on third party developed adapters(SEEBURGER,iWAY..etc.).
Especially for Mapping between EDI to XML or XML to EDI .SAP leverages BIC Adapters(ex.,AS2 Adapter) developed by SEEBUGER for B2B integration part of it.
   If you want to kow more on EDI mapping in XI lots many blogs are there in SDN it self.All the very best and go ahead.
Thanks,
Ram.

Conversion in Seeburger BIC and XI

Hi,
We receive e-mails with an EDIFACT messages (ORDERS or DELFOR) as an attachment. The e-mails are received in the same INBOX on an e-mail server.
I configured a sender mail adapter in XI and added the PAYLOADSWAPBEAN to put the e-mail attachment into a SOAP attachment (see also /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step)
Now I need to convert the EDIFACT message to XML EDIFACT using a standard 1:1 mapping of Seeburger. I have to determine dynamically what message has to be used (for ORDERS or DELFOR)
How can I establish this?
I tried to use the classifier and BIC modules of Seeburger but I did not succeed.
Ron

Hi all,
when receiving files and you have no idea what file it is, you usually use 3 Modules of the Adapter-Set:
1. SeeClassifier
- determines the file type (e.g. EDIFACT,ANSI...)
2. BIC
- can be set to "Auto"-Mode, which means depending on the information from the Classifier, it executes a "MainMapping" which takes a look at the Header-Fields of this type (for example if it is an Edifact-File it looks at the UNH-Information...and then dynamically creates the name of the real 1:1-Mapping that needs to be executed)
So this means, if you receive a Edifact-File with several UNH within a UNB, it can even be a combination of DELFOR; ORDERS, INNOIV or whatever... each UNH-Loop will be translated seperately with the correct Mapping.
3. Split-Module
This allows you to have a seperate attachment for each UNH-Part (for Edifact). A new SenderChannel can also be created depending on the UNB Sender-Information.
Hope this clarifies the Modules a little bit. If you receive for example lots of different files from different partners via a VAN like IBM or GXS, you probably have no other possibility than use these 3 Modules together to separate all these messages by type and partner and be able to process them correct in the XI.
Regards
Stefan

Classifier, BIC and MessageSplitter with Seeburger

Hi,
Anybody have a example to use the Classifier, BIC and MessageSplitter from Seebubrger with SAP XI comminication channel?. I try with the example scenario from documentation Seeburger, but the
classifierMappingID it does not recognize the map and the value is NULL, and the process of the MessageSplitter don´t work.
Any idea from this error?.
Greetings,
Hervey P.

HI,
Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Regards
Chilla..

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

2 file to file scenarios and one sender channel

hello there,
i am implementing 2 file to file scenarios. referring to the below link i have 'by-pass' integration repository in order to perform my file to file transfer since both the input and output files have the same structure, hence no mapping is required.
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417500%29ID0036662950DB01052533299951691312End?blog=/pub/wlg/4383 --> How to send any data (even binary) through XI, without using the Integration Repository
as seen in the link provided above, it is mentioned to provide a 'dummy' interface and namespace as no such things were created in the IR.
Now i have a second development which perform the same task(file 2 file) however the naming and source/target directory for the second one differs fromt eh first.
that is for the first one the source directory is srcroot/folder1/ and for the secon one is srcroot/folder2
the target for the first scenario is trtroot/folder1 and second is trtroot/folder2.
i wanted to use the same sender channel, making use of the advanced features to pick the files from the different directories, however the scenario always put my files, even those from srcroot/folder2, in the first target folder that is in trtroot/folder1 instead of trtroot/folder2.
one easy way of doing this, is to create channels for each scenario, but if possible i want to use one sender channels for both, is that possible for my scenarios?
can anyone please advise me?
if there is a better way, you are welcome to share it with me.
thank in advance.

Hi,
You can pick the data using same sender channel.
But there are two ways of putting the files to their corresponding destinatios:
1)Using 'Adapter Specific Message Attribute' in communication channel.
But for this to work you have write UDF in your mapping, but as you are not using IR part, this approach can't be used.
2) Another way is, you can use variable substitution method, where the values of the target directory is populated by payload of the incoming file.
If this is not possible, then there is no way but to define 2 diffrent communication channels for receiver.
-Supriya.

JDBC and FTP sender channels stop polling

Hi,
We have a great volume of sender JDBC and FTP sender channels.
For this reason there is nothing unusual to have temporary error connections.
Several months ago, with an XI 3.0 system, sender channels recover its functionality automatically when temporary error connection is solved.
But now, he have migrate to a PI 7.1 sytem, and in the same scenario and configuration, sender channel stop polling after a temporary error . In cc monitor this channels remains in green status and there were no signs of stopped interfaces.
Timeouts are correctly defined and there is no difference between channel configuration in our Xi and PI system.
How to solve this problem?
Thanks, in advance.
Carme.

Thanks for your fast response, Stefan.
After writing this post, i ask the same question to our basis team and we are in the latest sp.
¿do you know if there is any note or can you provide me some additional information?
I'm not able to find any note about this issue...
Regards,
Carme.

Sender and receiver channel parameters

Hi Experts,
I am working on a flat file to flat file scnario. I need to remove the first two lines and last two lines from the flat file and send it to ECC via PI
The flat file looks like this
%802 750285 7502857 7502
%JHKJ UYOU 99 9090
dfafds 2255425 4545 sdfs fsdfsdf dsffs fsfda sfsf
rewre ewrewr wetwt wtwtw
%iuoi iuipo
%7878 8787
so i need to remove the first two lines (starts with % symbol) and last two lines (starts with % symbol) and convert back to flat file and send it to ECC.
I have created the data types as
Source Data type
DT_Source
Header 1..1
Header1
Header2
Recordset 1.. Unbounded
Record 1.1
Trailer 1...1
Trailer1
Trailer2
Target Data type
DT_Target
Recordset 1.. unbounded
Record 1.1
Could you plz let me know the sender and receiver channel parameters
Regards,
Vai

Hi Vaigai,
Grzegorz is right.
You can read all the flat file and remove the first two and last two lines using a mapping.
Check this link. There are some content conversion parameters in the sender file adapter that can be helpful
[http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm]
Regards,
Diego Estanguini Gabriel

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

Why Can't see RFC Sender communicaiton channels and Sender Agreenment

Why Can't see RFC Sender communicaiton channels and Sender Agreenment,
but other type communicaiton channels is ok.

hi
If the sender is R/3 then it has connection directly through RFCs .
XI system can understand HTTP procal directly without any communication channel.
It is the same case for both sender R/3 RFCand IDOC adapters.
more over u can registered to IMPORTS permitted for RFCs and IDOCs while creating the name space as WEB AS ABAP.
regards
sreeni

Seeburger BIC Mapping deployment issue in PI 7.1

Hi experts
We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to a compatible version.(2.x).
Mappings_user.sda was used in 3.0 environment.
But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
Is there any way to convert .sda to .sca and deploy?
Or how can we generate a compatible deployment file for 7.1?
I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
Thanks in advanceDhanish Joseph

Hi
I have installed BICMD 632 version and imported .BICMD project file.
Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
Then installed this in PI system using JSPM.
I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
When i send data to PI data comes to channel and it shows conversion error. But detailed information not available.
In seeburger monitoring the message goes to recovery mode.
I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
I faced some issues>>>
1. while importing project file into BIC MD it asked for apply some autocorrection for one map.(different than this). I have clicked on cancel
2. When i assigned SDA number to my project i have selected 2.1.0 SDA version( 1.8.0 option was also there).
Your prompt reply is greatly appreciated .
Thanks

Seeburger BIC module not working

I am using Seeburger BIC module in my sender file adapter. But when I pick up an EDI file using this file adapter, the BIC module is not called. The file adapter simply passes the EDI file to Integration Engine without passing it through the BIC module. Hence, message mapping fails at Integrating Engine as the Message is not in XML form. Also I am not getting any error in adapter monitoring/Message monitoring saying that the adapter module does not exist.
The BIC module is deployed on XI server. I have activated my communication channel. I have put the module names correctly and in proper sequence and also there are no typo errors in entering the parameter names.
Please help.
Regards,
Shweta

R u passing the correct mapping name under the parameter value in module configuration?
Regards,
Anoop

Chain interfaces to set file name in sender channel dynamically

Hi,
I have a requirement to use the Seeburger SFTP adapter to import a file from an external server to an SAP ECC system.
The adapter must be Seeburger as the protocol has to be SFTP, not FTPS as with the File adapter.
Although I can set a wildcard selection, I really want to poll for specific filenames with predetermined naming criteria.
The sender SFTP communication channel doesn't provide any options to specify dynamic attributes but I wonder if I can link several interfaces together, please can you confirm if the following process would work conceptually:
1) SAP ECC program runs and determines the fixed filename that I wish to import (e.g. file_abc123.xml).
2) SAP ECC program calls an outbound proxy with a mapping to set the relevant parameter in dynamic configuration ('http://seeburger.com/xi' is the namepsace, 'dtSubject' is the parameter name for the filename of the SFTP adapter). Besides mapping I think the Seeburger attribute mapper module could also be used to set this value.
3) The outbound proxy is configured on the receiver side to call an SFTP sender channel (with a dummy/blank payload as we're only calling the interface to allow settng of the filename to take place) which links to an inbound service interface on the SAP ECC receiver side.
I don't know whether chaining of service interfaces in this fashion (receiving interface also being a sender) is a viable approach or whether there are any alternatives.
Thanks in advance,
Alan

Hi Alan,
Are the specific file names that you are polling for going to be changing or will they be fixed? Are each of the unique names going to be processed using the same interface? If so then I would just create multiple SFTP sender channels that poll at different intervals but use the same mappings, etc.
Regards,
Ryan Crosby

Seeburger AS2/EDI sender configuration details

Hello All,
I am working in EDI interface for ANSI X12 using Seeburger AS2/EDI , As I am new to B2B interface I have one doubt regarding Transaction set identifier code,interchange sender and receiver ID , In case of B2B add on it is clearly configured on EDISeparator Sender Adapter under filter
but in case of Seeburger AS2/EDI I am not understanding where we can add this details ,
Thanking you
Sridhar

Hello Sridhar,
for incoming data, the Seeburger BIC-Adapter uses a mapping in the Module-Chain which automatically detects the following parameters
- MessageType and Version (e.g. ANSIX12_850_V4010) from ST segment
- Interchange Sender ID (from ISA segment)
And the MessageSplitter then allows to forward each combination to a specific SenderAgreement for processing the data in PI.
This example shows an entry in the "MessageSplitter" that assigns an 850 V4010 message from a partner with the Sender ID 11111111111 to a specific SenderAgreement to process the data...
Kind Regards
Stefan

SAP GTS------- SAPPI with Seeburger BIC----- ATLAS using with SAP PI

Hi All,
I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
Regards,
Ramesh

>
Ramesh Gulipalli wrote:
> Hi All,
>
> I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
>
> 1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
> 2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
>
> How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
>
> Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
>
> For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
>
> Regards,
> Ramesh
> .
for converting an XML to EDI or vice versa you can use the seeburger adapter.
http://www.seeburger.com/xi-pi-adapters/

Seeburger BIC and Sender Channel

Similar Messages

Maybe you are looking for