The Oracle Prodigy: fbdi

Showing posts with label fbdi. Show all posts

When to Use FBDI or WebServices in Oracle Fusion Applications

I've been working through a really tough task recently and it involves updating Customer Data, more specifically to Contact Responsibility and Customer Class Profiles. I've had a lot of "mistakes"/shortcomings working on this task and I'd like to share this with you, so you can hopefully avoid it in the future.

This articles discusses when to Use FBDI or WebServices in Oracle Fusion Applications:

File-Based Data Import (FBDI)

FBDI is faster because it's executed from inside the Oracle Cloud Server and can do Bulk Updates/Inserts.
Troublesome to populate numerous Fields and Worksheets in the Spreadsheet.
CSVs can really ruin your number and date formatting.
Need to Extensive Effort to make sure Data Preparation is Accurate.
Use FBDI when updating data in BULK (thousands of rows)
DO NOT, use FBDI when updating data for Manually-Created Customers, because they do not have Original System References. This is an important field in the Customer FBDI template for some reason. This is the main point of my suffering for the past 2 months. :P

WebServices (SOAP or REST)

Specifically, I've only had experience with SOAP and i'm admittedly still not that good at it. But below are some tips that I can share based on what I've experienced so far and what I've researched on.

Strongly consider using Web Services for Integrations between Oracle Fusion Applications and other platforms since Oracle Fusion already has the pre-built ERP Integration Service that can be used to perform outbound or inbound ETL.
Consider using Web Services when you have small amounts of data to Update as WebServices aren't designed for Bulk Updates.
Web Services are a row-by-row update and are triggered from either your PC (using a Software such as SOAPUI or ReadyAPI) or from a separate Server from Oracle Cloud.
This means you would need constant network connection to process all the data, especially if you'll invoke the Web Services from your own machine.
Since Web Services are row-by-row, it's understandably slower than FBDI.
Would entail less data preparation compared to FBDI as you would only need to provide the mandatory tags, unlike in FBDI wherein you have to populate multiple worksheets.

In summary, I used to think FBDI was the way to go when doing Bulk Updates in Oracle ERP Cloud, but now, I think it's really troublesome and entails a lot of unnecessary work. I would strongly recommend that you first verify the data you'll be updating/inserting/deleting, before pursuing FBDI.

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/

Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)

Overview of Oracle Accounting Hub Cloud Rapid Implementation Approach

The rapid implementation approach is a new approach that has been introduced for the purpose of registering source systems quicker with the use of spreadsheet templates, where you will populate the details based on which the registration of the third-party systems will take place.

This is especially useful if you have numerous third-party application systems and you would like to register them into the Accounting Hub Cloud solution. It offers a simplified, streamlined source system registration and automation-ready transaction upload to Financials Cloud.

Steps in the Rapid Implementation Approach

Source System Registration. First, you need to figure out which are the third-party systems that you want to use for the purpose of registration into the Oracle Accounting Hub Cloud. And within the application, you have an option to download a spreadsheet template. You can populate the information into the respective sections of the spreadsheet template. And based on the data that you will enter, when you upload that into the application, the system will register a source system automatically.
Upload Transactional Data. You can upload transactional data for the registered Accounting Hub Cloud subledgers in a CSV format. Optionally, you can automate the process from uploading to create accounting journal entries with the help of web services as well. This actually increases control of financial and management reporting requirements because you have a streamlined, smooth approach to bring the transactional data from the various systems into the Accounting Hub Cloud solution.
Accounting Transformations. To generate the accounting entries against the transactional data that we are bringing from the various systems, we need accounting rules. And those accounting rules are basically designed with the help of a solution called accounting transformations. Accounting transformations will basically help you to set up your accounting methods which are containers for all the accounting rules and other related attributes based on the journal entry that's supposed to be created.

When you register a source system, you will need to establish an event model under that. Once a source system has been registered and an event model has been established, you will design an accounting method. All of them will be utilized. And then you will load the transactional data by using those components.

Finally, these transactional data will be converted into journal entries and they are then posted into GL to update the balances in the Essbase cube. This allows your organization to run Financial Statements and reports using the Financial Reporting Center, the intended primary user interface for accessing all the journal ledger-related reports.

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/
Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)

