1 Feature Summary

The enhancements below are included in this release.

Column Definitions

• Feature: Provides a description of feature being delivered.

• SR Number: Identifies the SR number associated with the feature, if any.

• Delivered: Identifies whether the feature is Enabled or Disabled upon initial delivery.

• Scale: Identifies the size of the feature. Options are:

  • Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

  • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

• Customer Action Required – You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.

Table 1-1

Feature	Delivered	Scale	Customer Action Required?
E-invoicing	Disabled	Small	Yes
Gapless Document Sequencing	Disabled	Small	Yes
Enhanced Tax Support	Disabled	Large	Yes
Updated Exchange Rates for Invoice Matching	Enabled	Small	No
Invoice Matching Cloud Service Technical Upgrade	Enabled	Small	No
Invoice Matching Mobile Re-introduction	Enabled	Small	No
Invoice Matching Security Updates	Disabled	Small	Yes
Document Maintenance User Interface Enhancements	Enabled	Small	No

E-invoicing

E-Invoicing is the electronic exchange of financial documents between a business and a government agency, a business to another business, or a business to consumer. Invoice Matching uses a configurable approach to identifying documents to be extracted for E-invoicing. The configurable approach allows the user to identify documents by country or by country/set of books combination and map transaction types to be included in the extract for integration with 3rd party solutions which manage local tax reporting.

Steps to Enable

1. Configure the documents you want to be extracted for E-Invoicing using the following instructions.

   1. From the Merchandising task list, select Foundation Data > Download Foundation Data.

   2. In the Download Data screen, select the template type Foundation and template E-Invoicing Mapping.

   3. Then, click Download and when prompted, select to open the data in the spreadsheet application of your choosing.

   4. In the spreadsheet, you will see one tab - E-invoices. Enter information in to configure the transaction types that should be configured for E-invoicing. More details are available in the Invoice Matching Implementation Guide on how to complete this step.

   5. Save your updated spreadsheet to a local directory (retaining the .ods extension) and close the document.

   6. In the Merchandising task list, select Foundation Data > Upload Foundation Data.

   7. In the Upload Data screen, select the template type Foundation and template E-Invoicing Mapping. Then, using the Browse button, select the file that you saved in step e. The Process Description will default for you. Then click Upload.

   8. Then, validate that there were no errors with your updates. From the Merchandising task list, select Foundation Data > Review Status.

   9. In the Data Loading Status screen, navigate to the row containing the process description that defaulted in step g. If the status is Processed Successfully, the currencies were successfully deleted. If there are errors, use the View Issues button to get more information on the errors and correct your updates. Once the data is corrected, repeat steps f and g.

2. Enable the E-invoicing batch jobs as described below.

Batch Schedule Impacts

Table 1-2

Process Name	Process Type	New/Updated?	Delivered
BDI_REIM_INVC_MATCH_DOC_TX_CYCLE_PROCESS	Recurring	New	Disabled
BDI_REIM_INVC_MATCH_DOC_TX_PROCESS_ADHOC	Ad hoc	New	Disabled

Steps to Enable

To enable one or both of the above jobs as part of your nightly batch cycle, follow the instructions below.

1. Log into the Process Orchestration and Monitoring (POM) application with the Administrator role

2. In the task list, select Schedules > MERCH > Administration > Batch Administration. This will bring up the MERCH: Batch Administration screen which has the following panels:

   1. Batch Applications and Modules

   2. Batch Cycle Management

   3. Batch Jobs

3. Under Batch Jobs, scroll (or filter) to locate the jobs to be enabled and click the Enabled check box to enable or disable the job. Repeat until all jobs have been updated.

4. Click Save and Close to save your changes and update the schedule.

Note:

After saving, the changes will take effect once the new scheduler day is created. The changes will not take effect for the current day.

Code Updates

Table 1-3

Code Type	Code Type Description	Code	Code Description	New/Updated	Delivered
IMRA	Invoice Matching Receiving Authority	1	Trusted Third Party	New	Y
IMEP	Invoice Matching Extract Point	1	Creation	New	Y
IMEP	Invoice Matching Extract Point	2	Posting	New	Y

