Reports used to Reconciliation AR Receivables with General Ledger

List of Reports used to Reconciliation AR Receivables with General Ledger 

Sales Journal By Customer – Use to review all transactions.

Transaction Register – Use to check that all items that can be posted are reflected on the Sales Journal. The Sales Journal balance should match the total of the transactions here after adding the credit memo total twice (because it is a negative on the Transaction Register and a positive on the Sales   Journal).

Receipts Register – Use to review a list of receipts.

Sales Journal By GL Account – Use to ensure that the Transaction Register matches the Sales Journal.

Journal Entries Report – Use to review the details that make up the general ledger journal entries.

Receipts Journal Report – Use to review details of receipts that appear in the Journal Entries report.

Aging Report – Use the last day of the prior month to get the outstanding opening balance.

Transaction Detail Report – Use to identify transactions that increase the outstanding opening balance.

Adjustments Register – Use to identify any adjustments that affect the transactions for the month.

Unapplied Receipts Register – Use to determine customer balance after taking into account all on-account and unapplied amounts

Applied Receipts Register – Use to identify receipts that reduce the outstanding opening balance.

Invoice Exceptions Report – Use to identify transactions that reduce the outstanding opening balance. This report shows all transactions where the Open Receivables flag is set to No. Therefore, the transactions do not display on the aging but do show in the Transaction Register. This can occur when an item can be ordered in Order Management but not invoiced, such as an internal item.

Supplier Approval Process in Oracle apps

Setting up Supplier Approval

A “Prospective Supplier Registration” or “New Supplier Request” must be approved before a Supplier record is created in the Supplier Master. To implement an approval chain, so that the approval is routed to the appropriate person, you can use an existing implementation of Oracle Approvals Management Engine. Else, from Supplier Lifecycle Management, follow these steps to create approval rules:

1. Set the profile option POS: Use AME for Supplier Approval to Yes for AME rules to apply.
2. Navigate to Approvals Management Business Analyst responsibility. Set up rules for the transaction type: POS Supplier Approval Management.

When AME is enabled, any “Prospective Supplier Registration” or “New Supplier Request” will be routed to a designated approver based on the applicable AME approval rule.

Approving and Managing Supplier User Profile

Use the Approve and Manage Supplier User Profile link to approve prospective supplier users. After approving the users, you can manage the user profile. Complete the following steps:

1.    Search for the user using the Supplier User Profile Management page.

2.    Select the View icon for the applicable supplier user in the search results region to open the Manage User Profile page.

3.    Update the user account as required and click Apply.

Adding Adhoc Approvers

As a buyer, you can add a new approver or an FYI approver during the supplier registration approval process using the Manage Approvals action.
As a current approver, you can also add a new approver or an FYI approver during the supplier registration approval process using the Manage Approvals action.
Both buyer and current approver need to note that they can only add a new approver or an FYI approver only after current approver group(s), and not before or between current approver group(s).

Prospective Supplier Registration Approval Workflow

Oracle Supplier Lifecycle Management uses Oracle Approvals Management for supplier approval. Supplier registration goes through multiple levels of approval and approvers can approve or reject a request.
Using the prospective supplier registration approval workflow, the To-Do Approval Notifications feature provides action-required notifications for approval, which ensures that all related workflow features are enabled. The approval workflow enables administrators to track their pending tasks better and supports key workflow features like vacation rules, forwarding, and requesting additional information. Additionally, the approval workflow enables administrators to set vacation rules and forward the approvals.
The approvals mechanism is similar to that found in Oracle iProcurement. Approvals happen from the new Prospective Supplier Registration Approval Notification page and the Supplier Request page. The system uses AME parallel approval for prospective supplier registration. If AME is enabled, the application displays the AME approval flow graphically. If AME is not enabled, all users who have subscribed to the supplier registration notification receive the approval notification.
The prospective supplier registration approval notification page displays status history and notification history. When the buyer approves or rejects a prospective supplier, the system notifies the supplier. If rejected, the system informs the supplier the reason for rejection, which is captured in Note to Supplier. In this scenario, rejection is permanent and cannot be revoked. If the administrator does not want to reject and would like to send it back to the supplier to update their request / enter additional information, administrators can use the return to supplier after entering a note to the supplier.
If you have navigated to the Supplier Request page from the notification, the system takes you back to the notification when you click Save or Cancel. This page displays AME approval flow graphically.
The buyer administrator's task flow for approvals is as follows:

·         The administrator receive an action-required notification when assigned the task of processing this request.

·         The administrator opens the notification and clicks View / Edit Registration request. Administrators can update the registration request.