Overview of Revenue Management in Oracle Fusion Applications

What is Revenue Management?

Oracle Revenue Management Cloud is a centralized, automated Revenue Management product. It enables you to address revenue as defined in the ASC 606 and IFRS 15 accounting standards that came in 2018.

Oracle Revenue Management Cloud is an application that enables you to manage customer contracts and performance obligations easily so that you can address the revenue mandates that are in these new accounting guidelines.

There used to be differences between ASC and IFRS as to how revenue was recognized. But now, the two standards have converged. So the rules for recognizing revenue are now very similar between these two standards. More information can be found on a separate article: Overview of the ASC 606 and IFRS 15 Revenue Management Standards.

Features of Revenue Management

Revenue Management allocates revenue according to the published guidelines for the ASC 606 IFRS 15 standard.
Identifies and creates customer contracts and performance obligations in those contracts based on both seeded and user-defined rules.
Has a rule-based engine called SubLedger Accounting (SLA) that creates journals for Revenue Management and send them over to either Oracle Fusion Cloud GL or externally, to E-Business Suite GL.
Books revenue when performance obligations are satisfied. It processes revenue independently of billing.
Simplifies and automates revenue accounting across product bundles
The centralized dashboard to be your system of record for revenue data.
Has Pre-defined integration with Oracle E-Business Suite
Extract, Transform, and Load (ETL) functionality and Spreadsheet integration.
Several core-defined Revenue reports using BI Publisher (BIP) and Oracle Transactional Business Intelligence (OTBI), and also allows users to create their own reporting objects

Key Terminologies in Revenue Management

Customer Contract in Revenue Management is not in terms of a physical legal contract, but rather an accounting contract.
Performance Obligation is the promise to the customer that needs to be fulfilled so revenue can be recognized.
Performance Satisfaction is the fulfillment of a Performance Obligation. Performance Satisfaction is measured in terms of accounting periods in terms of percentage or quantities.
Inventory items are products and services associated with price that your organization sells. This is an important data point in Revenue Management because this will be the basis for standalone selling price and the allocation of the transaction price.
Standalone Selling Price (SSP) is the price of a component of a contract if you purchase it separately.
Allocation determines the transaction price allocated to various performance obligations in the ratio of SSP. This is based on a relative method of allocation.
Transaction Price is the amount of consideration that is expected to be received for the transfer of goods or services. This could be fixed or variable. These are the amounts that are recognized as revenue when the performance obligation is satisfied.

Overview of Revenue Management Cloud

Below is a quick overview of Revenue Management Cloud, including the five steps to revenue recognition and also integration. So you can see integration within other Oracle Cloud products and with products outside of the Oracle Cloud as well.

Revenue Management Cloud can integrate with third-party solutions, including Oracle E-Business suite (EBS). A number of EBS applications such as Receivables, Contracts and Order Management have data that's relevant to this new revenue recognition process. You can use the predefined integration with EBS to bring that data over to the Cloud.

In addition to that, you can integrate to third-party non-Oracle applications. We provide File Based Data Import (FBDI) templates to allow you to use the template, populate them, generate a data file that you can then load to the Oracle Cloud. Or you can also even create a custom program from your third-party non-Oracle application.

In the diagram, there is also inbound integration with fusion receivables and project financial management. Also important is the outbound integration here to the Fusion Cloud General Ledger, or externally, to Oracle EBS GL. This means that a subledger journal is going to be generated and transferred over to GL. Once the Journal Entries have been posted, then the The balances cube (called the "Essbase cube") will be updated and you can create financial statements for your organization.

To know more about these Integrations, check out separate articles on Inbound Integration with Revenue Management Cloud and Integrating E-Business Suite with Oracle Revenue Management Cloud.

In the middle of the Diagram, you can see the five steps to revenue recognition. Below provides a summary of the five steps to revenue recognition:

Five Key Steps to Revenue Recognition

1. Identifying customer contracts. The first step in the process is to identify customer contracts from transaction lines. These contracts can be identified based on common attributes in transaction lines (i.e. Customer Name, Extensible Attributes, etc.). Contract Identification Rules are used to identify these common links together and group them in a contract. The Identify Customer Contracts job set creates the accounting for each stage of the Revenue Recognition Process.

