P2P Tables R12.........................

-

REQUISITIONS: SELECT * FROM PO_REQUISITION_HEADERS_ALL WHERE TYPE_LOOKUP_CODE='PURCHASE' AND TRUNC (CREATION_DATE) =TRUNC (SYSDATE)
SELECT * FROM PO_REQUISITION_LINES_ALL WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM PO_REQ_DISTRIBUTIONS_ALL WHERE TRUNC(CREATION_DATE)=TRUNC(SYSDATE)

RFQ :
SELECT * FROM PO_HEADERS_ALL WHERE TYPE_LOOKUP_CODE='RFQ' AND QUOTE_TYPE_LOOKUP_CODE='BID' AND TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM PO_LINES_ALL WHERE PO_HEADER_ID=110306
SELECT * FROM PO_LINE_LOCATIONS_ALL WHERE PO_HEADER_ID=110306

QUOTATION :SELECT * FROM PO_HEADERS_ALL WHERE TYPE_LOOKUP_CODE='QUOTATION' AND QUOTE_TYPE_LOOKUP_CODE='BID' AND TRUNC(CREATION_DATE)=TRUNC(SYSDATE)
SELECT * FROM PO_LINES_ALL WHERE PO_HEADER_ID=110307
SELECT * FROM PO_LINE_LOCATIONS_ALL WHERE PO_HEADER_ID=110307

PURCHASE ORDER :
SELECT * FROM PO_HEADERS_ALL WHERE TYPE_LOOKUP_CODE='STANDARD' AND SEGMENT1='6025'
SELECT * FROM PO_LINES_ALL WHERE PO_HEADER_ID=110308
SELECT * FROM PO_LINE_LOCATIONS_ALL WHERE PO_HEADER_ID=110308
SELECT * FROM PO_DISTRIBUTIONS_ALL WHERE PO_HEADER_ID=110308

INVOICES :SELECT * FROM AP_INVOICES_ALL WHERE INVOICE_NUM='1234'
SELECT * FROM AP_INVOICE_LINES_ALL WHERE INVOICE_ID=211300
SELECT * FROM AP_INVOICE_DISTRIBUTIONS_ALL WHERE PO_DISTRIBUTION_ID IN(270850,270851) (OR)
SELECT * FROM AP_INVOICE_DISTRIBUTIONS_ALL WHERE INVOICE_ID=211300

PAYMENT :
SELECT * FROM AP_INVOICE_PAYMENTS_ALL WHERE INVOICE_ID=211300
SELECT * FROM AP_PAYMENT_SCHEDULES_ALL WHERE INVOICE_ID=211300
SELECT * FROM AP_CHECKS_ALL WHERE CHECK_NUMBER=6396
SELECT * FROM AP_CHECK_FORMATS
SELECT * FROM AP_PAYMENT_HISTORY_ALL WHERE CHECK_ID=77530
SELECT * FROM AP_BANK_ACCOUNTS_ALL
SELECT * FROM AP_BANK_BRANCHES
SELECT * FROM AP_TERMS_TL WHERE TERM_ID='10002'
SELECT * FROM AP_TERMS_LINES WHERE TERM_ID='10002'
SELECT * FROM AP_HOLDS_ALL

Comments

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                         Nav: System administrator à Profile à system             Step3: Assign  PO  Responsibility to User                         Nav: System administrator à security à user à define Note:  PO  is including some of i.e. Options, Supplier, Item, Expenses, and Purchasing . Options : Options nothing but a Controlling future at the operating unit level.                         Th
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  difference is
Read more