Seeburger AUTO mapping issue

[former_member206760]

Hey experts,

I have configured a scneario where classifier BIC split are used in sequence.

now what is happening is we are using a custom BIC mapping starting from say ZZ.

so in clasifier mapping ID we have specified ZZ ...and in BIC mapping we have used AUTO

so that the BIC mapping name constructred should be ZZ_ANSIX12.....( we have already deployed mapping ZZ_ANSIX12...)

but when we run the interface we get an error saying BIC mapping ANSIX12_ZZ.....not deployed.

[prateek · Accepted solution]

but when we run the interface we get an error saying BIC mapping ANSIX12_ZZ.....not deployed.

The name you mentioned in error is not the one you said you deployed. This means that somewhere you are providing incorrect mapping name.

Regards,

Prateek

[former_member206760 · Accepted solution]

Hi Prateek,

As you know, when we specify mapping name as AUTO ...we do not specifically give a mapping name..

that has to be generated by the system. and when i give classifer id as ZZ..it should create mapipng name like ZZ_E2X_ANSIX12..

this is what i expect system to auto create

[Former Member · Accepted solution]

Hi,

Enable the logs of the seeburger by using the parameter of the BIC...(dont remember that name exactly...for knowing the more details of the same)

looks like the mapping deployed is not compiled/activated before deployment...

if you are using the 1.8 version of the seeburger you can check the mappings deployed in the PI system..using system status tab in the Seeburger workbench....

HTH

Rajesh

[prateek · Accepted solution]

As you know, when we specify mapping name as AUTO ...we do not specifically give a mapping name..

But you provide mapping name in splitter configuration.

Set auditLogStatus as true for classifier and check out the audit log generated. Also change the mode of Seeburger log to Debug and check the traces for more details.

Regards,

Prateek

[Former Member · Accepted solution]

Hey Tarang,

Dude this one is simple. You can easily fix it. Dont worry about your module config that is correct.

So AUTO part for Bic mapping is fine. And classifier ZZ part is good too.

The issue is in your naming convention and how BIC wants it; and BIC is moody

So below are the steps:

1) Go back to your BIC mapping designer

2) You have named your Parent mapping in BIC MD like this ZZ_ANSIX12

3) Change that to ANSIX12_ZZ

And that's it it will start working (don't forget to redeploy it though)

regards

[sbuttler77]

You can enable verbose logging using parameter: logAttID value: ConverterLog in your bic

module configuration

[sbuttler77]

Also, if you're using the splitter you might want to check out the mapping name in the message

splitter setup

http://xihost:50000/seeburger/index.html