Billing Required Report

From UG

Revision as of 17:15, 19 January 2015 by Andrei (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Contents

Info

Parent Mantis

0003192: (OpsRep): Billing Required Report

Scope of this wiki

Covers one report.

Version 1

SOW 1

Operators are responsible to check the gross margin of each shipment. To assist with this, it is requested a dashboard report (or email option) be created that can alert operators of any shipments showing no profit or a negative profit.

Business requirements - Phase 1

Report should be added to the report scheduler - action required reports

Report should have email and dashboard option

Include all shipments that have a P/L of 0 or less

This should include:

  • CT's with no sales invoices and no purchase invoices.
  • CT's that the total sales invoices are lower then the total purchases invoices.
  • CT's with purchases invoices and no sales invoices.
    • Basically the only shipments that should NOT be included on this report are shipments that the total sales invoices that are greater then the total purchase invoices.

Exclude any shipments that do not have an actual arrival date confirmed

Summary of Hard coded conditions

Include all shipments that:

  • have a P/L of 0 or less AND
  • have an actual arrival date confirmed OR created more than 120 days ago

Section added: --Alex 18:24, 6 December 2011 (EST)

Filters

Filters are to be defined in next phase

Output

Level One

Dashboard to display

  • Report Name

  • Counter = the total amount of loss in USD.
    • The number should be a hyperlink to the next level.

For example
If the report lists:
CT# 123456  P/L -123.00
CT# 234567  P/L    0.00
CT# 345678  P/L    0.00
CT# 456789  P/L  -22.00
CT# 567891  P/L    0.00
Total loss:     -145.00 
The dashboard should show:
Billing Required Report:  -145.00
Level Two

To be defined in next phase

Level Three

In first phase, clicking the hyperlink should open html report.

  • This report should be downloadable to excel
Report Output Columns
  • CT number
    • as a hyperlink to the CT record
  • CT created on date
  • E0. Client Company
  • Origin Country
  • Destination Country
  • Mode Of Transport
  • Actual Arrival date
  • Total Profit/Loss amount

Example of output

Level One Output

File:Billing Required Report.JPG

Level Two Output

To be defined in next phase

Level Three Output
HTML Version

To be added

Excel Version

File:Billing Required Report - Excel Output.JPG

Version 2

SOW 2

Groupped CT case

This report should ONLY include the 1st or lowest CT record within the group. Not each of the CT numbers for the group.

Example:

GRP# 55763 CT# 123456 CT# 123457 CT# 123458 CT# 123459 CT# 123460

Report should show only CT# 123456

The P/L amount displayed on the report, should be the "group" P/L amount. The same amount that is displayed on the P/L tab in CT.

SOW 2a

This work was done under DR/KPI task: see DR_for_9_existing_Action_Required_internal_reports#One_more_AR_added_to_the_group

SOW 3

  • 0003203: (OpsRep): Billing Required Report (SOW 3)

Glossary

Mechanism to authorize a loss

Management would like the ability to be able to approve a loss on a specific CT or Group.

This "loss approval"" feature should be within the actual CT record, not part of the report.

MO has requested this be added in the ICOM section or P&L tab of the CT record.

  • In the ICom tab the user approving this loss can read the explanation of loss if posted in this section and will also be able to add a comment into this section.
  • In the P/L tab the user will view profit and loss history.

Once the loss is approved, the record should be removed from the report.

UI Design

File:Icom section.JPG

Add the above to the ICom tab

Main Use case (story)

  • Simon opens this report and clicks the CT hyperlink to see why this record has a loss. If he can not determine this by viewing P/L screen then he will read notes in ICom section to see if explanation is there.
  • After that he might:
    • post ICom note requesting explanation
    • approve Loss

CT can re-appear on this report

In the case that a new purchase invoice is assigned against a record or group, that has already been approved for a loss, the approval should automatically be voided by the system and record should again be added to the report.

It is a new loss and new approval is required.

A history of these actions should be recorded in Update Log.

Add this to Users Roles Admin

Ability to "Authorize a loss" should be added as an option to Users Roles Admin . It will be only granted to very small group of users. All other users should see this checkbox as read only.

Note to QA and BA
-----------------
"Authorize a loss" item should be linked to "Super Management" role or "Authorize a loss" role.
Both roles do not exist now.

Global Loss vs Office specific Loss

 !!!! This requirement was removed by Simon

Loss in Main P and L currency vs Loss in Additional P and L currency

See definitions here: P and L currency

If P/L in Additional P/L currency is defined and it is positive while corresponding P/L in Main P/L currency is negative or zero then do not consider that a Loss.

Example of perceived loss

File:Loss caused by currency.JPG

CT link to the Edit Not View

Hyperlinks in the Excel report should link to the “Edit” Not “View” visibility of a CT record.


Billing Required Start Date

Any shipments created prior to 5/1/2010 (Billing Required Start Date) should not be included on this report.

  • pls make it part of config file, do not hardcore.
  • post note to report UI and output: " shipments created prior to [Billing Required Start Date] are not included on this report"

History

0003192: (OpsRep): Billing Required Report (ver 1)

0003237: (OpsRep):Billing Required Report-Bug:Report should display the group P/L amount for any record that is part of a group (ver2))

User Guide

Config

File:Billing required.JPG

Lev 1 and 2

File:Billing Req Lev 1 and 2.JPG

Lev 3

File:Billing Req Lev 3.JPG

Output

File:Billing req - output.JPG

Business Logic

User Guide Status and SOW covered

Personal tools