Seeburger Instatllation problem.

Hi All,
I am trying to install Seeburger BIC Mapping designer but it is not getting installed. Ony unistaller is getting installed in system.
Can some one help me out.
Error Log :
Custom Action:            RefreshEnvironment
                          Status: SUCCESSFUL
Modify Text File - Single File:   New File C:\Program Files\SEEBURGER_Mapping_Designer\Bin\bic_mapping_designer.exe
                          Status: ERROR
Thanks a lot for your help and tiime.
Venkat..

Hi Srikanth,
Thanks a lot for your reply. Now its working and installed Seeburger.
I am new to this technology, can you please me help me out with some documents and important links.
Is there any kind of Training available?
Once again thanks and have a great day!!!

Similar Messages

Seeburger BIC problem

Hello experts,
I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
The error is:
- SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
Adapter Framework caught exception: BICMODULE:Adapter call failed. Reason:
- Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error in BICMODULE-module:Adapter call failed. Reason: .
As you can see, the reason is not mentioned.
When I look into the message monitoring, I see the message does not have a payload. On the SOAP ducument is provided with this content:
authorization:Basic UElJU1VTRVI6SUQzaW5zdGFsbA== accept-encoding:gzip
sap-xi-messageid:4BA11A89186666D8E1000000C0A8A310 content-
length:2916349 host:id3-ma-dwh1.mrco.be:51300 user-agent:SAP NetWeaver Application Server (1.0;711) content-
type:multipart/related;boundary=SAP_001E0BFD21001DEF8CBF15AFFC885B07_END;type="text/xml";start="" soapaction:"http://sap.com/xi/XI/Message/30"ApplicationMessageasynchronous4ba11a89-1866-66d8-e100-0000c0a8a3102010-
03-17T19:07:56ZID2CLNT001SteriaVANBC_UTILMDToSteriaVANMDSnapShot_In_AExactlyOnceInformationOffID2CLNT001XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0is.13.id3-ma-dwh1XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0af.id3.id3-ma-dwh1XIRA4ba11a89-1866-66d8-e100-0000c0a8a310MainDocumentApplication
The Seeburger modules used in my receiver adapter:
1. localejbs/CallBicXIRaBean -- BIC
2. localejbs/Seeburger/Zip -- ZIP
The Module Configuration:
BIC - destEncoding - ISO8859_1
BIC - destSourceMsg - MainDocument
BIC - destTargetMsg - MainDocument
BIC - mappingName - X2E_....
BIC - srcEncoding - ISO8859_1
ZIP - mode - zip
ZIP - sourceDest - MainDocument
ZIP - targetDest - MainDocument
ZIP - zipFormat - gzip
Messages fail at random. ABAP mapping and data are ok.
I think there is a problem with capacity or memory or something.
Anyone any idea?
Thanks a lot!
Dimitri

>
Dimitri Sannen wrote:
> Hello experts,
>
> I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
>
> The error is:
>
> - SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
>
> The Seeburger modules used in my receiver adapter:
>
> 1. localejbs/CallBicXIRaBean -- BIC
> 2. localejbs/Seeburger/Zip -- ZIP
>
Dimitri,
The reason that you are getting this error is because you are missing the exit module bean. add this module after the zip module
Processing sequence
3. localejbs/ModuleProcessorExitBean Local Enterprise Bean Exit
Module configuration
exit JNDIName deployedAdapters/SeeXIAS2/Shareable/SeeXIAS2
There is an exit entry missing which actually is used to pass the bic data to PI box.
Regards,
Pavan

PI Seeburger Map Problem

Hi,
Plzz help me on this issue,
I am working on edi to idoc scenarion using seeburger.
I want to map EDI850 to Idoc. In PI Repository I have standard Mappings with version 4010.BUt,
I need Version 4030 Mappings. Where do i get these version mappings.
Can use same version mappings. Plzz help me on this.
Thanks,
Singh.

Hi Seenu/Singh ( Why mutiple names??),
When you say mappings, there are two types of mapping in Seeburger EDI scenarios.
1) EDI2XML, XML2EDI mappings which convert the ED formatI to XML and vice versa.
2) The actual EDIXML data to the IDOCXML data.
The first type of mappings, you should use BIC mapping designer to develop and then deploy in the PI server.
The second mapping, you have to create in your Integration repository(Within PI system).
The External definition that you see is not the one you want.
If you want to map the IDOC to the EDI 850 V4030, then you should do the following.
1) Login into the physical server of the PI system using Remote Desktop (The userid and pwd are not the ones u use for logging into IR or ID. Contact your basis team to get access to the physical server of PI system)
2) Open the file explorer in that system and navigate to a directory by name seeburger. Inder that you have to search for XSD file corresponding to your EDI Document and version.
3) Copy that file and paste it on your desktop.
4) Then open your IR.
5) Right Click on the external definitions node and click on new.
6) Then import the xsd file which is now tehre on your desktop into PI system.
7) Now, create a message mapping under the mappings node.
8) Drag your IDOC structure as the source and External Definition as your target.
9) Then you can do your mapping as per the requirement.
Regards,
Ravi Kanth talagana

