What are some practical mapping strategies that can be used to map EBS tables with Fusion PVOs? Please advise if anyone has worked on this activity before.
H @Usha Athimakula
Are there specific tables you are looking for. Just asked the question on chat GPT and it came up with this
EBS Table
Fusion Table
Fusion PVO (BICC/Extract)
MTL_SYSTEM_ITEMS_B
EGP_SYSTEM_ITEMS_B
ItemExtractPVO
MTL_ITEM_CATEGORIES
EGP_ITEM_CATEGORIES_B
ItemCategoryExtractPVO
MTL_PARAMETERS
INV_ORG_PARAMETERS
InventoryOrganizationExtractPVO
MTL_MATERIAL_TRANSACTIONS
INV_MATERIAL_TXNS
InventoryTransactionExtractPVO
MTL_TRANSACTION_LOT_NUMBERS
INV_TRANSACTION_LOT_NUMBERS
InventoryLotTransactionExtractPVO
MTL_ONHAND_QUANTITIES
INV_ONHAND_QUANTITIES_DETAIL
OnHandQuantityExtractPVO
PO_HEADERS_ALL
PurchasingDocumentHeaderExtractPVO
PO_LINES_ALL
PurchasingDocumentLineExtractPVO
PO_DISTRIBUTIONS_ALL
PurchasingDistributionExtractPVO
RCV_TRANSACTIONS
ReceivingTransactionExtractPVO
AP_INVOICES_ALL
PayablesInvoiceExtractPVO
AP_INVOICE_DISTRIBUTIONS_ALL
PayablesInvoiceDistributionExtractPVO
AP_CHECKS_ALL
PaymentExtractPVO
GL_LEDGERS
LedgerExtractPVO
GL_CODE_COMBINATIONS
CodeCombinationExtractPVO
GL_JE_HEADERS
JournalHeaderExtractPVO
GL_JE_LINES
JournalLineExtractPVO
HZ_PARTIES
PartyExtractPVO
HZ_CUST_ACCOUNTS
CustomerAccountExtractPVO
RA_CUSTOMER_TRX_ALL
ReceivablesTransactionExtractPVO
OE_ORDER_HEADERS_ALL
DOO_HEADERS_ALL
SalesOrderHeaderExtractPVO
OE_ORDER_LINES_ALL
DOO_LINES_ALL
SalesOrderLineExtractPVO
WIP_ENTITIES
WIE_WORK_ORDERS_B
WorkOrderExtractPVO
GME_BATCH_HEADER
ProcessManufacturingBatchExtractPVO
@Daniel Ryan Thank you for taking the time and answering! We are upgrading to Fusion from EBS and would require this for all modules - OM, AP, AR, GL, SCM etc.
@Usha Athimakula , Mapping Oracle EBS tables to Fusion Public View Objects (PVOs) is one of the trickiest parts of coexistence and FDI/BICC-based integrations because there is no 1:1 universal mapping layer. In practice, successful implementations rely on various people's research and experience rather than trying to find “perfect equivalence.” Oracle also does not publish anything because EBS being on-prem offering would have so much customization that there is no certain way for Oracle to come up with one universal doc.
Fusion PVOs are pre-joined, abstraction-layer views, not table equivalents. Many EBS tables collapse into a single PVO or vice versa. I would suggest looking at the object level e.g. AP_INVOICES_ALL in EBS is same as fusion business object: Payables Invoice which is PayablesInvoiceExtractPVO.
Hope it helps!