My Oracle Support Banner

EAP: FSCM 9.2 Maintenance From #35 To #39 Package Is Not Including Related Records In Alters (Doc ID 2795129.1)

Last updated on FEBRUARY 21, 2023

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

After upgrading from PUM Image 35 to 39, some records, including the following, were not altered to reflect changes made to the length of some fields.

 

1) APPLIED_PCT field. 

Associated records:

UPG_PREPAID_AET
VCH_PPAY_XREF_C
VCH_PPAY_XREF_E"

2) EOPCBUFFER_LEVEL field.


Associated records:

EOPCAPPSRCTMP
EOPCAPP_SRC_REC
EOPC_OBJECT"

 

3) CURR_STATUS field.


Associated records:

IN_REQ_LINE_AVW
KP_REQLN_MFG_VW
KP_REQLN_WS_VW
KP_REQ_LINE_GV
KP_REQ_LNESP_GV
POREQLN_TEO1
POREQLN_TEO2
POREQLN_TEO3
PO_LN_SRCH_RSLT
PV_EF_DATAE_LN
PV_MOB_LNE_SHIP
PV_REQLINCAT_VW
PV_REQLIN_AW_VW
PV_REQMGRLN_WRK
PV_REQ_LINES_VW
PV_REQ_LINE_VW
PV_REQ_LINE_VW0
PV_REQ_LINE_VW2
PV_REQ_LNSHP_VW
PV_REQ_LN_FLVW
PV_REQ_LN_WS
PV_REQ_LN_WS2
PV_REQ_MBL_L_VW
PV_REQ_SHIP_VW
PV_REQ_TMPLNVW2
PV_REQ_TMPL_VW
PV_REQ_TMPL_VW2
PV_REQ_VNTM_VW2
PV_REQ_VTMP_VW
PV_REQ_VTMP_VW2
REQLNSHIP_TEO1
REQLNSHIP_TEO2
REQLNSHIP_TEO3
REQ_LINE
REQ_LINE1_T
REQ_LINE2_T
REQ_LINE_S
REQ_LINE_SHIP
REQ_LINE_SHIP_S
REQ_LINE_SHP_VW
REQ_LINE_VW
REQ_LN_SHP1_T
REQ_LN_SHP2_T
REQ_LN_SRCH_VW
REQ_RC_LINE
REQ_RC_LINE_T
REQ_RC_SHIP
REQ_RC_SHIP_T
REQ_RC_WB_SCR_L
REQ_RC_WB_SCR_S
REQ_SE_LINE_VW
SPF_REQ_LINE_VW

4) NUM2 Field.


Associated records:

EOTP_PARTNRADDR
ESTAB_TBL
EX_ADVNCE_PMT_S
EX_SHEET_PMT_S
INTFC_CRCARD_C
INTFC_CRCARD_E
INTFC_CRCARD_S
AGENCY_LOC_CD_S
AUDIT_BNK_BCHTB
AUDIT_BNK_CDTBL
AUDIT_EOTP_ADDR
AUDIT_LOC_TBL
AUDIT_STL_INSTR
AUDIT_TR_WR_TMP
AUDIT_VNDR_ADDR
AUDIT_VNRBNKACT
BANK_CD_TBL_S
BI_HDR_CC_TEO1
BI_HDR_CC_TEO2
BI_HDR_CC_TEO3
CC_TRANLN_TEO1
CC_TRANLN_TEO2
CC_TRANLN_TEO3
COMPANYTBL_UPG
CRCARD_AR_HST_C
CRCARD_AR_HST_E
CRCARD_AR_HST_S
IN_DEMAND_ADR_C
IN_DEMAND_ADR_E
IN_DEMAND_ADR_S
KP_ACTGEN_T
KP_ACTGEN_TAO
KP_AP_CHCK_ADDR
KP_AP_TRP_T3O
KP_AUC_ADDR_HDR
KP_EB_ACT_STG
KP_EB_PRJ_STG
KP_INDMDAD_HIST
KP_INTFCPHB_AUD
KP_PROJGEN_T
KP_VCHR_VDR_STG
KP_VNDR_BNK_ACT
KP_VNDR_BNK_AUD
KP_VND_ADDR_AUD
MSR_HDR_INV_S
PAYMENT_TBL_C
PAYMENT_TBL_E
PAYMENT_TBL_S
PYCYCL_RST_S
SAC_MP_CONTACTS
STLEFTTRAN_TEO1
STLEFTTRAN_TEO2
STLEFTTRAN_TEO3
TRWRTEMPLT_TEO1
TRWRTEMPLT_TEO2
TRWRTEMPLT_TEO3
TR_WR_DETAIL_C
TR_WR_DETAIL_E
TR_WR_DETAIL_S
UPG_APF01_AET
UPG_APF05_AET
VCHR_BANK_QV_S
VCHR_BANK_STG_S
VCHR_LINE_TXG_C
VCHR_LINE_TXG_E
VCHR_LINE_TXG_S
VCHR_VNDR_QV_S
VCHR_VNDR_STG_S
VCH_VNDR_BANK_C
VCH_VNDR_BANK_E
VCH_VNDR_BANK_S
VCH_VNDR_INFO_C
VCH_VNDR_INFO_E
VCH_VNDR_INFO_S

5) NUM2_OTHER field.
There is one impacted record for this and that is upgrade record.



STEPS
 
1. The issue is happening during the upgrade from PUM Image 35 to 39.

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.