See Burger Error in BICMODULE-module:Adapter call failed. Reason: null

Hello All,
Scenario IDOC to File using Seeburger BIC problems in in my receiver adapter when converting from XML to EDI.
Error is:
"Message processing failed. Cause: Error in BICMODULE-module:Adapter call failed. Reason: null"
The Seeburger modules used in my receiver adapter:
1     localejbs/CallBicXIRaBean     Local Enterprise Bean     BIC_MT
2     localejbs/CallBicXIRaBean     Local Enterprise Bean     BIC
3     localejbs/Seeburger/FileStore     Local Enterprise Bean     ARCHIVE_EDI
4     CallSapAdapter     Local Enterprise Bean     0
with following module configurations
BIC     destDelimiter     @http://seeburger.com/xi/bic/destDelimiter
BIC     destSourceMsg     source
BIC     destTargetMsg     MainDocument
BIC     dynamicConfiguration     true
BIC     newLine     true
BIC     useAttribIfSet     true
BIC_MT     PartnerLookup     on
BIC_MT     destSourceMsg     MainDocument
BIC_MT     destTargetMsg     MainDocument1
BIC_MT     mappingName     XML_Generic_ANSI_X12_to_DB_MT_OUT
BIC_MT     saveSourceMsg     source
Can some one tell me why there is an Error and what additional module configurations it requires .
Thank you,

Hi,
If possible go to mapping in BIC designer Tool and execute the same by passing your payload there...
if you encounter any errors then there might be a problem with mapping developed...or can be payload..
Also check the parameter used for destSourceMsg source ...is that the source message which contains the payload ?
HTH
Rajesh

Seeburger AS2 comm channel problem (B2B) - "perhaps AS2ID missing"

Hi guys!
We try to configure B2B scenario using Seeburger AS2, but communication channel monitor returns error:
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 9/25/07 10:05 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321) [9/25/07 10:05 AM]
We're not sure about the scenario configuration and using identifiers (cos' this is probably the problem).
Did someone of u already configured Seeburger AS2?
We have configured in receiver party alternative identifier Seeburger - AS2ID, however, the message sent to target has always agency XI and scheme XIParty. It should be probably Seeburger and AS2ID (the alternative one).
<SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">XXXX</SAP:Party>
<SAP:Service>BS_3RD_XXXXX</SAP:Service>
<SAP:Interface
How to achieve it?
Thanx a lot!
Peter

