Overview of the Build Phase in Implementing Accounting Hub Cloud

The build phase is where you will actually register the source systems for Accounting Hub Cloud. You have the flexibility to register source systems with the help of predefined spreadsheet templates. The source system is the place where you will get all the information about the transactions that you want to bring into the Accounting Hub.


Before you start bringing the transactions, you must register the source systems and their underlying event models. And for that, you will use the Excel templates to populate the values for the source system name and columns that will be used for registering your transaction objects used to store the transactional data from the source systems.

Underneath the source system, you will establish an event model that will carry your process categories, event classes, and event types. This will also carry all the column details that are required for storing the values at the header-level values and line level values. This means when you use this template, you will specify the entire event model and the other attributes that are required for generating your accounting entries.

When the data is uploaded using that spreadsheet template, it will register a transaction object. A transaction object is a database table which is used to store the header-level data and the line-level data. You will have to analyze what attributes you want to bring from the source system. And you need to have a column for each one of those attributes in your transaction object.

For example, in the source system, you have many important fields like such as customer name, customer number, loan number, loan reference number, sales person, currency amount, etc. To bring this information into Accounting Hub, these fields need to be populated in the rapid implementation spreadsheets. When the data is loaded into the application through the upload mechanism, the system will register a transaction object and build the respective columns. Whatever fields you will specify on your spreadsheet templates, each one of those fields will be considered as the sources. And they will become part of your transaction object.

You can use these sources for the purpose of designing your description rules, account rules. Use those sources when you are defining your journal line rules to identify what is your debit line, what is your credit line as well.

And then you must verify the source system information. When the source system has been created, you will have to figure out the accounting attributes that are associated with those sources or with those objects. And you must figure out the source assignments as well. So that is going to be your first step.

Accounting Hub always works based on a three-model definition. The three models are called the data model, the event model, and the accounting model.

Data Model. The data model will be generated based on the source system registration process. In the spreadsheet template, provide the source system name, the transaction objects and specify the fields that will be used as columns. When you load the spreadsheet into the system, system will establish a data model.

Event Model. Simultaneous with the Data Model creation, the system will also establish an event model. When you provide the information on the spreadsheet template, you will also specify the event class and the respective event types that will be part of your event model. This process of registering source systems will help you in creating a data model and an event model.

Accounting Model. Creating the Accounting Model is the time when you will actually configure your accounting rules. Here, you will manage the information based on the transaction object data that has been created as part of the data model and the event model.

And finally, once your three models are in place, then you can start bringing the transactional data from the source system and upload that into the application either by using the spreadsheet templates or by automating the process using the predefined web services.

How can you Register a Source System?



The spreadsheet integration upload process accelerates the time from implementation and testing to production. It's a faster way of registering your source systems and helps us in registering our source systems by generating the transaction objects to the spreadsheet upload process.

After completing the source system transactional flow analysis, Go to the Setup and Maintenance work area, you will search for a task called Create Subledger Application Setups in Spreadsheet. When you go to that task page, you will get a button on that page called Download Setup Template. When you click on that button, a pop-up message will appear to open the spreadsheet template. Open it, and then you can start populating the data.

Populate the data into the spreadsheet template with the following guide questions to establish your data and event models:
  1. What is the name of the source system?
  2. What is the event class name?
  3. What are the event types that you want to use?
  4. What are the columns that will be used to store the data at the header level?
  5. What are the columns that will be used to store the data at the line level?
Then you must validate the spreadsheet content once the data has been populated in each of those fields. You will generate the zip files. And then you will upload the zip files into the application. And finally, once the process gets over, you will verify whether your source system has been created or not.

For a full-detailed tutorial on Creating Custom Subledger Application Setups using a Spreadsheet, check out a separate article: Overview of Creating Custom Subledger Application Setups in Spreadsheet

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)

No comments:

Post a Comment