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

Similar Messages

IDOC to EDI Seeburger Mapping Issue

Hi,
I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
As per my little knowledge i can understand that i need two step mapping:
1) IDOC XML to EDI XML
2) EDI XML to EDI
Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
Also i dont know how i can map the 2nd mapping.
when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
msg_PAYEXT_UN_D96A.xml
msg_XML_PAYEXT_UN_D96A.xml
XML_PAYEXT_UN_D96A.xsd
Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
Please experts reply soon as it is delaying my project
Regards,
Shradha

Shradha,
You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
You can have a look whether PAYEXT is there and would be useful
To start with
1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
2. You should also liase with your business partners to prepare an business rules and other conditions.
3.Also decide whether you are going to deliver it via AS2 communication or via VAN
4. Accordingly you need to configure the seeburger adapters.
5.The mappings provided to you are from XML to EDI and EDI to XML which is a second stage automatically done by seeburger once you specify the module steps in the comms channel.
I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
Regards
Krish

EDI seeburger interface

Dear experts,
i have a inbound scenario EDI -> XI -> R3
1. I am thinking of going the BIC mapping way like creating a BIC mappign installing in XI and specifing the mapping name in the module section of the sender file adapter as specified in this blog /people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
2. however when i check in the communication channel and try to select the adapter, i can also see a Seeburger AS2 adapter...
so i am confused ...which option is correct ....
option 1 : to use BIC mapping and mapping name in module section of the sender FILE adpter or
option 2 : to use sender SEEBURGER AS2 adapter..
advance thanks

>
Ravi Mehta wrote:
> Dear experts,
>
> i have a inbound scenario EDI -> XI -> R3
>
> 1. I am thinking of going the BIC mapping way like creating a BIC mappign installing in XI and specifing the mapping name in the module section of the sender file adapter as specified in this blog /people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
>
> 2. however when i check in the communication channel and try to select the adapter, i can also see a Seeburger AS2 adapter...
>
> so i am confused ...which option is correct ....
> option 1 : to use BIC mapping and mapping name in module section of the sender FILE adpter or
> option 2 : to use sender SEEBURGER AS2 adapter..
>
> advance thanks
Note that you will use the Seeburger AS2 adapter only if your transport protocol is AS2.
In case you are just accessing files from a FTP then you dont have to go for the AS2 adapter.
The BIC modules can be attached any where.. it has nothing to with the transmission protocol.
So the choice of the adapter is based on how the transmission protocol is needed.

IDoc to EDI mapping problem (Invoic01 to 810 v4010)

Hi,
I have a problem with my invoice mapping.
I need to exclude children parts from the outbound EDI invoice.
In my mapping I was able to control the number of lines that should go out from the top line item node level using:
G_SIT1 -> If E1EDP02-QUALF = 002 then E1EDP02-ZEILE->Remove Context->SplitByValue->CollapseContext->G_STI1
I have the right amount of lines but the fields under G_STI1 are wrong since I'm missing the last ones.
Then I tried different combinations + playing with the contexts and played again with the top node and my conclusion is that it might be easier to exclude them in IDoc in SAP using an UserExit?!?
Anybody was able to get around this problem without changing the IDoc in R/3?

Can I filter on a partner type KU? I need to customize an outboud invoice to not send some segments.
Or is it only for type LS?
Rgds,
Yves

Many .sda files required,EDI,Seeburger?

hi,
do we need to create .sda files using Seeburger BIC Mapper for each mapping and deploy each <b>.sda</b> file on to XI server using SDM?

Hi Babu,
Let me tell you the step by step process of SDA creation and deployment.
1) Go to BIC Mapping designer tool
2) Create the maps of needed documents(For example if we know that we will be needed EDI 850, 810,855 etc transactions then we need to add E2X(EDI To XML) and X2E (XML to EDI maps in a project
3) Select that project folder
4)Right click on it
5)Create deployment (SDA) file.
6)Default name of the created SDA file is "Mapping_User.sda"
7)Deploy this .sda in to the J2EE side of XI server using SDM.
Now if you anticipate that you have to add some aditional EDI maps for transtions other then the one covered in the earlier SDA file ::
1) Add the new maps in the old project.
2) Create the new SDA file
3) Again name of the created SDA file is "Mapping_User.sda"
4) deploy this new SDA file.
5) It will over write the existing "Mapping_User.sda" .
Hope i have answered your question
Let me know if you need any further clarifications.
regards
Piyush

