The General Ledger (GL) setup information in Merchandising provides essential information that is used in the GL integration process. For every ledger or set of books that Merchandising will be posting to in a GL, a record needs to exist on this table. These records are used in populating data on journals posted from Merchandising and Sales Audit. The data on the table also provides some controls to processing in Merchandising. This table is typically populated at implementation, but as a business changes, records may be added or deleted, or some of the data may also change over time; however the data on the table is usually fairly static.
All of the updates that can be made for GL setup are done through spreadsheet download and upload processes, which are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add or update records, select the template type of Financial Control from the Download Data screen and then the template FIF GL Setup. Click the Download button and, when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice.
To add a new GL Setup record, select the action type of Create on the GL Setup tab. Next, enter the Set of Books ID, a description for the Segment 1-10 values, values for Category ID, Deliver To and Destination Ord ID. Also add a Period Name, a description for the Ledger or Set of Books, the Currency for that Ledger/Set of Books and values for Category and Source. The Category and Source are typically set to ”Oracle Retail”, but can be varied if there is a desire to have different values shown in the GL Journals generated from Oracle Retail. The Category ID, Deliver To and Destination Ord ID values are required, but drive no processing so a default value of 1 can be entered.
If you would like to update existing GL Setup records, then a similar process will be followed to that described above for entering new GL Setup records. First, download the spreadsheet, and then find the GL Setup combination that you want to update. In that row select the action type of Update, and then update the one or more of the records in the spreadsheet.
If you wish to delete a GL Setup record because it is not used by your business any longer, then a similar process will be followed to that described above for entering or updating GL Setup records. First, download the spreadsheet, and then find the GL Setup record that you want to delete. In that row select the action type of Delete, and then update the one or more of the records in the spreadsheet.
For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, you'll again select the template type Financial Control and the template FIF GL Setup. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
The General Ledger (GL) cross reference information in Merchandising provides essential information that is used in the GL integration process. The records that are included in this process provide the basis for mapping Merchandising Stock ledger information to the GL to create journals in terms of the GL structure. From the Merchandising perspective, the source data has the following data elements that identify what the information is from a retail perspective: Set of Books, Location, Department, Class, Subclass, Transaction Code, Cost or Retail, and for some transaction codes a Transaction Reference Number. Each combination of those data elements from the retail side will need to be mapped to a set of GL accounts segments for both a debit and a credit. How many segments need values and what those values are will depend on how the GL has been setup.
While a record should exist for every combination of retail data elements where you expect transactions to exist, the mapping can be done at a higher level than subclass/location level. If for example, all subclasses within a department/class will have the same mappings, then rather than set up a record for each subclass, a single record for the department/class can be entered with "-1" for the subclass. Using -1 can be done for subclass, class, department, location, and transaction reference number.
All of these updates that can be made for GL cross references are done through a spreadsheet download and upload processes, which are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add or update GL cross reference records, select the template type of Financial Administration from the Download Data screen and then the template GL Cross Reference. Optionally, you can download a subset of records by using the filter criteria, which includes department, set of books and location. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice.
To add a new GL cross reference record, navigate to a blank row in the GL Cross Reference tab and select the action type of Create. Next, enter the Set of Books ID, the Department, Class, Subclass, Location, Tran Code for the mapping. Also, indicate whether the value in this mapping will represent cost or retail in the Cost/Retail column. For certain Tran Codes, you will also need to enter a value for Tran Ref No. The transaction codes which require this mapping are:
Purchases (20) – the reference value here will either indicate a record for the merchandise on a PO receipt or the values of the landed cost components for the PO receipt
Non-COGS Stock Adjustments (22) – the reference value will represent the reason for the adjustment
COGS Stock Adjustments (23) – the reference value will represent the reason for the adjustment
Intercompany Transfer In (37) – the reference value will represent the "from" location on the intercompany transfer
Intercompany Transfer Out (38) – the reference value will represent the "to" location on the intercompany transfer
Work Order Activity – Update inventory (63) – the reference value will represent the work order activity ID
Work Order Activity – Post to Financials (64) – the reference value will represent the work order activity ID
VAT In (87) – the reference value will represent the tax code
VAT Out (88) – the reference value will represent the tax code
Values will also need to be added in the Debit Account and Credit Account fields. Depending on the number of GL segments being used, values will also need to be entered into the Debit Segment and Credit Segment fields.
If you would like to update existing GL Cross Reference records, then a similar process will be followed to that described above for entering new GL Cross Reference records. First, download the spreadsheet, and then find the GL Cross Reference combination that you want to update. In that row select the action type of Update, and then update the one or more of the records in the spreadsheet.
If you wish to delete a GL Cross Reference record because it is not used by your business any longer, then a similar process will be followed to that described above for entering or updating GL Cross Reference records. First, download the spreadsheet, and then find the GL Cross Reference combination that you want to delete. In that row select the action type of Delete, and then update the one or more of the records in the spreadsheet.
For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, you'll again select the template type Financial Administration and the template GL Cross Reference. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
See also Download/Upload Data from Spreadsheets and View Data Loading Status.
Non-Merchandise codes are used on invoices, both in Import Management and in Invoice Matching to represent costs that are not specifically merchandise, such as freight, insurance, and so on. The costs can be for services that a supplier or partner performs or for costs associated with the delivery of a purchase order. Non-merchandise codes are associated with cost components, which are a more granular definition of non-merchandise costs for the purchasing and importation process in the form of expenses and assessments. Multiple cost components can be associated with a single non-merchandise code. Financial mapping to the GL for these costs is done through non-merchandise codes. Cost components themselves are created separately and are entered through the Foundation template type and Cost Components template.
All of the updates that can be made by the retailer for non-merchandise codes, their association with cost components as well as adding translations for non-merchandise code descriptions are done through a spreadsheet download and upload processes, which are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add or update non-merchandise codes or add cost components to non-merchandise codes, select the template type of Financial Administration from the Download Data screen and then the template Non-Merchandise Codes. Click the Download button and, when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice.
Note:
Non-Merchandise codes for escheatment cost, tax cost and freight cost cannot be deleted using this functionality as they are system required.To add a new non-merchandise code, start in the Non-Merchandise Codes tab, and, in a blank line in the template, select the action type of Create. Next enter a Code value, which can be a character field of up to 6 characters. Also enter the description for the Non-Merchandise Code in the primary language (as defined in the Merchandising system options) of up to 250 characters and a unique code for the reason of up to 6 characters.
If you wish to add Non-Merchandise Code descriptions in any other languages, then select the Non-Merchandise Code Trans tab and in a blank row select an action type of Create. Then, enter the non-merchandise code and language for the translated description, and then a translated description. The translated description can also be up to 250 characters long. This is an optional step.
If you wish to associate Cost Components to the Non-Merchandise Code, then select the Non-Merchandise Cost Components tab, and in a blank row select an action type of Create. Then enter the Non-Merchandise Code and the ID and the Cost Component you want to associate together. You can associate multiple cost components with a single non-merchandise code, but a cost component can only be associated with a single non-merchandise code. This is an optional step.
If you would like to update an existing non-merchandise code then a similar process will be followed to that described above for entering new codes. First, download the spreadsheet, and then find the code that you want to update and the tab that contains the data that you want to update. In that row select the action type of Update, and then update one or more of the values for that record. You can update the Description of the non-merchandise codes or the language translations.
If you wish to delete a non-merchandise code because it is not used by your business any longer, update the action column to select Delete for the selected non-merchandise code in the Non-Merchandise Codes tab. When deleting a non-merchandise code, you will also need to delete any Translations for that code in the Non-Merchandise Code Translation tab, and any cost component associations for that code in the Non-Merchandise Cost Component tab.
If you wish to delete a Cost Component association with a non-merchandise code because that cost component is not used by your business any longer or if it should be associated with a different code, update the action column to select Delete for the non-merchandise code/cost component record you wish to delete. This action will not delete the actual cost component, only it's association with that non-merchandise code.
For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, you'll again select the template type Financial Administration and the template Non-Merchandise Codes. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.
Freight and payment terms are industry codes that are used in trade between a seller and buyer to define and agree to how responsibility for freight is set and what the expectation for payment is, including whether there are any discounts for prompt payment of an invoice. Freight and payment terms are included on purchase orders to vendors and also on invoices from vendors. Both sets of terms are ”owned” by the financial system, so any freight or payment term values entered into Merchandising should mirror the terms available in the associated financial system and use the same codes or IDs to ensure successful integration of the values to financials on transactional data.
All of the updates that can be made by the retailer for freight and payment terms, as well as adding translations for descriptions of the terms, is done through a spreadsheet download and upload processes, which are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add or update freight or payment terms, select the template type of Financial Administration from the Download Data screen and then the template Terms. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice.
The Terms template has several tabs including; Freight Terms, Freight Terms Translations, Payment Terms, Payment Terms Detail and Payment Terms Translation.
To add a new freight term, start in the Freight Terms tab, and in a blank line in the template, select the action type of Create. Next enter a Freight Term value, which can be a character field of up to 30 characters. Also, enter the description for the Freight Terms in the primary language (as defined in the Merchandising system options) of up to 240 characters. Then, optionally enter date values for Active Start Date and Active End Date and enter a Yes or No value for the Enabled Flag.
If you wish to add freight terms descriptions in any other languages, then select the Freight Terms Translations tab and in a blank row select an action type of Create. Then, enter the Freight Terms code and language for the translated description, and then translated description. The translated description can also be up to 240 characters long. This is an optional step.
If you would like to update any details for existing freight terms, a similar process will be followed as that described above for creating new reasons. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.
The following columns can be updated in each tab:
Freight Terms – Description, Active Start Date, Active End Data, Enabled Flag
Freight Terms Translations – Description
In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.
If you wish to delete a freight term because it is not used by your business any longer, update the action column to select Delete for the selected freight term in the Freight Terms tab. Any associated freight terms translations should also be deleted in the Freight Terms translation tab. If you wish to delete a translated freight term description, you can take a similar action to set the action column to Delete on the Freight Terms Translation tab for a record. For Freight Terms, this table also includes the description in the primary language, so that language record cannot be deleted unless the entire freight term is being deleted.
Note:
A Freight Term cannot be deleted if it is currently associated with an active Purchase Order, so an error will be raised if this occurs when the changes are uploaded.To add a new payment term, start in the Payment Terms tab, and in a blank line in the template, select the action type of Create. Next, enter a Terms value that matches the same term in the Financials system, which can be up to 15 characters. Also enter the Terms Code, which can be up to 50 characters used to provide a short description of the terms, and a description for the Payment Terms in the primary language (as defined in the Merchandising system options) of up to 250 characters. Additionally enter a Rank value, which is numeric and provides a priority ranking for terms when determining ”best terms”.
If you wish to add payment terms descriptions in any other languages, then select the Payment Terms Translation tab and in a blank row select an action type of Create. Then, enter the Terms ID and select the language you are adding a translation for. Next, enter the translated descriptions for Terms Code and Terms Description. The translated description can also be up to 250 characters long. This is an optional step.
You will also need to add a detail to a payment term. Merchandising currently only supports a single active detail record for a payment term; it does not support complex payment terms that manage things like partial payments. To add a detail to a payment term, select the Payment Term Details tab, and in a blank line in the template, select the action type of Create. Next enter the Terms value for which you are adding a detail, and also add a sequence value. In addition to these, you will need to add the details of the terms that define the payment term and how it functions. These include the Due Days, Due Max Amount, Due Day of Month Forward, Due Months, Discount Days, Discount Percentage, Discount Day of Month and Fixed Due Date and Cutoff Day. Also indicate whether it is enabled (Y/N), and Start and End Active Days.
If you would like to update existing payment terms then a similar process will be followed to that described above for entering new payment terms. First, download the spreadsheet, and then find the Payment Term, Payment Term Details or Payment Terms Translation that you want to update and the tab that contains the data that you want to update. In that row select the action type of Update, and then update one or more of the values for that record. At the payment terms level you can update the Description and the Rank for the term. At the detail level, you can update all values except the term itself.
If you wish to delete a payment term because it is not used by your business any longer, update the action column to select Delete for the selected term in the Payment Terms tab. You will also need to delete the related records on the Payment Terms Detail and Payment Terms Translation tabs with a similar update of the Action field to Delete.
For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Financial Admin and the template Terms. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.
When value added tax (VAT) functionality is enabled in Merchandising, certain VAT entities are required to be setup so that they can be associated with locations, suppliers, partners and items to support proper VAT calculations on transactions across the Merchandising suite. The primary VAT entities are VAT codes and their associated rates, as well as VAT regions.
VAT codes represent the different categories of VAT that are used in the system. Each of these categories will also have VAT rates associated with them. While VAT codes are normally country specific, the VAT codes and rates set up in Merchandising are not specifically associated with a specific country or VAT region. So if multiple VAT regions use the same rate, they could share a VAT code. But, if there is a need to differentiate by country, even though the rates are the same, different codes should be set up for the different countries/VAT regions. There is also a system required VAT code of Exempt, which is associated with a 0% VAT rate. This code cannot be deleted. VAT codes and rates are managed through spreadsheet download and upload processes. These processes are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add, update, or remove VAT regions, codes, and rates, you will select the template type of Financial Admin from the Download Data screen and then the template VAT. Click the Download button and, when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be 5 sheets that can be modified – VAT Codes, VAT Code Translations, VAT Rates, VAT Regions and VAT Regions Translations.
To add a new VAT code, start in the VAT Code tab, and, in a blank line in the template, select the action type of Create. Next, enter the Code Value up to 6 characters and a description for the code in the primary language (as defined in the Merchandising system options) of up to 120 characters. Also include a value in the Incl. in NIC column. Normally this should be set to No. Only in the case of an implementation with Brazilian Localization enabled would this be a value other than No.
If you wish to add VAT Code descriptions in any other languages, then select the VAT Code Translations tab and in a blank row select an action type of Create. Then, enter the language for the translated description, the code added in the VAT Codes tab, and then translated description. The translated description can also be up to 120 characters long. This is an optional step.
For every VAT Code added, there should be at least on VAT rate associated with the code. Only a single rate can be active for a VAT code at any given time, but the rate associated with a VAT code can change over time, so the rates are effective dated. To add a new VAT rate, start in the VAT Rates tab, and, in a blank line in the template, select the action type of Create. Next, enter the code value for the VAT code that you want to add a rate to and include a Rate Value, which represents a percentage, and an Active Date. Also include a value for the New Active Date. As the rate associated with a VAT code changes over time, new records will be added for the changed rates and Merchandising will use the New Active Date to determine when those rates become effective.
To add a new VAT Region, start in the VAT Region tab, and, in a blank line in the template, select the action type of Create. Next enter the VAT Region ID of up to 4 characters and a VAT Region Description in the primary language (as defined in the Merchandising system options) of up to 120 characters. Also include values for the VAT Region Type (E = Base EU Region, M = EU-Member, and N = Non-Member), Acquisition VAT (Yes or No), and VAT Calc Type (Simple, Exempt, or Custom). Finally, if reverse charge domestic VAT is used for certain items in the region, then include a threshold value in the Reverse VAT Threshold field.
Note:
Acquisition VAT is currently only enabled for regions flagged as Base EU Regions or EU Members.If you wish to add VAT region descriptions in any other languages, then select the VAT Region Translations tab and in a blank row select an action type of Create. Then, enter the language for the translated description, the code added in the VAT Regions tab, and then translated description. The translated description can also be up to 120 characters long. This is an optional step.
If you would like to update any details for existing VAT codes or rates, a similar process will be followed as that described above for creating new reasons. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.
The following columns can be updated in each tab:
VAT Codes – Description, Include in NIC
VAT Code Translations – Description
VAT Rates – Active Date, New Active Date, Rate
In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.
If you wish to delete a VAT Code because it is not used by your business any longer, update the action column to select Delete in each of the tabs where it occurs. This includes the VAT Codes, VAT Codes Translations and VAT Rates tabs.
Note:
A VAT code cannot be deleted if it is currently associated with any items or departments, so an error will be raised if this occurs when the changes are uploaded. Additionally, as noted above, the system generated code Exempt cannot be deleted.For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Financial Admin and the template VAT. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.
Within Merchandising, org units are an equivalent concept to Operating Units in Oracle Financials, which exists within a set of books in the General Ledger. Org units are associated with suppliers, partners, stores, and warehouses within Merchandising. The financial operating unit is generally a geographic area of a business and it allows the business to control which supplier addresses a particular operating unit and its locations can do business. Org units can be added, updated or deleted through spreadsheet download and upload processes. These processes are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add or update org units, you will select the template type of Administration from the Download Data screen and then the template Org Units. Click the Download button and, when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be two sheets that can be modified – Org Units and Org Units TL.
To add a new org unit, start in the Org Units tab, and, in a blank line in the template, select the action type of Create. Next enter a unique org unit ID (up to 15 numbers, no spaces), enter the General Ledger set of books ID for the new org unit to reside under, along with a description for the org unit in the primary language (as defined in the Merchandising system options) of up to 120 characters.
If you wish to add translations for the org unit in languages other than the primary language, this can be done in the Org Units TL tab. Navigate to a blank row and select the action type of Create and the language in which the translated description will be entered. Then, enter the org unit for which the translation applies. Finally, enter the translated description. The translated description can also be up to 120 characters long. This is an optional step.
If you would like to update any details for existing org units, a similar process will be followed as that described above for creating new org units. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.
The following columns can be updated in each tab:
Org Units – Description
Org Units TL - Description
In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.
If an existing org unit is not referenced by a supplier, partner, store, or warehouse it can be deleted by selecting the Delete action type for the row containing the org unit you wish to delete.
For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Administration and the template Org Units. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.
Transfer entities are part of the Merchandising structure around locations used to control when transfers are considered to be intra-company transfers as opposed to inter-company transfers, which indicate a sale/purchase movement between different entities in a business. Store and warehouse locations, along with external finishers, are associated with transfer entities. Business logic for transfers will look at the transfer entities for the sending and receiving locations of the transfer and this will help to determine whether a transfer is intra-company or inter-company. There is also a relationship in Merchandising between transfer entities, org units and sets of books, which is also maintained through this process. The list of valid transfer entities as well as the relationships with the org units and sets of books is managed through spreadsheet download and upload processes. These processes are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.
To add, update, or remove transfer entities, you will select the template type of Financial Admin from the Download Data screen and then the template Transfer Entities. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice.
Once opened, there will be 3 sheets that can be modified – Transfer Entities and Transfer Entities Translations and Transfer Entity Set of Books. The main tab is the Transfer Entities tab, which is where new transfer entities can be created and existing transfer entities can be updated or deleted. Optionally, you can also add translated descriptions in the Transfer Entities Translations tab and set of the relationship of the transfer entity with org units and sets of books.
To add a new transfer entity, start in the Transfer Entity tab, and, in a blank line in the template, select the action type of Create. Next enter the ID for the transfer entity (number up to 10 digits) as well as a Description and Secondary name in the primary language (as defined in the Merchandising system options). These values can be up to 120 characters.
If you wish to add Transfer Entity descriptions in any other languages, then select the Transfer Entity Translations tab and in a blank row select an action type of Create. Then, enter the language for the translated description, the transfer entity ID added in the Transfer Entity tab, and then translated description. The translated description can also be up to 120 characters long. This is an optional step.
Transfer entities, org units and sets of books in Merchandising are related. In general, the set of books is the highest level of the three, where a single transfer entity or org unit cannot be associated with more than one set of books. However, multiple org units or transfer entities can be associated with a single set of books. Transfer entities and org units are not necessarily related to each other and a 1-to-many or many-to-1 relationship can exist between these two entities.
To add a new Transfer Entity Set of Books relationship, start in the Transfer Entity Set of Books tab and, in a blank line in the template, select the action type of Create. Next, enter the IDs for the Transfer Entity, Org Unit and Set of Books.
If you would like to update any details for transfer entities, a similar process will be followed as that described above for creating new transfer entities. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.
Transfer Entity – Description, Secondary Name
Transfer Entity Translations – Description
In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.
If you wish to delete a transfer entity because it is not used by your business any longer, update the action column to select Delete in each of the tabs where it occurs. This includes the Transfer Entity and Transfer Entity Translations tabs, as well as the Transfer Entity Set of Books. Additionally, as noted above, the system generated codes cannot be deleted.
Note:
A Transfer Entity cannot be deleted if it is currently associated with a location, so an error will be raised if this occurs when the changes are uploaded.For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Financial Admin and the template Transfer Entities. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.
To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.