Default Mapping Program name in SEEBURGER Adapter

Hi all,
Can any one help me with the default Mapping Program names supplied by SEEBURGER for EDIFACT D96a---->XML and Vice versa.
your help will be appreciated.
Thanks
Gopi

Hello Gopi,
It is as follows (I am assuming your EDIFACT message is:
ORDERS_UN_D96A)
E2X - See_E2X_ORDERS_UN_D96A
X2E- See_X2E_ORDERS_UN_D96A
Thanks
Abinash

Similar Messages

Setting Google Maps as default Map program

I am using Torch 9810 Ssw V7.0.0 build 2404 on ATT. I have installed Google Maps and it seems to be working fine. Of course the Torch also came with ATT Maps and Blackberry Maps. How to I set up Google Maps as the default map program so that when I click addresses in the address book, on the web, or in email Google Maps is opened rather than Blackberry Maps.
I have searched all of the set up options on the Torch, withing Blackberry Maps and within Google Maps but can not find the this possibility.
Thanks,
Paul

You don't, only Apple can do such. However, Google's SDK for their Maps app permits developers of other apps to use Google Maps. Obviously will take time for that to happen.

Default mapping program on the iphone

Is there a way to change the default mapping app on the iPhone away from the new apple maps and to another program?

Thanks I thought as much, but was hoping that someone had figured out otherwise. Nuts, I had an email the other day with an address in it, clicked it, and it took me to the wrong address in their stupid map. And here I am thinking it's a "smart" phone, phhhhhbbbbbtttt.

Seeburger Adapter details

Hi All
What are the things that are to be kept in mind for choosing the Seeburger adapters.
For a logistics based EDIs we are planning to go for Seeburger adapters in XI, i need to know the following things that will help me to contact the seeburger guys for pricing.
1. what are the seeburger components we need to develop the interfaces,(The softwares comes with what all adapters)
2. Does any trial version is available for download?
3. What are the things that will differ from a normal interface development when we use the Seeburger adapters(any1)
steps in IR and ID.
is there any Document from SAP which gives overall picutres the things to be taken care when taking seebuger in XI?
regards
Nisar Khan

Hi Nisar,
1. what are the seeburger components we need
to develop the interfaces,(The softwares comes
with what all adapters)
2. Does any trial version is available for
download?
No trial version available.
3. What are the things that will differ from a
normal interface development when we use the
Seeburger adapters(any1)
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
4) from the followingt types of adapters:
1)BIC Adapter:
There is no BIC adapter it is the client based tool provided by seeburger which has the standard mapping program which does the conversion of EDI-XML and XML-EDI it supports many data types like INHOUSE,CSV, TRADACOM etc. So the std mappinf provided by seeburger has to be deploye first on XI and then used in adapter module tab for conversion.
Using BIC we can create our own data strucutre like we do in IR,we can create our own data type mapping program.
There are three mapping program which is provided by seeburger which is used for creating our own mapping program.
1) Create XML message
2) CreateMappingXML to EDI
3) CreateMappingEDI to XML.
You need to use this mapping program and create your own mapping program for your own structure once it is created import it in BIC.
2)Split997 adapter
The SEEBURGER message splitter module initiates new XI messages as children of a main (or parent) XI Message. A new child (or split) message will be created for each main messages attachment in the split list.
Example of when to use splitter:
1) mail adapter initiates a XI message which contains several attachments, you can use the message splitter to create a new XI Message for each attachment in the original email.
2) U have many UNH messages in one EDI file and u want to create different IDOC for every UNH message for that file that time splitter can be sued.
3)AS2 adapter.
I have provided u the details.
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
I hope I have given u better picture.
Thnx
Chirag

Seeburger Adapter

Hi all,
I have installed a generic seeburger FTP adapter, but I dont have any VAN connectivity at present. Can I convert the EDI ANSI X12 format to xml with this installation or it requires VAN connectivity to do this.
In this case do we require the BIC mapper? if so how to work with BIC mapper?
In the communication channel, I am able to see the installed Seeburger FTP adapter but it does not show the transport and message protocol. Is this related to the Installation/setup of VAN connection.
Regards,
Nithiyanandam

