Known Issues

The following is a list of known issues with out-of-box integration module between GTM and EBS.

• The ITM Adapter cannot send a purchase order in EBS to GTM. You will have to create a customized process in EBS to convert purchase orders to Trade Transaction XML and send them to GTM via integration methods such as httppost.
• If a delivery is modified by removing line(s), the ITM adapter cannot send proper instructions to GTM to remove the corresponding lines.
• The response XML into EBS does not contain any information about license and product classification. It has only the COMPLIANCE or NOT_COMPLIANCE status mapped to GtmTransactionLine/ControlScreeningResult/GtmExceptionControlCode. The modification of the response.xsl file responsible for transforming GTM XML to EBS XML is almost unavoidable.
• When a sales order modification is sent to GTM for re-screening, the ITM adapter cannot properly process the response from GTM containing update screening results.
• The ITM adapter can only take ONE response from GTM. If the response is COMPLIANT, EBS removes the exception hold of the sales order or delivery. If the response is NOT_COMPLIANT, the exception will not be removed. When the user manually resolve the compliance issues in GTM (sanction, RPLS, classification, or license), and GTM sends response of COMPLIANT again to EBS, EBS does not have the ability to accept the second or sub-sequential response from GTM. This means that if a Sale Order is on hold due to a GTM screening response of NOT_COMPLIANT, the end user will have to manually remove the exception in EBS, after they resolve the screening hold in GTM.
• The ITM adapter does not process the restricted party screening result from GTM.