You are on page 1of 5

In this Document Goal Solution References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

APPLIES TO:
Oracle Cash Management - Version 12.0.0 to 12.1.3 [Release 12 to 12.1] Information in this document applies to any platform.

GOAL
Q1: UNABLE TO CREATE PAYMENT DOCUMENTS FOR A BANK ACCOUNT as it errors as: Exception: JBO-25058: Definition Country of type Attribute not found in CEInternalBankAccountsVO1 Q2: When you Try to Create Chek Book Information it errors as: Error Row 1 Error - Checkbook Start Number and End Number must be between First Available Document Number and Last Available Document Number. Row 2 Error - Checkbook Start Number and End Number must be between First Available Document Number and Last Available Document Number. Q3: Payables allows check numbers not included in check books? Q9: Latest Patches:

SOLUTION
A1: Q1: UNABLE TO CREATE PAYMENT DOCUMENTS FOR A BANK ACCOUNT as it errors as: Exception: JBO-25058: Definition Country of type Attribute not found in CEInternalBankAccountsVO1

Bug: 14370593: R.RPC-AUG12:UNABLE TO CREATE PAYMENT DOCUMENTS FOR A BANK ACCOUNT Apply following Patch: Patch: 13621810:R12.CE.B This patch fixes the issue wherein the bank information in Payment Document Setup pages is not displayed properly Oracle Applications Release 12.1.x CEInternalBankAccountsVO.xml 120.5 Old Behavior ------------The Bank Details are not displayed in the Manage Payment Documents page for accounts which belong to bank branches which do not have address details. Subsequently on trying to create/update a payment document, the following error is thrown: Creating Payment Document Throwing error "Attribute InternalBankAccountId in PaymentDocumentAM.PaymentDocumentsVO1 is required"

New Behavior ------------The Manage Payment Documents page now works properly. This patch supersedes and incorporates the fixes for patches 13332110:R12.CE.B and 12931958:R12.CE.B

A2. checkbooks functionality in Oracle applications: This is just to track the physical check book data. There is no functionality associated with the same and a documentation Bug: 6662743 has been logged for this. This is only to capture information. Please insure that the Chck Book Start and End Numbers are with in the Range of the First Available Document Number to Last Available Document Number. If it is beyon the range it will error. A3: Payables allows check numbers not included in check books? Apply: 1). Patch: 13621810:R12.CE.B This patch fixes the issue wherein the bank information in Payment Document Setup pages is not displayed properly Oracle Applications Release 12.1.x ce java/bankaccount/server CEInternalBankAccountsVO.xml 120.1.12010000.5 ce java/bankaccount/server CEInternalBankAccountsVORowImpl.java 120.1.12010000.3 Old Behavior: The Bank Details are not displayed in the Manage Payment Documents page for accounts which belong to bank branches which do not have address details. Subsequently on trying to create/update a payment document, the following error is thrown:Creating Payment Document Throwing error "Attribute InternalBankAccountIdPaymentDocumentAM.PaymentDocumentsVO1 is required"

New Behavior: The Manage Payment Documents page now works properly. This patch supersedes and incorporates the fixes for patches 13332110:R12.CE.B and 12931958:R12.CE.B 2). Patch: 14000178:R12.CE.B This patch makes sure value entered in Payment Document Category LOV is validated against attached list of values in Payment Document Create or Update page Old Behaviour: In Bank Account Payment Document create or update page, value in Payment Document Category is not validated against the values present in attached list of values when Apply button is clicked. New Behaviour: Payment Document Category is getting validated against the values present in attached list of values when Apply button is clicked in Bank Account Payment Document create or update page. Patch can be applied over 12.1.x ce mds/bankaccount/webui PaymentDocumentPG.xml 120.15.12010000.6 Q4: What is the use for checkbook when creating a check payment document? There is not documentation on the cash or payments user guide about the checkbooks. The documentation for the payment documents is already available in the user guide. However, need to elaborate it to specify the following: 1. The creation of multiple cheque books for a bank account 2. Using them in payments. Ref: Bug: 6662743 - DOCUMENTATION BUG: DOCUMENTATION ABOUT CHECKBOOK NEEDED

A9: Insure following Latest: 1). Patch: 8924979:R12.CE.B This patch fixes the issues with payment document number range overlap and last issued document number field. Bug Description: It is not possible to use the same Number range more than once for a bank account. Also, it is never possible to use the First Document Number. The payments workbench shows skips the first document. Bug Resolution: It is possible to use the same Number range more than once for a bank account. The First payment Document Number can be used from the payments workbench. Patch can be applied over 12.1.1. ce java/bankaccount/server PaymentDocumentAMImpl.java 120.7.12010000.5 ce java/bankaccount/server PaymentDocumentsVORowImpl.java 120.6.12010000.3 ce java/bankaccount/webui PaymentDocumentsCO.java 120.4.12010000.5 ce java/schema/server CEPaymentDocumentsEOImpl.java 120.3.12010000.4 ce patch/115/import/US ce12amg.ldt 120.42.12010000.19

2). Patch: 14000178:R12.CE.B This patch makes sure value entered in Payment Document Category LOV is validated against attached list of values in Payment Document Create or Update page Old Behaviour: In Bank Account Payment Document create or update page, value in Payment Document Category is not validated against the values present in attached list of values when Apply button is clicked. New Behaviour Payment Document Category is getting validated against the values present in attached list of values when Apply button is clicked in Bank Account Payment Document create or update page. Patch can be applied over 12.1.x ce mds/bankaccount/webui PaymentDocumentPG.xml 120.15.12010000.6 (2). Since there is no documentation on how or even if, the checkbook fields are to be used, I would recommend that you do not use them. You can use the document First/Last Available numbers to limit the numbers that a document can use. When the Last has been reached, you can change the range to reflect the second 'checkbook' number range. Bug: 6662743 DOCUMENTATION BUG: DOCUMENTATION ABOUT CHECKBOOK NEEDED PROBLEM STATEMENT: What is the use for checkbook when creating a check payment document? There is not documentation on the cash or payments user guide about the checkbooks STEPS TO REPRODUCE THE PROBLEM: This documentation bug is being tracked in the R12.2 (GA) Cash Management Documentation Tracking Sheet (DTS). It will be addressed in the R12.2 (GA) Cash Management Documentation Update.

Screen shots:

REFERENCES
NOTE:557542.1 - What Is The Usage Of Check Book Field In Payment Documents? BUG:6662743 - DOCUMENTATION BUG: DOCUMENTATION ABOUT CHECKBOOK NEEDED BUG:8924979 - MANAGE PAYMENT DOCUMENTS AND LAST ISSUED NUMBER BUG:14000178 - MANUALLY ENTER

BUG:6662743 - DOCUMENTATION BUG: DOCUMENTATION ABOUT CHECKBOOK NEEDED