Seeburger Classifier

Hi,
I am using Seeburger Classifier module.
I have a doubt over there.While doing module configuration,how we are going to decide about the value of parameter classifierAttID .
From where i will get the parameter value for parameter name classifierAttID
Thnanks,
Anoop

HI,
Though I dont have much experience with classifier module but what i know is:
classifierAttID:
This parameter is used to specify an attachment, in which the information about the classification is
attached to the XIMessage.If no attID is set, the defaultname MessageTypeReport will be used.
Paramter name should be classifierAttID and parameter value wil be classifierAtt. that what should be mentioned in AS2.
Thnx
Chirag

Similar Messages

Regarding Seeburger Classifier Module

Dear Expert,
I am using Seeburger EDI Adapter to handle EDI plain file into SAP XI. As I just want to use the Seeburger build-in mappings start with "See_", I did not set the parameter classifierMappingID of Seeburger Classifier Module, but always get the output of Seeburger Functional Acknowlegement. How can I set the parameters to use the build-in mappings like "See_E2X_ANSIX12_810_V4010"?
Any suggestion or idea are appreciated!
Thanks and Regards,
Nick

Hi Nick,
you need to choose if you want to use classifier or predefined mapping name. The purpose of classifier is to classify your message (exp. ANSI 12, EDIFACT etc.) and than to find the mapping specified in Seeburger Message splitter (from http://<XI Host>:<J2EE port>/seeburger/index.html -> Message splitter).
In Message splitter you need to choose you sender agreement from XI, Mapping name and sender number (for ANSIX12 it's the value of ISA06 from inbound ANSI message).
Please check Seeburger manual SAPXI_FunctionalAck_en.pdf.
If you need your communication channel to process only ANSIX12_810_V4010 messages than you don't need classifier and you can hardcoded parameter mapping name "See_E2X_ANSIX12_810_V4010".
Regards
Naycho

Use of Seeburger Classifier withour splitter?

Hello,
Can you please let me know if we can use Seeburger Classifier without splitter?
if this is possible,can you please suggest relevant links which explain such scenario?
Than

Hi Shweta,
It's a little while since I've used Seeburger but I seem to remember the following, which I hope will help you.
Seeburger Classifier creates an attachment by the name of the "attName" parameter you submit to the Classifier module. If you do not submit an "attName" parameter value, the Classifier module will use a default value. You can see the classifier attachment in SXI_MONITOR - it is simply a set of information about what the Classifier determined about the message.
Where the Seeburger mapping module parameter setting is mappingName=AUTO (instead of a static mappingName of the a single mapping, e.g. mappingName=AnsiX12_812_V4030) it will attempt to use the classification xml attachment which was (in the case of where you specify mappingName=AUTO) expected to be have been created earlier in the module chain - again, if no classifierAtt parameter value is specified to provide the name used for the Classifier module's attName (attachment name) then I believe Seeburger mapping module uses the default. I think the default behaviour of Seeburger mapping module when using mappingName=AUTO is also to split by default, and creates the FunctionalAck in place of the whole message.
I believe there are two solutions to your problem (without getting into developing AF modules):
The first, and easiest, way to get Seeburger mapping module to not produce an Ack and to map 1-to-1, is to leave the Classifier module out of the chain and to specify your exact mapping in order for it to perform a 1-to-1 mapping. In order to do this you will need to know what file is coming in on your Sender channel.
The second way is that there is a "split" parameter (true/false - true by default for AUTO), and (if I remember correctly) a splitMode parameter too. The long and short of it here though, is that the ability to support these parameters' usage to enable 1-to-1 mapping on a mappingName=AUTO will be down to your master (e.g. AnsiX12_Company, EDIFACT_Company, TRADACOM_Company) mappings which are used to then branch out to the per-instance mappings which are message name/version specific (e.g. AnsiX12_810_V4010, EDIFACT_ORDHDR_V9). If using these parameters does not automatically get your 1-to-1 mapping working, you may require some consultancy from Seeburger to enable the 1-to-1 mapping for Classifier driven mapping - I seem to remember this not being a very straightforward process.
Kind regards.

Query regarding Seeburger Classifier

Hello,
We have a problem with Russian characters where these are cut by AS2 adapter.
In order to analyze this,I have changed the configuration to use Classifier instead of giving fixed mapping name.
Now,I can see the log as:
2009-09-17T09:58:27.144+0200 INFO starting conversion Edifact_XXX (id : 7281816071253174307119 ) at Thu Sep 17 09:58:27 CEST 2009
2009-09-17T09:58:27.172+0200 INFO starting conversion See_E2X_ORDERS_UN_D96A (id : 14608852671253174307172 ) at Thu Sep 17 09:58:27 CEST 2009
2009-09-17T09:58:27.664+0200 INFO Child Dest   Encoding : UTF-8
2009-09-17T09:58:27.664+0200 INFO Child Source Encoding :
2009-09-17T09:44:56.541+0200 INFO Child XML Encoding :
Problem still persists.
Child Source Encoding and Child XML Encoding are always blank in the log.
I have tried setting source encoding using BIC module ,CharsetConversion module, and setSourceEncodingFromClassifier module.
Still ,I cant see any value in thes fields in the log.
Can anybody please let me know how can I populate these values.
I suspect that the problem with special characters is because of incorrect source encoding.
Thanks.
Regards,
Shweta

This is some mapping code (as used in the SEEBURGER standard mappings) from the NewMapping program, which passes the encoding input parameters to the child mappings.
// Source Encoding
copy getInputValue("srcEncoding")        to srcEncoding$;
setInputValue("getChildSourceEncoding", srcEncoding$);
// Destination Encoding
copy getInputValue("destEncoding")       to destEncoding$;
setInputValue("getChildDestEncoding", destEncoding$);
In the child mapping we read the passed parameters and set the values (the if in the beginning results from a different handling for split messages):
copy getInputValue("SplittingMode") to splittingMode$;
copy splittingMode$ to Split%;
if Split% = 1
   modifyWarningLevel(2150,4);
   stopReadingOnError("off");
   copy getInputValue("getChildDestEncoding") to ChildDestEncoding$;
   if ChildDestEncoding$ != ""
      #javastart
      m_stdout.setEncoding(_StrVar_CHILDDESTENCODING.getString());
      #javaend
   else
      ChildDestEncoding$ = "UTF-8";
      #javastart
      m_stdout.setEncoding("UTF-8");
      #javaend
   endif
   traceln("Child Dest   Encoding : " & ChildDestEncoding$);
endif
// Getting Source Encoding Paramteter
copy getInputValue("getChildSourceEncoding") to ChildSrcEncoding$;
if ChildSrcEncoding$ != ""
    #javastart
    m_stdin.setEncoding(_StrVar_CHILDSRCENCODING.getString());
    #javaend
endif
traceln("Child Source Encoding : " & ChildSrcEncoding$);
// Getting XML Encoding Parameter
copy getInputValue("setXMLEncoding") to ChildXMLEncoding$;
if ChildXMLEncoding$ != ""
    #javastart
    m_stdout.setXMLEncoding(_StrVar_CHILDXMLENCODING.getString());
    #javaend
endif
I hope this helps, you may have a look at the standard mappings shipped by SEEBURGER in addition where this functionality is included !

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

Seeburger Splitter adapter!!

hi,
what is Seeburger splitter adapter ?how does it function?
can configure splitter adapter as a module like BIC adapter and Module?
thank you,
babu

Hi Babu,
The splitter is configured with the Functional Acknowledment in Seeburger, this component works in combination with the Seeburger Classifier. For example:
1. You receive a document EDI with the Classifier in a communication channel and this execute the map with the document type sand the version number.
2. The Functional Ack. is generate from the result of the conversion in the map.
3. You have other communication channel configured with the Splitter in a mode Sender.
4. With this, you can map the Functional Ack of Seeburger to a document 997.
5. You have other communication channel with a Receiver mode, to send the result of the mapping process to a SAP or any destination.
This funcionality works with the XI FTP adapter(File), with the FTP Adapter or any other Adapter to receive a document EDI.
You need deploy the 997SplitterMetadata.xml from installation CD with Integration Design and loaded as Adapter Metadata.
To use the splitter, you need configure in the communication channel in the module chain, the BIC and the classifier, in the bic parameters, you define the splitter with true value.
For a example to this component, you can use the Functional Acknowledgement documentation from Seeburger manuals, this have a example to this funcionality.
Greetings,
Hervey

SEEBURGER/MSGSPLITTER: There is no attachment to split. Urgent ..!!!

Hi All,
I have the following scenario.
1) An EDI File is placed in a File location.
2) A File adapter picks the file.
3) The file adapter has a module Processing Sequence of
Classifer, converter and splitter.
4) After picking the EDI File, we should get a Main document and a FunctionACK.
I am facing the problem in step 4.
After picking the file, the main document is not found, Im getting only FunctionACK with status as "R".
Am i missing something here?
- I have only one attachment in this case.
- FuncACK does not tell me which EDI segment/element has error.
- I have configured the message splitter in Seeburger work bench also.
- Iam making sure that the senderID I have maintained in the SB workbench is corresponding to the same senderid in edi file which Iam picking.
Note : Its working perfectly for one message, but its showing the same problem for remaining other interfaces.
Only one thread is there for this problem in SDN, but they haven't mentioned the solution.
Re: SEEBURGER/MSGSPLITTER: There is no attachment to split.
Waiting for your answers.Its very urgent for me.
Thanks & Regards,
Seema.

