Need help with a data mapping assignment.
Just need to match attributes to api’s
& identify which match & which do not. Basically identify the gap between them.
Let me know how much you want & we can discuss the price in private.
Dont worry, you will be well compensated
Thanks
————————————————-
Files attached.
Only the Data Mapping V0.1 is the one i created.
The 2 zip files contain the API’sSupplier Master data contains the attributes that need to be mapped to the API’s.The Account API’s should correspond to the Supplier facility attributes.
The Management API’s show the relationship between hierachy & supplier location.
I need to Map the files and identify the GAPS that exist between them.
So basically the Account file shows the facility information that can be in the entity table.
& Mgt file shows the relationships b/w hierachy (owner/responsible company) & supplier location.
I tried creating the file that i attached called data mapping but dont think its the way to go.
Let me know if you have further questions/comments/ concerns.
SQS USER
Steton Field | SUPPLIER COMPANY PROFILE | SUPPLIER FACILITY PROFILE | SUPPLIER CONTACT | COMMENTS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Control.RecordCount | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.UserID | Not defined in Supplier Master Data sheet | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.NamePrefix | Name Prefix | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.NameFirst | Contact First Name | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.NameLast | Contact Last Name | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Title | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Company | Responsible or Legal Owner ? | Parent Company / Facility Name | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Address1 | Physical, Postal or Billing ? | It has 4 fields: Address Line 1, Address Line 2, Address line 3 or Address line 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Address2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.City | City | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.MailStop | NOT SURE What does these element exaclty means | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.State | State or Province | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.PostalCode | Postal Code | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User. | Country | Country | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Phone1 | Phone # | Phone Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Phone2 | Only Single | Phone Number | Is it Mobile/Pager number or Emergency Contact | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User. | Fax | Fax # | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Email | Email Address | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.UserName | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.InitialPassword | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Password | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.Active | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.DownloadFolder | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.AdminNotifications | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.SuperUser | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.AppConfigName | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.WebLanguage | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.MALanguage | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfPrimaryAccounts.PrimaryAccount.AccountID | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfPrimaryManagements.PrimaryManagement.ManagementID | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ManagementIDs (OBSOLETE) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ManagementListIsDefinitive | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfManagements.Management.ManagementID | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.AccountListIsDefinitive | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfAccounts.Account.AccountID | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfAccounts.Account.DirectReportAccess | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.AuditListIsDefinitive | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfAudits.Audit.AuditReference | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.RoleIDs (OBSOLETE) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.RoleListIsDefinitive | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ListOfRecords.User.ListOfRoles.Role.RoleID |
SQS ACCOUNT
Control.AccountCount | ||
ListOfAccounts.Account.AccountId | Needs more description from Steton regarding the difference between Account.Account_____ and Account.Contact_____. | |
ListOfAccounts.Account.AccountName | Parent Company / Facility Name might be if it corresponds to SUPPLIER CONTACT | |
ListOfAccounts.Account.Address1 | Physica, Postal or Billing | |
ListOfAccounts.Account.Address2 | ||
ListOfAccounts.Account.MailStop | ||
ListOfAccounts.Account.City | ||
ListOfAccounts.Account.State | ||
ListOfAccounts.Account.PostalCode | ||
ListOfAccounts.Account.Country | ||
ListOfAccounts.Account.Phone1 | ||
ListOfAccounts.Account.Phone2 | ||
ListOfAccounts.Account.Fax | ||
ListOfAccounts.Account.Email | ||
ListOfAccounts.Account.UserField1 | Needs more clarification | |
ListOfAccounts.Account.UserField2 | ||
ListOfAccounts.Account.UserField3 | ||
ListOfAccounts.Account.UserField4 | ||
ListOfAccounts.Account.UserField5 | ||
ListOfAccounts.Account.UserField6 | ||
ListOfAccounts.Account.UserField7 | ||
ListOfAccounts.Account.UserField8 | ||
ListOfAccounts.Account.UserField9 | ||
ListOfAccounts.Account.UserField10 | ||
ListOfAccounts.Account.ContactName | Are the values same as ListOfContacts | |
ListOfAccounts.Account.ContactPhone | ||
ListOfAccounts.Account.ContactEmail | ||
ListOfAccounts.Account.ContactFax | ||
ListOfAccounts.Account.UserID | ||
ListOfAccounts.Account.DivisionID | ||
ListOfAccounts.Account.ModifiedDate | ||
ListOfAccounts.Account.Active | ||
ListOfAccounts.Account.ActiveDate | Supplier Since Date | Facility Since Date |
ListOfAccounts.Account.TimeZone | TIME ZONE | |
ListOfAccounts.Account.DaylightSaving | Daylight Savings Time | |
ListOfAccounts.Account.ManagementListIsDefinitive | ||
ListOfAccounts.Account.ListOfManagements.Management.ManagementID | ||
ListOfAccounts.Account.AuditListIsDefinitive | ||
ListOfAccounts.Account.ListOfAudits.Audit.AuditReference | ||
ListOfAccounts.Account.ReportAccess | ||
ListOfCustomFields.CustomField.UniqueKey | ||
ListOfCustomFields.CustomField.Value | ||
ListOfContacts.Contact.NameFirst | ||
ListOfContacts.Contact.NameMiddle | Contact Middle Name | |
ListOfContacts.Contact.NameLast | ||
ListOfContacts.Contact.Title | ||
ListOfContacts.Contact.Address1 | ||
ListOfContacts.Contact.Address2 | ||
ListOfContacts.Contact.MailStop | ||
ListOfContacts.Contact.City | ||
ListOfContacts.Contact.State | ||
ListOfContacts.Contact.Country | ||
ListOfContacts.Contact.PostalCode | ||
ListOfContacts.Contact.Email1 | Email Address | |
ListOfContacts.Contact.Email2 | ||
ListOfContacts.Contact.Phone1 | ||
ListOfContacts.Contact.Phone2 | Mobile / Pager Number | |
ListOfContacts.Contact.ContactType | Contact Type |
SQS MANAGEMENT
Is Management same as Supplier or Facility ? |
ListOfRecords.Management.ManagementID |
ListOfRecords.Management.ParentID |
ListOfRecords.Management.RootID |
ListOfRecords.Management.LogoID |
ListOfRecords.Management.LevelID |
ListOfRecords.Management.ManagementName |
ListOfRecords.Management.Address1 |
ListOfRecords.Management.Address2 |
ListOfRecords.Management.City |
ListOfRecords.Management.MailStop |
ListOfRecords.Management.State |
ListOfRecords.Management.PostalCode |
ListOfRecords.Management.Country |
ListOfRecords.Management.Phone1 |
ListOfRecords.Management.Phone2 |
ListOfRecords.Management.Fax |
ListOfRecords.Management.Email |
ListOfRecords.Management.UserID |
ListOfRecords.Management.UDF1 |
ListOfRecords.Management.UDF2 |
ListOfRecords.Management.UDF3 |
ListOfRecords.Management.UDF4 |
ListOfRecords.Management.UDF5 |
ListOfRecords.Management.UDF6 |
ListOfRecords.Management.UDF7 |
ListOfRecords.Management.UDF8 |
ListOfRecords.Management.UDF9 |
ListOfRecords.Management.UDF10 |
ListOfRecords.Management.AccountListIsDefinitive |
ListOfRecords.Management.ListOfAccounts.Account.AccountID |
ListOfRecords.Management.AuditListIsDefinitive |
ListOfRecords.Management.ListOfAudits.Audit.AuditReference |
>Supplier Attributes
column at the end of the worksheet. column at the end of the worksheet.
equired / ptional
Change Log Action COMPANY PROFILE
O . Should this attribute be required? Companies are related together in a hierarchical fashion. From a logical perspective, requiring this field means there must be a provided value even when the company is at the top of the hierarchy. . . WSI length is 0. % ownership” in the business definition.
from . O Will be a Droplist field. Character 200 Character 200 R -digit numeric data structure. For further information on how to allocate a GLN for each location, contact your local GS1 Member Organization.
13 field in Merllin-Cross Reference drop down list
Currently, the WSI only identifies suppliers that manufacture and move products to McD Restaurants through a D.C.
Numeric 5 3.It is important to ensure scope covers “ship points that move provides through a DC, or Forward Warehouse” (U.S.)
3. Modified business rule to include this concept.
O Character 6
Name
O This supplier could exist in multiple legacy/AoW application systems using different identification schemes. Character 1. Attribute added to cross-reference capabilities to all legacy/AoW systems. R Character 1 R or Business Area that manages the relationship with the Supplier Company.
Character 50 is responsible for managing the relationship. R Will be a Multi-select field. See
2
This worksheet contains all the Supplier Company, Supplier Location/Facility and Supplier Contact attributes identified to be included in the Supplier Master database
All the teams feedback has been consolidated into the
Change Log
The response to all feedback has been provided in the
Change Log Action
Field Name
R
O
Field
Definition
Business Rule or Standard
Attribute Type
Attr Len
Change Log Issue
SUPPLIE
R
Responsible
Company Name
An enterprise,also known as a parent corporation, that is responsible for this Company/Facility.
Will be a Droplist field.
Character
200
1
2. EYES length is
100
3
5
4. Rona has questioned the “
50
1. Changed this attribute to
Optional
Required
2. No Change – Since EYES will publish data to the Supplier MDM, the source field length can be smaller than the target field length.
3. No Change to Supplier MDM. The business rules for formating this attribute into a smaller length field will be determined during interface design.
4. Rona, can you provide a more clear definition of this field? It appears that two seperate relationships can exist between comapnies – one relationship to depict ownership between the business entities and another to depict responsibility of one business entity over another. Consequently, two seperate parent attributes will be created.Further discussions will occur in Novermber between Quality leads to determine best way to capture and store these relationships.
Legal Owner Company Name
An enterprise,also known as a parent corporation, that owns more than 50% of this Company/Facility.
1. This attribute is being created because it appears that two seperate relationships can exist between comapnies – one relationship to depict ownership between the business entities and another to depict responsibility of one business entity over another. Consequently, two seperate parent attributes will be created.Further discussions will occur in Novermber between Quality leads to determine best way to capture and store these relationships.
Company Name R
This is the legal name of the company.
* Use legal entity names and spelled out fully, acronyms are placed in brackets at the end of the name w/ no punctuation.
* To distinguish a facility name, can use the city within the name, must have a hyphen between facility name and location 1. WSI lengthis 50.
2. EYES length is 100.1. No Change to Supplier MDM . The business rules for formating this attribute into a smaller length field will be determined during interface design.
2. No Change to Supplier MDM. Since EYES will publish data to the Supplier MDM, the source field length can be smaller than the target field length.
Company GLN
A Global Location Number (GLN) is a unique and unambiguous number used to identify physical locations or legal entities.
The GLN has a
13
Numeric
1. This is a 50
character
1. No Change to Supplier MDM. Since Supplier MDM will publish data to Merlin, the source field length can be smaller than the target field length.
Company WSI Number
R for Ship-Point Locations that move products to a DC
The WorldWide Supplier Information number identifies a trading partner (i.e., Supplier, Distrbutor, Warehouse) used in the WSI system.
The WSI system allocates a 5 digit number between the ranges of 10000 and 49999.
1.WSI length is 5.
2. Not applicable to all products as I understand, and therefore would not want required.Hub
1. Changed attribute length to 5.
2. Changed conditional requirement to those ship points that move products through a DC. Suppliers that don’t move products through a DC, i.e., uniforms of restaurant furniture, would not require a WSI #.
Legacy Reference Code
Identification scheme used to identify this Supplier Company in a legacy or AoW application system.
This supplier could exist in multiple legacy/AoW application systems using different identification schemes.
25
1. Attribute added to cross-reference capabilities to all legacy/AoW systems.
Legacy Reference System
Identifies the application system referred to by the Legacy Reference Code attribute.
256
Supplier Status
Indicates the state of the Supplier in terms of whether it has been doing business with McDonald’s.
1.
There is a difference between the status of the supplier and the status of the markets where this supplier can do business (i.e., sell to). EYES, Steton and WSI all have a supplier Status code.
1. The Supplier Status attribute has been added to Supplier MDM at just the Supplier Company level.
2. The proposed list of valid values has been provided in a seperate. Request broader team to review and provide feedback.
Party Responsible for Relationship
The Area of the World,
Country
Will be a Multi-Selection List.
Quality Systems requires reporting of company and facility information by which business entity or Aow/Market manages them.
1. Merlin and Steton have indicated they need this information.
* Merlin leads have decided not to carry this information at the supplier company or supplier facility level because this it is managed at the product spec level. Quality will maintain this attribute in Steton.
2. I need clarification to whether this is AoW or Market or both
3. I need clarification on whether this attribute applies to Supplier Company and/or Supplier Facility.
4. I need confirmation that only one Market/
AOW
Business area like procurement or marketing can also be valid values.
Supplier Category
Indicates the type of product or service provided to McDonald’s
Supplier &
values. Character 50
2. Does this attribute apply to the Supplier Company or Supplier Facility or Both?
3.If Both(e.g., Supplier Company is a
Manufacturer, but a related Supplier Facility is a Warehouse) are there any business rules restricting what values the supplier facility can accept based on the value choosen for its parent company?
s as suppliers while Steton will contain Uniform suppliers.
2. Request feedback from the broader group.
3. Request feedback from the broader group.
R
and further categorizes the product or service being offered by the Supplier.
N/A
R
Date N/A
2. Optional in Steton
3. Does it change by status type?
2. No change to Supplier MDM. Request that Intertek begin collecting this data – it is simply the date the Supplier record was created.
3.Once entered, this date will never change.
Supplier Close Date
O
Date N/A
2. If the supplier is closed what should happen to all the supplier’s facilities? Should they automatically be closed also?
3. Attribute does not exist in Steton
2. Ask broader group for feedback.
3.Need to discuss impact with broader group.
Trading Market Areas
R
for Use In”.
In EYES, a Supplier can only be associated to one market.
Character 50
2.Merlin has stated this field is required. However, the question has been asked: is it possible to approve a supplier to do business with McDonald’s before knowing what markets they will be selling to? If this field is left as required the implication is a supplier data record can not be created until this information is known.
3. What is the value of logistical supplier types like Distribution Centers, warehouses, hubs…etc.? Should it be required only for Manufacturing locations?
4. Does this attribute apply to the Supplier Company and/or Supplier Facility record?
5. Multi-selection list must align to EYES.
2. Request McD Quality team member feedback.
3.Does this apply to only specific supplier categories? If so, then the business rule should be required for specific supplier categories. Request broader team feedback – should this attribute be required for all supplier categories?
4. Confirm whether this atribute applies to the Supplier Company and/or the just the Supplier Location. If the answer is both then must the values provided at the company level comprise all the values choosen at the supplier facilities?
5. The assumption is that EYES will be a source of all APMEA supplier companies, so the list of countries should align to EYES.
Trading Market Area Status
R
Will be a multi-select field. See
Trading Market Status
values. Character
2. This value can change over time. It could be France today and Germany could be added tomorrow. This suggests the information isn’t master data, but transactional in nature. The impact is that reporting may be incorrect (i.e., master data vs. transactional data).
3. Multi-selection list must align to Merlin.
2. Request broader team feedback: is this attribute master data? This attibute is master data. While it could be defined as transactional, somehow we need AOWs to be able to communicate to itself and to other markets as to the supplier company status. In reality, it will not change that much over the course of a year or a larger block of time. May change a bit in the beginning as we all settle into an open communication mode, but point-of-view is that it will settle down.
3. The values now align to Merlin.
Will be a Droplist field. See
Ethnicity, Minority & Gender
values. N/A N/A
2. Attribute does not exist in Steton
business rule was adjusted.
2. Need to discuss impact with broader group.
R for US-based companies for use in WSI system
N/A N/A 1. Clarification: this attribute is required for US Companies for use in the WSI system.
2. Attribute does not exist in Steton 1.Required business rule was adjusted.
2. Need to discuss impact with broader group.
R for US-based companies for use in WSI system
Will be a Droplist field. See Ethnicity, Minority & Gender values. N/A N/A 1. Clarification: this attribute is required for US Companies for use in the WSI system.
2. Attribute does not exist in Steton 1.Required business rule was adjusted.
2. Need to discuss impact with broader group.
O
Character 256
R
Character 25
.
2. EYES length is 20
3. Steton length is 25
Call prefixes depend on the caller, not the callee, and thus shouldn’t (in many circumstances) be stored with a phone number. If the database stores data for a personal address book (in which case storing the international call prefix makes sense), the longest international prefixes you’d have to deal with (according to Wikipedia) are currently 5 digits, in Finland.
As for suffixes, some PBXs support up to 11 digit extensions (again, according to Wikipedia). Since PBX extension numbers are part of a different dialing plan (PBXs are separate from phone companies’ exchanges), extension numbers need to be distinguishable from phone numbers, either with a separator character or by storing them in a different column.
1. Changed length to 25 to accomodate largest sized attribute.
#
O
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. Character 25
2. EYES length is 20
3. Steton length is 25
O
N/A N/A
O
N/A 1. This attribute exists in Steton, but is not currently being populated. 1. Remove attribute from Supplier MDM.
R
Character 100
O
100
2. WSI only contains one type of address – there is no distinction between a physical or postal address. Consequently, as a matter of convention the WSI system stores the P.O. Address into either address line 1 or 2.
2. These business rules will be implemented in the Supplier MDM-to-WSI interface.
O
Chacter 100
2. Address is not large enough to hold longer addresses. Consider for example:
Building Room 210, Martin House
Street Pauline Avenue
Industrial Estate Venture Industrial Estate
Road 504 Stokeport Road
2. Added address Line 3 & 4 for all address types in Supplier Company and Supplier Facility.
O
Chacter 100
for Physical Location
R
Character 100
2. Steton length is 100
for Physical Location
O
Will be a Droplist field. Character 2
for Physical Location
O
Character 15
2. EYES length is 10
3. Steton length is 15
2. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
R
The country name and associated reference code are based on ISO standards.
Character 50
2. EYES length is 30.
2. Further discussion is necessary to determine how to consistently format attribute into a smaller sized field when the applicable interface is developed.
for Physical Location
O
is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html
Character 3
O
Character 100
O
Chacter 100
O
Chacter 100
O
Chacter 100
O
Character 100
1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
O
Will be a Droplist field. Character 2 1. Is droplist feasible with all the states\provinces in each country WW? 1. This issue applies more to UI design than database design.
O
Character 15
1. Changed length to 15 because the longest international postal currently is 9 characters.
O
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. Changed length to 50 because the longest ISO country name currently is: South Georgia and the South Sandwich Islands, which is 44 characters.
O Code representing the Subdivision of a Country. Similar to US State or Canadian Province this code allows for other subdivisions like British Counties, French Departments and German Länders.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html
Character 3 1. Added attribute to accommodate and align with international standards.
O
Character 100
O
Chacter 100
O
Chacter 100
O
Chacter 100
O
Character 100 1. Steton length is 100. 1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
O
Will be a Droplist field. Character 2 1. Is droplist feasible with all the states\provinces in each country WW? 1. This issue applies more to UI design than database design.
O
Character 15 Steton length is 15. 1. Changed length to 15 because the longest international postal currently is 9 characters.
O
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. Changed length to 50 because the longest ISO country name currently is: South Georgia and the South Sandwich Islands, which is 44 characters.
O Code representing the Subdivision of a Country. Similar to US State or Canadian Province this code allows for other subdivisions like British Counties, French Departments and German Länders. Will be a Droplist field.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html Character 3 1. Added attribute to accommodate and align with international standards.
R
Will be a Droplist field. Character 200
2. Pending – does this attribute apply to supplier company facility or justjust supplier company?
Character 200
2. EYES length is 100.
3. WSI length is 50.
4. Rona has questioned the “50% ownership” in the business definition.
2. No Change – Since EYES will publish data to the Supplier MDM, the source field length can be smaller than the target field length.
3. No Change to Supplier MDM. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
4. Rona, can you provide a more clear definition of this field? This attribute is being created because it appears that two seperate relationships can exist between comapnies – one relationship to depict ownership between the business entities and another to depict responsibility of one business entity over another. Consequently, two seperate parent attributes will be created.Further discussions will occur in Novermber between Quality leads to determine best way to capture and store these relationships.
R
* Use legal entity names and spelled out fully, acronyms are placed in brackets at the end of the name w/ no punctuation.
* To distinguish a facility name, can use the city within the name, must have a hyphen between facility name and location Character 200
2. EYES length is 50.
2. No Change – Since EYES will publish data to the Supplier MDM, the source field length can be smaller than the target field length.
R A Global Location Number (GLN) is a unique and unambiguous number used to identify physical locations or legal entities.
Numeric 13 1. This is a 50 character field in Merllin-Cross Reference drop down list 1. No Change to Supplier MDM. Since Supplier MDM will publish data to Merlin, the source field length can be smaller than the target field length.
R for Ship-Point Locations that move products to a DC The WorldWide Supplier Information number identifies a trading partner (i.e., Supplier, Distrbutor, Warehouse) used in the WSI system. The WSI system allocates a 5 digit number between the ranges of 10000 and 49999. Numeric 5 1.WSI length is 5.
2. Not applicable to all products as I understand, and therefore would not want required. 1. Changed attribute length to 5.
2. Changed conditional requirement to those ship points that move products through a DC. Suppliers that don’t move products through a DC, i.e., uniforms of restaurant furniture, would not require a WSI #.
Legacy Reference Code O Identification scheme used to identify this Supplier Company in a legacy or AoW application system. This supplier could exist in multiple legacy/AoW application systems using different identification schemes. Character 256 1. Attribute added to cross-reference capabilities to all legacy/AoW systems.
Legacy Reference System Name O Identifies the application system referred to by the Legacy Reference Code attribute. This supplier could exist in multiple legacy/AoW application systems using different identification schemes. Character 256 1. Attribute added to cross-reference capabilities to all legacy/AoW systems.
Will be a Multi-Selection List. Character 50
2. Merlin and Steton have indicated they need this information.
* Merlin leads have decided not to carry this information at the supplier company or supplier facility level because this it is managed at the product spec level. Quality will maintain this attribute in Steton.
3. I need clarification to whether this is AoW or Market or both
4. I need clarification on whether this attribute applies to Supplier Company and/or Supplier Facility.
5. I need confirmation that only one Market/AOW is responsible for managing the relationship.
Business area like procurement or marketing can also be valid values.
Character 50
2. Does this attribute apply to the Supplier Company or Supplier Facility or Both?
3.If Both(e.g., Supplier Company is a Food Manufacturer, but a related Supplier Facility is a Warehouse) are there any business rules restricting what values the supplier facility can accept based on the value choosen for its parent company?
4. This field seeks to utilize the same attribute to contain two possible different categorizations – one for the supplier company level and one for the supplier facility level.
2. Request feedback from the broader group.
3. Request feedback from the broader group.
4. Merlin and SWA have a need to categorize both the supplier company as well as the supplier facility, so having an attrbute at both levels is necessary. However, it is not clear whther the possible values for each attribute are the same. Further discussions will be needed to determine if a signle lookup table can be utilized or whether two seperate lookup tables will be employed.
Will be a Multi-select field. See Supplier & Product Category values. N/A N/A 1. Will Merlin be using? 1. Remove attribute from Supplier MDM because per Vicki “In MERLIN the product category is derived by linking a supplier facility to a product spec via a sourcing approval. With that said, MERLIN does not need to receive Product Category from the Supplier MDM for food suppliers”
R
Date N/A
2. Does it change by status type?
3. Can Facility Since Date ever occur before the associated Supplier Since Date?
2.Once entered, this date will never change.
3. No, a supplier’s facility can never exist within Supplier MDM before the Supplier Since Date of the Parent Company.
Facility Close Date
O This life cycle evet represents the date a supplier left the McDonald’s system. Date N/A
2. If the status changed to cause a closed supplier to reopen, the associated attributes should be revalidate.
2. This feedback applies to any related business approval processes.
Trading Market Areas
R
Will be a Multi-Selection List. Describes where the Supplier can do business (i.e. country approved to sell to). Also indicates where the Supplier is “Approved for Use In”.
In EYES, a Supplier can only be associated to one market. Character 50 1. The original name of the field isn’t consistent with the type or usage of the data.
2.Merlin has stated this field is required. However, the question has been asked: is it possible to approve a supplier to do business with McDonald’s before knowing what markets they will be selling to? If this field is left as required the implication is a supplier data record can not be created until this information is known.
3. What is the value of logistical supplier types like Distribution Centers, warehouses, hubs…etc.? Should it be required only for Manufacturing locations?
4. Does this attribute apply to the Supplier Company and/or Supplier Facility record?
5. Multi-selection list must align to EYES.
2. Request McD Quality team member feedback.
3.Does this apply to only specific supplier categories? If so, then the business rule should be required for specific supplier categories. Request broader team feedback – should this attribute be required for all supplier categories?
4. Confirm whether this field applies to the Supplier Company and/or the just the Supplier Location. If the answer is both then must the values provided at the company level comprise all the values choosen at the supplier facilities?
5. The assumption is that EYES will be a source of all APMEA supplier companies, so the list of countries should align to EYES.
Trading Market Area Status R
Character 80 1. The original name of the field isn’t consistent with the type or usage of the data.
2. This value can change over time. It could be France today and Germany could be added tomorrow. This suggests the information isn’t master data, but transactional in nature. The impact is that reporting may be incorrect (i.e., master data vs. transactional data).
3. Multi-selection list must align to Merlin.
2. Request broader team feedback: is this attribute master data?
3. The value now align to Merlin.
R for US-based companies for use in WSI system Identifies the ethnicity of the company owers. A person’s ethnicity refers to cultural factors such as nationality, culture, ancestry, language and beliefs. Will be a Droplist field. See Ethnicity, Minority & Gender values. N/A N/A 1. Clarification: this attribute is required for US Companies for use in the WSI system.
2. Attribute does not exist in Steton 1.Required business rule was adjusted.
2. Need to discuss impact with broader group.
R for US-based companies for use in WSI system Identifies whether this company is owned by a minority. Will be a Droplist field. See Ethnicity, Minority & Gender values. N/A N/A 1. Clarification: this attribute is required for US Companies for use in the WSI system.
2. Attribute does not exist in Steton 1.Required business rule was adjusted.
2. Need to discuss impact with broader group.
R for US-based companies for use in WSI system Identifies which gender the companies owner belongs. Will be a Droplist field. See Ethnicity, Minority & Gender values. N/A N/A 1. Clarification: this attribute is required for US Companies for use in the WSI system.
2. Attribute does not exist in Steton 1.Required business rule was adjusted.
2. Need to discuss impact with broader group.
Character 256
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. character 25 1. WSI lengthis 15.
2. EYES length is 20
3. Steton length is 25 1. the ITU-T recommendation E.164 for the international telephone network (which most national networks are connected via) specifies that the entire number (including country code, but not including prefixes such as the international calling prefix necessary for dialling out, which varies from country to country, nor including suffixes, such as PBX extension numbers) be at most 15 characters.
Call prefixes depend on the caller, not the callee, and thus shouldn’t (in many circumstances) be stored with a phone number. If the database stores data for a personal address book (in which case storing the international call prefix makes sense), the longest international prefixes you’d have to deal with (according to Wikipedia) are currently 5 digits, in Finland.
As for suffixes, some PBXs support up to 11 digit extensions (again, according to Wikipedia). Since PBX extension numbers are part of a different dialing plan (PBXs are separate from phone companies’ exchanges), extension numbers need to be distinguishable from phone numbers, either with a separator character or by storing them in a different column.
1. Changed length to 25 to accomodate largest sized attribute.
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. character 25 1. WSI lengthis 15.
2. EYES length is 20
3. Steton length is 25 1. See (Phone #) above. Changed length to 25 to accomodate largest sized attribute.
Time Zone O Abbreviation representing the Time Zonein which this Supplier Facility belongs Will be a droplist field of the standard Windows timezones. One of 24 regions or divisions of the globe approximately coinciding with meridians at successive hours from the observatory at Greenwich, England. N/A N/A 1. This attribute exists in Steton, but is not currently being populated. 1. Remove attribute from Supplier MDM.
Physical Address Line 1 R This is the address of the Supplier’s physical location Character 100 1. WSI length is 35. 1. No Change to Supplier MDM. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Chacter 100 1. WSI length is 35.
2. WSI only contains one type of address – there is no distinction between a physical or postal address. Consequently, as a matter of convention the WSI system stores the P.O. Address into either address line 1 or 2. 1. No Change to Supplier MDM. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
2. These business rules will be implemented in the Supplier MDM-to-WSI interface.
Chacter 100 1. WSI length is 35.
1. No Change to Supplier MDM. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Chacter 100
Character 100 1. WSI length is 29.
2. Steton length is 100 1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Will be a Droplist field. Character 2 1. Is droplist feasible with all the states\provinces in each country WW? 1. This issue applies more to UI design than database design.
Character 15 1. WSI lengthis 15.
2. EYES length is 10
3. Steton length is 15
2. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. WSI length is 25.
2. EYES length is 30.
2. Further discussion is necessary to determine how to consistently format attribute into a smaller sized field when the applicable interface is developed.
Country Subdivision Code for Physical Location O Code representing the Subdivision of a Country. Similar to US State or Canadian Province this code allows for other subdivisions like British Counties, French Departments and German Länders. Will be a Droplist field.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html Character 3 1. Added attribute to accommodate and align with international standards.
Postal Address Line 1 O This is the main Supplier address used for all mail correspondance Character 100
Chacter 100
Chacter 100
Chacter 100
Character 100 1. Steton length is 100. 1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Will be a Droplist field. Character 2 1. Is droplist feasible with all the states\provinces in each country WW? 1. This issue applies more to UI design than database design.
Character 15 Steton length is 15. 1. Changed length to 15 because the longest international postal currently is 9 characters.
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. Changed length to 50 because the longest ISO country name currently is: South Georgia and the South Sandwich Islands, which is 44 characters.
Country Subdivision Code for Postal Location O Code representing the Subdivision of a Country. Similar to US State or Canadian Province this code allows for other subdivisions like British Counties, French Departments and German Länders. Will be a Droplist field.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html Character 3 1. Added attribute to accommodate and align with international standards.
Billing Address Line 1 O This is the Supplier address used for all invoices and billing Character 100
Chacter 100
O
Chacter 100
Chacter 100
Character 100 1. Steton length is 100. 1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Will be a Droplist field. Character 2 1. Is droplist feasible with all the states\provinces in each country WW? 1. This issue applies more to UI design than database design.
Character 15 Steton length is 15. 1. Changed length to 15 because the longest international postal currently is 9 characters.
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. Changed length to 50 because the longest ISO country name currently is: South Georgia and the South Sandwich Islands, which is 44 characters.
Country Subdivision Code for Billing Location O Code representing the Subdivision of a Country. Similar to US State or Canadian Province this code allows for other subdivisions like British Counties, French Departments and German Länders. Will be a Droplist field.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html Character 3 1. Added attribute to accommodate and align with international standards.
R
Character 200
O
Character 5
2. This attribute exists in Steton, but is not currently being populated.
R
Character 100 1. EYES concatonates name prefix, first name, middle name and last name into one attribute with a combined length of 50.
O
Character 100
2. This attribute exists in Steton, but is not currently being populated.
R
Character 100
2. Steton length is 50
R
Will be a Droplist field. N/A N/A 1. Do not believe we require this field when we have the
Contact Category
field – potential duplication.
2. Seems to be redundant with Contact Category.
3. Per Rona, “I am a bit confused between contact type and contact category – can you explain?”
R
Character
O
Character 100
1. No Change – Since EYES will publish data to the Supplier MDM, the source field length can be smaller than the target field length.
R
Character
2. Steton length is 200.
2. Supplier MDM will now be able to hold the largest Email Address from Steton.
R
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. Character 25
2.Steton length is 25.
O
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. Character 25
2. Steton length is 25.
1. See (Supplier Phone #) above. Changed length to 25 to accomodate largest sized attribute.
Only the country code (drop the zeros) and area codes with NO hyphens, parenthesis, pluses, periods. May include extensions at the end of number, must insert Ext and then number. Character 25
Steton length is 25.
1. See (Supplier Phone #) above. Changed length to 25 to accomodate largest sized attribute.
Character 100
Chacter 100
Chacter 100
Chacter 100
Character 100
1.Changed length to 100. The business rules for formating this attribute into a smaller length field will be determined during the interface design.
Character 2
Character 15
1. Changed length to 15 because the longest international postal currently is 9 characters.
Will be a Droplist field.
The country name and associated reference code are based on ISO standards. Character 50 1. Changed length to 50 because the longest ISO country name currently is: South Georgia and the South Sandwich Islands, which is 44 characters.
UN/Locode is a geographic coding scheme developed andmaintained by the United Nations Economic Commission for Europe that assigns standard codes to locations used in trade and transport.
http://www.unece.org/cefact/locode/welcome.html Character 3 1. Added attribute to accommodate and align with international standards.
Contact
R
&”-,Bold Italic”Supplier Master Data
&”-,Bold”Supplier Master Data
Printed:
&D &F Page &P
Printed: &D &F Page &P
Missing Attributes
This worksheet contains all the attributed that have been proposed to be added to the Supplier Master database | ||||||||||
All the teams feedback has been consolidated into the Change Log column at the end of the worksheet. The response to all feedback has been provided in the Change Log Action column at the end of the worksheet. |
SUPPLIER COMPANY PROFILE | |||||||||
Attribute Name | Required / Optional | Attribute Length | Comments | |||||||
Registration No. | The legal government company registration number. | The legal government company registration no. as detailed in the Business Relationship & Confidentiality Ageement | Character\Numberic | 12 | Aligns with Global legal requirement to have BRA signed with a legally registered company. | 1. Supplier attributes eligible for inclusion in Supplier MDM are those that are shared/used between multiple business processes/systems. This attribute will not be included in Supplier MDM because it only has relevance to EYES (where it should be maintained). | ||||
what AOW the facility is supplying | We may not need this for supplier but definitely for facility | 1. AOW is a level within the McD global geographic hierarchy and can be determined based on the “Country for Physical Location” attribute. Consequently, there is no need to add this attribute to the Supplier Master Record. | ||||||||
Physical | Address Line #3 in WSI | We typically use either the 2nd or 3rd address line | 1. A third address line will not be added to Supplier MDM. The need by the WSI system for placing the postal address will be resolved within the interface between Supplier MDM and the WSI system. | |||||||
Required | The Area of the World or country that manages the relationship with the company | 1. This attribute has been added to Supplier MDM. Merlin leads have decided not to carry this information at the supplier company or supplier facility level because this it is managed at the product spec level. Quality will maintain this attribute in Steton. 2. Merlin and Steton have indicated they need this information. 3. I need clarification to whether this is AoW or Market or both 4. I need clarification on whether this attribute applies to Supplier Company and/or Supplier Facility. 5. I need confirmation that only one Market/AOW is responsible for managing the relationship. |
||||||||
1. The Supplier Status attribute has been added to Supplier MDM. 2. The proposed list of valid values has been provided. Request broader team to review and provide feedback. |
||||||||||
Assumption is this line is usually only used for PO Box info (and not used well especially if zip code is different than ship address) | ||||||||||
The Area of the World or country that manages the relationship with the facility | ||||||||||
Facility Status | Indicates the state of the Supplier facility in terms of whether it has been manufacturing products for McDonald’s. | 1. The Facility Status attribute has been added to Supplier MDM. 2. The proposed list of valid values has been provided. Request broader team to review and provide feedback. |
||||||||
NONE |
&”-,Bold Italic”Missing Attributes
Supplier Status
This worksheet contains all the proposed values for the Supplier Status & Facility Status attributes. | All the teams feedback has been consolidated into the Change Log column at the end of the worksheet. The response to all feedback has been provided in the Change Log Action column at the end of the worksheet. |
||||
Supplier Status Attribute Values | Company Definition | Facility Definition | |||
Active | 1. Does active imply the Company/Facility has been approved? 2. Business definition is needed. |
1. Ask for feedback from broader group? | |||
Inactive | 1. Does this imply the Company/Facility is Closed? 2. Business definition is needed. |
1. From WSI perspective we would close an Inactive location (but Inactive to me sounds different that closed) – and if a Parent, either reparent to a new parent or close the subsidiaries (as aprropriate to the situation). | |||
On Hold | 1.Business definition is needed. | ||||
Suspended | |||||
Approved? |
Supplier & Facility Category
This worksheet contains all the proposed values for the Supplier & Facility Category attributes. | |||||||||||||||
Supplier Category | Description | ||||||||||||||
AOW Office | Facility that provides services at a Regional or country/ local operations and managerial functions | 1. Not used in Merlin. | 1. The Supplier MDM will contain a broader set of supplier categories than used in Merlin. For example, the WSI system will have Distribution Centers as suppliers while Steton will | Uniforms | |||||||||||
Construction & Development | Seating, Décor & Furniture Suppliers. | 1. The Supplier MDM will contain a broader set of supplier categories than used in Merlin. For example, the WSI system will have Distribution Centers as suppliers while Steton will Uniforms. | |||||||||||||
Co-Packer | Company that manufactures and/or packages foods for other companies. A co-packer works under contract with the hiring company to manufacture food as though the products were manufactured directly by the hiring company. For example, Nestle s a Supplier and ConAgra is a Co-Packer for canned sausage gravy. | ||||||||||||||
Business enterprise that purchased product from suppliers and ship product to the McDonald’s restaurants. | 1. Not used in Merlin. 2. Need Business Definition. |
1. The Supplier MDM will contain a broader set of supplier categories than used in Merlin. For example, the WSI system will have Distribution Centers as suppliers while Steton will Uniforms. | 2. Ask HGS for business definition. | ||||||||||||
Equipment | Company that supplies equipment | ||||||||||||||
External Warehouse | Business enterprise that stores and manages the warehousing of a supplier’s product. The supplier does not own the warehouse but they pay the external warehouse company for storage and warehousing services. The external warehouses do not own the product, the product is owned by the supplier. External warehouses usually contain products from multiple suppliers. Many McDonald’s suppliers utilized “cold storage” external warehouse. | 1. The Supplier MDM will contain a broader set of supplier categories than used in Merlin. For example, the WSI system will have Distribution Centers as suppliers while Steton will Uniforms. 2. Ask HGS for business definition. |
|||||||||||||
Company that manufactures and/or processes food | |||||||||||||||
(In the US) Hubs are business enterprises that ship product to the McDonald’s DC’s. Hubs do not ship directly to restaurants. Hubs typically own the product in their warehouse and purchase directly from suppliers. Hubs usually carry slower moving items or items where DC’s consistently do not want to order full trailer loads. Hubs do not carry all products carried by the DC and products carried by the Hubs are by agreement with McDonald’s Supply Chain. | |||||||||||||||
McDonald’s BU Office | Location is a business unit for McDonald’s | ||||||||||||||
Operations Supplies | Company that manufactures and/or distributes operating supplies (i.e. gloves, mops) | ||||||||||||||
Other Ship Point | Business enterprises are suppliers that provide product directly to the restaurants, not through the restaurant’s distribution center. For example, some bakeries supply to both the DC’s and directly to restaurants (but a restaurant typically will only receive baked goods either from a bakery directly or from the DC, not both). | ||||||||||||||
Packing | Company that manufactures packing materials for a product to distribution center. (i.e. corrugated boxes, poly bags) | ||||||||||||||
Paper/Packaging | Company that manufactures packaging products for presentation to consumer. (i.e. wraps, straws, lids, cartons, fry boxes) | ||||||||||||||
Promotional (including Happy Meal) | All promotional production including Happy Meal toys, Arch cards, etc. | ||||||||||||||
Service Provider | Company that provides supply chain management services (i.e. oil collection, waste management), consulting services, technology providers, etc. | ||||||||||||||
Company that provides uniforms for crew, managers, etc. | |||||||||||||||
Worldwide Headquarters | Facility where a company’s executive offices and direct support staff are located |
&”-,Bold Italic”Supplier and Product Catagory Values
&D &F Page &P
Trading Market Status
This worksheet contains all the proposed values for the Trading Market Status attribute contained on both the Supplier Company and Supplier Facility records. | |||||||
Status Field Values | |||||||
Identified | Potential supplier for a product. This could be companies we are considering based on new product and new menu management initiatives, network optimization strategies, top industry leaders or other companies that who we currently do not do business with. Suppliers does not have approval status. | Company has identified facilities that could potentially do business with McDonald’s. | 1. Not aligned with Merlin. | 1. Delete value. | |||
Developmental | We have determined to conduct business with the supplier. Minimum requirements are in order to proceed with potential supply. – In process of signing BRL and Confidentiality Agreements and Code of Conduct – McMatrix completed – Supplier does not have approval status |
New Supplier Checklist started. Audits have been scheduled |
|||||
Temporary Approved | Company is in the process of getting all the minimum requirements completed. BRL and Confidentiality Agreement, Pricing Protocol and Code of Conduct is signed | Facility is considered for short-term promotion and/or awaiting the completion of Quality Systems Approvals. |
|||||
Company meets all minimum requirements in column 1 of SPI | Facility meets all minimum requirements for SPI, SWA, SQMS and any additional QA requirements. | ||||||
Company that was once approved and we no longer use this company. For example, promotional items. | Facility was once approved and we no longer get supply from. For example, promotional products. | ||||||
Archived | Company that we will not do business with. May have been approved in the past | Facility is closed and/or ownership has change. | |||||
Probation | Company has a serious business violation and/or product performance issues. Formal Compliance/ Corrective action plan in place. | Facility has serious product performance issues. The facility is on a formal corrective action notice. | |||||
Disapproved | McDonald’s Management decision to no longer conduct business with this supplier. | McDonald’s Management decision to no longer conduct business with this company. |
&”-,Bold Italic”Status Values
Printed: &D &F Page &P
Ethnicity, Minority & Gender
This worksheet contains all the proposed values for the Company Ownership Ethnicity and | Company Ownership Minority Type |
African American | A person of black African descent living in the United States. |
Native American | A person descended from any of the aboriginal peoples of the western hemisphere, specifically of North America. |
Asian | A person of Asian descent living in the United States. |
Hispanic | A person of Latin American descent living in the United States. |
Arab American | A person who identifies themselves as Arab living in the United States. |
Caucasian | A person of European descent living in the United States. |
MBE | Minority Business Enterprise is a business which is at least 51% owned, operated and controlled on a daily basis by one or more (in combination) American citizens of the ethnic minority classifications identified in Company Owned Ethnicity. |
WBE | Women Business Enterprise is a business which is at least 51% owned, operated and controlled on a daily basis by one or more (in combination) American citizens that are women. |
MBE/WBE | A business which is at least 51% owned, operated and controlled on a daily basis by a combination of one or more American citizens that are women and are of the ethnic minority classification identified in Company Owned Ethnicity. |
Male | |
Female |
&”-,Bold Italic”Ethnicity, Minority and Gender Values
Contact Category
This worksheet contains all the proposed values for the Contact Category attribute. | |||||||||||||||
Contact Category Values | |||||||||||||||
ALL Previous Values | 1. They need to align to Merlin and Steton. 2. EYES and WSI need Contacts. |
1. Original values were deleted from Supplier MDM because Merlin and Steton agree that their respective contacts are different. Consequently, their contacts will not be condidates for Supplier MDM. Instead, they will be maintained in by their separate business groups within either Merlin or Steton. 2. New Contact Category values align to EYES and WSI. |
|||||||||||||
Primary | 1. Need business definition. | 1. Request business definition from EYES. | |||||||||||||
GM | |||||||||||||||
R&D | |||||||||||||||
1. Emergency is a separate attribute on the Supplier Contact record. | |||||||||||||||
Shipping Point | |||||||||||||||
Remittance | |||||||||||||||
RPC Complaints | |||||||||||||||
Account Manager | |||||||||||||||
Master Data Management | 1. Request feedback for definition from the broader group. |
&”-,Bold Italic”Contact Category Values
Printed: &D &F Page &P
Accounts_200705010800436745416.xml
3
123
LUBBOCK TX
abc street #1
LUBBOCK
TX
12345
US
true
true
District1
Region12
456
ROCKY MOUNT
123 NORTH BOULEVARD
ROCKY MOUNT
NC
12345
US
true
false
District24
Region20
true
form1
789012
GREENVILLE STORE
3240 N. SOUTH DRIVE
#2
GREENVILLE
SC
12345
US
true
false
District11
Region337
SQS Account Master Data Mapping.xls
Sheet1
Special Instructions
1. Any node that is sent will replace the value in the database with the node value. If the node is empty, the value in the database will be removed.
2. In order to not effect a value in the database, the node should be omitted from the file that is sent.
3. Required nodes must always be sent.
Steton Field Freq (min, max) Description Data Type XML Type Lookup Reference Len Format Possible Values
Control.AccountCount 1,1 Total number of accounts included in the file xs:integer
ListOfAccounts.Account.AccountId 1,1 Account ID xs:string 15
ListOfAccounts.Account.AccountName 1,1 Account name xs:string 200
ListOfAccounts.Account.Address1 0,1 Address line 1 xs:string 100
ListOfAccounts.Account.Address2 0,1 Address line 2 xs:string 100
ListOfAccounts.Account.MailStop 0,1 Mail stop xs:string 100
ListOfAccounts.Account.City 0,1 City xs:string 100
ListOfAccounts.Account.State 0,1 State xs:string 50 Generally, this is a state abbreviation for US accounts
ListOfAccounts.Account.PostalCode 0,1 Postal code xs:string 50
ListOfAccounts.Account.Country 0,1 Country xs:string 100
ListOfAccounts.Account.Phone1 0,1 Phone 1 xs:string 50
ListOfAccounts.Account.Phone2 0,1 Phone 2 xs:string 50
ListOfAccounts.Account.Fax 0,1 Fax xs:string 50
ListOfAccounts.Account.Email 0,1 Email xs:string 200
ListOfAccounts.Account.UserField1 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField2 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField3 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField4 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField5 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField6 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField7 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField8 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField9 0,1 User defined field xs:string 255
ListOfAccounts.Account.UserField10 0,1 User defined field xs:string 255
ListOfAccounts.Account.ContactName 0,1 Primary contact name xs:string 200 Alternative primary contact name (this value is not applicable if a UserID has been associated with this account).
ListOfAccounts.Account.ContactPhone 0,1 Primary contact phone xs:string 200 Alternative primary contact phone (this value is not applicable if a UserID has been associated with this account).
ListOfAccounts.Account.ContactEmail 0,1 Primary contact email xs:string 200 Alternative primary contact email (this value is not applicable if a UserID has been associated with this account).
ListOfAccounts.Account.ContactFax 0,1 Primary contact fax xs:string 200 Alternative primary contact fax (this value is not applicable if a UserID has been associated with this account).
ListOfAccounts.Account.UserID 0,1 Primary contact user ID xs:string 15 This value takes precedence of the Contact fields and references an SQS user as the primary contact for this account.
ListOfAccounts.Account.DivisionID 0,1 Division ID xs:integer This field is only relevant for extracts from SQS. This field is ignored for imports to SQS
ListOfAccounts.Account.ModifiedDate 0,1 Date when any account attribute was last modified. xs:datetime yyyy-MM-ddTHH:mm:ss.fffffffK (Example: 2007-2-12T12:09:19.0000000-07:00) For exports, this field contains the date when any account attribute (i.e. Address1, UserField1, etc.) was last modified. This field is ignored for imports to SQS.
ListOfAccounts.Account.Active 1,1 Account status xs:boolean true, false “true” if the account is active. This node is case-sensitive and must be lowercase.
ListOfAccounts.Account.ActiveDate 0,1 Activation date xs:datetime Date the account was activated
ListOfAccounts.Account.TimeZone 0,1 Timezone xs:string One of the standard MS Windows timezones (e.g. “Atlantic Standard Time”, “Atlantic Daylight Time”, “China Standard Time”, “Mountain Standard Time”, “Mountain Daylight Time”, etc.)
ListOfAccounts.Account.DaylightSaving 0,1 Daylight saving xs:boolean true, false “true” if the account observes daylight savings. This node is case-sensitive and must be lowercase.
ListOfAccounts.Account.ManagementListIsDefinitive 0,1 Is this list of Management IDs definitive? If so, any management IDs associated with this account that are not included in this file will be removed. xs:boolean true, false “true” = delete any management associations for this account that are not included in this file.
“false” = add management associations included in this file but DO NOT delete any existing management associations not included in this file. This node is case-sensitive and must be lowercase.
ListOfAccounts.Account.ListOfManagements.Management.ManagementID 0,1 Management IDs associated with this account xs:string 15 One management ID per ListOfAccounts.Account.ListOfManagements.Management node
ListOfAccounts.Account.AuditListIsDefinitive 0,1 Is this list of Audit Forms definitive? If so, any Audit Forms associated with this account that are not included in this file will be removed. xs:boolean true, false “true” = delete any audit form associations for this account that are not included in this file.
“false” = add audit form associations included in this file but DO NOT delete any existing audit form associations not included in this file. This node is case-sensitive and must be lowercase.
ListOfAccounts.Account.ListOfAudits.Audit.AuditReference 0,1 Audit forms associated with this account xs:string 15 One audit reference per ListOfAccounts.Account.ListOfAudits.Audit node
ListOfAccounts.Account.ReportAccess 0,1 Report Access xs:boolean true, false “true” if direct access to this location through reporting is allowed. This node is case-sensitive and must be lowercase.
ListOfCustomFields.CustomField.UniqueKey 0,1 Custom field identifier **NOTE: Steton will provide values for this field based on configuration completed in support of custom fields xs:string 50 **NOTE: Steton will provide values for this field based on configuration completed in support of custom fields
ListOfCustomFields.CustomField.Value 0,1 Custom field value xs:string
ListOfContacts.Contact.NameFirst 1,1 xs:string 50
ListOfContacts.Contact.NameMiddle 0,1 xs:string 50
ListOfContacts.Contact.NameLast 1,1 xs:string 50
ListOfContacts.Contact.Title 0,1 xs:string 100
ListOfContacts.Contact.Address1 0,1 xs:string 100
ListOfContacts.Contact.Address2 0,1 xs:string 100
ListOfContacts.Contact.MailStop 0,1 xs:string 50
ListOfContacts.Contact.City 0,1 xs:string 100
ListOfContacts.Contact.State 0,1 xs:string 50
ListOfContacts.Contact.Country 0,1 xs:string 100
ListOfContacts.Contact.PostalCode 0,1 xs:string 50
ListOfContacts.Contact.Email1 0,1 xs:string 200
ListOfContacts.Contact.Email2 0,1 xs:string 200
ListOfContacts.Contact.Phone1 0,1 xs:string 50
ListOfContacts.Contact.Phone2 0,1 xs:string 50
ListOfContacts.Contact.ContactType 1,1 xs:integer 1=primary, 2=secondary
Sheet2
Sheet3
SwXsdSqsAccountMasterData v1.3.xsd
Managements_200701120200436746416.xml
2
Eastern
Eastern Region
true
0010012
true
A120
USA
US
false
0010012
0010013
false
A10
SQS Management Master Data Mapping.xls
Sheet1
Special Instructions
1. Any node that is sent will replace the value in the database with the node value. If the node is empty, the value in the database will be removed.
2. In order to not effect a value in the database, the node should be omitted from the file that is sent.
3. Required nodes must always be sent.
Steton Field Freq (min, max) Description Data Type XML Type Lookup Reference Len Format Possible Values
Control.RecordCount 1,1 Total number of management records in the file xs:integer
ListOfRecords.Management.ManagementID 1,1 Management ID xs:string 15
ListOfRecords.Management.ParentID 1,1 Parent ID for this record. This is the management ID of the parent record. xs:string 15
ListOfRecords.Management.RootID 1,1 Root ID for this record. This is the management ID of the record at top of the management hierarchy to which this record belongs. xs:string 15
ListOfRecords.Management.LogoID 0,1 Logo ID of the logo associated with this record. xs:integer Unless you know the appropriate Logo ID, exclude this node or leave it blank.
ListOfRecords.Management.LevelID 1,1 Management Level ID for this record. xs:integer
ListOfRecords.Management.ManagementName 1,1 Management name xs:string 200
ListOfRecords.Management.Address1 0,1 Address line 1 xs:string 100
ListOfRecords.Management.Address2 0,1 Address line 2 xs:string 100
ListOfRecords.Management.City 0,1 Mail stop xs:string 100
ListOfRecords.Management.MailStop 0,1 City xs:string 100
ListOfRecords.Management.State 0,1 State xs:string 50 Generally, this is a state abbreviation for US accounts
ListOfRecords.Management.PostalCode 0,1 Postal code xs:string 50
ListOfRecords.Management.Country 0,1 Country xs:string 100
ListOfRecords.Management.Phone1 0,1 Phone 1 xs:string 50
ListOfRecords.Management.Phone2 0,1 Phone 2 xs:string 50
ListOfRecords.Management.Fax 0,1 Fax xs:string 50
ListOfRecords.Management.Email 0,1 Email xs:string 200
ListOfRecords.Management.UserID 0,1 Primary contact user ID xs:string 15 This field references an SQS user as the primary contact for this record.
ListOfRecords.Management.UDF1 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF2 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF3 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF4 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF5 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF6 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF7 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF8 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF9 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.UDF10 0,1 This optional user defined field can be used to hold additional information about this management record xs:string 255
ListOfRecords.Management.AccountListIsDefinitive 0,1 Is this list of Accounts definitive? If so, any Accounts associated with this management that are not included in this file will be removed. xs:boolean true, false “true” = delete any account associations for this record that are not included in this file.
“false” = add account associations included in this file but DO NOT delete any existing account associations not included in this file. This node is case-sensitive and must be lowercase.
ListOfRecords.Management.ListOfAccounts.Account.AccountID 0,1 Account IDs associated with this record xs:string 15 One Account ID per ListOfRecords.Management.ListOfAccounts.Account node
ListOfRecords.Management.AuditListIsDefinitive 0,1 Is this list of Audit Forms definitive? If so, any Audit Forms associated with this management that are not included in this file will be removed. xs:boolean true, false “true” = delete any audit form associations for this record that are not included in this file.
“false” = add audit form associations included in this file but DO NOT delete any existing audit form associations not included in this file. This node is case-sensitive and must be lowercase.
ListOfRecords.Management.ListOfAudits.Audit.AuditReference 0,1 Audit forms associated with this record xs:string 15 One audit reference per ListOfRecords.Management.ListOfAudits.Audit node
Sheet2
Sheet3
SwXsdSqsManagementMasterData v1.1.xsd