·         After making the required changes, the administrator clicks Save. The administrator then returns to the notification from where the registration request was opened.

·         The administrator can approve / reject / re-assign the notification.

 

Creating Hello World OAF Page

1. Create Workspace

2. Create New Project with any Name

3. Use Repository for design time to get connect with Database

4. Browse DBC file from your local machine under folder JDevHome/JDev/DBCFile/Secure

    Then enter your Oracle application Username and Password

    Select Appln Short Name and Responsibility Key





OAF Hello World Page



Solution for OAF Error "oracle.apps.fnd.framework.OAException: Application: ICX, Message Name: Could not find the specified responsibility."

ERROR
-----------------------
oracle.apps.fnd.framework.OAException: Application: ICX, Message Name: Could not find the specified responsibility.
at oracle.apps.fnd.framework.CreateIcxSession.getEncryptedSessId(Unknown Source)
at oracle.apps.fnd.framework.CreateIcxSession.createSession(Unknown Source)

STEPS TO REPRODUCE
-------------------------
The issue can be reproduced at will with the following steps:
1. Setting Up JDeveloper Development Environment
2. Follow the JDeveloper guide to do the 'Hello World' demo
3. Test demo

The issue occurs because the user didn't assign responsibility 'FWK_TBX_TUTORIAL' and 'FWK_TOOLBOX_TUTORIAL_LABS' to applications user.

---------------------------------------------

Solution:
To implement the solution, please execute the following steps:

1. From the responsibility: System Administrator.

2. Navigate to Security > User > Define.

3. Query up the applications user using 'Ctrl + F11'.

4. Assign responsibility OA Framework ToolBox Tutorial (responsibility key:'FWK_TBX_TUTORIAL' and 'FWK_TOOLBOX_TUTORIAL_LABS') to the user.

5. Save the changes and retest the issue.

EDI Gateway Terminology

