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

Similar Messages

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 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

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

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

Documentation of the Classifier module

Hi,
I use the classifier module from Seeburger on XI with File Adapter from SAP XI, but on the documentation, don't tell me about the standard name of the map, and I prove different names. If I use the classifierMappingID variable, the error "The mapping: AnsiX12_mappingID you are trying to load cannot be found in the classpath! Maybe you forgot to compile or to activate the mapping", where the mappingID is the value of the variable classifierMappingID on the module sequence. If I don't set this variable, the process is succesfull, but the classifier don't execute any map, only generate the Functional Aknowledgement with "R" status.
How I can know the name that must be used in the map, if it does not come mentioned in the documentation?, I can review some file of Seeburger or will have some document with this information?.
For example, a standard name, ANSIX12_<document>_<version>, to the classifier execute the correct map.
I thank for its aid.
Best regards,
Hervey.

Hi Hervey,
see my post to your last thread from Feb. 17th Classifier, BIC and MessageSplitter with Seeburger
That should help you a bit further.
I also suggest that you read the documentation from Seeburger for
SAPXI_BICMD_config_en.pdf
SAPXI_BICAdapter_Setup_en.pdf
SAPXI_BICAdapter_en.pdf
that will explain how you will know the names for the 1:1 and classifier mappings.
If you are using a document for which Seeburger does not already provide a 1:1 mapping, you will have to create it first, otherwise the Classifier Mapping will error out because it can not find the mapping.
Seeburger is able to provide you with remote help if you can't get any further. This won't be for free, but will get you setup much faster than try and error.
You can contact their north american office at 770 904 3888
Regards,
Andrea

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.

Seeburger BIC module not working

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

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

Regarding Seeburger Adpater

Hi can any one tell me what are seeburger adpaters and how actually is it used in EDI based intergrations

HI,
please look in to this links u will come to know about seeburger adapter.
HI,
/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
/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
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.
Seeburger thread:
Refer this forum which is replied by me which talka about the configuration which need to be done for AS2 adapter. This is very helpful:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
Seeburger info:
Re: seeburger adapter
Re: SEEBURGER's VAN Adapter
AS2 info:
Re: Regarding Seeburger AS2 Adapter
Thnx
Chirag Gohil

Seeburger BIC module

Hi all,
I am using seeburger BIC module to convert XML file to EDI.
My question is, can we configure BIC module parameter "srcDelimiter" dynamically rather than supplying any value?
Thanks

I dont think you can dynamically set the values for the parameters of the same..
There is an option which you can look for is how to pass dynamic parameters to the mapping using some other module..
In that direction you need to look for..but for bic and for delimiter parameter you cannot pass the values dynamically..
HTH
Rajesh

Dump regarding 'Error in module RSQL 'in dynamic internal table

Here is a Dump regarding 'Error in module RSQL of the database interface'.My program runs fine if 100 rows is getting selected from SAP Table.But for mass selection program is giving Dump. The program has dynamic selection of any SAP Table with dynamic selection ranges.I have attached below snippet code for your understanding and analysis.
Looking forward your kind support.
* Select Data from table using field symbol which points to dynamic table with packet size
SELECT *
    INTO CORRESPONDING FIELDS OF TABLE <fs_table_tmp>
    FROM (p_table) PACKAGE SIZE p_packet.
    INSERT LINES OF <fs_table_tmp> INTO TABLE <fs_table> .
    UNASSIGN <fs_table_tmp> .
ENDSELECT.

Hello Salmali,
Are you checking in the debugger mode?
Error CX_SY_OPEN_SQL_DB comes when there is any pause between select and endselect.
one more thing use INTO in place of APPENDING.
SELECT (i_field_select)
    FROM (p_table)
    into CORRESPONDING FIELDS OF TABLE <fs_table_tmp>
    PACKAGE SIZE p_packet.
    append LINES OF <fs_table_tmp> INTO TABLE <fs_table> .
    Refresh <fs_table_tmp> .
ENDSELECT.
Please let me know what is the value of p_packet.
also have you created the table <fs_table_tmp> and <fs_table> of same type . Please check
Thanks,
Gaurav

Regarding Lightroom Slideshow module: When I click on the preview button I get the following error: An internal error has occurred: ?:0: attempt at index a nil value. This occurs with any group of images I select in my catalog.

Regarding Lightroom Slideshow module: When I click on the preview button I get the following error: An internal error has occurred: ?:0: attempt at index a nil value. This occurs with any group of images I select in my catalog.

Jeannine,
If you follow the advice of the previous poster Julie Kmoch and then gradualy add presets back in one at a time you might be able to find the one that is causing the issue. I may be guessing, but I believe the issue has something to do with either an incompatible Preset setting (eg a older preset in newer version of LR) or a corrupt Preset.
Say you bought LR2 and imported a bunch of Presets from the internet, cuz 'Hey these effects are cool and I don't have to recreate the wheel', and then you upgraded to LR3 (not a clean install) and now one of the Presets that calls a certain slider setting or value that is different in LR3 doesn't work anymore. This might be why it throws the error, but again I am just speculating.
Location of LR Preset folder in Windows Vista/ Windows 7
C:/Users/<YourUserName>/AppData/Roaming/Adobe/Lightroom/Develop Presets
If you do not see the folder AppData, you may need to change the settings in Windows Explorer to 'Show Hidden Files and Folders'. To do that in Windows Vista/ Windows 7, open a Windows Explorer window, Click on Organize, then Foler and Search Options. Then click on the View tab and select the option button next to Show hidden files, folders and drives.
Hope this helps a bit,
Glenn

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

Variable substitution & Seeburger conversion module

Hi everybody!
I would like to use the variable substitution in a receiver file adapter to add the order no. (which is contained in the XML file) to the filename.
In addition I have to convert the XML file to an edifact format using the seeburger module "localejbs/CallBicXIRaBean".
As soon as this entry is made in the modules the following error message occurs:
"com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Caught SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 53, 4f, 48(:main:, row:1, col:3)"
My problem is that the conversion from XML to edifact is done before the variable substitution is started. That`s why the reference for the variable is no longer valid as the file is already converted to a edifact (=flatfile) format.
If I disable one of the two steps (either 1:1-mapping or variable substitution) the other step runs properly.
Has anybody an idea how to solve this topic? Is it possible to specify the variable substitution as module? If this is possible I could solve it by just reordering the two steps in the module chain.
Kind regards
Chris

Use Dynamic Configuration Bean to set this value. You have to use this well before "localejbs/CallBicXIRaBean".
Check SAP note : 974481 for more information.
Blog: [/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean|/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean]
Second Approach if the above approach doesnt work.
Use Dynamic Configuration concept in UDF to set the filename under message Mapping.
Thanks,
- Gujjeti.
Edited by: Praveen Gujjeti on Feb 25, 2009 11:25 AM

Regarding SEEBURGER

Hi ALL,
Could you plz tell me ,
In IDOC to EDI SEEBURGER Scenario, We have to purchage the SEEBURGEREDI Adapter Software ?
Where to install the SEEBURGER Software ? In XI System or Non-SAP System ?
Any Configuration required in Non-SAp System ?
Thanks & Regards
Murali

Hi,
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Thoughts on EDI in an SAP XI Environment
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
http://www.seeburger.com
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
The below links will answer your all questions
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
Thanks
Swarup

Regarding Seeburger Classifier Module

Similar Messages

Maybe you are looking for