Fusion Diagnostic Message

Message NamType Family Product LBA Short Name
ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList
ATK_INVALID Error (FND) ATF ATK AtkHelpPortal
ATK_UAP_WRError (FND) ATF ATK AtkHelpPortal
ATK_WATCHLIError (FND) ATF ATK AtkWatchList
ATK_INVALID Error (FND) ATF ATK AtkHelpPortal
ATK_ADDRES Error (FND) ATF ATK AtkContextAddress
ATK_HOSTED Error (FND) ATF ATK AtkHelpPortal
FND_CMN_ESError (FND) Common FND FndAppCommon
FND_CMN_NEError (FND) Common FND FndAppCommon
FND_CMN_RCError (FND) Common FND FndAppCommon

FND_CMN_PRError (FND) Common FND FndAppCommon
FND_CMN_FLError (FND) Common FND FndAppCommon
FND_CMN_USError (FND) Common FND FndAppCommon
FND_CMN_SEError (FND) Common FND FndAppCommon
FND_CMN_SOError (FND) Common FND FndAppCommon

FND_CMN_SYError (FND) Common FND FndAppCommon
FND_CMN_FLError (FND) Common FND FndAppCommon
FTA_HIRING_ Error (FND) Common FTA FtaServer
CSO_KM_APPError (FND) CRM CSO CsoKmUi
CSO_KM_APPError (FND) CRM CSO CsoKmUi
CSO_ATTACH Error (FND) CRM CSO CsoKmUi

CSO_SEARCH_Error (FND) CRM CSO CsoKmUi
CSO_NO_SEA Error (FND) CRM CSO CsoKmUi
CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin
CSO_CATEGORError (FND) CRM CSO CsoKmUi
CSO_APPL_NOError (FND) CRM CSO CsoAdmin

CSO_CONCEPTError (FND) CRM CSO CsoAdmin
CSO_CONCEP Error (FND) CRM CSO CsoAdmin
CSO_ADMIN_LError (FND) CRM CSO CsoAdmin
CSO_CONCEP Error (FND) CRM CSO CsoAdmin
CSO_ADMIN_LError (FND) CRM CSO CsoAdmin
CSO_ADMIN_N
Error (FND) CRM CSO CsoAdmin
CSO_CONCEPTError (FND) CRM CSO CsoAdmin
CSO_DICT_M Error (FND) CRM CSO CsoAdmin
CSO_SEARCH Error (FND) CRM CSO CsoAdmin
CSO_ADMN_CError (FND) CRM CSO CsoAdmin

CSO_LOCALE Error (FND) CRM CSO CsoAdmin
CSO_ROLES_RError (FND) CRM CSO CsoAdmin
CSO_AVAIL_L Error (FND) CRM CSO CsoAdmin
CSO_SERVICE Error (FND) CRM CSO CsoAdmin
CSO_USER_GRError (FND) CRM CSO CsoAdmin
CSO_NO_REPOError (FND) CRM CSO CsoAdmin

CSO_CHILD_NError (FND) CRM CSO CsoAdmin
CSO_PRODUCTError (FND) CRM CSO CsoAdmin
CSO_USERS_RError (FND) CRM CSO CsoAdmin
CSO_ACTIVE_ Error (FND) CRM CSO CsoAdmin
CSO_INTERNAError (FND) CRM CSO CsoAdmin
CSO_CATEGORError (FND) CRM CSO CsoAdmin
CSO_SERVICE Error (FND) CRM CSO CsoAdmin
FOD_ERROR_ Error (FND) CRM FOD SimplifiedSetup
FOD_SA_FRCSError (FND) CRM FOD SimplifiedSetup
HZ_RES_PARTError (FND) CRM HZ FoundationResources
HZ_GEO_GNRError (FND) CRM HZ FoundationGeographie

LOY_TXN_STAError (FND) CRM LOY LoyTransaction
MCT_INV_SP Error (FND) CRM MCT MctCommon
MCT_INV_RL Error (FND) CRM MCT MctCommon
MKL_DEAL_A Error (FND) CRM MKL MklDeals
MKL_LEAD_U Error (FND) CRM MKL MklLeads
MKT_CONT_RError (FND) CRM MKT MktCoreMarketing
MKT_IMP_ATTError (FND) CRM MKT MktCommonMarketing
MKT_IMP_ERRError (FND) CRM MKT MktCommonMarketing
MKT_CONT_RError (FND) CRM MKT MktCommonMarketing

MKT_SYS_ERRError (FND) CRM MKT MktCoreMarketing
MKT_BI_APP_Error (FND) CRM MKT MktBi
MKT_SALES_ Error (FND) CRM MKT MktSalesCampaigns

MKT_TRMT_TE
Error (FND) CRM MKT MktCoreMarketing
MOO_IMP_INError (FND) CRM MOO OpptyMgmtOpportuniti
MOO_OPTY_AError (FND) CRM MOO OpptyMgmtOpportuniti
MOT_QM_RETError (FND) CRM MOT SalesTerrMgmtQuotas
MOT_IMP_PAError (FND) CRM MOT SalesTerrMgmtTerritori
MOT_ESSBAS Error (FND) CRM MOT SalesTerrMgmtTerritori
MOT_QM_SYSError (FND) CRM MOT SalesTerrMgmtQuotas
MOT_QM_ESSError (FND) CRM MOT SalesTerrMgmtQuotas
MOW_AMENG_
Error (FND) CRM MOW WorkMgmtAssignment
MOW_CORE_N
Error (FND) CRM MOW WorkMgmtCore
MOW_CORE_A
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENGError (FND) CRM MOW WorkMgmtAssignment
MOW_AMENGError (FND) CRM MOW WorkMgmtAssignment
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_CORE_KError (FND) CRM MOW WorkMgmtCore
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_CORE_D
MOW_AMENG_
MOW_CORE_EError (FND) CRM MOW WorkMgmtCore
MOW_CORE_EError (FND) CRM MOW WorkMgmtCore
MOW_AMENG_
MOW_CORE_LError (FND) CRM MOW WorkMgmtCore
MOW_AMENG_
MOW_AMCLIEError (FND) CRM MOW WorkMgmtAssignmentC

MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_CORE_IN
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_AMENG_
MOW_CORE_D
OSS_PREVIEWError (FND) CRM OSS OssSubscriptionManag
QSC_GENMAPError (FND) CRM QSC OcSalesCatalogCommo
QSC_GENMAPError (FND) CRM QSC OcSalesCatalogCommo
QSC_SERVICE Error (FND) CRM QSC OcSalesCatalogCommo

SVC_FIELD_WError (FND) CRM SVC SvcFieldSvc
SVC_FIELD_S Error (FND) CRM SVC SvcFieldSvc
SVC_CSS_SEL Error (FND) CRM SVC SvcCustSelfSvc
SVC_CSS_INT Error (FND) CRM SVC SvcCustSelfSvc

SVC_FIELD_F Error (FND) CRM SVC SvcFieldSvc
SVC_FIELD_I Error (FND) CRM SVC SvcFieldSvc
SVC_AP_CREAError (FND) CRM SVC SvcActionPlan
SVC_AP_DISC Error (FND) CRM SVC SvcActionPlan
SVC_OBM_NUError (FND) CRM SVC SvcMgmt
SVC_FIELD_S Error (FND) CRM SVC SvcFieldSvc

SVC_OBM_GEN
Error (FND) CRM SVC SvcMgmt
SVC_HD_PARTError (FND) CRM SVC SvcMgmt
SVC_OMNI_WError (FND) CRM SVC SvcOmniChannel
SVC_SAVING_Error (FND) CRM SVC SvcMgmt
SVC_EMAIL_AError (FND) CRM SVC SvcMgmt
SVC_AP_INIT Error (FND) CRM SVC SvcActionPlan
SVC_HD_PERSError (FND) CRM SVC SvcMgmt
SVC_EMAIL_PError (FND) CRM SVC SvcMgmt

SVC_AP_ADD Error (FND) CRM SVC SvcActionPlan
SVC_FIELD_I Error (FND) CRM SVC SvcFieldSvc
ZCA_CPQ_INTError (FND) CRM ZCA CrmCommonSalesOrder
ZCA_INFOLET_Error (FND) CRM ZCA CrmCommonCore
ZCA_INFOLET Error (FND) CRM ZCA CrmCommonCore
ZCA_WORKSPError (FND) CRM ZCA ElasticSearch
ZCA_SA_ASSGError (FND) CRM ZCA CrmCommonSalesParti
ZCA_EXP_ERRError (FND) CRM ZCA CrmCommonBulkExpor
ZCH_EUM_CUError (FND) CRM ZCH CdmHubBase

ZCM_DATAFOX
Error (FND) CRM ZCM CustomerCtrInfra360
ZCM_DATA_CLError (FND) CRM ZCM CustomerCtrInfra360
ZCM_DATA_CError (FND) CRM ZCM CustomerCtrInfra360
ZCM_DAAS_S Error (FND) CRM ZCM CustomerCtrInfra360
ZCM_DATAFOError (FND) CRM ZCM CustomerCtrInfra360
ZCM_DATAFOError (FND) CRM ZCM CustomerCtrInfra360
ZCQ_CLEANSEError (FND) CRM ZCQ DataQualityRealTime
ZCQ_DQ_MATError (FND) CRM ZCQ DataQualityRealTime
ZCX_EXTN_BI Error (FND) CRM ZCX ExtnConfigurator


ZCX_OPA_HU Error (FND) CRM ZCX ExtnConfigurator
ZCX_CLOB_MAError (FND) CRM ZCX ExtnConfigurator
ZCX_DCL_MAXError (FND) CRM ZCX ExtnConfigurator

ZCX_EXTN_B Error (FND) CRM ZCX ExtnConfigurator
ZCX_EXTN_BI_Error (FND) CRM ZCX ExtnConfigurator


ZCX_EXTN_BI_Error (FND) CRM ZCX ExtnConfigurator