Terminology	Description
ACH	Business enterprise through which banking transactions are routed.
AIAG	Automotive Industry Action Group. An organization that designs and maintains EDI transaction sets for the automotive industry. Also the name of the X12 subset used by the automotive industry
ANSI	American national Standards Institute. An organization that maintains standards on many different topics.
ANSI ASC X12	ANSI Accredited Standards Committee X12. The ANSI subcommittee appointed to develop standards for EDI in North America.
ASN	Advance Shipment Notice. The EDI document transmitted from a supplier to its customer to describe a pending shipment.
Business Process Re-engineering	The modification of computer applications and related procedures in order to streamline processing.
Communications Software	Software to electronically link two computers for the exchange of information.
Compliance Checking	Comparison of EDI data being sent or received with the applicable EDI standard. Normally part of the EDI translation process.
Data Mapping	Provides significant enhancement and transformation of data from multiple sources to multiple target formats. For example, converting a purchase order file in a proprietary format to a set of EDI purchase order transactions.
DEX/UCS	Direct Exchange UCS. EDI transaction sets used by the direct store delivery segment of the grocery industry.
DISA	Data Interchange Standards Association. The organization responsible for performing the administrative duties of the ANSI X12 subcommittee.
Download	The transfer of data from a large computer to a smaller computer used for front-end or back-end processing.
DSD	Direct Store Delivery
EAGLE	An EDI standard developed and used by the hardware and houseware industry. Part of X12.
EC	Electronic Commerce. The conducting of business through electronic means such as EDI, E-mail, fax and file transfer.
ECR	Efficient Consumer Response. Technologies, procedures and practices used in the grocery industry to eliminate supply chain waste and inefficiencies.
EDI	Electronic Data Interchange. The computer-to-computer transfer of business transactions using standard, industry-accepted message formats.
EDI Document	An EDI transaction set.
EDI Translator	See translation software.
EDI VAN	See Value Added Network.
EDIA	Electronic Data Interchange Association. The organization that wrote the original UCS and WINS standards. It currently acts as Secretariat for the EDI standards for the Ocean, Rail, Motor and Air industries.
EDICA	Electronic Data Interchange Council of Australia. The Australian EDI administrative organization.
EDICC	Electronic Data Interchange Council of Canada. The Canadian EDI administrative organization.
EDIFACT	EDI for Administration, Commerce and Transport. Also known as UN/EDIFACT. The international EDI standard developed through the United Nations and administered in the U.S. by DISA.
EDX	Electrical Industry Data Exchange. The organization which develops EDI data requirements for the electrical industry and represents the industry regarding maintenance of the X12 standard.
E-form	Electronic Form. Usually refers to a computerized version of a paper form.
EFT	Electronic Funds Transfer. Computerized systems for processing transactions between financial institutions. The electronic transfer of funds through the banking system.
EIDX	Electronics Industry Data Exchange. The organization which develops EDI data requirements for the electronics industry and represents the industry regarding maintenance of the X12 standard.
Encryption	A procedure for scrambling data to make it indecipherable to an outside observer. The receiver of the encrypted data must use a decryption procedure to unscramble the data.
File	A collection of related records which serves as a basic unit of storage in a computer system.
Financial EDI	EDI activity that supports financial activities such as billing, paying, and reconciliation.
Functional Acknowledgment	An EDI transaction set sent to acknowledge the receipt of a prior transaction set.
GAS*FLOW	The mission of the Natural Gas Electronic Data Interchange (EDI) Pilot was to bring together a group of companies performing different roles in the transportation of natural gas to test and validate the use of the GAS*FLOW EDI Implementation Guide.
HCFA	Health Care Finance Administration. Government agency responsible for implementing laws relative to Medicare and Medicaid transaction and information reporting.
Hub	Larger organizations that encourage their paper-based business partners to begin using EDI. Wal-Mart and General Mills are examples of hubs.
Implementation Guide	A publication that documents the EDI messages used by a particular industry or company.
Integrated EDI	An approach to EDI implementation requiring no human involvement in the computer-to-computer exchange of data.
Interconnect	The transmission of EDI data from one VAN to another. Enables trading partners to use different VANs.
ISO	International Standards organization. An organization that works with the UN to maintain the standards for all applications of technology and mechanics for furthering global industry.
Just-In-Time	Also JIT. A business approach that assures the receipt of a product at a manufacturing site just in time to be used in the manufacturing process.
Kit	An EDI software solution that has been pre-configured according to the EDI specification of a hub organization in order to simplify EDI implementation.
LAN	Local Area Network. A network of computers that enables access to the same computer software and files from all locations.
Mailbox	A file storage area where data is placed until it can be retrieved by the intended receiver.
NEX/UCS	Network Exchange UCS. Refers to EDI transaction sets used in the direct store delivery segment of the grocery industry.
Odette	An EDI standard used by the European automotive industry.
PIDX	Petroleum Industry Data Exchange. The organization which develops EDI data requirements for the petroleum industry and represent the industry regarding maintenance of the X12 standard.
Point of Sale	Also POS. A computer application that enables the seller to collect product identification information at the time of sale.
Point to Point	Refers to a type of communication where messages are sent directly from one trading partner to another without the use of a VAN.
Proprietary Data Format	A format that does not comply with X12 or EDIFACT standards. Usually a data format specific to a company or application.
Proprietary Standards	Industry specific or company specific data formats that does not comply with X12 or EDIFACT standards.
Protocol	A set of conventions between communication devices that validates the format and content of messages to be exchanged, and controls the communication session.
Quick Response	Also QR. Refers to technologies, procedures and practices used in the retail industry to eliminate supply chain waste and inefficiencies.
Re-engineering	The modification of computer applications and related procedures in order to streamline processing.
Stand-alone EDI	An approach to EDI implementation where the EDI software is not linked to computer applications.
Standard	Something established for use as a rule. Within EDI, the agreed-to format for exchanging business transactions.
TDCC	Transportation Data Coordinating Committee. The organization within the U.S. originally responsible for developing EDI and furthering its growth.
Tradacoms	Message standards for data interchange between major UK retailers and suppliers.
Trading Partner	A customer, supplier or other partner with whom business is conducted using EDI.
Transaction Set	The EDI equivalent of a complete business documents such as an invoice, a purchase order, or a remittance advice.
Translation Software	A program used to convert data to and from EDI formats.
UCC	Uniform Code Council. The organization that administers the UPC symbols and other retail bar code and retail standards.
UCS	Uniform Communication Standard. An EDI standard designed for and used by trading partners within the grocery industry.
UPC	Universal Product Code. A code that uniquely identifies a product. Used extensively in the retail and grocery industries.
VAN	Value-added Network.
VICS	Voluntary Inter-industry Communication Standard. A committee active in EDI on behalf of the retail industry. Also the name of standards (now part of X12) that were developed by that group.
WINS	Warehouse Information Network Standard. A standard developed to support warehouse applications. Now part of X12.
X12 Standards	A public EDI implementations widely used in North America. The standard incorporates many industry-related standards such as VICS, WINS, AIAG, PIDX, EIDX and UCS.
Year 2000	A set of issues pertaining to the format of dates when 19 cannot be assumed to be the first two digits of the year.

Oracle e-Commerce Gateway Views

