Getting 1400: Could Not Save To Database. MODE=UPGRADE EFFDATE=<null> while applying patch 20575403?
(Doc ID 2088821.1)
Last updated on MAY 01, 2023
Applies to:
Oracle iSupplier Portal - Version 12.1.2 and laterInformation in this document applies to any platform.
Goal
Getting error while applying <Patch 20575403>:R12.POS.B:
1602: Could not save.
1400: Could not save to database. MODE=UPGRADE EFFDATE=
1404: Please first load this entity or check protect and custom level of PROCESS_ACTIVITY 'WFSTD/FED_BUILD_PA_AP_INVO_ACCT_GEN'.
saved.
ACTIVITY 'FNDFFWK/FND_FLEX_GET_VALUE_FROM_COMB' is protected, no changes were saved.
ACTIVITY 'FNDFFWK/FND_FLEX_GET_VALUE_FROM_COMB2' is protected, no changes were saved.
ACTIVITY 'FNDFFWK/FND_FLEX_IS_COMB_COMPLETE' is protected, no changes were saved.
ACTIVITY 'FNDFFWK/FND_FLEX_START_GENERATION' is protected, no changes were saved.
ACTIVITY 'FNDFFWK/FND_FLEX_VALIDATE_COMBINATION' is protected, no changes were saved.
PROCESS_ACTIVITY 'WFSTD/FED_BUILD_PA_AP_INVO_ACCT_GEN' is protected, no changes were saved.
Solution
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
Goal |
Solution |
References |