ZCX_EXTN_BI Warning (FNDCRM ZCX ExtnConfigurator

ZCX_EXTN_CRError (FND) CRM ZCX ExtnConfigurator
ZCX_LAYOUT_Error (FND) CRM ZCX ExtnConfigurator
ZCX_SUBTAB_Error (FND) CRM ZCX ExtnConfigurator
ZCX_ITEM_DEError (FND) CRM ZCX ExtnConfigurator
ZCX_SUMMARY
Error (FND) CRM ZCX ExtnConfigurator
ZCX_FIELD_G Error (FND) CRM ZCX ExtnConfigurator
ZCX_EXTN_MSError (FND) CRM ZCX ExtnConfigurator
ZCX_METADAError (FND) CRM ZCX ExtnConfigurator
ZCX_PERSONAError (FND) CRM ZCX ExtnConfigurator

ZCX_GROOVY_Error (FND) CRM ZCX ExtnContent
ZCX_EXTN_UPError (FND) CRM ZCX ExtnConfigurator
ZOC_STAR_R Error (FND) CRM ZOC Star
ZOC_NO_JOINError (FND) CRM ZOC TransformContext
ZOC_UTIL_N Error (FND) CRM ZOC OcCoreUtil
ZOC_CORE_R Error (FND) CRM ZOC OcCoreUtil
ZOC_UTIL_L Error (FND) CRM ZOC OcCoreUtil
ZOC_UTIL_VAError (FND) CRM ZOC OcCoreUtil

ZOE_BASE_OBError (FND) CRM ZOE OutlookEditionConnect
ZOE_GML_MAError (FND) CRM ZOE OutlookEditionConnect
ZOE_CONFIG_Error (FND) CRM ZOE OutlookEditionConnect
ZOE_BASE_OBError (FND) CRM ZOE OutlookEditionConnect
ZOE_SERVICE Error (FND) CRM ZOE OutlookEditionConnect
ZOE_OBJ_DE Error (FND) CRM ZOE OutlookEditionConnect
ZOE_BASEOBJError (FND) CRM ZOE OutlookEditionConnect
ZOE_UNEXPE Error (FND) CRM ZOE OutlookEditionConnect

ZOE_PARSIN Error (FND) CRM ZOE OutlookEditionConnect
ZOE_LEAD_T Error (FND) CRM ZOE OutlookEditionConnect
ZOE_PERSON Error (FND) CRM ZOE OutlookEditionConnect
ZOE_BASE_O Error (FND) CRM ZOE OutlookEditionConnect
ZPS_365_SY Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_MS_Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_MS_Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_INA Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_PAGError (FND) CRM ZPS_365 SalesCloudOffice365

ZPS_365_UNEError (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_SE Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_SET Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_SYN Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_CONError (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_SAV Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_SAV Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_APP Error (FND) CRM ZPS_365 SalesCloudOffice365
ZPS_365_LGI Error (FND) CRM ZPS_365 SalesCloudOffice365
ZSF_FCST_CU Error (FND) CRM ZSF SalesForecastingForeca

ZSF_FCST_SA Error (FND) CRM ZSF SalesForecastingForeca
ZSF_FCST_RE Error (FND) CRM ZSF SalesForecastingForeca
ZSO_FILE_IN Error (FND) CRM ZSO LightboxCore
ZSP_CMN_SYSError (FND) CRM ZSP ZspEngineAdministrati
ZSP_CMN_PR Error (FND) CRM ZSP ZspEngineAdministrati
ZSP_CMN_PR Error (FND) CRM ZSP ZspEngineAdministrati
ZSP_OBR_RULError (FND) CRM ZSP ZspBusinessRules
ZSP_OBR_RULError (FND) CRM ZSP ZspBusinessRules
AP_INV_ISP_ Error (FND) Financials AP FinApInvCore
AP_IDR_POSTError (FND) Financials AP FinApSharedCore
AP_ONLINE_VError (FND) Financials AP FinApInvCore

AP_ETX_NO_AError (FND) Financials AP FinApInvCore
AP_CANNOT_Error (FND) Financials AP FinApInvCore
AP_ERR_TAX_Error (FND) Financials AP FinApInvCore
AP_DEBUG Error (FND) Financials AP FinApSharedCore
AP_AWT_PROError (FND) Financials AP FinApInvCore
AP_CANNOT_D
Error (FND) Financials AP FinApInvCore
AP_INV_DIS_ Error (FND) Financials AP FinApInvCore
AP_UNFRZN_TError (FND) Financials AP FinApInvCore

AP_PAY_INTEGError (FND) Financials AP FinApPmtCore
AP_SUM_TAX_Error (FND) Financials AP FinApInvCore
AP_IBY_PAY_FError (FND) Financials AP FinApPmtCore
AP_FRZN_TAXError (FND) Financials AP FinApInvCore
AP_PAY_ACCTError (FND) Financials AP FinApPmtCore
AP_PAY_HIST Error (FND) Financials AP FinApPmtCore

AP_PAY_UPDAError (FND) Financials AP FinApPmtCore
AR_SYSTEM_ Error (FND) Financials AR FinArShared
AR_ADJ_ENT Error (FND) Financials AR FinArTransactionsMain
AR_BR_CANNO
Error (FND) Financials AR FinArBillsReceivable
AR_MFAR_SPLError (FND) Financials AR FinArShared
AR_XML_INVOError (FND) Financials AR FinArTransactionsMain
CE_IMPORT_ Error (FND) Financials CE FinCeCashTransactions
CE_SYS_ERR Error (FND) Financials CE FinCeBankStatements
CE_CUBE_UPDError (FND) Financials CE FinCeCpInquiry
EXM_CC_DWNError (FND) Financials EXM FinExmCreditCardCore

EXM_APREI_GInformation ( Financials EXM FinExmAuditCore
EXM_CC_UPL Error (FND) Financials EXM FinExmCreditCardCore
EXM_APREI_ Information ( Financials EXM FinExmAuditCore
EXM_APREI_I Information ( Financials EXM FinExmAuditCore
EXM_CC_DWNError (FND) Financials EXM FinExmCreditCardCore
FUN_SRC_FIL Error (FND) Financials FUN FinFunWorkflow
FUN_NOTIF_CError (FND) Financials FUN FinFunShared
FUN_APPROVError (FND) Financials FUN FinFunShared
FUN_SRC_RULError (FND) Financials FUN FinFunWorkflow
FUN_ERROR_RError (FND) Financials FUN FinFunIntercoTransacti
GL_POST_OTHError (FND) Financials GL FinGlProgramMisc
XCC_DASH_N Error (FND) Financials XCC FinCcSetup

XCC_HYP_AD Error (FND) Financials XCC FinCcSetup
XCC_ENG_UNError (FND) Financials XCC FinCcSetup
XCC_ENG_SY Error (FND) Financials XCC FinCcSetup
XCC_ENG_PR Error (FND) Financials XCC FinCcSetup
XCC_CB_RC_ Error (FND) Financials XCC FinCcSetup
XCC_ENG_CR Error (FND) Financials XCC FinCcSetup
XCC_ENG_PO Error (FND) Financials XCC FinCcSetup
XCC_ENG_GE Error (FND) Financials XCC FinCcSetup
XCC_BPS_INV Error (FND) Financials XCC FinCcSetup
XCC_CB_RC_ Error (FND) Financials XCC FinCcSetup
XCC_CB_RT_UError (FND) Financials XCC FinCcSetup
XLA_TAB_CCI Error (FND) Financials XLA FinXlaTrAccBuilder

XLA_TAB_FUNError (FND) Financials XLA FinXlaTrAccBuilder
XLA_AP_FATAError (FND) Financials XLA FinXlaSharedObj
XLA_AP_TECHError (FND) Financials XLA FinXlaSharedObj
XLA_COMMON
Error (FND) Financials XLA FinXlaSharedStp
XLA_TAB_CANError (FND) Financials XLA FinXlaTrAccBuilder
XLA_TAB_CMPError (FND) Financials XLA FinXlaAMSetup
XLA_AP_FATAError (FND) Financials XLA FinXlaSharedObj
XLA_AP_CMA Error (FND) Financials XLA FinXlaSharedObj
GTG_FILE_ST Error (FND) GRC GTG GrcCore

GTG_GRCCR_ Error (FND) GRC GTG GrcCore
GTG_GRCCR_ Error (FND) GRC GTG GrcCore
GTG_CONTENError (FND) GRC GTG GrcCore
GTG_FRC_IM Error (FND) GRC GTG GrcCore
ANC_PAY_INTError (FND) HCM ANC HcmGblAbsencesProces
ASE_PWD_MGError (FND) HCM ASE HcmApplicationsSecuri
ASE_RESET_P Error (FND) HCM ASE HcmApplicationsSecuri
ASE_CERT_DEError (FND) HCM ASE HcmApplicationsSecuri
ASE_CERT_EX Error (FND) HCM ASE HcmApplicationsSecuri

ASE_ROLE_NOError (FND) HCM ASE HcmApplicationsSecuri
ASE_CERT_SAError (FND) HCM ASE HcmApplicationsSecuri
ASE_CERT_IMError (FND) HCM ASE HcmApplicationsSecuri
ASE_CERT_CS Error (FND) HCM ASE HcmApplicationsSecuri
BEN_BILL_SYSError (FND) HCM BEN HcmBenefitsTop
CMP_SAL_EF Error (FND) HCM CMP HcmCompSalaryTop
CMP_PLANS_ Error (FND) HCM CMP HcmCompPlans
CMP_VC_ALL Error (FND) HCM CMP HcmCompVarCompTop

CMP_SAL_IN Error (FND) HCM CMP HcmCompSalaryTop
CMP_SAL_AC Error (FND) HCM CMP HcmCompSalaryTop
CMP_SAL_CREError (FND) HCM CMP HcmCompSalaryTop
CMS_TCS_UNError (FND) HCM CMS HcmCompTotalCompTo
CMS_CMN_PRError (FND) HCM CMS HcmCompTotalCompTo
CMS_TCS_XMLError (FND) HCM CMS HcmCompTotalCompTo
EHW_CONN_OError (FND) HCM EHW HcmEmployeeWellness
FF_FFCR_DBI_Error (FND) HCM FF HcmFormulaCore
FF_FFCR_ARR Error (FND) HCM FF HcmFormulaCore
FF_FFCR_ARR Error (FND) HCM FF HcmFormulaCore
FF_FFCR_DA Error (FND) HCM FF HcmFormulaCore

FF_33286_MAError (FND) HCM FF HcmFormulaCore
FFSY789_ALI Error (FND) HCM FF HcmFormulaCore
FF_FFCR_BADError (FND) HCM FF HcmFormulaCore
FF_FFCR_DAT Error (FND) HCM FF HcmFormulaCore
FF_34999_W Error (FND) HCM FF HcmFormulaCore
FFT78_PLACE Error (FND) HCM FF HcmFormulaCore
FFPLU01_ASS Error (FND) HCM FF HcmFormulaCore
FF_FFCR_INP Error (FND) HCM FF HcmFormulaCore
FF_FFCR_BA Error (FND) HCM FF HcmFormulaCore
FFX18_PLSQL Error (FND) HCM FF HcmFormulaCore
FF_FFCR_OUTError (FND) HCM FF HcmFormulaCore
FF_FFCR_ORAError (FND) HCM FF HcmFormulaCore
FF_33289_COError (FND) HCM FF HcmFormulaCore

FF_FFCR_DAT Error (FND) HCM FF HcmFormulaCore
HMO_PROCESError (FND) HCM HMO HcmWorkforceModelin
HNS_PRMSS_ Error (FND) HCM HNS HnsIncidents
HRC_DEEP_LI Error (FND) HCM HRC HcmCommonTop
HRC_CCORE_VError (FND) HCM HRC HcmCommonCore
HRC_CCORE_KError (FND) HCM HRC HcmCommonCore
HRC_CCORE_ Error (FND) HCM HRC HcmCommonCore
HRC_CCORE_ Error (FND) HCM HRC HcmCommonCore
HRC_DE_BLO Error (FND) HCM HRC HcmCommonDateEffecti

HRC_DE_BLO Error (FND) HCM HRC HcmCommonDateEffecti
HRC_CCORE_CError (FND) HCM HRC HcmCommonCore
HRC_EVT_PU Error (FND) HCM HRC HcmCommonEvents
HRC_EVT_GROError (FND) HCM HRC HcmCommonEvents
HRC_EVT_PUBError (FND) HCM HRC HcmCommonEvents
HRC_EVT_PU Error (FND) HCM HRC HcmCommonEvents
HRC_DE_INTEError (FND) HCM HRC HcmCommonDateEffecti
HRG_GOAL_PLError (FND) HCM HRG HcmGoalCore
HRT_AUTHENTError (FND) HCM HRT HcmProfileTop
HRT_MIG_NOError (FND) HCM HRT HcmProfileTop

HRW_SDL_ES Error (FND) HCM HRW HcmEntSetupCfgTop
HTS_RESET_R Error (FND) HCM HTS HcmSchedulesTop
HTS_SCH_PUBError (FND) HCM HTS HcmSchedulesTop
HTS_TEAMMOError (FND) HCM HTS HcmSchedulesTop
HWM_RBE_DEError (FND) HCM HWM HcmWfmTop
HWM_MANAGE
Error (FND) HCM HWM HcmWfmTop
HWM_TL_VALIError (FND) HCM HWM HcmWfmTop
HWM_RBE_APError (FND) HCM HWM HcmWfmTop
HWP_PROCESError (FND) HCM HWP HcmPredictivesTop
HWR_SAVE_UError (FND) HCM HWR WorkforceReputation
HXT_TCS_SUBError (FND) HCM HXT HcmTimeTop

HXT_TCS_APPError (FND) HCM HXT HcmTimeTop
HXT_TCS_DELError (FND) HCM HXT HcmTimeTop
HXT_SUBMIT_Error (FND) HCM HXT HcmTimeTop
HXT_LOAD_TCError (FND) HCM HXT HcmTimeTop
HXT_DELETE_Error (FND) HCM HXT HcmTimeTop
HXT_SAVE_TCError (FND) HCM HXT HcmTimeTop
PAY_PAYPRO Error (FND) HCM PAY HcmBatchProcessCore
PAY_PAYJAV Error (FND) HCM PAY HcmBatchProcessCore
PAY_HPCM_L Error (FND) HCM PAY HcmPayCore
PAY_ELMAINTError (FND) HCM PAY HcmPayElementTop
PAY_HPCM_I Error (FND) HCM PAY HcmPayCore
PAY_ELEEN_ Error (FND) HCM PAY HcmPayElementTop

PAY_ELEEN_PError (FND) HCM PAY HcmPayElementTop
PAY_ADJ_GRPError (FND) HCM PAY HcmPayBalTop
PAY_ADJ_INV Error (FND) HCM PAY HcmPayBalTop
HR_7423_DT_Error (FND) HCM PAY HcmPayCore
PAY_BAL_DB Error (FND) HCM PAY HcmPayBalTop
HR_7329_ELEError (FND) HCM PAY HcmPayElementTop
PAY_ADJ_GRPError (FND) HCM PAY HcmPayBalTop
PAY_ELE_CRI Error (FND) HCM PAY HcmPayElementTop
HR_6880_HRPError (FND) HCM PAY HcmBatchProcessCore
HR_7275_PAYError (FND) HCM PAY HcmBatchProcessCore

HR_6882_HRPError (FND) HCM PAY HcmBatchProcessCore
PAY_PRA_NOTError (FND) HCM PAY HcmPayCore
HR_7273_PA Error (FND) HCM PAY HcmBatchProcessCore
HR_6153_ALLError (FND) HCM PAY HcmPayCore
HR_6881_HR Error (FND) HCM PAY HcmBatchProcessCore
HR_UNRECOGN
Error (FND) HCM PAY HcmBatchProcessCore
PER_SECUR_I Error (FND) HCM PER HcmSecurity
PER_INTG_ES Error (FND) HCM PER HcmCoreIntegrations
PER_SECUR_ Error (FND) HCM PER HcmSecurity
PER_POS_FLAError (FND) HCM PER HcmWorkPositions
PER_CHK_I9 Error (FND) HCM PER HcmChecklists
HES_DEFAULTError (FND) Higher EducatHES HedHesCommonSetup
HES_INVALID Error (FND) Higher EducatHES HedHesPayments

HES_PROXY_GError (FND) Higher EducatHES HedHesPayments
HES_PAY_INVError (FND) Higher EducatHES HedHesPayments
HES_PAY_CONError (FND) Higher EducatHES HedHesPayments
HEY_NUR_MISError (FND) Higher EducatHEY HedHeyAccess
HEY_POPSELEError (FND) Higher EducatHEY HedHeyPopulationMgm

HEY_NUR_MI Error (FND) Higher EducatHEY HedHeyConstituentSet
HEY_EVENT_ Error (FND) Higher EducatHEY HedHeyEvents
HEY_EVENT_PError (FND) Higher EducatHEY HedHeyEvents

HEY_EVENT_ Error (FND) Higher EducatHEY HedHeyEvents
HEY_EVENT_SError (FND) Higher EducatHEY HedHeyEvents
CN_ORA_APPLError (FND) IC CN IcCnSharedTop
CN_CPSTP_FOError (FND) IC CN IcCnSharedTop

CN_CLNDR_BIError (FND) IC CN IcCnSharedTop
CN_CPSTP_F Error (FND) IC CN IcCnSharedTop
PO_APPRVL_CError (FND) Procurement PO PrcPoCommonPo
PO_B2B_COMError (FND) Procurement PO PrcPoCommonPo
PO_XCC_FATAError (FND) Procurement PO PrcPoCommonPo
PO_APPRVL_TError (FND) Procurement PO PrcPoCommonPo
PO_COMM_PD
Error (FND) Procurement PO PrcPoCommonPo
PO_ALL_NO_LError (FND) Procurement PO PrcPoCommonPo
PON_PO_CRE Error (FND) Procurement PON PrcPonCommon
PON_NEG_CREError (FND) Procurement PON PrcPonCommon
PON_APPROVError (FND) Procurement PON PrcPonCommon
PON_PUBLISHError (FND) Procurement PON PrcPonCommon
POR_APPROVWarning (FNDProcurement POR PrcPorCommonPor
POR_LOAD_UError (FND) Procurement POR PrcPorCommonPor
POR_UNEXPE Error (FND) Procurement POR PrcPorCommonPor
POR_MUPDATError (FND) Procurement POR PrcPorCommonPor

POR_APPROVError (FND) Procurement POR PrcPorCommonPor
POR_LOAD_CRError (FND) Procurement POR PrcPorCommonPor
POR_LOAD_C Error (FND) Procurement POR PrcPorCommonPor
POR_LOAD_C Error (FND) Procurement POR PrcPorCommonPor
POZ_CR_COPYWarning (FNDProcurement POZ PrcPozCommonPoz
POZ_SYSTEM Error (FND) Procurement POZ PrcPozCommonPoz
POZ_CR_SEL_ Warning (FNDProcurement POZ PrcPozCommonPoz
PJC_PLSQL_G Error (FND) Projects PJC PjcCommon

PJC_CAP_OVRError (FND) Projects PJC PjcCommon
PJC_CAP_XFR Error (FND) Projects PJC PjcCommon
PJC_CAP_ASS Error (FND) Projects PJC PjcCommon
PJC_CAP_CRE Error (FND) Projects PJC PjcCommon
PJC_TXN_REQError (FND) Projects PJC PjcCommon

PJC_TXN_TBC Error (FND) Projects PJC PjcCommon
PJC_CC_TP_E Error (FND) Projects PJC PjcCommon
PJC_AL_FATA Error (FND) Projects PJC PjcCommon
PJE_INTERNA Error (FND) Projects PJE PjeCommon
PJF_STATE_D Error (FND) Projects PJF PjfCommon
PJF_PROJECT Error (FND) Projects PJF PjfCommon
PJF_INVALID Error (FND) Projects PJF PjfCommon
PJF_GENERIC Error (FND) Projects PJF PjfCommon

PJF_NO_BI_S Error (FND) Projects PJF PjfCommon
PJF_PROJ_NOError (FND) Projects PJF PjfCommon
PJF_PROJ_BU Error (FND) Projects PJF PjfCommon
PJF_PROJ_N Error (FND) Projects PJF PjfCommon
PJF_NO_CREAError (FND) Projects PJF PjfCommon
PJF_ORG_DE Error (FND) Projects PJF PjfCommon
PJF_PROJ_PE Error (FND) Projects PJF PjfCommon
PJF_ORG_DENError (FND) Projects PJF PjfCommon

PJF_PROJ_AT Error (FND) Projects PJF PjfCommon
PJF_PROJ_FI Error (FND) Projects PJF PjfCommon
PJF_SRC_RO Error (FND) Projects PJF PjfCommon
PJF_INVALID_Error (FND) Projects PJF PjfCommon
PJF_INSERT_ Error (FND) Projects PJF PjfCommon
PJF_ADDING_Error (FND) Projects PJF PjfCommon
PJO_XCC_GENError (FND) Projects PJO PjoCommon
PJO_XFACE_GError (FND) Projects PJO PjoCommon
PJR_INDEX_BUError (FND) Projects PJR PjrCommon

PJR_INVALID Error (FND) Projects PJR PjrCommon
PJS_ESSBASE Error (FND) Projects PJS PjsCommon
PJS_KPI_ESS Error (FND) Projects PJS PjsCommon
PJS_UDB_OSNError (FND) Projects PJS PjsCommon

PSC_BL_REG_Error (FND) Public Sector PSC_BL PscBlAppIntake
PSC_CC_ACTL Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_CFT_ Error (FND) Public Sector PSC_CC PscCcReports
PSC_CC_SET Error (FND) Public Sector PSC_CC PscCcTradeLicenses
PSC_CC_LIC Error (FND) Public Sector PSC_CC PscCcTradeLicenses
PSC_CC_ARCHError (FND) Public Sector PSC_CC PscCcArchitecture
PSC_CC_AUT Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_ACCTError (FND) Public Sector PSC_CC PscCcAccountingTop

PSC_CC_CARTError (FND) Public Sector PSC_CC PscCcPaymentCart
PSC_CC_RPT_Error (FND) Public Sector PSC_CC PscCcReports
PSC_CC_GEN_Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_FOU Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_FOU Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_SETUError (FND) Public Sector PSC_CC PscCcFoundationSetup

PSC_CC_CAR Error (FND) Public Sector PSC_CC PscCcPaymentCart

PSC_CC_INVAError (FND) Public Sector PSC_CC PscCcPaymentTop
PSC_CC_DLG Error (FND) Public Sector PSC_CC PscCcManagedAccts
PSC_CC_ACC Error (FND) Public Sector PSC_CC PscCcAccountingTop
PSC_CC_GEN Error (FND) Public Sector PSC_CC PscCcFoundationSetup

PSC_CC_BIP_ Error (FND) Public Sector PSC_CC PscCcFoundationSetup
PSC_CC_CASHError (FND) Public Sector PSC_CC PscCcPaymentTop
PSC_CE_INTA Error (FND) Public Sector PSC_CE PscCeIntake
PSC_PER_FNDError (FND) Public Sector PSC_PER PscPerFoundation
PSC_PER_INS Error (FND) Public Sector PSC_PER PscPerInspections
PSC_PER_FEE Error (FND) Public Sector PSC_PER PscPerFees

ACA_NO_CRE Error (FND) SCM ACA AcaChanges
ACA_INVALID Error (FND) SCM ACA AcaCommon
ACA_ITEM_CLError (FND) SCM ACA AcaItems
ACA_AU_VO_Error (FND) SCM ACA AcaAuIntegration
ACA_AU_COUError (FND) SCM ACA AcaAuIntegration
ACA_AU_LINKError (FND) SCM ACA AcaAuIntegration

ACA_AU_OBJEError (FND) SCM ACA AcaAuIntegration
ACA_AU_VO_IError (FND) SCM ACA AcaAuIntegration
ACA_AU_ENTIError (FND) SCM ACA AcaAuIntegration
ACA_AU_NO_Error (FND) SCM ACA AcaAuIntegration
ACA_AU_INV Error (FND) SCM ACA AcaAuIntegration
ACA_AU_INVAError (FND) SCM ACA AcaAuIntegration
ACA_AU_INVAError (FND) SCM ACA AcaAuIntegration
ACD_MAPPIN Error (FND) SCM ACD AcdConcepts

ACN_RQMNT_Error (FND) SCM ACN AcnRequirements
ACN_RQMNT_I
Error (FND) SCM ACN AcnRequirements
ACN_BIP_REQError (FND) SCM ACN AcnRequirements
CJM_CMN_SQError (FND) SCM CJM CjmCommon
CJM_CREATE_Error (FND) SCM CJM CjmClaims
CMR_MISSIN Error (FND) SCM CMR CmrMonitorReceiptAcc
CST_CADJ_SA Error (FND) SCM CST CstCostProcessor
CST_VUNIT_VError (FND) SCM CST CstCoreSetup
CST_VUNIT_VError (FND) SCM CST CstCoreSetup
CST_VUNIT_K Error (FND) SCM CST CstCoreSetup

CST_UTIL_C Error (FND) SCM CST CstCommon
DOO_WB_REQError (FND) SCM DOO DooWorkbench
DOO_CMN_INError (FND) SCM DOO DooCommon
DOO_MFRCMN
Error (FND) SCM DOO DooCommon
DOO_MFRCMN
DOO_MFRCMN
DOO_MFRCMN
DOO_NOTIFY_Error (FND) SCM DOO DooCommon
DOO_BIP_FAI Error (FND) SCM DOO DooCommon

EDR_BPM_TAError (FND) SCM EDR EdrCore
EDR_INLINE_ Error (FND) SCM EDR EdrCore
EDR_EREC_ESError (FND) SCM EDR EdrCore
EDR_ESS_SUBError (FND) SCM EDR EdrCore
EDR_EREC_DEError (FND) SCM EDR EdrCore
EGI_BATCH_DError (FND) SCM EGI EgiItemImport
EGO_INSUFFICError (FND) SCM EGO EgoChangeManagemen
EGP_ITEMCLAError (FND) SCM EGP EgpItemClasses
EGP_SOA_CMError (FND) SCM EGP EgpCommon

EGP_ITEMCLAError (FND) SCM EGP EgpItemClasses
EGP_ITEM_CLError (FND) SCM EGP EgpItemClasses
EGP_INVALID Error (FND) SCM EGP EgpItems
FOM_CM_DISError (FND) SCM FOM FomManageOrders
FOM_CM_CON
Error (FND) SCM FOM FomManageOrders
FOM_CM_CANError (FND) SCM FOM FomManageOrders
FOM_CM_REVError (FND) SCM FOM FomManageOrders
FOM_UNEXPEC
Error (FND) SCM FOM FomImportOrders
FOS_EVENT_EError (FND) SCM FOS FosEventManagement
FOS_TASK_PRError (FND) SCM FOS FosOrchestrationProces
FOS_EVENT_PError (FND) SCM FOS FosEventManagement
FOS_WSH_TP Error (FND) SCM FOS FosOrchestrationProces
FOS_DOO_PRIError (FND) SCM FOS FosOrchestrationProces
FOS_BUSEVENError (FND) SCM FOS FosEventManagement

FOS_TRIGGERError (FND) SCM FOS FosOrchestrationProces
INV_CST_SER Error (FND) SCM INV InvCommon
INV_INVALID_Error (FND) SCM INV InvCoreSetup
INV_SEEDDATError (FND) SCM INV InvCoreSetup
INV_CRT_LOCError (FND) SCM INV InvCommon
INV_CCT_ERR Error (FND) SCM INV InvCounting
INV_MATAV_ Error (FND) SCM INV InvMaterialAvailability
INV_COMMIT_Error (FND) SCM INV InvCommon
INV_EXCEPTI Error (FND) SCM INV InvCommon
INV_QRY_EXEError (FND) SCM INV InvCommon
INV_CCEOI_E Error (FND) SCM INV InvCounting

INV_MATAV_SError (FND) SCM INV InvMaterialAvailability
INV_QRY_QTYError (FND) SCM INV InvMaterialAvailability
INV_LOCK_REError (FND) SCM INV InvMaterialAvailability
INV_TREE_R Error (FND) SCM INV InvMaterialAvailability
INV_PRINT_PIError (FND) SCM INV InvPicking
INV_ERR_CREError (FND) SCM INV InvMaterialTransaction
INV_TRANSFEError (FND) SCM INV InvMaterialAvailability

INV_TREE_N Error (FND) SCM INV InvMaterialAvailability
INV_LOCK_TRError (FND) SCM INV InvMaterialAvailability
MSC_PROTEC Warning (FNDSCM MSC MscCommon
MSC_DM_ENGError (FND) SCM MSC MscCommon
MSC_SOP_ENError (FND) SCM MSC MscCommon
MSC_SOP_MGError (FND) SCM MSC MscCommon

MSC_SOP_PL Error (FND) SCM MSC MscCommon
MSC_SOP_WSError (FND) SCM MSC MscCommon
MSC_LD_MSRWarning (FNDSCM MSC MscCommon
MSC_LD_MSR_
Error (FND) SCM MSC MscCommon
MSC_BM_PLAN
MSC_SOP_LO Error (FND) SCM MSC MscCommon

MSC_SOP_ENG
MSC_SOP_ENG

MSC_SOP_ENG
MSC_PCENG_Error (FND) SCM MSC MscCommon
MSC_CONFIG_Error (FND) SCM MSC MscCommon
MSC_PIVOT_TError (FND) SCM MSC MscCommon
MSC_GOPENGError (FND) SCM MSC MscCommon
MSC_CONFIG Error (FND) SCM MSC MscCommon
MSC_CONFIG_Error (FND) SCM MSC MscCommon
MSC_CREATE Error (FND) SCM MSC MscCommon

MSC_REFRES Error (FND) SCM MSC MscCommon
MSC_DM_EN Error (FND) SCM MSC MscCommon
MSC_DM_EN Error (FND) SCM MSC MscCommon

QP_ALGM_P Error (FND) SCM QP QpExecution
RCS_SCHED_EError (FND) SCM RCS RcsCalendars
VCS_CM_LOAError (FND) SCM VCS VcsCommon
WIE_WO_NO_Error (FND) SCM WIE WieWorkOrders
WIE_IMP_UN Error (FND) SCM WIE WieMassImport

WIE_WOOT_DError (FND) SCM WIE WieOperationTransacti
WSH_PS_DOCError (FND) SCM WSH WshShipConfirm
WSH_PR_REVError (FND) SCM WSH WshPickRelease

WSH_BOL_DOError (FND) SCM WSH WshShipConfirm
WSH_RTN_TOError (FND) SCM WSH WshShipConfirm
WSH_CI_DOC Error (FND) SCM WSH WshShipConfirm
WSH_SHIP_COError (FND) SCM WSH WshShipConfirm
WSH_LINE_L Error (FND) SCM WSH WshShipConfirm
WSH_LINE_L Error (FND) SCM WSH WshShipConfirm
WSH_UNEXP_Error (FND) SCM WSH WshShipConfirm
WSH_SPKWV_F
Error (FND) SCM WSH WshPickRelease
ASM_TASK_R Error (FND) Setup ASM ASM
ASM_WEB_SRV
Error (FND) Setup ASM ASM
ASM_TM_DOM
ASM_RTF_AU Error (FND) Setup ASM ASM
ASM_RTF_UNError (FND) Setup ASM ASM
ASM_TM_INVError (FND) Setup ASM ASM
ASM_MIG_ERError (FND) Setup ASM ASM
ASM_OFFNG_Error (FND) Setup ASM ASM
ASM_OFFNG_Error (FND) Setup ASM ASM
ASM_MIG_ERR
ASM_MIG_SERError (FND) Setup ASM ASM
ASM_IP_TAS Error (FND) Setup ASM ASM

ASM_IP_SCO Error (FND) Setup ASM ASM
ASM_IP_TAS Error (FND) Setup ASM ASM
ASM_CMSTP_A
ASM_FILT_IN Error (FND) Setup ASM AsmCommonSetup
ASM_PORTLE Error (FND) Setup ASM ASM
ASM_TASK_D Error (FND) Setup ASM ASM

Message Number Diagnostic Setting
ATK-3315011 Diagnostic Log
ATK-3315001 Incident
FND-9 Incident
FND-12 Incident
FND-16 Incident
FND-13 Incident
FND-14 Incident
FND-10 Incident
FND-17 Incident
FND-1 Incident
FND-3 Incident
FND-4 Incident
FND-5 Incident
FND-2 Incident
FND-15 Incident
FND-11 Incident
FTA-4095016 Incident
CSO-555042 Diagnostic Log

CSO-555011 Incident
CSO-555038 Incident
CSO-555040 Incident
CSO-555002 Incident
CSO-555000 Incident
CSO-555003 Incident
CSO-555017 Incident
CSO-555015 Incident
CSO-555001 Incident
CSO-555006 Incident
CSO-555020 Incident
CSO-555016 Incident
CSO-555004 Incident
CSO-555005 Incident
CSO-555018 Incident
CSO-555013 Incident
CSO-555014 Incident
CSO-555009 Incident
CSO-555007 Incident
CSO-555019 Incident
CSO-555008 Incident
CSO-555012 Incident
CSO-555030 Incident
CSO-555026 Incident
CSO-555029 Incident
CSO-555025 Incident
CSO-555031 Incident
CSO-555021 Incident
CSO-555034 Incident
CSO-555032 Incident
CSO-555027 Incident
CSO-555028 Incident
CSO-555024 Incident
CSO-555033 Incident
CSO-555022 Incident
FOD-3480006 Diagnostic Log
FOD-3480018 Incident
HZ-120666 Diagnostic Log
HZ-120669 Diagnostic Log

LOY-5595411 Incident
MCT-180012 Incident
MCT-180013 Incident
MKL-315111 Diagnostic Log
MKL-315020 Incident
MKT-285044 Diagnostic Log

MKT-285166 Incident
MKT-285158 Incident
MKT-285211 Incident
MKT-285021 Incident
MKT-285167 Incident
MKT-285040 Incident
MOO-450199 Diagnostic Log
MOO-450005 Diagnostic Log
MOT-480551 Diagnostic Log
MOT-480519 Incident
MOT-480325 Incident
MOT-480336 Incident
MOT-480249 Incident
MOW-225256 Diagnostic Log


MOW-225252 Incident
MOW-225234 Incident
MOW-225099 Incident
MOW-225036 Incident
MOW-225024 Incident
MOW-225067 Incident
MOW-225026 Incident
MOW-225049 Incident
MOW-225093 Incident
MOW-225031 Incident
MOW-225033 Incident
MOW-225035 Incident
MOW-225186 Incident
MOW-225015 Incident
MOW-225048 Incident
OSS-6075180 Diagnostic Log
QSC-375026 Incident
QSC-375027 Incident
QSC-375024 Incident
SVC-5295235 Diagnostic Log

SVC-5295300 Incident
ZCA-210257 Diagnostic Log
ZCA-210181 Incident
ZCA-210027 Incident
ZCA-210125 Incident
ZCH-105095 Incident
ZCM-3090096 Incident
ZCQ-90050 Diagnostic Log
ZCQ-90051 Diagnostic Log
ZCX-3075183 Diagnostic Log







ZCX-3075206 Incident
ZOC-360030 Diagnostic Log
ZOC-360040 Incident
ZOC-360001 Incident
ZOC-360003 Incident
ZOC-360004 Incident
ZOC-360044 Incident
ZOE-435045 Diagnostic Log
ZOE-435057 Diagnostic Log
ZOE-435013 Incident
ZOE-435018 Incident
ZOE-435008 Incident
ZOE-435016 Incident
ZOE-435021 Incident
ZOE-435047 Incident
ZOE-435024 Incident
ZOE-435046 Incident
ZOE-435029 Incident
ZOE-435010 Incident
ZPS_365-5685039 Diagnostic Log

ZPS_365-5685035 Incident
ZSF-465093 Incident
ZSF-465081 Incident
ZSF-465080 Incident
ZSO-3630020 Diagnostic Log
ZSP-3195028 Incident
AP-810540 Diagnostic Log
AP-811098 Incident
AP-810391 Incident
AP-810102 Incident
AP-810332 Incident
AP-810483 Incident
AP-810101 Incident
AP-810023 Incident
AP-810098 Incident
AP-810460 Incident
AP-810486 Incident
AP-810361 Incident
AP-810485 Incident
AP-810363 Incident
AP-810484 Incident
AP-810362 Incident
AP-810367 Incident
AP-810364 Incident
AR-856541 Diagnostic Log
AR-857772 Incident
AR-857095 Incident
CE-660281 Diagnostic Log
CE-660243 Diagnostic Log
CE-660330 Incident
EXM-630323 Diagnostic Log

EXM-630124 Incident
EXM-630377 Incident
EXM-630115 Incident
EXM-630099 Incident
EXM-630320 Incident
FUN-720475 Diagnostic Log
FUN-720529 Incident
FUN-720244 Incident
GL-782078 Incident
XCC-675333 Diagnostic Log

XCC-675322 Incident
XCC-675393 Incident
XCC-675327 Incident
XCC-675379 Incident
XCC-675392 Incident
XCC-675323 Incident
XCC-675394 Incident
XCC-675332 Incident
XCC-675420 Incident
XCC-675378 Incident
XCC-675404 Incident
XLA-870924 Diagnostic Log

XLA-870106 Incident
XLA-870143 Incident
XLA-870347 Incident
XLA-870557 Incident
XLA-870559 Incident
XLA-870576 Incident
XLA-870142 Incident
XLA-870136 Incident
GTG-3660187 Diagnostic Log

ANC-3405066 Diagnostic Log
ASE-4335095 Diagnostic Log

ASE-4335028 Incident
BEN-991186 Diagnostic Log
CMP-1005120 Diagnostic Log
CMP-1005209 Incident
CMS-3240069 Diagnostic Log
EHW-5100007 Incident
FF-1605149 Incident
FF-1605150 Incident
FF-1605088 Incident
FF-1605085 Incident
FF-1605074 Incident
FF-1605061 Incident
FF-1605059 Incident
FF-1605058 Incident
FF-1605037 Incident
FF-1605048 Incident
FF-1605053 Incident
FF-1605023 Incident
FF-1605051 Incident
FF-1605070 Incident
FF-1605060 Incident
FF-1605155 Incident
FF-1605073 Incident
FF-1605071 Incident
FF-1605056 Incident
FF-1605168 Incident
FF-1605148 Incident
FF-1605165 Incident
HMO-3150017 Diagnostic Log
HNS-4110008 Diagnostic Log
HRC-1035753 Diagnostic Log

HRC-1035069 Incident
HRG-3120373 Incident
HRT-975255 Incident
HRT-975195 Incident
HRW-1050038 Incident
HTS-1680088 Incident
HWM-3750116 Diagnostic Log
HWM-3750122 Incident
HWP-3270002 Diagnostic Log
HWR-4260040 Incident
HXT-1665086 Diagnostic Log

HXT-1665064 Incident
PAY-1635269 Incident
PER-1531141 Diagnostic Log
PER-1532425 Incident
HES-5220170 Diagnostic Log
HES-5220168 Diagnostic Log

HES-5220190 Incident
HEY-5190186 Diagnostic Log
HEY-5190166 Incident
CN-1575605 Diagnostic Log
CN-1575389 Incident
CN-1575483 Incident
CN-1575388 Incident
PO-2055548 Diagnostic Log
PO-2055097 Incident
PO-2055040 Incident
PON-2085635 Diagnostic Log
PON-2085792 Incident
POR-2010710 Diagnostic Log
POR-2010324 Incident
POZ-2130485 Diagnostic Log
PJC-2220695 Diagnostic Log

PJC-2220261 Incident
PJE-3990023 Incident
PJF-2235052 Diagnostic Log

PJF-2235931 Incident
PJO-2205092 Diagnostic Log
PJO-2205213 Incident
PJR-2295037 Incident
PJR-2295042 Incident
PJS-2265083 Diagnostic Log
PJS-2265086 Incident
PSC_BL-5955031 Diagnostic Log
PSC_CC-6030486 Diagnostic Log



PSC_CC-6030390 Incident
PSC_CE-5940016 Diagnostic Log
PSC_PER-5925144 Diagnostic Log
PSC_PER-5925110 Diagnostic Log
PSC_PER-5925104 Incident
ACA-3600277 Diagnostic Log

ACA-3600087 Incident
ACD-3555076 Diagnostic Log

ACN-3540011 Diagnostic Log
CJM-6135064 Diagnostic Log
CJM-6135109 Incident
CMR-3180038 Incident
CST-2385167 Diagnostic Log
CST-2385237 Incident
DOO-2685657 Incident
EDR-2580007 Incident
EGI-2760056 Incident
EGO-2745643 Diagnostic Log
EGP-2775749 Diagnostic Log
EGP-2775888 Incident
FOM-4515065 Diagnostic Log
FOM-4515343 Incident
FOS-3465291 Diagnostic Log
FOS-3465303 Incident
INV-2416634 Diagnostic Log
INV-2416458 Incident
MSC-2806088 Diagnostic Log

MSC-2806026 Incident
QP-2715641 Incident
RCS-3360269 Incident
VCS-5490145 Diagnostic Log
WIE-4425194 Diagnostic Log
WIE-4425195 Incident
WIE-4425481 Incident
WSH-2460833 Diagnostic Log

WSH-2460891 Incident
ASM-75277 Diagnostic Log



Fusion Message Text
The notification was not updated. Contact your help
desk.
The notification was not created. Contact your help

desk.
desk.
The notification was not created. Contact your help

desk.
desk.
The unique key for the help window is invalid. Try

performing a search directly in Applications Help.
Links to help cannot be displayed. Contact your help
desk.
The Watchlist has timed out. Contact your help desk.
The unique key for this help window is invalid. You can
manage help for another help window by specifying a
different help key, hierarchy, and help location.
A map is currently unavailable. Contact your help desk.
Oracle Fusion Applications Help is not available. Try

again later.
Your process {PROGRAM_NUMBER} has completed with

errors. Contact your help desk.
You don't have permission to create a new value.
Contact your help desk.
You don't have permission to delete this record. Contact
your help desk.
You don't have permission to access this information.
You don't have the required permission. You can request
that your help desk change your security settings.
The default flexfield query didn't return any rows.
Your user profile {USER_PROFILE} can't be read. Contact

your help desk.
The process {PROGRAM_NAME} wasn't submitted
because of an error. Contact your help desk.
The process {PROGRAM_NAME} failed because of an
error. Contact your help desk.
An error occurred while establishing the server
connection to the {SERVER} server. Contact your help
desk.
An error occurred while establishing the server
connection. Contact your help desk.
An error occurred. Contact your help desk.
Your process failed because of a scheduling error.
An error occurred with the file {FILENAME}. Contact your
help desk.
Hiring functionality is not available because of internal
errors in the hiring server. Contact your help desk.
A configuration error has occurred. Contact your help

desk.
The knowledge application credentials aren't configured

correctly. Contact your help desk.
The attachments of the article couldn't be displayed

because of an attachment processing error. Contact your
help desk.
Knowledge search isn't performing correctly. Contact
your help desk.
Search has no data available. Contact your help desk.
The locale object {LOCALE_CODE} couldn't be retrieved.

The content type {REFKEY} couldn't be retrieved.
The categories couldn't be retrieved. Contact your help

desk.
The knowledge application isn't available at this time.

Try again later. If the issue persists, contact your help
desk.
The locale object {LOCALE_CODE} couldn't be updated.

The locale objects couldn't be updated. Contact your

help desk.
The knowledge repository couldn't be found. Contact

your help desk.
The clean-up step of the import process couldn't be
completed because a concept ceased to be available
during the import. Contact your help desk.
One or more concepts couldn't be transferred. Contact

your help desk.
You can't perform this operation because you don't have

the required privileges. Contact your help desk.
No locale objects could be retrieved. Contact your help

desk.
The locales couldn't be updated because one or more of

the locale record IDs are empty or invalid in the
exported configuration file. Contact your help desk.
The concept domain couldn't be retrieved. Contact your

help desk.
The locale objects couldn't be retrieved. Contact your

help desk.
No active locale objects could be retrieved. Contact your

help desk.
One or more concepts couldn't be transferred. Contact
your help desk.
The search dictionary maintenance status couldn't be

found. Contact your help desk.
The search dictionary version couldn't be found. Contact

your help desk.
The content type {REFKEY} couldn't be updated because

the content field {REFKEY_FIELD} ceased to be available
during the import. Contact your help desk.

its document prefix ID is empty in the exported
configuration file. Contact your help desk.

its name is empty in the exported configuration file.
the locale object {LOCALE_CODE} isn't available during
the import step. Contact your help desk.

the content type {REFKEY} ceased to be available during
the import. Contact your help desk.
The locales couldn't be retrieved. Contact your help

desk.
The roles couldn't be retrieved. Contact your help desk.
The available locales couldn't be retrieved. Contact your

help desk.
This service is temporarily unavailable. Contact your help

desk.
The user groups couldn't be retrieved. Contact your help

desk.
The default locale couldn't be found. Contact your help

desk.
The child nodes couldn't be retrieved. Contact your help
desk.
The products couldn't be retrieved. Contact your help

desk.
The users couldn't be retrieved. Contact your help desk.
The active locales couldn't be retrieved. Contact your

help desk.
A service error occurred. Contact your help desk.
The categories couldn't be retrieved. Contact your help

desk.
This service is unavailable. Contact your help desk.
An application error occurred during the Import Nokia

Geography Data process for country {COUNTRY_NAME}.
An error occurred when enabling forecasting. Contact

your help desk.
The creation of the partner organization failed because

of a system error. Contact your help desk.
An error occurred when compiling the PL/SQL program

unit {NAME}. Contact your help desk.
A database error occurred while updating the
transaction. Contact your help desk.
The global function {SP_GLOBAL_FUNCTION_NAME}
returned a communication data string that wasn't valid.
The service call {RL_GLOBAL_FUNCTION_NAME} failed
while preprocessing reverse lookup data. Contact your
help desk.
The deal registration assignment process failed due to a
system error. Contact your help desk.
An error occurred while updating the lead. Contact your

help desk.
An error occurred while reading from the content
repository. The content may not be available or you
don't have permission to access it. Contact your help
desk.
Uploading of the file selected as an attachment

document failed due to an application error. Contact
your help desk.
Your request couldn't be completed because of an error
with the content management server. Contact your help
desk.
An error occurred while saving content to the content
repository. Contact your help desk.

An error occurred when calling the business intelligence
server. Contact your help desk.
The campaign wasn't sent. Contact your help desk.
Your request can't be completed because the content

repository is unavailable. Contact your help desk.
An error occurred while saving the content to the

content repository. Contact your help desk.
The test email couldn't be sent because of the following
error: {BOLDFISH_ERROR}. Contact your help desk.
A conversion rate doesn't exist to convert the source

currency {SOURCE} to the target currency {TARGET} on
{DATE}. Contact your help desk.
The automatic rule-based assignment failed. Contact
your help desk.
Quota calculations are currently unavailable due to

planned maintenance of territories. Contact your help
desk.
The import files didn't load as expected. Contact your
help desk.
An error occurred within Essbase (message number
{MSG_NUM}). Contact your help desk.
An error occurred while establishing the connection with

Oracle Essbase. Contact your help desk.
An active assignment rule can't be found. Contact your

help desk.
The assignment object view can't be found. Contact your

help desk.
The object to be assigned can't be found. Contact your

help desk.
An active assignment rule set can't be found. Contact

your help desk.
The assignment failed because of invalid values for one
or more mappings that are associated with the mapping
set {MAPPING_SET}. Contact your help desk.
An active assignment rule category can't be found.

The assignment failed because of missing values for one

or more mappings that are associated with the mapping
set {MAPPING_SET}. Contact your help desk.
The assignment failed because of invalid and missing

values for one or more mappings that are associated
with mapping set {MAPPING_SET}. Contact your help
desk.
The assignment attributes for storing the matching

candidates are missing. Contact your help desk.
The attribute used to store the calculated score hasn't

been defined. Contact your help desk.
A qualified candidate can't be found. Contact your help

desk.
An active assignment mapping set or mapping can't be

A relationship between the work object and candidate

object can't be found. Contact your help desk.
The rule set can't be found. Contact your help desk.

An error occurred while retrieving the attribute
{ATTR_NAME} from the candidate object {CO_CODE}.
The primary key information of the object being
assigned is missing. Contact your help desk.
The assignment processing failed because conflicting

rules were found. Contact your help desk.
An error occurred while loading assignment object

{AO_CODE}. Contact your help desk.
An error occurred while processing work object

{AO_CODE} with the identifier {WO_IDENTIFIER}.
The Assign Candidate and the Run Custom Logic options
are disabled. Contact your help desk.
An attribute value for the assignment mapping is

missing. Contact your help desk.
An error occurred while syncing the configuration with
assignment objects and rules. Contact your help desk.
An error occurred while publishing assignment object

and rules. Contact your help desk.
A rule session wasn't available in the rule session pool
for candidate object {CO_CODE}. Contact your help desk.
An application error occurred. Contact your help desk.
An error occurred while executing the rule set

{RULE_SET}. Contact your help desk.
The candidate object display column can't be found.
An error occurred when extracting the assignment
object {AO_CODE} from the rule session. Contact your
help desk.
An error occurred while loading rule set {RULE_SET} into
a rule session. Contact your help desk.
An application error occurred while reading data for
candidate object {CO_CODE}. Contact your help desk.
An error occurred while connecting to the rules

An error occurred while releasing the rule session back
to the rule session pool for object {CO_CODE}. Contact
your help desk.
An error occurred while accessing assignment object
definitions. Contact your help desk.
An error occurred while loading assignment object
{AO_CODE}. Contact your help desk.
An error occurred when calling the translation function
{FUNCTION} and service {CLASS}. Contact your help desk.
An error occurred while saving the rule dictionary.

Preview of the subscription couldn't be generated.
An error occurred while generating the map. Contact
your help desk.
The mapping of hierarchies failed because of an error.

See the log file for details. Contact your help desk.
The service {SERVICE} failed due to an error. Contact

your help desk.
The scheduler can't be opened because of the work
order type that was selected with type code
{WO_ACTIVITY_ID}. Contact your help desk.
No quota has been set up in Oracle Field Service to

support the work order area and type combination.
An error was detected with the registration setup.

The error {ERROR_ID} occurred at the following time:

{ERROR_DATE}. Contact your help desk.
The connection to Field Service couldn't be made.
The integration message with the message code

{INTEGRATION_MESSAGE_CODE} doesn't exist. Contact
your help desk.
An error occurred while creating an action plan from a
template. Contact your help desk.
An error occurred while discarding the action plan.

The email couldn't be sent due to issues with the mail

server. Contact your help desk.
The predefined data for the work order tasks isn't

loaded. Contact your help desk.
An error occurred while processing the outbound
message. Contact your help desk.
The person record wasn't found for the selected party.

An assignment error occurred while processing the work

offer type {WO_TYPE_NAME} with the title {WO_TITLE}.
An error occurred while saving the collaboration
network credentials. Contact your help desk.
The email account values in the profile option for your

implementation aren't registered. Contact your help
desk.
An error occurred while initiating an action plan for

template {NAME}. Contact your help desk.
The party record isn't found for the selected person.

The email accounts aren't configured for your

implementation. Contact your help desk.
An error occurred while creating an action plan for
template {NAME}. Contact your help desk.
Not all fields could be saved. Contact your help desk.
Your Manage CX Sales to CPQ setup is incorrect. Contact

your help desk.
The selected filter is no longer available. Contact your

help desk.
The selected action is no longer available. Contact your

help desk.
The Workspace feature is temporarily unavailable.

An error occurred during territory assignment. Contact

your help desk.
The view criterion wasn't saved because of an error.
The merge request can't be processed. Contact your
help desk.
Your request can't be processed by DataFox. Contact
your help desk.
Your request can't be processed by Oracle Data as a
Service. Contact your help desk.
Your connection to Oracle Data as a Service can't be

established. Contact your help desk.
You can't establish a connection with Oracle Data as a

Service because the service is down.
Your CX Sales service isn't configured in DataFox.
Your connection to DataFox can't be established.
Cleansing operations couldn't be performed because the

data quality cleanse server is disabled. Contact your help
desk.
Cleansing operations couldn't be performed because the
data quality match server is disabled. Contact your help
desk.
The sync process didn't complete.
The sync process stopped due to timeout inactivity.
The sync process did not complete.

The sync process stopped due to timeout inactivity.
The sync process did not complete. Contact your help

desk.
The sync process did not complete. Contact your help

desk.
The list of interviews can't be retrieved from the
Intelligent Advisor hub. Contact your help desk.
You have exceeded the maximum number of long text

fields allowed for this object. Contact your help desk.
You have exceeded the maximum number of dynamic

choice list fields allowed for this object. Contact your
help desk.
The custom subject area was only partially published

due to an error with the CRM Analytics server. Contact
your help desk.
The custom subject area wasn't published. Contact your

help desk.
The custom subject area {SUBJECT_AREA_NAME} wasn't

saved. Contact your help desk.

help desk.
help desk.

help desk.
The custom subject area wasn't inactivated because the

CRM Analytics server is down. Contact your help desk.

help desk.
The custom subject area wasn't published. Object

{BIVO_NAME} isn't available in the Oracle BI EE

help desk.

help desk.
The custom subject area was only partially published.
The changes for custom subject area

{SUBJECT_AREA_NAME} failed validation. Contact your
help desk.

help desk.

The custom subject area wasn't published because the

publication process couldn't update the Oracle BI EE
An error occurred when updating the custom subject

area. Contact your help desk.
The new custom subject area {SUBJECT_AREA_NAME}
can't be created without any primary entity. Contact
your help desk.
The custom subject area wasn't published because the

publication process couldn't query the Oracle BI EE

inactivated. Contact your help desk.

help desk.
The custom subject area was only partially published

because the CRM Analytics server is down. Contact your
help desk.
help desk.

help desk.
An error occurred when creating the custom subject

area. Contact your help desk.
The new custom subject area {SUBJECT_AREA_NAME}
can't be created with multiple primary entities. Contact
your help desk.

help desk.
The sync process has completed with warnings.

help desk.

help desk.

published. Contact your help desk.
The custom subject area wasn't activated because the

CRM Analytics server is down. Contact your help desk.

activated. Contact your help desk.
The object {OBJECT} can't be created because of an

The layout can't be deleted because of an error. Contact

your help desk.
The subtab can't be deleted because of an error. Contact

your help desk.
The item can't be deleted because of an error. Contact

your help desk.
The summary box can't be deleted because of an error.
The field group can't be deleted because of an error.
The details for the object {OBJECT_TYPE} can't be

displayed because of an error. Contact your help desk.
While republishing the custom subject area, the

following command failed: {COMMAND_NAME}. Contact
your help desk.
The custom subject area wasn't published. An error

occurred while accessing the BI Server. Contact your
help desk.
An application error occurred while upgrading the

custom subject area to the current release. Contact your
help desk.
The following command wasn't found:

{COMMAND_NAME}. Contact your help desk.
Upgrade step {NUMBER} can't be completed. Contact

your help desk.
The subject area {SUBJ_AREA_NAME} wasn't found.
The application for the primary object

{PRIMARY_OBJECT} wasn't found. Contact your help
desk.
Personalization changes made by user {USERNAME}

couldn't be reset. Contact your help desk.
The Groovy action is disabled for the object
{OBJECT_NAME}. Contact your help desk.
The custom subject area wasn't successfully saved.
The custom subject area wasn't submitted. Contact your
help desk.
The object {OBJECT} can't be updated because of an
The custom subject area {SUBJ_AREA_NAME} has an

invalid status. Contact your help desk.
The schema registration of the BPEL web service request

or response service data object failed due to an error.
Either the join entity {JOIN_ENTITY} or join attribute
{JOIN_ATTR} isn't set. Contact your help desk.
The type definition validation of the loaded service
object failed. Contact your help desk.
The round function doesn't support the data type

{DATA_TYPE}. The supported types are {BIG_DECIMAL},
{DOUBLE}, and {LONG}. Contact your help desk.
An error occurred loading the XML document

{ERROR_MSG}. Contact your help desk.
The validation of the XML document {XML_URL} against

its schema {XSD_URL} failed. Contact your help desk.
There was a problem performing a step in the sync
process. Review error details in the application log and
try syncing again.
You have exceeded the maximum number of attempts.

An error occurred when reading the configuration file.

The user {USER_LOGIN} doesn't have the required

permission to execute the method {METHOD_NAME} on
the service {SVC_NAME}. Contact your help desk.
An error occurred when the sync service called the base

service {BASE_SVC_NAME}. Contact your help desk.
The object {OBJ_NAME} specified in the client sync

request isn't supported by the server configuration.
An error occurred in the sync service when the method

{METHOD_NAME} was called from the base service
{BASE_SVC_NAME}. Contact your help desk.
The sync process didn't complete. Contact your help

desk.
The parsing of the XML string of type {XML_TYPE} failed
because the loaded metadata file was incorrectly
formed. Contact your help desk.
The lead conversion failed. Contact your help desk.
The search operation failed because person ID

{PERSON_ID} doesn't exist. The record was possibly
deleted while it was being synced. Contact your help
desk.
The base object definitions aren't available in the

metadata file. Contact your help desk.
The Microsoft sync module isn't enabled. Contact your

help desk.
You need the required Microsoft permissions to

continue. Contact your help desk.
There is an issue communicating with Microsoft

Services. Contact your help desk.
The add-in application isn't registered or is inactive.
The page can't be loaded. Contact your help desk.
An error occurred while syncing data. Contact your help
desk.
Your data wasn't synced because the server is down.

Your data can't be synced because application settings

aren't defined. Contact your help desk.
Your preferences couldn't be loaded. Contact your help

desk.
An error occurred while saving the conflict resolution

preference. Contact your help desk.
An error occurred while loading the saved searches.

An error occurred while saving the saved search

preference. Contact your help desk.
An error occurred while loading the application settings.

An error with the error code {ERROR_CODE} occurred

while you were logging in. Contact your help desk.
An error occurred while executing server script

{FN_NAME}. Contact your help desk.
An error occurred. Your changes weren't saved. Contact
your help desk.
An application error occurred. Your changes are saved,
but the forecast wasn't successfully updated. Contact
your help desk.
An error occurred during the processing of {FILE_NAME}

file. Contact your help desk.
An error occurred during program execution. Contact

your help desk.
The program {PROGRAM_NAME} wasn't submitted

The program {PROGRAM_NAME} failed. Contact your

help desk.
The rule {RULE_NAME} failed. Deleting and re-creating

the rule may resolve the issue. Contact your help desk.
The rule dictionary couldn't be constructed because an

application error occurred. Contact your help desk.
The application can't proceed with invoice submission

due to incomplete setup. Contact your help desk.
An error occurred while saving the changes done.

The invoice validation process couldn't complete

You can't continue with allocation because tax
calculation has failed.
An error occurred while calculating tax. Distributions

can't be generated because tax calculation failed:
{ETAX_ERROR}
An error occurred when synchronizing the invoice and

tax distributions. Contact your help desk.
An error occurred. Message: {DEBUG_INFO}
An error occurred while calculating withholding for the

invoice. Contact your help desk.
An error occurred while generating distributions for tax

lines. Contact your help desk.
An error occurred during invoice cancellation. Contact

your help desk.
An error occurred during synchronizing of invoice and

tax distributions. Contact your help desk.
The product integration program for payments failed
An error occurred when synchronizing invoice and tax

lines. This may result in tax lines getting deleted. Contact
your help desk.
An error occurred during the payment creation. Contact

your help desk.
An error occurred while calculating tax. Contact your

help desk.
An error occurred during creation of payment

accounting event. Contact your help desk.
An error occurred while creating single payment.

The creation of withholding or interest distributions
failed because of an error. Contact your help desk.
You can't create or update this adjustment because the

entered amount and accounted amount don't match in
the ledger currency. Contact your help desk.
The receipt wasn't created and applied. Contact your

help desk.
The creation of detailed distributions and updates to the

account balances has failed due to an error. Contact
your help desk.
Receivables XML Invoicing encountered an error while

accessing the SOA service. Contact your help desk.
An application error occurred when importing external

transactions. Save the log file of the process. Contact
your help desk.
An application error occurred during reconciliation
processing. Save the log file of the process. Contact your
help desk.
An application error occurred while downloading the

transaction file. Contact your help desk.
Default payment attributes failed: {ERROR_CODE}.
An error occurred while processing the transaction file.

The upload process has terminated. Contact your help
desk.
An error occurred while processing the expense report.
The Process Expense Reimbursements and Cash
Advances process failed to create an invoice in Oracle
Fusion Payables. Contact your help desk.
An error occurred while downloading the file from the
card issuer's server. The upload process has terminated.
An error occurred during the workflow rules creation for
the process {PROCESS_ID}. Check the log for more
information.
The notification content isn't available at this time.

The journal approval process has stopped due to a

The rule restoration process failed. Contact your help

desk.
An application error occurred when raising the business

event and the batch couldn't be submitted. Contact your
help desk.
Balances can't be retrieved for the {BDGT_MNTR} table.

An application error has occurred. Contact your help
desk.
Balances can't be retrieved for the {BDGT_MNTR} table.
Your process can't complete due to Essbase connectivity
issues. Contact your help desk.
Your budgetary control validation request can't be

completed. A system error has occurred. Contact your
help desk.

completed. Contact your help desk.

completed. An application error has occurred. Contact
your help desk.
The control budget balance recalculation process failed.


completed. An application error has occurred. Contact
your help desk.
Balances can't be retrieved for the table {BDGT_MNTR}.

The budget periods can't be opened due to an
application error. Contact your help desk.
The control budget balance recalculation process failed.

The process failed to refresh the tree due to a system
The transaction account definition {TAD_NAME} was
unable to create a new account due to an application
The transaction account definition was unable to derive
a valid account due to an error. Contact your help desk.
The accounting engine can't complete due to a system

The Create Accounting process can't complete due to a

A system error occurred. Contact your help desk.
The transaction account definition activation can't

complete due to a system error. Contact your help desk.
The transaction account definition activation can't

complete due to an error. Contact your help desk.
The accounting engine can't complete due to a system

Subledger Accounting can't derive accounts due to an

error when using chart of accounts mapping
{GL_COA_MAPPING_NAME}.
The Risk Management file storage doesn't exist, read-
write access to it isn't available, or disk space is
insufficient. Contact your help desk.
The record object {RECORD_OBJECT_TYPE} wasn't saved.
The record object {RECORD_OBJECT_TYPE} wasn't

deleted. Contact your help desk.
Your request couldn't be completed because of an error

with the content management server. Contact your help
desk.
An exception occurred. Contact your help desk.
The payment info couldn't be transferred for payroll

processing. Contact your help desk.
Your password reset information can't be sent. Contact

your help desk.
An error occurred when you tried to reset your

password. Contact your help desk.
An application error occurred while deleting the alias

{ALIAS_NAME}. Contact your help desk.
An application error occurred as you attempted to
export the alias {ALIAS_NAME} to the file {EXPORT_FILE}.
An application error occurred when you attempted to
save the role {ROLE_NAME}. Contact your help desk.
An application error occurred as you attempted to save

the alias {ALIAS_NAME}. Contact your help desk.
An error occurred during import file processing. Ensure

the contents of the import file are valid. Contact your
help desk.
An application error occurred as you attempted to
generate a CSR for the alias {ALIAS_NAME}. Contact your
help desk.
The billing task failed due to an error. Contact your help
desk.
Salary information isn't available because the effective
date information is missing or invalid. Contact your help
desk.
An invalid expression type exists.
At least one required parameter isn't available to

continue with the transaction. Contact the help desk.
An invalid conversion request exists.
An invalid conversion type exists.

The component information for the salary basis is
invalid. Contact your help desk.
The salary record couldn't be created because required

action information isn't available. Contact your help
desk.
An error occurred while creating the salary record.

Validation of the default dynamic expressions failed.
The process {PROCESS_NAME} with the process ID

{PROCESS_ID} erred. Contact your help desk.
XML generation failed for this statement. Contact your
help desk.
The service OSN failed due to an error. Contact your
help desk.
The database item for this flexfield wasn't created.
The database item for this input value wasn't created.
An error occurred. The array value type used at location
{1} is incorrect. Contact your help desk.
An error occurred. The array index type at location {1} is
incorrect. Contact your help desk.
Data item not found in table {1}, key column {2},
statement {3}. Contact your help desk.
An error occurred. Couldn't allocate {1} bytes of memory
at location {2} in formula code. Contact your help desk.
An application error occurred. The formula symbol table

contains the alias name {1}. Contact your help desk.
Formula function {1}, alias name isn't unique. Contact

your help desk.
A data item error occurred in formula {1}, formula data

item {2}, at location {3}. Contact your help desk.
A system error occurred. Formula wrapper failed to
generate PL/SQL package {PACKAGE}. Contact your help
desk.
Database item {1}, placeholders remain. Contact your
help desk.
An application error occurred. Assertion failed at

location {1}. Contact your help desk.
An error occurred for formula input or context {2} at
location {3} of formula {1}.
Database item {1}, unterminated comment in route text.
An Oracle error occurred in formula {1} when attempting

to execute formula PL/SQL. Contact your help desk.
The route text for database item {1} is empty or too

long. Contact your help desk.
An error occurred for output {2} at location {3} of
formula {1}.
A system error occurred. The following Oracle error
occurred for table {1}: {0}. Contact your help desk.
An error occurred. The formula context cache is full.
The database item {1} has an invalid data type. Contact
your help desk.
The creation of a database item for element {ELEMENT}

failed. Contact your help desk.
A formula date conversion error {1} occurred at location
{2}.
The changes to the model have failed validation. Contact

your help desk.
You don't have permission to access this information.

Request a change to your security settings. Contact your
help desk.
This page isn't available because the responsive profile
option must be enabled to access it. Contact your help
desk.
The {VO_NAME} view object is invalid and doesn't exist
at run time. Contact your help desk.
You must enter a value for a flexfield segment name.

The {AM_NAME} application module is invalid and

doesn't exist at run time. Contact your help desk.
The effective start date must be later than the effective

end date of the previous record.
Effective sequence numbers can't have gaps when
multiple changes to date-effective records exist for the
same day.
The {CLASS_NAME} class doesn't support the

{METHOD_NAME} method. Contact your help desk.
Business event connection factory not found for

namespace {EDL_NAMESPACE}. Check the Oracle SOA
Suite EDN connection settings. Contact your help desk.
An exception occurred evaluating Groovy rule for event

type {EVENT_TYPE_ID}. Groovy rule
{GROOVY_RULE_TEXT}, Exception {EXCEPTION_CLASS},
{EXCEPTION_MESSAGE}.
Raising HR event failed for namespace

{EDL_NAMESPACE}. Exception {EXCEPTION_CLASS},
{EXCEPTION_MESSAGE}. Contact your help desk.
A connection configuration error occurred when
attempting to create a business event connection for
namespace {EDL_NAMESPACE}.
The date effective processing can't be completed due to

a technical issue. Contact your help desk.
You can't use the goal plan set tasks at this time. Contact
your help desk.
The email server couldn't be authenticated. Contact

your help desk.
Set the profile option Talent Profile User Interface
Redesign to Y or supply a valid POD key to access the
upgrade mapping UI. Contact your help desk.
HCM Spreadsheet Data Loader can't create a new
scheduled process. Contact your help desk.
The schedule couldn't be reset. Try again and if the issue
persists, contact your help desk.
An error prevented the schedule from being published.

Try publishing again and if the problem persists, contact
your help desk.
You can't create, modify, or delete the shift because of

an error. Contact your help desk.
Several of the exception time events can't be deleted

due to a system issue. Contact your help desk.
The time card can't be approved due to an error.

An error occurred while validating your time card.
An error occurred and your changes can't be applied.
The process couldn't be submitted. Contact your help
desk.
An error occurred while creating the artifact. Contact

your help desk.
A system error occurred while submitting the following

number of time cards: {QTY_SELECTED_TIME_CARDS}.
A system error occurred while approving the following
number of time cards: {QTY_SELECT_TIME_CARDS}.
A system error occurred while deleting the following
number of time cards: {QTY_SELECT_TIME_CARDS}.
The time card can't be submitted due to a system error.

The time card can't be submitted due to a system error.

The time card can't be deleted due to a system error.

The time card can't be saved due to a system error.
A system error occurred during processing. Contact your

help desk.
The process {PROCNAME} can't be run because it isn't

registered.
The view object doesn't contain an attribute for
LegislativeDataGroupId. The function call can't be
executed.
The value passed as the assigned payroll ID parameter
doesn't exist. Contact your help desk.
The module ID is invalid. Contact your help desk.
The entry usage start date must be after the original

effective start date of the element entry with which it's
associated.
The payroll relationship identifier doesn't exist. Contact
your help desk.
A unique identifier for the payroll terms record doesn't

exist. Contact your help desk.
The assigned payroll identifier doesn't exist. Contact

your help desk.
An invalid payroll action was used for the balance

adjustment group.
The balance adjustment group with ID

{BAL_ADJ_GRP_ID} doesn't exist.
An application error occurred. The argument
{ARGUMENT} doesn't exist as of the effective date.
A no-data-found exception was detected while
processing the balance database item.
The payroll process was unable to locate and stop a
recurring entry for element {ELEMENT_NAME}.
The start date and end date of the first entry usage for a
nonrecurring entry must match the start and end dates
of the entry on insert.
The unique identifier for the entry value record already

exists.
This balance adjustment group was processed, as shown
by the status {BATCH_GROUP_STATUS}.
This combination of element eligibility criteria already

exists. Contact your help desk.
An attempt to allocate memory failed. Contact your help

desk.
The process has failed during the expiration checking of
a balance. The check failed with system error
{ERROR_MESSAGE}.
An application error occurred. An assertion failure was
detected at location {LOCATION}.
The payroll relationship action ID is invalid.
The database item {USER_ENTITY_NAME} returned

more than one row.
An error occurred. The procedure {PROCEDURE} failed at
step {STEP}.
A system error {SQLERRMC} occurred in table
{TABLE_NAME} at location {SQL_NO}. Contact your help
desk.
An unrecognized action type {ACTION_TYPE} was found
during processing.
The instance set {INST_SET_NAME} for secured object
{OBJECT_NAME} doesn't exist in the
FND_OBJECT_INSTANCE_SETS table. Contact your help
desk.
A system error occurred when trying to call the

enterprise scheduler service. Contact your help desk.
The process identified a severe error while reading the

data role details. Contact your help desk.
The security model application module is missing from
the root application module. Contact your help desk.
An error occurred while retrieving the security profile

for the object {SECURED_OBJ}. Contact your help desk.
The position hierarchy flattening failed with error code

{ERR_CODE} after changing the position with code
{POSITION_CODE}. Contact your help desk.
Your request couldn't be successfully processed. Contact

your help desk.
There is a problem processing your request. Contact
your help desk.
Your payment for user {LEARNER_NAME} wasn't
successfully processed. Contact your help desk.

your help desk.

your help desk.
An error occurred during processing. Contact your help

desk.
An error occurred when connecting to the BI server.

desk.
desk.

desk.
desk.

desk.
An error occurred. The required event code and payload

parameters are missing from the publish request.
An error occurred. The event couldn't be published

because the payload couldn't be parsed. Contact your
help desk.
The event couldn't be published because the messaging

component couldn't accept the message. Try again after
some time. If unresolved: Contact your help desk.
The event couldn't be published due to an error. Contact

your help desk.
An error occurred. The event couldn't be published
because the messaging component is down. Try again
after some time. If unresolved: Contact your help desk.
The event couldn't be delivered to a subscriber due to

The event couldn't be delivered to the subscriber

because the subscriber isn't reachable. Try again after
some time. If unresolved: Contact your help desk.
An error occurred. The event couldn't be delivered

because the subscriber can't parse the event payload.
Your request can't be completed due to an error.

The PL/SQL package for the formula couldn't be

generated. Contact your help desk.
Your changes were saved but an error occurred while
updating the business intelligence tables used for
reporting. Contact your help desk.
The formula generation package wasn't run. Contact

your help desk.
An error occurred in your request for approval. Contact

your help desk.
The supplier site is enabled for communication using

electronic messages but the application wasn't able to
deliver the message. Contact your help desk.
An application error occurred in your request for

approval. Contact your help desk.
An error occurred while generating the PDF. Contact

your help desk.
An application error occurred while creating the
purchase order. Contact your help desk.
An application error occurred while submitting the
purchasing documents. Contact your help desk.
The operation couldn't be completed due to an error.

An application error occurred when processing your

request for approval. Contact your help desk.
An application error occurred when publishing the PDF.

The deployment job {ESS_PROCESS_NUM} failed due to

one or more errors. Contact your help desk.
The agreement loader experienced an error. Contact

your help desk.
The attempted operation couldn't be completed due to

The operation couldn't be completed due to an error.
An error occurred while retrieving rule information.
The agreement loader encountered a purchasing

document open interface error. Contact your help desk.
The agreement loader encountered an SQL error while

initializing the parser. Contact your help desk.
The agreement loader encountered an application error

while initializing the parser. Contact your help desk.
The agreement loader encountered an application error.


during initialization. Contact your help desk.

while initializing the upload handler. Contact your help
desk.
You can't edit this supplier's existing {COMPONENT} due
to an error. Contact your help desk.
An application error occurred when updating the

supplier profile. Contact your help desk.
You can't select supplier {COMPONENT}

{COMPONENT_VALUE} due to an error. Contact your
help desk.
An instruction set exception occurred. Contact your help
desk.
The asset lines aren't generated for the asset
{ASSET_NAME} because of an error in the overriding
client extension procedure.
The asset lines weren't generated because of an error in
the overriding client extension procedure.
The asset lines aren't generated because of an error in

the overriding client extension procedure. Contact your
help desk.
The asset lines aren't generated because of an error in
help desk.
The asset {ASSET_NAME} wasn't transferred because of

an error in the group retirement adjustment process.
the overriding client extension procedure.
The asset lines aren't generated for the asset

{ASSET_NAME} because of an error in the overriding
client extension procedure.
An asset line was generated but couldn't be allocated to

the assets because one or more errors exist in the asset
allocation basis client extension procedure.
An unknown error occurred in the Create Project Assets

client extension procedure. Asset lines weren't
generated as a result. Contact your help desk.
The transactions weren't imported because the source

application isn't available. Contact your help desk.
The status of the processed transactions wasn't sent to
the source application because the source application
isn't available. Contact your help desk.
The burdened cost couldn't be determined while

calculating the transfer price due to an application error.

help desk.
The allocation generation failed because of a system

An application error has occurred. Contact your help

desk.
The project can't be created because of an application

installation issue. Contact your help desk.
The action can't be performed because of an application


The task structure wasn't flattened for reporting in
Oracle Transactional Business Intelligence because of an
The team members weren't copied to the new project or

project template because of an application error.
The burden schedule overrides weren't copied to the
new project or project template because of an
The organization overrides weren't copied to the new
project or project template because of an application
The asset assignments weren't copied to the new
The cross charge options weren't copied to the new
A new project or project template can't be created
because of an application error. Contact your help desk.
The task attachments weren't copied to the new project

or project template because of an application error.
An application error occurred when retrieving the
organization information. Contact your help desk.
The key performance indicators weren't copied to the

The project tasks weren't copied to the new project or
An application error occurred during the maintenance of
project organizations. Contact your help desk.
The project attachments weren't copied to the new
The assets weren't copied to the new project or project
template because of an error. Contact your help desk.
The financial plans weren't copied to the new project or

Your changes to the enterprise project structure weren't

saved. Contact your help desk.
An error occurred while adding unassigned projects to

the Enterprise Project Structure. Contact your help desk.
An application error occurred during the import process.

The project resource search index wasn't created

because of an application error. Contact your help desk.
The calendar with the ID {SCHEDULE_ID} no longer
exists. Contact your help desk.
The connection to Oracle Essbase server can't be

The application couldn't connect to the Oracle Essbase

Server. Contact your help desk.
The connection to Oracle Essbase server can't be

An application error occurred while generating KPI

values. Contact your help desk.
The connection to the Oracle Essbase server can't be

The reminder message couldn't be posted on Oracle

Social Network. Contact your help desk.
There was a problem processing the business
information. Contact your help desk.
There was a problem generating or recalculating the

activity due dates. Contact your help desk.
The certificate couldn't be generated. Contact your help

desk.
Settings for validating contractor information don't exist,

so you can't enter contractor information. Contact your
help desk.
You can't submit this application due to an error in
processing the contractor license information. Contact
your help desk.
This request wasn't accepted. Contact your help desk.
The rule {RULEID} for creating the next sequence

number is missing information about the sequence
number format. Contact your help desk.
The requested range isn't satisfied. Contact your help
desk.
The server can't fulfill the request. Contact your help

desk.
The rule for creating the next sequence number can't be

The Generate Accounting process failed. Contact your

help desk.
The terms of use for this application don't exist. Contact
your help desk.
The Journal Edit process failed. Contact your help desk.
The next sequence number couldn't be created. Contact

your help desk.
The request expectation failed. Contact your help desk.
The checkout process failed. Contact your help desk.
The report {REPORT_ID} couldn't be generated. Contact

your help desk.

help desk.

help desk.
A SQL processing error occurred. Contact your help desk.
A processing error occurred. Contact your help desk.
There was an error with the integration connection.

The checkout confirmation failed after you submitted
items in the cart for payment. Contact your help desk.
The request entity is too large. Contact your help desk.


help desk.

help desk.
help desk.
The accounting source transaction couldn't be created.

help desk.

help desk.
The report wasn't printed. Contact your help desk.
The cashier session ID must have a numeric value.

You can't use this worklist to view incoming issues

because you haven't been assigned to any issue types.
There are no users that can be assigned to this

application. Contact your help desk.
The notification for the final inspection wasn't sent.

An error occurred while updating the fee status. Contact

your help desk.
An error occurred while generating the invoice. Contact

your help desk.
An error occurred while evaluating conditions placed on

fees. Contact your help desk.
An error occurred while generating the accounting
transaction. Contact your help desk.
The rest endpoint for resource {RESOURCE_NAME} is

blank. Contact your help desk.
The REST endpoint for service {BASE_NAME} is blank.

There was a fee calculation error. Contact your help

desk.
You don't have permission to create a change of this

type. Contact your help desk.
The selected value {ATTR_VALUE} is no longer valid for

the {ATTR_LABEL} field. Contact your help desk.
The item creation failed. Contact your help desk.
An application error occurred and view object

{VO_NAME} is unavailable. Contact your help desk.
An application error occurred while trying to clone the

view object {VO_NAME}. Contact your help desk.
An application error occurred in the linked item. Contact

your help desk.
An application error occurred. The Applications
Unlimited object ID provided internally was empty or
contained no value. Contact your help desk.
An application error occurred and the view object

instance {VO_NAME} is unavailable. Contact your help
desk.
An application error occurred because the Oracle

Applications Unlimited entity value is empty or
contained no value. Contact your help desk.
An application error occurred because there is no

primary key defined to store the SQL BLOB contents.
The number of groups in the provided object ID

{OBJECT_ID} is {GROUP_COUNT}. This is not the
expected number of groups for a valid object ID.
An application error occurred because the object ID

{OBJECT_ID} does not match the correct pattern.
An application error occurred when the object ID

{OBJECT_ID} did not have the correct length. Contact
your help desk.
The type value {GOT_TYPE} received for the attribute

{ATTRIB_NAME} is incorrect. The expected type value is
{EXP_TYPE}. Contact your help desk.
You are unable to connect to Oracle BI Publisher Server.
You are not an authorized user to run the report.

Your security credential cannot be validated and you

cannot connect to Oracle BI Publisher. Contact your help
desk.
You are unable to connect to Oracle BI Publisher.

You were unable to get requirement templates. Contact

your help desk.
An error occurred while creating a receivables claim.

The transaction is missing the original receipt or delivery

reference. Contact your help desk.
The cost adjustment wasn't saved due to the error
{EXCEPTION_MESSAGE}. Contact your help desk.
The process to derive the valuation unit failed because
of an error. Contact your help desk.
The process failed due to an error. Contact your help
desk.
The program that derives the key flexfield segment
The following number of records were quarantined:
{ROW_COUNT}. Contact your help desk.
An error occurred while processing your action request.

An error occurred: {MESSAGE}. Contact your help desk.
The request to save the message failed because you

cannot use the lookup code with function {FUNC}.
The request to save the message failed because you
cannot use the lookup code with message type
{MESSAGE_TYPE}.
The messaging service did not save your messages
because entity type {ENTITY_TYPE} is not valid.
The messages cannot be saved because result code
{REQUEST_RESULT} is invalid. An invalid lookup code
was passed to the messaging service.
The e-mail was not sent. Contact your help desk.
A document or notification was not created. Contact

your help desk.
An error occurred while initiating the approval task flow.
An error occurred while downloading the electronic

record. Contact your help desk.
An error occurred while generating the electronic

The Generate Electronic Record process was not

submitted because of an error. Contact your help desk.
An error occurred while generating the electronic

Item batch {ITEM_BATCH_NUMBER} was not deleted

because of a system error. Contact your help desk.
You do not have the required privilege to complete this
operation. You need to request a change to your
privileges. Contact your help desk.
The item number generation failed. Contact your help
desk.
An exception occurred while running SOA process

{PROCESS_NAME} for business keys {KEY_MAP}. Contact
your help desk.
Item description generation failed. Contact the
administrator to set up the schema correctly. Contact
your help desk.
Item class creation failed. Contact your help desk.
The style item for the SKU does not exist. Contact your
help desk.
An error occurred when calling the service to discard
draft revision {REVISION} of order {ORDER}. Contact your
help desk.
An error occurred in the attempt to check constraints for
order {ORDERNUM}. Contact your help desk.
An error occurred in the generation of a cancellation to

An error occurred in the generation of a revision to
The request to price the sales order failed. Contact your
help desk.
An error occurred while retrieving the event

information. Contact your help desk.
An error occurred while processing the {TASK_NAME}
task. Contact your help desk.
An error occurred while processing the event. Contact
your help desk.
An error occurred while calculating the transfer price for
the delivery detail {DEL_DET_ID}. Contact your help
desk.
The transfer price calculation failed because a valid unit
selling price couldn't be derived for the delivery detail
{DEL_DET_ID}. Contact your help desk.
The selected records could not be reprocessed due to an

The transfer price events couldn't be triggered for the
selected records due to an error. Contact your help desk.
The Item Cost service connection failed because the

Item Cost service is unavailable. Contact your help desk.
The profile option {PROFILE} does not exist. Contact your

help desk.
The creation of predefined data setup failed for object

{OBJECT_NAME} in the organization
{ORGANIZATION_CODE}. Contact your help desk.
You cannot create a locator for this subinventory
The adjustment transaction failed due to a system error.

An error occurred when creating the movement request.
The process {PROCESS_ACTION_NAME} failed while

saving the information. Contact your help desk.
The process {PROCESS_ACTION_NAME} failed. Contact
your help desk.
An error has occurred because the movement request
cannot be created. Contact your help desk.
The process {PROCESS_ACTION_NAME} failed while

retrieving the required information. Contact your help
desk.
An error occurred when executing the min-max planning
process. Contact your help desk.
The Export Count Sequences process failed due to an

An error occurred while executing the min-max planning

An error occurred in the process that maintains
inventory supply. Contact your help desk.
The quantity available to be reserved could not be
computed for the item {ITEM} being pick released.
An error occurred when maintaining inventory supply
records. Contact your help desk.
An error occurred in the program that unlocks the

quantity tree. Contact your help desk.
The root node for the quantity tree cannot be found.

An error occurred when creating requisition import
records. Contact your help desk.
The printing of pick slip {PICK_SLIP_NUM} failed.
An invalid supply entity type was passed while

processing the information. Contact your help desk.
Reservations cannot be created because a web service
error has occurred. Contact your help desk.
An error occurred while creating the replenishment

order request data through the Supply Chain
Orchestration process. Contact your help desk.
An error occurred in constructing the quantity tree while
calling {ROUTINE}. Contact your help desk.
The reservation transfer failed because the record was

incorrect or incomplete. Contact your help desk.
An error occurred while retrieving the secondary unit of
measure for the item. Contact your help desk.
The quantity tree node cannot be found. Contact your
help desk.
An error occurred in the program that locks the quantity

tree. Contact your help desk.
The plan run process attempted to change a protected

option. Your plan was run without the change, but you
should report this message. Contact your help desk.
The demand forecasting engine failed to complete

successfully. Contact your help desk.
The current plan action stopped due to a processing

A database error occurred. Contact your help desk.
At least one of the inputs to the demand engine is

invalid. Contact your help desk.
The current plan action ended in error because the

refresh type {REFRESH_TYPE} is not supported for this
plan type. Contact your help desk.
The current plan action ended in error because an error

occurred when accessing plan input data. Contact your
help desk.
The plan run ended in error because the dimension
catalog {DIM_CAT_NAME} is missing the following
dimensions: {DIM_NAME_LIST}. Contact your help desk.
An error occurred when the application was

preprocessing the plan action {PLAN_ACTION}. Contact
your help desk.
The following number of measures for measure name

{MEASURE_NAME} were not loaded:
{MEASURE_COUNT}. Contact your help desk.
The Load Measures from Other Plans process
completed, but no measures were loaded. Contact your
help desk.
The aggregate planning model ran out of memory.

The plan run failed. The incident with ID {INCD_ID} is on

server {SRVR_NAME}. Contact your help desk.
The demand plan measure wasn't loaded to the

shipments forecast. Contact your help desk.
The current plan action ended in error when saving the
initial model data. Contact your help desk.
The aggregate supply plan run failed during the model

solve process. Contact your help desk.
Some of the changes you saved couldn't be simulated

for the aggregate supply plan. Contact your help desk.
The aggregate supply plan run failed during the model

save process. Contact your help desk.
The aggregate supply plan run failed during the data

load process. Contact your help desk.
The aggregate supply plan run failed during the measure
data flush process. Contact your help desk.
The plan ended in an error. The supply planning engine

cluster stack size is too small. Contact your help desk.
The PL/SQL procedure {PROCEDURE_NAME} returned a

status of error. Contact your help desk.
The demand forecasting process was terminated due to
The table or graph you requested cannot be opened

because an error occurred. The incident with ID {INC_ID}
is on server {SERVER_NAME}. Contact your help desk.
The request was not processed. Review the Oracle

Fusion Global Order Promising engine log file for more
details. Contact your help desk.
An error occurred with the service named
{SERVICE_NAME}. Contact your help desk.
At least one parameter is incorrect. The process was

terminated. Contact your help desk.
The plan {PLAN_NAME} was not created. The problem

may be temporary. You may want to try to create your
plan again. Contact your help desk.
The instance environment variable is not set. Check that

the Oracle Fusion GOP engine is installed correctly.
The Oracle Fusion Global Order Promising web service
cannot connect. Verify that the Oracle Fusion Global
Order Promising engine is running.
The Oracle Fusion Global Order Promising data refresh
The demand forecast failed due to a missing table.

The demand forecast failed during the forecast output
The demand forecast failed because the parameters
associated with the forecasting profile are empty.
The demand forecast failed due to an empty set of
causal factors. Contact your help desk.
The demand forecast failed. Some of the causal
decomposition groups defined in the forecast profile are
not configured properly. Contact your help desk.
The demand forecast failed during the data aggregation

The demand forecast failed during the data set analysis
The demand forecast failed during the process of

decomposing the forecast output. Contact your help
desk.
The demand forecast failed due to an empty set of
forecasting methods. Contact your help desk.
The demand forecast failed during the branch allocation

The demand forecast failed because the selected
calendar does not have sufficient information. Contact
your help desk.
The demand forecast failed during the error metric
generation process. Contact your help desk.
The demand forecast failed while resetting the forecast.
The demand forecast failed because the parameters for
the forecasting method cannot be found. Contact your
help desk.
The algorithm promotion failed. Contact your help desk.
Job {JOB_NUM} didn't start. Contact your help desk.
There was a problem processing the uploaded supply

data. Contact your help desk.
Generating the work order number failed. Contact your

help desk.
The import batch failed due to a system error. Contact

your help desk.
The operation transaction failed due to a system error.
The packing slip document sequence category creation

A document sequence creation failed. Contact your help

desk.
A document sequence category assignment to the

document sequence failed. Contact your help desk.
The document sequence generation failed for Packing

Slip Document Sequence Category. Contact your help
desk.
Your request to create a pick wave failed. Contact your

help desk.
The document sequence generation failed for the bill of
lading document sequence category. Contact your help
desk.
The transaction can't be completed because an error

occurred. Contact your help desk.
The document sequence generation failed for the

commercial invoice document sequence category.
The ship confirmation transaction failed due to a system

An error occurred when trying to lock the shipment

lines. Contact your help desk.
A deadlock occurred when trying to lock a shipment line.

The transaction failed due to a system error. Contact

your help desk.
Your request to create a pick wave failed due to an
An error has occurred while generating the setup data

report for business object {BO_NAME}. Contact your
help desk.
This operation can't be performed. You must meet all
the prerequisites for this web service before invoking it.
The domain connections weren't regenerated as
expected. Contact your help desk.
An authorization error occurred while invoking task
{TASK} of module code {MODULE}. Review the security
configuration. Contact your help desk.
An error occurred while invoking task {TASK}. Review the

FunctionalSetupServer logs for more details on this
The task can't be opened because the referenced

enterprise application {ENT_APP} is invalid. Contact your
help desk.
The importDataAsync service method can't be found.
Generate Asynchronous Web Service methods in
service. Service URL is {SERVICE_URL}. Contact your help
desk.
Service Message Transmission Optimization Mechanism

MTOM policy not found for service. Service URL is
{SERVICE_URL}. Contact your help desk.
The offering import process has completed with errors.

Service method exportDataAsync can't be found.

Generate Asynchronous Web Service methods in your
service. Service URL is {SERVICE_URL}. Contact your help
desk.
The offering export process has completed with errors.

An error occurred while invoking the service

{SERVICE_URL}. Check it's registered correctly and is
currently running. Contact your help desk.
Service information isn't available. Contact your help
desk.
The task {TASK_NAME} wasn't submitted for execution
because of the following error. Contact your help desk.
The task {SEARCH_TASK} used for scope selection of the
business object {BUSINESS_OBJECT} isn't returning all
expected scope parameters. Contact your help desk.
An error occurred while submitting task {TASK_NAME}

for execution. The process ID or a task status wasn't
returned. Contact your help desk.
Unable to reach the endpoint URL for application
{APPLICATION_NAME}. Make sure the application is
registered properly and running. Contact your help desk.
You can't perform this operation without fulfilling the

prerequisites. Contact your help desk.
An error occurred while submitting a new ESS request.

Review the Enterprise Storage Server deployment or
configuration. Contact your help desk.
Service method parameter names are incorrect. Use

exportCriteria and exportControl respectively. Service
URL is {SERVICE_URL}. Contact your help desk.
Task {TASK} for product {PRODUCT} has errors. Review

errors in the web component producer logs and correct
them. Contact your help desk.
Insufficient data received from the service. Verify that

the service is working correctly. The service URL is
Service method parameter names are incorrect. Use the
importData and importControl. Service URL is
An error has occurred while generating the setup data
report for business object {BO_NAME}. Contact your
help desk.
Message User Details Message Cause
- -
- -
- -
- -
- -
Contact your help desk. -
- -
- -
- -
- -
- -
- -
- -
- -
The query didn't return any rows for -

segment {SEG_NAME} of the flexfield for
application {APP_NAME} and flexfield
{FLEX_NAME}. Contact your help desk.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
Resubmit the request. If the error occurs -

again, get assistance. Contact your help
desk.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The errors are {BI_ERROR_DETAILS}. -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The mapping based assignment evaluation -

process was unable to call a translation
function.
- -
- -
- -
The mapping failed for the following target -

hierarchies: {TARGET_LIST}.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
An internal, unspecified error occurred -

during the sync process. Review the
application logs and the OBIEE server logs to
see why the sync process didn't complete.
Contact the vertical development
environment team.
- -
- -
- -
This error occurs when the rules file required -
for the sync process is not generated.
Review the application logs to see why the
sync process didn't run and contact the
vertical development environment team.
The process to generate the rules file -

required for the sync stopped. Review the
application logs and contact the vertical
development environment team if needed.
The OBIEE server is down. Restart the OBIEE -

server and then rerun the sync process.
The sync process status was not updated. -

Review the application logs to see why the
sync process did not complete and contact
the vertical development environment team.
The OBIEE process applied the rules file to -

the OBIEE server metadata repository.
Review the application logs and the OBIEE
server logs to see why the sync process did
not complete. Contact the vertical
development environment team.
- -
An unspecified error occurred during the -

sync process. Review the application log,
SOA server log, and the OBIEE server log.
- -
- -
- -
- -
- -
The business intelligence view object for -

dimension entity {ENTITY_NAME} in MDS
failed to generate.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The business intelligence view link between -
the custom subject area fact and the
dimension entity {ENTITY_NAME} in MDS
failed to generate.
- -
- -
- -
- -
The OBIEE process returned the warning -

message: {BI_ERR_MSG}. Review the
warning messages in the application log and
the OBIEE server log. Contact the vertical
- -
The business intelligence view object for the -

custom subject area fact in MDS failed to
generate.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The type definition isn't consistent with the -

specified target namespace {NAMESPACE}
and element type {TYPE_NAME}.
- -
- -
The following number of errors resulted: -

{TOTAL_NUM_ERROR}. An error occurred:
{ERROR_MSG}.
Review the detailed error messages in the -
application log, and, where possible, correct
the failure by making changes in the
Synchronization Issues dialog and try
synchronizing again. If the error persists,
contact your help desk.
- -
- -
- -
- -
- -
- -
- -
- The server couldn't parse the XML string due
to an error.
- This can occur if required fields on the lead

aren't provided.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
An application error has occurred. Contact -

your help desk.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
An error has occurred in module {MODULE}. -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
Inform your help desk that you received an -

error during transfer of payment info.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The expression engine detected an internal -

program error. Contact your help desk.


- -
- -
- -

- -
- -
- -
- -
- -
Expected array value type {2}, but actual -

value type is {3}.
Expected array index type {2}, but actual -
index type is {3}.
The data item with key value {4} couldn't be -
retrieved.
- -
- -
Alias name {2} is being used as a formula -

function name or as another functions alias
name.
- -
- -
- -
- -
- -
Context at the time of the error: {2}. -
- -
The error {2} occurred when executing -

statement {3}.
- -
- -
- -
- -
- -
- -
The internal surrogate key ID for this record -

already exists in table {TABLE_NAME}.
- -
- -
Effective date records can't contain rows -

which have overlapping effective start and
end dates. Contact your help desk.
Effective sequence numbers for changes -
within a day must be contiguous. Contact
your help desk.
- -
- -
An exception occurred while evaluating a -

Groovy rule for the event type. Contact your
help desk.
- -
Context at the time of error: Exception -

{EXCEPTION_CLASS},
{EXCEPTION_MESSAGE}. Contact your help
desk.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
If you were submitting a record using a -

service, correct the module ID and resubmit
it. Otherwise, contact your help desk.

- -
- -
- -
A formula result initiated the stop action for -

this element, but there was no active entry
to stop. Contact your help desk.
- -
- -

- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
Your help desk can use the following -

information to obtain a more detailed
description of this incident: Incident ID:
{INCIDENT_NUM}, Server Domain:
{DB_SERVER_NAME}, Server Instance:
{DB_INSTANCE_NAME}, Application Name:
{APPLICATION_NAME}, Additional
Information: {ADDITIONAL_INFO}.
- -

{INCIDENT_SID}, Server Domain:
{DB_INSTANCE_NAME}.

{INCIDENT_SID}, Server Domain:
{APPLICATION_NAME}.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
The overriding client extension procedure -
has an asset which isn't placed in service.
has the asset {ASSET_NAME} that belongs to
another project. Contact your help desk.

has the asset {ASSET_NAME} that doesn't
exist.
has asset {ASSET_NAME} with the actual
service date after the processing date.
- -

has an asset {ASSET_NAME} on hold. Contact
your help desk.

has an asset with an invalid project asset
type. Contact your help desk.
To allocate costs to the assets automatically, -

correct the errors in the client extension
procedure and then generate the asset lines.
Alternatively, you can manually allocate and
assign the asset line to the assets. Contact
your help desk.
- -
- -
- -
- -

has asset {ASSET_NAME} where the asset
event is different from the expenditure item
event.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
An Oracle Essbase connection failed or an -

Oracle Essbase Provider Services error
occurred while generating KPI values.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
{MESSAGE} -
{MESSAGE} -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
An incident was raised. Contact your help -

desk.
- -
- -
- -
- -
- -
- -
Possible reasons for this error are the -
quantity tree has not been built, item
attribute combinations are invalid or
nonexistent, or a given set of item attributes
are newly created, but the tree information
is old.
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- Import setup data process requires the

asynchronous importDataAsync method is
enabled for the service.
- A Service Message Transmission Optimization

Mechanism policy is required for services
used to export or import setup data.
- -
- Export setup data process requires the

asynchronous exportDataAsync method is
enabled for the service.
- -
- -
- -
Error details are {SERVICE_DETAILS}. -

- -
- -
- -
- -
- -
- A service requires both exportCriteria and

exportControl method parameter are named
correctly.
An error was received for the task {TASK} -

and is identified with code {TASKCODE} that
calls program {TASKFLOW} of module code
{MODULE}. An application error
encountered by the producer server
prevented it from rendering the program
{TASKFLOW} of module code {MODULE}.
- -
- A service requires both importCriteria and

importControl method parameters are named
correctly.
- -
Message User Action
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Verify the XML content and import the package
again.
Check additional error messages for the fields that

need to be provided and update the lead with that
information before trying the lead conversion again.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Make sure the asynchronous exportDataAsync

method is defined in the business object service.
Enable Message Transmission Optimization

Mechanism policy in your service.
Make sure the asynchronous exportDataAsync

method is defined in the business object service.
-
-
Make sure the parameters of the exportData are

named exportCriteria and exportControl.
Make sure the parameters of the importData are

named importCriteria and importControl.
-
Message Admin Details
A notification with the key
{KEY_ATTR_NAME_WITH_VALUE} was not found.
Values were not passed to the create API for these

attributes: {ATTR_NAMES}.
For the notification with the key
{KEY_ATTR_NAME_WITH_VALUE}, invalid values were
passed to the update API for these attributes:
{ATTR_NAMES_WITH_VALUES}.
Invalid values were passed to the create API for these

attributes: {ATTR_NAMES_WITH_VALUES}.
For the notification with the key
{KEY_ATTR_NAME_WITH_VALUE}, values were not
passed to the update API for these attributes:
{ATTR_NAMES}.
The database key for each help window identifies the

help links to show in the help window.
The application is not properly set up with Oracle Fusion
Application Toolkit files.
The cache for the Watchlist was not initialized, possibly
because the application database is down, or a service
end point for the Watchlist does not exist in Oracle
Fusion Functional Setup Manager.
The database key for each help window identifies the

help links to show in the help window.
The mapping service to display maps for addresses has

not been defined.
The web site might be down temporarily, or help might

not be configured correctly in your application.
-
-
-
-
Connection is made to the hiring server but internal

errors exist.
Knowledge application configuration settings aren't

working as expected. The sales application
administrator must check the knowledge configuration
settings are properly set so that the knowledge
application service can be accessed.
The knowledge application can't access the shared

service via the REST APIs. This is because the knowledge
integration user isn't authenticated.
This message appears in the application when the
server is down or the URL of the attachment isn't
working. This error wasn't caused by any user action.
This error occurs when there is an issue with the
knowledge search. The Service Request knowledge
panel or My Knowledge then fails to display the
knowledge base articles. This error wasn't caused by
any user action.
A knowledge search can fail in any of the following

conditions: no content was authored, or the content
processing hasn't run successfully, or no search index
has been synced to the Search runtime engine. All the
conditions noted result in no index available at Search
runtime.
While calling the REST API didn't return the locale.
This error occurs if the knowledge application isn't

available. This error can't be caused by any user action.
This message appears when the REST API for retrieving

categories couldn't be called successfully. The
application couldn't retrieve the server information for
the module ORA_CRM_REST from the topology
manager.
This error occurs if the knowledge application isn't

available. This error can't be caused by any user action.
This error occurs if the locale object isn't available in the

target instance during the import step of the export or
import process. This error can't be caused by any user
action.
This error occurs if the repository object ceases to exist

on the target instance during the import step of the
export or import process. This error can't be caused by
any user action.
This error occurs if the knowledge repository isn't

available on the target environment. This error can't be
caused by any user action.
This error occurs if the target instance configuration is
changed while performing the import step of the export
or import process.
This error occurs if one or more concepts referenced in

the import step are invalid. This error can't be caused by
any user action.
This error occurs if the user performing the export or
import process doesn't have the required access
permissions. This error can't be caused by any user
action.
This error occurs if the source instance locale

configuration doesn't have at least one active locale.
This error occurs if the exported configuration file is

manually edited and one or more locale IDs are
modified or deleted.
This error occurs if the domain parameter referenced in

the export or import step is empty. This error can't be
This error occurs if the mode parameter referenced in

the export step of the export or import process isn't set.
This error can't be caused by any user action.
This error occurs if any of the parameters referenced in

the export step of the export or import process is
empty. This error can't be caused by any user action.
This error occurs if one or more concepts persist in the
target environment after the clean-up step of the
import process. This error occurs if the target instance
configuration is changed while the import step of the
export or import process is performed.
This error occurs if the dictionary maintenance status

can't be found on the source or the target environment.
This error can't be caused by any user action.
This error occurs if the search dictionary version can't

be found on the source or the target environment. This
error can't be caused by any user action.

changed while the import step of the export or import
process is performed.

manually edited and a content type reference key is
deleted.

manually edited and a content type name is deleted.
This error occurs if the target instance locale
configuration doesn't have all the locales which are
available in the source instance. This error can't be

changed while the import step of the export or import
process is performed.
This error occurs when the REST service isn't able to

retrieve the data. The Manage Knowledge Locales UI
then can't display the locale object. This error wasn't

retrieve the data. The Knowledge Users UI then can't
display the roles. This error wasn't caused by any user
action.

then can't display all the available locales. This error
wasn't caused by any user action.
This message appears when there is an issue with the

REST server. This error wasn't caused by any user
action.
retrieve the data. The Manage Content Types UI then
can't display the user groups. This error wasn't caused
by any user action.
This error occurs when the REST service isn't able to find
the data. The Knowledge Locale UI then can't display
the default locale. This error wasn't caused by any user
action.
can't display the child nodes of the products or
categories. This error wasn't caused by any user action.

can't display the products. This error wasn't caused by
any user action.

retrieve the data. The Knowledge Users UI then can't
display the users. This error wasn't caused by any user
action.

then can't display all the active locales. This error wasn't
This message appears when there is an issue with the

REST server. This error wasn't caused by any user
action.
can't display the categories. This error wasn't caused by
any user action.
This message appears in the application when there is

an issue with the REST server. This error wasn't caused
by any user action.
The Import Nokia Geography Data process failed due to
a database issue.
Either the top of the sales resource hierarchy or the

accounting calendar didn't get created. This could occur
due to an environment issue or a service failure.
The cause of this error is unknown but may be due to

issues such as the unavailability of the HCM server or
the database.
There is an error in the dynamic compilation of the
Generate Geography Name Referencing PL/SQL
package.
The cause may be due to a database connectivity loss.
The function using Oracle Fusion CRM Application

Composer requires a fix in the Groovy expression.
The Groovy expression in the global function

{RL_GLOBAL_FUNCTION_NAME} returned an invalid
communication data string.
An error occurred during deal registration assignment.
This may be due to a system error while accessing the
Assignment Manager engine or adding matching
resources and territory rows to the deal registration
row.
The update of the lead failed due to an unknown

reason.
There was a problem connecting to UCM. The UCM
server could be down.
The upload of the selected files failed due to an

application error, system error, or due to the
unavailability of the UCM Server.
The request couldn't be completed because of the
following error: {UCM_ERROR_MESSAGE_TOKEN}.
An application or system error occurred while saving

the success log, error log, and exception log to the
content repository.
An error occurred and the cause is unknown.
The Sales server logs will contain any failures in the BI
connection attempt.
The sales campaign wasn't sent due to an unknown

reason.
An error occurred while trying to connect to the content
repository.
The content wasn't saved due to an unknown reason.

Sales server logs will contain any errors related to this
failure.
A conversion rate isn't present for converting a currency

from source to target for a particular date.
The rule-based assignment of a resource has failed

either in batch mode or using the Recommended
Resources action in the UI.
The load-and-activate process for territory management
is currently running. Quota calculations are currently
unavailable as a result.
Some of the territory definition import files didn't load
or didn't load completely.
The cause of the Essbase error is unknown.
The application couldn't determine the cause of the

error so the processing details have been captured in
the logs for support and the development team to
review.
The Quota Management application needs the Essbase

server to be up and running to manage and execute
territory quota formulas.
There is no assignment rule defined for this
combination of work object, candidate object,
assignment mode, and rule set group.
The view object instance for assignment object

{AO_CODE} can't be found.
The assignment object {AO_CODE} with the identifier

{WO_IDENTIFIER} can't be found.
There is no assignment rule set defined for this

combination of work object, candidate object,
assignment mode, and rule set group.
These values aren't valid for the mappings {MAPPINGS}.
There is no assignment rule category defined for this

combination of work object, candidate object, and
assignment mode.
These values are missing for the mappings

{MISS_MAPPINGS}.
Values for the mappings {MISS_MAPPINGS} are missing.

Values for the mappings {INVLD_MAPPINGS} are invalid.
When the assignment process runs, one or more

matching candidates are identified and the application
attempts to store these back in appropriate work object
attribute or attributes. The attribute or attributes where
these values are to be stored haven't been defined.
When the assignment scoring process runs, a score is

calculated and the application attempts to store the
value back on the object. The attribute where this value
is to be stored hasn't been defined.
The no match handling option in the Manage

Assignment Objects setup task of the appropriate
application has been configured to show an error, and
no matching candidates were found during assignment
processing of a record.
There are no active assignment mappings or mapping

sets found for this combination of work object and
candidate object.
There are no active relationships between the work

object and the candidate object.
The assignment rule set {RULE_SET} can't be found as a

candidate cache refresh is in progress.
The application was unable to retrieve a display
attribute for the candidate object.
The assignment object primary key attribute

information is missing.
More than one matching rule was found during

assignment processing.
There is a mismatch between the view object definition

in the assignment configuration and the actual view
object definition used during assignment processing.
An application error occurred during the assignment

processing.
Both the Assign Candidate and Run Custom Logic

options are turned off.
The work object attribute name is missing for the

attribute or dimension assignment mapping.
The configuration couldn't be synced with assignment
objects and rules. The cause is unknown.
The assignment objects and rules couldn't be published.

The cause is unknown.
The maximum number of caches were reached and a
rule session wasn't available in the rule session pool for
the candidate object being processed.
Oracle Business Rules couldn't load the rules for rule-
based assignment processing.
Oracle Business Rules couldn't process the rule set
{RULE_SET}.
The application was unable to retrieve the candidate
object display column details from the assignment
object definitions.
Failed to retract the assignment object {AO_CODE} from
the rule session.
The application is unable to load rule set {RULE_SET}

into a rule session.
Either the configuration for the candidate object has a
mismatch with its view object or there is a problem in
loading data using the view object.
There may be an environment or database issue

preventing the connection to the rules repository.
The application is unable to release the rule session
back to the rule session pool for object {CO_CODE}.
The application was unable to access the assignment

object definitions.
An error occurred while loading the assignment object
for assignment processing.
The territory based assignment evaluation process was
unable to call a translation function.
The application was unable to save the assignment

rules.
There has been a problem with the BI server and hence
the preview couldn't be generated.
An error was detected during the product group
hierarchy mapping generation process. Following are
the error details: {DETAILS}. The error isn't due to any
user action and can't be resolved by the user. This is
likely an error where the cause is unknown.
The generate map process failed. The root cause could

be an earlier exception such as a query failure or
database issues. The exception causes the process to
fail and is unable to continue.
The service {SERVICE} failed with the following details:

{DETAILS}. This error is an internal processing error,
most likely caused by an incorrect setup.
The point-to-point Capacity API call to retrieve the
quota data from field service to populate the scheduler
object returned an error code of 12. This error can be
caused when the corresponding activity type in field
service that was mapped to the selected work order
type has the multiday activity property selected. The
error can also be caused when no work skill condition
has been defined to connect the activity type to a skill.
The work order area is {WO_AREA}. The work order

type is {WO_TYPE}.
This error message is displayed when one of the

following conditions occur: either the
SVC_CSS_REG_WITHOUT_ACCOUNT profile option set
to false, and the user didn't specify an account key, or
the SVC_CSS_ACCOUNT_KEY_FIELD profile option
doesn't have a value specified, and the user specifies an
account key.
This is a generic error message that's returned when

there is a problem in processing a self-service
registration request. The error message will have a
string identifier that can be used to search the log files
and quickly locate the root cause of the error.
This error will occur if your Field Service instance is
unavailable or if the credentials to connect to Field
Service during the create or rescheduling of a work
order fails. During create, it can occur after selecting an
address and time zone which triggers a call to Field
Service to retrieve the Work Order Area list and when
opening the scheduler which triggers another call to
Field Service to retrieve the date and time slot
information based on the Work Order Area and Work
Order Type. During reschedule, it can also occurs when
opening the scheduler to select a different date and
time slot.
The work order field integration message contains a

value that doesn't exist in the Integration Message
lookup table.
This error message is displayed when a user is creating
an action plan from a template ID and the operation
fails.
This message is displayed when there is an error in the
middle tier on the Oracle Weblogic application service
when the user is trying to discard an action plan before
initiating it.
This message is displayed in the REST API response

when the gateway message ID returned is blank for the
corresponding outbound message ID. The outgoing mail
server returns the gateway message ID to the
application after sending the email. The value of this
gateway message ID can be blank if the outgoing mail
server can't send the outbound email due to some error
on the server.
This will only happen if required data wasn't loaded

correctly when this site was provisioned.
This message is displayed if an error occurs due to
issues with the environment. For example, when the
outgoing mail server is down and the application isn't
able to access it to send the outbound email. This
message can also be used by the application if the
outbound email couldn't be sent when some specific
validation fails. For example, when the attachment size
or the length of the recipient email ID of the outbound
email exceeds the permitted limit.
This message is displayed when a TCA party record isn't

found. There could be an issue with the HCM to TCA
integration.
The work offer couldn't be assigned because of either a
channel handler error or an assignment handler error
updating the work offer object.
This error occurs when the collaboration network client
identifier and secret couldn't be saved to the credential
store. This can happen when the application isn't able to
connect to the credential store or when the credential
store is down. The administrator trying to set up the
credentials for oAuth-based integration with a
collaboration network sees this message.
The email values in the

SVC_INBOUND_EMAIL_ADDRESSES profile option don't
match the values in the User Messaging Service.

when the user is trying to initiate an action plan.
This message is displayed when a TCA party record isn't

found which could be an issue with the HCM to TCA
integration.
The email account values may not be valid.
when the user is trying to add a new action plan.
This error can occur if one or more of the three API calls
fail to save the url into topology manager, credentials
into the credential store or the profile options.
This error message is generated either due to an

incorrect URL, incorrect or missing parameter values for
the create, edit, copy, version and get proposal actions
on the Manage CX Sales to CPQ cloud setup page.
A user created a saved search which was added as a

filter to the Actionable Infolet. But later the search was
deleted and the selected filter is no longer available for
use in Actionable Infolets.
A custom action configured in Application Composer has

been removed and therefore is no longer available for
use in Actionable Infolets.
The Workspace search server is down or not functioning

properly.
The cause of this error is unknown and can't be resolved

by the user.
The file where view criteria are stored is missing from
Oracle Metadata Services.
The merge request can't be processed.
DataFox couldn't be reached due to connection issues
or the server may be down.
The user tried to retrieve account or contact
information using the Oracle Data as a Service, but an
exception or error occurred during the web service
invocation.
The Oracle Data as a Service couldn't be reached

because the server information is incorrect or the server
may be down.
The user couldn't connect to the Oracle Data as a
Service because the service is down.
DataFox couldn't be reached due to the CX Sales
configuration issues in DataFox.
DataFox couldn't be reached because of an invalid host
name or invalid port ID, or the server may be down.
Data Quality cleansing service hasn't been enabled and

must be turned on.
Data Quality match service hasn't been enabled and

must be turned on.
There was an internal, unspecified error during the sync

process.
The OBIEE process stopped while applying the rules file

to the OBIEE server metadata repository.
This error occurred when the OBIEE process applied the

rules file to the RPD.
The OBIEE server could be down.
The rules file that's required for the sync process wasn't
generated.
The process to generate the rules file required for the

sync stopped.
The OBIEE server is down.
The sync process status was not updated.
This error occurred when the OBIEE process applied the

rules file to the OBIEE server metadata repository.
This error occurs when the sync process can't be started

because the application fails to start the business event
to trigger the composite for the sync process.
An internal, unspecified error occurred during the sync

process.
This error occurs when the sync process can't be

started.
There is an error communicating with the designated
Intelligent Advisor hub that hosts interviews for
Intelligent Advisor subtabs. This error might be seen if
the hub is unavailable due to maintenance or if the hub
information, written to CX Sales during the creation of
the CX Sales connection, is invalid or missing.
The custom long text field couldn't be created because

the maximum number of long text fields allowed for an
object has been reached.
The custom dynamic choice list field couldn't be created
because the maximum number of dynamic choice list
fields allowed for an object has been reached.
This error occurs when the user attempts to publish a

custom subject area to Oracle BI EE. The publishing
process didn't complete because an internal,
unspecified error occurred in the CRM Analytics server.

process saves the custom subject area definition but
fails to generate the necessary business intelligence
view object for dimension entity in MDS. The
application experiences an internal, unspecified error
while publishing the custom subject area.
This error occurs when the user attempts to save a

custom subject area and the process fails to save the
custom subject area label and description in the
resource bundle due to an unknown system error.

process saved the custom subject area definition but
failed to generate the necessary business intelligence
view object artifacts. An internal, unspecified error
occurred while publishing the custom subject area.
custom subject area to Oracle BI EE and the publishing
process fails to update the ViewCriteria for the fact view
object in MDS when applying the fix for related objects.
The application experiences an internal, unspecified
error while publishing the custom subject area.

custom subject area to Oracle BI EE when the Oracle BI
Server is down.
This error occurs when the user attempts to inactivate a
custom subject area to Oracle BI EE. The inactivation
doesn't complete because the CRM Analytics server is
down.

fails to add ViewUsage for the custom subject area fact
entity to CRM Analytics application module in MDS. The

custom subject area to Oracle BI EE, and the Oracle BI
Server can't locate the reported business intelligence
view object in the Oracle BI EE repository.

custom subject area to Oracle BI EE and the publishing
process fails to update the BI_JOINTYPE property value
to LEFTOUTER. The application experiences an internal,
unspecified error while publishing the custom subject
area.

fails to add ViewUsage for the dimension entity
{ENTITY_NAME} to the CRM analytics application
module in MDS. The application experiences an
internal, unspecified error while publishing the custom
subject area.
process saves the custom subject area definition and
finishes generating the necessary business intelligence
view object artifacts in MDS and partially publishes the
custom subject area to Oracle BI EE. It fails to build
necessary XUDML to add the custom subject area to the
custom project in Oracle BI EE RPD. The application
experiences an internal, unspecified error while
publishing the custom subject area.
This error occurs when the user attempts to save or

publish a custom subject area to Oracle BI EE. The
process fails because the custom subject area changes
couldn't be validated due to an unknown system error.

process doesn't complete because the CRM Analytics
server is down.

necessary XUDML to update custom subject area
security in the Oracle BI EE RPD. The application
experiences an internal, unspecified error while
publishing the custom subject area.

custom subject area to Oracle BI EE. The publication
process failed when trying to update the Oracle BI EE
repository because of an internal, unspecified error.
necessary XUDML to create segmentation catalogs, list
catalogs, and update target level in Oracle BI EE RPD.
This error occurs when the user attempts to update a

custom subject area.
process fails because the custom subject area has no
primary entity due to an unknown system error.

process failed when trying to query the Oracle BI EE
repository because of an internal, unspecified error.
This error occurs when the user attempts to inactivate a

custom subject area. The process fails to delete the

custom subject area to Oracle BI EE. An internal,
unspecified error occurred while publishing the custom
subject area.

process didn't complete because the CRM Analytics
server is down.
view link between the custom subject area fact and the
dimension entity {ENTITY_NAME} in MDS. The

process saved the custom subject area definition and
generated the necessary business intelligence view
object artifacts. However, it failed to build the
necessary XUDML to update the Oracle BI EE repository.
An internal, unspecified error occurred while publishing
the custom subject area.
This error occurs when the user attempts to create a

new custom subject area.
process fails because the custom subject area has
multiple primary entities due to an unknown system
error.

process fails because the custom subject area definition
in MDS is missing necessary entity usage information for
the entity {ENTITY_NAME} and requires to be manually
fixed before the custom subject area can be
republished. The application experiences an internal,
unspecified error while publishing the custom subject
area.
The OBIEE process returned the warning message:

{BI_ERR_MSG}.
custom subject area to Oracle BI EE. An internal,
unspecified error occurred while publishing the custom
subject area.

view object for the custom subject area fact in MDS.

custom subject area to Oracle BI EE. The process fails to
save the custom subject area label and description in
the resource bundle due to an unknown system error.
This error occurs when the user attempts to activate a

custom subject area to Oracle BI EE. The activation
doesn't complete because the CRM Analytics server is
down.
This error occurs when the user attempts to activate a

custom subject area. The process fails to save the

application error. There are various reasons for the
failure ranging from environment issues to metadata
corruption.
There are various reasons for the failure ranging from

environment issues to metadata issues or corruption.


environment issues to metadata issues.
The details for the object {OBJECT_TYPE} can't be

displayed because of an application error, such as
missing parameters or the inability to retrieve source or
target details to execute the criteria that the context
link subtab is built on.
This error occurs when the user attempts to republish a

custom subject area after adding a new related object
to it. The cause of this error can be an issue with the
server.

custom subject area to Oracle BI EE when the Oracle BI
Server may be down.
An error occurred while retrieving the target levels or
qualifying identifiers from the Oracle BI server.
Application errors are typically caused by server-related

errors, such as a concurrent file update or server
connection failure.
The application can't find the command to save or

publish. The cause of this error can be an issue with the
remote server or an application error. The remote
server might not be available.
The metadata upgrade may have failed because of

existing configurations.
This error occurs when the application can't find the
subject area and the subject area isn't saved
successfully.
This error occurs when the user attempts to publish or
save a custom subject area and the application for the
primary object can't be found. The application may
exist, but the application can't be found due to an
incorrect configuration.
The application failed to remove the personalization

data for the specified user.
The Web service for the object {OBJECT_NAME} isn't
registered with the object workflow framework.
The application experienced an internal, unspecified
error while saving the custom subject area.
The application experienced an internal, unspecified
error while submitting the custom subject area.
application error. There are various reasons for the
failure, ranging from environment issues to metadata
corruption.
The subject area save operation can fail for one of the
following reasons: The analytics server is down, the
security server is down (restarting the server can often
resolve issues caused by this reason), or the UI
applications can't reach the crmAnalytics server. Also,
the failure of a WebService function permission can
cause this error (for example, the customer might have
changed some custom roles).
Registering this schema is based on the provided URL of

the schema. A MalformedURLException or IO exception
{ERROR_MSG} was detected.
The context service detected the missing data for a
provider.
The loaded service data object doesn't have the same
specified namespace and type name.
The number rounding function of the context service

failed because the data type isn't supported.
An IO exception has occurred while processing the XML

document.
There is incorrect or invalid content in the XML file that

must be revised based on the violation message.
The Outlook Edition synchronization process failed
because it called another service that returned an error.
The user has exceeded the maximum attempts to sign-

in to the application, and is therefore locked out.
The server configuration file used by the sync service

doesn't match the expected format. The file may have
an incorrect XML format and missing a required
element, or may not include a close tag for an element.
Typically this error occurs only when the configuration
file is loaded through a programming UI, like the
Manage Outlook Server Configuration Files setup task.
An error has occurred because the user doesn't have

access to the web service method. It could be because
the access of the web service or web service method
isn't granted to the user's role, or the role with such
access isn't granted to the user.
The registered, underlying base service for an object

couldn't be called by the sync service. The base service
returned an undetermined error.
An error has occurred because the server configuration
file doesn't contain definition of the object that the
client requested.
The base service returned an invocation target

exception that caused the sync service request to fail.
An error occurred in the sync service that was caused by
validation or configuration settings.
An error occurred with the synchronization process that

caused it to fail.
There seems to be a file type mismatch in the package
that was imported.
If the user isn't able to resolve this failure, the cause

may be due to the lead service availability or a
configuration issue.
The search for a specific person didn't result in a record

being found. The most likely cause is that the record
was possibly deleted during synchronization.
An error occurred where the content of the server

configuration in memory was corrupted and is no longer
accessible. This error happens mainly for two reasons:
Object definition is missing from the uploaded server
configuration file, or the configuration xml file is
malformed and hence couldn't load by the code. Either
it's lost or malformed during upload or the format isn't
supported by the server. Oracle Sales for Outlook refers
to the metadata file (server_configuration.xml) during
the sync process in which all the objects are stored as
object definitions. It couldn't locate the object
definitions. Contact your application administrator.
The profile options that enable and disable the contact

and activity synchronizations are disabled.
As part of the Sales for Office 365 setup, the Microsoft

Exchange administrator must grant Outlook permissions
to the sales application so that updates to Outlook
records can be initiated from the sales application.
The tokens are expired or can't be retrieved.
The add-in deployment in the sales application is

incomplete.
One possible cause is that the user has insufficient
privileges to local storage.
The error must be diagnosed through log messages on
the Enterprise Manager Console. The user was syncing
data at the time.
The error must be diagnosed through log messages on
the Enterprise Manager Console. The user was syncing
data at the time.
The application settings aren't active. This is an internal
processing error that was most likely caused by an
incorrect setup. The user was running the sync process
at the time.
The zpsUsers service failed while loading the

synchronization settings. This is an internal processing
error that was most likely caused by an incorrect setup.
The user was retrieving the synchronization settings at
the time.
The service zpsUsers failed while saving the conflict

resolution preference. This error is an internal
incorrect setup. The user was saving the conflict
resolution preference at the time.
The service savedSearches failed while loading the

saved searches. This error is an internal processing error
that was most likely caused by an incorrect setup. The
user was retrieving the list of saved searches at the
time.
The service zpsUsers failed while saving the saved

search preference. This is an internal processing error
which is most likely caused by an incorrect setup. The
user was saving the saved search preference at the
time.
The service zpsApps failed while loading the application

settings. This error is an internal processing error that
was most likely caused by an incorrect setup.
The service zpsUsers has failed. This error is an internal

incorrect setup. The user was logging in at the time.
An exception occurred while trying to execute the

groovy script with the name {FN_NAME}. There is a
problem with the groovy script, or it's missing.
An application error occurred while attempting to save
the forecasting data.
An application error occurred. Your changes are saved,
but the forecast wasn't successfully updated. You can
continue working on the forecast, but some forecast
items might not be fully synchronized with the
underlying opportunity data until the next forecast
refresh is successfully run.
An error occurred on the Universal Content

Management application server while processing a Sales
Lightbox document upload.
The cause of the error is unknown. There may be

subsequent messages in the log files and incident
reports to help diagnose the problem.
A rule failed to generate correct code. Rule conditions
must be true for recommendations to be made.
The rule dictionary couldn't be created due to a

database error.
The invoice submission has failed due to a missing

payment service provider relationship for business unit
{BU_NAME}.
The IDR POST call service failed because of an
application error. This can happen when the REST
service didn't receive any response.
An application error occurred during the invoice
validation process.
An application error occurred during the tax call:
{ETAX_ERROR}. Any issues with the Tax API are passed
back to Payables.
An application error occurred during the tax call and

invoice distributions can't be generated. Any issues with
the Tax API are passed back to Payables.
An application error occurred during the tax call to

synchronize distributions between Payables and Tax.
Any issues with the Tax API are passed back to Payables.
An application error occurred while processing an

invoice: {ERROR}. Parameters {PARAMETERS}. Package
{CALLING_SEQUENCE}.
An application error occurred while calculating

withholding tax on invoice {INVOICE}.
An application error occurred while generating tax

distributions: {ETAX_ERROR}.
An application error occurred during invoice

cancellation process. Possible reason can be due to data
integrity issues on the invoice distributions.
An application error has occurred while synchronizing

the invoice and tax data.
An application error has occurred during payment
generation.
An application error occurred during tax call. This error

can happen if there are data integrity issues.
An application error has occurred during creation of

payment. The exact cause is unknown.
An application error occurred during the tax call and

might result in tax distributions getting deleted.
An application error has occurred during payment event

creation while processing a single payment.
Creation of payment history records failed because of

an application error.
An application error occurred during creation of
distributions for withholding tax or for interest.
This is a system error probably caused by an attribute

being set which isn't relevant for a particular flow.
Data corruption has caused a mismatch between the

entered amount and accounted amount in the ledger
currency.
The error was returned from the PLSQL back-end

process. The error could have originated from one of
several causes, including a system failure, data
corruption, failure of the receipt application, or missing
attribute values.
The process to create detailed distributions for this

activity and updates to the corresponding account
balances has failed. This is an internal processing error
which has failed to update the table
AR_DETAILED_DISTRIBUTIONS_ALL.
While trying to call the Document Transfer Service from

the SOA service, an error was reported from component
{CM_NAM} with component Instance ID {CM_ID} while
executing composite {CMPS_NAM} with a composite
Instance ID {CMPS_ID}.
The import external transactions process encountered

an unexpected database error during processing.
The bank statement reconciliation process encountered

an unexpected database error during processing.
This message occurs when there is an application error

when connecting to or updating the Essbase cube.

transaction file.
Retrieving the necessary payment attributes failed
when processing the expense report for
reimbursement.
The following error occurred when processing the
corporate card transaction file: {SQLERRM}.
A SQL error occurred while processing this expense

report: {SQLERRM}. Review the log file for details.
An error occurred that prevents invoices from being
created.
The following error occurred when downloading the

file: {SQLERRM}.
Rules aren't created in BPM because the SOA server is

down or unresponsive, CMDS API failed, the composite
isn't accessible, no task or rule file exists, or the
composite is inactive.
This issue is related to the BI infrastructure used to

generate the notification content. The notification is
based on the following report in the BI catalog:
{REPORT_PATH}.
A system error has occurred in the journal approval

flow. This error wasn't caused by incorrect rule
definitions or service unavailability.
The rule restoration can fail due to one of these causes:
the backed up files not being found due to deletion, the
ESS directory not being accessible, or the UCM server
being unavailable.
This message occurs when there is a failure to raise

business events for intercompany transactions.
An error occurred: {ERROR}. This is a generic message

that covers issues caused by missing shipped data, data
corruption, or code bugs.
The budget cube for the control budget
{CONTROL_BUDGET} can't be identified.
The control budget {CONTROL_BUDGET} is missing from

the budget dimension.
A budgetary control or its setup related process
attempts but fails to connect to the Essbase server due
to connectivity issues.
The budgetary control validation program has
encountered a system error. Check for system errors
related to the following exception to understand the
nature of the failure and determine the corrective
action: {ERROR}.
The burden synchronization subprocess within the

budgetary control validation process failed with an
error: {ERROR}.
The preprocessing procedure prior to the budgetary
control validation program has encountered an error:
{ERROR}.
The control budget balance recalculation process can't
complete due to the following exception:
{EXCEPTION_DETAILS}.
The burden creation subprocess within the budgetary
control validation process failed with an error: {ERROR}.
The postprocessing procedure after the budgetary

control validation program has encountered an error:
{ERROR}.
The burden information retrieval subprocess within the
budgetary control validation process has failed with an
error: {ERROR}.
The period to date value is missing from the lookup
{BALANCE}.
In preparing to release funds as part of the opening
budget period process, the application updated the
process tracking information with an invalid
combination of budget period status and release funds
process tracking number.
The control budget balance recalculation process failed

due to dynamic SQL stack overflow.
The refresh tree for budgetary control process has
encountered a system error: {ERROR}.
The function {FUNCTION_NAME} failed because of
database error {ERROR}.
The function {FUNCTION_NAME} failed because of this
database error: {ERROR}.
An error has occurred in module {MODULE} while

working with the statement {STMT} and the error is
{ERROR}.
A system error is reported on the application
{APPLICATION_NAME}.
A system error has occurred in the program
{LOCATION}, {ERROR}.
The procedure {PROCEDURE} couldn't be called because
of the following database error {ERROR}.
The stored package {PACKAGE_NAME} was generated,

but its status is invalid. The error returned by the
package compilation was {ERROR_MSG}.
A system error occurred in module {MODULE} and the

details of the problem are as follows {PROBLEM}.
Using chart of accounts mapping

{GL_COA_MAPPING_NAME} to derive GL accounts
failed due to a system error.
This system error could happen if the Risk Management
job has failed to run because it requires file storage that
isn't available or isn't in a read-write state.
database is unavailable, the connection pool has been
exhausted, the connection request has timed out, or
some other issue occurred.

database is unavailable, the connection pool has been
exhausted, the connection request has timed out, or
some other issue occurred.
Export operation was terminated because a connection

to the content management server couldn't be
established.
This system error occurred if the Risk Management
import job has failed during the legacy import process
or the incremental data load. The file format could be
invalid, a duplicate name exception may have been
returned even if all validations have passed, or another
system error may have occurred.
An error occurred during transfer of payment info.

Person {PERSON_NAME}. Absence plan {PLAN}.
Assignment {ASSIGNMENT}. Effective date
{EFFECTIVE_DATE}. Payroll processing error {ERROR}.
This error occurs when the user initiates the password

reset request but the request isn't sent because either
the user doesn't have an email or a manager. Even if the
user has a manager, the manager doesn't have an email.
This error message appears when there is a problem

occurs during password validation or resetting of the
password using the Forgot Password Reset flow or the
Password Reset (Preferences task)flows. The log file
contains details of the exception that occurred.
An error occurred while deleting a certificate.
An error occurred during an attempt to export a

certificate to a file.
An error occurred as a role was being saved.
An error occurred during an attempt to save a

certificate to the key store or a key to the credential
store.
An error occurred while importing a certificate from a

file.
An error occurred as a CSR for the certificate was being

generated.
The billing task failed with the following error code:

{ORA_ERRCODE}. This is a system error.
Salary information couldn't be displayed correctly
because no effective date was passed to the page.
The expression engine detected an internal program

error.
The following parameters need to be passed to the task

flow: Person ID {PERSON_ID}, Assignment ID
{ASSIGNMENT_ID}, Work Terms ID {WORK_TERMS_ID},
Effective Date {EFFECTIVE_DATE}, Legal Employer ID
{LEGAL_ENTITY_ID}, Action Type ID {ACTION_TYPE_ID}.

error.

error.
The service or process didn't pass the proper salary
components.
Action occurrence ID is necessary to track logistics

during the creation of salary records, but it wasn't
generated.
There might be a mismatch in the table definition or

other back-end objects.
An internal program error was detected, review the

logs.
An error occurred due a formula, data corruption, or

some other reason.
The XML generation failed for the total compensation

statement.
XML generation failed for this total compensation
statement.
The server is down either due to network issues or
business object synchronization.
An internal processing error occurred when creating a
flexfield database item.
An internal processing error occurred when creating an
element input value database item.
An array operation failed because the array value type
used didn't match the expected value type.
An array operation failed because the array index type
used didn't match the expected index type.
A database query that was expected to return some
data returned no data.
This is an unrecoverable error. The most likely cause is
memory not being released after use in the program
code.
In internal processing, an alias name was found where
an alias name isn't permitted.
Formula function alias names must be unique. The

formula function definition is incorrect.
When loading a formula for execution, an internal

validation check failed.
This is an internal processing error that could be caused
by the formula wrapper generating invalid code or by a
database resource issue.
After replacement of route parameter or context
placeholders, some placeholders remain. This occurs
when the route text or database item definition is
inconsistent with the specified route contexts, or the
route text is inconsistent with the specified route
parameters. Make sure that route parameters and
route contexts are specified for all the placeholders.
The formula code has failed an internal assertion test.
A formula input or context value failed validation

checks.
The database item route text is incorrect. Comments
within database item route text must be terminated.
A PL/SQL error occurred when setting up formula {1} to

be executed.
Database item route text must not be empty and must

be no longer than {2} characters in length.
An internal consistency test detected a problem with a
formula output item.
An error occurred when getting information from the
database.
The application tried to use more than the limit of {1}
formula contexts in use at any one time.
Database items may only have a permitted type (DATE,
NUMBER, TEXT, DATE_NUMBER, NUMBER_NUMBER,
TEXT_NUMBER).
An internal processing error occurred when creating the
database item for element {ELEMENT}.
An error occurred in internal processing when
converting a date value to a string or a string to a date
value.
One or more of the planned changes in the model have
failed validation checks when they were applied in the
application. The proposed changes in the model must
be applied manually to the worker's HR record.
The user is attempting to access data by selecting a

dashboard metric and the user doesn't have the
appropriate security permissions.
The deep link navigates to a responsive page. But the
responsive profile option of that work area isn't
enabled.
This error occurred when accessing the view object
{VO_NAME}. The view object doesn't exist at Run Time.
This error occurred when inserting data with a

surrogate key ID. The surrogate key ID supplied is
already in use.
This error occurred when accessing a flexfield segment
name. The flexfield segment value is provided but the
name is missing.
This error occurred when accessing the application

module {AM_NAME}. The application module doesn't
exist at run time.
This error occurs when effective date records contain

rows that have overlapping effective start and end
dates.
This error occurs when the effective date records for
multiple changes don't have a contiguous effective
sequence for changes within a day and therefore a
sequence gap exists (for example, 1, 2, 4, 5 where 3 is
missing and is a gap). This occurs if records are updated
in a way that bypasses the normal validation. The
DE_OBJECT_NAME token identifies the database table,
PRIMARY_VALUE is the surrogate key ID.
This error occurred when executing the method

{METHOD_NAME} for class {CLASS_NAME}. The class
method doesn't exist or contains an unhandled
exception.
Business event connection factory not found for

namespace. Contact your help desk.
An exception occurred while evaluating the Groovy rule

provided for the event type.
An exception has been raised when attempting to

publish the event. Check the message queue status.
A connection configuration error occurred when

attempting to create a business event connection for
namespace.
The date effective processing failed in method

{METHOD} at step {STEP}.
The goal plan set functionality isn't activated for
responsive Goal Management.
The email server connection didn't work and

authentication failed.
The person was trying to run the Data Upgrade process
but doesn't have the upgrade key or Talent Profile User
Interface Redesign profile option value isn't set to Y.
The Oracle Enterprise Scheduler isn't running or has an
error.
An infrastructure or framework issue might be
preventing the submission of the schedules reset
process. It's possible the application server is down or
that there are runtime issues with SOA or ESS.
This error is raised when an infrastructure or framework

issue prevents the submission of the schedules publish
job. Possible issues include the application server being
down or runtime issues with SOA or ESS.
The error that occurred, such as a database or model

error, isn't directly related to the team schedule.
Some invalid time events can't be deleted due to an

unexpected failure, such as a database connection
issue. Review the log files for more information.
An error occurred that prevented the time card from
being approved.
The time card can't be validated due to a failure.
Some badge exceptions can't be resolved due to a

failure, such as a database connection issue.
The user has calculated predictions in the Manage HCM
Predictive Models set up task; however, the ESS server
is either down or unavailable.
This occurred because of an application error. The
artifact wasn't created because it doesn't use a valid
class.
Some time cards can't be submitted due to an
Some time cards can't be approved due to an
Some time cards can't be deleted due to references not
being fully deleted from all tables. This can be due to a
database connection issue. Review the log files for more
information.
The time card can't be submitted because either there

was a discrepancy in the audit consolidation of the
attribute rows or there was an error when synchronizing
the time card with absence entries.
The time card can't be submitted because either there

was a discrepancy in the audit consolidation of the
attribute rows or there was an error when synchronizing
the time card with the absence entries.
The time card can't be deleted due to the references

not being fully deleted from all the tables.
The time card can't be saved due to either an error in
the setup profiles, or an error in loading the time cards.
A system error occurred that doesn't have an assigned

error message. The context for the error isn't known.
Registration data for the process {PROCNAME} hasn't

been delivered.
A function called getLdgEntId, but the current
ViewObject doesn't contain getLdgEntId.
A direct call to the service or PL/SQL passed a unique

identifier for the assigned payroll record that doesn't
exist in the database. This is most likely caused by
coding error in the method of calling the service or
PL/SQL calling the service.
If the error was returned during processing, then it's

probably the result of predefined data being loaded
with an invalid module ID, or the data is corrupted.
The entry usage start date is set automatically by the

service. This error could be due to corrupted data or a
bug that has occurred during an update.
A direct call to the service or API has been passed a
unique identifier for the payroll relationship record that
doesn't exist in the database.
A direct call to the service or API was passed a unique
identifier for the payroll terms record that doesn't exist
in the database.
A direct call to the service or API has passed a unique
identifier for the assigned payroll record that doesn't
exist in the database.
The payroll action called to process the balance
adjustment group is different from the payroll action
that's assigned to it.
The specified balance adjustment group passed to the
balance adjustment process doesn't exist.
A date effective record that should exist couldn't be
retrieved for processing.
The balance database item was expected to return the
balance value, but it returned nothing.
Either the data was corrupted or an error occurred.
The entry usage start date is set automatically by the

service. This error could be due to data corruption or a
bug that has occurred during an update.
Either data was corrupted or an error occurred.
The Oracle Enterprise Scheduler received a request to

run a balance adjustment process that was already run.
The balance adjustment group should be processed only
one time unless it completed with error.
An attempt was made to enter another record with the

same values for the combination of criteria, for
example, element eligibility and job.
Memory allocation failed because the batch process has
run out of dynamic memory.
A system error occurred during balance expiration
checking.
The process code has failed an internal assertion test.
An application error occurred. A payroll relationship

action was obtained but found to be invalid when
verified for use.
This database item allows the return of only one row of
information but has retrieved multiple rows.
The procedure {PROCEDURE} and step {STEP} identify
where the application error took place.
The error occurred when getting information from the
database.
An application error occurred in the payroll action

creation code.
An error occurred while trying to save your data role.
The enterprise scheduler or SOA managed servers may

be down.
A technical problem has occurred while saving your data

role.
A technical problem has occurred while running an HCM
security service.
Issues found while retrieving the associated secured

objects.
The position hierarchy flattening failed after changing

the parent position to {PARENT_POSITION_CODE} for
effective start date {START_DATE} to the end date
{END_DATE}.
This occurred either due to an application error or

integration error with the external service provider.
There is no default business unit setup on student
financials options page.
The payment can't be processed because the
application registration code is incorrect.
The post payment processing (receipt or invoice
creation) was unsuccessful because the settings in
Oracle Financials may be incorrectly configured. For
example, the wrong business unit may have been used
in setting up receipt classes and methods.
The fee calculation request couldn't be processed

because the Fee Association Group Code or the Artifact
Group Code is incorrect or not valid anymore.
This error has occurred due to a failure in invoice

creation. It can happen when the due date schedule is
missing for the appropriate date or academic period in
context. Also, missing Oracle Financials setup can
account for such a failure.
The user was trying to create an account for student

self-service. The user account creation process didn't
complete because the required setup values are
missing.
The process didn't run because the BI web service didn't

respond or returned an error message.
The process didn't run because population selection
didn't run internally.
didn't receive the selection tool code internally.
The process didn't run because the BI server didn't

respond.
The user was trying to create an account for student
self-service. The user account creation process didn't
complete because the required setup values are
missing.

didn't receive the process context code internally.
The event couldn't be published because the required

parameters of event code and payload are missing from
the publish request.
The payload couldn't be parsed, so the event couldn't

be published. This could be because the payload data
has been corrupted or wasn't constructed correctly due
to data not being available.
The event couldn't be published because the message

component couldn't accept the message being
delivered. This could indicate an issue with the SOA
server or its components.
The event couldn't be published because of an error.

The error could have occurred due to a server or
hardware issue. The error could also have occurred in
the middleware that processes these events.
The event couldn't be published because the messaging
component isn't working. This could be because the
SOA server or one of its components is down.
The event couldn't be delivered to its subscriber due to

an error. The error could have occurred due to a server
or hardware issue. The error could also have occurred in
the middleware that processes these events.
The event couldn't be delivered because the subscriber

isn't reachable. This is most likely because the REST
service is down.
The event couldn't be delivered because the subscriber

is unable to parse the event payload.
The user action failed due to application error

{ERRCODE}, error message {ERRMSG}. The error is
originating from Oracle Fusion Middleware. The error
message text may be enough to help you troubleshoot
the issue. The Oracle Fusion Middleware Error
Messages Reference Guide is also available.
This is an error at the database level, such as a lack of

disk space or permission errors, where the database
couldn't generate PL/SQL package.
The server may have been down when the user saved
his changes.
An error occurred when calling the package generation

code through the rosetta wrapper. The failure of the call
to the formula generation package can happen when a
valid package, or PL/SQL code, doesn't exist in the
database.
An application error occurred while processing the

request for approval. Possible causes could be incorrect
rule setup, or interrupted connectivity due to a
database or application server failure.
An error occurred while delivering the electronic

message.
Funds check encountered an application error.

{REASON}.
An application error occurred while processing the

request for approval.
The application encountered a system error while trying

to generate the PDF.
purchase order.
Purchasing documents couldn't be created because
error was encountered when submitting the
transaction. Possible causes could be incorrect setup, or
interrupted connectivity due to a database or
application server failure.
An error occurred when executing the operation using

web service. This could be caused by a failure in the
service invocation, application middle tier, or data
model.
The approval task couldn't be completed because the

application server or a related web service is down.
The PDF document couldn't be generated or, it was

generated but the application failed to publish it.
Possible causes of failure can be downtime or failure of
the BI publisher server, or downtime of the utilities
server, or network connectivity issues.
Approval rules changes couldn't be deployed to the

rules engine. The possible causes could be interrupted
connectivity or an unreachable SOA server.
The operation to load the agreements couldn't be

completed due to the failure of the Load Agreement
Lines scheduled process that was submitted.
An application error, such as a null-pointer exception,
occurred for the requisition.
An error occurred while trying to update records.
Information about the approval rules couldn't be
retrieved from the SOA server. Possible causes are
interrupted connectivity, an unreachable SOA server, or
issues with the SOA composite.
An unknown purchasing document open interface error

occurred and agreement loader program was stopped.
An SQL error occurred during parser initialization and

agreement loader was stopped.
An unknown error occurred during parser initialization

and agreement loader program was stopped.
An unknown error occurred and agreement loader

program was stopped.
An upload failure occurs if there are loader initialization

errors during the upload process.
An unknown handler initialization error occurred and

agreement loader program was stopped.
One or more components of a supplier profile can't be

updated because they contain data that's no longer
valid.
The supplier profile can't be updated. The issue could
be due to a down server that the application is hosted,
an interrupted network connection with the server, or
any other unexpected reason.
One or more components of a supplier profile can't be

selected because they contain data that's no longer
valid.
An error occurred during the open interface import
process. Review the error code: {SQLCODE} and error
message: {ERRMSG}.
Asset lines can't be generated for assets that aren't in
service. The client extension procedure must exclude
assets that aren't in service.
The client extension to add asset lines to assets has
processed asset lines that are associated to a different
project. Only those asset lines that belong to assets in
the current project should be included.
The client extension that adds asset lines to assets is

attempting to add asset lines to an asset that doesn't
exist.
The generate asset lines client extension procedure has
code that's attempting to generate asset lines for an
asset whose actual service date is after the current
processing date.
The Retirement Adjustment API has returned a generic

error. A review of the diagnostic logs must be done to
determine what caused the failure.
The client extension created to add asset lines to assets
on a project has processed one or more assets with
capital holds. These assets should not be included for
processing.
The client extension that was created to add asset lines

to assets has included assets with the asset type of
estimate that should not have been included.
The asset line generation process has returned an error

due to a problem in the asset allocation client
extension.
The create project assets client extension has an error

that prevents assets from being created. The error is
captured in the diagnostic logs.
The source application may be down for maintenance. It

must be up and running and communications must be
established with the application server.
The source application may be down for maintenance. It
must be up and running and communications must be
established with the application server.
This message was displayed to the user because of an

application error. The exception may have occurred as
the result of database errors, loss of a database
connection, or for other reasons.
The client extension created to process asset lines has

encountered an error that caused the asset event to be
different from the expenditure item event.
An allocation generation error has occurred due to a

system error. The error occurred as part of custom
business logic found in the allocation generation client
extension.
An application error occurred that prevented action for

the issue or deliverable from completing. A application
error can happen due to missing data, another user
deleting the selected record, loss of a database
connection, or application failures.
An application error has occurred while retrieving the

state of the data.
An invalid project definition builder is configured in the
application. The project definition builder was
registered, but it isn't a valid class for use when creating
a project.
An application error prevented the user from

performing an action. The error could have occurred
because more than one user modified the project plan
at the same time, or because the task the user
attempted to modify was already deleted. The error
could have also have occurred if a database connection
was lost and an unexpected SQL exception occurred.
An application error occurred preventing the processing

of the method {METHOD_NAME}. Review the
application server log for further details. The exception
occurs as a result of database errors, loss of a database
connection, or for other reasons.
The task structure for the new project wasn't flattened
for reporting in Oracle Transactional Business
Intelligence because of an application error.
The team members weren't copied to the new project

The burden schedule overrides weren't copied to the

application error.
The organization overrides weren't copied to the new
error.
The asset assignments weren't copied to the new
error.
The cross charge options weren't copied to the new
error.
A new project or project template wasn't created
because of an application error.
The task attachments weren't copied to the new project

The user submitted the process to maintain the project

organization tables. An error that wasn't anticipated
occurred while retrieving the information from the HCM
organization table.
The key performance indicators weren't copied to the

application error.
The project tasks weren't copied to the new project or
The user submitted the process to maintain the project

organization tables. An error that wasn't anticipated
occurred when executing a PL/SQL statement.
The project attachments weren't copied to the new
error.
While the new project was created, the assets weren't
copied to it.
The financial plans weren't copied to the new project or

A source row wasn't found when performing the

operation {OPERATION}.
The data check failed because a key reference failed to

fetch a row in the table {TABLE_NAME}. The specified
value for the column {COLUMN_NAME} isn't valid.
A system error occurred while running the

denormalization process for the enterprise project
structure in Oracle Fusion Project Portfolio
Management.
A system error occurred while adding unassigned

projects to the enterprise project structure on the
Manage Enterprise Project Structure page. The message
appears when the user selects the Include Unassigned
Projects action to add the excluded projects and the
operation fails. An example of how this might happen is
if the Oracle database is out of space, data is corrupted,
or duplicate records exist.
The exception may have occurred as the result of

database errors, loss of a database connection, or for
other reasons.
The error could have occurred if more rows are
returned by a SQL cursor than expected. The error could
have also occurred if a database connection has been
lost and an unexpected SQL exception would have been
thrown.
A database or other application error occurred that

prevented the Maintain Project Resource Search Index
job set from completing. An application error can
happen due to database errors, loss of a database
connection, or application failures.
At least one resource is assigned to a calendar that no
longer exists in the application. A resource must have a
valid resource calendar for the application to calculate
available capacity for the resource.
An error occurred while connecting to the Oracle

Essbase server because the sign in credentials used are
invalid.
An error occurred while connecting the Oracle Essbase

server. Either there is data corruption in the Essbase
cube for the Projects application or the Oracle Essbase
server is down.

Essbase server because the cluster name is invalid.
An Oracle Essbase connection failed or an Oracle

Essbase Provider Services error occurred while
generating KPI values.

Essbase server. Either Oracle Essbase server is down, or
the host and port details are invalid.
The reminder message couldn't be posted on the Oracle

Social Network because either the Oracle Social
Network server is unavailable or the Oracle Social
Network server isn't configured correctly to function
with Oracle Fusion Applications, or the team member to
whom the reminder message is addressed doesn't have
access to Oracle Social Network.
The business entity REST API sends an error message for
most of the common integration errors such as missing
or duplicate information between the business license
and the business entity during business entity
processing. However, this error message appears when
a failure occurs for any other reason, such as a problem
with the Trading Community Architecture integration or
other data errors.
This error message appears when a failure occurs for

any reason such as the activity transaction isn't
generated or the due date can't be recalculated.
The process failed because the report configuration or
transaction type setup is incorrect.
At least one of the contractor license setup options

must be active for the contractor license validation to
get the required license information.
At least one of the contractor license setup options
must be active for the contractor license validation to
get the required license information.
Some of the parameter information in the http string is
missing.
The autonumbering rule doesn't specify the format of
the autonumbering sequence.
The requested resources size is greater than the full

resources size that lies beyond the end of file.
The server doesn't recognize the request method, or it

lacks the ability to fulfill the request.
An autonumbering rule couldn't be found. This could be

due to incorrect setup or to a database error.
This is a generic diagnostic message indicating that the

process failed due to incorrect setup or many other
possible errors.
This permit application doesn't have any valid terms of
use definitions. Either the terms of use definition is
expired, or it isn't available for the selected permit.
This is a generic diagnostic message indicating that the

process failed due to incorrect setup or many other
possible errors.
The autonumbering process couldn't generate the next
sequence number due to incorrect setup or other
database errors.
The servers don't recognize the http header attribute

values.
The failure reason could be the following: The permit
fee couldn't be calculated, or there is another network
issue such as the checkout service isn't available.
The process failed because the report parameters or

report URL are incorrect.
The process failed because it couldn't retrieve the

accounting date for the transaction from the general
ledger accounting calendar.
The process failed while creating a subledger accounting
event because subledger event types aren't properly
defined, or the user doesn't have the proper security
access assigned.
The error may have been caused by a database

connectivity issue, duplicate data, or an application
issue.
issue.
There is a problem integrating with Oracle Integration
Cloud.
The payment page used for checkout should return a
response when the payment for items in the payment
cart is submitted. The returned response should
indicate that the payment status is canceled, successful,
or failed. The error message indicates that an error
occurred and the response couldn't be generated. This
message is used to capture outside cases that aren't
covered by other error messages on the payments and
billing side, such as Invoice Creation Failed and Bill
Creation Failed.
The request entity information was too large and

exceeded the maximum request size for the browsers.
An unknown exception has occurred on the server.

The checkout page was accessed by a user with an
invalid checkout ID, invalid checkout status, invalid
checkout data or with an invalid party ID.
An HTTP request was sent to a delegation-related POJO
endpoint without a PSC_DELEGATE_TOKEN.
The delegation identifier couldn't be retrieved because
the verification token for the delegation operation is
invalid or expired.
The URL for the delegation confirmation page doesn't
contain the verification token.
An accounting event wasn't found for source
{SOURCE_NAME} and business function {FUNCTION_ID}.
Accounting events must be added by Oracle.
Batch request ID {BATCH_ID} wasn't found in table

{TABLE}.
The journal {JOURNAL_ID} wasn't found in table
{TABLE}.
The {FIELD_NAME} field is required for this accounting
source transaction. Missing field values must be added
by Oracle.
The process failed because the configuration for
accounting event {EVENT_ID} doesn't contain
transaction field information.
The process failed because the Agency ID specified in
the transaction isn't valid.
The BIP report configuration must be complete before a
BIP report can be printed.
The autonumbering rule for the Cashier Session number
type must be numeric.
A SQL error {ERROR_ID} occurred when updating table

{TABLE}.
A SQL error {ERROR_ID} occurred when inserting rows
into table {TABLE}.
The Incoming Incidents worklist displays issues with the
types and subtypes that match the user's job function
attributes. This user doesn't have any issue type or issue
subtype attributes, so the user can't access issues on
the Incoming Incidents worklist tab.
There are no planners assigned with the job function of

planner or no planners are assigned to the planning
application type on the manage agency staff page.
An error occurred during communications processing of

the final inspection notification.
The message appears when the payment service that

calls confirmPayment to update the fee status fails. The
error might be caused by code level or network
exceptions.
The message appears when the payment service calling

confirmPayment that generates an invoice fails. The
error might be caused by code level or network
exceptions.
The message appears when the ConditionListDetails

method validation didn't function properly. The
condition REST service failed to return a response while
checking for any lock or hold conditions with payment
restrictions.
The message appears when the payment service that
calls confirmPayment fails to generate the accounting
transaction. The error might be caused by code level or
network exceptions.
The message appears when the process to retrieve the

REST endpoint returns an exception. The error might be
caused by code level or network exceptions.
The message appears when the process to retrieve the

REST endpoint returns an exception. The error might be
caused by code level or network exceptions.
This is a General Conditional REST return error message

from the fee calculation.
The user isn't configured as an authorized creator for

the selected change type.
The selected lookup value {ATTR_VALUE} was

deactivated or removed after it was created, so it can't
be used for new object creation.
The item was not generated due to an application error.

The item generation is either set to rule generated or
sequence generated at the item class setup, or incorrect
parameters are used.
There was an application error when trying to load the

VO of an Oracle Applications Unlimited object type. This
could be caused by a mismatch in the connector type of
the active connector or an invalid connector
configuration.
There was a general failure during a normal functional

operation in the Applications Unlimited integration
framework. This could be caused by a mismatch in the
connector type of the active connector.
An Oracle Applications Unlimited item that was linked in

Oracle Fusion PLM does not work properly. This could
be due to a mismatch in the connector type.
The ID of an Applications Unlimited object being used in
Oracle Fusion Innovation Management is not found or
does not correspond to the connector type of the active
connector.
There was an application issue when trying to load the

VO of an Oracle Applications Unlimited object type. This
could be caused by a mismatch in the connector type of
the active connector or an invalid connector
configuration.
The ID of an Oracle Applications Unlimited object being

used in Oracle Fusion Innovation Management is not
found or does not correspond to the connector type of
the active connector.
There is an error in the key that is used to store

thumbnail images. This could be due to an invalid
configuration or mismatch in the connector type.

Oracle Fusion PLM appears to be invalid. This could be
caused by an invalid connector or database data issues.


The Oracle Applications Unlimited to Oracle Fusion

Innovation Management mappings are configured
incorrectly and the expected classes are mismatched in
the application to what Oracle Applications Unlimited
returns.
Users cannot connect to Oracle BI Publisher if the BI
Publisher Server, which is a separate server and
application, is unavailable for a variety of reasons, such
as the power went down for that server, the server was
rebooted, or the administrator removed the user from
the BI Publisher Server by mistake.
The user does not have permissions to access the report

template in the BI Publisher Server.


There is an error accessing BI Publisher. There is an

error Message: {BIP_ERROR_MESSAGE}. There is a
report ID: {BIP_REPORT_ID}.
issue.
This is most likely caused by a server failure, an
interrupted network connection, or an invalid setup.
The receipt accounting distribution process failed due to

invalid data from receiving source system.
The cost adjustment wasn't saved due to an application
error.
The cost processor was unable to derive the valuation
unit due to an application error.
The valuation unit wasn't created due to an application
error.
An SQL exception occurred during Valuation Unit
generation.
One or more records to be processed using set-based
processing could not be processed and had to be
quarantined so that other records could be processed.
The quarantined records will need to be investigated
and released from quarantine. Records are typically
quarantined due to application error data and require
the help of support for debugging and resolution.
To diagnose this message refer to error reference:

{MESSAGE}.
The incident log includes details of the error.
An invalid lookup code was passed to the messaging

service.
service.
The lookup code that the messaging service sends is not

valid.
service.
The process that sends the e-mail notification or

document to the customer contact failed, typically
because of a setup problem.
A user attempted to create an order document or a

background process tried to send an automatic
notification, but an error occurred, most likely with BI
Publisher, that prevents the application from creating
the document. The process that creates an order
document or sends notification of a sales order event
failed.
An application error occurred while initiating the
approval human task.

electronic record.
An application error occurred while generating an

Oracle BI Report or attaching a generated report to the
electronic record.
An application error occurred while submitting the

Generate Electronic Records process.
An application error occurred while generating an

Oracle BI report or attaching a generated report to the
BPM human task.
Item batch did not get deleted due to a system error.
The user attempted to carry out an operation without

sufficient privileges or is not authorized to perform.
The item number was not generated due to an

application error. The item number generation is either
set to rule generated or sequence generated at the item
class setup, or incorrect parameters are used.
The SOA process has failed and require review of the log
files to determine the issue that caused the exception.
The item description was not generated due to an
application error. The item description generation is
either set to rule generated or sequence generated at
the item class setup, or incorrect parameters are used.
The item class could not be created as entered.
Style item reference for a SKU item does not exist.
A service failure occurred in the attempt to discard a

draft revision.
The call to the constraints framework failed.
The call to the revision service failed.
The call to the revision service failed.
An incorrect payload, incomplete or incorrect setup in

pricing, or some other underlying error occurred while
pricing the sales order.
The event information web service failed due to a
system error or time out.
The task processing failed due to an error or time out.
The event processing failed due to an error or time out.
An application error occurred while calculating the

transfer price.
An application error occurred while retrieving the sales

order unit price.
A system error occurred when calling the business

event connection factory for raising the event.
An error occurred when calling the business event
connection factory for raising the event.
The Item Cost service connection failed in method

{METHOD_JOB_NAME}, file {JAVA_FILE_NAME}.
An error occurred while conducting an inventory

transaction that does not have a corresponding profile
option {PROFILE}.
An error occurred while creating data for object
{OBJECT_NAME}, error {SQL_ERROR}.
An error occurred while creating a locator for a

subinventory during an inventory transaction.
The call to the transaction manager failed in method

{METHOD_NAME}, file {JAVA_FILE_NAME}.
An error occurred when executing the min-max
planning process to create movement request in
procedure {PROCEDURE_NAME}. Details: {MSG_DATA}.
The error occurred while executing a save in method

The error occurred while executing method
An error has occurred in calling the Inventory
Movement Request function to create the movement
request replenishment order.
The error occurred while executing {VO_NAME} query
method {METHOD_NAME} file {JAVA_FILE_NAME}.
An error occurred when executing the min-max

planning process in procedure {PROCEDURE_NAME}.
Details: {MSG_DATA}.
The Export Count Sequence process failed due to an
application error in method {METHOD_NAME}, file
{JAVA_FILE_NAME}.
An error {ERROR_CODE} occurred when executing the
min-max planning process in procedure
{PROCEDURE_NAME}.
An invalid supply cursor mode {CURSOR_MODE} was
passed in procedure {PROC_NAME}.
An error occurred when processing reservations during
pick release.
An error {ERROR_CODE} occurred when maintaining

inventory supply records in procedure {PROC_NAME}.
An error occurred while releasing the database lock for

the quantity tree.
An error occurred while parsing the quantity tree.
An error has occurred in calling the Replenishment

Requisition function to create the Procurement
Requisition Import records.
An error occurred when creating request to print a pick
slip report during pick release.
An invalid supply entity type {ENTITY_TYPE} was passed
in procedure {PROC_NAME}.
An error occurred in the reservations service causing
the service to fail for an unknown validation exception.
An error has occurred in the replenishment function to

create the replenishment order requests through the
Supply Chain Orchestration process.
An error occurred while calling the quantity tree using
the following parameters: {QT_PARAMETERS}.
An error occurred while calling the API to transfer

reservations for an unconfirmed quantity.
An error has occurred in the replenishment function to
retrieve the secondary unit of measure for the item.
An error occurred while parsing the quantity tree.
An error occurred while acquiring database lock for the

quantity tree.
An attempt to modify the protected plan option

parameter {ATTRIBUTE_NAME} was made by the
application. The value was restored to the value
{ATTRIBUTE_VALUE}, and then the plan was run.
An application error has occurred in the demand

forecasting engine. The automated engine recovery
process could not resolve the issue.
Due to database or other application problems, the
application is unable to clean up the past records of
editable analytical measures. Collect application log files
for further analysis.
An error occurred in a call to the database. This may

occur when the database is unavailable or no database
connections can be allocated.
An error occurred when starting the demand
forecasting profile {PROFILE_NAME}. The error is due to
invalid demand forecasting profile definitions.
During a Plan Run action, an unsupported refreshing

mode was presented to the application. Plans of the
Sales and Operations plan type only support the Full
Refresh and No Refresh modes. The displayed message
shows the name of the mode that was attempted, but is
not supported. Collect application log files for further
analysis.
During a Plan Run action, the application discovered

that the record of an WillBeInput data entity is missing
from supply or demand snapshot process or its content
is not accessible. Collect application log files for further
analysis.
This error occurs in the Build Plan phase, but may be
reported in a later phase. The error occurs when there
are dimensions in the measure granularity of the
measures in the measure catalog that are not available
in the dimension catalog.
During the Plan Copy, Run, Load, Close, or Delete

actions, due to database or other application problems,
the application is unable to complete the action. Collect
application log files for further analysis.
Reasons measures can fail to load include required

values missing due to configuration issues, self-
referencing expressions, and dependency issues.
Measures which involve weighted average,
computation, or archive are not supported for the Load
Measures from Other Plans process. Other reasons
measures can fail to load include required values
missing due to configuration issues, self-referencing
expressions, and dependency issues.
During a Plan Run action, due to a memory problem, the

application is unable to generate the aggregate supply
network. This problem may occur when the Java heap
size is set too low for the plan size.
The backlog planning solver failed to yield planning

results. This failure is probably due to problems related
to the Enterprise Service Scheduler.
During a Plan Run action, the application was unable to

load the demand plan measure to the shipments
forecast. This error occurs during a Plan Run action
when the application is unable to access the demand
plan or the measure isn't available in the demand plan.
During a Plan Run action, due to database or other
application problems, the application is unable to save
the aggregate supply network. This error occurs during
a Plan Run action when the application is unable to
store the initial aggregate model to database, due to
database or other application problems.
During a Plan Run action, due to solver problems, the

application is unable to solve in memory the aggregate
plan model. This error occurs during a Plan Run action
when the application is unable to solve the in memory
aggregate plan model, due to solver problems.
This error occurs during a Plan Run action in No Refresh

mode when the application is unable to append records
of edited analytical measures to the content of the in
memory aggregate plan model, due to database or
other application problems.

application problems, the application is unable to store
the content of the in memory aggregate plan model to
the database. This error occurs during a Plan Run action
when the application is unable to store from memory to
database the aggregate plan model, due to database or

application problems, the application is unable to load
into memory the content of the stored aggregate plan
model. This error occurs during a Plan Run action when
the application is unable to load the content of the in
application problems, the application is unable to insert
records of analytical measures from the content of the
in memory aggregate plan model to the database. This
error occurs during a Plan Run action when the
application is unable to insert measure data from the in
The XSS java stack size setting was set too small when
your environment was configured.
An application error has occurred in the process. The

processing could not complete successfully.
A system error occurred while initiating the scheduled
process for the demand forecasting profile
{PROFILE_NAME}. The demand engine was terminated
due to the Oracle Enterprise Scheduler Service not
being available to process the request or not
responding.
An exception occurred when opening a table or graph.
The Oracle Fusion Global Order Promising Engine could

not process the request. Check the response payload for
more details.
An error occurred with the service named
{SERVICE_NAME}.
At least one of the parameter values is not provided or

is not valid.
An error occurred while creating a new plan. The user is

advised to try again because the problem may be
something being temporarily unavailable, such as a
server.
A system error has occurred while attempting to run the

Refresh the Oracle Fusion Global Order Promising
process to refresh the data store files into directory
datastore0.
Connection to Oracle Fusion Global Order Promising
could not be established.
An application error has occurred in refreshing the

Oracle Fusion Global Order Promising data store. This
may occur due to data modeling issues in ODS data or
due to issues in refreshModelAsync WS invocation or
Oracle Fusion Global Order Promising engine startup
problem.
The table containing forecast parameters cannot be

found.
The table used for task allocation during the forecasting
process cannot be found.
The demand forecast failed during the forecast output
process.
The parameters associated with the forecasting profile
are empty.
The list of available causal factors is empty.
Some of the causal decomposition groups may have

incorrect dimension definitions.
The demand forecast failed during the data aggregation

process.
The demand forecast failed during the data set analysis
process.
Some of the causal decomposition groups may have
incorrect dimension definitions.
The demand forecast failed during the process of

decomposing the forecast output.
A predefined list of forecasting methods cannot be

found.
The demand forecast failed during the branch allocation

process.
The selected calendar does not have sufficient
information.
The demand forecast failed during the error metric

generation process.
The demand forecast failed while resetting the forecast.
The parameters for the forecasting method cannot be

found.
A system error occurred while trying to promote

algorithms.
An error occurred during an attempt to start a

scheduled job to generate backing schedule data for
working time, week, year, and period start dates.
A contract manufacturer is an organization that's
modeled as a supplier. The supply data upload process
is: The supplier uploads supply data using the
Collaboration Supply Data Uploads REST resource. Then
the Load Supply Data for Externally Managed
Organizations scheduled process job is initiated. Then
the Load Supply Data for Externally Managed
Organizations scheduled process job initiates the Load
Planning Data from Flat Files scheduled process job as a
child process. Then the Load Planning Data from Flat
Files scheduled process job will log any errors to the
scheduled process log file. Since suppliers can't view
scheduled process log files directly, they need an
enterprise user to report any errors received.
Generating the work order number failed, possible

causes are: The document sequence setup for the
organization is missing or incorrect or the generated
work order number is exceeding the maximum attribute
length or document sequence maximum capacity has
been reached.
The import batch failed due to a system error.

Error {ORA_ERROR_CODE} occurred at PL/SQL package
{PL_SQL_PKG} in procedure {ORA_PROC_NAME} while
trying to create operation transactions.
An application error occurred while creating the packing

slip document sequence category {CAT_CODE} within
the Shipping Parameters user interface for the
inventory organization {ORG_CODE}. There is a problem
with either the data that is being processed or the code
itself. The FND document sequence API failed with error
code {ERROR_CODE}.

document sequence {DOC_SEQ_NAME} within the
Shipping Parameters user interface for the inventory
organization {ORG_CODE}. There is a problem with
either the data that is being processed or the code
code {ERROR_CODE}.
An application error occurred while assigning the

document sequence category {CAT_CODE} to the
document sequence {DOC_SEQ_NAME} within the
Shipping Parameters user interface for the inventory
organization {ORG_CODE}. There is a problem with
either the data that is being processed or the code
code {ERROR_CODE}.
An application error occurred while generating the

document sequence value for Packing Slip Document
Sequence Category {CAT_CODE}. There is a problem
code {ERROR_CODE}.
An error occurred while submitting the Release Pick

Wave scheduled process. This error may occur because
the Oracle Enterprise Scheduler Service Server is not
available or there are unknown technical issues in the
Oracle Enterprise Scheduler Service Server.
document sequence value for bill of lading document
sequence category {CAT_CODE}. There is a problem
code {ERROR_CODE}.
The cause for the failure for this transaction is the

failure of the API on the Financial Application to provide
the tax related details to WSH as the same couldn't be
calculated by an automated process in FOS.

document sequence value for commercial invoice
document sequence category {CAT_CODE}. There is a
problem with either the data that is being processed or
the code itself. The FND document sequence API failed
with error code {ERROR_CODE}.
The call to the ship confirmation transaction failed in

the routine {API_NAME} after the process step
{PROCESS_STEP} in the package {PACKAGE}.
An error occurred while acquiring database lock on
shipment lines.
A deadlock occurred when trying to establish a database

lock on a shipment line.
The transaction failed in the package routine

{PACKAGE}.
The Pick Wave process failed due to an application error
in routine {API_NAME}, package {PACKAGE}. SQL error
message: {SQLERRM}.
Service {SERVICE_URL} specified for the business object
can't be found.
An invalid value has been passed to the program.
Some problems occurred while regenerating the

domain connections. {CONNECTION_ERROR}.
Authorization on the remote client failed while invoking
task {TASK}. It's identified with the code {TASKCODE}
that invokes the program {TASKFLOW} of module code
{MODULE}.
An error was received for the task {TASK}. It's identified

with the code {TASKCODE} that invokes the program
The enterprise application {ENT_APP} referenced by

task {TASK} wasn't found.
The service {SERVICE_URL} must have the asynchronous

importDataAsync method enabled.
A Service Message Transmission Optimization

Mechanism policy can't be found for service
{SERVICE_URL}.
The offering import process didn't succeed due to one

or more reasons described in the log file.
The service {SERVICE_URL} must have the asynchronous

exportDataAsync method enabled.
The offering file wasn't generated due to one or more

reasons described in the log file.
An error can occur when the service isn't registered

correctly and isn't available at the time it was invoked.
Service information isn't found for the

{BUSINESS_OBJECT} business object.
The service {SERVICE_NAME} returned the following
error while executing the task {TASK_NAME}:
{SERVICE_DETAILS}.
Functional Setup Manager is expecting to receive the
scope selection parameters from the task
{SEARCH_TASK}. This task only returned parameters
{SCOPE_PARAMS}.
The service {SERVICE_NAME} didn't return an Process ID

or a status as expected.
The end point URL for application

{APPLICATION_NAME} couldn't be reached because the
server information is incorrect or the server may be
down.
One of the prerequisite conditions for this operation

isn't met.
There may be an issue with the Functional Setup

Enterprise Storage Server application.
The service {SERVICE_URL} must have both

exportCriteria and exportControl method parameters
enabled respectively.
An application error encountered by the producer

server prevented it from rendering the program
Service must return status after processing the setup

data and any error messages relevant to the process.
The service {SERVICE_URL} must have both importData

and importControl method parameters enabled
respectively.
Some errors occurred while generating the setup data
report. Error: {ERROR_MSG}.
Message Admin Action
Verify that the notification exists, or search for another
reason why the notification cannot be found in the
notifications table.
Review the notification attribute missing values to
determine what went wrong.
Review the notification attribute values to determine
what went wrong.
Review the notification attribute values to determine

what went wrong.
Review the notification attribute missing values to
determine what went wrong.
Upgrade to a newer release, if possible, and ensure that

the key {HELP_KEY} is in the help tables.
Check whether the Oracle Fusion Application Toolkit
JAR files are in classpath.
Check the error stack for the cause of failure. If the
cause was the database connection or a Functional
Setup Manager issue, then resolve that issue and
restart the managed server.
Ensure that the Key {HELP_KEY} is in the help tables.
For the profile value of the Mapping Service for

Contextual Addresses profile option, enter the URL for a
mapping service.
Check your help configuration to ensure that access to
help has been set up correctly.
-
-
-
-
Log a service request so development can investigate

those errors.
Check the knowledge application configuration settings

to confirm that they're correct.
Ensure that the knowledge integration has the correct

credentials and can be authenticated by the
application.
Check whether the attachment server is running
correctly.
Check whether the published articles are available in
the environment or the content processing was run
successfully.
Confirm whether knowledge articles have been created

and published. If content is available in the knowledge
repository, confirm that knowledge content processing
has run to generate a search index.
Check the locale table for the locale object.
Verify that the knowledge application is available. If so,

restart the export or import process. If not, or if the
error persists, contact Oracle Support for assistance.
Contact Oracle Support to check the topology definition

for module ORA_CRM_REST in the topology manager.
Verify that the knowledge application is available. If so,

restart the export or import process. If not, or if the
error persists, contact Oracle Support for assistance.
Verify that the available locales on the source

environment and the target environment are identical.
If so, restart the import step of the export or import
process. If not, or if the error persists, contact Oracle
Support for assistance.
Restart the import step of the export or import process.

If the error persists, contact Oracle Support for
assistance.
Verify that the knowledge application can be accessed

on the target environment. If so, restart the import step
of the export or import process. If not, or if the error
persists, contact Oracle Support for assistance.
Make sure that the target instance configuration isn't
modified during the import step of the export/import
process. Restart the import step of the export/import
process. If the error persists, then contact Oracle
Restart the import process. If the error persists, contact

Oracle Support for assistance.
Restart the import or export step of the export or

import process. If the error persists, contact Oracle
Verify that the source instance locale configuration has

at least one active locale. If there is an active locale,
restart the export step of the export or import process.
assistance.
Ensure that the exported configuration file isn't

modified manually before the import step of the export
or import process. Verify that the exported
configuration file has valid locale record IDs. If so,
restart the import step of the export or import process.
assistance.
Verify if the domain parameter value passed during the

export step in the export or import log files is empty.
Restart the export step of the export process again. If
the error persists, contact Oracle Support for
assistance.
Verify in the export or import log files for the mode

parameter value passed during the export step that it
isn't empty. Restart the export step of the export or
import process again. If the error persists, contact
Verify in the export or import log files for the

parameter values passed during the export step that
they aren't empty. Restart the export step of the export
or import process again. If the error persists, contact
Restart the import process. If the error persists, contact
Restart the export or import process. If the error

Restart the export or import process. If the error

Ensure that the target instance configuration isn't

modified during the import step of the export or import
process. Verify that the content field {REFKEY_FIELD} or
the content type {REFKEY} or both are absent in the
target environment. If this is the case, then stop the
export or import process because it will reintroduce
these objects to the target instance. If they're present,
then restart the import step of the export or import
process. If the error persists, then contact Oracle

configuration file has the document prefix ID for the
content Type {REFKEY}. If so, restart the import step of
the export or import process. If the error persists,
contact Oracle Support for assistance.

configuration file has a name for the content Type
{REFKEY}. If so, restart the import step of the export or
import process. If the error persists, contact Oracle
Verify that the source instance locale configuration has
at least one active locale. If there is an active locale,
restart the import step of the export or import process.
assistance.
Assure that the target instance configuration isn't

modified during the import step of the export/import
process. Verify that the absence of the content type
{REFKEY} on the target environment is valid. If so, stop
the export/import process as it would reintroduce
these objects to the target instance. Else, restart the
import step of the export/import process. If the error
persists, then contact Oracle Support for assistance.
Retry the task after some time. If the error persists,












Review the log for details of the issue. Contact Oracle

Contact Oracle Support for assistance.
Review the error log to determine the cause of the

issue. Contact Oracle Support for assistance.
Review the geography validation setup. Contact Oracle

Contact Oracle Support to review the log and status of
the database.
Open the global function using Oracle Fusion CRM
Application Composer and fix the Groovy expression to
return the correct string.
Open the global function using Oracle Fusion CRM
Application Composer and fix the Groovy expression to
return the correct string.
Review the diagnostic log details to determine why deal
registration assignment failed.
Verify the UCM server status and connection between

the Sales server and the UCM server. Verify the user
permissions.
Review the log to determine the cause of the failure.

Restart the UCM server if it was unavailable. Contact
Oracle Support if needed.
Resolve the error that the content management server
displayed in the error message.
Review the log to determine the cause of the error.

Restart the UCM server if it was unavailable. Contact
Check the health of the BI server and verify that the
connection between the Sales and BI server is working
correctly. Contact Oracle Support if needed.

Verify the health of the FusionESD application. Contact
Add daily conversion rates for the currencies being

used.
Review the diagnostic log file for additional details.
Ensure that the load-and-activate process for territory

management has finished.
You must define an active rule for work object

{WO_CODE}, candidate object {CO_CODE}, assignment
mode {AM_MODE}, and rule set group {RULE_SET_GRP}
in the appropriate application Manage Assignment
Rules setup task.
Verify the view object definition for the assignment

object in the appropriate application Manage
Assignment Objects setup task.
Check for missing information that's required for the
work object in the appropriate application Manage
You must define an active rule set for work object
mode {AM_MODE}, and rule set group {RULE_SET_GRP}
Rules setup task.
You must either provide valid values for the object
that's being assigned or update the mapping definition
Objects setup task.
You must define an active rule category for work object

mode {AM_MODE} in the appropriate application
Manage Assignment Objects setup task.
You must either provide values for the object that's

being assigned or update the mapping definition in the
appropriate application Manage Assignment Objects
setup task.
You must provide valid values for the object that's

being assigned and update the mapping definition in
the appropriate application Manage Assignment
Objects setup task.
Check the assignment object definitions for the work

object {WO_CODE} and candidate object {CO_CODE}
combination in the appropriate application Manage
Check the assignment object definitions for work object

{WO_CODE}.
Change the setting of the no match handling option, or

review the assignment rules to understand why there
are no matching candidates.
You must define at least one active mapping set and

mapping for the work object code {WO_CODE} and the
candidate object code {CO_CODE} in the appropriate
application Manage Assignment Objects setup task.
You must establish a relationship between the work

object {WO_CODE} and the candidate object
{CO_CODE}.
When the refresh is complete, resubmit the object for
assignment.
Review the value of the candidate object display
attribute in the appropriate application Manage
You must define primary key attributes for assignment
object {AO_CODE} in the appropriate application
Manage Assignment Objects setup task.
Review the rules in the appropriate application Manage
Assignment Rules setup task. Ensure that a single value
is returned for the rule conditions that are defined.
Update and publish the assignment object to register it

with the latest view object definition.
Run the assignment processing in diagnostic mode for

the identified work object.
You must enable either the Assign Candidate option or

the Run Custom Logic option. Check the assignment
object definition for the work object {WO_CODE} in the
appropriate application Manage Assignment Objects
setup task.
You must enter a work object low attribute for mapping

type {MAPPING_TYPE}.

Register the candidate object again using the Manage

Assignment Objects page. Also check if the data can be
loaded using the view object specified for this
candidate object.
Contact Oracle Support to review the logs to resolve

this.
Check the BI server status and make sure it's up and

running.
Review the error details and incident logs for further
diagnosis.
Review the log file for the exception and error that
occurred from the same user and session, prior to
failure from mapping hierarchies.
Review the error log for other messages related to this

failure.
Open the configuration in your field service instance
and select the activity type for the work order type with
the label {WO_ACTIVITY_ID}. Modify the activity type
by deselecting the multiday activity property, then save
the changes. The multiday activities aren't supported in
this integration. If the multiday property wasn't
selected, then open the resource that maps to the
selected work order area {WO_AREA}, and verify the
skills associated with the resource. In the configuration,
open the work skills and verify that there is a work skill
condition for a work skill associated with the resource.
The work skill condition connects the activity type to
the resource through the work skill.
Work with the Oracle Field Service Cloud administrator

to complete the quota setup for the resource and
capacity category. If the Work Order Type should not be
active, contact the sales application administrator to
disable it.
Specify a value for the account key, or remove the value

specified for the account key.
Review the log file to find the root cause.

Verify Field Service is active, validate the connection in
the Manage Service to Field Service FSM Task and make
the required corrections to the url or user credentials to
successfully validate the connection.
Enter a new message with the message code in the

Manage Integration Messages FSM Task and correct the
integration flow in ICS or the API.
Review the incident log for additional error details.
Review the diagnostic log for additional details about

the error, and take corrective action. If the problem
Contact Oracle Support to have the required data

loaded.
Review the diagnostic log for additional details about
the error, and take corrective action. If the problem
Review the application server logs for additional details

and look for any exceptions containing text
handleOfferAccepted.
Contact Oracle Support to verify whether the
application isn't able to connect to the credential store
or the credential store is down, and to help resolve the
issue.
Get the correct email account values from Oracle

Support and then register them in the Access Point
Setup table.
Get the correct email account values for your

implementation from Oracle Support and then update
the SVC_INBOUND_EMAIL_ADDRESSES profile option
value.
Contact Oracle Support to review the diagnostic logs.
Use the Manage CX Sales to CPQ cloud set up page to

correct the parameter values entered for the create,
edit, copy, version and get proposal actions.
Create a sandbox with Page Composer enabled at the

appropriate layer. Using Page Composer and Configure
UI, from the Filters tab, move the deleted custom filter
from the Selected list to the Available list and click
Save. Publish the Sandbox. Alternatively, if
personalization is enabled, users can use Configure UI
to hide the deleted filter.
References to the deleted action must be removed

from the Actionable Infolet. Create a sandbox with Page
Composer enabled at the appropriate layer. Using Page
Composer and Configure UI, from the Actions tab, move
the deleted custom action from the Selected list to the
Available list and click Save. Publish the Sandbox.
Alternatively, if personalization is enabled, users can
use Configure UI to hide the deleted custom action.
Refer to incident log for specific error conditions.

Investigate status of Workspace search server and
remediate server issue. This may require restarting the
Workspace search server.
Contact Oracle Support to review the log files and

incident reports.
You must either configure the User Merge Requests

profile to allow processing without giving approval or
implement Oracle Fusion Trading Community Hub to
process merge requests.
Contact Oracle Support to investigate the status of the

service.
Enable the data quality cleanse server by selecting the

Enable Cleanse Operation check box on the
corresponding Edit Server Configuration page.
Enable the data quality match server by selecting the
Enable Match Operation check box on the
corresponding Edit Server Configuration page.
Review the application logs and the OBIEE server logs to
see why the sync process failed. Contact the vertical
development environment team for assistance.
Review the application logs and the OBIEE server logs.

Contact the vertical development environment team if
needed.
Review this message with the OBIEE server team:
{BI_ERR_MSG}.
Restart the OBIEE server. Review the application logs
and the OBIEE server logs to see why the OBIEE server
is not available.
Review the application logs to determine why the sync
process failed and contact the vertical development
environment team.
Review the application logs and contact the vertical

Restart the OBIEE server and then rerun the sync

process.
Review the application logs to see why the sync process

failed and contact the vertical development
environment team.
Review the application logs and the OBIEE server logs to

see why the sync process failed. Contact the vertical

process failed. Contact the vertical development
environment team.
Review the application log, SOA server log, and the

OBIEE server log to see why the sync process failed.
Contact the vertical development environment team.

process couldn't be started and contact the vertical
Contact the Intelligent Advisor hub administrator, who
must reconfigure the connection to CX Sales from the
hub. Deleting and recreating the connection to CX Sales
from the hub is a possible solution.
Set the ORA_ZCX_CLOB_MAX_LIMIT profile option to a

higher value, keeping in mind any future needs and
performance impact.
Set the ORA_ZCX_DCL_MAX_LIMIT profile option to a
higher value, keeping in mind any future needs and
performance impact.
View the logs to determine why the error occurred.

Contact Oracle Support if needed.
Review the log to determine why the error occurred.



Review the log and restart the Oracle BI Server.
Ensure that the CRM Analytics server is running before

the custom subject area is inactivated again.

Resolve this error by importing the business intelligence

view object into the Oracle BI EE repository.




the custom subject area is published again.







the custom subject area is published again.

Review the application log to determine why the error

occurred. Contact Oracle Support if needed.

Contact Oracle Support to manually fix the custom
subject area definition in MDS.
Review the warning messages in the application log and

the OBIEE server log. Contact the vertical development
environment team if needed.
Determine the cause by checking the SOA logs and the
execution of the
ExtnFrameworkAsyncCrmAnalyticsServiceComposite
SOA composite. Contact Oracle Support if needed.



the custom subject area is activated again.

Create a new sandbox, repeat the configuration, and try

again.



Check the server status. Review the log to determine

why the error occurred. Contact Oracle Support if
needed.
View the Oracle BI server logs to determine the status

of the BI Server. Restart the BI Server or contact Oracle
Support if needed.
Review the Analytics Application Server incident log to
trace the actual causes and fix the related server issues.
Confirm that the connection to the Oracle Business
Intelligence server is valid.
Review the Application Server incident logs and

Analytics Application Server incident logs to trace the
actual causes and fix the related server issues. Confirm
that the Analytics Application Server connection is valid.
Check the server status. Review the log to determine

why the error occurred. Contact Oracle Support if
needed.
Contact Oracle Support and review the log files.
Restart the CRM Analytics server. Contact Oracle

Support if needed.



Review the log to check the format of the schema URL

or for details of the IO exception. Configure a valid URL
for the registration.
Contact Oracle Support for assistance. Provide error

log.
Review the logs to determine the nature of the IO

exception and which file it occurred on. Contact Oracle
Support if necessary.
Contact Oracle Support for assistance. Provide the
detail error log as well as the XML files.
Review the other service error to understand the
nature of the failure and determine the corrective
action.
Reset the user credentials and generate a new

password.
Verify that the server configuration file has valid XML

format. Use XML validator to correct any syntax error.
Refer to the default server configuration for
comparison.
Review the functional permissions for the role and

remove any restrictions that prevent access. Grant
access to the user's role from the Security Console if it's
missing.
Review the details of the error incident raised by the

base service and take appropriate action, or contact
Verify that the server configuration file correctly
references the object that the client must access.
Update object definition in server configuration if the
object requested is valid and is missing or incorrectly
defined. If the object requested by client is invalid,
Review details of the exception and check if it's a

functional validation error that can be fixed by changing
the values that were entered in Outlook. If the
exception cause is not known contact Oracle Support
for assistance.
Review additional error messages and log details to

determine the cause of the failure and the necessary
corrective action.
Verify the XML content and import the package again.
Review the log to determine the cause of the failure

and steps to resolve it.
You must ask the user to synchronize data again.
Verify the server configuration file content on the

server, make sure that it has proper object definitions
as expected, and restart the sync service to reload the
file. Finally, ask the user to resume the sync process.
You must enable the Enable Contact Synchronization

contact profile option and the Enable Appointment
Synchronization activity synchronization profile option.
Review the add-in deployment steps and ensure that

the Microsoft-specific steps for granting privileges have
been followed. Additional information is available in My
Oracle Support.
Review My Oracle Support to determine the root cause

and the steps to resolve the issue.
Review the add-in deployment steps and ensure all
steps are completed.
Review My Oracle Support to determine the root cause
and the steps to resolve the issue.
Ensure that a groovy script with this name exists or

Review the logs to determine the nature of the error.
Run the refresh forecast process to ensure that the

forecast accurately reflects the underlying opportunity
data.
Access the logs on the Universal Content Management

application associated with your CX Sales configuration.
Search for an incident or error message that
corresponds to the time stamp of the error message.
Take the appropriate action to resolve the error, as
detailed in the Universal Content Management
application logs.

incident reports.

incident reports.

incident reports.
Delete and re-create the rule. If the problem persists,

Complete the payment service provider relationship for

the business unit.
Generate the logs at finest level and forward to Oracle

Support.
Generate the Payables Data Collection Test (AP List) for

the invoice and forward to Oracle Support. See
document ID 1387595.1 on the Support portal for more
information about how to run the Payables Data
Collection Test (AP List).

document ID 1387595. 1 on the Support portal for
more information about how to run the Payables Data






Collection Test (AP List). You should also forward the
payment process logs to Oracle Support.





Review the log files for the technical details of the

system error.
You must obtain a data fix to correct this issue.
Review the Create Bills Receivable Remittance log file

for errors during receipt processing.
Verify through the Oracle Enterprise Manager that the

Document Transfer Service is up and able to accept
requests.
Contact Oracle Support for assistance and provide the

log file of the ESS job.
Contact Oracle Support for assistance and provide the

log file of the ESS job.
Contact your support administrator to resolve this

issue.
Refer to the ESS process log files to debug the issue.
Ensure that the BI server is up and running. Verify that

the report and data model used to generate the
notification don't have any errors. Check if retrieving
the report from the BI server has timed out.
Review the journal approval flow details and error logs

from Oracle Enterprise Manager.
Retrieve the AdminServer-diagnostic log for the date of

the error. Contact Oracle Support for assistance.

Ensure the Essbase server configuration is correct and
the Essbase server is running.
Contact Oracle Support for assistance, if necessary.
Determine whether the exception can be addressed by

system configuration. If the exception caused is
unknown, contact Oracle Support for assistance.
Check for system errors and contact Oracle Support for

assistance, if necessary.
Work with the environment owner to be sure storage is

allocated properly. Be sure data source synchronization
and analysis jobs aren't running or scheduled to be run.
Confirm the root Risk Management repository directory
exists. If not, create it manually. Ensure the OS user that
starts the Risk Management search application has full
access (777) to the root Risk Management repository
directory and all of its subdirectories. Check free disk
space under the root directory. Note the free disk space
and provide the information in a service ticket. If the
raw subdirectory of the root Risk Management
repository directory already existed, delete everything
under the raw subdirectory. Check free disk space
under the root directory again. Note the free disk space
and provide the information after all the steps are
followed.
Review the Risk Management application log for
additional information about the issue.

Resolve the error that the content management server

displayed in the logs.

Investigate the cause of the error in payroll by

reviewing payroll setup for the employee for which the
error was reported. Then resubmit the transaction or
the ESS job for which the failure occurred.
Ensure that the user has a valid email and a manager.

Also, the user's manager must have a valid email.
Review the log file for details about the issue.
Review the log file for more information.
Review the log file for more information. Ensure that

the target directory is writable.
Review the log file for more information. Ensure that
the role being saved doesn't already exist in LDAP.
Ensure the LDAP credentials are correct and the LDAP
user account isn't locked.
Review the log file for the error message. Ensure there
is sufficient privilege to access the Oracle Platform
Security Service key store and credential store.
Review the log file for more information. Ensure the

contents of the import file are valid. Contact Oracle
Review the log file for more details about the error.
Review the diagnostic logs to determine the cause of

error.
Salary information couldn't be displayed correctly
because no effective date was passed to the page. Log a
service request.
Review the logs and diagnostic resources to identify the
cause of the failure. Optionally, enable logging, submit
the progress again, and review the error logs. Finally, fix
the error and process the burden cost recalculation
again.
Turn on logging and log a service request.

again.

again.
Verify that the component code is the valid lookup code
for lookup type CMP_SALARY_COMPONENTS. Also
verify that the component code is valid for the salary
basis if specific components are selected for use for the
given salary basis.
Verify the start, end dates and reason codes used to

create action occurrence ID. For salary change actions,
the valid action types are Hire an Employee, Add
Employee Work Relationship, Rehire an Employee,
Promote, Transfer, Global Transfer, Change Salary,
Salary Change, and Group Compensation.
Verify the assignment data and salary history for which

the salary data is being created. If there are no data
issues, log a service request.
again.
Verify all formula are compiled correctly and there is no

invalid data in the HR application. If formulas and data
are verified to be accurate, log a service request.
Obtain the process log and file a service request.
File a service request for assistance with this issue.
Review the log files and contact Oracle Support for

assistance.
Contact Oracle Support for assistance if you can't

resolve this issue.

Apply the modeled changes manually to the worker's

HR record using the changes outlined in the proposed
model.
The user will need to request the appropriate privileges

from their IT security team.
You need to enable the responsive profile option of the

work area that the deep link navigates to.
If the error was received during a batch load operation,

then review the log file user interface for specific errors
for a batch line that failed. Otherwise, review stack
trace in logs for more information or contact your help
desk.
Generate a new surrogate key ID instead of using the

existing one, which is already in use by an existing
record.
Review the flexfield setup from the user interface and
the stack trace in the logs for more information.
Contact your Oracle Support for further assistance if
needed.

desk.
Review the log file user interface for specific errors for
a batch line that failed.
Review the log file user interface for specific errors for
a batch line that failed.

desk.
Review the EDN queue connection or status or check

the namespace in the HCM events setup.
Review the Groovy rule syntax. Otherwise, review stack

desk.
Check the EDN message queue or contact your help

desk.
Review the EDN message queue status or HCM event

setup namespace. Contact your help desk.
Log a service request to get an access key to activate

the goal plan set functionality. After you get the access
key, use the key to activate the functionality.
Check the server connection details and try again.
If authorized, provide the person with the appropriate

upgrade key. If you don't already have the key, contact
Oracle Support. You can also set the Talent Profile User
Interface Redesign profile option value to Y.
Restart the Oracle Enterprise Scheduler or fix the error.
You need to open the Scheduled Processes page and

check if any processes were recently submitted. Check
that all servers are up and running. If they're running,
try again to reset the schedule. If the issue persists,
retrieve the ESS and SOA server logs and contact Oracle
Open the manage scheduled processes page in the

Time Management work area and check if any
processes were recently submitted. Check that all
servers are up and running. If they're running, try again
to publish the schedule. If the problem persists,
retrieve the ESS and SOA server logs and contact Oracle
Check if the error is related to the database, for

example, if the database is down. Also check to see if
it's a general application failure. If both the database
and application are up and running, you need to review
the logs and contact Oracle Support for assistance.
Review the log files for more information. Contact

Oracle Support if you need assistance.
Oracle Support if you need assistance.
Ensure that the ESS server is running properly.
Review the logs for more information. Contact Oracle


Review log files to find context for this error.
Review the parameter values in the PL/SQL or other

method being used to call the service.
Take corrective action to repair the invalid module ID

and other invalid data. Create or update a bug as
needed.
Take corrective action to repair the damaged data or

the error caused by the bug. Create or update a service
request as needed.
Take corrective action to repair the damaged data or

the error caused by the bug. Create or update a service
request as needed.
Increase the amount of memory available for an

individual process.
The database item definition requires review. Contact

Provide the generated diagnostic log to Oracle Support.
Check the status of the managed servers to ensure

they're running. If they aren't, restart the servers and
submit the enterprise scheduler process again.
Examine the diagnostic log referring to the error code

{ERR_CODE}.
Review the logs for more information. Contact Oracle

Check the Student Financials Options page to make sure
a business unit is set up.
Check your setup. Make sure you registered your
application in Student Management, and use the
correct application registration code key that's assigned
to the application you registered.
Make sure Oracle Financials is configured correctly.
Refer to ISO/SEPA Direct Debit Guide on My Oracle
Support (ID 2025869.1). Contact Oracle Support for
assistance.
Check your setup. Make sure Fee Association Group

Code is available in Student Management, and you're
using the correct code associated with the pay point. If
you can't resolve the issue, contact Oracle Support for
assistance.
Check the setup for fees. Make sure the due date
schedule is set up for the correct date range or
academic period. To trace what setup is missing or
where it's failing, as administrator, create a charge for
the student. To verify the Oracle Financials setup for
Student Management, refer to the Implementing
Student Management guide. If your setup is correct,
restart the services to make sure they're running. If you
can't resolve the issue, contact Oracle Support for
assistance.
Review the manage student financials options setup

and confirm that the values are set for customer profile
class and customer class. If these values haven't been
set, contact the appropriate business area owner to
identify and set these values.
Review the incident log files. Contact Oracle Support for

assistance.
Review the incident log files and contact Oracle Support
for assistance.
Check whether the predefined data for the process
exists in the population selection process context setup.
Examples of the predefined data include the process
parameters and selection tool. If the data doesn't exist,
contact Oracle Support.
Check whether the BI server is working by accessing a

report or analysis. If the existing report or analysis
doesn't appear or a BI error message appears, check
the incident log files. Contact Oracle Support for
assistance.
Review the manage user role mappings setup and
confirm that the higher education constituent party
usage name and an associated job role is set. If these
values haven't been set, contact the security
administrator to identify and set these values.
Check whether the predefined data for the process

exists in the population selection process context setup.
Examples of the predefined data include the process
parameters and selection tool. If the data doesn't exist,
Call the REST service again to see if you can successfully

receive the event code and payload. If the error results
from the Java API, you will need to contact Oracle
Support.
Review the event payload that was generated and

stored in the database table of event framework. The
event payload may have minor errors that can be fixed.
If the payload is in a valid JSON data format, the parsing
error will get resolved. The corrected payload can be
updated back in the same database table row, and the
subscriber recovery operation can be retried from the
events UI. If you can't resolve the issue, contact Oracle
If the error doesn't get resolved automatically after

some time, check if the Event Delivery Network
component of the SOA server has some stuck
messages, which prevents acceptance of new
messages. In addition, there may be a problem in the
SOA server preventing messages from being accepted.
The log files and database tables for the event
framework would have additional information about
the error and may be used for troubleshooting. If you
can't resolve this issue, contact Oracle Support for
assistance.
Troubleshoot or review the log file. If you can't resolve

the issue, contact Oracle Support for assistance.
If the error doesn't get resolved automatically after
some time, check if the SOA server or some of its
components are down. The message delivery to
different subscribers is done by the Event Delivery
Network component of the SOA server. If you're unable
to solve this problem, contact Oracle Support for
assistance.
Troubleshoot or review the log file. If you can't resolve

the issue, contact Oracle Support for assistance.
Check if the subscriber REST service is down at the

moment. If so, bring it back up. The URL and other
details of the subscriber REST service can be obtained
from the database tables of the event framework. Once
the service is up, the recovery operation can be retried
from the events UI. If you can't resolve this problem,
Review the event payload that was generated and

stored in the database table of the event framework.
The event payload likely has minor errors that can be
fixed. If the payload is in a valid JSON data format, the
parsing error will get resolved. The corrected payload
can be updated back in the same database table row,
and the subscriber recovery operation can be retried
from the events UI. If you're unable to resolve this
issue, contact Oracle Support for assistance.
Contact Oracle Support for assistance, if you can't

resolve the issue.
Contact Oracle Support to review the compensation

plan details and log files.
Try to populate the business intelligence tables again by
defining a new period for the same calendar using the
Setup and Maintenance, Manage Periods page or by
updating an existing interval type using the Setup and
Maintenance, Manage Intervals page. If the error
persists, contact Oracle Support for their review of the
incident logs.
Contact Oracle Support to review the compensation

plan details and log files to triage the issue.
Review this incident: Incident ID: {INCIDENT_NUM},

Server Domain: {DB_SERVER_NAME}, Server Instance:
{APPLICATION_NAME}, Additional Information:
{ADDITIONAL_INFO}. Check database and application
server logs. Restart server if necessary. If it isn't a
hardware or code failure issue, and you suspect it's an
incorrect setup issue, contact the procurement
applications administrator to investigate and correct
the setup parameters.
Review the errors in the Oracle B2B Gateway console.
Review this incident: Incident ID: {INCIDENT_SID},

{DB_INSTANCE_NAME}.
Review this incident: Incident ID: {INCIDENT_SID},

{APPLICATION_NAME}.

Check database and application server logs. Restart

server if necessary. If it isn't a hardware or code failure
issue, and you suspect it's an incorrect setup issue,
contact the procurement applications administrator to
investigate and correct the setup parameters.
Check the log for details. If issue persists contact Oracle

Support.
Review the log files for web services of the related

applications and restart the service. If the problem
persists, check for a business logic failure that's due to
an incorrect setup. Contact Oracle Support for further
assistance.
Review the log files and check if the BI publisher and

Utilities servers are up and running. If the problem
persists, contact Oracle Support.
Ensure that the SOA server is up and is reachable. If the

issue isn't with the SOA server, on the ESS jobs page
search for the ESS job with the process number. View
the log file that's attached to the job for the error
description and error details. Contact Oracle Support if
the issue isn't resolved.
Refer to the log files for error details.
Check the logs for the cause of the error. If the cause of
the error can't be determined, log a Service Request
with the Enterprise Manager.
Ensure the SOA server is up and running. If the issue
isn't with the SOA server, ensure that the SOA
composite for approval is deployed to the SOA server,
and that the user hasn't made any changes to the
participant setup. View the log files for the
Procurement server for the error description and error
details. Contact Oracle Support if the issue isn't
resolved.
Check the health of the ESS server and also verify there
are no invalid objects in the Application Database.
Check the health of the ESS server and also verify there
are no invalid objects in the Application Database.
Check the health of the ESS server and the deployment

health of the ProcurementEssApp application from the
EM console.
EM console.
EM console.
EM console.
Ensure that the supplier profile components with
invalid data are fixed. Review the diagnostic log to
determine which information is invalid.
Ensure that the server where the application is hosted
is running and has uninterrupted connectivity with the
application. Review the diagnostic log to determine any
additional reasons for the process failure. Contact
Oracle Support for any assistance.
Ensure that the supplier profile components with

invalid data are fixed.
Review the diagnostic log view the error details to

resolve the problem.
Review and correct the overriding client extension
procedure to exclude processing assets that aren't in
service.
procedure to prevent asset lines that belong to assets
in a different project from being processed.

procedure. Ensure assets exist before asset lines are
added.
procedure to prevent this from occurring.
Review the diagnostic logs to determine the cause of

the error and correct the group retirement adjustment
procedure.
procedure that's used to add asset lines to assets.
Correct the logic to prevent assets with capital holds
from being processed.
Review and correct the client extension procedure that

was created to add asset lines to assets. Update the
code to only include asset types that are as built.
Review and correct the asset allocation basis client

extension procedure.
Review the diagnostic logs and correct the create

project assets client extension procedure. Reprocess
the asset lines to generate the asset.
Review the incident log. Contact Oracle Support for

assistance.
Review the incident log. Contact Oracle Support for
assistance.
Review the incident log for further details. Correct the

problem that caused the error identified in the incident
log. Contact Oracle Support for additional assistance.
Review the incident logs to locate what error was

encountered and where the error occurred. Correct the
overriding client extension procedure to resolve the
error.
Review and correct issues identified in the incident

logs. Review the incident logs to determine the error
and then revise the allocation generation client
extension to correct the issues.
View the incident log to resolve the issue. Contact

Oracle Support for assistance, if needed.
Review the application server log for further details.

Review the application server logs for more details.
Ensure that the product is installed correctly and that
the project definition builders are correct. Contact
Review the incident log for more information. If

required, contact Oracle Support for assistance.
Review the application server log for further details.

Review the incident log for additional information.


Review the incident log for more information on how to

resolve the issue. If needed, contact Oracle Support for
assistance.
Review the incident log for details to resolve the issue.
Contact Oracle Support for assistance if needed.

Review the incident log for further details.
Review the incident logs to find the error. The error will
indicate whether the issue is data related, application
related or database related. Go to the proper source
and correct the issue. Contact Oracle Support for
assistance.
View the incident log to resolve the issue. Contact

View the affected resources by querying the ID
{SCHEDULE_ID} in the SCHEDULE_ID column in the
PJT_PRJ_ENTERPRISE_RESOURCE_B table. Assign these
resources to a valid calendar.
Review the log for more information. Correct the

Essbase user name and password in the Oracle Essbase
server configuration. If needed, contact Oracle Support.
Verify and correct the Oracle Essbase connection

details and check if all data sources are started and
working correctly. For any environment specific issues,
see the Oracle Essbase application diagnostic logs. Then
delete the Essbase Cube for the Projects application
and restart Oracle Essbase server. If needed, contact
Oracle Support.
Review the log for more information. Correct the

cluster name in the Oracle Essbase server configuration.
If needed, contact Oracle Support.
Review the log for details. Verify and correct the Oracle
Essbase connection details, and check if all data sources
are running. Ensure that Oracle Essbase Provider
Services are started and working correctly. If needed,
Review the incident log for more information. Correct

the Oracle Essbase host and port details in the Oracle
Essbase server configuration. If needed, contact Oracle
Support.

If the integration error isn't clear, the application
administrator should check the Trading Community
Architecture integration and verify data.
The agency administrator should check the Activity

Group and Application Type to verify the setup.
In the report configuration, verify and update the

parameters, data type, and report URL associated with
Oracle Public Sector Compliance and Regulation in the
application. Also verify the report ID in the transaction
type.
Set up or activate at least one setup option for

contractor license validation.
Set up or activate at least one setup option for

contractor license validation.
Verify the parameters of the http string in the log.
Add format details to the autonumbering rule for this

application.
Ensure that the request file size setting for the HTTP
header is correct. Try reducing the request file size by
changing the http header.
Verify if the server has recognized the request method,
and verify if the requested web-service API has been
implemented on the server.
Confirm that a valid autonumbering rule has been
defined for the application. Review the server log files
and take action based on the detailed error message in
the log.
Review the log files and check for a business logic

failure that's due to an incorrect or missing setup.
Check for valid terms of use definition in the record
type setup or permit setup.

failure that's due to an incorrect or missing setup.
Confirm that the autonumbering rule for this

application is set up correctly. Review the server log
files and take action based on the detailed error
message in the log.
Check to see if the request header was hacked using

third-party tools.
Evaluate the potential processing issues to determine
the best course for fixing the problem.
Verify and update the parameters

REPORT_PARAM_NAME or REPORT_PARAM_DATATYPE
for the report in the application. Verify and set up the
correct report URL associated with Oracle Public Sector
Community Development in the application.

failure resulting from an incorrect setup or closed
accounting calendar period.
failure resulting from an incorrect setup.
In the application log, review the error function

{FUNCNAME}, error code {SQLCODE}, and error
message {ERRMSG}.
Review error message {ERRMSG} in the application log.
Confirm that the server for Oracle Integration Cloud is

running and that the REST services are working.
Review the log for server or database error messages.
Verify the network is running and that the REST service
is returning data.
Check to see if you can enlarge the browser http

request body size or request that the developers split
the request into multiple requests, and ask for server
feedback.
Verify the log for server or database error messages.

Ensure that the checkout ID is valid, checkout status is
valid, checkout data is complete, and that the checkout
is requested for a valid party.

Verify that the BIP reports are configured, the BIP
server is running, and setup is complete.
Verify the setup of autonumbering rules for the Cashier
Session number type on the Autonumber Details page.
Add the necessary attributes to the user's

ORA_CODE_ENFORCEMENT_TECHNICIAN job function.
The user should have at least 1 ORA_PSC_CE_ISSUE
_TYPE (issue type) or ORA_PSC_CE_ISSUE _SUBTYPE
(issue subtype) attribute.
Review the manage agency staff page to determine

whether any users have the planner role and the
planning application type.
Review the conditions required for sending the

notification. The three conditions for final inspection
communication notification to be sent are: inspection
status is completed, inspection type is identified as the
final inspection, and inspection result is passed.
Review the log files for more details. Contact Oracle

Support about any remaining issues.

Review the log file to see if a runtime exception exists.

Contact Oracle Support about any remaining issues.
Review the log files. Contact Oracle Support if

additional assistance is needed.
Review the log files. Contact Oracle Support if

additional assistance is needed.
You must verify that the fee calculation service is

operating correctly. The fee calculation service error is
{ERROR_MSG}.
Edit the change type definition using the Manage
Change Order Types task and add the user's role in the
Creators tab.
If the attribute value is still valid for your business, you
can reactivate the lookup value. If it's not valid, the new
object must be created again without copying an
existing object.
Ensure the generation schema is set up correctly and

that the correct content is generated. Review the
application server logs for more details.
Verify that the configuration of the active connector is

valid and revert to the last valid configuration if
needed.
Verify that the active connector matches the Oracle

Fusion Innovation Management application that Oracle
Fusion Innovation Management is being integrated to.
needed.

needed.

needed.

needed.

Also verify that the configuration of the active
connector is valid and revert to the last valid
configuration if needed.

Fusion PLM application that Oracle Fusion PLM is being
integrated to. Verify that the configuration of the active


Reconfigure the mappings correctly so that they match

up with what the application expects for the concept
structure attribute values.
Verify the status of the BI Publisher Server, investigate
the reason for the BI Publisher Server issue, and then
rectify the problem.
The user must be added as an authorized user to be

able to access the report template in the BI Publisher
Server. Also Verify the status of the BI Publisher Server.
Verify the status of the BI Publisher Server and rectify

the problem.
Verify the status of the BI Publisher Server and rectify

the problem.
The administrator must verify if the BI Publisher is

configured correctly for the requirement templates.
In the application log, review the error function

{FUNCNAME}, error code {SQLCODE}, and error
message: {ERRMSG}.
Generate detailed logs. Contact Oracle Support for
assistance.
The details of the exception have been logged for

review.
Contact Oracle Support with the incident details and
logs.
Contact Oracle Support with the incident details and
logs.
Contact Oracle support with the incident details and
logs.
Contact Oracle Support for assistance in moving the
records out of quarantine.
Review the log file to resolve the problem. Contact

Review the incident log. Contact your internal
operations, if necessary.
Make sure the lookup code that the messaging service

sends is valid.
Make sure that the setup for the topology manager that
starts the messaging driver is correct. Make sure the
arguments that the application uses to send the e-mail
message are correct, such as e-mail ID (identification),
authentication policy, security policy, and so on.
Attempt to make these fixes in the following
technologies: Oracle Unified Communications Suite,
Oracle User Messaging Service, or Oracle Application
Toolkit.
Make sure the BIP server is running and that the

configuration is correct. Examine the configuration files,
authentication setup, and security policy. Make sure
the arguments are correct, such as report path, report
format, and so on.
Review the incident log to determine the error cause.
Define valid approval rules and ensure that at least one
participant is enabled and the task owner is specified as
FUSION_APPS_SCM_ADF_APPID in the BPM Worklist.

Ensure that a valid template is available for the Oracle
BI report and the connection to the Oracle Business
Intelligence server is valid. Contact Oracle Support for
assistance.

Intelligence server is valid. For attachment errors, check
if the connection to the FND server is valid. Contact

Ensure that the ESS service is running. Contact Oracle
Intelligence server is valid. For attachment errors, check
if the connection to the BPM server is valid. Contact
Update the privileges or authorization for this user to

carry out this operation.
Ensure the number generation schema is setup

correctly and that the correct numbers are generated.
The SOA process details need to be reviewed to

determine the issue that caused the exception.
Ensure the description generation schema is setup
correctly and that the correct description is generated.
Review the information entered for the item class

record.
Contact Oracle Support for assistance, if needed.
Check the server logs to identify the reason for failure.
Investigate the data used for the invocation, and check

the deployment architecture.

Examine the log files and the incident log. If you can't
resolve the problem, contact Oracle Support for
assistance.
Submit the event for reprocessing. Review the
diagnostic logs if the error persists.
Submit the corresponding event for reprocessing.
Review the diagnostic logs if the error persists.
Submit the event for reprocessing. Review the
diagnostic logs if the error persists.

Ensure that the sales order line of the delivery detail
has a valid price. Contact Oracle Support for assistance.
Verify that the Event Delivery Network and the

associated data sources have been configured and
functioning properly. Contact Oracle Support for
assistance.
Verify that the Event Delivery Network and the
associated data sources have been configured and
functioning properly. Contact Oracle Support for
assistance.
Ensure that the Item Cost service is available.
Ensure that the profile option is available, or contact

Try again after some time. Contact Oracle Support for

assistance if the application error does not get resolved.
Review the diagnostics and incident logs for more

information.

Have the user try the action again. If this error happens
again, contact Oracle Support for assistance.
Review the log to confirm if the exception was caused

by the payload used in the service. If the exception
cause is unknown, contact Oracle Support for
assistance.
Check for errors related to the following exception that

was returned after process step {PROCESS_STEP} while
calling {PACKAGE_PROCEDURE}:
{CREATE_TREE_EXCEPTION}.

Have the user try the action again. If this error happens
again, contact Oracle Support for assistance.
There wasn't any impact on the results of the plan run,

but the occurrence of this message should be reported.
Ensure that the Oracle Enterprise Scheduler Service is

running and review the engine logs. Contact Oracle
Check the log for details. After the application is back to
being operational, if the plan still shows a busy status,
then suggest that the user issue a Close action before
resubmitting the original plan action request.
Review the database log for errors and ensure sufficient

disk space is available. Contact Oracle Support for
assistance.
Review plan definitions including history data range and
demand calendar. Review the forecasting engine profile
definitions including measure selections. Contact Oracle
Check the log for details. The log from the plan action
provides more details.
Check the log for details. The log from the plan action
provides more details.
Collect application log files for further analysis and
check the files for details. Add the missing dimensions,
specified in the error message or in the application log
files, to the dimension catalog, and then run the plan.
Check the log for details. After the application is back to

being operational, if the plan still shows a busy status,
then suggest that the user issue a Close action before
resubmitting the original plan action request.
Check the diagnostic log file for error details.
Check the diagnostic log file for error details.
Collect service log files for further analysis. Review the

service log for errors and a possible memory dump
(.hprof file) when the OutOfMemoryError occurred.
Ensure sufficient Java heap size is available. Contact
Ensure that the Enterprise Service Scheduler is running.

Ensure that the FScmService and FScmEss applications
were deployed correctly. Contact Oracle Support for
assistance.
Collect process log files for further analysis. Review the

process log for errors. Ensure the demand plan isn't
processing another plan action or isn't in an error state
during the Sales and Operations Plan run. Also ensure
the demand plan measure is a member of the measure
catalog used by the demand plan. Contact Oracle
Collect service log files for further analysis. Review the
service log for errors. Contact Oracle Support for
assistance.
Collect engine log files for further analysis. Review the

engine log for errors. Contact Oracle Support for
assistance.

assistance.

assistance.

assistance.
assistance.
Contact Oracle support to evaluate your environment

to determine updates for the java stack size settings.
Review the engine logs for the error messages. Contact

Verify that the Oracle Enterprise Scheduler Service is
running. Review the Oracle Enterprise Scheduler
Service logs. Contact Oracle Support for assistance.
Access the log from the Enterprise Manager for more

information including a stack trace that indicates the
root cause of the exception.
Review the Oracle Fusion Global Order Promising

diagnostic logs to get more details on failure.
Review the Oracle Enterprise Scheduler Service

application diagnostic file for more messages. Contact
Repeat launching the Collect Planning Data process
with the correct parameters. Refer to the user guide or
If the plan is not created after the user tries again, there
may be more a persistent problem. Contact Oracle
support for assistance.
Check if the Oracle Instance Environment variable is set

properly. Check if Oracle Fusion Global Order Promising
is installed properly.
Check if Oracle Fusion Global Order Promising engine is
running.
Review Oracle Enterprise Scheduler Service job logs to

know more about the failure reasons.
Review the process logs for error messages. Contact

Review the forecasting profile and ensure that the

parameters are set correctly.

Review the measures used in the decomposition groups
and ensure that they all have the time dimension. If this
does not resolve the issue, then contact Oracle Support
for assistance.
Review the measures used in the decomposition groups

and ensure that they all have the time dimension. If this
does not resolve the issue, then contact Oracle Support
for assistance.
Review the forecasting methods associated with the

forecast profile. Contact Oracle Support for assistance.

Correct the calendar definitions or select a different
calendar.
Examine the logs for the cause of the error. If you

cannot determine the cause of the error, then contact
Oracle Support.
Review the log file for the error message.
Provide the request ID from the supplier for the supply

data upload request. Using the Collaboration Supply
Data Uploads REST resource and the request ID
provided by the supplier, retrieve the load process ID
for the Load Planning Data from Flat Files scheduled
process job. Locate the job in Oracle Enterprise
Scheduler and view the log to determine the root cause
of the error.
Review the diagnostic log to understand the issue root

cause. Resolution might entail creating the missing
setup, shortening the length of the work order prefix,
or changing the prefix so the sequence is updated to a
lower value.
Review the incident log for more details about the

system error.
Ensure that the packing slip document sequence

category {CAT_CODE} for the inventory organization
{ORG_CODE} with the application Shipping, the module
Ship Confirm, and the table WSH_NEW_DELIVERIES is
defined through the Manage Document Sequence
Category user interface under the Setup and
Maintenance menu, or contact Oracle Support for
assistance.
Ensure that the document sequence {DOC_SEQ_NAME}

is defined for the inventory organization {ORG_CODE}
with the application Shipping, the module Ship Confirm,
the type Gapless, and the determinant type Legal Entity
through the Manage Document Sequence user
interface under the Setup and Maintenance menu, or
Ensure that the document sequence category

{CAT_CODE} is assigned to document sequence
{DOC_SEQ_NAME} for the inventory organization
{ORG_CODE} with the method as automatic and the
determinant type as legal entity value linked to the
inventory organization through the Manage Document
Sequence user interface under the Setup and
Maintenance menu, or contact Oracle Support for
assistance.
Ensure that either a valid document sequence category

is defined in the Shipping Parameters setup or contact
Ensure that the Oracle Enterprise Scheduler Service

server is available.
Ensure that a valid document sequence category is
defined in the Shipping Parameters user interface, or
Analyze the logs to determine the cause of the failure

to communicate with the FOS.
Ensure that a valid document sequence category is

defined in the Shipping Parameters user interface, or
Have the user try performing the task again. If this error
happens again, contact Oracle Support for assistance.
Have the user wait and try performing the task again. If
the error occurs again, contact Oracle Support for
assistance.
Fix the errors with the service and try this operation
again.
You can download the log files from

FunctionalSetupServer under CommonDomain to get
more details on the error.
Resolve the issues described above and attempt this
operation again.
Confirm that Keystore is set up correctly on both the
consumer and producer sides.
Review the details in the FunctionalSetupServer logs

and report the issue to the appropriate product.
Verify the enterprise application parameter for the

selected task is correct.
Make sure the asynchronous exportDataAsync method

is defined in the business object service.
Enable Message Transmission Optimization Mechanism

policy in your service.
You must download and check the log files from

more details on the error. Fix the errors before
attempting this operation again.
Make sure the asynchronous exportDataAsync method

is defined in the business object service.
You must download and check the log files from

more details on the error. Fix the errors before
attempting this operation again.
Check that the application that supports the service is

running and the service is available.
Make sure the service information is registered

correctly for this business object.
Review and correct the errors returned by the service
{SERVICE_NAME}.
Validate the search task associated to the business
object {BUSINESS_OBJECT} is correct and make sure it
returns values for each business object attribute that
identify the scope selection.
Ensure the service {SERVICE_NAME} associated to the

task {TASK_NAME} always returns a Process ID or a task
status.
Check that the application {APPLICATION_NAME} is
registered properly and that the server where the
application is hosted is running.
Check the log files from the server where this operation
was initiated. Examine the reason for this error and fix
it before attempting this operation again.
Make sure that Functional Setup Enterprise Storage

Server application is running and configured correctly.
Make sure that the exportCriteria and exportControl

method parameters are defined in the business object
service.
Review and correct the errors in the web component

producer logs. If applicable, report the errors against
product {PRODUCT}.
Check with the service provider that service meets the

requirements returning a completion status and
relevant messages.
Make sure that the importData and importControl
method parameters are defined in the business object
service.
Review and resolve the errors before attempting this
operation again.

Fusion Diagnostic Message

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fusion Diagnostic Message

Uploaded by

Copyright:

Available Formats

Message NamType Family Product LBA Short Name

ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList

ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList

ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList

ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList

ATK_NOTIFY_ Error (FND) ATF ATK AtkWatchList

ATK_INVALID Error (FND) ATF ATK AtkHelpPortal

ATK_UAP_WRError (FND) ATF ATK AtkHelpPortal

ATK_WATCHLIError (FND) ATF ATK AtkWatchList

ATK_INVALID Error (FND) ATF ATK AtkHelpPortal

ATK_ADDRES Error (FND) ATF ATK AtkContextAddress

ATK_HOSTED Error (FND) ATF ATK AtkHelpPortal

FND_CMN_ESError (FND) Common FND FndAppCommon

FND_CMN_NEError (FND) Common FND FndAppCommon

FND_CMN_RCError (FND) Common FND FndAppCommon

FND_CMN_PRError (FND) Common FND FndAppCommon

FND_CMN_FLError (FND) Common FND FndAppCommon

FND_CMN_USError (FND) Common FND FndAppCommon

FND_CMN_PRError (FND) Common FND FndAppCommon

FND_CMN_PRError (FND) Common FND FndAppCommon

FND_CMN_SEError (FND) Common FND FndAppCommon

FND_CMN_SOError (FND) Common FND FndAppCommon

FND_CMN_PRError (FND) Common FND FndAppCommon

FND_CMN_FLError (FND) Common FND FndAppCommon

FTA_HIRING_ Error (FND) Common FTA FtaServer

CSO_KM_APPError (FND) CRM CSO CsoKmUi

CSO_KM_APPError (FND) CRM CSO CsoKmUi

CSO_ATTACH Error (FND) CRM CSO CsoKmUi

CSO_NO_SEA Error (FND) CRM CSO CsoKmUi

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_CATEGORError (FND) CRM CSO CsoKmUi

CSO_APPL_NOError (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_CONCEP Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_LError (FND) CRM CSO CsoAdmin

CSO_CONCEP Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_LError (FND) CRM CSO CsoAdmin

CSO_DICT_M Error (FND) CRM CSO CsoAdmin

CSO_SEARCH Error (FND) CRM CSO CsoAdmin

CSO_ADMN_CError (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_ADMIN_ Error (FND) CRM CSO CsoAdmin

CSO_LOCALE Error (FND) CRM CSO CsoAdmin

CSO_ROLES_RError (FND) CRM CSO CsoAdmin

CSO_AVAIL_L Error (FND) CRM CSO CsoAdmin

CSO_SERVICE Error (FND) CRM CSO CsoAdmin

CSO_USER_GRError (FND) CRM CSO CsoAdmin

CSO_NO_REPOError (FND) CRM CSO CsoAdmin

CSO_PRODUCTError (FND) CRM CSO CsoAdmin

CSO_USERS_RError (FND) CRM CSO CsoAdmin

CSO_ACTIVE_ Error (FND) CRM CSO CsoAdmin

CSO_INTERNAError (FND) CRM CSO CsoAdmin

CSO_CATEGORError (FND) CRM CSO CsoAdmin

CSO_SERVICE Error (FND) CRM CSO CsoAdmin

FOD_ERROR_ Error (FND) CRM FOD SimplifiedSetup

FOD_SA_FRCSError (FND) CRM FOD SimplifiedSetup

HZ_RES_PARTError (FND) CRM HZ FoundationResources

HZ_GEO_GNRError (FND) CRM HZ FoundationGeographie