The blog provides the Oracle AR SQL Query for retrieving Uncleared Receipt Amount Total in Oracle apps R12
SQL Query to get Uncleared Receipt Amount Total
SELECT NVL(SUM(AR_Pay_Sch_tbl.AMOUNT_DUE_REMAINING), 0) unClearedReceiptTotalAmt
FROM HZ_CUST_Agcc_tblOUNTS_ALL HZ_CUST_Agcc_tblT_ALL_TBL,
AR_PAYMENT_SCHEDULES_ALL AR_Pay_Sch_tbl,
AR_RECEIVABLE_APPLICATIONS_ALL AR_Rec_Appl_tbl,
HZ_HZ_CUST_Agcc_tblT_ALL_TBL_SITES_ALL HZ_CUST_AGgcc_tbl_TBLT_SITES,
HZ_HZ_PARTY_SITES_TBLS HZ_PARTY_SITES_TBL,
HZ_Hz_loc_tblATIONS Hz_loc_tbl,
HZ_CUST_HZ_CUST_SITE_USES_TBL_ALL HZ_CUST_SITE_USES_TBL,
AR_CASH_RECEIPT_HISTORY_ALL AR_CASH_RECPT_HIST_TBL,
AR_CASH_RECEIPTS_ALL AR_CASH_RCPT_ALL_TBL,
GL_CODE_COMBINATIONS gcc_tbl
WHERE 1=1
AND AR_Pay_Sch_tbl.CUSTOMER_ID = HZ_CUST_Agcc_tblT_ALL_TBL.CUST_Agcc_tblOUNT_ID
AND AR_Pay_Sch_tbl.CUSTOMER_ID = HZ_CUST_Agcc_tblT_ALL_TBL.CUST_Agcc_tblOUNT_ID
AND HZ_CUST_AGgcc_tbl_TBLT_SITES.HZ_PARTY_SITES_TBL_ID = HZ_PARTY_SITES_TBL.HZ_PARTY_SITES_TBL_ID
AND Hz_loc_tbl.Hz_loc_tblATION_ID = HZ_PARTY_SITES_TBL.Hz_loc_tblATION_ID
AND AR_Pay_Sch_tbl.CASH_RECEIPT_ID = AR_CASH_RCPT_ALL_TBL.CASH_RECEIPT_ID
AND AR_CASH_RCPT_ALL_TBL.CASH_RECEIPT_ID = AR_CASH_RECPT_HIST_TBL.CASH_RECEIPT_ID
AND AR_CASH_RECPT_HIST_TBL.Agcc_tblOUNT_CODE_COMBINATION_ID = gcc_tbl.CODE_COMBINATION_ID
AND AR_Pay_Sch_tbl.CASH_RECEIPT_ID = AR_Rec_Appl_tbl.CASH_RECEIPT_ID
AND HZ_CUST_SITE_USES_TBL.HZ_CUST_Agcc_tblT_ALL_TBL_SITE_ID = HZ_CUST_AGgcc_tbl_TBLT_SITES.HZ_CUST_Agcc_tblT_ALL_TBL_SITE_ID
AND HZ_CUST_Agcc_tblT_ALL_TBL.CUST_Agcc_tblOUNT_ID = HZ_CUST_AGgcc_tbl_TBLT_SITES.CUST_Agcc_tblOUNT_ID
AND HZ_CUST_AGgcc_tbl_TBLT_SITES.HZ_CUST_Agcc_tblT_ALL_TBL_SITE_ID = HZ_CUST_SITE_USES_TBL.HZ_CUST_Agcc_tblT_ALL_TBL_SITE_ID
AND AR_Pay_Sch_tbl.CUSTOMER_ID = HZ_CUST_AGgcc_tbl_TBLT_SITES.CUST_Agcc_tblOUNT_ID
AND AR_Pay_Sch_tbl.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_TBL.SITE_USE_ID
AND AR_Pay_Sch_tbl.CASH_RECEIPT_ID = AR_CASH_RECPT_HIST_TBL.CASH_RECEIPT_ID
AND NVL(HZ_CUST_SITE_USES_TBL.STATUS, 'A') = 'A'
AND AR_Pay_Sch_tbl.CLASS = 'PMT'
AND AR_Rec_Appl_tbl.STATUS = 'UNAPP'
AND AR_Pay_Sch_tbl.STATUS = 'OP'
AND HZ_CUST_SITE_USES_TBL.SITE_USE_CODE = 'BILL_TO'
AND HZ_CUST_Agcc_tblT_ALL_TBL.Agcc_tblOUNT_NUMBER = '<ENTER AGCC TBLOUNT NUMBER>'
AND AR_Pay_Sch_tbl.TRX_DATE <= '<ENTER_TRX_DATE>'
AND TRUNC(AR_Pay_Sch_tbl.GL_DATE) <= '<ENTER_GL_DATE>'
AND AR_CASH_RECPT_HIST_TBL.STATUS NOT IN ('CLEARED') HAVING
NVL(SUM(AR_Rec_Appl_tbl.AMOUNT_APPLIED), 0) > 0
The blog provides the Oracle Apps R12 SQL Query to get fetch PO approval workflow activity details
SELECT EXECUTION_TIME,
WF_Item_Actvity_Status.BEGIN_DATE,
WF_Actvity_tbl2.NAME PROCESS,
WF_Actvity_tbl2.DISPLAY_NAME ,
WF_Actvity_tbl1.NAME ACTIVITY,
WF_Actvity_tbl1.DISPLAY_NAME ,
WF_Item_Actvity_Status.ACTIVITY_STATUS,
WF_Item_Actvity_Status.ACTIVITY_RESULT_CODE,
WF_Item_Actvity_Status.ASSIGNED_USER,
WF_Item_Actvity_Status.NOTIFICATION_ID ,
WF_NOTIF_TBL.STATUS,
WF_Item_Actvity_Status.ERROR_NAME,
WF_Item_Actvity_Status.ERROR_MESSAGE ,
WF_Item_Actvity_Status.ERROR_STACK
FROM APPLSYS.WF_ITEM_ACTIVITY_STATUSES WF_Item_Actvity_Status,
APPLSYS.WF_PROCESS_ACTIVITIES WF_Proc_Actvity,
APPS.WF_ACTIVITIES_VL WF_Actvity_tbl1,
APPS.WF_ACTIVITIES_VL WF_Actvity_tbl2,
APPLSYS.WF_ITEMS WF_ITEM_TBL,
APPLSYS.WF_NOTIFICATIONS WF_NOTIF_TBL
WHERE 1=1
AND WF_Item_Actvity_Status.ITEM_TYPE = 'POAPPRV'
AND WF_Item_Actvity_Status.ITEM_KEY = '<ENTER_ITEM_KEY>'
AND WF_Item_Actvity_Status.PROCESS_ACTIVITY = WF_Proc_Actvity.INSTANCE_ID
AND WF_Proc_Actvity.ACTIVITY_NAME = WF_Actvity_tbl1.NAME
AND WF_Proc_Actvity.ACTIVITY_ITEM_TYPE = WF_Actvity_tbl1.ITEM_TYPE
AND WF_Proc_Actvity.PROCESS_NAME = WF_Actvity_tbl2.NAME
AND WF_Proc_Actvity.PROCESS_ITEM_TYPE = WF_Actvity_tbl2.ITEM_TYPE
AND WF_Proc_Actvity.PROCESS_VERSION = WF_Actvity_tbl2.VERSION
AND WF_ITEM_TBL.ITEM_TYPE = 'POAPPRV'
AND WF_ITEM_TBL.ITEM_KEY = WF_Item_Actvity_Status.ITEM_KEY
AND WF_ITEM_TBL.BEGIN_DATE >= WF_Actvity_tbl1.BEGIN_DATE
AND WF_ITEM_TBL.BEGIN_DATE < NVL(WF_Actvity_tbl1.END_DATE, I.BEGIN_DATE+1)
AND WF_NOTIF_TBL.NOTIFICATION_ID(+) = WF_Item_Actvity_Status.NOTIFICATION_ID
ORDER BY 2,1;
Query to get Requisition Approval Path
SELECT PER_POS_STRUC_TBL.NAME
FROM PO_REQUISITION_HEADERS_ALL PO_REQ_HDR_TBL,
WF_ITEM_ATTRIBUTE_VALUES WF_ITM_ATTR_VAL_TBL,
PER_POSITION_STRUCTURES PER_POS_STRUC_TBL
WHERE 1=1
AND WF_ITM_ATTR_VAL_TBL.ITEM_TYPE = PO_REQ_HDR_TBL.WF_ITEM_TYPE
AND WF_ITM_ATTR_VAL_TBL.ITEM_KEY = PO_REQ_HDR_TBL.WF_ITEM_KEY
AND WF_ITM_ATTR_VAL_TBL.NAME = 'APPROVAL_PATH_ID'
AND TO_NUMBER(WF_ITM_ATTR_VAL_TBL.NUMBER_VALUE) = PER_POS_STRUC_TBL.POSITION_STRUCTURE_ID
AND PO_REQ_HDR_TBL.SEGMENT1 = '<ENMTER_REQUISITION_NUMBER>' ;
AND PO_REQ_HDR_TBL.ORG_ID = <ENTER_ORG_ID>;
Query to get Requisition Approval Path
SELECT PER_POS_STRUC_TBL.NAME
FROM po_headers_all poh PO_HDR_TBL,
WF_ITEM_ATTRIBUTE_VALUES WF_ITM_ATTR_VAL_TBL,
PER_POSITION_STRUCTURES PER_POS_STRUC_TBL
WHERE 1=1
AND WF_ITM_ATTR_VAL_TBL.ITEM_TYPE = PO_HDR_TBL.WF_ITEM_TYPE
AND WF_ITM_ATTR_VAL_TBL.ITEM_KEY = PO_HDR_TBL.WF_ITEM_KEY
AND WF_ITM_ATTR_VAL_TBL.NAME = 'APPROVAL_PATH_ID'
AND TO_NUMBER(WF_ITM_ATTR_VAL_TBL.NUMBER_VALUE) = PER_POS_STRUC_TBL.POSITION_STRUCTURE_ID
AND PO_HDR_TBL.PO_HEADER_ID = <PO_HEADER_ID>;
AND PO_HDR_TBL.ORG_ID = <ENTER_ORG_ID>;
The blog provides the Oracle SQL Query to fetch CREATEPO Workflow for the approved requisition. The Query requires the Requisition Number and particular ORG_ID for which approved requisition is to be determined.
Retrieve the Requisition Header Id
SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE SEGMENT1 = '&REQ_NUMBER'
AND ORG_ID = &ORG_ID;
Retrieve Item Type and Item Key by passing Requisition Header Id
SELECT ITEM_TYPE, ITEM_KEY
FROM WF_ITEMS
WHERE ITEM_KEY LIKE '&REQ_HDR_ID'||'%'
AND ITEM_TYPE='CREATEPO'
AND ROOT_ACTIVITY = 'OVERALL_AUTOCREATE_PROCESS';
Retrieve the Root Activity , item Type and Item Key by passing the Requisition Header Id
SELECT ITEM_TYPE, ITEM_KEY, ROOT_ACTIVITY
FROM WF_ITEMS
WHERE PARENT_ITEM_KEY LIKE '&REQ_HDR_ID'||'%'
AND ITEM_TYPE='CREATEPO'
AND ROOT_ACTIVITY IN ('REQ_LINE_PROCESSING', 'CREATE_AND_APPROVE_DOC');
The blog provides the SQL Query to get On-Account Receipt Amount Total in Oracle Receivables.
What is On-account receipt in Receivables?
Oracle Receivables R12 allows to apply on-account receipts to customer’s open debit items. Consider and example Customer receives the goods worth $1000 but was not happy with the received goods and thus company agrees to credit $200 to customer account. When customer makes the payment of $800, then $200 is credited as customer on-account
Oracle Receivables On-Account Receipt Amount
SELECT NVL(SUM(AR_PAYMENT_SCH_ALL_TBL.AMOUNT_DUE_REMAINING), 0) OnAccount_Recpt_TotalAmt
FROM HZ_CUST_AGCC_TBLOUNTS_ALL HZ_CUST_AGCC_TBLTS_ALL_TBL,
AR_PAYMENT_SCHEDULES_ALL AR_PAYMENT_SCH_ALL_TBL,
AR_RECEIVABLE_APPLICATIONS_ALL AR_RECV_APPLS_ALL_TBL,
HZ_HZ_CUST_ACCT_ALL_TBL_SITES_ALL HZ_CUST_AGCC_TBLT_SITES ,
HZ_HZ_PARTY_SITES_TBLS HZ_PARTY_SITES_TBL,
HZ_LOCATIONS LOC,
HZ_CUST_HZ_SITE_USES_TBL_ALL HZ_SITE_USES_TBL,
AR_CASH_RECEIPTS_ALL AR_CASH_RECPT_ALL_TBL,
AR_CASH_RECEIPT_HISTORY_ALL AR_CASH_RECPT_HIST_TBL,
GL_CODE_COMBINATIONS GCC_TBL
WHERE 1=1
AND AR_PAYMENT_SCH_ALL_TBL.CUSTOMER_ID = HZ_CUST_AGCC_TBLTS_ALL_TBL.CUST_AGCC_TBLOUNT_ID
AND AR_PAYMENT_SCH_ALL_TBL.CUSTOMER_ID = HZ_CUST_AGCC_TBLTS_ALL_TBL.CUST_AGCC_TBLOUNT_ID
AND HZ_CUST_AGCC_TBLT_SITES .HZ_PARTY_SITES_TBL_ID = HZ_PARTY_SITES_TBL.HZ_PARTY_SITES_TBL_ID
AND LOC.LOCATION_ID = HZ_PARTY_SITES_TBL.LOCATION_ID
AND AR_PAYMENT_SCH_ALL_TBL.CASH_RECEIPT_ID = AR_CASH_RECPT_ALL_TBL.CASH_RECEIPT_ID
AND AR_CASH_RECPT_ALL_TBL.CASH_RECEIPT_ID = AR_CASH_RECPT_HIST_TBL.CASH_RECEIPT_ID
AND AR_CASH_RECPT_HIST_TBL.AGCC_TBLOUNT_CODE_COMBINATION_ID = GCC_TBL.CODE_COMBINATION_ID
AND AR_PAYMENT_SCH_ALL_TBL.CLASS = 'PMT'
AND AR_PAYMENT_SCH_ALL_TBL.CASH_RECEIPT_ID = AR_RECV_APPLS_ALL_TBL.CASH_RECEIPT_ID
AND AR_RECV_APPLS_ALL_TBL.STATUS IN ('AGCC_TBL')
AND AR_PAYMENT_SCH_ALL_TBL.STATUS = 'OP'
AND HZ_SITE_USES_TBL.SITE_USE_CODE = 'BILL_TO'
AND HZ_SITE_USES_TBL.HZ_CUST_AGCC_TBLTS_ALL_TBL_SITE_ID = HZ_CUST_AGCC_TBLT_SITES .HZ_CUST_AGCC_TBLTS_ALL_TBL_SITE_ID
AND NVL(HZ_SITE_USES_TBL.STATUS, 'A') = 'A'
AND HZ_CUST_AGCC_TBLTS_ALL_TBL.CUST_AGCC_TBLOUNT_ID = HZ_CUST_AGCC_TBLT_SITES .CUST_AGCC_TBLOUNT_ID
AND HZ_CUST_AGCC_TBLT_SITES .HZ_CUST_AGCC_TBLTS_ALL_TBL_SITE_ID = HZ_SITE_USES_TBL.HZ_CUST_AGCC_TBLTS_ALL_TBL_SITE_ID
AND AR_PAYMENT_SCH_ALL_TBL.CUSTOMER_ID = HZ_CUST_AGCC_TBLT_SITES .CUST_AGCC_TBLOUNT_ID
AND HZ_CUST_AGCC_TBLTS_ALL_TBL.AGCC_TBLOUNT_NUMBER = '<ENTER_ACCOUNT_NUMBER>'
AND AR_PAYMENT_SCH_ALL_TBL.TRX_DATE <= '<ENTER_TRX_DATE>'
AND TRUNC(AR_PAYMENT_SCH_ALL_TBL.GL_DATE) <= '<ENTER_GL_DATE>'
AND AR_PAYMENT_SCH_ALL_TBL.CUSTOMER_SITE_USE_ID = HZ_SITE_USES_TBL.SITE_USE_ID HAVING
NVL(SUM(AR_RECV_APPLS_ALL_TBL.AMOUNT_APPLIED), 0) > 0;
The blog provides the steps to create Oracle Receivables R12 AR Receipt Batch Sources. The Receipt batch sources provides the default value for the Receipt Class, Receipt Methods and Remittance Bank Account fields that are added as part of Receipt Batch. Oracle Receivables allows to accept the default value or can be created as per user requirement.
Receipt Batch sources can use manual or automatic batch numbering as defined in the setup
When receipt batch source is selected for Receipt Creation, Oracle Receivables automatically uses the Cash, Unapplied, Unidentified, On-Account, and Earned and Unearned Discount account to the Receipt Payment Method.
Prerequisites for Receipt Batch Source
The below setup should be available before you define a Receipt Batch Source
Define Banks
Define Receipt Classes
Define Receipt Methods
How to Create a Receipt Source in Oracle Receivables R12?
Perform the below steps to define a Receipt Source in Oracle AR R12
Navigate to AR -> setup -> Receipt -> Receipt source
Select an OU (Operating Unit)
Enter the Receipt Class
Enter the Receipt Method (Optional)
Enter Bank Account
Manual Batch Numbering ( Select if Receipt Batch Numbers to be entered manually)
Automatic Batch Numbering ( Select if Receipt Batch Numbers are entered by System)
Enter Start Date ( Date from when Receipt Source becomes Active)
Enter End Date ( Date when Receipt Source becomes Inactive)
Oracle Receivables SQL to get AR Receipt Sources Data Extract
SELECT HOU.NAME OPERATING_UNIT
,AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.NAME
,AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.DESCRIPTION
,AR_LOOKUPS_TBL.MEANING RECEIPT_SOURCE_TYPE
,AR_RECEIPT_CLS_TBL.NAME RECEIPT_CLASS
,AR_RECEIPT_MTHDS_TBL.NAME PAYMENT_METHOD
,CE_BANK_ACCTS_TBL.BANK_ACCOUNT_NAME BANK_ACCOUNT
,AR_LOOKUPS_TBL1.MEANING BATCH_NUMBERING
,AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.LAST_BATCH_NUM LAST_NUMBER
,AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.START_DATE_ACTIVE EFFECTIVE_START_DATE
,AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.END_DATE_ACTIVE EFFECTIVE_END_DATE
FROM AR_BATCH_SOURCES_AR_LOOKUPS_TBLL AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL
,HR_OPERATING_UNITS HOU
,AR_LOOKUPS AR_LOOKUPS_TBL
,AR_RECEIPT_CLASSES AR_RECEIPT_CLS_TBL
,AR_RECEIPT_METHODS AR_RECEIPT_MTHDS_TBL
,AR_LOOKUPS AR_LOOKUPS_TBL1
,CE_BANK_ACCOUNTS CE_BANK_ACCTS_TBL
WHERE 1=1
AND AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.ORG_ID=HOU.ORGANIZATION_ID
AND HOU.ORGANIZATION_ID=NVL(:P_ORG_ID,HOU.ORGANIZATION_ID)
AND AR_LOOKUPS_TBL.LOOKUP_CODE(+)=AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.TYPE
AND AR_LOOKUPS_TBL.LOOKUP_TYPE(+)='BATCH_TYPE'
AND AR_RECEIPT_CLS_TBL.RECEIPT_CLASS_ID(+)=AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.DEFAULT_RECEIPT_CLASS_ID
AND AR_RECEIPT_MTHDS_TBL.RECEIPT_METHOD_ID(+)=AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.DEFAULT_RECEIPT_METHOD_ID
AND AR_LOOKUPS_TBL1.LOOKUP_CODE(+)=AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.AUTO_BATCH_NUMBERING
AND AR_LOOKUPS_TBL1.LOOKUP_TYPE(+)='BATCH_NUMBERING'
AND CE_BANK_ACCTS_TBL.BANK_ACCOUNT_ID(+)=AR_BATCH_SOURC_AR_LOOKUPS_TBLL_TBL.REMIT_BANK_ACCT_USE_ID ;
The blog provides the steps to “How to Setup AR Receipt Classes in Oracle Receivables R12 ?”. The Receipt Classes in Oracle Receivables R12 helps in Receipt processing steps ( Receipt Confirmation, Receipt Remittance and Receipt Reconciliation. The Receipt Method assigned to Receipt Class helps in determining the accounting for receipts in Oracle Receivables. Each Create Receipt Class should have the following defined
Receipt Creation Method ( Manual / Automatic)
Receipt Remittance Method ( Standard, Factoring, Standard and Factoring, No Remittance)
Receipt Payment Method
AR Receipt Classes Setup in Oracle Receivables R12
Perform the below steps on how to setup AR Receipt Classes in Oracle Apps AR R12
Navigate to Receipt Classes
Enter Receipt Name
Notes Receivable Receipt Class ( Select the Checkbox if Receipt to handle future payments through Check or Promissory Note Document are considered in this option. A Note could have the status ( Open, Return, Delinquent, Repurchase, Exchange)
Enter Creation Method ( Manual / Automatic)
Require Confirmation : Select Checkbox if allows automatic receipt creation to use the Receipt Class
Enter Remittance Method: Selection of Require Confirmation for automatic receipts, make Remittance Method as mandatory. The Remittance Methods can be classified as given below
Standard : Remittance account used for automatic receipts with the Receipt Class
Factoring : Factoring account used for automatic receipts with the Receipt Class
Standard and Factoring : Allows to select Remittance Account or Factoring Account regardless of the batch remittance method
No Remittance : If do not require receipts assigned to the receipt class to be remitted
Enter Clearance Method: The Receipts created using a payment method assigned to the receipt class rquires to be reconciled before posting them to Cash Account in the General Ledger. The Clearance Method can be classified as given below
Directly : Select the option if the receipts do not need to be remitted to the bank and subsequently cleared
By Automatic Clearing : Select the option if the receipts to be cleared using the Automatic Clearing program
By Matching : Select the option if the receipts to be cleared manual in Order Cash Management
Remittance Bank Accounts
Click “Bank Accounts” on Receipt Sources Windows to assign the Remittance Bank Account . Provide the below given details
S. No
GL Field Name
GL Field Description
User Action
1
Operating Unit
Operating Unit
Select OU (Operating Unit)
2
Bank Name
Bank Name
Select Bank Name
3
Account Name
Account Name
Select the Account Name
4
Effective Dates
Effective Date
Enter the Effective Date
S. No
GL Field Name
GL Field Description
User Action
1
Cash
Cash Accounting Flexfield
Enter Cash Accounting segments
2
Bank
Bank Accounting Flexfield
Enter Bank Accounting segments
3
Unapplied Receipts
Unapplied Receipts Accounting Flexfield
Enter Unapplied Receipts Accounting segments
4
Unidentified Receipts
Unidentified Receipts Accounting Flexfield
Enter Unidentified Receipts Accounting segments
5
On Account Receipts
On Account Receipts Accounting Flexfield
Enter On-Account Accounting segments
6
Unearned Discounts
Unearned Discounts field
Select Unearned Discount Value
7
Earned Discounts
Earned Discounts field
Select Earned Discount Value
Oracle Receivables AR Receipt Method Setup
Oracle Receivables R12 uses Payment method to determine the Customer’s Remittance Bank Account details . Oracle Receivables allows to assign multiple remittance banks to each payment method considering one bank account as the primary bank account for each currency. Payments methods can be assigned to Receipt Sources to account the manual receipts and Autolockbox in Oracle receivables.
Automatic Receipts are required to be associated with Payment Methods. The below given are the Receipt Rule to be defined for payment methods when used with automatic reeipts
One Per Customer : Allows to create 1 payment per person
One per Customer and Due Date : Allows to create 1 payment per person and Due Date. Multiple payments can be processed based on Due Date
One Per Site : Allows to create 1 payment per site
One Per Invoice : Allows to create 1 payment per invoice
One Per Site and Due Date : Allows to create 1 payment per site and Due Date. Multiple payments can be processed based on Due Date
Perform the below steps to setup Receipt Methods in Oracle Apps R12
Navigate to Receipt Classes Window
Enter the Receipt Class
Enter the New Payment Method ( shows as Printed Name field on Receipt Classes Window)
Receipt Maturity Date Rule ( Enter Maturity Date for Automatic Receipts where Due Date is used for payment processing)
Automatic Print Program ( Automatic Receipts uses receivables standard receipt print program to format the payment output)
The blog provides the AR Receipt API methods and its usage in Oracle Receivables R12. The Oracle Receivables used AR Receipt API for creating and updating receipts received for AR Receipts Forms and from AR Lockboxes
What functionality is provided by AR Receipt API ?
The Oracle Receivables (AR) Receipt API helps in providing the below given functionality
AR Receipt API allows to create Cash Receipts
AR Receipt API allows to create Cash Receipts and applying to the Debit item
AR Receipt API allows on -account application
AR Receipt API allows to Unapply the on-account application
AR Receipt API allows to Unapply Receipt to a particular AR transaction
AR Receipt API allows to Reverse the Receipt
AR Receipt API allows to perform Receipt Write -Off
AR Receipt API allows to create Miscellaneous Receipt
AR Receipt API allows to create Receipt-to-Receipt application
AR Receipt API allows to create Cash Receipts and on-account application
AR RECEIPT API – AR_RECEIPT_API_PUB
The AR Receipt API AR_RECEIPT_API_PUB provides the below given API call
AR Receipt API Routine
Description
AR_RECEIPT_API_PUB.Create_Cash
Creates a single Cash Receipt
AR_RECEIPT_API_PUB.Apply
Applies the Cash Receipt to a particular Debit Item
AR_RECEIPT_API_PUB.Create_and_apply
Creates the Cash Receipt and applies to a particular Debit Item
AR_RECEIPT_API_PUB.Unapply
unapply a particular Debit Item against the Cash Receipt
AR_RECEIPT_API_PUB.Apply_on_account
Creates a on-account application for a Cash Receipt
AR_RECEIPT_API_PUB.Unapply_on_account
unapplies on-account application for a Cash Receipt
AR_RECEIPT_API_PUB.Reverse
Reverse the Cash Receipt
AR_RECEIPT_API_PUB.activity_application
Applies Receipt to an activity such as Receipt Write -Off
AR_RECEIPT_API_PUB.activity_unapplication
Unapplies Receipt from an activity such as Receipt Write -Off
AR_RECEIPT_API_PUB.Create_misc
Creates a Miscellaneous Receipt
AR_RECEIPT_API_PUB.apply_other_account
Applies Receipt to other account such as Claim Investigation
AR_RECEIPT_API_PUB.unapply_other_account
Unapplies Receipt from other account such as Claim Investigation
AR_RECEIPT_API_PUB.apply_open_receipt
Creates a receipt-to-receipt application (payment netting)
AR_RECEIPT_API_PUB.unapply_open_receipt
unapplies a receipt-to-receipt application (payment netting)
AR_RECEIPT_API_PUB.Create_apply_on_acc
Creates a cash receipt and an on-account application
Integration with Oracle Payments
The Receipt API uses the Oracle Payment Integration for the below given API calls
The blog provides the list of AR Lookups that need to be defined in the Oracle Receivables R12. New lookups can be created or predefined lookups can be updated in the Oracle Receivables R12. The Oracle Receivables R12 AR lookups are maintained in the FND_LOOKUP_VALUES Table where the LOOKUP_TYPE and MEANING Column values should be unique.
The below given are the commonly used Oracle Receivables lookups in R12.
Customer Lookups
Customer Profile Lookups
Transaction Lookups
Collections Lookups
Receipt Lookups
Customer Lookups: The below given are the Customer Lookups defined in the Oracle Receivables R12
Lookup Type
Lookup Code
Address Categories
ADDRESS_CATEGORY
Customer Address Business Purpose
SITE_USE_CODE
Customer Categories
CUTOMER_CATEGORY
Customer Class
CUSTOMER_CLASS
Demand Class
DEMAND_CLASS
FOB
FOB
Customer Contact Job Title
RESPONSIBILTY
Party Fiscal Classification for Leasing
AR_TAX_PARTY_FISCAL_CLASS
Contact Title at Customer Sites
CONTACT_TITLE
Customer Communication Type
COMMUNICATION_TYPE
Customer Relationship
RELATIONSHIP_TYPE
SIC Code Type
SIC_CODE_TYPE
State Codes
STATE
Customer Profile Lookups: The below given are the Customer Profile Lookups defined in the Oracle Receivables R12
Lookup Type
Lookup Code
Account Status
ACCOUNT_STATUS
Customer Credit Rating
CREDIT_RATING
Customer Credit Risk
CREDIT_RISK
Transaction Lookups: The below given are the Transaction Lookups defined in the Oracle Receivables R12
Lookup Type
Lookup Code
Adjustment Reason
ADJUSTMENT_REASON
Approval Type
APPROVAL_TYPE
Batch Status
BATCH_STATUS
Canadian Provinces
AR_CANADIAN_PROVINCE
Commitment Description
COMMITMENT_DESCRIPTION
Credit Memo Reason
CREDIT_MEMO_REASON
Credit Memo Status
CREDIT_MEMO_REQUEST_STATUS
Invoice Reason
INVOICING_REASON
Location Identifier
ARTAXVDR_LOC_QUALIFIER
Magnetic Format Codes
MAGNETIC_FORMAT_CODE
Product Fiscal Classification
AR_TAX_PRODUCT_FISCAL_CLASS
Special Instructions
SPECIAL_INSTRUCTIONS
Tax Classification
AR_TAX_CLASSIFICATION
Tax Exemption Reason
TAX_REASON
Tax Rate Exception reason
TAX_EXCEPTION_REASON
Tax Type
TAX_TYPE
Transaction Fiscal Classification
AR_TAX_TRX_BUSINESS_CATEGORY
Message Type
STANDARD_MSG_TYPES
Standard Text Type
STANDARD_TEXT
Collections Lookups: The below given are the Collections Lookups defined in the Oracle Receivables R12
Lookup Type
Lookup Code
Special Bucket type
AGING_BUCKET_LINE_TYPE
Receipt Lookups: The below given are the Receipt Lookups defined in the Oracle Receivables R12
The blog covers the Supplier Conversion Process in Oracle Payables R2. The Supplier Conversion Process in Oracle Payables is one of the most commonly used for Supplier Conversion / Migration Process. The Supplier Conversion / Migration Program loads the Supplier Master Data, Supplier Sites Data and Supplier Contacts from source data files into Supplier Staging Tables in Oracle Payables, Validates the Supplier Staging Data and loads into Supplier Interface Tables.
Open Interface Approach : Flat File -> processed using SQL *Loader Staging Table -> processed using PLSQL Package Interface Table -> processed using Standard Concurrent Programs
Prerequisites for Supplier Conversion Process
The below given setup should be available before Supplier Conversion Program runs
Set of Books Setup
Payment Terms Setup
Pay Groups Setup
GL Code Combinations (CCID) Setup
Supplier Setup
Bank Accounts Setup
Currency Setup
Employee Setup ( if Employee is considered as Supplier)
Supplier Data Load for Supplier Conversion Process
The below given approach can be used for load Supplier Data Load for the Supplier Conversion Program
SQL Loader: SQL Loader helps in loading the bulk records into Oracle Tables
APEX: Oracle Application Express could be another option for bulk upload for supplier records
Supplier Validation in Supplier Conversion Process
The below given are the validations that needs to be considered when running the Supplier Conversion Program
Duplicate Vendors NOT to be processed from AP_SUPPLIERS Table
Duplicate Vendor Name NOT to be processed from AP_SUPPLIERS_INT and AP_SUPPLIERS Table
Retrieve the valid Payment Terms from AP_TERMS_TL table
Retrieve the valid Pay Groups from FND_LOOKUP_VALUES_VL table where lookup_type=‘PAY GROUP’
Retrieve the valid Vendor Type from PO_LOOKUP_CODES table where lookup_type=‘VENDOR TYPE’
Retrieve the valid Employee records from PER_ALL_PEOPLE_F table
Duplicate Vendors NOT to be processed from AP_SUPPLIERS Table
Duplicate Supplier Site Code NOT to be processed from AP_SUPPLIERS_SITES_ALL Table
Retrieve the valid Country Code records from FND_TERRITORIES_TL table
Retrieve the Payment Method records from IBY_PAYMENT_METHODS_VL table
Supplier Interface Programs
The below given interface programs are to be used as part of Supplier Conversion
Supplier Open Interface Import
Supplier Sites Open Interface Import
Supplier Site Contacts Open Interface Import
Supplier Interface Tables
The below given interface tables are to be used as part of Supplier Conversion
AP_SUPPLIERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACT_INT
AP_SUPPLIER_INT_REJECTIONS ( list down the rejected records for Supplier Master, Supplier Sties and Supplier Contact as part of Supplier Conversion Process)
AP_SUPPLIERS_INT : Oracle Payables provides the AP_SUPPLIERS_INT as the Open Interface Table which holds the Supplier Master data. When the Supplier Open Interface Import Program is submitted, then each record having unique VENDOR_INTERFACE_ID in AP_SUPPLIERS_INT is processed and loaded into PO_VENDORS Table
AP_SUPPLIERS_INT Table Column
AP_SUPPLIERS_INT Column Description
VENDOR_INTERFACE_ID
Unique record identifier generated using AP_SUPPLIERS_INT_S.NEXTVAL
SEGMENT1
Supplier Number
VENDOR_NAME
Supplier Name
VENDOR_TYPE_LOOKUP_CODE
Provides the Supplier Type
SHIP_TO_LOCATION_CODE
Default ship-to-location name
BILL_TO_LOCATION_CODE
Default bill-to-location name
TERMS_NAME
Provides the Supplier Payment Terms
TAX_VERIFICATION_DATE
Provides the Tax verification date(1099)
VAT_REGISTRATION_NUM
Provides the Tax Registration Number
PAY_GROUP_LOOKUP_CODE
Provides the Supplier Pay Group
INVOICE_CURRENCY_CODE
Default Invoice Currency Code
PAYMENT_CURRENCY_CODE
Provides the Supplier Payment Currency Code
NUM_1099
Provides the Tax Identification date(1099)
VAT_CODE
Provides the default Invoice Tax Code
HOLD_FLAG
‘Y’ if Supplier is on Purchasing Hold
SUMMARY_FLAG
Key flex field summary flag
ENABLED_FLAG
Key flex field enable flag
EMPLOYEE_ID
provides Employee_id if supplier is an employee
ATTRIBUTE1 -15
Descriptive Flex field Segments
AP_SUPPLIER_SITES_INT : Oracle Payables provides the AP_SUPPLIER_SITES_INT as the Open Interface Table which holds the Supplier Site Code data. When the Supplier Site Open Interface Import Program is submitted, then each record having unique VENDOR_ID in AP_SUPPLIER_SITES_INT is processed and loaded into PO_VENDOR_SITES_ALL Table
AP_SUPPLIER_SITES_INTTable Column
AP_SUPPLIER_SITES_INT Table Column Description
VENDOR_SITE_INTERFACE_ID
Unique record identifier generated using AP_SUPPLIER_SITES_INT_S.NEXTVAL
VENDOR_SITE_CODE
Provides the Supplier Site Name
ADDRESS_LINE1
Provides the Supplier Address
ADDRESS_LINE2
Provides the Supplier Address
ADDRESS_LINE3
Provides the Supplier Address
CITY
Provides the Supplier City
STATE
Provides the Supplier State
ZIP
Provides the Supplier State Zip Code
COUNTRY
Provides the Supplier Country
PHONE
Provides the Supplier Phone Number
FAX
Provides the Supplier Fax Number
SHIP_TO_LOCATION_CODE
Default ship-to-location name
BILL_TO_LOCATION_CODE
Default bill-to-location name
PAYMENT_METHOD_LOOKUP_CODE
Provides the Supplier Payment Method
VAT_CODE
Provides the Supplier Invoice Tax Code
PAY_GROUP_LOOKUP_CODE
Provides the Supplier Payment Group
TERMS_NAME
Provides the Supplier Payment Terms
INVOICE_CURRENCY_CODE
Provides the Default Supplier Invoice Currency Code
PAYMENT_CURRENCY_CODE
Provides the Supplier Invoice Payment Currency Code
EMAIL_ADDRESS
Provides the Supplier Email Address
PURCHASING_SITE_FLAG
‘Y if the Supplier Site is allowed for Purchasing
AUTO_TAX_CALC_FLAG
Level of automatic tax calculation for supplier
HOLD_ALL_PAYMENTS_FLAG
‘Y’ if Supplier Payments are on HOLD
AP_SUP_SITE_CONTACT_INT: Oracle Payables provides the AP_SUP_SITE_CONTACT_INT as the Open Interface Table which holds the Supplier Site Code data. When the Supplier Site Open Interface Import Program is submitted, then each supplier contact record is mapped to Supplier Site using the VENDOR_SITE_CODE and ORG_ID to create a Supplier Contact into PO_VENDOR_CONTACTS Table
AP_SUP_SITE_CONTACT_INT Table Column
AP_SUP_SITE_CONTACT_INT Table ColumnDescription
VENDOR_INTERFACE_ID
Supplier interface record unique identifier
VENDOR_CONTACT_INTERFACE_ID
Unique record identifier generated using AP_SUP_SITE_CONTACT_INT_S.NEXTVAL
VENDOR_SITE_CODE
Provides the Supplier Site Name
FIRST_NAME
Provides the Supplier First Name
LAST_NAME
Provides the Supplier Last Name
AREA_CODE
Provides the Supplier Area Code
PHONE
Provides the Supplier Phone Number
FIRST_NAME_ALT
Provides the Alternate Name for Supplier First Name
LAST_NAME_ALT
Provides the Alternate Name for Supplier Last Name
The blog provides the commonly used SQL Queries to reconcile the Oracle Receivables R12 AR Receipts to get accounted AR Receipts with GL Code Combinations, AR Payments received through checks , AR Receipts processing details, etc.
Oracle AR Receipts Tables
The below given are the Oracle AR Receipts tables in Oracle Receivables R12
Oracle AR R12 Receipts Tables
AR Receipt Table Description
AR_CASH_RECEIPTS_ALL
The Receipt table stores receipt entry per record
AR_CASH_RECEIPT_HISTORY_ALL
The Receipt table stores the AR Receipt History and AR Receipt status updates
AR_MISC_CASH_DISTRIBUTIONS_ALL
The table stores the accounting entries for miscellaneous cash applications
AR_DISTRIBUTIONS_ALL
The table stores the accounting distributions for cash receipts, miscellaneous receipts, adjustments, credit memo applications, cash receipt applications, and bills receivable transactions
AR_RECEIVABLE_APPLICATIONS_ALL
The table stores the accounting entries for cash and credit memo applications
Oracle Receivables R12 SQL Query to retrieve AR Receipts accounted with GL Code Combinations
The Oracle Receivables R12 SQL Query uses table mappings for AR_DISTRIBUTIONS_ALL , GL_CODE_COMBINATIONS, AR_CASH_RECEIPT_HISTORY_ALL and AR_CASH_RECEIPT_ALL to retrieve AR Receipts with GL Code Combinations from GL Table
SELECT AMOUNT_DR, AMOUNT_CR, ACCTD_AMOUNT_DR, ACCTD_AMOUNT_CR,
GCC.SEGMENT1
|| '.'
|| GCC.SEGMENT2
|| '.'
|| GCC.SEGMENT3
|| '.'
|| GCC.SEGMENT4
|| '.'
|| GCC.SEGMENT5 ACCOUNT
FROM AR.AR_DISTRIBUTIONS_ALL AD,
GL.GL_CODE_COMBINATIONS GCC
WHERE 1=1
AND EXISTS (
SELECT 'T'
FROM AR.AR_CASH_RECEIPT_HISTORY_ALL A,
AR.AR_CASH_RECEIPTS_ALL B
WHERE A.CASH_RECEIPT_ID = B.CASH_RECEIPT_ID
AND SOURCE_ID = CASH_RECEIPT_HISTORY_ID
AND B.ORG_ID = '&ORG_ID'
AND B.ORG_ID = A.ORG_ID
AND B.RECEIPT_NUMBER LIKE '%&RECEIPT_NUMBER%')
AND AD.CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID
Oracle Receivables R12 SQL Query to retrieve AR Receipts Payment Schedule Details
The Oracle Receivables R12 SQL Query uses table mappings for AR_PAYMENT_SCHEDULES_ALL , AR_CUSTOMERS, AR_CASH_RECEIPT_ALL, HZ_CUST_SITE_USES_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES to retrieve AR Receipts Payment Schedule details based on ORG_ID input
SELECT AR_PAY_SCH_ALL_TBL.AMOUNT_DUE_ORIGINAL RECEIPT_AMOUNT,
AR_PAY_SCH_ALL_TBL.AMOUNT_DUE_REMAINING UNAPPLIED_AMOUNT,
AR_PAY_SCH_ALL_TBL.DUE_DATE,DECODE(AR_PAY_SCH_ALL_TBL.STATUS,'OP','OPEN','CL','CLOSED') RECEIPT_STATUS,
AR_PAY_SCH_ALL_TBL.INVOICE_CURRENCY_CODE,
AR_CUSTOMERS_TBL.CUSTOMER_NAME,
HZ_PARTY_SITES_TBL.PARTY_SITE_NUMBER,
HZ_CUST_SITE_USES_ALL_TBL.SITE_USE_CODE,
AR_CASH_RECEIPTS_ALL_TBL.RECEIPT_NUMBER,
AR_CASH_RECEIPTS_ALL_TBL.RECEIPT_DATE,
AR_CASH_RECEIPTS_ALL_TBL.COMMENTS,
AR_PAY_SCH_ALL_TBL.AMOUNT_APPLIED,
AR_PAY_SCH_ALL_TBL.EXCHANGE_RATE,
AR_PAY_SCH_ALL_TBL.EXCHANGE_DATE,
AR_PAY_SCH_ALL_TBL.EXCHANGE_RATE_TYPE
FROM AR_PAYMENT_SCHEDULES_ALL AR_PAY_SCH_ALL_TBL,
AR_CUSTOMERS AR_CUSTOMERS_TBL,
HZ_CUST_SITE_USES_ALL HZ_CUST_SITE_USES_ALL_TBL,
HZ_CUST_ACCT_SITES_ALL HZ_CUST_ACCT_SITES_ALL_TBL,
HZ_PARTY_SITES HZ_PARTY_SITES_TBL,
AR_CASH_RECEIPTS_ALL AR_CASH_RECEIPTS_ALL_TBL
WHERE AR_PAY_SCH_ALL_TBL.ORG_ID=:P_ORG_ID
AND AR_PAY_SCH_ALL_TBL.CUSTOMER_ID=AR_CUSTOMERS_TBL.CUSTOMER_ID
AND AR_PAY_SCH_ALL_TBL.CASH_RECEIPT_ID=AR_CASH_RECEIPTS_ALL_TBL.CASH_RECEIPT_ID
AND AR_PAY_SCH_ALL_TBL.CLASS='PMT'
AND AR_PAY_SCH_ALL_TBL.CUSTOMER_SITE_USE_ID=HZ_CUST_SITE_USES_ALL_TBL.SITE_USE_ID
AND HZ_CUST_SITE_USES_ALL_TBL.CUST_ACCT_SITE_ID=HZ_CUST_ACCT_SITES_ALL_TBL.CUST_ACCT_SITE_ID
AND HZ_CUST_ACCT_SITES_ALL_TBL.PARTY_SITE_ID=HZ_PARTY_SITES_TBL.PARTY_SITE_ID
Oracle Receivables R12 SQL Query to retrieve AR Receipts Processing Details
SELECT ACRA.REQUEST_ID,ACRA.RECEIPT_NUMBER,
ACRA.AMOUNT, ACRA.RECEIPT_DATE, ACRA.DEPOSIT_DATE, ACRA.*
FROM AR_CASH_RECEIPTS_ALL ACRA
WHERE 1=1
AND RECEIPT_NUMBER IN (<AR_RECEIPT_NUMBER>)
Oracle Receivables R12 SQL Query to retrieve AR Receipts Accounted
SELECT ACR.RECEIPT_NUMBER,
ADA.AMOUNT_DR,
ADA.AMOUNT_CR,
ADA.ACCTD_AMOUNT_DR,
ADA.ACCTD_AMOUNT_CR,
ADA.SOURCE_TABLE,
MCD.SET_OF_BOOKS_ID
FROM AR.AR_DISTRIBUTIONS_ALL ADA,
AR.AR_MISC_CASH_DISTRIBUTIONS_ALL MCD,
AR.AR_CASH_RECEIPTS_ALL ACR
WHERE 1=1
AND ADA.SOURCE_ID = MCD.MISC_CASH_DISTRIBUTION_ID
AND MCD.CASH_RECEIPT_ID = ACR.CASH_RECEIPT_ID
AND ACR.RECEIPT_NUMBER =<AR_RECEIPT_NUMBER>
AND MCD.SET_OF_BOOKS_ID = <SOB_ID>
Oracle Receivables R12 SQL Query to retrieve AR Payments Received Through Checks
SELECT APIA.CHECK_NUMBER, APIA.STATUS, APIA.*
FROM AR_PAYMENTS_INTERFACE_ALL APIA
WHERE 1=1
AND APIA.STATUS ='AR_PLB_GL_PERIOD_CLOSED'
AND CHECK_NUMBER IN (<CHECK_NUMBER>)
ORDER BY CREATION_DATE DESC
SELECT * FROM AR_PAYMENTS_INTERFACE
WHERE 1=1
AND STATUS = 'AR_PLB_GL_PERIOD_CLOSED'
AND CHECK_NUMBER = <CHECK_NUMBER>
The blog provides the Oracle Payables Standard Programs provided in Oracle Account Payables R12. The Oracle Payables Standard Program helps in processing the Payables Invoices and get accounted into General Ledger for specified accounting period
Oracle Payables R12 Standard Programs
The below given are the Oracle Payable programs
Oracle Payables R12 Standard Programs
Payables Program Description
AutoRate Program
The AutoRate Program enters the Exchange Rate Value based on matched invoice or payment currency, rate date, and rate type for the Invoices with No Exchange Rate defined. The AutoRate Program retrieves Exchange Rate, rate date, and rate type from the GL Daily Rates Table.
Create Procurement Card Issuer Invoice Program
The program creates invoices for the procurement card issuers in the Payables Open Interface tables and selects records for the given date range in AP_EXPENSE_FEED_DISTS and should have Validated Status. Submit Procurement Card Transactions Validation before running procurement card issuers program
Employee Update Program
The program updates employee type supplier records if the corresponding employee record has been changed
Expense Report Export Program
The program create Payables invoices from expense reports in Oracle Payables or Oracle Internet Expenses. Expense Report Export verifies all your expense report information to ensure it creates valid, fully-distributed invoices that are ready for validation.
Invoice Validation Program
The Invoice Validation program Verifies the matching tax, period status, exchange rate, and invoice distribution and automatically applies holds to exception invoices. If an invoice has a hold, manually release the hold or correct the error and then resubmit Invoice Validation
Mass Additions Create Program
The Mass Additions Create program transfers the capital invoice line distributions from Oracle Payables to Oracle Assets. The mass addition line appears in Oracle Assets with the ledger currency amount and thus Oracle Payables R12 sends the invoice distribution amount in the converted ledger currency for Foreign Currency Assets
Payables Open Interface Import Program
The Payables Open Interface Import program creates the Oracle Payables R12 invoices from invoice data in the Payables Open Interface tables received from the source as Quick Invoices , Supplier Invoices, Supplier Invoices transferred from Oracle XML Gateway, Third Party Invoices loaded using SQL Loader , Credit Card transactions , Lease Invoices from Oracle Property Manager, Lease Payments from Oracle Assets
Procurement Card Transaction Validation Report
Procurement Card Transactions Validation program validates the procurement card transactions received from the card issuer and identifies exceptions such as undefined card numbers, invalid transaction or posted currency codes, and invalid card codes
Payables Open Interface Purge Program
The Payables Open Interface Purge Program purges records from the Payables Open Interface tables (AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE)which are successfully imported
Purging Records
The Purging records program helps to purge the transactions from Oracle Payables, Oracle Purchasing, and Oracle Supplier Scheduling records including invoices, purchase orders, suppliers, invoice payments, supplier schedules and purchase receipts which are no longer required
Supplier Merge Program
The Supplier Merge Program helps to merge duplicate suppliers into a single, consolidated supplier and merge transactions within the same supplier from one supplier site to a different supplier site. The program allows to merge all transactions for a supplier into a new supplier, or can merge unpaid invoices. The Supplier merge process cannot be Reverted.
Unaccounted Transactions Sweep Program
The Unaccounted Transactions Sweep Program transfers unaccounted transactions from one accounting period to another by changing the accounting date for all transactions to specified Open Period
Unapply Preupgrade Prepayments Program
The program helps to unapply the prepayment from the invoices
Update Income Tax Details Utility and Report
The program updates the Income Tax Type and/or Income Tax Region fields on invoice distributions required for invoice distributions of United States Federally Reportable suppliers because the fields are necessary for 1099 reporting
Update Matured Future Payment Status Program
The Payables program updates the status of matured bills payable from Issued to Negotiable. If the payment’s Maturity Date is on or before the Maturity Date parameter, then system updates the payment’s status and creates the journal entries to record the status change of the payment