Hello..
SeeBurger is a leading provider of global business integration solutions.
Market launch of the most successful EDI solution for the automotive industry in 1986.
the company today serves more than 7,000 customers in 42 countries and more than 15 industries through its flagship B2B Gateway and related products and services.
First company worldwide to receive certification for SAP R/3
Building a closer partnership with SAP.
Extended any-to-any-conversion.
The SEEBURGER Business Integration Converter (BIC) is an Any-To-Any Format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex,high performance XML-to-XML mappings or to interface to existing JDBC Data Sources.
Supported EDI formats include: ANSI, EDIFACT, INHOUSE, IDOC, XML Schema, XML DTD, CSV,Delimited Data, positional data, SWIFT, EANCOM and many more.
Mapping Designer, a graphical tool, easily defines data format conversions via drag and drop functionality, enabling easy integration between source and destination files. A central mapping reposiu00ADtory enables comprehensive support of versioning and deployment support, such as self-testing and auditing.
The SAP Exchange Infrastructure message format is based on XML, but it also can work with non-XML data using attachments. In some cases it may be necessary to convert the main XML document in a message, into a non-XML document. The use of BIC is very common in Business-to-Business scenarios where EDI standards are in use.
The Business Integration Converter (BIC) of Seeburger is based on Java JIT Technology and can be used for small real-time messages, as well as very large master data (i.e.Catalogs) batches.
BIC can convert outbound invoices from XML format (used in SAP XI) to an EDIFACT invoice. The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, which is the format SAP XI supports.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. BIC will allow you to do the following
Once you install BIC, you need to do Import the Generator Mappings into the Project Explorer of BIC MappingDesigner.
You can find Generator Mappings as a ZIP file in the following location <BICMappingDesignerInstallationDirectory>\user\bicmd\Exchange and select the file prj_GeneratorMappings.zip.bicmd.
In MappingDesigner select File Import Generator Mappings Zip File prj_GeneratorMappings.zip.bicmd Clik on Add and OK.
Once Import is done you can see Generator Mappings in BIC Mapping Designer.
The SEEBURGER Adapter runs on the SAP WEB AS (J2EE Engine)
The SEEBURGER Adapter is integrated into the SAP Exchange Infrastructure over JCA (Java Connector Architecture)
Consequence :
Supply of the complete SEEBURGER EDI/B-to-B-Technology-Suite within SAP NetWeaver
Central File of Business Content (mappings, integration processes) in the Integration Repository of SAP XI
Central configuration and design by using the Tools of XI in the configuration
Central monitoring and alerting over SAP XI
Seeburger Solutions Overview
BIC Mapping Module
Functional Acknowledgement Solution
Operational Dashboard / Archiving
Invoice Solutions
Communication
The Business Integration Converter (BIC) from SEEBURGER is a converter for the implementation of data formats.
Following formats are available:
ANSI X.12 (American National Standards Institute)
CSV (Comma Separated Variable formats)
EDIFACT (all subsets)
INHOUSE (VDA, flatfiles, e. g. SAP IDoc)
SWIFT (banks)
TRADACOM (Trading Data Communications Standard)
XML (DTDs and SCHEMATA)
Able to classify messages into the following message types:
XML
EDIFACT
Ansi X 12
Tradacom
VDA
IDOC
Swift
Inhouse
XML Ansi X 12
XML EDIFACT
XML Tradacom
XML VDA
XML IDOC
Go through this links..
Some more..
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
Reward Points if it is really useful to you.....
Thanks,
Satya Kumar..

Bsi mapping in seeburger adapter

hi experts,
i want to know about bic mapping in idoc to edi scenarios in which i am using seeburger adapter.please help me and provide me some documentation.

Hi,
BIC is mapping tool which converts EDIFACT to EDI_XML.
You will be accepting EDI flat file i.e. csv file and using BIC you will map it 1:1 mapping ....this flat file will be converted into EDI_XML after mapping.
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/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
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://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Regards,
Akshay Jamgaonkar.
Don't forget to reward points.
Message was edited by:
Akshay Jamgaonkar

Sender / Receiver ID mapping for EDI interfaces and Type of seeburger adapt

We need to set up a interface using Seeburger adapter for Purchase order IDOC to 850 EDI mapping.. After reading from SDN,
1) We can use the standard mapping in BIC MD to do E2X and X2E mapping..
2) We can use any of the AS2, EDI generic adapter, Seeburger FTP adapter or Seeburger SFTP adapter...
How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security...
Also how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID
Also the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping.