VIEW NAME	DESCRIPTION
ECE_ADVO_DETAILS_V	This view extracts advice detailsfor the outbound Application Advice (824/APERAK) transaction.@rep:scope private@rep:product EC@rep:lifecycle active@rep:displayname Application Advice Details View@rep:category BUSINESS_ENTITY EC_APPLICATION
ECE_ADVO_HEADERS_V	This view extracts advice header informationfor the outbound Application Advice (824/APERAK) transaction.@rep:scope private@rep:product EC@rep:lifecycle active@rep:displayname Application Advice Header View@rep:category BUSINESS_ENTITY EC_A
ECE_ATTACHMENT_V	/*#* This view extracts attachment data* for the outbound Purchase Order (850/ORDERS) and* outbound Purchase Order Change (860/ORDCHG) transactions.* The attachment view is used for header, line, shipment, distribution, item and master item
ECE_CDMO_ALLOWANCE_CHARGES_V	This view extracts allowance and charges informationfor the outbound Credit/Debit Memo (812/CREADV/DEBADV) transaction.The allowance and charges view is used for both the header and line level data.@rep:scope private@rep:product AR@rep:life
ECE_CDMO_HEADER_1_V	This view extracts additional header informationfor the outbound Credit/Debit Memo (812/CREADV/DEBADV) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Credit/Debit Memo Header Attributes View@rep:category
ECE_CDMO_HEADER_V	This view extracts header informationfor the outbound Credit/Debit Memo (812/CREADV/DEBADV) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Credit/Debit Memo Header View@rep:category BUSINESS_ENTITY AR_CRE
ECE_CDMO_LINE_TAX_V	This view extracts line tax informationfor the outbound Credit/Debit Memo (812/CREADV/DEBADV) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Credit/Debit Memo Line Tax View@rep:category BUSINESS_ENTITY AR
ECE_CDMO_LINE_V	This view extracts line informationfor the outbound Credit/Debit Memo (812/CREADV/DEBADV) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Credit/Debit Memo Line View@rep:category BUSINESS_ENTITY AR_CREDIT_
ECE_CDMO_TRX_NUMBER_V	Contains the credit/debit memo number for the customer for outbound Credit/Debit Memo  (812 - CREADV / DEBADV) transaction.
ECE_INO_ALLOWANCE_CHARGES_V	This view extracts allowance and charge informationfor the outbound Invoice (810/INVOIC) transaction.The allowance and charges view is used for both header and line level data.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displ
ECE_INO_HEADER_1_V	This view extracts additional header informationfor the outbound Invoice (810/INVOIC) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Invoice Header Attributes View@rep:category BUSINESS_ENTITY AR_INVOICE
ECE_INO_HEADER_V	This view extracts header informationfor the outbound Invoice (810/INVOIC) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Invoice Header View@rep:category BUSINESS_ENTITY AR_INVOICE
ECE_INO_LINE_TAX_V	This view extracts line tax informationfor the outbound Invoice (810/INVOIC) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Invoice Line Tax View@rep:category BUSINESS_ENTITY AR_INVOICE
ECE_INO_LINE_V	This view extracts line informationfor the outbound Invoice (810/INVOIC) transaction.@rep:scope private@rep:product AR@rep:lifecycle active@rep:displayname Invoice Line View@rep:category BUSINESS_ENTITY AR_INVOICE
ECE_LOOKUP_VALUES	View of FND_LOOKUP_VALUES table.
ECE_MTL_MOV_STAT_V	Contains the movement type information for documents with EDI transactions pending.
ECE_MVSTO_DETAILS_V	This view extracts line informationfor the outbound Movement Statistics (INTRASTAT) transaction.@rep:scope private@rep:product INV@rep:lifecycle active@rep:displayname Movement Statistics Line View@rep:category BUSINESS_ENTITY INV_MOVEMENT_
ECE_MVSTO_HEADERS_V	This view extracts header informationfor the outbound Movement Statistics (INTRASTAT) transaction.@rep:scope private@rep:product INV@rep:lifecycle active@rep:displayname Movement Statistics Header View@rep:category BUSINESS_ENTITY INV_MOVEM
ECE_MVSTO_LOCATIONS_V	This view extracts line location informationfor the outbound Movement Statistics (INTRASTAT) transaction.@rep:scope private@rep:product INV@rep:lifecycle active@rep:displayname Movement Statistics Line Location View@rep:category BUSINESS_EN
ECE_POCO_HEADERS_V	This view extracts header informationfor the outbound Purchase Order Change (860/ORDCHG) transaction.@rep:scope private@rep:product PO@rep:lifecycle active@rep:displayname Purchase Order Change Header View@rep:category BUSINESS_ENTITY PO_PU
ECE_POCO_LINES_V	This view extracts line informationfor the outbound Purchase Order Change (860/ORDCHG) transaction.@rep:scope private@rep:product PO@rep:lifecycle active@rep:displayname Purchase Order Change Line View@rep:category BUSINESS_ENTITY PO_PURCHA
ECE_POCO_SHIPMENTS_V	This view extracts shipment informationfor the outbound Purchase Order Change (860/ORDCHG) transaction.@rep:scope private@rep:product PO@rep:lifecycle active@rep:displayname Purchase Order Change Shipment View@rep:category BUSINESS_ENTITY P
ECE_POO_HEADERS_V	/*#* This view extracts header information* for the outbound Purchase Order (850/ORDERS) transaction.* @rep:scope private* @rep:product PO * @rep:lifecycle active* @rep:displayname Purchase Order Header View* @rep:category BUSINESS_ENTI
ECE_POO_LINES_V	/*#* This view extracts line information* for the outbound Purchase Order (850/ORDERS) transaction.* @rep:scope private* @rep:product PO* @rep:lifecycle active* @rep:displayname Purchase Order Line View* @rep:category BUSINESS_ENTITY PO_PUR
ECE_POO_SHIPMENTS_V	/*#* This view extracts shipment information* for the outbound Purchase Order (850/ORDERS) transaction.* @rep:scope private* @rep:product PO* @rep:lifecycle active* @rep:displayname Purchase Order Shipment View* @rep:category BUSINESS_ENTIT
ECE_PO_DISTRIBUTIONS_V	/*#* This view extracts distribution information* for the outbound Purchase Order (850/ORDERS) and* outbound Purchase Order Change (860/ORDCHG) transactions.* @rep:scope private* @rep:product PO* @rep:lifecycle active* @rep:displayname Purc
ECE_PO_PROJECT_INFO_V	Contains the project level data for the the Purchase Order (850/ORDERS) and the Purchase Order Changes (860/ORDCHG) transactions.
ECE_PRIMARY_CONTACT_PHONE_V
ECE_PRIMARY_CUSTOMER_PHONE_V
ECE_PROFILE_OPTIONS	View on FND_PROFILE_OPTIONS_VL and FND_PROFILE_OPTIONS_VALUES tables
ECE_PYO_INVOICE_V	This view extracts invoices selected for payment to supportthe outbound Payment Order/Remittance Advice (820/PAYORD/REMADV) transaction.@rep:scope private@rep:product AP@rep:lifecycle active@rep:displayname Payment Order/Remittance Advice I
ECE_PYO_PAYMENT_V	This view extracts payment informationfor the outbound Payment Order/Remittance Advice (820/PAYORD/REMADV) transaction.@rep:scope private@rep:product AP@rep:lifecycle active@rep:displayname Payment Order/Remittance Advice Payment View@rep:c
ECE_RCO_ADDRESS
ECE_RSU_CONTACT
ECE_RSU_NOCONTACT
ECE_SPSO_HEADERS_V	This view extracts header informationfor the outbound Planning Schedule (830/DELFOR) transaction.@rep:scope private@rep:product CHV@rep:lifecycle active@rep:displayname Planning Schedule Header View@rep:category BUSINESS_ENTITY CHV_PLANNING
ECE_SPSO_ITEMS_V	This view extracts item informationfor the outbound Planning Schedule (830/DELFOR) transaction.@rep:scope private@rep:product CHV@rep:lifecycle active@rep:displayname Planning Schedule Item View@rep:category BUSINESS_ENTITY CHV_PLANNING_SCH
ECE_SSSO_HEADERS_V	This view extracts header informationfor the outbound Shipping Schedule (862/DELJIT) transaction.@rep:scope private@rep:product CHV@rep:lifecycle active@rep:displayname Shipping Schedule Header View@rep:category BUSINESS_ENTITY CHV_SHIPPING
ECE_SSSO_ITEMS_V	This view extracts item informationfor the outbound Shipping Schedule (862/DELJIT) transaction.@rep:scope private@rep:product CHV@rep:lifecycle active@rep:displayname Shipping Schedule Item View@rep:category BUSINESS_ENTITY CHV_SHIPPING_SCH
ECE_STAGE_LEVEL1_V	ECE_STAGE_LEVEL1_V  is used in ECERNCON.fmb to retrieve the
ECE_STAGE_LEVEL2_V	ECE_STAGE_LEVEL2_V  is used in ECERNCON.fmb to retrieve