Hi Anoop!
Yes, we use it on receiver side.
ModuleProcessorExitbean exists, so it should be ok.
What I'm not sure about is the thing with identifiers..
In Party (let's call it X) - Identifiers, we have default agency http://sap.com/xi/XI, scheme XIParty and name X.
What values should be there for Seeburger?
We have Agency: Seeburger, Scheme: AS2ID; Name: X.
Is it correct?
We also received some 9 char long number - probably some ID to adapter(?). Any idea, if it is necessary and where to use it?
Is it necessary to configure identifier seeburger also in Identifiers tab of Receiver communication channel? Or we can leave it empty (both- sender, receiver)?
We use this in B2B scenario, of course: Target system is party, but we use our R/3 as Business System w/o party. Is it ok, or do we laso have to "be" as Party in our configuration scenario?
A lot of questions, but points will be awarded 4 sure
Thanx!
Peter

Seeburger BIC Mapping Designer: Special Character (German Umlaut) Problem

Hi,
i have created a Mapping with Seeburger Mapping Designer (Invoicd96a to XML). I started the test environment, compiled the mapping and converted the Message to XML. I got a syntax error in the destination file so i added the setSourceEncoding("UTF-8") option and i got a working xml file.
My problem is that all special characters, will be displayed as ? So the word "Beträge" will be converted to "Betr?ge".
What i have to di, to fix this problem ?
Thanks in advance
Matthias

hi,
i have to create an Edifact to XML Mapping with the BIC Mapping Designer. After creation i can deploy this mapping to SAP XI and calling it by using it as module in the specified adapter.
My idea is that the mapping should working correct in test enviroment before i deploy to SAP PI.
Perhaps anyone has an idea.
regards
Matthias
P.S.: A few month ago i had a similar problem with the conversion agent and it was just a "secret" checkbox

Problem in SEEBURGE BIC mapping adapter

Hi experts
I am using SEEBURGER MAPPING adapter for file to idoc scenario .I have to convert an input flat file into xml using BIC mapping adapter.The problem is that when i am giving input file to convert into xml ,the conversion is failing with a error that a special character(?) occurs in the begining of file.when we r opening the file then we r not able to see any special character.The file is in UTF16 Little endian encoding. we r unable to find that how the spechial character is coming in the input files and how to debugg it.Plz guide me how to proceed.Is there any function in SEEBURGER to remove special character from the source file?
Regards
Neha

Hi Neha,
Seeburger is providing Modules (Configurable in CC module chain) described in SAPXI_SeeXIModules_en.pdf with additional functionality like Replace String,Start Local Up, Charset Conversion, zip and dynamic Configuration.
So if you have those modules installed you can use Replace String functionality to replace this string.
Regards
Naycho

Seeburger EDI Adapter with terrible performance problems

Hi,
we installed seeburger edi adapter on PI 7.1 and we have terrible performance problems:
We have a mail sender adapter polling a mail account.
Till the message is visible inside integration engine it takes sometimes 1-2 minutes or longer.
We already tuned the j2ee-engine and checked the DB-indexes (there are some OSS Notes) - no success.
We think that the problem is inside the DB-tables of Seeburger an that some indexes are missing (Oracle DB).
Any ideas?
Thanx
regards
Wolfgang Hummel

Hi,
I think in PI 7.1 SAP installed their own Java-VM (compatible with Sun 1.5) - is it true?
Do you have the same performance problems inside the adapter?
The adapter is like a black hole and it take sometimes one hour till you can see a message inside the integration engine (sxmb_moni).
Regards
Wolfgang

Seeburger Interface configuration problem

I am facing some problems in configuring the interfaces in seeburger.
As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.

>
Rohit Kaushal wrote:
> I am facing some problems in configuring the interfaces in seeburger.
> As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
> Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.
Can you provide more details like what you are expecting..
If my understanding is correct you want to implement a mappings in seeburger bic mapping tool for your sceanrio which can take care of conversions right?
if yes provide more details about your scenario
Rajesh

EDI Seeburger problem

Hey,
I'm testing an invoice EDI file which contains 3 invoices. I'm putting the edi file in the ftp but nothing happens. When I check the channel it says this:
Error: com.sap.engine.interfaces.messaging.api.exception.MessagingException: MESSAGESPLITTER:Adapter call failed. Reason: javax.resource.ResourceException: MessageSplitter failed. MESSAGESPLITTER:No configuration found for the source file 7310XXXXXXXXX|See_E2X_INVOIC_UN_D96A|PARTLY_ACCEPTED|1. Please make sure you have configured <Sender>|<MappingName>|<ACCEPTED> in the module configuration or you have used BIC, split is enabled and corresponding splitting configuration is configured in the splitter frontend
The sender IS already setup in Message splitter. I've tried to modify the edi file and it works if it only contains 1 invoice so my best guess is there's some problem with the edifact syntax, but I cant find what it is. What do you think?

Hi Stefan,
you found the solution? I have the same problem and could not find the error.
Fehler:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
MESSAGESPLITTER:Adapter call failed. Reason: javax.resource.ResourceException:
MessageSplitter failed. MESSAGESPLITTER:No configuration found for the source
file 40xxxxxxxxxxxxx|Z_E2X_ORDERS_UN_D93A_2_1|ACCEPTED|1. Please
make sure you have configured
<Sender>|<MappingName>|<ACCEPTED> in the module configuration
or you have used BIC, split is enabled and corresponding splitting configuration
is configured in the splitter frontend.
I checked the splitter configuration twice but the same sender with (customized) mapping and also ACCEPTED is configured.
What does the 1 mean after ACCEPTED?
Does anyone have another hint how to check?
UPDATE / SOLVED : I configured the Seeburger Splitter Configuration on the AAE, but because I have only access
to the filesystem of the Central Adapter Engine I set up the used File Adapter to this and he tried to find the
Splitter Configuration in Seeburger of the PI (CAE).
After configuring it in the other workbench he found it without problem.
regards
Chris

Problem with Seeburger BIC

Hi Guru.
I've a question for you!!
I'm using the Seeburger BIC Mapping Designer but I'va a big problem: I' can't create the deploy file.
I'm try to follow all the documentation that i find in internet but doesn't work...
After the generation of the XML 2 EDI mapping I want to create the deploy file.
After the selection of this function the system shows the following message:
"You can't create a deploy file for this project! There is no SDA/SCA numbers for this project!"
Have you some solution or workaround?
Thanks
Regards Manuel Chiarelli

Hello Manuel
I assume the Seeburger MD is installed on a client system? If yes, you need to start the Mapping Designer in ProjectAdmin mode.
Below is an excerpt from the SAP_BICMD_config_en.pdf. See the section "Start Mapping Designer as ProjectAdmin"
Start Mapping Designer as ProjectAdmin
In order to assign projects to SCAs, you need to modify the bic_mapping_designer.ini. This file is located under <BIC MD Installation path>/Bin/bic_mapping_designer_ini. Open the file with your
favorite text editor and add to following line below the last CmdLineArg <number> line
CmdLnArgX=-ProjectAdmin
Please note the CmdLnArgX prefix must have an ascending numbering where X is representing the number. Save the file and exit. After that restart the MappingDesigner.
Regards
Mark

Outbound Seeburger AS2 setup problem

Hello,
I am trying to setup Seeburger AS2 adapter in the way that I can post documents from our SAP system to the external server that is sitting in the internet. I was following the SAPXI30_AS2Adapter.pdf guide but it is still not working. When I initiate the posting in SAP it goes correctly to XI, XI correctly process the IDOC and maps it to XML document and pass it to AS2 adapter. But here it fails. In adapter monitoring I can see this error message:
Description: AS2 Adapter failure
Details: Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..[8/31/06 9:23 AM]
ConnectionId: null-allianceTestingServer_Party >> PartnerAddressId: allianceTestingServer_Party >> Transferred: 0/0 >> Error type: pre plugin call failed >> Error date: 1157030604769 >> Description: [8/31/06 9:23 AM]
2006/08/31 - 09:28:28:40
Retryable fault in 'Channel:allianceTestingServer_AS2_outbound'.
I think I've setup everything correctly so no idea where can be the problem. It is saying that I probably do not have AS2ID setup but it is either not true or I do not know how to do it.
Any help would be very much appreciated.
Thank you.
Martin
Solved on my own:
I really didn't have sender configuration completed. I've created new Party, configured it as AS2, created AS2ID for it etc. and then forced it as a sender in the Receiver Agreement.

Hi Anoop!
Yes, we use it on receiver side.
ModuleProcessorExitbean exists, so it should be ok.
What I'm not sure about is the thing with identifiers..
In Party (let's call it X) - Identifiers, we have default agency http://sap.com/xi/XI, scheme XIParty and name X.
What values should be there for Seeburger?
We have Agency: Seeburger, Scheme: AS2ID; Name: X.
Is it correct?
We also received some 9 char long number - probably some ID to adapter(?). Any idea, if it is necessary and where to use it?
Is it necessary to configure identifier seeburger also in Identifiers tab of Receiver communication channel? Or we can leave it empty (both- sender, receiver)?
We use this in B2B scenario, of course: Target system is party, but we use our R/3 as Business System w/o party. Is it ok, or do we laso have to "be" as Party in our configuration scenario?
A lot of questions, but points will be awarded 4 sure
Thanx!
Peter

Problems with Seeburger FTP Receiver adapter

Hello,
I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
Hostname <Hostname of our FTP server>
Port <Port # of our FTP server>
Host Path/VAN partner id <some local directory of FTP server>
Payload mode: Maindocument.
At runtime i received following exception
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
Few questions related to this
1] can we use Seeburger adapter to generate EDI files on local FTP server
2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
Any idea how to generate EDI files with Seeburger FTP on test server?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
> 1] can we use Seeburger adapter to generate EDI files on local FTP server
Yes we can use.
> Any idea how to generate EDI files with Seeburger FTP on test server?
It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
BIC
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Regards
Ramesh