Hi Kris,
I had worked in the somehow same scenario, It was IDOC to EDIFACT file.
I can give you few clues which might be helpful
In BIC MD you have to create your own mapping if the standard mapping is not available (First check all the standard mappings in BIC). For your reference you need X2E mapping, as your scenario is IDOC to 850 EDI.
"the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping."
In graphical mapping i created my own mapping, Seeburger has given some sample mappings you can check those for your reference (SEEBURGER_GENERIC_EDI software component). Mostly you have to create your own. You need a document from your functional consultant so that you are able to map correct fields and constants.
"how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID"
This has been generally hardcoded in message mapping (In my case i hardcoded). If any of ur IDOC field contains that data you can map that field. But better Idea is ask your functional expert.
"How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security... "
You can choose adapter according to your requirement. In my case i used File adapter as i have to create file in PI server only. My suggestion you can use SFTP for seeburger
Hope these points are helpfu for u
Regards,
Shradha

Changing the default logical system names for adaptive RFC models

Hello,
When I create an Adaptive RFC model the dialog that asks me to specify the model name, package, source folder, etc. has default values in the "Default logical system name for model instances" and "... RFC metadata".
I know I can type in another name there but I'd like to change the default name to something that fits our naming conventions. Can I change that? If so, can someone tell me where?
Thanks in advance!
David.

Suresh,
Thank you for your response. However, that is not what I was looking for. Sorry if my post was not clear.
I knew that I could change it AFTER the import. I also know that I can type in something else besides the default DURING the import.
What I am asking is if there is a way to change some configuration setting so that the 'default' that comes up in the drop down DURING the import is something different than what comes 'out-of-the-box' with NWDS.
Hope that clears up what I'm looking for.
David.
Message was edited by:
David Z. Pantich

Extension of SeeBurger inbuilt mapping programs

hey guys
what is the extension for seeburger inbuilt mapping programs as we have .zip or .jar for Java mapping.
my understanding is that when we install seeburger,we get a SWCV which stores all the metadata and the mapping programs,but when i want to import a standard mapping program under imported archives,what should i look for?
thanx
saif

Saif,
Please check out the below forum discussion. I hope it might help you.
Re: Configure Seeburger modules
Best regards,
raj.

Mapping related errors in SOAP Adapter scenario

Hello Friends
I have done this several times and in this particular case I am getting some errors.
Here is the scenario
External --- (SOAP) --- XI -
(RFC) -
SAP TABLE.
Program
I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
However, it is failing with some mapping errors.
Here is the error message I got in SXMB_MONI
Any help will be greatly appreciated.
<Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description>Main XML document</SAP:Description>
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>

Hi Ram,
This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
Thanks,
Bhargav.
Note:Award Points if found useful

File name in file adapter

Hello Guys,
I need to get a message from RFC, map it in a way that I wouldn't need to do any file conversions in file adapter and send it to FTP. How could I set the file name in this case?
PS: the file name cannot be included in payload, while I don't want to do any conversations of that payload...
Many thanks for your answers,
Milan

Hi Milan,
Is your query related to sending the file name from the source xml document to the reciever file adapter. If so this can be achieved.
Pls. do the following.
1. in the mapping program that you are using populate the filename coming from the source into the target in any of the fileds.
2.Sender adapters can write adapter-specific attributes to the message header; these can then be evaluated at configuration time
3. To change the adapter-specific attributes of the message header by using message mappings, you access the required classes of the mapping API by using a mapping runtime constant.
To access the classes DynamicConfiguration and DynamicConfigurationKey by using the mapping runtime constant DYNAMIC_CONFIGURATION, use the method getTransformationParameters() of the container object.
Create an simple user defined function in the mapping and use the following code.
Imports: com.sap.aii.mapping.api.*;
Parameter: String filename
Paramter: String filename;
filename = fileName + ".DAT";
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/File", "FileName");
conf.put(key, filename);
return filename;
You donot need to hard code the value of the filename in the file adapter for your interface.
In SXMB_MONI, when you see the pipeline services you would see that the value of the filename is populated in the message payload.
Thanks
Indranil

Dynamic file name using FTP adapter

