Results 1 to 6 of 6

Thread: P0030A Bank Account Number-Customer (CBNK) size

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    New Member
    Join Date
    Mar 2015
    Location
    Turkiye/ Istanbul
    Posts
    3

    P0030A Bank Account Number-Customer (CBNK) size

    hi all,

    I've a problem in P0030A. CBNK (bank account number - customer) field size is 20.
    So I can't enter a bank account number more than length 20, there is no IBAN info.
    I don't also want to change CBNK size .


    E1. 9.1
    What do you recomend to solve that issue?
    Your thoughts would be greatly appreciated.
    Thanks.

  2. #2
    Member
    Join Date
    Jan 2010
    Location
    Karnataka
    Posts
    188
    Create a custom Tag Table that will maintain the extra chars. Customise your application logic to include this table.

  3. #3
    Senior Member Chan Rana's Avatar
    Join Date
    Aug 2005
    Location
    PA,USA
    Posts
    1,016
    You say there is no IBAN info so you can use that field which i think is greater then CBNK. Never heard of account# going bugger then 20. Are you sure that you haven't merged both routing and acoount #?.

    Chan
    Chandrakant Rana
    E1 Xe-9.0, AS/400, XML, BSSV
    E1 Integration,C,HTML,Java,CreateForm 3.0

  4. #4
    New Member
    Join Date
    Mar 2015
    Location
    Turkiye/ Istanbul
    Posts
    3
    Hi Chan,


    We are using IBAN info for domestic banks account and some foreign banks. Some bank accounts have no IBAN info so we need CBNK. Also you're right I have never see that CBNK is bigger than 20 length before. But there is a China's bank that bank account info greater than 20 (actually:22). We're using that CBNK info many reports and forms. I think I will create a new additaional table to store that number and change all reports and forms. I wonder is there any other method for solution?

  5. #5
    Senior Member peterbruce's Avatar
    Join Date
    Jan 2004
    Location
    NSW Australia
    Posts
    2,134
    ersinokur,

    We have come across a single instance of a bank account being greater than 20 characters. That is with one of our off-shore campuses. They do not use the transit number (TNST) (our main campus does), so we put the overflow characters in that field. The only things I had to do were:

    1) Modify a custom validation for TNST to exclude the off-shore campus users
    2) Modify the custom EFT file creation for the off-shore campus
    Thanks, Peter

    "Give a person a fish, feed them for a day, teach them how to fish, feed them for a lifetime."

    E9.1 TR9.1.2.1, Enterprise Server: Sun, Database Server: Sun, Oracle DB: 11g, Weblogic.
    Create!form 7

  6. #6
    New Member
    Join Date
    Mar 2015
    Location
    Turkiye/ Istanbul
    Posts
    3
    Quote Originally Posted by Abhishek Chhajer View Post
    Create a custom Tag Table that will maintain the extra chars. Customise your application logic to include this table.
    Thank you for your answer. I think I will create a new additaional table to store that number and change all reports and forms

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.