Problem with CC Receiver with AS2 Adapter Seeburger

Hi,
I try to test the AS2 Adapter with Receiver channel y one server and Sender channel in second server, but in the Receiver channel, I have the error :
"MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2."
I find the error and I found the URL Error in AS2 adapter. Object not found in lookup of as2.. Its urgent..!! with the same problem, but I have the same configuration in the Party of the receiver and the Sender, the same AS2ID name, and try with the solution in the forum respect the Party name in the scenario of the Receiver, but don't work.
My scenario is send an IDOC from R/3 to a partner with the AS2 receiver channel.
Is my fisrt scenario with AS2 adapter. Somebody help me please with any example or with any idea about the solution to my problem?
Greetings,
Hervey

I have resolved this problem, thanks.

Problem Encountered in JMS adapter using SEEBURGER module

While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
1. The error encountered is :
Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3'; detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
SEEBURGER BICXIADAPTER --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: XML file should begin with white spaces or <. (Found char :U(Hex :85). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
2. The targer PAYMUL xml is as follows :
( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
PAYMUL XML
<?xml version="1.0" encoding="UTF-8" ?>
- <LIST>
- <S_UNA>
<D_DELIMITER>:+.? '</D_DELIMITER>
</S_UNA>
- <S_UNB>
- <C_S001>
<D_0001>UNOA</D_0001>
<D_0002>2</D_0002>
</C_S001>
- <C_S002>
<D_0004>SAPDM</D_0004>
<D_0007>ZZ</D_0007>
</C_S002>
- <C_S003>
<D_0010>000000000000</D_0010>
<D_0007>55</D_0007>
</C_S003>
- <C_S004>
<D_0017>070201</D_0017>
<D_0019>1150</D_0019>
</C_S004>
<D_0020>01945678912345</D_0020>
- <S_UNH>
<D_0062>1</D_0062>
- <C_S009>
<D_0065>PAYMUL</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
<D_0057>FUN01G</D_0057>
</C_S009>
- <S_BGM>
- <C_C002>
<D_1001>452</D_1001>
</C_C002>
<D_1004>01945678912345</D_1004>
<D_1225>9</D_1225>
</S_BGM>
- <S_DTM>
- <C_C507>
<D_2005>137</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <G_SSG4>
- <S_LIN>
<D_1082>1</D_1082>
- <S_DTM>
- <C_C507>
<D_2005>203</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>ACK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>AEK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_BUS>
<D_3279>IR</D_3279>
- <C_C551>
<D_4383>UGI</D_4383>
</C_C551>
</S_BUS>
- <G_SSG5>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
</G_SSG5>
- <G_SSG6>
- <S_FII>
<D_3035>OR</D_3035>
- <C_C078>
<D_3194>ES921998500000000012</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAES17000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG6>
- <G_SSG7>
- <S_NAD>
<D_3035>OY</D_3035>
- <C_C080>
<D_3036>XYZ CORPORATION LTD</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG7>
- <G_SSG11>
- <S_SEQ>
- <C_C286>
<D_1050>1</D_1050>
</C_C286>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
- <S_DTM>
- <C_C507>
<D_2005>227</D_2005>
<D_2380>2007-02-01</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>AIK</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>CR</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_FCA>
<D_4471>13</D_4471>
</S_FCA>
- <G_SSG12>
- <S_FII>
<D_3035>BF</D_3035>
- <C_C078>
<D_3194>AT921998500000000011</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAAT14000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG12>
- <G_SSG13>
- <S_NAD>
<D_3035>BE</D_3035>
- <C_C080>
<D_3036>ABC CORPORATION 1</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG13>
- <G_SSG16>
- <S_PRC>
- <C_C242>
<D_7187>11</D_7187>
</C_C242>
- <S_FTX>
<D_4451>PMD</D_4451>
- <C_C108>
<D_4440>SENDERPN1</D_4440>
</C_C108>
</S_FTX>
</S_PRC>
</G_SSG16>
</S_SEQ>
</G_SSG11>
</S_LIN>
</G_SSG4>
- <S_CNT>
- <C_C270>
<D_6069>2</D_6069>
<D_6066>1</D_6066>
</C_C270>
</S_CNT>
- <S_UNT>
<D_0074>1</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</S_UNH>
- <S_UNZ>
<D_0036>1</D_0036>
<D_0020>01945678912345</D_0020>
</S_UNZ>
</S_UNB>
</LIST>
3. The module parameters for Seeburger inputs :
( In receiver communication channel)
Processing Sequence
localejbs/CallBicXIRaBean Local Ent Bean x2e_bic_paymul
SAP XI JMS Adapter/ConvertMessageToBinary Local Ent Bean convert_XI2Bin
SAP XI JMS Adapter/SendBinarytoXIJMSService Local Ent Bean
 exit
Module Key
x2e_bic_paymul destSourceMsg MainDocument
x2e_bic_paymul destTargetMsg MainDocument
x2e_bic_paymul logAttID ConverterLog
x2e_bic_paymul mappingName See_X2E_PAYMUL_UN_D96A
x2e_bic_paymul newLine true
x2e_bic_paymul saveSourceMsg XMLEDI

Hi,
Check Below links,
/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
Regards,
Phani

Seeburger Instatllation problem.

Similar Messages

Maybe you are looking for