The AUDIT LOG in RWB is ,
2008-02-28 09:31:08 Success Channel CC_FILE_SND_ORDERS: Send binary file "/sapint/testout/ORDERS_TEST". Size 2572 with QoS EO
2008-02-28 09:31:08 Success SEEBURGER/CLASSIFIER: Successfully read message and configuration data. The analysing and classifing starts now
2008-02-28 09:31:08 Success SEEBURGER/CLASSIFIER: exiting SeeClassifier successfully
2008-02-28 09:31:08 Success SEEBURGER BICXIADAPTER.MODULE Message entered Module (CallBicXIRaBean) and will be passed to the adapter now.
2008-02-28 09:31:08 Success SEEBURGER BICXIADAPTER +++ starting conversion with mapping: See_Edifact +++
2008-02-28 09:31:09 Success SEEBURGER BICXIADAPTER +++ CONVERSION SUCCESSFUL +++
2008-02-28 09:31:09 Success SEEBURGER BICXIADAPTER.MODULE BIC Module (CallBicXIRaBean) is exiting succesfully.
2008-02-28 09:31:09 Warning SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do.
2008-02-28 09:31:09 Success SEEBURGER/MSGSPLITTER: Finished splitting!
2008-02-28 09:31:09 Success Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
-Seema.

Content based receiver determination with Seeburger AS2 adapter

