Hi, I am using PI 7.3 – Java Only Stack Version and using ICO for interface.
My Scenario is EDI – 810 to Invoic02 IDOC - Invoice coming from vendor to ECC and then acknowledgement back to VENDOR.
At Sender Side instead of using AS2 Adapter Currently I am using File Sender but Having all EDI related Modules in It - Like Classifier, BIC, Splitter.
Below is my Sender File Channel Configuration:-
1 localejbs/SeeClassifier Local Enterprise Bean classifier
2 localejbs/CallBicXIRaBean Local Enterprise Bean bic
3 localejbs/Seeburger/MessageSplitter Local Enterprise Bean splitter
4 CallSapAdapter Local Enterprise Bean 0
bic classifierAttid classifierAtt
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_E2X_ANSIX12_810_V4010
bic setIgnoreCRLF true
bic split true
classifier showInAuditLog true
classifier attId classifierAtt
classifier destSourceMsg MainDocument
splitter sourceDest MainDocument
splitter targetChannel 943274043090098|See_E2X_ANSIX12_810_V4010|ACCEPTED|1
With this configuration my File Sender is working perfectly fine - It is reading EDI 810 file and converting it to XML and passing data to Invoice02 IDOC and successfully IDOC is posted on ECC
1. But for functional acknowledgement it is getting failed at Split997 Adapter.
SEEBURGER/MESSAGESPLITTER: Initiation of inbound message 117656e7-ee04-11e1-869e-0000000f65ff failed!:
Error in senderChannel 33a1cd37d2453df5acf45f9ec4746470: Catching exception calling messaging system-module:senderChannel 33a1cd37d2453df5acf45f9ec4746470: Catching exception calling messaging system Start processing 2f7e1097-edcc-11e1-9113-0000000f65ff (INBOUND-splitter-1).
Mode: MESSAGE & ASYNC Roll back transaction for 2f7e1097-edcc-11e1-9113-0000000f65ff(INBOUND-splitter-1)----Error in channelSplit997_FunctionalAck_Sender:
Error in senderChannel '33a1cd37d2453df5acf45f9ec4746470': Catching exception calling messaging system-module:senderChannel '33a1cd37d2453df5acf45f9ec4746470':
Catching exception calling messaging system Alert triggered:
Initiation of inbound message with id 68d17ee3-edcd-11e1-caad-0000000f65ff.
Parent ID Reference: 2f7e1097-edcc-11e1-9113-0000000f65ff(INBOUND-splitter-1) failed:
Error in senderChannel '33a1cd37d2453df5acf45f9ec4746470':
Catching exception calling messaging system-module:senderChannel '33a1cd37d2453df5acf45f9ec4746470': Catching exception calling messaging system
And In Addition to this in See Burger Workbench - Status is - Initiation for backend Pending.
2. Now when I Change Module Configuration Say AUTO Instead of See_E2X_ANSIX12_810_V4010
bic mappingName AUTO
Then functional Acknowledgements is get generated
Commit transaction for ec0f3d04-ee07-11e1-cf42-0000000f65ff(INBOUND-splitter-1). Mode: MESSAGE & ASYNC
Finish processing message ecb04513-ee07-11e1-c64a-0000000f65ff (parent reference ec0f3d04-ee07-11e1-cf42-0000000f65ff(INBOUND-splitter-1) )
But this time File Sender got into error and invoice02 not getting generated.
Error: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface