R12: Understanding What the Oracle EBS "Payments" (IBY) module Is, and What It Does (Doc ID 1391460.1)

The Payments module (IBY) is a payment engine designed to work with multiple Oracle E-Business Suite products in order to facilitate the receipt of, issuance of, and management of, customer receipts and batched supplier payments. 

NOTE:  The term "supplier payments" includes payments to several types of "creditors", including external suppliers, expense payments to employees, refunds to customers, and (in the Payments Workbench) refunds received from creditors. 

NOTE:  As with earlier versions of Oracle Payables, single payments ("unbatched" payments to a single creditor) are still made through the Payments Workbench form in the Oracle Payables module.

Learn more about what the Payments (IBY) module is, what it does, and what products it works with within My Oracle Support document:

Understanding What the Oracle EBS "Payments" (IBY) module Is, and What It Does (Doc ID 1391460.1)
Comments:

Is IBY an acronym? What does it mean, how did it come about to be used. It has got to mean or work from some developer understanding of the three initials - IBY. Thanks!

Bill Wheeler
DELPHI Systems Developer
Federal Aviation Administration
Oklahoma City, OK

Posted by BillW on May 22, 2013 at 03:34 PM EDT #

Hi Bill,
IBY isn't an acronym. In EBS all the different modules are given a 'short code' which is used internally to identify each module e.g. Payments database object names start with 'IBY_'. Some of these short codes are acronyms e.g. AR = Accounts Receivable, but others are just fairly random such as IBY.

Thanks for your comment!
Lucia.

Posted by LuciaC on June 26, 2013 at 08:34 PM EDT #

How do you join the ivy table to oe_order_headers?

Any help would be greatly appreciated...

Thx!!
Lisa

Posted by guest on August 08, 2013 at 09:51 PM EDT #

Hi Lisa,
Here's information taken from Doc ID 1313304.1 (written for 12.1.3):

The link between OM and IBY can be found several ways.

(1) TRXN_EXTENSION_ID - if extension_id is populated in iby_trxn_summaries_all.INITIATOR_EXTENSION_ID, it links to oe_payments.TRXN_EXTENSION_ID.

oe_payments has header_id column

(2) The view iby_trxn_ext_auths_v which has columns TRXN_EXTENSION_ID and PAYMENT_SYSTEM_ORDER_NUMBER.

(3) The view iby_trxn_extensions_v which has columns TRXN_EXTENSION_ID and ORDER_ID.

(4) select ORDER_ID, ORIGIN_APPLICATION_ID from IBY_FNDCPT_TX_EXTENSIONS where TRXN_EXTENSION_ID in
(select TRXN_EXTENSION_ID from IBY_FNDCPT_TX_OPERATIONS where TRANSACTIONID in
(select TRANSACTIONID from IBY_TRXN_SUMMARIES_ALL where TANGIBLEID = '<enter your tangibleid>'));

The ORDER_ID returned is the order header id.

Posted by LuciaC on August 11, 2013 at 08:26 PM EDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« July 2014
SunMonTueWedThuFriSat
  
2
4
5
6
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today