ASN 20 Solution

From UG

Revision as of 18:25, 2 August 2012

Info

Preliminary Work

Add TMS E0 attribute

Currently "TMS solution" supports only one Client Company (E0) at a time - we can not send shipments to TMS that are identified by more than one E0 - this case is not defined - no code or business process exists.

We need to add parameter to the system that defines what E0 "is linked to" TMS currently. This will help in :

• reporting
• validation (to make sure we do not send CTs with other E0s to TMS)

Add Role Type attribute: Built In vs User Defined User Roles

We have to distinguish between Built In and User Defined User Roles.

Also this should make it obvious for the user - what role is Built In and what is User Defined.

User Defined Role is a role that can be created and fully defined by user through Open Admin > Security > User Roles.

Add column

Add Generic Shipper and Generic Planner Built In User Roles

Currently the only Shipper and related Planner roles defined in the system are "EA Shipper" and "EA Planner". These are built in roles.

They currently support only Elizabeth Arden (EA) Domestic Trucking workflow.

Since it is intention to increment/change EA workflow and also to add support for any Client Company without distracting existing operations it is suggested to create two new built in roles "Generic Shipper" and "Generic Planner" that would fully satisfy ASN 2.0 requirements. Deploy this into production. After release we would have:

• EA Shipper
• EA Planner
• Generic Shipper
• Generic Planner

At that point In production we could:

• start creating new Generic Shippers/Planners for any E0
• transfer all users from EA Shipper to Generic Shipper
• transfer all users from EA Planner to Generic Planner
• remove EA Planner, EA Shipper (in the following Rel to Prod)

Important Note to Developer
------------------------
Code should be re-used by both EA and Generic Shipper/Planners. 
We should not create separate similar code for EA vs Generic roles.

SOWs and Change Requests