Hi Sruthi
From your module config, parameter classifierMappingID is not specified for the classifier module. As such the main mapping that will be used will be the default Seeburger main mapping, i.e. See_<ContentType>
SEEBURGER/CLASSIFIER: type -> AnsiX12
EBURGER/CLASSIFIER: exiting SeeClassifier successfully
From the audit log, the content type is determined as AnsiX12 by the classifier, so the BIC mapping that will be executed will be See_AnsiX12. It is this mapping that will generate the intermediate FA message as well as any child 945 messages. The child 945 messages will then be sent to the splitter (provided Message Splitter Config is done correctly in Seeburger Workbench.)
However, you mentioned that you are using a custom 945 message. Without further details of what exactly is the customization, I can't tell for sure what is happening. My guess is that the main mapping See_AnsiX12 is not able to determine the 945 segments from the source file. If you have BIC Mapping Designer tool, I would suggest you test it out there - try transforming your input file with the See_AnsiX12 mapping and check the logs.
Additionally, I would suggest that you add the parameter logAttID = BIC_Log for the BIC module. This would create an additional attachment named BIC_Log which you can view in SXMB_MONI. This gives you further details on what is happening during BIC conversion. If you provide the details of that log here, it would be useful for further investigation too.
If indeed the default See_AnsiX12 mapping can't handle the custom message, then you need to create a customized main mapping in BICMD. You can copy from See_AnsiX12 to AnsiX12_Custom and modify it to handle the custom 945 message. To ensure that the classifier uses the custom main mapping, add parameter classifierMappingID = Custom to the classifier module.
Rgds
Eng Swee