Vertex O series and Oracle R12 integration

There are very few documentation which provide insight to integrate Oracle P2P and Vertex. I would try to cover some basics here but if you need any indepth consulting knowledge, please email me.

Vertex allows the customers to customize the Oracle / Vertex integration process by adding logic in the client extension packages. The client extension package for the Procure to Pay process is VTX_P2P_UTL_CUSTOM_ATTR_AP_PKG

 

Vertex Oracle Integration Connector (OIC) supports sending additional data to Vertex through the following data elements in the OIC array data structure

•  25 character fields LINE_CHAR1~25)
•  10 numeric fields (LINE_NUMERIC1 ~ 10)
•  5 date fields (LINE_DATE1 ~5)

OIC reserves some fields for internal use, and we can only control the data source for such reserved fields

•  LINE_CHAR3 for source system name
•  LINE_CHAR16 for vendor class
•  LINE_CHAR17 for purchasing class
•  LINE_CHAR18 for usage class
•  LINE_CHAR19 for store location code
•  LINE_CHAR20 for cost center
•  LINE_CHAR21 for department code
•  LINE_CHAR22 for GL account
•  LINE_CHAR23 for material code
•  LINE_CHAR24 for project number
•  LINE_CHAR25 for vendor SKU
•  LINE_NUMERIC6 for charged tax

Some of the basic vertex table to debug the P2P transactions are as follows:
LINEITEM and lineitemtaxovrflw
TRANSSYNCIDCODE in LINEITEM table has the invoice details in it.