Enterprise Service Automation (ESA) - PSFT (MOSC)

MOSC Banner

AP_FG_PROC is failing after PUM 26 applied

edited Apr 26, 2018 5:07AM in Enterprise Service Automation (ESA) - PSFT (MOSC) 5 commentsAnswered

Hi,


We are in the process applying PI 24 to 26 in our FSCM environment. During testing found that AP_FG_PROC is failing with below error. While this is exact error was coming when we were with PI 23 and Oracle delivered a fix in 26083616 part of PUM 26. Now after applying complete PUM 26 the same error started occurring. Not sure what's broken now. Appreciate some assistance if anyone aware of this new issue with PI 26 and if any new fix available

5:06:28AM

File: /vob/peopletools/src/pspcm/pcmobuf.cppSQL error. Stmt #: 6799  Error Position: 0  Return: 1400 - ORA-01400: cannot insert NULL into ("SYSADM"."PS_PMT_DETAIL_STG"."PYMNT_DT") Failed SQL stmt: INSERT INTO PS_PMT_DETAIL_STG (PMT_MSG_ID,PMT_SEQ_NUM,PMT_SOURCE,BUSINESS_UNIT,SRC_ REF_ID,AMOUNT,AMOUNT_CURRENCY_CD,PMT_STATUS,PMT_TYPE,BANK_SETID,BANK_CD,BANK_ACCT_KEY,FROM_BNK_ID_NB R,FROM_BNK_ACCT_NUM,FROM_DFI_ID_NUM,FROM_DFI_ID_QUAL,PYMNT_METHOD,FORMAT_ID,PRENOTE_FLAG,PAY_IMMEDIA TELY,COUNTRY,BANK_ID_QUAL,BNK_ID_NBR,BRANCH_ID,BANK_ACCT_TYPE,BANK_ACCOUNT_NUM,CHECK_DIGIT,DFI_ID_QU AL,DFI_ID_NUM,BANK_NAME,BANK_NAME_AC,BRANCH_DESCR,BRANCH_NAME_AC,IBAN_CHECK_DIGIT,IBAN_ID,PARTY_ID_T YPE,PARTY_SETID,PARTY_ID,NAME1,NAME1_AC,NAME2,STD_ID_NUM,STD_ID_NUM_QUAL,EFT_PYMNT_FMT_CD,EFT_RTNG_F LG,EFT_RTNG_STATUS,EFT_TRANS_HANDLING,EFT_DOM_COSTS_CD,EFT_CORR_COSTS_CD,EFT_CROSSED_CHECK,EFT_CHECK

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center