We are planning to use the Seeburger AS2 adapter on our XI 3.0 installation to post custom XML documents to XI from external business partners. The problem we have is to do the receiver and interface determination based on the xml message type that is submitted. How can we identify what is the name of the root xml node (which is representing the message type that was submitted to us) during the receiver determination and specify conditions for the receiver determination based on this? We can not use the Seeburger Classifier module here as this is only determining the mapping name to be used for an EDI conversion but can not handle any type of XML message.

Rudy,
I think the easiest way would still be the ReceiverDetermination and creating an XSD that contains the main important TAGs from the different messages.
That should allow you to test for the existing of certain important TAGs or check the value of some TAGS.
I don´t know about aedaptive-adapters, but I don´t think that they are Drummond-Certified. Check out...
http://www.drummondgroup.com/html-v2/as2-companies.html
Without this certification, a lot of your partners might not allow you to use this adapter if you wanna make AS2 with them.
Greetings
Stefan

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier        classifier
localejbs/CallBicXIRaBean      bic
CallSapAdapter                 0
classifier   attID             classifierAtt
classifier   destSourceMsg     MainDocument
classifier   showInAuditLog    true
bic          classifierAttID   classifierAtt
bic          destEncoding      UTF8
bic          destSourceMsg     MainDocument
bic          destTargetMsg     MainDocument
bic          mappingName       AUTO
bic          newLine           true
bic          srcEncoding       UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
    <D_I01>00</D_I01>
    <D_I02/>
    <D_I03>00</D_I03>
    <D_I04/>
    <D_I05>ZZ</D_I05>
    <D_I06>CELORGS01</D_I06>
    <D_I05_2>ZZ</D_I05_2>
    <D_I07>AVX</D_I07>
    <D_I08>032008</D_I08>
    <D_I09>1718</D_I09>
    <D_I10>X</D_I10>
    <D_I11>00401</D_I11>
    <D_I12>000000008</D_I12>
    <D_I13>0</D_I13>
    <D_I14>T</D_I14>
    <D_I15>^</D_I15>
    <S_GS>
      <D_479>PO</D_479>
      <D_142>CLS01</D_142>
      <D_124>058895921</D_124>
      <D_373>20080320</D_373>
      <D_337>1718</D_337>
      <D_28>8</D_28>
      <D_455>X</D_455>
      <D_480>004010</D_480>
      <S_ST>
        <D_143>850</D_143>
        <D_329>800001</D_329>
        <S_BEG>
          <D_353>00</D_353>
          <D_92>SA</D_92>
          <D_324>4500005037</D_324>
          <D_373>20051110</D_373>
        </S_BEG>
        <S_CUR>
          <D_98>BY</D_98>
          <D_100>USD</D_100>
        </S_CUR>
        <S_FOB>
          <D_146>CC</D_146>
          <D_309>OR</D_309>
          <D_352>FREE CARRIER</D_352>
          <D_334>02</D_334>
          <D_335>FOB</D_335>
          <D_309_2>DE</D_309_2>
        </S_FOB>
        <S_ITD>
          <D_336>01</D_336>
          <D_333>3</D_333>
          <D_351>45</D_351>
        </S_ITD>
        <G_SN9>
          <S_N9>
            <D_128>L1</D_128>
            <D_369>GEN</D_369>
            <S_MSG>
              <D_933>TEST</D_933>
            </S_MSG>
            <S_MSG>
              <D_933>MESSAGE</D_933>
            </S_MSG>
          </S_N9>
        </G_SN9>
        <G_SN1>
          <S_N1>
            <D_98>BY</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
            <S_PER>
              <D_366>BD</D_366>
              <D_93>Graham Crawford</D_93>
            </S_PER>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>BT</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>SE</D_98>
            <D_93>3M COMPANY</D_93>
            <D_66>92</D_66>
            <D_67>0000019591</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>ST</D_98>
            <D_93>SAMPLE</D_93>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SPO1>
          <S_PO1>
            <D_350>00010</D_350>
            <D_330>10.000</D_330>
            <D_355>EA</D_355>
            <D_212>10</D_212>
            <D_639>PE</D_639>
            <D_235>BP</D_235>
            <D_234>230-1812-01JDS</D_234>
            <D_235_2>EC</D_235_2>
            <D_234_2>A00000000000002</D_234_2>
            <G_SPID>
              <S_PID>
                <D_349>F</D_349>
                <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
              </S_PID>
            </G_SPID>
            <S_REF>
              <D_128>CO</D_128>
              <D_127>4500005037-00010</D_127>
            </S_REF>
            <G_SSCH>
              <S_SCH>
                <D_380>10.000</D_380>
                <D_355>EA</D_355>
                <D_374>002</D_374>
                <D_373>20051208</D_373>
              </S_SCH>
            </G_SSCH>
          </S_PO1>
        </G_SPO1>
        <G_SCTT>
          <S_CTT>
            <D_354>1</D_354>
          </S_CTT>
        </G_SCTT>
        <S_SE>
          <D_96/>
          <D_329>800001</D_329>
        </S_SE>
      </S_ST>
      <S_GE>
        <D_97>1</D_97>
        <D_28>8</D_28>
      </S_GE>
    </S_GS>
    <S_IEA>
      <D_I16>1</D_I16>
      <D_I12>000000008</D_I12>
    </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