I was trying the dynamic filename scenario taking help from Michal's blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2664. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
If I check the 'adapter specific properties' in both sender and receiver file adapter,then in output I am getting the output filename as same as input filename without using the UDF.
When I used the UDF in mapping,it had absolutely no effect. I am not clear what is the use of the UDF. please let me know where to use the UDF and how to use it.
Thanks
Smith

1. In the mapping program that you are using populate the filename coming from the source into the target in any of the fileds.
2.Sender adapters can write adapter-specific attributes to the message header; these can then be evaluated at configuration time.You can get dynamic filename in UDF in msg mapping....just in ID in comm channel select adapter specific attributes -> filename.....then whatever dynamic name you will create in UDF will be the target filename.....
3. To change the adapter-specific attributes of the message header by using message mappings, you access the required classes of the mapping API by using a mapping runtime constant.
To access the classes DynamicConfiguration and DynamicConfigurationKey by using the mapping runtime constant DYNAMIC_CONFIGURATION, use the method getTransformationParameters() of the container object.
You donot need to hard code the value of the filename in the file adapter for your interface.
In SXMB_MONI, when you see the pipeline services you would see that the value of the filename is populated in the message payload.

One mapping program for three diferent enviroments

Hello there,
I have developed a scenario in which an rfc requests a web service trough XI. In the process a BPM is involved together with some XSLT mappings.
 R3->XI->WebService
The Web service request message looks like follows:
<?xml version="1.0" encoding="UTF-8"?>
<cem:Z_ORDER_SEARCH xmlns:cem="http://XXXXXXXX/yyyyyyyyyyyy">
 <messageStructure/>
</cem:Z_ORDER_SEARCH>
Where "http://XXXXXXXX/yyyyyyyyyyyy" Is the web service destination.
Everything works fine, but as I have to manage three different environments for Development, Quality and Production I need three different versions of the XSL mapping since destinations are not the same for Dev, Qlty and Production environments.
I found out that I can get information of the sender using runtime parameters as follows:
<xsl:param name="SenderSystem">
I would like to evaluate this information to determine the target URL destination.
If the sender is the development sender then the URL target is the development destination and so on.
I tried the following code:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:cemDev="http://developmentDestination"
xmlns:cemQlty="http://qualityDestination"
xmlns:cemPrd="http://productionDestination"
xmlns:cem=""
<xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemDev"/>
<xsl:template match="/">
 <cem:mappingProgram/>
</xsl:template>
</xsl:stylesheet>
This works all right, but I cannot insert code to evaluate the destination.
On the other hand, this code is not valid:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:cemDev="http://developmentDestination"
xmlns:cemQlty="http://qualityDestination"
xmlns:cemPrd="http://productionDestination"
xmlns:cem="">
<xsl:param name="SenderSystem"/>
 <xsl:choose>
 <xsl:when test="string($SenderSystem) = 'PRODUCTION'">
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemPrd"/>
 </xsl:when>
 <xsl:when test="string($SenderSystem) = 'QUALITY'">
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemQlty"/>
 </xsl:when>
 <xsl:otherwise>
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemDev"/>
 </xsl:otherwise>
 </xsl:choose>
 <xsl:template match="/">
 <cem:mappingProgram/>
 </xsl:template>
</xsl:stylesheet>
Neither this one:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:cemDev="http://developmentDestination"
xmlns:cemQlty="http://qualityDestination"
xmlns:cemPrd="http://productionDestination"
xmlns:cem="">
 <xsl:param name="SenderSystem"/>
 <xsl:template match="/">
 <xsl:choose>
 <xsl:when test="string($SenderSystem) = 'PRODUCTION'">
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemPrd"/>
 </xsl:when>
 <xsl:when test="string($SenderSystem) = 'QUALITY'">
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemQlty"/>
 </xsl:when>
 <xsl:otherwise>
 <xsl:namespace-alias stylesheet-prefix="cem" result-prefix="cemDev"/>
 </xsl:otherwise>
 </xsl:choose>
 <cem:mappingProgram/>
 </xsl:template>
</xsl:stylesheet>
I tried this other code, which is obviously not valid:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <xsl:param name="SenderSystem"/>
 <xsl:choose>
 <xsl:when test="string($SenderSystem) = 'PRODUCTION'">
 <cem:Z_ORDER_SEARCH xmlns:cem="http://productionDestination">
 </xsl:when>
 <xsl:when test="string($SenderSystem) = 'QUALITY'">
 <cem:Z_ORDER_SEARCH xmlns:cem="http://qualityDestination">
 </xsl:when>
 <xsl:otherwise>
 <cem:Z_ORDER_SEARCH xmlns:cem="http://developmentDestination">
 </xsl:otherwise>
 </xsl:choose>
 <cem:mappingProgram/>