Data Access Schema (DAS) Updates

Table 1-4

Table Name	View Name	New/Updated?	Change Notes
IM_DOC_HEAD	DAS_WV_IM_DOC_HEAD	Updated	Added TRANSMISSION_NUMBER, EXTRACT_TIMESTAMP, and RECEIVING_AUTHORITY

Integration Impacts

Table 1-5

API Name	New/Updated?	Integration Type	Field Name	Change Notes
E-invoicing BDI Publishing	New	BDI	N/A	This is a new integration to support the E-invoicing requirement, and will publish documents to external systems if the system is configured to do so. There are two new processes that can be used in the batch schedule to trigger the integration jobs (cyclic or ad hoc).

Gapless Document Sequencing

The main purpose of gapless document sequencing is to uniquely identify a transaction, which is a requirement of bookkeeping legislation and global standards in many countries. This requirement mandates the ability for each accounting posting to support an audit trail back to the original document or transaction. Invoice Matching uses a configurable approach to creating and maintaining document sequences, which allows you to create a document sequence by country or by country/set of books combination and to map transaction types to the sequence. The sequence number is incremented and assigned to each qualifying document during the entry process. Additionally the user can select specific attributes associated with the document which can be kept as part of a prefix associated with the document sequence.

Steps to Enable

To use the document sequencing feature in Invoice Matching, you will need to define the document sequences. This is done in Merchandising, using the following instructions:

1. From the Merchandising task list, select Foundation Data > Download Foundation Data.

2. In the Download Data screen, select the template type Foundation and template Document Sequence.

3. Then, click Download and when prompted, select to open the data in the spreadsheet application of your choosing. There will be two tabs - Document Sequence and Transaction Types. Fill in the details in both tabs for document sequences for all applicable transaction types. More details are available in the Invoice Matching Implementation Guide on how to complete this step.

4. Save your updated spreadsheet to a local directory (retaining the .ods extension) and close the document.

5. In the Merchandising task list, select Foundation Data > Upload Foundation Data.

6. In the Upload Data screen, select the template type Foundation and template Document Sequence. Then, using the Browse button, select the file that you saved in step 4. The Process Description will default for you. Then click Upload.

7. Then, validate that there were no errors with your updates. From the Merchandising task list, select Foundation Data > Review Status.

   In the Data Loading Status screen, navigate to the row containing the process description that defaulted in step 6. If the status is Processed Successfully, the sequences were successfully created. If there are errors, use the View Issues button to get more information on the errors and correct your updates. Once the data is corrected, repeat steps 5 and 6.

Code Updates

Table 1-6

Code Type	Code Type Description	Code	Code Description	New/Updated	Delivered
IMPV	Invoice Matching Prefix Values	1	Document Date	New	Y
IMPV	Invoice Matching Prefix Values	2	Location	New	Y
IMPV	Invoice Matching Prefix Values	3	Document Type	New	Y
IMPV	Invoice Matching Prefix Values	4	Transaction Type	New	Y
IMPV	Invoice Matching Prefix Values	5	Supplier Site	New	Y
IMPV	Invoice Matching Prefix Values	6	Supplier	New	Y
IMPS	Invoice Matching Prefix Separator	1	.	New	Y
IMPS	Invoice Matching Prefix Separator	2	:	New	Y
IMPS	Invoice Matching Prefix Separator	3	;	New	Y
IMPS	Invoice Matching Prefix Separator	4	/	New	Y
IMPS	Invoice Matching Prefix Separator	5	\	New	Y
IMPS	Invoice Matching Prefix Separator	6	|	New	Y
IMPS	Invoice Matching Prefix Separator	7	-	New	Y
IMPS	Invoice Matching Prefix Separator	8	_	New	Y
IMPS	Invoice Matching Prefix Separator	9	,	New	Y
IMTT	Invoice Matching Transaction Types	1	Consignment Invoice	New	Y
IMTT	Invoice Matching Transaction Types	2	ERS Invoice	New	Y
IMTT	Invoice Matching Transaction Types	3	Bill Back Deal	New	Y
IMTT	Invoice Matching Transaction Types	4	Other Merchandise Invoice	New	Y
IMTT	Invoice Matching Transaction Types	5	Non-Merchandise Invoice	New	Y
IMTT	Invoice Matching Transaction Types	6	Debit Memo Cost	New	Y
IMTT	Invoice Matching Transaction Types	7	Debit Memo Quantity	New	Y
IMTT	Invoice Matching Transaction Types	8	Debit Memo Tax	New	Y
IMTT	Invoice Matching Transaction Types	9	Credit Memo Cost	New	Y
IMTT	Invoice Matching Transaction Types	10	Credit Memo Quantity	New	Y
IMTT	Invoice Matching Transaction Types	11	Credit Note	New	Y
IMTT	Invoice Matching Transaction Types	12	Credit Note Request Cost	New	Y
IMTT	Invoice Matching Transaction Types	13	Credit Note Request Quantity	New	Y
IMTT	Invoice Matching Transaction Types	14	Credit Note Request Tax	New	Y

Data Access Schema (DAS) Updates

Table 1-7

Table Name	View Name	New/Updated?	Change Notes
IM_DOC_HEAD	DAS_WV_IM_DOC_HEAD	Updated	Added DOC_SEQ_NUM, DOC_SEQ_PREFIX, and SEQ_GROUP_ID

Enhanced Tax Support

Invoice Matching has been extended to support multiple taxes per item, and to add a tax type that supports per unit taxes. Invoice Match also utilizes the new Merchandising tax processing, which will return tax details for item/location combinations. Changes were also made to the induction templates and for deals and fixed deals to account for the new tax enhancements. A new choice has been added to the Taxes Allowed system option in Invoice Matching. This new option will enable these new tax options and should be updated if enabling Global Tax in Merchandising.

Note:

There is a known issue in that if you are not moving to the new Global Tax mode in Invoice Matching and you are currently running in Single Tax mode, then the templates that include tax need to be customized to remove the multi-tax and per-unit tax components. This will require raising an SR for assistance from the Oracle Cloud Operations team. If you are using No Tax mode, there is no impact for this change.

Steps to Enable

The following steps are required to enable the use of Global Tax in Invoice Matching.

1. Update the Taxes Allowed system option to choose the new Global Tax option. This will require logging an SR, as the system option is not editable in the UI once it is initially set.

2. If you update your configuration to run in Global Tax mode, then for all templates that you are using for Invoice Induction, you will need to download a new blank template, as new fields for tax have been added for Global Tax.

   • Per Unit Tax column

   • Multi-tax Worksheets

3. For inbound integration changes outlined below, there is no change required for the new fields added regardless of your Taxes Allowed setting - the program will accept both formats. Version 2 is the format that should be used if you are going to be using the additional new fields for the Global Tax.

4. For the outbound integration changes outlined below, only version 2 will be produced by Invoice Matching with this change, including the new fields outlined below. These will need to be accounted for in your integrations.

See also the Merchandising Global Tax requirements for details on setting Global Tax as your tax type default and other required configurations.

System Options Updates

Table 1-8

Attribute Name	New/Updated?	Description	Patch Default
Taxes Allowed	Updated	Indicates the type of taxes supported in Invoice Matching. Previous values: No Tax and Single Tax. New option added Global Taxes.	No update to previous settings

Data Access Schema (DAS) Updates

Table 1-9

Table Name	View Name	New/Updated?	Change Notes
IM_DOC_DETAIL_RC_TAX	DAS_WV_IM_DOC_DETAIL_RC_TAX	Updated	added TAX_CALC_TYPE
IM_DOC_NON_MERCH_TAX	DAS_WV_IM_DOC_NON_MERCH_TAX	Updated	added TAX_CALC_TYPE
IM_DOC_TAX	DAS_WV_IM_DOC_TAX	Updated	added TAX_CALC_TYPE
IM_INVOICE_DETAIL_TAX	DAS_WV_IM_INVOICE_DETAIL_TAX	Updated	added TAX_CALC_TYPE

