14 Process Codes
This topic describes the information on the manual stages along with the functional activity codes.
Cash Management
The following table represents the manual stages in Cash Management workflow along with the functional activity codes which can be used for mapping in role activity screen under Security Management System menu.
Table 14-1 Functional Activity Code - Cash Management
| Stage | Functional Activity Code | Description |
|---|---|---|
| Processing | CMS_FA_MANUAL_ENRICHMENT | This is the processing stage of instrument collection where the maker can submit/reject an entry of instrument. If the entry is rejected, the record will be deleted and if submitted, then the transaction will be sent to the Authorization stage. |
| Authorization | CMS_FA_AUTHORISATION | This is the authorization stage of instrument collection / instrument management, where the checker can approve/reject an entry of instrument. |
| Rework | CMS_FA_CMSWK_REWORK | If the checker rejects an entry, it goes to the rework stage where the maker can do the required modifications to the entry and submit it again. |
| Posting Accounting Entries Exception | CMS_FA_POSTING_ACC_EXCEPTION |
This is the accounting-posting workflow stage exception, where posting to FCUBS fails due to errors. These errors need to be resolved. |
| Accounting Generation Exception | CMS_FA_ACC_GEN_EXCEPTION |
This is the accounting-generation workflow stage exception, where accounting generation fails due to accounting setup errors. These accounting setup errors need to be resolved. |
Note:
Refer the Role section on Oracle Banking Security Management System User Guide to understand procedure for creating roles and assigning activity to it.Finance
The following table represents the manual stages in Finance workflow along with the functional activity codes which can be used for mapping in role activity screen under Security Management System menu.
Table 14-2 Functional Activity Code - Finance
| Stage | Functional Activity Code | Description |
|---|---|---|
| LimitProcessingException | LimitProcessingException | This is a stage before authorization and transaction falls in this stage when maintenance of limits is not done properly. |
| CreditApprovalException | CreditApprovalException | This is a stage before authorization and transaction falls in this stage when exception handling behavior has been maintained as STOP in the Product Parameters screen for limit amount and limit expiry breach. |
| CreateAdhocLimitsTransactionException | CreateAdhocLimitsTransactionException | This is a stage before authorization and transaction falls in this stage if there is a technical error while identifying Adhoc limits applicability in transaction. |
| InitiateWorkflowForAdhocLimitTxnException | InitiateWorkflowForAdhocLimitTxnException | This is a stage before authorization and transaction falls in this stage if there is a technical error due to which a transaction for Adhoc limits is not initiated in the system. |
| AutoFinanceException | AUTOFIN_EXCEPTION | This is a stage before authorization and after limit is blocked. Transaction falls in this stage when auto processing is enabled, and it fails due to financing validations being done as per finance parameters maintained in Product/Program/Interest/Accounting/Charges. |
| Processing | PROCESSING | This is a stage before authorization and after limit is blocked. Transaction falls in this stage when auto-processing is disabled in Program/Product parameters. |
| Authorization | AUTHORIZATION | This is authorization step wherein user can either Approve/Reject the record. Transaction falls in this stage when auto-authorization is disabled in Product/Program parameters. |
| Loan Integration Exception | OBCL_EXCEPTION | This stage is after authorization and transaction falls in this stage when integration with lending product (OBCL) to create contracts or make payment fails. |
| AccountingEntriesPostException | ACC_ENTRIES_EXCEPTION | This stage is after authorization and transaction falls in this stage when accounting entries posting integration is configured as ‘Yes’ in system parameters with another product and posting fails. |
| AccountPostingResponseAwaited |
ACCPOSTING_RESPONSE_AWAITED (Not be mapped on screen) |
This stage is after authorization and transaction falls in this stage if accounting entries posting integration is configured as ‘Yes’ in system parameters with another product and the mode of integration is asynchronous and transaction is waiting for response. |
| ExternalPaymentException | EXTERNAL_PAYMENT_EXCEPTION | This stage is after authorization and transaction falls in this stage when external payment integration is required as per payment mode in transaction and external payment system integration fails. |
| OutgoingPaymentResponseAwaited |
OUTPAY_RESPONSE_AWAITED (Not be mapped on screen) |
This stage is after authorization and transaction falls in this stage when external payment integration is required as per payment mode in transaction and integration is asynchronous and transaction is waiting for response. |
| LimitsUpdateException | LIMITS_UPDATE_EXCEPTION | This stage is after authorization and transaction falls in this stage when limits utilization/release fails due to technical error. The user can retry the transaction after the technical error is resolved. |
| FinanceMasterUpdate | POSTAUTH_UPDATE_EXCEPTION | This stage is after authorization and transaction falls in this stage when work table to main table approval update fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
| InstrumentUpdateException | INSTRUMENT_UPDATE_EXCEPTION | This stage is after authorization and transaction falls in this stage when update of linked invoice/PO as financed/paid fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
| AlertsException | ALERTS_EXCEPTION | This stage is after authorization and transaction falls in this stage when alerts generation for transaction fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
| ReconCompletionException | RECON_COMPLETION_EXCEPTION | This stage is after authorization and transaction falls in this stage for settlement transactions when payment is initiated through Finance Payment Recon (FPR) and FIFO (First In First Out) is not completed and status of the same cannot be found due to technical errors. The user can retry the transaction after the technical error is resolved. |
| ReconAuthorizationException | RECON_AUTHORIZATION_EXCEPTION | This stage is after authorization and transaction falls in this stage for settlement transactions when payment is initiated through Finance Payment Recon (FPR) and FIFO (First In First Out) is not completed and status of recon of current finance settlement is not updated due to technical errors. The user can retry the transaction after the technical error is resolved. |
| ReconStepAuthorizationException | RECON_STEP_AUTHORIZATION_EXCEPTION | This stage is after authorization and transaction falls in this stage for settlement transactions when payment is initiated through Finance Payment Recon (FPR) and FIFO (First In First Out) is not completed and status of payment corresponding to current finance settlement is not updated due to technical errors. The user can retry the transaction after the technical error is resolved. |
Note:
Refer the Role section on Oracle Banking Security Management System User Guide to understand procedure for creating roles and assigning activity to it.Recon
The following table represents the manual stages in Recon workflow along with the functional activity codes which can be used for mapping in role activity screen under Security Management System menu.
Table 14-3 Functional Activity Code - Recon
| Stage | Functional Activity Code | Description |
|---|---|---|
| Processing | SCFCM_FA_PROCESSING_AUTH_REJECT | This is a stage before authorization in which transaction is under processing before rejection. |
| CL Exception | SCFCM_FA_CL_EXCEPTION | This stage is after authorization and transaction falls in this stage when integration for corporate lending is configured as ‘Yes’ in system parameters with another product and it fails. |
| Accounting Regeneration Exception | SCFCM_FA_AC_REGEN_EXCEPTION | This stage is after authorization and transaction falls in this stage when integration for accounting entries re-generation is configured as ‘Yes’ in system parameters with another product and regenerating the same fails. |
| Authorization | SCFCM_FA_PROCESSING_AUTH | This is authorization step wherein user can either Approve/Reject the record. Transaction falls in this stage when auto-authorization is disabled in Product/Program parameters. |
| Accounting Post Exception | SCFCM_FA_ACC_POST_EX | This stage is after authorization and transaction falls in this stage when accounting entries posting integration is configured as ‘Yes’ in system parameters with another product and posting fails. |
| Limits Update Exception | SCFCM_FA_LIMITS_UPD_EX | This stage is after authorization and transaction falls in this stage when limits utilization/release fails due to technical error. The user can retry the transaction after the technical error is resolved. |
| VAM Integration Exception | SCFCM_VAM_INTG_AUTH | This stage is after authorization and transaction falls in this stage when integration with virtual account management system fails. |
| Master Update Retry | SCFCM_FA_MASTER_UPDATE_ERROR | This stage is after authorization and transaction falls in this stage when work table to main table approval update fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
Note:
Refer the Role section on Oracle Banking Security Management System User Guide to understand procedure for creating roles and assigning activity to it.Discounting
The following table represents the manual stages in Discounting workflow along with the functional activity codes which can be used for mapping in role activity screen under Security Management System menu.
Table 14-4 Functional Activity Code - Discounting
| Stage | Functional Activity Code | Description |
|---|---|---|
| Authorization | AUTHORIZATION | This is authorization step wherein user can either Approve/Reject the record. Transaction falls in this stage when auto-authorization is disabled in Product/Program parameters. |
| masterUpdateException | MASTER_UPDATE_EXCEPTION | This stage is after authorization and transaction falls in this stage when work table to main table update fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
Note:
Refer the Role section on Oracle Banking Security Management System User Guide to understand procedure for creating roles and assigning activity to it.Instrument
The following table represents the manual stages in Instrument workflow along with the functional activity codes which can be used for mapping in role activity screen under Security Management System menu.
Table 14-5 Functional Activity Code - Instrument
| Stage | Functional Activity Code | Description |
|---|---|---|
| MlTagCorrection | SCFCM_FA_TXN_CREATE_EXCEPTION | The transaction falls in this stage when transaction is not automatically created through file upload due to missing of tags. |
| Create Instrument Exception | SCFCM_FA_TXN_CREATE_EXCEPTION | This is a stage before authorization and transaction falls in this stage if there is a technical error while creating a transaction for instrument. |
| Processing | SCFCM_FA_TXN_PROC | This is a stage before authorization and transaction falls in this stage when auto-processing is disabled in Program/Product parameters. |
| Transaction Rejection Approval | SCFCM_FA_TXN_REJECTION | This is a stage after authorization and transaction falls in this stage when it is rejected. |
| CL Exception | SCFCM_FA_CL_EXCEPTION | This stage is after authorization and transaction falls in this stage when integration for corporate lending is configured as ‘Yes’ in system parameters with another product and it fails. |
| Accounting Regeneration Exception | SCFCM_FA_AC_REGEN_EXCEPTION | This stage is after authorization and transaction falls in this stage when integration for accounting entries re-generation is configured as ‘Yes’ in system parameters with another product and regenerating the same fails. |
| Authorization | SCFCM_FA_TXN_AUTH | This is authorization step wherein user can either Approve/Reject the record. Transaction falls in this stage when auto-authorization is disabled in Product/Program parameters. |
| Accounting Post Exception | SCFCM_FA_ACC_POST_EX | This stage is after authorization and transaction falls in this stage when accounting entries posting integration is configured as ‘Yes’ in system parameters with another product and posting fails. |
| Limits Update Exception | SCFCM_FA_LIMITS_UPD_EX | This stage is after authorization and transaction falls in this stage when limits utilization/release fails due to technical error. The user can retry the transaction after the technical error is resolved. |
| Instrument Master Update Exception | SCFCM_FA_MASTER_UPD_EXCEPTION | This stage is after authorization and transaction falls in this stage when update of linked instrument in the master table fails due to technical errors. The user can retry the transaction after the technical error is resolved. |
| File Upload Exception | SCFCM_FA_FILE_UPLOAD_EX | This is a stage before authorization and transaction falls in this stage when upload of file fails. |
| Portal Response Exception | SCFCM_FA_PORTAL_RES_EX | This is a stage where in portal does not respond due to the technical error. The user can retry the transaction after the technical error is resolved. |
Note:
Refer the Role section on Oracle Banking Security Management System User Guide to understand procedure for creating roles and assigning activity to it.