Seeburger - Mapping - Classifier Module

Within the Sender communication channel I am specifying
classifierMappingID = MVVM
The error log on the communication channel says it is trying to load map XML_MVVM
Where is the XML_coming from within the BIC MD I have AnsiX12_MVVM (which is what i want it to use)
I have looked at various threads including
Seeburger problem for Custom Mappings..!!! ( but this refers to EDIFACT not ANSIX12)
All I would like to know is how to get rid of the XML and replace with AnsiX12
Many Thanks
M

Hi Guys,
Am working on testing the file however for the parameters as mentioned (see my answers in brackets)
Module key = bic (key which you have used for module "localejbs/CallBicXIRaBean")
Parameter Name = classifierAttID
Parameter value = classifierAtt (I am using ClassifierAddInfo instead)
this will show an additonal attachement for message processing in the sxmb_moni as "classifierAtt" .here you can confirm how the Classifier identifies your file as "XML" or "AnsiX12".
If classifier recognizes your file as "XML" but not as "AnsiX12" , then there must be some issues with input file format.
along with it -
Module key = bic (key which you have used for module "localejbs/CallBicXIRaBean")
Parameter Name = logAttID
Parameter value = ConverterLog (I am using this as you suggest)
It will show you the attachement for message processing in the sxmb_moni as "ConverterLog" , which discribes all the steps including what indivisual mapping are being called within BIC (850, 860....)
( The message is not getting to Moni - it is in fact failing in the Seeburger Monitor with error - cannot initiate received message to backend system)
Thanks
Mark

