How to track down the most likely problems with FI Connect api messages.
Check the FI Connect queue by looking in the Message Queue, View Message Queue. You should be able to find the message by "Created Date and Time" and "Touchpoint Key".
What's the Status? DONE means FI Connect considers the message to have processed OK. ERROR, click the "Message ID".
What does it say under "Error Messages"? Hopefully it's meaningful and is about missing or incorrect data. Possibly cross reference data from the Indus Connect (the Y) panels is missing.
"Please refer to the log for details." and "NO ERROR Messages found for this messages." means you're going to have to look in the FI Connect logs for the message type.
The message can be restarted from Message Queue, click the xml link, scroll to the bottom, and click Resubmit.
The message logs
Go to ../webapps/fixml/regions/REGION/docs/logs. Find the log file you're interested in by message type, date, and time. Reading the log file can be tricky due to the long record lengths. Unix vi tends to foul up. Try the Unix cat command or FTP the file to a PC.
Look for a java abend.
Example:
SEVERE 2005-01-01-10.00.00.000000 Passport Exception. Throwable caught at PeopleSoftPuInserv.generateXML() - Throwable caught at PeopleSoftPuInservXmlBuilder.getXml() - Throwable caught at PeopleSoftPuInservXmlBuilder.createPuInservElmt(Connection) - Throwable caught at PeopleSoftPuInservXmlBuilder.createWpElmt(Connection) - Throwable caught at PuInserv.processWdTag(Connection) - FI00014E - No LOCAT row found, can't create WD segment(s).
com.iint.ic.util.PassportException: Throwable caught at PuInserv.processWdTag(Connection) - FI00014E - No LOCAT row found, can't create WD segment(s). at com.iint.ic.app.PuInserv.processWdTag(PuInserv.java:1130)
This is saying that the Java class PuInserv bombed in method processWdTag because an expected entry in PassPort table TIDLOCAT was not found.
Cannot identify the external system for the incoming XML.
Tomcat catalina.out log contains messages similar to:
<PUBLISH_RULE_ID/>
<MSGNODENAME/>
</PSCAMA>
</Transaction>
</MsgData>
</CUSTOM_VENDOR_OUT_EFF>
Got pref
INFO 2008-07-15-13.33.37.000727 In setData of PeopleSoftXmldata
INFO 2008-07-15-13.33.37.000729 @PeopleSoftXmlData.setData, XML tag not found!
WARN 2008-07-15-13.33.37.000730 @InboundGateway.doPost -NonPassportException - Cannot identify the external system for the incoming XML. Pl check the XML.
What the log entry is trying to tell you is that FI Connect cannot determine the source application for the incoming XML.
PassportLiterals.properties contains entries that associate XML tag fragments with 3rd party applications.
…
PsftProjects=<CUSTOM_PROJECT>
PsftActivities=<CUSTOM_ACTIVITY>
PsftApPayments=<CUSTOM_AP_PAYMENT>
PsftEmployees=<PERSONAL
PsftVendors=<CUSTOM_VENDOR
PsftLaborRate=</CUSTOM_LABOR_RATE>
PsftApRecons=<CUSTOM_AP_RECON>
…
SapVendors=<VendorDoc
...
Entry "PsftVendors=<CUSTOM_VENDOR" had reverted back to "PsftVendors=<FININT_VENDOR". "<CUSTOM_VENDOR" is found in the incoming XML and lets FI Connect know that PeopleSoft is the 3rd party application.