Skip to main content

Invoice on Hold

 


 

Lean Specification Document

 

AP Invoices on Hold

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

                                

Document Control Information

Document Identification

RPT_AP_1

Document Name

AP Invoices on Hold

Project Name

Client

Document Author

Document Version

1.0

Document Status

<Draft >

Date Released

 

Document Edit History

Version

Date

Additions/Modifications

Prepared/Revised by

1.0



1.1

 

 

 

Document Review History

Date

Name

Organization/Title

Comments

 

 

 

 

Distribution of Final Document

The following people are designated recipients of the final version of this document:

Name

Organization/Title

 

 

Sign-off of Lean Spec

Lean spec design details and requirements have been signed off by:

Date

Name

Organization/Title

Comments

 

 

 

 

 

 

 

 

 

 

Table of Contents

1     Introduction. 4

1.1   Purpose/Justification. 4

1.2   Report Description and Overview.. 4

2     Functional design. 5

2.1   Report Details. 5

2.2   Data Selection Criteria. 5

2.3   Assumptions. 6

2.4   Launch Parameters. 6

2.5   Data Mapping. 6

2.5.2      Totals/Breaks. 7

2.6   Configuration Prerequisites. 7

2.7   Dependencies. 7

2.8   Sample Report. 8

2.9   Security Considerations. 8

3     Technical design. 9

3.1   Overview – Technical Design. 9

3.2   Detailed Technical Design and Data Flow.. 9

3.3  10

3.4   Report Design. 10

3.5   Sample Report. 11

3.6   Custom/Customized Component List. 12

3.7   Additional Technical Information. 12

3.8   Error Handling. 12

3.9   Launch Parameters. 13

4     Test Scenarios. 14

5     Open Decision Items. 15

 


1      Introduction

1.1           Purpose

This document specifies the details of an OTBI report to track AP Invoices on Hold which are Hold Invoices in Cloud Payables. There is no ‘out of the box’ reports in Oracle Cloud to extract Hold Invoices in excel format.

1.2           Report Description and Overview

·       AP Invoices on Hold OTBI report should capture all AP Invoices on Hold

·       Report should capture AP Invoices on Hold.

·       Report output should be in excel format

·       The user should have the ability to run the report with multiple parameters

o   For a Invoice date range

o   For a single Invoice or all Invoices

 

 

2      Functional design

2.1           Report Details

 

Report Name

AP Invoices on Hold

Reporting Tool (BI Publisher/OTBI/FRS)

OTBI

Report Path

<TBD>

Data Source

 

Oracle Cloud Payables

Full Extract / Changes Only

NA

Report Schedule

Ad- Hoc Basis

Distribution List

NA

File Name

AP Invoices on Hold

Output Format

XLSX

Department Owner

Estimated number of records

<TBD>

Additional Comments

NA

PII/Confidential Data

NA

 

 

2.2           Data Selection Criteria

·       Select all AP Invoices on Hold

·       Group Invoices on Hold by Supplier

·       Sort data by Invoice on Hold date in descending order

2.3           Assumptions

·       This report should only capture AP Invoices which are in Hold of the run date.

·       Unhold Invoices should not be captured in this report.

2.4           Launch Parameters

·       Invoice Date From/To: (Optional)

·       Invoice From/To: (Optional)

2.5           Data Mapping

Fields required on Invoices on Hold OTBI report.

2.5.2       Totals/Breaks

·       NA

2.6           Configuration Prerequisites

·       NA

2.7           Dependencies

·       NA

2.8           Sample Report

Legacy sample output:

2.9           Security Considerations

Below role and security access should be assigned to the business user to access the report.

·       Role: Accounts Payable Manager

·        Data Access set: 

Level: Business Unit

 Value 'DeKalb County'

3      Technical design

3.1           Overview – Technical Design

 

<Yet to be updated by Tech Team>

 

<Explain a high-level technical design/architecture about how this requirement will be developed in ERP Cloud. This should cover a high-level overview of key design elements, (such as tool used to develop integration/report (BIP, OTBI, FRS etc.), any middleware, any component external to ERP Cloud etc.)>

3.2           Detailed Technical Design and Data Flow

 

<Yet to be updated by Tech Team>

 

·       Explain a detailed design of how the technical object will be developed. This should cover a detailed description of all design elements, (such as tool used to develop integration/report( BIP, OTBI, FRS etc., any middleware, any component external to ERP Cloud etc.), how the data flows between them and any key technical considerations.

·       Bullet points are recommended.

·       A flow/architecture diagram is recommended in case of complex integration/report design.

 

 

 

 

 

 

 

 

 

 

 

 

 

3.3           Report Design

<Provide details related to the integration/report>

Integration/Report Design

Integration/Report Name

 <Name of the integration/report as in ERP Cloud>

Type

 Inbound

 Outbound

 N/A – (E.g. reports)

 

Tool

 

 OTBI

 BIP

 FRS

 Inbound Tool <please specify>

 REST Services

 Others <please specify>

Data Source

 ERP Cloud

 Custom Report <Insert Report Name>

 Web Service <insert WWS name or external web service>

 File Inbound into Oracle <insert inbound source and file name>

Transformation

 Doc Transformation

 eText

 None

<Any other – please mention>

Delivery / Retrieval Service/ File Handling

<Mention how the output/input file will be processed, transferred, file destinations>

Output/Inbound Filename

Name of the output file.

Mention applicable file extensions, such as .txt, .pdf etc.

Mention any sequence of date/time format needed in file name, E.g., INT01_MMDD.vv

File Format

<Mention the format of the output file>

Field Delimiter

<Delimiter of the fields in the file, E.g., comma, Tab, Fixed Length etc.>

Compression/Encryption

Please mention any compression (Zip etc.) or encryption needed of the output file.

Archiving Options

Number of days saved in directory

 

 

3.4           Sample Report

<Yet to be updated by Tech Team>

 

<Please attach a sample interface file or sample report. Ensure to remove confidential data>

 

3.5           Custom/Customized Component List

Cover components such as:

·       OTBI Subject Area

·       BIP Report Name

·       Template Name

·       Data Model Name

 

Component Name

Component Type

Purpose

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3.6           Additional Technical Information

<Yet to be updated by Tech Team>

 

·       Mention details of any technical development/tools/components which are part of this report, but not covered in previous sections

 

 

3.7           Error Handling

 

<Yet to be updated by Tech Team>

 

·       Mention details of how program errors will be handled.

·       Capture details of any error report or log file needed.

·       Mention exceptions and acceptable errors based on agreed upon assumptions.

 

 

 

3.8           Launch Parameters

<Yet to be updated by Tech Team>

4      Test Scenarios

 

Scenario 

Expected Result 

Report is run for a specific date/date range

Excel output shows all Hold Invoices for the given date/date range.

Report is run for all suppliers

Excel output shows all Hold Invoices for all suppliers.

Report is run for a single supplier

Excel output shows all Hold Invoices for the given supplier.

5      Open Decision Items

 

Date Reported

Status

Question

Answer

Due Date

Responsible Party

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Comments

Popular posts from this blog

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management  

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management  

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management