258829
258829 SS-7MEK47 Alignment of INT_MSG
Version :
|
Copyright OBS Logistics © 2009
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
Not Applicable - Internal Changes
Solution
Not Applicable==
Scope
This change will be applied to system version 10.5.0 on CONTST, DSGTST, IIBTST, EMTTST, POCTST, JRLTST, UKSTST and once approved CONPRD, DSGPRD, IIBPRD, EMTPRD, JRLPRD, UKSPRD.
SET-UP
Pre-Requisites
None
FUNCTIONAL DESCRIPTION
There are 4 different versions of INT_MSG across the different database instances. The objective of this alignment is to create one generic version which will compile on all instances and still provide the current functionality to all instances. Going forward the one generic version will be developed and released to all instances.
There are several steps which will be taken to achieve the alignment
- Identify the differences
Consumer Network version is many versions ahead of all of the other versions. It was decided that this version will be ignored until a generic version of the other instances is established. The matrix above shows the differences in INT_MSG across the ‘other’ database instances.
Once an aligned version has been created for the ‘other’ versions this will be compared with the Consumer Network version.
- Differences are categorised as Issues or Implements.
No code will be discarded, multiple versions of the same function may exist within the Generic package. System Parameters will be used to control which version of the code is run. There will be many System Parameters , covering each area where the code is slightly different across the instances and we are unable to establish which version suits all.
Implements are those changes that can be applied to the generic version of INT_MSG without causing any change to its functionality
Issues are code differences which do impact functionality. In these cases it has been agreed to include all versions of the code and use a system parameter to control which version is run,
- Dependancies
Some code will not compile in certain instances because of dependencies missing from the instance. Dependancies include tables and fields. Part of the alignment process will be to ensure all dependencies exist in all instances.
In addition to the differences detailed previously, a new version of INT_MSG called INT_MSG_IIB has been created as part of a recent RIO. This new version of the code must be integrated into the generic version. The majority of the procedures and functions are new, so can be easily added. There is reference made to a table INT_ORDER_IIB which only exists on the IIB database and must be created in all instances.
Document History
| Initial version |
Authorised By
| Matt Crisford | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