Integration Impacts

Table 1-10

API Name	New/Updated?	Integration Type	Field Name	Change Notes
EDI Injector Batch	Updated	Flat File	FILE_VERSION	Version for the file format
EDI Injector Batch	Updated	Flat File	TAX_PER_UNIT_ITEM_SIGN_IND	Sign indicator for per unit tax
EDI Injector Batch	Updated	Flat File	TAX_PER_UNIT_ITEM	Per unit tax value
EDI Invoice Download Batch	Updated	Flat File	FILE_VERSION	Version for the file format
EDI Invoice Download Batch	Updated	Flat File	TAX_PER_UNIT_ITEM_SIGN_IND	Sign indicator for per unit tax
EDI Invoice Download Batch	Updated	Flat File	TAX_PER_UNIT_ITEM	Per unit tax value

Updated Exchange Rates for Invoice Matching

With this update, the rate captured and displayed on each of the documents created in Invoice Matching (through both online and upload) will be the rate against the currency of the location on the document. All conversions between any two currencies in Invoice Matching, will use direct exchange rates between the two currencies involved provided they exist, as described in the Merchandising updates. If a direct rate is not available, then a conversion via the primary currency would be used.

Invoice Matching Cloud Service Technical Upgrade

Invoice Matching Cloud Service was upgraded to the latest middleware and framework components with this release.

Invoice Matching Mobile Re-introduction

The Invoice Matching mobile workflow is being re-introduced with this release to better support SaaS implementations and to provide increased usability.

Invoice Matching Security Updates

Below is an outline of new and updated privileges and duties added in the solution since the last update. Review the details of the duties and privileges and then follow the instructions outlined below to enable them in your implementation and add them to your user roles, as appropriate.

New/Updated Duties

Table 1-11

Title	New/Update?	Base Role	Duty Description
TOLERANCE_MAINTENANCE_DUTY	Update	FINANCIAL_MANAGER_JOB	TOLERANCE_MAINTENANCE_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
SYSTEM_OPTIONS_INQUIRY_DUTY	Update	FINANCIAL_MANAGER_JOB	SYSTEM_OPTIONS_INQUIRY_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
SUPPLIER_OPTIONS_MAINTENANCE_DUTY	Update	FINANCIAL_MANAGER_JOB	SUPPLIER_OPTIONS_MAINTENANCE_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
RESOLVE_TAX_DISCREPANCY_DUTY	Update	FINANCIAL_MANAGER_JOB	RESOLVE_TAX_DISCREPANCY_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
RESOLVE_DISCREPANCIES_DUTY	Update	FINANCIAL_MANAGER_JOB	RESOLVE_DISCREPANCIES_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB. It also has modified permissions relating to the global tax requirement.
REASON_CODE_MAINTENANCE_DUTY	Update	FINANCIAL_MANAGER_JOB	REASON_CODE_MAINTENANCE_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
MATCH_STRATEGY_MAINTENANCE_DUTY	Update	FINANCIAL_MANAGER_JOB	MATCH_STRATEGY_MAINTENANCE_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
INVOICE_MATCHING_HIGH_SECURITY_DUTY	Update	FINANCIAL_MANAGER_JOB	INVOICE_MATCHING_HIGH_SECURITY_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
GENERAL_LEDGER_MANAGEMENT_DUTY	Update	FINANCIAL_MANAGER_JOB	GENERAL_LEDGER_MANAGEMENT_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
FINANCIAL_POSTING_ERROR_DUTY	Update	FINANCIAL_MANAGER_JOB	FINANCIAL_POSTING_ERROR_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
DOCUMENT_HIGH_SECURITY_DUTY	Update	FINANCIAL_MANAGER_JOB	DOCUMENT_HIGH_SECURITY_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
DASHBOARD_MANAGER_DUTY	Update	FINANCIAL_MANAGER_JOB	DASHBOARD_MANAGER_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.
CREDIT_NOTE_MATCHING_DUTY	Update	FINANCIAL_MANAGER_JOB	CREDIT_NOTE_MATCHING_DUTY was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.

