Business Requirement Specification

Business Requirement Specification

<p> Business Requirement Specification</p><p>Cost Generation Modification 2 3 S e p t e m b e r , 2 0 1 3</p><p>TSL Taipei Company/User Mr. Edward and TPE ITD</p><p>ID Tharanga Perera</p><p>Copyright © Information Dynamics LLC, 2018 www.infodynamic.net</p><p>Information Dynamics 1 CONTENTS</p><p>1. DOCUMENT MANAGEMENT...... 3</p><p>1.1. DOCUMENT CONTROL...... 3 1.2. REVISION HISTORY...... 3 1.3. FINAL APPROVAL AND SIGN OFF...... 3 2. OVERVIEW...... 4 3. MORE DETAILS...... 4</p><p>Information Dynamics 2 1. Document Management</p><p>1.1. Document Control Author Tharanga Perera Prepared on 23/09/2013 Last Updated on 23/09/2013 File Path File Name Cost Generation Modification.doc</p><p>1.2. Revision History Version Release date Author Summary of Changes Reviewer Name Ver No dd/mm/yy Name Description of changes Name of all reviewers 1</p><p>1.3. Final Approval and Sign off Name Title Signature Date </p><p>Information Dynamics 3 2. Overview</p><p>Current cost calculation will take the from move’s “Current location” field and then will match against the “Port/Terminal” in the tariff But there are some cost items where we need to take the tariff based on the To move’s “Current location”, therefore system should be able to identify whether to take from move’s location or to move’s location by each charge type Also the current rule of fetching the tariff will be irrespective of the vender. In another word, vender is not an input parameter to fetch the tariff (System consider that one location has one vender). But there are some charges where we need to fetch based on the location + Vender and therefore we need to have some rule built in the system to find the correct vender</p><p>3. More Details</p><p>Existing “Move cost link” program will be modified by adding 2 new parameters</p><p>Location rule – There should be to values for the selection From Move – F To Move – T Mandatory and default value should be “F”</p><p>Information Dynamics 4 AP Rule</p><p>Non mandatory and LOV should be from common code master where common type equal to “C_AP_RULE”</p><p>Cost generation program needs to be modified to consider the above changes In Tariff fetch, Point 1 First check whether the “Location Rule” is set to “F” or “T” If the location rule = “F” then Take the from move’s current location to check the tariff If the location rule = “T” then Take the To move’s current location to check the tariff</p><p>Point 2 Now check whether any value is available in the “AP Rule” field If the AP rule = “OPR” and location rule = “F” then Take the from move’s operator code from EQC and then take the corresponding AP code from feeder operator master and check against the port tariff’s vender code If the AP rule = “OPR” and location rule = “T” then Take the To move’s operator code from EQC and then take the corresponding AP code from feeder operator master and check against the port tariff’s vender code</p><p>Information Dynamics 5 Example 1 Location rule is set to “From Location” and AP rule is blank</p><p>Example 2 Location rule is set to “To Location” and AP rule is set to “OPS”</p><p>------EOF------</p><p>Information Dynamics 6</p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us