Sales Distribution
From UG
(→Changes to Sales Invoices) |
(→Analysis and Solution) |
||
| Line 27: | Line 27: | ||
=== Core logic === | === Core logic === | ||
| - | + | Currently if invoice is issued against one or more grouped CTs we associate that sales information with entire group. | |
| + | |||
| + | That is how it is stored in database and that is how it is available in reports. | ||
| + | |||
| + | New logic will associate sales charges with individual CTs. This info will be stored in DB and become available in reports. | ||
| + | |||
| + | Now each CT will have its own gross margin and P/L. | ||
All new logic is used for both Sales Invoices and Credit Notes. | All new logic is used for both Sales Invoices and Credit Notes. | ||
| + | |||
| + | |||
| + | |||
| + | === Changes to Sales Invoices === | ||
Interface for issuing sales invoice '''for grouped CTs''' will change. | Interface for issuing sales invoice '''for grouped CTs''' will change. | ||
| + | |||
| + | Decision related to what and how to associate amounts with specific CTs will be done for each line item in TOC table. | ||
| + | |||
| + | Each line is linked to unique charge code (CC). | ||
| + | |||
| + | CC can be of two types "Master"(M) or "Individual"(I). I call it "M/I class" | ||
| + | |||
| + | CC Admin defines default M/I class. This value can be overwritten by operator in TOC at the moment of issuing invoice. | ||
| + | |||
| + | CC Admin also defines unique default CBV type (Chargeable Weight vs Gross Weight vs CBM vs CT Count) for each charge code. This type dictates how to distribute charges entered across selected CTs. We use similar logic for PIs. | ||
| + | |||
As now system will ask user to "Select CTs in the group". User will select a subset of CTs in the group relevant to this invoice. | As now system will ask user to "Select CTs in the group". User will select a subset of CTs in the group relevant to this invoice. | ||
| Line 44: | Line 65: | ||
2/ Sales amounts will be assigned at the moment of creating/saving Invoice. | 2/ Sales amounts will be assigned at the moment of creating/saving Invoice. | ||
| - | + | ==== Change in parameters ==== | |
| + | |||
| + | Change in parameters that define distribution will '''NOT''' force re-distribution (different from PI philosophy): | ||
* CTs can be added or removed from group/Master | * CTs can be added or removed from group/Master | ||
* weight, CBM, chargeable weight could all change | * weight, CBM, chargeable weight could all change | ||
Revision as of 03:54, 24 July 2013
Contents |
Info
This is a project.
It will impact different components of CT2.
It will have multiple phases.
Parent mantis: 0004230.
Business Need
Main business need Is to accommodate distribution of sales amounts across the CTs in the group. This will allow to report on sales amounts and gross margin on individual CT level.
Currently if CTs are grouped into GRP group sales figures and gross margin figures are only available for entire GRP and not individual CTs that are part of given group.
Main idea on how to manage this distribution is similar to what we are doing on purchase side. But not all logic is identical.
First component that will benefit from this is KPIs module.
In the future we can use this in other reports.
Analysis and Solution
Core logic
Currently if invoice is issued against one or more grouped CTs we associate that sales information with entire group.
That is how it is stored in database and that is how it is available in reports.
New logic will associate sales charges with individual CTs. This info will be stored in DB and become available in reports.
Now each CT will have its own gross margin and P/L.
All new logic is used for both Sales Invoices and Credit Notes.
Changes to Sales Invoices
Interface for issuing sales invoice for grouped CTs will change.
Decision related to what and how to associate amounts with specific CTs will be done for each line item in TOC table.
Each line is linked to unique charge code (CC).
CC can be of two types "Master"(M) or "Individual"(I). I call it "M/I class"
CC Admin defines default M/I class. This value can be overwritten by operator in TOC at the moment of issuing invoice.
CC Admin also defines unique default CBV type (Chargeable Weight vs Gross Weight vs CBM vs CT Count) for each charge code. This type dictates how to distribute charges entered across selected CTs. We use similar logic for PIs.
As now system will ask user to "Select CTs in the group". User will select a subset of CTs in the group relevant to this invoice.
....
1/ Changes to TOC:
- add M/I selector as in PI; define default
- add CBV selector as in PI; define default
- for I-charges add CT selector (from CTs selected when started invoice)
2/ Sales amounts will be assigned at the moment of creating/saving Invoice.
Change in parameters
Change in parameters that define distribution will NOT force re-distribution (different from PI philosophy):
- CTs can be added or removed from group/Master
- weight, CBM, chargeable weight could all change
Phases
Phase 1 will cover the following SOWs: 1, 2, 3.
Phase 2: TBD.
See Also
SOWs
SOW 1 Core logic and changes to Sales Invoices
mantis:
spec: implement these 2 sections - see below
SOW 2 Update KPI logic accordingly
We can now change all logic (cost logic, association, inclusion, etc) to be on per CT vs per Group basis.
Details pending discussion with Sasha.
SOW 3 Pre-calculations
This is pending investigation and can be dropped/postponed.
SOW 4 Modify non KPi reports to show per CT sales amounts for grouped CTs
This is phase 2.
Spec: TBD.
