Seeburger problem for Custom Mappings..!!!

[Former Member]

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 didn’t 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 didn’t 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.

[i812848 · Accepted solution]

Hi,

Don't give your childmapping the name for classifierMappingId!

If a customised child mapping is to be started, follow these

steps:

1. Create the child mapping using the SEEBURGER Converter Mapping Designer. E.g. it can be

called: “E2X_INVOICES_ABC”.

2. Make a copy of the standard main mapping See_AnsiX12 and name it, e.g.

“AnsiX12_MyMainMapping”.

The name of the modified mapping should not contain the “See_” prefix; instead it can

have a user defined suffix, in our example “_MyMainMapping”.

3. change the “AnsiX12_MyMainMapping” that it calls your child mappings.

4. Modify the inbound channel module chain so that it uses the new main Mapping. E.g.:

classifierMappingID MyMainMapping

Best regards,

ilka

[Former Member · Accepted solution]

Hi llka,

Sorry for the late reply.

So by changing the Main mapping name into ANSI_mymapping and by using mymapping in our classifiermappingID .. it will work.??

after that can i use any custom name for my maps??

>> 3. change the “AnsiX12_MyMainMapping” that it calls your child mappings.

I didnt understand this point.

I need to do any thing with child mappings after changing the name of the Main mapping?

Thanks

Seema.

[Former Member · Accepted solution]

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 won’t 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

[Former Member · Accepted solution]

Hi Schults,

Thanks for your reply,

Its working perfectly.

In the same way we need to work for Inhouse files.Based on the content of the message the map has to takes place which we will provide in the seeburger splitter configuration.

Please suggest me how we can go about it.

Here I raised a separate thread for that question.

Waiting for your reply.

Thanks&Regards

Seema.

[Former Member]

Hi,

While creating custom mappings in BIC MD,

Custom mappings name u can use there is "E2X_ORDERS_D96A_XXX".

this XXX at the end is any value which u can give here.

After deployment of mapping_user.sda from BIC MD into server,u can use these custom mappings in modules configuration tab.

While configuring modules using these custom mappings, u have to set a parameter

C classifierMappingID XXX.

Thanks,

Anoop