MasterData - The Art of Flower -- Coeur dAlene _ Spokane Wedding .xls
Document Sample
LSG Impact Analysis
LSG Impact Assessment (by table)
Chg Phase to Phase to
Priority K eyField FieldType Table Session Description Convention Current Recom m ended LSG Usage LSG Analysis Alternative Use/ Com m on Multi-site Analysis Multi-site Recom m endation Suggested Define Define
for LSG Convention Data
No specific convention followed. ok Usage is ok. Numeric Non- Possible overlap of multi-site data OK
H Address Formats Alphanumeric - 3 chars tccom135 tccom4535m000 Address Formats N [NONE] Numeric Non-intelligent Numeric-non-intelligent intelligent is a good use for this minimized in shared environment.
table. no
7-series is used basic on ADD Use a number group with First Free Unique multi-site address id is Create convention that does not
Number Group. Numerical Counter. Numbers that indicates the Baan available within this 9-digit alpha- allow for duplicates. 2-digit country
logistic company number as the first numeric field. Should be able to code, plus 3-digit site code, plus 4-
H Address Alphanumeric - 9 chars tccom130 tccom4530m000 Addresses N [NONE] [FIRST NUM GRP]
free number. By this way sorting by conform to a standard, else digit counter.
every site in a shared environment duplicate address ids may exist.
is easy. yes
LSG is using this area code naming ok All sites could use the same Convention could be set for Multi- Conform to USA convention. Ok
convention as straight forward 3 conventions in a shared site data according to USA method.
digit numeric starting from 000 thru environment.
H Area Alphanumeric - 3 chars tcmcs045 tcmcs0145m000 Area Y 604 [N/C]
999 with the description that which
is self explanatory.
no
No specific convention followed. Use a convention with 6 characters. Duplication of data, by language. A master data set could be
1st and 2nd char to indicate the Could be standardized. maintained. Ok for now due to 2
country as United States(US), planned records at LSG. Room for
Canada(CA), etc, and 3rd char as Growth.
city such as Hercules(H),Irvine(I)
H Availability Type Alphanumeric - 6 chars tcccp001 tcccp0501m000 Availability Types N [NONE] USHTR1 and 4th and 5th char as resource
category for Transport(TR),
Delivery(DE), Maintenance(MA),
Operation(OP), Service(SE),
Holiday(HO), and 6th char for
running numbers 1 thru 9. no
used for business partner W ill not be comprehensive enough Evaluate other sites. Conventions do not overlap, but Ok
description lookup - mapped to for multi-site adoption, but ok since could. Likely we will keep adding to
Abbr. +
H Business Partner Type Alphanumeric - 3 chars tcmcs029 tcmcs0129m000 Business Partner Types Y [N/C] legacy systems codes. we can keep adding to the data set. data set.
numeral id
no
Single entry Appears to be unused. Is this defined for other sites? Southern Europe has the best Recommended convention is 1-digit
"ZZZ - Undefined Business Partner" method (9-digit semi-sequential alpha plus 8-digits sequential
alpha-numeric), but they also have numeric.
H Business Partner Alphanumeric - 9 chars tccom100 tccom4500m000 Business Partners Y [NONE]
the most business partners. It could
be possible for all sites to adopt this
method. yes Now Corporate Purchasing
No specific convention followed. Use a convention with 6 characters. Current mismatch of data types and Use a convention with 6 characters.
Codes based on Manufacturing 1st and 2nd char to indicate the usage. 1st, 2nd, and 3rd char to indicate
groups. country as United States(US), site (LS1). 4th, 5th and 6th char
Canada(CA), etc, 3rd char to sequential numeric. This helps to
indicate group as LSG (L), CDG distinguish in a shared environment.
H Calendar Code Alphanumeric - 9 chars tcccp010 tcccp0510m000 Calendar Codes N [NONE] USLH01 (C), and shared (S), 4th char as city
such as Hercules(H),Irvine(I) and
5th char through 6th for running
numbers. This helps to distinguish
in a shared environment.
yes
No specific convention followed. Use a convention such as 6 char Various change reason codes could Should standardize in order to
alphanumeric. Examples - first 2 be consolidated, but wide and consolidate statistics on changes.
char indicaing the function such as varied. Suggested use: 6 char
Planning (PL), Sales (SL), alphanumeric. First 2 char indicaing
Purchasing (PU), etc, and the 3rd the function such as Planning (PL),
through 5th char indicating the type Sales (SL), Purchasing (PU), etc,
of change reason. Examples and the 3rd through 5th char
change (CHG), delete (DEL), and indicating the type of change
H Change Reason Alphanumeric - 6 chars tdpur097 tdpur0197m000 Change Reason Code N [NONE] PUCHG1
the last a numeric counter for reason. Examples change (CHG),
subcategorizations that may be delete (DEL), and the last a numeric
required Using these change codes, counter for subcategorizations that
there is another session that gives may be required
the ability to specify what types of
changes are taking place such as
cancel, delete, add, etc.
yes Now
No specific convention followed. Use a convention such as 6 char all are probably language-specific, Should standardize in order to
alphanumeric. Examples - first 2 and so would have to be consolidate statistics on changes.
char indicaing the function such as standardized on English, but could Suggested use: 6 char
Planning (PL), Sales (SL), be standardized. alphanumeric. First 2 char indicaing
Purchasing (PU), etc, and the 3rd the function such as Planning (PL),
through 5th char indicating the type Sales (SL), Purchasing (PU), etc,
of change reason. Examples and the 3rd through 5th char
change (CHG), delete (DEL), and indicating the type of change
H Change Reason Alphanumeric - 6 chars tdsls097 tdsls0197m000 Change Reason Codes N [NONE] SLCHG1
the last a numeric counter for reason. Examples change (CHG),
subcategorizations that may be delete (DEL), and the last a numeric
required Using these change codes, counter for subcategorizations that
there is another session that gives may be required
the ability to specify what types of
changes are taking place such as
cancel, delete, add, etc.
yes Now
LSG is using a multi-char coding All sites could use the same Various change types could be ok
convention for additions,deletions, conventions in a shared consolidated, but are language-
H Change Type Alphanumeric - 6 chars tdpur098 tdpur0198m000 Change Types Y ADD [N/C]
cancellations order, cancel order environment. specific and varied.
lines, etc. no II
LSG is using a multi-char coding All sites could use the same Could be standardized, but in ok
convention for additions,deletions, conventions in a shared English.
H Change Type Alphanumeric - 6 chars tdsls098 tdsls0198m000 Change Types Y ADD [N/C]
cancellations order, cancel order environment.
lines, etc. no II
Specifc data set is being used. Good data set but is it all ok - but will possibly need to expand Conventions could be normalized. If ok - but will possibly need to expand
encompassing data set. standardized, many sites would be data set.
H Cost Component Alphanumeric - 8 chars tcmcs048 tcmcs0148m000 Cost Components N [NONE] Master List
affected. All are language-specific.
no II
LSG is using the 2-digit ISO 3166 Good data set. All sites could use the same Either the 2- or 3-char ISO standard Use 2-char ISO country code.
standard. This will be the corporate conventions in a shared should be used here. No reason to
approved country code standard. environment. have duplicate sets among sites.
May have to re-migrate other sites
H Countries Alphanumeric - 3 chars tcmcs010 tcmcs0510m000 Countries Y [ISO] [N/C] down the line.
no
Page 1
LSG Impact Analysis
LSG follows ISO standard with 3 Good data set. All sites could use the same no conflict apparent. Sites should adopt this convention.
char upper case. conventions in a shared
environment.
H Currencies Alphanumeric - 3 chars tcmcs002 tcmcs0102m000 Currencies Y [ISO] [N/C]
no
For work centers, 1st char indicates * Why have lookup for chars 2 & 3? All sites could use the same naming Largely, the descriptions for this Need standard nomenclature for
the group such as Instrumnet, Just use values. convention for work centers, and field are overloaded with redundant multi-site. 1-digit for type of
Chemicals, etc, 2nd, 3rd indicates * Use standard 4-char code for the rest should be standardized. info. We need to ensure we department is okay plus 3-digit site
the work center such as 01 for Assembly (ASBY), Testing (TEST), standardize the naming convention code, plus 2-digit numerical
EM1, 02 for EM2, etc, and last 3 etc. as we will be sharing this table. counter.
char indicates Assembly,
Packaging, Testing ,etc., with a
H Department Alphanumeric - 6 chars tcmcs065 tcmcs0565m000 Departments N [NONE] N/C
running number from 001 thru 999.
For all other departments such as
Accounts, Purchase, Sales, the first
alpha is taken followed by 3
numeric running digits such as
A001 - for Accounts.
yes Now II
LSG follows simple naming All sites could use the same All sites seem to be referencing the Ok for now. Should standardize to
convention such as DIS-Discount, conventions in a shared same classifications. Should USA standard to create global list.
H Discount Codes Alphanumeric - 3 chars tcmcs021 tcmcs0121m000 Discount Codes Y DIS [N/C]
REB-Rebates and COM- environment. standardize naming convention.
Commissions. no II
No consistent coding convention is Use employee serial numbers Unique multi-site employee id may Using Login ID is okay so long as
followed. Employee ID defined in (restrict to 4 digits) prefixed with 2 be difficult to attain with a 6-char the id is derived from a source DB
Baan today are mixed with generic character indicating the country data field. This could be that does not allow duplicates
H Employee Alphanumeric - 6 chars tccom001 tccom0501m000 Employees N [NONE] US1234
#s and employee serial #. code such as US, CA, etc. This standardized though. (Corporate systems - Peoplesoft)
helps to distinguish in a shared
environment. no
Three distinct abbreviations. Language-specific, but good Evaluate other sites. distinct naming conventions, could Ok for now, but need to create fixed
convention. be conformed. data set.
H Business Partner Group Alphanumeric - 3 chars tfacp001 tfacp0110m000 Financial Business Partner Groups Y EMP [N/C]
no II
LSG is following a naming All sites could use the same Three distinct conventions, not Ok for LSG use. Room for Growth
convention such as 3 char alpha conventions in a shared language-specific. although should define for phase II.
H Invoicing Method Alphanumeric - 3 chars tcmcs055 tcmcs0555m000 Invoicing Methods Y DOM [N/C] indicating the area such as DOM - environment.
for Domestic and SUB - for
Subsidiaries. no II
LSG is using first 3 digit to * Division Overloading by Country? All sites could use the same Conventions are not in accordance. Likely we will want to define Item
represent the division such as conventions in a shared USA's is the most clear, but this Groups at a Regional Level, and
Instrument or Chemical. For environment. convention may not be flexible therefore convention is ok.
example, IRM for Instrument Raw enough to encompass all sites'
H Item Group Alphanumeric - 6 chars tcmcs023 tcmcs0123m000 Item Groups Y IRM001 [N/C]
Material and CRM for Chemical needs.
Raw Material and followed by 3 digit
sequential running number i.e.,
IRM001, CRM001, etc. no II
LSG is using this but not consistent A 6 char coding convention can be Not used in CE, and mixed in SE. Ok until further functional definition
in coding convention. However, followed in a shared environment USA method is language-specific,
there are several groups/categories such as 1st 3 char of the but clear. Should be able to
to indicate the line of business of business/profession and 2nd, 3rd conform methods for multi-site
either a supplier or a customer. This char for sub-division of the business adoption
H Line of Business Alphanumeric - 6 chars tcmcs031 tcmcs0131m000 Lines of Business N [NONE] DISHA1
is used for reporting historical and the 6th char as a running
and/or statistical data for a given number 1 thru 9. Examples -
supplier, customer or employee DISHA1 - Distributor for Hardwares,
falling under the same line of DISSO1 - Distributor for Softwares,
business. etc. no II
LSG is following a naming It is strongly recommended to use All three conventions are very close Standardize on English
convention such as 3 char alpha the same terminology in a shared to each other. However, they are Abbreviations. Keep LSG proposal
indicating the module for environment since the First Free language-specific. Perhaps we for definition of business model.
H Number Group Alphanumeric - 3 chars tcmcs051 tcmcs0151m000 Number Groups Y PUO [N/C] transactions. Examples - PUO for Numbers is the one that will make could standardize on English?
Purchase Orders, CON for difference between sites.
Contacts, SAO for Sales Orders,
etc. no
LSG is not using this price group * Are other sites using this table? All sites could use the same Appears to match. Should adopt SE Ok for LSG. Will define global use
and hence coded as NA for Not conventions in a shared method with language nuetral in Phase II
H Price Group Alphanumeric - 6 chars tcmcs024 tcmcs0124m000 Price Groups N NA [N/C]
Applicable as the field value is environment. convention.
mandatory in Item Master. no II
LSG is using 3 char alphanumeric All sites could use the same for Looks to be three distint type of Ok until further functional definition
such as CON - for Consumables, better sorting or reporting purposes. lists, but could be related. Likely a
H Product Class Alphanumeric - 6 chars tcmcs062 tcmcs0162m000 Product Classes Y FRT [N/C] FRT - for Freight Charges, ACC - data mismatch, and conforming
for Accessories, etc. would be difficult, unless this table
is repurposed no II
LSG is using a 4 digit numeric * 9000 enough? All sites could use 4-digit numbers Could be standardized to USA Ok for LSG. Need to ensure non-
coding convention starting from with clear description to distinguish convention, not language-specific duplication and therefore should
1000 thru 9999 with appropriate the product lines. obtain a master data set from
H Product Lines Alphanumeric - 6 chars tcmcs061 tcmcs0161m000 Product Lines Y 7833 [N/C]
description that which is self functional owner.
explanatory. This is based on BOSS
system data. no II
LSG follows a convention with 1 All sites could use the same Looks to be a naming convention Ok until further functional definition
digit alpha to indicate the number of conventions in a shared issue. However CE and USA use
days required for shipping in the environment. letter convention. Could be
H Product Type Alphanumeric - 3 chars tcmcs015 tcmcs0115m000 Product Types Y 1 [N/C] description. language-specific naming issues.
no II
LSG follows specific naming All sites could use the same This field is very inconsistent in Ok until further functional definition.
standard with 4 char upper case conventions in a shared naming convention. Could be Creating a standard data set is
such as "XNNN". X - stands for the environment. standardized, but language issues desireable to help increase clarity of
business function such as E- might arise. data and audit trail on the
H Reason Alphanumeric - 6 chars tcmcs005 tcmcs0105m000 Reasons Y F904 [N/C] Engineering, F-Finance, M- transactional-side (troubleshooting,
Materials, P-Planning, Q-Quality, S- financial integrations, etc).
Sales, V-Service, W-Warehousing,
etc., and the NNN is a running
number. no II
LSG is following the international All sites could use the same entries checked conformed to ISO Continue following ISO 3166
standards such as 2 char alpha for conventions in a shared 3166 Country/State/County codes naming convention
H State/Province Alphanumeric - 3 chars tcmcs143 tcmcs1143m000 States/Provinces Y [ISO] [N/C] a given state in a country. environment. (Country/State/Province/County)
no
LSG follows the ISO standard for In a shared environment, all sites Three different conventions for two Ok.
the country code as mentioned can follow the same naming distinct methods. Could be a
above, and there is a blank tax code convention as ISO standards for mismatch, since USA is using a
H Tax Code Alphanumeric - 9 chars tcmcs036 tcmcs0137m000 Tax Codes Y [ISO] [N/C]
defined for no tax sales or country codes, blank tax code and VERTEX entry. However,
purchases and VERTEX as another whatever software is used to handle convention could be conformed.
tax code. taxes such as VERTEX. Also, this is the container no
Page 2
LSG Impact Analysis
LSG follows naming convention as All sites could use the same Should be global in nature and ok to Ok. Implement LSG proposed
P-Payables and R-Receivables and conventions in a shared standardize across the enterprise. codes and standardize data set for
XX - For payment discounts. environment. phase II. Putting P or R in front is
H Terms of Payment Alphanumeric - 3 chars tcmcs013 tcmcs0513m000 Terms of Payment Y P09 [N/C] not mandatory to set up Payment
Terms, but it is a good practice
nonetheless in order to keep
departmental flexibility. no II
There is a time zone naming All sites could use the same Possible overlap of multi-site data. Time Zones are per ISO standards.
H Time Zone Code Alphanumeric - 3 chars tcemm100 tcemm1100m000 Time Zones Y [ISO] [N/C] convention. The convention is per conventions in a shared Should be standardized. Ok to use and keep as approved
the ISO standards. environment. data set. no
Alpha convention employed. Other conventions are used around All sites could use the same Could be normalized, but is W e should start with the LSG
the world, thus a migration effort will conventions in a shared language-specific, so convention proposed codes and then finalize
H Transaction Type Alphanumeric - 3 chars tfgld011 tfgld0511m000 Transaction Types Y AAP [N/C] be required by sites adopting this environment. would be in English. the data set in Phase II. Naming
business model. Convention is typical for Baan
implementation. Ok. no II
LSG follows one standard code i.e., All other site could follow, else Looks like most sites have a single Ok due to low volume of unit sets
001 for all units. every site can follow a unit set that code for units. This should be set to and numerical counter.
H Unit Set Alphanumeric - 6 chars tcmcs006 tcmcs0106m000 Unit Sets Y 001 [N/C] which indicates the Baan logistics one value for all sites.
company number as the unit set, in
a shared environment. no
LSG has a naming convention per All sites could use the same Some overlap of data, by letter Ok for LSG - appears to be ISO
H Unit Alphanumeric - 3 chars tcmcs001 tcmcs0101m000 Units Y [ISO] [N/C] ISO standards. conventions in a shared case, but ISO standard is adhered compliant. Should standardize
environment. to. Could be standardized further. entire data set in Phase II. no II
There is a w/h naming convention. We will need to ensure CDG We should extend the convention to Unique multi-site warehouse id is Need to discuss
naming conventions do not conflict accommodate CDG. Some w/hs available within this 6-digit alpha-
with LSG current plan - does not appear to be offices and should numeric field. Should be able to
H W arehouse Alphanumeric - 6 chars tcmcs003 tcmcs0503m000 W arehouses Y [NONE] [-]
appear to be a problem as an Alpha have the same number of digits (6). conform to a standard, else
(6-digit) convention is being used. duplicate warehouse ids may exist.
yes
LSG is following a coding All sites could use the same Best solution is CE, language- Ok for LSG. May want to
convention which is 3 char alpha conventions in a shared nonspecific. Could be adapted for standardize data set for Phase II
indicating as follows: 1st char environment. all sites.
indicates the type of transaction
such as I - for Issue, R - for
H Order Type Alphanumeric - 3 chars whinh010 whinh0510m000 W arehousing Order Types Y RDR [N/C] Receipts, etc, 2nd char indicates
starting warehouse such as D - for
Distribution warehouse, and the 3rd
char indicates the desitination
warehouse such as R - for Raw
Material warehosue. no II
Mostly 3, some 2-digit alphas. Will need to ensure unique (new) We should standardize to 3-digit to E-Item Groups will not drive Convention looks ok for LSG. May
H Engineering Item Group Alphanumeric - 3 chars tiedm001 tiedm0101m000 Engineering Items Groups N [NONE] 123 codes are added to data set not create consistency across all Baan functionality beyond sorting, etc, in want to standardize data set for
created by LSG implementation. sites. the Baan ERP system for BR. Phase II after further functional no II
definition.
Page 3