2. Identifying Performance Obligations in those contracts. As mentioned in the terminologies, Performance Obligations are the promises you made to the customer. These are goods or services that you promise to deliver in exchange for payment. Performance Obligation Identification Rules are used to Identify these contractual obligations based on common links in the contract.

3. Calculating transaction Prices. Transaction price is price of the contract or deal. Think of the amount of expected consideration that your organization is going to receive for transferring those goods or services. The amount what you expect to receive from the customer after delivering the service or delivering the product.

4. Allocate the transaction price using Standalone Selling Prices. Determines how much revenue is going to be allocated for each service and product based on the Standalone Selling Price.

5. Recognize the revenue when that performance obligation has been satisfied.

Revenue Management Process Flow

Before you can effectively use Revenue Management, there are a number of items you would have to configure first, such as registration of source systems, set the standalone selling prices, set the default accounts to use, etc.

The Diagram below shows the steps to configure Revenue Management:

1. Extract Transform and Load. You would need to register data sources and source systems in Revenue Management to be able to import transactions from other applications. You can import these data using FBDI templates and load them into the Universal Content Manager (UCM) Server, before going into the Revenue Management Cloud tables.

2. Manage Standalone Selling Prices. You need to populate prices in the system to allocate the transaction price of a customer contract. That customer contract is going to products and/or services and each of those products and/or services need to have a standalone price. Revenue Management is going to use these standalone selling prices as the basis to allocate revenue. You can run processes in Revenue Management to calculate the prices or you can load them from a spreadsheet template.

3. Five Steps to Revenue Recognition. The Five steps to revenue recognition is where the actual process takes place. As previously mentioned, the five steps is to identify the customer contract, identify performance obligations, calculation of the transaction price, the allocation of that transaction price, and finally, recognize the revenue when you have satisfied the performance obligations.

4. Accounting. With the use of the SubLedger Accounting Engine, we will create accounting journals based on rules we have set. These rules are created Component by component, there are rules that are going to impact how the description of the journal looks like, what the journal lines are going to have, which accounts, which descriptions, etc. Create Accounting is the process that is going to look at these rules and create the journal. Once the journal is created, it can be sent to GL, either Cloud GL or E-Business Suite GL. Financial statements such as balance sheet reports, and income statement reports can then be generated from the Essbase Cube.

A Working Example of Revenue Management

Below is an example a contract with a telecommunications company:

Item	Standalone Selling Price	Satisfaction Start Date	Satisfaction End Date	Revenue Recognized
Smart Phone	490.68	07/01/2016	07/01/2016	490.68
Voice Plan	588.82	07/01/2016	06/30/2017	50.01 (1st Month)
Data Plan	392.5	07/01/2016	06/30/2017	33.34 (1st Month)

The customer contract is going to include these inventory items: a smartphone, a voice plan service and a data plan service. Each has a defined standalone selling price, which is key to allocate the revenue properly. There is a time frame on when we can recognize revenue.

As for the Smart phone, we will recognize the revenue immediately, as the performance obligation has been fulfilled right away. For the Voice and Data plan, revenue will be spread out in terms of when the performance obligation will be fulfilled. We cannot recognize revenue immediately because we haven't completely fulfilled the service yet.

At contract inception, you are going to be seeing accounting entries, even prior to billing. So prior to billing, there will already be accounting entries generated under the new ASC606/IFRS 15 standard.

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/

Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)

Integrating E-Business Suite with Oracle Revenue Management Cloud

In this Article, you will gain an understanding of how Oracle E-Business Suite integrates with Revenue Management.

Before you can perform more work on these integrations, You need to have reference data in place such as enterprise structures, legal entities, ledgers, business units, Parties, Customers, customer accounts, customer account sites and inventory items in the Oracle Cloud. And you would need to read about Integrating with Revenue Management in Oracle Fusion Applications.

There are predefined programs in E-Business Suite called that extract data from EBS and bring it over to the Cloud. Below programs are run sequentially:

Extract Revenue Basis Data program
Create Billing Data program
Create Revenue Management Data export file

