Page Comparison

Description

Library vendors routinely send invoices billing for multiple Purchase Orders (POs). In many cases, the cost of additional charges (freight, shipping, etc) needs to be split among the accounts on these POs. Instead of manually creating one Payment Request (PREQ) for each PO referenced on the Invoice, users need a way to process the Invoice on one screen in order to avoid having to create individual PREQs and to distribute the cost of additional charges.

Design Technical

The technical design document shall lay out the high level design of how the Many Purchase Orders to One Invoice. The details laid out shall include the Wire¬frames for User Interface design, Data Element Layout, including the logical Database Design, Component Specifications including artifacts such as Class Diagram, State Chart Diagrams, OJB.xml specifications and other relevant information.

Service Design and Implementation

Screen Flow Diagram

Layout use cases based on the screen flows indicating navigation between different screens. 

Security

• Roles – list of roles to be defined

• • OLE-PURAP Accounts Payable Processor
  • OLE-PURAP Purchasing Processor
  • OLE-SYS Tax Manager
  • OLE-PURAP Accounts Payable Document Reviewer
  • KR-WKFLW Approve Request Recipient
  • OLE-SYS Accounts Payable Manager
  • OLE-PURAP Payment Request Hold / Cancel Initiator
  • OLE-SYS System User
  • OLE-SYS Manager
  • OLE-SELECT Accounting-AQ2
  • OLE-SELECT Accounting-AQ3
  • OLE-SELECT Accounting-AQ4
  • OLE-SELECT OLE-Receive-Mgr
  • OLE-SELECT Receiving-AQ3
  • OLE-SELECT OLE-Invoicing
  • OLE-SELECT Receiving-AQ4
  • OLE-SELECT OLE_Prepayment
  • OLE-SELECT OLE_RCV
  • OLE-SELECT OLE-Payment
  • OLE-SYS Fiscal Officer
  • KR-SYS Document Initiator
  • OLE-SYS Workflow Administrator
  • OLE-SYS Treasury Manager
  • OLE-SYS User
  • KR-WKFLW Initiator or Reviewer
  • KR-NS Document Editor
  • OLE-SYS Active Faculty or Staff
  • Recall Document (KR-WKFLW)     
  • Recall Document OLE (OLE-SYS)
  • OLE-SELECT OLE_User
  • KR-WKFLW Initiator
  • KR-WKFLW Non-Ad Hoc Approve Request Recipient
  • KR-NS Document Opener
  • OLE-PURAP Budget Reviewer
  • OLE-PURAP Sub-Account Reviewer
  • OLE-SYS Accounting Reviewer
  • OLE-SYS Tax Manager
  • OLE-SELECT OLE-Payment
  • OLE-SELECT OLE_Prepayment
  • OLE-SELECT OLE-Invoicing

• Permissions – list of permissions to be defined

• • Add Note / Attachment PREQ Invoice Image (OLE-PURAP)
  • View Note / Attachment PREQ Invoice Image (OLE-PURAP)
  • Edit Document PREQ R (OLE-PURAP)
  • Use Transactional Document PREQ requestPaymentRequestCancel (OLE-PURAP)
  • Use Transactional Document PREQ paymentRequestHoldCancelRemoval (OLE-PURAP)
  • Use Transactional Document PREQ requestPaymentRequestHold (OLE-PURAP)
  • Edit Document PREQ P (OLE-PURAP)
  • Edit Document PREQ F (OLE-PURAP)
  • Edit Bank Code PREQ (OLE-PURAP)
  • Blanket Approve Document PREQ (OLE-PURAP)
  • Initiate Document PREQ (OLE-PURAP)
  • Edit ENROUTE Payment Request Document (OLE-SELECT)
  • Edit PROCESSED Payment Request Document (OLE-SELECT)
  • Edit FINAL Payment Request Document (OLE-SELECT)
  • Modify PREQ Account Accounting Lines (OLE-SELECT)
  • Cancel Payment Request (OLE-SELECT)
  • Edit Payment Request Document (OLE-SELECT)
  • Edit Document AP PreRoute (OLE-PURAP)
  • Modify Accounting Lines AP Account items.sourceAccountingLines (OLE-PURAP)
  • Use Transactional Document AP editPreExtract (OLE-PURAP)
  • Modify Accounting Lines AP PreRoute items.sourceAccountingLines (OLE-PURAP)
  • Use Transactional Document AP managerCancel (OLE-PURAP)
  • Use Transactional Document AP processorCancel (OLE-PURAP)
  • Open Document PRAP (OLE-PURAP)     
  • Error Correct Document KFST (OLE-SYS)
  • Administer Routing for Document KFST (OLE-SYS)
  • Edit Bank Code OpenLibraryEnvironmentTransactionalDocument (OLE-SYS)
  • Administer Routing for Document KFS (OLE-SYS)
  • Blanket Approve Document KFS (OLE-SYS)
  • Initiate Document KFS (OLE-SYS)
  • Open Document KFS (OLE-SYS)
  • save Document KFS (OLE-SYS)
  • Delete Note / Attachment OLE FALSE (OLE-SYS)
  • Ad Hoc Review Document KFS A (OLE-SYS)
  • Ad Hoc Review Document KFS F (OLE-SYS)
  • Ad Hoc Review Document KFS K (OLE-SYS)
  • Copy Document KFS (OLE-SYS)
  • Add Message to Route Log KFS (OLE-SYS)
  • Super User Approve Single Action Request OLE (OLE-SYS)     
  • Super User Approve Document OLE (OLE-SYS)
  • Super User Disapprove Document OLE (OLE-SYS)
  • Open Document (OLE-SELECT)
  • Initiate OLE Documents (OLE-SELECT)
  • Cancel Document (KUALI)
  • Route Document (KUALI)
  • Edit Kuali ENROUTE Document Node Name PreRoute (KUALI)
  • Edit Kuali ENROUTE Document Route Status Code R (KUALI)
  • Add Note / Attachment Kuali Document (KUALI)
  • View Note / Attachment Kuali Document (KUALI)
  • Send FYI Request Kuali Document (KR-SYS)
  • Send Acknowledge Request Kuali Document (KR-SYS)
  • Send Approve Request Kuali Document (KR-SYS)
  • Add Message to Route Log (KUALI)
  • Send Complete Request Kuali Document (KR-SYS)

