Running ERPI Write-Back Rule Results in - JBO-27121: SQL Error During Statement Execution (Doc ID 1523107.1)

Last updated on AUGUST 08, 2016

Applies to:

Hyperion Financial Data Quality Management - Version 11.1.2.1.000 and later
Information in this document applies to any platform.

Symptoms

1. When running an ERPI Write-Back rule in ERPI 11.1.2.1.502 an error like the following is seen in the ERPI GUI (where x is an integer):

JBO-27121: SQL error during statement execution. Statement: INSERT INTO TDATAMAP(
  PARTITIONKEY,DIMNAME,SRCKEY,SRCDESC,TARGKEY,WHERECLAUSETYPE,WHERECLAUSEVALUE,DATAKEY,TDATAMAPTYPE,SYSTEM_GENERATED_FLAG
) SELECT x
,a.IMPFLDFIELDNAME
,'DEFAULT'
,'System Generated Mapping'
,'*'
,'LIKE'
,LPAD(
  CASE
  WHEN (c.MAPPING_TYPE_CODE = 'CONCATE_SEGMENT') THEN
  CASE a.impsourcecoalineid1
  WHEN b.impsourcecoalineid1 THEN ''
  WHEN b.impsourcecoalineid2 THEN ''
  WHEN b.impsourcecoalineid3 THEN ''
  WHEN b.impsourcecoalineid4 THEN ''
  WHEN b.impsourcecoalineid5 THEN ''
  ELSE '*'
  END
  ELSE '*'
  END
  ,(CASE WHEN (member_prefix IS NULL) THEN 0 ELSE LENGTH(member_prefix) END) +
  (CASE WHEN (c.MAPPING_TYPE_CODE = 'CONCATE_SEGMENT') THEN 3 ELSE 1 END)
  ,'?'
)
,TDATAMAP_DATAKEY_S.NEXTVAL
,'EPM'
, 'Y'
FROM tbhvimpitemerpi a
,tbhvimpitemerpi b
,aif_map_dim_details_v c
,aif_mapping_rules d
,aif_dimensions e
,tpovpartition f
WHERE a.impgroupkey = b.impgroupkey
and a.impdimname = b.impdimname
and a.impmaptype = 'EPM'
and b.impmaptype = 'ERP'
and a.impdimname = e.target_dimension_name
and e.dimension_id = c.dimension_id
and c.rule_id = d.rule_id
and d.partitionkey = f.partitionkey
and f.partimpgroup = a.impgroupkey
and f.partitionkey = x

ADF_Faces-60097:For more information, please see the server's error log for an entry beginning with: ADF_Faces-60096:Server Exception during PPR, #1

2. The same SQL query is seen in HyS9aifWeb-sysout.log but there are no corresponding entries in the HyS9aifWeb-syserr.log.
3. Write-back mappings have not been imported.

Changes

 If this has been working in the past then system generated write-back mappings may have been partially edited and saved.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms