Free Oracle Magazine Profit:The Executive's Guide to Oracle Applications

Enter your e-mail address to receive notifications when there are new posts

Profit Magazine: The Executive's Guide to Oracle Applications

Know the Changes because of R12 Oracle Payment Module (Fund Disbursement) in EBS

Posted on November 26th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

payment

As we know , fund disbursement functionality has been moved from Oracle payables to new Payment module, which provides these functionality like;

  • Creation & validation of payments
  • Aggregation of payments into files
  • Format & transmission of files

where as selection & approval of invoices remains in Payables itself.

It is very important to understand some of important changes impact while upgrading 11i to r12 to some of the custom reports if they are based out of R11i10 version schema model.

 

greUnderstand some of the changes because of Funds Disbursement(Oracle Payment)

Some of the important changes can be summarized as:12tablechangespayment

Will take some more discussion on Oracle Payments some other day.:)

Posted in Oracle Payment Module, Release12 | Email This Post Email This Post | Print This Post Print This Post

7 Responses
  1. Navneeth Says:

    I understand that Customer Bank Accounts are stored in IBY_EXT_BANK_ACCOUNTS but how do I link the customer stored in AR_CUSTOMERS and the Customer Bank stored in IBY_EXT_BANK_ACCOUNTS.

    For example, I defined Customer X with Bank Y. I can see the Customer X information in AR_CUSTOMERS and that customer’s Bank Y Information in IBY_EXT_BANK_ACCOUNTS. What is the linking point between X and Y between these 2 tables?

    Appreciate your help.

  2. Sanjit Anand Says:

    In Release 12, Customer Bank Information is no longer stored in AP_BANK_ACCOUNTS and
    AP_BANK_ACCT_USES_ALL tables as they are obsolete.

    This information is stored in the following iPayment (IBY) tables:

    1) IBY_EXT_BANK_ACCOUNTS defines the external bank account entity. This table should not be
    translated for any columns.
    2) IBY_ACCOUNT_OWNERS stores the joint account owners of a bank account.
    3) IBY_EXTERNAL_PAYERS_ALL stores payment attributes of the customer.
    4) IBY_PMT_INSTR_USES_ALL Payment instruments assignments

    hope you get the answer

  3. Navneeth Says:

    Hi
    I am new to this site. So I had trouble finding the reply for my post. Coming to the point of my query, I am a core functional guy, so I don’t understand the exact meaning of ‘This table should not be translated for any columns’.

    In fact I searched Metalink and found the exact statement. so can you please explain me what it means.

    From one of your another blog, i understood that I can use the following query:
    SELECT * FROM iby_ext_bank_accounts, hz_code_assignments WHERE hz_code_assignments.owner_table_id = iby_ext_bank_accounts.branch_id
    to get the Customer bank but it is duplicating the data. It is showing 2 records for each bank. Can you pls tell me why it is so.

  4. Jonathan Aitken Says:

    Is anyone else having problems getting payments to work. We are testing R12.0.4 and we cannot get the Payments module to complete a check run.
    We are implementing R12 from scratch (not an upgrade) and we have not been able to successfully process any transactions from Oracle Payments.
    AP invoices seem to work. Paying them via Payments does not.
    We have logged lots of bugs and are currently on R12.0.4 in our test system.
    We had some success on 12.0.3 with quick checks but we have never been successful with a full check run.
    Since upgrading to 12.0.4 we have had nothing but more problems.

  5. Jonathan Aitken Says:

    It turned out to be a bug.
    We applied several patches 6673696 6827266, 6849046 and 6940908.
    6940908 turned out to fix our issue.

  6. shashi Says:

    What is the reason for fund disbursement functionality or payment batch which is moved from Oracle payables to new Payment module. what is the importance of the Payment module.

    Regards,
    Shashi.

  7. Antje Schneider Says:

    hi payment gurus!

    have the same issue like Jonathan. 6940908 doesnt solve our problem.

    we cannot format the remittance
    sytem doesnt create format report. in the exception column we have always “INVALID_AUTHORIZATION”

    Payer Granted Authorization to Debit Bank Account Flag is set!

    any help would be great!

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.