Component Design

• OBJ.xml
• State Chart Diagram

Service Contracts

Service Implementation

  Work-flow Diagram

 UI Wire-frames Design

InvoiceProcessScreen

DocumentOverview Tab

VendorTab

InvoiceInfoTab

InvoiceProcessItemsTab

Accounting lines

AccountSummaryTab

RelatedDocuments

PaymentHistory

General Ledger Pending Entries

Data Model

User Story : Many Purchase Orders to One Invoice

Entity: OLE_AP_INV_T

Entity: OLE_AP_INV_PO_ITM_T

Entity: OLE_AP_INV_ACCT_T

Entity: OLE_AP_INV_SUM_ACCT_T

Entity: OLE_AP_INV_PO_ITM_USE_TAX_T

1) How to handle the credit/debit data, in Invoice Document. As per new requirement user can give credit/debit for the invoice amount in Invoice. When debit is given or no data is given, logic will be handled

as in Payment Request now. If the user gives credit.. what needs to be done.

 Answer : Not sure of functional requirements. May be need to generate credit memo's for credit Transaction and Payment Requests for Debit Transaction.

2) Now SFC is to be done in Invoice and not in Payment Request. As we are not going to save gl entries in Invoice Screen, gl entries are saved only in Payment Request. We may end up in wrong SFC calculation as

expense amount will not reflect correct amount. How to handle the gl entries?

 Answer : Generate temporary gl entries and do not save these entries and check SFC based on these values. Create one sample role like OLE-SYS-USER with one user and forward the document to that user.

3) How to handle document linkage identifier,...where we need to have the linkage identifier. What identifier needs to be stored in Invoice and Payment Request.

Answer : Store AP_PUR_DOC_LNK_ID generated for PO document in OLE_AP_INV_PO_ITM_T table. Generate new AP_PUR_DOC_LNK_ID and save it in OLE_AP_INV_T table.

Store AP_PUR_DOC_LNK_ID generated for invoice in AP_PMT_RQST_T table, if Payment Request is created through Invoice Screen. If Payment request is created through Payment Request  Screen, then store AP_PUR_DOC_LNK_ID generated for PO document.

4) Payment Terms Calculation...How to handle the Payment Terms Calculation in Invoice and Payment Request Screen.

Answer : OLE currently does not take into account the Payment Terms discount amount at the document level. The info is captured in PDP extract process, when the actual cheque is cut-off.

5) Payment Info.. From where and how the information is fetched?

Answer : The info is fetched after PDP Process is run. Not required in Invoice as PDP Process is done only in Payment Request Screen.

Date : 13-July-2013

1) Accepting negative value in invoice document should result in creating vendor credit memo or the Invoice / Payment Request documents should allow negative values ?

If so how accounting data should be posted concern accounts?

2) Requirement is Extract date should be added to PDP_PROC_T : Process Date (PROC_TS column) is available in PDP_PROC_T table. Is that a extract date or do we need to create new field as extract date in that table

3) The scope for this 1.0 is only the insertion of data into PDP tables or it includes extraction of scripts and services also?  

4) How the invoice / Payment Request Documents should process the prorating ?