EDI Seeburger Message Spliter

Hi,
I am testing a EDI ANSI X12 850 Vxxxx using SEEBURGER adapter in SAP PI. It is a simple file to IDOC scenario. I have configured all the ID objects (includng the Split 997 channel). But when i try to configure the Message Splitter in Seeburger workbench, i am not able to access the service and Channel. The buttons are not active. Do i need to do any other setup before trying to do this ?

Hi,
After entering the party and services need to click on the search button of the services to display the channel names...
and similarly for the other objects...(buttons will get activated after clicking on the search...)
HTH
Rajesh

EDI SEEBurger Adapter

We are evaluating XI for ANSI X12 EDI , Have some EDI Quesitions using SEEBurger Adapter.
1) Does SEEBurger Adpater has ANSI X12 Enveloping and De-Enveloping capabilities ??? If Yes,how this is configured /Developed.
2) Does SEEBurger Adapter has capability of generating sequential ISA control numbers by Trading Partner ??? If Yes,how this is configured /Developed.
3) Can It perform EDI Structure validation based on the EDI standard rules (For eg: Looping structures, Element qualifier restriction list .....)

Hi,
Seeburger is a tool which will conver any type of standard EDI format into XML.
All standard EDi mappings are predefined in seburger,we have to install in XI Server and use that standard mappings.
Check this links
SEEBURGER
http://www.seeburger.com
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.pdf
Regards,
Phani
Reward Points if Helpful

EDI - Seeburger: Replace existing VAN FTP connection.

Hi All,
We have running EDI interface in PI using Seeburger adaptor and GXS VAN service provider using FTP channel.
Now one of our Vendors has upgraded to PowerTrack system and hence they can not accept FTP connections.
Instead they are asking us to use SFTP, HTTPS AS2 or webportal upload.
Without disturbing much of our existing setup in PI how can we change the VAN connection? And what is the best suitable way?
I am new to XI so detailed explanation will be much helpful.
Thanks and Regards,
Atul

You'll need to change the adapter you're using in your communication channel. For SFTP and AS2 you'll need a new adapter (like aedaptive for SFTP and AS2 or seeburger for just AS2). HTTPS is supported default by PI.

Conversion Agent - EDI Parser Problem

Hi Experts,
We are writing a parser for EDI message type 850.
When we are giving Repeating Group and Marker "ST", it is taking more fields also, having this value "ST", which are in other Segments other then ST.
and reading that ST fields as a segment,
the output data is not correct due to this problem,
Please help,
Regards,
Study SAP

Hi VJ,
thanks for your reply,
We are writing this Parser at Conversion Agent for EDI 850 & 856, X12 Version 4030.
The example file for the problem is here :
ST/856/00001~
BSN/00/013721/20070806/1808/0001~
HL/1//S~
TD1/CTN25/17////G/198/LB~
TD5//2/HRMN/M/HERMANN TRUCKIN~
REF/BM/67450800000020664~
REF/CN/125173569~
REF/PUA/125173569~
PER/IC/dan/EM/[email protected]~
DTM/011/20070806/1807~
N1/ST//92/93922~
ST is a segment, when we are going to give this as Marker in Repeating Group, it is picking ST of N1 Segment also.
'/' is seperator for fields and '~' is seperator for lines.
Regards,
Study SAP

Seeburger problem for Custom Mappings..!!!