The file created by the "Create Revenue Management Data export" program gets into the Cloud via the Universal Content Manager, and from there data gets pushed into the Revenue Management interface tables. Data will be validated and create customer contracts in the Revenue Management base tables by running a process called "Identify Customer Contracts".

Identify Customer Contracts will create contracts based on rules. These rules can be predefined or defined by your organization. Once that has been completed, Revenue Management can now perform the five steps to revenue recognition.

There is out-of-the-box integration with the below E-Business Suite modules

Order Management
Service Contracts
Receivables

These E-Business Suite modules have pre-built integration because they contain information relevant to Revenue Management Cloud. Service Contracts would contain contract information, Sales orders in Order Management, and invoices and credit memos information in Receivables.

Required steps to configure E-Business Suite integration with Revenue Management:

Apply patches provided by Oracle (25505159 and
Configure system options in EBS Receivables to add a new tab.
Profile Option "AR: Source System Value for Revenue Management"
Configure business events using Fusion Web Services
Set up EBS Secure Socket Layer (SSL) for consuming Fusion services

For steps 1, 4 and 5, go to Oracle Metalink Support and download the appropriate patches and notes on how to implement these steps. The patches are applicable for releases 12.1.3 and 12.2.x.

After that patch is applied, as we can see here, you're going to see a new tab shown below:

In Setting the profile option, the name of the profile option is "AR: Source System Value for Revenue Management" and the value that you want to set the option is "EBIZ". This is a mandatory setting in order to extract revenue basis data from EBS and bring that over to Oracle Revenue Management Cloud.

Once everything has been configured and set, you may proceed to extract revenue data by running a process in EBS called Extract Revenue Basis Data. Extract Revenue Basis Data is a request set that will run three sub-processes that does the following:

Extract Revenue data
Extract Billing data.
Create a data export file that will be sent to the Universal Content Manager

After you have run an import process to transfer files into the UCM, the next process that needs to take place is Load Interface File for Import. This process transfers setup or transaction data files from a user-specified location to the interface tables. The interface tables we are discussing here are the Revenue Management interface tables.

For more full-detailed Tutorials and Tips, check out #TheOracleProdigy at https://lifeofanoracleprodigy.blogspot.com/
Follow The Oracle Prodigy on Facebook (https://www.facebook.com/theOracleProdigy/) and Twitter (https://twitter.com/D_OracleProdigy)

Integration with Revenue Management in Oracle Fusion Applications

This article discusses the Inbound Revenue data Integration with Revenue Management in Oracle Fusion Applications. Below are the Objectives of this Article:

Understanding inbound integration options with Revenue Management
Understanding how Oracle E-Business Suite integrates with Revenue Management
Understanding how third party applications integrate with Revenue Management
Understanding Outbound integrations with Revenue Management

Before you can perform more work on these integrations, You need to have reference data in place such as enterprise structures, legal entities, ledgers, business units, Parties, Customers, customer accounts, customer account sites and inventory items in the Oracle Cloud. Also, you would need to create a source system and item relationship called Spoke System Relationship.

Defining a Source System

This is part of the prerequisites for integration. Go to the task "Manage trading community source system" and click on "Create" and click on the option "Enable for Items" and also "Enable for Trading Community Members" because we're going to be loading inventory item information as well as customer information into the cloud.

Defining a Spoke System Relationship

A spoke system relationship is a relationship between items and a source system. This is required when integrating with third-party applications. To define a spoke system relationship, you would need to first Define Master Data.

To find out more about Defining a Spoke System Relationship, check out a separate article on Creating Items and Their Spoke System Relationship in Oracle Fusion Applications.

Defining Master Data means that you need customer and inventory item data loaded into Oracle Fusion before you can do integrations. There are predefined templates to upload customer information and import or update inventory items. Once done, you would need to register the source of the integration, called a Source System.

Prior to Performing a third-party or spreadsheet integration, you must register the source system so that you can then bring data into the Oracle Cloud and over to the Revenue Management interface tables. The Steps to Registering a Source System are:

Create a source system within the Trading Community Model
Import a source system reference file from a Spreadsheet

Inbound Integration to Revenue Management Cloud

There are multiple ways to bring data into Oracle Revenue Management Cloud. As mentioned, it can be through an FBDI template, or the pre-defined integration with E-Business Suite, or a custom program. The entry point for all solutions would be the Universal Content Manager (UCM).

Integration with E-Business Suite

There is out-of-the-box integration with the below E-Business Suite modules

Order Management
Service Contracts
Receivables

These E-Business Suite modules have prebuilt integration because they contain information relevant to Revenue Management Cloud. Service Contracts would contain contract information, Sales orders in Order Management, and invoices and credit memos information in Receivables.

There is a predefined program in E-Business Suite that extract data from EBS and brings it over to the Cloud via the Universal Content Manager. In turn, the UCM will populate the interface table and will create contracts in Revenue Management Cloud based on rules. Note that there are required steps to configure E-Business Suite integration with Revenue Management.

For more detailed information on Integrating E-Business Suite with Oracle Revenue Management Cloud, check out a separate article: Integrating E-Business Suite with Oracle Revenue Management Cloud

Integration with other Oracle Fusion Cloud Modules

Oracle Revenue Management also tightly integrates with other Oracle Cloud applications such as Fusion Receivables, Cloud Project Financial Management Contracts since both of these applications contain data that's going to be relevant to the new revenue recognition standard.

For Cloud Receivables, source documents such as invoices, credit memos will be relevant to Revenue Management, while for Project Financial Management, it would be documents like contracts, warranties, etc.

There is a pre-defined process called the Extract Revenue Basis Data from Oracle Fusion Applications that will extract data from the other modules and populate the interface tables. After the interface tables have been populated, a process called "Identify Customer Contracts" needs to be run to validate that data and identify customer contracts, the same process used for E-Business Suite.

Setups for Revenue Management Integration with Oracle Cloud applications

There are some required configuration in the page "Manage System Options for Revenue Management". You would need to configure Source Document Types for both Receivables and Project Financial Management. Source documents are documents such as warranty contracts, specific types of invoices, or credit memos, etc.

You would need to specify revenue clearing account for each Source Document Type to identify the default accounting combination. Also, we see extraction start date. This indicates that starting on this date, the data will to be extracted from the Fusion applications and into the interface tables to creating customer contracts.

Additionally for AR, you need to configure Oracle Fusion Receivables Transaction Sources because every single invoice, credit memo, debit memo that you create in Receivables is associated with a transaction source.

Processing Historical Data

It will be important to load historical revenue and billing data for iterative modeling and comparative analysis. In the Manage System Options page, you will need to provide the start date for that particular integration to indicate how far you are going to integrate that source data for modeling.

The revenue standard was effective January 1, 2018, but you might make a decision to go back two years, or three years for modeling and comparative analysis. You can bring that data on or after January 1, 2014 from the E-Business Suite ERP or Financials Cloud ERP. You can not really bring that data over prior to this date.

Spreadsheet Integration using File-Based Data Import

Oracle Fusion has a number of templates that can be used to bring data over into Revenue Management from third-party applications with the use of File-Based Data Import (FBDI) templates. They allow you to bring revenue basis and billing data into the Cloud and over to the Revenue Management interface tables.

If you decide to go with the FBDI template, there are separate FBDI templates you need to use for revenue data (Revenue Basis Data Import) and billing data (Billing Data Import). The template will contain source header data from the source document, sales order, the warranty contract, and sublines that impact satisfaction information. You can download the FBDI template from Oracle Documentation: File-Based Data Import for Financials.

The Revenue Basis Data Import template will have three tabs, each one for different types of data:

Header Data (VRM_SOURCE_DOCUMENTS)
Line Data (VRM_SOURCE_DOC_LINES)
Satisfaction event information (VRM_SOURCE_DOC_SUB_LINES)

While the Billing Data Import only has one tab (VRM_BILLING_LINE_DETAILS).

You need to run an import process to get that CSV data file into the Cloud, called "File Import and Export". After the import process takes the data into the UCM server, run the process "Load Interface File for Import" to populates the Revenue Management interface tables.

This will trigger the process "Validate Customer Contract Source Data" that will validate the data in the inteface. Next, you would need to run "Identify Customer Contracts" to create customer contracts from the Revenue Management base tables.

Custom Program using a SOAP Web Service

If you decide to go with a custom program, you will need two APIs for this integration, the Revenue Basis Data Import API and the Billing Import API.

You will have to utilize the Web Service API to place a file in the UCM server. After the file is in the UCM server, you run the same process to load the interface tables ("Load Interface File for Import") and proceed to run another process to automate the five steps to revenue recognition ("Identify Customer Contracts").

Error Correction for Integrations

There is a spreadsheet template that Oracle provide that allows you to not only correct import errors but check for errors. This function is called "Correct Contract Document Errors in Spreadsheet" and is found by navigating to the Revenue Management work area.

Outbound Integration

With the use of the subledger accounting engine, we are going to generate journals in Revenue Management. Those journals will end up either in a target General Ledger. If your target General Ledger is Fusion GL, We're not going to do any outbound transactions because the journals are going to stay within the cloud.

However, if you are using EBS, what will happen here is that you will run Create Accounting as you normally would do. A data file will be created and sent over to the Universal Content Manager, then you then run a process to import those journal entries from the cloud and into E-Business Suite. This data is going to go to the GL interface tables in EBS. You can then run an import process that takes the data to the EBS GL production tables. It creates the journals. After you create the journals, then you can post those journals in EBS GL.

There are certain setups you have to do in the cloud to allow for this outbound integration with EBS. And so here you see the name of the task, Manage Subledger Application. Pick the desired application ("Revenue Management") and choose the application you'll transfer the Ledgers to. There is an option to transfer to EBS. You have to go with this option here to transfer ledgers externally to EBS.

Overview of Payable Transactions in Oracle Fusion Applications

This article will discuss an overview of Payable Transactions in Oracle Fusion Applications. Before you can create Payable transactions in Oracle Fusion Applications, make sure all configurations are complete. Check out a separate article "Overview of Payables Configurations in Oracle Fusion Applications" for more information on the configurations.

Once everything is configured, you may proceed to create payables transactions in multiple approaches. There are four approaches to create a Payables Invoice:

Manual

Manual Invoice created from the Payables Work Area - allows you to create invoices by using an invoice work area within the application. There is a dedicated user interface where you can navigate and you can start recording your invoices by capturing header level information, line level information, and distribution level information.
Integrated Imaging
Manual Invoice created from Spreadsheets - Oracle provides functionality to upload invoices in bulk using Spreadsheets with the use of File-Based Data Import (FBDI) templates. This allows the user to be more efficient in getting their invoices in the application. Check out the video demonstration below on how to create invoices from an Excel Spreadsheet:

Self-Service

Matched Invoices - This involves a process where you can match the invoices against purchase orders or maybe against receipts, depending on what type of matching level you are going to use.
Unmatched Invoices - Invoices that are not matched to purchase orders can be routed to workflow approval rules that you configure
Advanced Shipment Notices (ASNs) - A document which allows you to generate invoices automatically, which will be created when supplier create an ASN for drop shipments.

Automated

Integrated Imaging - This will use Oracle Integrated Invoice Imaging solution to support integrated imaging of scanned invoices for paperless processing and routing. It then uses the import process to match to purchase order or receipts. If it's a PO based invoice, you can view invoice information including invoice status, installments, holds, payments, and applied prepayments against these invoices as well. You can also drill down to the original purchase order or receipt if required. And if errors are found during the process, manual intervention may be required to resolve the import errors.
Self-Billed - In the application we have a feature called Evaluated Receipt Settlement, also known as Pay-On-Receipt. You can use the Pay On Receipt feature to help you in automatically generating an invoice the moment you create a receipt against a purchase order. You can use the predefined jobs, schedule them, and enable your supplier for Pay On Receipt functionality. When you do that, the moment you will create a receipt against a purchase order, based on the scheduled jobs system will automatically keep on creating an invoice against those receipts which you can access from the Payables application. Apart from that, we have also got something called Return to Supplier feature, or sometimes called as Return to Vendor (RTV). This basically helps you in automatically generating a debit memo the moment you create an RTV transaction in the Purchasing application. The moment you create an RTV transaction, that becomes the base to automatically generate a debit memo in the Payables application.
Expense Reports - Expense reports are Invoices created from Employee Expenses that need to be reimbursed to them. It can be either done electronically through their registers bank accounts or in the form of a physically printed check. Whenever the expense reports are approved by both the manager as well as the Payables team, they become eligible for import into the Payables application. There is a job which you need to submit to export the expense reports from the Expense application into the Payables application, because from the Expense application you cannot directly process the payments. The type of invoice that is used for these expense reports is now known as Payment Requests. Whenever you will export the invoice from Expenses to the Payables application, you need to search with the invoice type as Payment Request.
Customer Refunds - Similar to Expense Reports, customer refunds can be triggered whenever there are any credit balance in Receivables that require a refund. Once approved, they will flow to Payments as Payment Requests.
Inter-company invoices - An intercompany transaction that requires invoicing is imported to Payables for payment processing for internal suppliers

Electronic

Business to Business (B2B) Web Service - Used to import invoices in an electronic format via a Web Service

Check out a separate article for more information on how to create Expense reports: Creating an Expense Report in Oracle Fusion Applications or check out the below step-by-step video demonstration:

Create and Upload Bank Statements from a Spreadsheet in Oracle Fusion Applications

Oracle allows the import of non-standard bank statement formats using just a Excel spreadsheet. You just have to populate the spreadsheet with the correct data and there's a button that allows you to generate a CSV file that you would then load to the cloud.

From the Welcome Springboard, Navigate to the Cash Management application and go into the Bank Statements and Reconciliations work area.

Click on the Task Pane and select the function “Create bank statements in Spreadsheet”:

The template includes instructions for the generation of the CSV file after the population of data being imported. There's a separate tab for bank statement headers, a statement balances, statement balance availabilities, statement lines, etc.

To find out how to Manually create Bank Statements, check out a separate article:
Manually Creating a Bank Statement and Reconciling against a Receivable Transaction

For more information on Cash Management and Bank Statements, check out this separate article: Overview of Cash Management in Oracle Fusion Applications

Create Journals though Spreadsheet in Oracle Fusion Applications

You can create Journal Entries in Oracle Fusion applications in two ways.
You can create it manually one-by-one or by Bulk through Excel Spreadsheets using the File-Based Data Import for Financials Cloud (commonly known as FBDI). For the manual process, you may refer to the tutorial found here: Create GL Journal Entry in Oracle Fusion Applications. For the bulk process, you first need to install FBDI on your Local PC and ensure you have the appropriate Microsoft Office version installed. For this article, we will use Microsoft Office o365 or 2016 and FBDI version 11.1.1.9.3 (build 5.0.2.18097).

Go to General Accounting > Journals

Click on the Task Pane and choose Create Journal in Spreadsheet

Depending on the browser, you will be asked to either open the file in Microsoft Excel (for Mozilla) or it will download the file on your Local PC right away (for Chrome). Either way, proceed to open the file in Microsoft Excel:

Once the file has been opened in Excel, click on "Enable Editing" and proceed to confirm that you want to Connect:

You will be prompted to login using your Username and Password. Use the Username and Password that has the appropriate access to the Ledger you want to import transactions in.

Once login has been confirmed, the spreadsheet will now show the appropriate fields and you can proceed to input the Ledger Header and Line Details. The fields below in Red are the recommended fields you must populate:

For the Chart of Accounts (CoA), You may manually input the values or double-click on the field to select from the List of Values (LoV):

If you've completed entering the necessary information, proceed to click on "Submit" from the Ribbon. You will be prompted to select an option to either:

Save the data to the GL_INTERFACE table without importing into the GL Base Tables (GL_JE_HEADERS, GL_JE_LINES, etc.)
Save the data to the GL_INTERFACE table and subsequently import data into the GL Base Tables
Save the data to the GL_INTERFACE table and subsequently import data into the GL Base Tables and process them for Posting

Once the process has completed successfully, the status will show as "Row inserted successfully" in the "Row Status" column in the Spreadsheet.

On the other hand, Error Lines will show as "Error" and you may update any incorrect data and resubmit to try again.

To verify the uploaded data, navigate to the Springboard > General Accounting > Journals then click on the Task Pane and select "Manage Journals".

You may use the Ledger name you've provided to quickly search for your Journal Batch:

Below is a quick video demonstration on the topic above: