Clarity: When a xml transaction file contains "expenseType" attribute the XOG causes the Error "Inbound Transaction Object Insert failed".

Document ID : KB000050965
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Details: When a xml transaction file contains "expenseType" attribute the XOG causes the Error "Inbound Transaction Object Insert failed".

Steps to Recreate:

  1. XOG in the xml file with transaction that contains "expenseType" attribute.
      <?xml version="1.0" encoding="UTF-8" ?> - <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_inboundTransaction.xsd">  <Header action="write" externalSource="NIKU" objectType="transaction" version="12.0.6.5471" /> - <Transactions>  <Transaction projectID="ITPR000120" taskID="5000128" transactionDate="2010-07-24" resourceID="Hardware" transactionType="X" chargeCode="Capital" inputTypeCode="Default" transactionClass="Hardware" chargeable="1" units="1.0" voucherNumber="PSFIN1" expenseType="CAP_EXPENSE" notes="1111111" groupId="65" externalID="65" actualCostRate="100.0" actualCostRateCurrency="USD" billRate="100.0" billRateCurrency="USD" importStatus="N" />   </Transactions>  </NikuDataBus>

Expected Result:
The transaction is XOGed-in without error.

Actual Result:
The Xog causes the error "Inbound Transaction Object Insert failed".

Solution:

Workaround:

None

Status/Resolution:
The issue has been documented as CLRT-57428. The bug is fixed in hotfix 12.0.6_generic_011

Keywords:
CLARITYKB, CLRT-57428