Hi All,
File to Idoc using seeburger adapters(BIc & split)
When I use standard mapping (Which starts with See_.. )in seeburger splitter configuration, ,the scenario is working perfectly.The idoc is posting in R/3 and Funcack is sending to Partner.
But When I do for customised mappings (Like the ones which we will develop in BIC and deploy into XI and we will use the mapping name like E2X_DT_INVOICE).. then its not working.
I tried by keeping custom mappings (E2X_DT_ORDERS) in splitter configuration. But it didnt work.. !!
Can anyone please tell the changes what I need to do in the modules or in splitter configuration..??
Here is the Module parameters which i mentioned in sender File adapter.
localejbs/SeeClassifier            C
localejbs/CallBicXIRaBean   BIC
localejbs/Seeburger/MessageSplitter   S
C         attID                classifierAtt
C         destSourceMsg        MainDocument
C         showInAuditLog       true
BIC       classifierAttID          classifierAtt
BIC       destSourceMsg       MainDocument
BIC       destTargetMsg         MainDocument
BIC       mappingName           AUTO
BIC       split                          true
1. mappingName I kept as AUTO for standard mappings..
I need to change anything here for Custom Mappings???
2. I didnt mention anything here in split adapter in modules.
Did I need to mention anything here when we do for custom mappings??
Kindly let me know anyone has idea on this.
Thanks&Regards
Seema.

You will also have to create this mapping on the BIC site.
check the documentation on the classifier and functional acknowledgements
Seeburger Classifier with customer mappings.
In the manual Functional Acknowledgement For SAP XI3.0, Configuration Guide this is described. I add a description of how I have configured it at another customer
In the Sender Communication Channel the classifier modules are configured (localejbs/SeeClassifier). This module expects some parameters:
Parameter               Value
attID                    ClassifierAtt
classifierMappingID          XXXX (Choose something for XXXX)
destSourcMsg               MainDocument
showInAuditLog          true
The parameter mappingName of module localejbs/Seeburger/CallBicXIRaBean should be set to AUTO otherwise the classifier functionality wont work.
In the BIC Mapping Designer now you have to create a program called Edifact_XXXX (have a look at page 40 of the manual)
I generated a mapping called Edifact_XXXX from the message Edifact_service with the programs CreateXMLMessage, CreateMappingXMLToEdi, CreateMappingEdiToXML.
After this I adjusted the generated program in the UNH segment I added the following rules:
if name$ = "See_E2X_ORDERS_UN_D96B"
   copy "E2X_ORDERS_UN_D96B" to name$;
endif
With this code you change the mapping name that is called in the BIC to convert the EDIFACT message to XML. Or other functionalities.
The mapping that you use here should be the same as configured in the Splitter of the Seeburger FrontEnd
Screen prints:
Configuration of Sender Communication Channel
BIC MD: Generation programs
BIC MD: New generated mapping Edifact_xxxx from message Edifact_Service
BIC MD:Adjustment in mapping program Edifact_XXXX
Seeburger FrontEnd Splitter configuration

EDI Seeburger

Hi All,
Can you please provide me the steps for the XSD Conversions for the Standard Mapping Programs?
Also, can you please tell me the configuration steps for all the Seeburger Adapters?
Thanks in advance.

Hi Shweta,
To generate the X2E and E2X mappings by using BIC tool check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Splitter configuration:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70808338-c4ea-2b10-dcb4-c628756da4fe
Full B2B Scenario:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
Regards
Ramesh

EDI EDI867 problem please help

Hi Alll,
I am new in EDI .
I am not able to understand what is EDI867 .
guyz please guide me this issue is very critical for me .
Thanks & Regards

Hi,
EDI867 is a document standard for EDI:
867 Product Transfer and Resale Report
For more information take a look at this page:
http://www.edibasics.co.uk/edi_resources/ANSI.htm
Regards
Dirk

EDI Fax Problem

Hi All,
The EDI notifications (payment details for electronic payments) being sent by fax are erroring out because mail servers were reconfigured to point to Exchange instead of Domino servers.
The issue is the syntax used for Domino (ie. “Accts_rec@7802222222@fax”@test.com) is not recognized by Exchange.
Does anyone know whether there is any particular syntax to send faxes on Exchange.
Thanks

What is the application release?
The EDI notifications (payment details for electronic payments) being sent by fax are erroring out because mail servers were reconfigured to point to Exchange instead of Domino servers. What is the error?
Thanks,
Hussein

SO via inbound EDI. partner problem LIFNR - PARTN

Hi,
Working on PO -> SO interface. Question on populating VOE4 (EDPAR).
in the inbound IDOC I have this segment:
E1EDKA1:
PARVW: AG
PARTN: external customer number (in my case it is purchasing organisation)
LIFNR: 'blank'
In forums it is told that segment LIFNR should be populated by external customer number.
What is the difference between PARVW and LIFNR? Does VOE4 look at PARTN for substitution?
in my case seems that it ignores PARTN at all..
Thanks,
Artashes

I think what you need is the following.
On the EDIDC record, field SNDPRN, you need to have the Sold To customer number mapped. You'll also need to have the SoldTo setup in WE20 with a partner profile.
You can send in an Order to SAP with a Logical System in the above field but you then have to have the PARTN fields filled in with the correct Sold To Ship To. Which you typically would not have.
On the KA1 segments, you'll need two KA1 segments, one for the Sold To and the Other for the Ship To. Since you already would know the Sold To since you put it in the EDIDC record, just fill it in the PARTN field, unless your partner wants their store number back. Personally I would set it up this way with the external store number.
So you'll want a KA1 record with the AG qualifier for the Sold To and the LIFNR field filled in with the partners external number for the Sold To. This could be the Duns number or N1/04 code.
On the second KA1 for the ship to, set the qualifier to WE for Ship To and then fill in the LIFNR with the external store number.
You'll now need entries in VOE4 for each KA1. Customer would be the same as the Customer in the EDIDC record, field SNDPRN. external function is either SP or SH. External Number is the external number, either the DUNS number for the Sold To (Most likely) or the N1/04 code for the ship to. Int No is the Internal customer number for the Sold To and Ship To.
Sold To 55555
Customer Sender ID/Dunning # 123456789
External Ship To Store # 321
WE20 setup for Sold To 55555
VOE4 setup for 55555    SP    SOLD TO   123456789 55555
VOE4 setup for 55555    SH    SHIP TO     321              55555
I think what SAP Messed up on is the fact that we should not have an external cross reference or hard coding mechanism to populat the SNDPRN with a customer number for inbound transactions in order for the EDPAR table to work correctly. You can have a logical system at the EDIDC level but would need to populate the correct Sold To and Ship To on the KA1 segments. When using the LIFNR fields, SAP Uses the SNDPRN, External Partner Number and Partner Function on the KA1 record to determine the Internal Customer Number.
If anyone else has an opinion please let me know.   I would love a way to be able to cross reference the Dunning Number for a partner to a Sold To within SAP and allow for the LIFNR fields to be used for the Ship To's.

EDI using seeburger

Hi Friends,
Recently I have worked on EDI scenarios using Seeburger adapter.
there are so many in and outs for EDI / Seeburger ,
out of that I need some inputs on finalization of error handling framework for EDI implementation using Seeburger.
Please give your thoughts on error handling in EDI /Seeburger.

Beside my two cents above, your question can't really be answered without defining some business rules around it. So for the sake of discussion i am going to make up a scenario. And the cycle upto Despatch advice.
So business rules are:
1) Over supply not do able. Which implicitly means no manual changes in the incoming ORDER.
2) Under supply allowed as in the real world this will always happen as at the time of ORDER, the supplier side could be out of stock on a particular item ordered.
Message Cycle:
1) Order (Inbound)
2) Order confirmation (Outbound)
3) Dispatch advice (outbound) - DESADV
So briefly speaking based on how the Order confirmation is setup (based on business guidelines) will determine what we are suppose to handle.
If order confirmation is allowed to change the Order i.e. If no stock available and hence line item rejected it would update the original Order in the sending partners system hence no issues at the time of desadv (this is situation one). However if due to some human error more stock shipped than agreed upon in the DESADV then 'excess stock' process can be invoked and based on business rule it can be returned e.g.. This wouldn't require any message amendment. However if short delivered then what was agreed in DESADV partner can always request amends and new DESADV (corrected) can be issued.
I will stop here; I am hoping that i am making sense above? Will continue if i am making sense and then we can talk about technical side for addressing different situations.
regards,

EDI Seeburger problem

Similar Messages

Maybe you are looking for