Skip to main content

Ar Queries

AR_QUERIES

SELECT HP.PARTY_NAME CUSTOMER_NAME
  FROM HZ_PARTIES HP,
       RA_CUSTOMER_TRX_ALL RCTA,
       HZ_CUST_ACCOUNTS_ALL HCAA
 WHERE HP.PARTY_ID = HCAA.PARTY_ID
   AND HCAA.CUST_ACCOUNT_ID = RCTA.BILL_TO_CUSTOMER_ID
   AND RCTA.TRX_NUMBER = '500875'
   AND RCTA.ORG_ID = 204
 
   =======================================
 
   SELECT ACRA.RECEIPT_NUMBER
     FROM RA_CUSTOMER_TRX_ALL RCTA,
          AR_CASH_RECEIPTS_ALL ACRA,
          AR_RECEIVABLE_APPLICATIONS_ALL ARAA
    WHERE RCTA.CUSTOMER_TRX_ID = ARAA.APPLIED_CUSTOMER_TRX_ID
      AND ACRA.CASH_RECEIPT_ID = ARAA.CASH_RECEIPT_ID
      AND RCTA.TRX_NUMBER = '500875'
      AND RCTA.ORG_ID = 204
    
      ===============================
    
      SELECT RCTTA.NAME
        FROM RA_CUST_TRX_TYPES_ALL RCTTA,
             RA_CUSTOMER_TRX_ALL RCTA
       WHERE RCTTA.CUST_TRX_TYPE_ID = RCTA.CUST_TRX_TYPE_ID
         AND RCTA.TRX_NUMBER = '500875'
         AND RCTA.ORG_ID = RCTTA.ORG_ID
         AND RCTA.ORG_ID = 204
       
         =============================================
       
         SELECT HP.PARTY_NAME,
                HCAA.ACCOUNT_NUMBER,
                HL.ADDRESS1,
                HL.ADDRESS2,
                HL.ADDRESS3,
                HL.ADDRESS4,
                HL.CITY,
                HL.STATE,
                HL.COUNTRY
           FROM HZ_LOCATIONS HL,
                HZ_PARTIES HP,
                HZ_PARTY_SITES HPS,
                HZ_CUST_ACCOUNTS_ALL HCAA,
                HZ_CUST_ACCT_SITES_ALL HCASA,
                HZ_CUST_SITE_USES_ALL HCSUA,
                RA_CUSTOMER_TRX_ALL RCTA
          WHERE HP.PARTY_ID = HPS.PARTY_ID
            AND HPS.LOCATION_ID = HL.LOCATION_ID
            AND HP.PARTY_ID = HCAA.PARTY_ID
            AND HCAA.CUST_ACCOUNT_ID = HCASA.CUST_ACCOUNT_ID
            AND HCASA.CUST_ACCT_SITE_ID = HCSUA.CUST_ACCT_SITE_ID
            AND HCSUA.SITE_USE_ID = RCTA.SHIP_TO_SITE_USE_ID
            AND HCASA.PARTY_SITE_ID = HPS.PARTY_SITE_ID
            AND HCAA.CUST_ACCOUNT_ID = RCTA.BILL_TO_CUSTOMER_ID
            AND HCSUA.SITE_USE_CODE = 'SHIP_TO'
            AND RCTA.TRX_NUMBER = '500875'
          
       
         =============================================
       
         SELECT HP.PARTY_NAME,
                HCAA.ACCOUNT_NUMBER,
                HL.ADDRESS1,
                HL.ADDRESS2,
                HL.ADDRESS3,
                HL.ADDRESS4,
                HL.CITY,
                HL.STATE,
                HL.COUNTRY
           FROM HZ_LOCATIONS HL,
                HZ_PARTIES HP,
                HZ_PARTY_SITES HPS,
                HZ_CUST_ACCOUNTS_ALL HCAA,
                HZ_CUST_ACCT_SITES_ALL HCASA,
                HZ_CUST_SITE_USES_ALL HCSUA,
                RA_CUSTOMER_TRX_ALL RCTA
          WHERE HP.PARTY_ID = HPS.PARTY_ID
            AND HPS.LOCATION_ID = HL.LOCATION_ID
            AND HP.PARTY_ID = HCAA.PARTY_ID
            AND HCAA.CUST_ACCOUNT_ID = HCASA.CUST_ACCOUNT_ID
            AND HCASA.CUST_ACCT_SITE_ID = HCSUA.CUST_ACCT_SITE_ID
            AND HCSUA.SITE_USE_ID = RCTA.BILL_TO_SITE_USE_ID
            AND HCASA.PARTY_SITE_ID = HPS.PARTY_SITE_ID
            AND HCAA.CUST_ACCOUNT_ID = RCTA.BILL_TO_CUSTOMER_ID
            AND RCTA.ORG_ID = 204
            AND HCSUA.SITE_USE_CODE = 'BILL_TO'
            AND RCTA.TRX_NUMBER = '500875'     

Comments

Popular posts from this blog

FND_PROFILE API In Oracle Apps

 FND_PROFILE API In Oracle Apps --------------------------------------------------------------------------------------------------- FND_PROFILE API is used very frequently in oracle apps development. The major purpose of this API is to: ·                      Retrieve user profile values for the current run-time environment ·                      Set user profile values for the current run-time environment FND_PROFILE API has different procedures and functions which are most frequently used. Following are the brief explanation of them: 1. FND_PROFILE.PUT:  This can be used to put a value to the specified user profile option. Example:  FND_Profile.Put(‘PROFILE_NAME’, ‘New_Value’) FND_Profile.Put(’USERNAME’, Usr_Name) FND_Profile.Pu...

PO Matching Setting in Purchase Order Shipment Line(2-way,3-way,4-way)

[PO] Matching Setting in Purchase Order Shipment Line Invoice matching can be set in five different areas of Oracle Purchasing: In the list below, a setting at any level will override the settings above it. 1. Oracle Purchasing Options a. Navigate to: Setup > Organizations > Purchasing Options b. Select Default Alternative Region 2. Supplier Information a. Navigate to: Supply Base > Suppliers b. Query on specific supplier c. Click on Open d. Select Receiving Alternative Region 3. Line Types a. Navigate to: Setup > Purchasing > Line Types b. In the Receipt Required field: Yes = 3-way, No = 2-way 4. Items a. Navigate to: Items > Master Items b. Query on specific item c. Select Purchasing Alternative Region d. In the Invoice Matching section: Yes = 3-way, No = 2-way 5. Purchase Order Shipments a. Navigate to: Purchase Orders > Purchase Orders b. Enter (header and) line information c. Click on Shipments button d. Select More Alternative Region Ramification of Invoice ...

To make the program to complete with warning. Through sql

 To make the program to complete with warning. Through sql -------------------------------------------------------------------------------------------------------------------------------------- l_submit_status:=FND_CONCURRENT.SET_COMPLETION_STATUS('WARNING',NULL); --------------------------------------------------------------------------------------------------------------------------------------