Classifier, BIC and MessageSplitter with Seeburger

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

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

Version not recognized by Classifier of Seeburger

Hi,
I have a document EDI with version 002001ABC and this document can convert without problema in BICMD from Seeburger, but when I receive the document in SAP XI with the Classifier and Converter, don't recognize the version. If I replace the version in the document EDI to 002001, the Classifier and Converter recognize the document and execute the map correctly.
I try with the name of the map, I replace the _V2001 by _V2001ABC in the BICMD, but it doesn't works.
Somebody help me please, about how I can configure the Classifier or Converter to the version 002001ABC works?.
Greetings,
Hervey.

I resolve this problem.

Classifier mapping to read Sender & Receiver Identification Number from XML. How to handle in B2B Add on

In current See burger tool, We have this functionality to read Sender and Receiver Identification number from the XML. Is there any way in b2b add on to do this.

Hi,
The classifier within the Seeburger context is being used to call your parent mapping, in case you want to dynamically determine your mapping, based on data in the UNB/UNH segment.
Within the B2B add-on, there is no need to.
Only use module localejbs/EdifactConverterModule in case you want to convert to or from EDI.
You have a specific requirement or do you want to test something out?
Kind regards,
Dimitri

Error with Seeburger Splitter module

Hi all,
I had configured Seeburger Splitter and using seeburger splitter module in file adapter with classifier,convertor and splitter in same sequence.But,while testing i m getting null
error for sender file adapter in communication channel monitoring.It isn't able to process the file placed in directory.
When audit log of same is seen,it shows
ERROR : getXmlContentFromMessage()
ERROR : process()
ERROR : Attempt to process file failed with null
Any inputs why is it so.
Regards,
Anoop

Hello Ravi,
We have seen this issue on a few occasions. It might be related to the ConverterJNI class.
In the defaulttrace file you can check for error such as
Caused by: com.sap.i18n.cp.ConverterRuntimeException........
Got exceptions: null
at com.sap.i18n.cp.ConverterJNI.<clinit>(ConverterJNI.java:46).....
If this is the case, Then the problems is within the Startup Framework. I would advise you to update the Startup Framework as described in note #710914.
Thanks,
David

Seeburger FTP Adapter And SAP PI 7.1

Hi Everyone,
Just a few questions about Seeburger FTP adapter please. Bit of background for clarity, we are doing an implementation using Seeburger FTP and sap PI 7.1 picking up EDIFACT (Orders) and returning (DESADV, ORDERSP, INVOICES). However we are not using any BIC, using another tool for EDIFACT -> EDIFACT-XML conversion (conversion agent) and in-house mapping development using graphical mapping.
So couple of things which I haven't been able to figure out from the standard documentation for Seeburger FTP adapter:
1) First is the functional ACK which we are meant to send back to the VAN is that a STANDARD FUNCTIONALITY with Seeburger FTP adapter?
2) Because we are receiving a mix bag EDIFACT interchange on the way IN, I need to split messages accordingly and pass them on to the relevant channels and mappings. By using the standard module Splitter can I achieve that?
3) Lastly some of the standard validations which are applicable to EDIFACT are they supported within the FTP adapter automatically? e.g. Counting number of messages in one interchange etc.
Any help in this regard will be really great.
regards

Now a Good news.
If you are using Seeburger version 2.1 (which you should be as you want it for PI 7.1), then there is an Internal Classifier and Split option for FTP adapter. You just need to tick checkbox "Use built-in splitting" and you are done. Then I believe there won't be any need for considering all these problems. The earlier version of Seeburger with PI 7.0 doesn't have such option and that could be the reason you haven't received any appropriate response yet.
Still I will reply all your questions considering that "your case is of PI 7.0". -> remember PI 7.0
>>even with just splitter we should be able to break it up?????? or am I wrong in thinking this?
No. You even need BIC or an equivalent custom module for achieving this.
>>I can't visualize where to handle the overall message count in one Interchange any suggestions?
You need to write an adapter module for this. Not sure about the code but this module has to be added before the split happens.
>> seeburger ftp adapter it does talk about a lot of reports which are available on sender/reciever actions. e.g. delivered, despatched etc. Are these reports not essentially ACKs?
These reports are the ones used at the receiver side for getting the ACKs from the receiver. Your requirement is at present for sender scenario.
Regards,
Prateek

Seeburger Classifier

Similar Messages

Maybe you are looking for