New/Updated Privileges

Table 1-12

Title	New/Update?	Parent Duty	Privilege Description
MAINTAIN_DOCUMENTS_PRIV	Update		MAINTAIN_DOCUMENTS_PRIV has modified permissions relating to the global tax requirement.
SEARCH_DOCUMENTS_PRIV	Update		SEARCH_DOCUMENTS_PRIV has modified permissions relating to the global tax requirement.
SEARCH_TAX_DISCREPANCY_LIST_PRIV	Update		SEARCH_TAX_DISCREPANCY_LIST_PRIV has modified permissions relating to the global tax requirement.
authenticated-role	Update		authenticated-role has modified permissions relating to the global tax requirement.
anonymous-role	Update		anonymous-role has modified permissions relating to the global tax requirement.
UPLOAD_DOCUMENTS_PRIV	Update	FINANCIAL_MANAGER_JOB	UPLOAD_DOCUMENTS_PRIV was unmapped from FINANCE_MANAGER_JOB and is now mapped to the new (renamed) FINANCIAL_MANAGER_JOB.

Customer Actions

Based on these new/updated duties and privileges, the following actions are required in the order described below in order to enable the features. If this update doesn't contain changes related to one of the steps below, it can be skipped and you can move to the next one. For more information on the workflows used to support the actions described below, see the Merchandising Administration Guide.

Step 1: Remove Privileges and Duties

For each of the privileges described above as removed, do the following:

1. Select Settings > Security > Role Mappings

2. Search for every instance of the removed privileges and delete them

For each of the duties that were flagged as removed above, you do not need to delete them, but you may choose to in order to stay in closer alignment with the base configuration. If you choose to delete these duties, then follow these steps:

1. Select Settings > Security > Role Mappings

2. Search for every instance of the removed duties and delete them

Step 2: Add New Duties

For each of the new duties listed above, follow these steps:

1. Select Settings > Security > Roles

2. Click on the Add iconic button or select Add from the Actions menu

3. Add the first new duty, including the name, and optionally the description in the popup displayed. Then click OK.

4. Repeat for all new duties listed above

Step 3: Add New Duties to Roles

Each of the new duties should then be added to the roles that require the access as defined in the privileges above.

1. Select Settings > Security > Role Mappings

2. Selecting a role that will be assigned one or more of the duties

3. For each role, click Select and Add and then select the the duties you want to add to the role using the popup

4. Repeat for each role where you want to add the new duties

Step 4: Add Child Duties

For any new duty listed above that contains other duties, the child duty will also need to be mapped to the new duty using the below steps.

1. Select Settings > Security > Role Mappings

2. Highlight the parent duty

3. Click Select and Add and then select the duties you want to add to the role using the popup.

4. Repeat until you have added all child duties to the parent duties

Step 5: Synchronize Privileges with New Duties

Each new duty then needs to have its privileges synchronized.

1. Select Settings > Security > Policy Patching

2. Select Sync with Patch

3. Under the Base Policies tab, working through the duties one at a time, select the checkbox next to each the corresponding privileges

4. Click Copy to Custom and then select the duty

5. Repeat until you have synchronized each duty

   Note:

   The Copy to Custom option does not clear the check boxes that you selected, so be sure to de-select the check boxes after each duty.

Step 6: Synchronize Modified Privileges

Each privileges that had changed permissions from previous updates and will need to be synchronized to update these permissions for the patch.

1. Select Settings > Security > Policy Patching

2. Select Sync with Patch

3. Under the Base Policies tab, select the checkbox next to each the corresponding privileges and click Sync

4. Repeat this for each privilege that had updated permission

Document Maintenance User Interface Enhancements

In this release, several changes were made to the Document Maintenance page to standardize the layout, provide additional information, and improve the process flow. The changes include:

• Updating the Create Document popup to a full screen along with adding the supplier name, supplier site name, and location name.

• Rearranging and reformatting several fields on the page to improve process flow and better utilize screen space.

• Rearranging the Document Header tab to improve usability.