Skip to main content

P2P Table Descriptions






P2P Tables With Details


1.PO_REQUISITION_HEADERS_ALL

2.PO_REQUISITION_LINES_ALL
When you raise the Requisition these tables effected 

3.PO_REQUISITION_HEADER_ID is the join between the tables



4.PO_REQ_DISTRIBUTIONS_ALL
It distribute the Requisition Account information.



5.PO_HEADERS_ALL  (PO_HEADER_ID)



6.PO_LINES_ALL
When PO Created PO stores in tables(PO_HEADER_ID) is the join for tables



7.PO_DISTRIBUTIONS_ALL
It will distribute the PO# Account information



8.PO_ACTION_HISTORY
Here you can get Approvals notification Status



9.PO_VENDORS  (VENDOR_ID)



10.PO_VENDOR_SITES_ALL  (VENDOR_SITE_ID)



11.PO_VENDOR_CONTACTS  (VENDOR_CONTACT_ID)
Contacts Vendor ,Vendor site and contact information Vendor_id,Vendor_contact_id, (VENDOR_SITE_ID)


12. RCV_SHIPMENT_HEADERS   (SHIPMENT_HEADER_ID)
Common information about the source of your receipts or expected receipts


13. RCV_SHIPMENT_LINES
When you issue the receipt The recipient number , Shipment location stores in the table.


14. RCV_TRANSACTIONS  (TRANSACTION_ID)


15. MTL_MATERIAL_TRANSACTIONS  (TRANSACTION_ID)
Stores material transaction information (Transaction_id)



16.PO_RELEASES_ALL
To see the which purchase order is released.



17.PO_AGENTS
Contains information about buyers and purchasing managers.



18.PO_NOTIFICATION_CONTROLS
Contains information about the notification control rules for blanket, planned, and contract purchase orders.



19.PO_APPROVAL_LIST_HEADERS
List of approves for the purchasing document used for requisition approvals only



20.PO_APPROVAL_LIST_LINES
Approval list lines for the requisition approval list.



21.PO_POSITION_CONTROLS_ALL
Assignment of control groups to jobs and/or positions


22.PO_DOCUMENT_TYPES_ALL_B

Default, control, and option information you provide to customize



23.PO_CONTROL_GROUPS_ALL

Control groups you use in your business



24.PO_RFQ_VENDORS

Information about the set of suppliers assigned to a request for quotation (RFQ)



25.PO_VENDOR_LIST_HEADERS  (VENDOR_LIST_HEADER_ID)

Stores information about supplier quotation lists you create.



26.FINANCIALS_SYSTEM_PARAMS_ALL

This Tables stores common and default information between AP and PO.


Comments

Popular posts from this blog

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12 GL Module (General Ledger Module tables in Oracle Apps R12) Interface Table Base Table gl_interface gl_budget_interface gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations AR Module (Account Receivable Module  tables  in Oracle Apps R12) Interface Table Base Table ra_customers_interface_all   ra_contact_phones_int_all ra_customer_profiles_int_all hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ar_periods ar_perio

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set property for your responsibility

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set the property for your responsibility. Solution-:      (1)  Go to System administrator > Profile > System       (2) Now Search “ HR: User Type ” Profile option at Responsibility level with Respective Responsibility. And Click On FIND Button. Now Select HR: User Type Value “HR with Payroll User” (you can choose another option as well accordingly). And SAVE. Now check your responsibility, error removed. Go ahead with your next step and enjoy Oracle Apps. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12? The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next: Code       Meaning M             Male F              Female U             Unknown Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns: FIRST_NAME LAST_NAME DATE_OF_BIRTH GENDER The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the database columns reference the lookup via a lookup code. If in the future your organization wants the users to s