cancel
Showing results for 
Search instead for 
Did you mean: 

Seeburger - Mapping - Classifier Module

Former Member
0 Kudos

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

( 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

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Mark,

I totally agree what Sven Buttler said.

Apart from this I would suggest you to make few additional configuration under "Module configration" tab as below-

Module key = bic (key which you have used for module "localejbs/CallBicXIRaBean")

Parameter Name = classifierAttID

Parameter value = classifierAtt

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

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

Thanks

-Jyoti

Former Member
0 Kudos

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

sbuttler77
Active Participant
0 Kudos

It's a sender com channel he's probably pulling through different file formats thats why he needs the classifier.

Did you double check your file is ok? Can you try another one? It looks like the classifier thinks its dealing with

a XML file.

Former Member
0 Kudos

Sven,

So are you saying this piece is set according to file format...the file is coming in from a Trading Partner (new connection) what should I be telling him to ensure its AnsiX12

Thanks

sbuttler77
Active Participant
0 Kudos

For all I know the classifier tries to determine what format its dealing with. Next its calling the corresponding service mapping, defined in BIC mapping designer/sca module you deploy on your server.

Afaik this looks like format_YourCompany, e.g. Edifact_YourCompany, AnsiX12_YourCompany, Tradacom_YourCompany etc. So in your case it appears the classifier identifies your file as a XML file and not as a Ansi file. I'd ask your TP for a copy of the file and then setup a test scenario on your QA box and try to pull the file through from a local ftp if you get the chance to.

Former Member
0 Kudos

Hi,

I hope 'classifierMappingID' is not mandatory parameter with Classifier module.

mention your actual mapping name against your BIC module 'mappingname' parameter.

Suresh

Former Member
0 Kudos

Suresh

setting the mapping name as you suggest will not help in my scenario

I have set the BIC mappingname to AUTO as you could have 850s and 860s etc. coming in together

each one of course uses a different map

Former Member
0 Kudos

Hi,

after setting 'AUTO' to mapping name you need to use splitter module as well and needs to provide mapping names in splitter configuration in Seeburger work bench.

Suresh