</cem:Z_ORDER_SEARCH>
 </xsl:template>
</xsl:stylesheet>
So the only way I found to make it works is like this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <xsl:param name="SenderSystem"/>
 <xsl:choose>
 <xsl:when test="string($SenderSystem) = 'PRODUCTION'">
 <cem:Z_ORDER_SEARCH xmlns:cem="http://productionDestination">
 <cem:mappingProgram/>
 </cem:Z_ORDER_SEARCH>
 </xsl:when>
 <xsl:when test="string($SenderSystem) = 'QUALITY'">
 <cem:Z_ORDER_SEARCH xmlns:cem="http://qualityDestination">
 <cem:mappingProgram/>
 </cem:Z_ORDER_SEARCH>
 </xsl:when>
 <xsl:otherwise>
 <cem:Z_ORDER_SEARCH xmlns:cem="http://developmentDestination">
 <cem:mappingProgram/>
 </cem:Z_ORDER_SEARCH>
 </xsl:otherwise>
 </xsl:choose>
 </xsl:template>
</xsl:stylesheet>
Unfortunately this doesnt solve my problem, because I need to reproduce the mapping program three times in the document.
Any ideas, or suggestions how to manage one mapping program for the three different environments?
Thanks a lot in advance, Raú

Hi there,
I just found one way of getting this done. It may not be the better waw, but I post it in case it is helpfull.
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 
 <xsl:param name="senderSystem"/>
 
 <xsl:variable name="qualitySenderSystem" select="'WHATEVERTHENAMEOFTHEQUALITYSENDERSYSTEM'"/>
 <xsl:variable name="productionSenderSystem" select="'WHATEVERTHENAMEOFTHEPRODUCTIONSENDERSYSTEM'"/>
 
 <xsl:template name="mappingProgram" match="/">
 
 <UNIQUE_MAPPING_PROGRAM/>
 
 </xsl:template>
 <!Receiver determination depending on senderSystem>
 <xsl:template match="/">
 <xsl:choose>
 <xsl:when test="$senderSystem=$productionSenderSystem">
 <xxx:Z_ORDER_SEARCH xmlns:xxx="http://production">
 <xsl:call-template name="mappingProgram"/>
 </xxx:Z_ORDER_SEARCH>
 </xsl:when>
 <xsl:when test="$senderSystem=$qualitySenderSystem">
 <xxx:Z_ORDER_SEARCH xmlns:xxx="http://quality">
 <xsl:call-template name="mappingProgram"/>
 </xxx:Z_ORDER_SEARCH>
 </xsl:when>
 <xsl:otherwise>
 <xxx:Z_ORDER_SEARCH xmlns:xxx="http://development">
 <xsl:call-template name="mappingProgram"/>
 </xxx:Z_ORDER_SEARCH>
 </xsl:otherwise>
 </xsl:choose>
 </xsl:template>
</xsl:stylesheet>

EDI TRADACOM through Seeburger Adapter into PI

Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
Is there a useful tutorial to have a look at ?

>>Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
Yes
>>Is there a useful tutorial to have a look at ?
Well, there is nothing specific avauilable for TRADACOM. TRADACOM is just a type of format as we have EDIFACT OR X12. You can search for EDIFACT related articles/blogs on SCN (there are many). The only thing you then need is to use TRADACOM related mapping name in BIC module wherever you see EDIFACT mapping name.
One more thing, for using TRADACOM, there is a separate licence where Seeburger provides the TRADACOM related SWC with all the formats. So talk to Seeburger about this as well.
Regards,
Prateek Raj Srivastava

Seeburger Adapter Scenario

Hi Frnds,
I want See Burger ,CIDX Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
Regards,
Raj

Hi Rajshekar,
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
AS2 vs OFTPS:
AS2 & OFTPS
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
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
https://www.sdn.sap.com/irj/sdn/forums
/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
/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
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Regards,
Vinod.

Default Mapping Program name in SEEBURGER Adapter

Similar Messages

Maybe you are looking for