RosettaNet
XML Message Guidelines
5C4_MG_V01_03_00_RegistrationStatusNotification.htm
(04-Dec-2002 11:32:00)
This
document has been prepared by RosettaNet (http://www.rosettanet.org) from
requirements
gathered
during the cluster/segment workshops and in conformance with the RosettaNet
methodology.
Guideline Information
|
lines 2 |
|
|
Constraint: Mandatory when
GlobalRegistrationStatusCode is equal to "Accepted". |
|
|
lines 3 |
|
|
Constraint: Mandatory when
GlobalRegistrationStatusCode is equal to "Accepted". |
|
|
lines 4 |
|
|
Constraint: Mandatory when
GlobalRegistrationStatusCode is equal to "Accepted". |
|
|
lines 19, 39 |
|
|
Constraint: At least one
location specification must be provided: Global Location Identifier, Partner
Location Identification, or Physical Address. |
|
|
lines 30,50,65,76,80,92,111,115,133,137 |
|
|
Entity Instances |
|
|
AD:
ANDORRA |
|
|
AE:
UNITED ARAB EMIRATES |
|
|
AF:
AFGHANISTAN |
|
|
AG:
ANTIGUA AND BARBUDA |
|
|
AI:
ANGUILLA |
|
|
AL:
ALBANIA |
|
|
AM:
ARMENIA |
|
|
AN:
NETHERLANDS ANTILLES |
|
|
AO:
ANGOLA |
|
|
AQ:
ANTARCTICA |
|
|
AR:
ARGENTINA |
|
|
AS:
AMERICAN SAMOA |
|
|
AT:
AUSTRIA |
|
|
AU:
AUSTRALIA |
|
|
AW:
ARUBA |
|
|
AZ:
AZERBAIJAN |
|
|
BA:
BOSNIA AND HERZEGOVINA |
|
|
BB:
BARBADOS |
|
|
BD:
BANGLADESH |
|
|
BE:
BELGIUM |
|
|
BF:
BURKINA FASO |
|
|
BG:
BULGARIA |
|
|
BH:
BAHRAIN |
|
|
BI:
BURUNDI |
|
|
BJ:
BENIN |
|
|
BM:
BERMUDA |
|
|
BN:
BRUNEI DARUSSALAM |
|
|
BO:
BOLIVIA |
|
|
BR:
BRAZIL |
|
|
BS:
BAHAMAS |
|
|
BT:
BHUTAN |
|
|
BV:
BOUVET ISLAND |
|
|
BW:
BOTSWANA |
|
|
BY:
BELARUS |
|
|
BZ:
BELIZE |
|
|
CA:
CANADA |
|
|
CC:
COCOS (KEELING) ISLANDS |
|
|
CF:
CENTRAL AFRICAN REPUBLIC |
|
|
CG:
CONGO |
|
|
CH:
SWITZERLAND |
|
|
CI:
CÔTE D'IVOIRE |
|
|
CK:
COOK ISLANDS |
|
|
CL:
CHILE |
|
|
CM:
CAMEROON |
|
|
CN:
CHINA |
|
|
CO:
COLOMBIA |
|
|
CR:
COSTA RICA |
|
|
CU:
CUBA |
|
|
CV:
CAPE VERDE |
|
|
CX:
CHRISTMAS ISLAND |
|
|
CY:
CYPRUS |
|
|
CZ:
CZECH REPUBLIC |
|
|
DE:
GERMANY |
|
|
DJ:
DJIBOUTI |
|
|
DK:
DENMARK |
|
|
DM:
DOMINICA |
|
|
DO:
DOMINICAN REPUBLIC |
|
|
DZ:
ALGERIA |
|
|
EC:
ECUADOR |
|
|
EE:
ESTONIA |
|
|
EG:
EGYPT |
|
|
EH:
WESTERN SAHARA |
|
|
ER:
ERITREA |
|
|
ES:
SPAIN |
|
|
ET:
ETHIOPIA |
|
|
FI:
FINLAND |
|
|
FJ:
FIJI |
|
|
FK:
FALKLAND ISLANDS (MALVINAS) |
|
|
FM:
MICRONESIA, FEDERATED STATES |
|
|
FO:
FAROE ISLANDS |
|
|
FR:
FRANCE |
|
|
GA:
GABON |
|
|
GB:
UNITED KINGDOM |
|
|
GD:
GRENADA |
|
|
GE:
GEORGIA |
|
|
GF:
FRENCH GUIANA |
|
|
GH:
GHANA |
|
|
GI:
GIBRALTAR |
|
|
GL:
GREENLAND |
|
|
GM:
GAMBIA |
|
|
GN:
GUINEA |
|
|
GP:
GUADELOUPE |
|
|
GQ:
EQUATORIAL GUINEA |
|
|
GR:
GREECE |
|
|
GS:
SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS |
|
|
GT:
GUATEMALA |
|
|
GU:
GUAM |
|
|
GW:
GUINEA-BISSAU |
|
|
GY:
GUYANA |
|
|
HK:
HONG KONG |
|
|
HM:
HEARD ISLAND AND MCDONALD ISLANDS |
|
|
HN:
HONDURAS |
|
|
HR:
CROATIA |
|
|
HT:
HAITI |
|
|
HU:
HUNGARY |
|
|
ID:
INDONESIA |
|
|
IE:
IRELAND |
|
|
IL:
ISRAEL |
|
|
IN:
INDIA |
|
|
IO:
BRITISH INDIAN OCEAN TERRITORY |
|
|
IQ:
IRAQ |
|
|
IR:
IRAN, ISLAMIC REPUBLIC OF |
|
|
IS:
ICELAND |
|
|
IT:
ITALY |
|
|
JM:
JAMAICA |
|
|
JO:
JORDAN |
|
|
JP:
JAPAN |
|
|
KE:
KENYA |
|
|
KG:
KYRGYSTAN |
|
|
KH:
CAMBODIA |
|
|
KI:
KIRIBATI |
|
|
KM:
COMOROS |
|
|
KN:
SAINT KITTS AND NEVIS |
|
|
KP:
KOREA, DEMOCRATIC PEOPLE'S REP. OF |
|
|
KR:
KOREA, REPUBLIC OF |
|
|
KW:
KUWAIT |
|
|
KY:
CAYMAN ISLANDS |
|
|
KZ:
KAZAKSTAN |
|
|
LA:
LAO PEOPLE'S DEMOCRATIC REPUBLIC |
|
|
LB:
LEBANON |
|
|
LC:
SAINT LUCIA |
|
|
LI:
LIECHTENSTEIN |
|
|
LK:
SRI LANKA |
|
|
LR:
LIBERIA |
|
|
LS:
LESOTHO |
|
|
LT:
LITHUANIA |
|
|
LU:
LUXEMBOURG |
|
|
LV:
LATVIA |
|
|
LY:
LIBYAN ARAB JAMAHIRIYA |
|
|
MA:
MOROCCO |
|
|
MC:
MONACO |
|
|
MD:
MOLDOVA, REPUBLIC OF |
|
|
MG:
MADAGASCAR |
|
|
MH:
MARSHALL ISLANDS |
|
|
MK:
MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF |
|
|
ML:
MALI |
|
|
MM:
MYANMAR |
|
|
MN:
MONGOLIA |
|
|
MO:
MACAU |
|
|
MP:
NORTHERN MARIANA ISLANDS |
|
|
MQ:
MARTINIQUE |
|
|
MR:
MAURITANIA |
|
|
MS:
MONTSERRAT |
|
|
MT:
MALTA |
|
|
MU:
MAURITIUS |
|
|
MV:
MALDIVES |
|
|
MW:
MALAWI |
|
|
MX:
MEXICO |
|
|
MY:
MALAYSIA |
|
|
MZ:
MOZAMBIQUE |
|
|
NA:
NAMIBIA |
|
|
NC:
NEW CALEDONIA |
|
|
NE:
NIGER |
|
|
NF:
NORFOLK ISLAND |
|
|
NG:
NIGERIA |
|
|
NI:
NICARAGUA |
|
|
NL:
NETHERLANDS |
|
|
NO:
NORWAY |
|
|
NP:
NEPAL |
|
|
NR:
NAURU |
|
|
NT:
NEUTRAL ZONE |
|
|
NU:
NIUE |
|
|
NZ:
NEW ZEALAND |
|
|
OM:
OMAN |
|
|
PA:
PANAMA |
|
|
PE:
PERU |
|
|
PF:
FRENCH POLYNESIA |
|
|
PG:
PAPUA NEW GUINEA |
|
|
PH:
PHILIPPINES |
|
|
PK:
PAKISTAN |
|
|
PL:
POLAND |
|
|
PM:
SAINT PIERRE AND MIQUELON |
|
|
PN:
PITCAIRN |
|
|
PR:
PUERTO RICO |
|
|
PT:
PORTUGAL |
|
|
PW:
PALAU |
|
|
PY:
PARAGUAY |
|
|
QA:
QATAR |
|
|
RE:
REUNION |
|
|
RO:
ROMANIA |
|
|
RU:
RUSSIAN FEDERATION |
|
|
RW:
RWANDA |
|
|
SA:
SAUDI ARABIA |
|
|
SB:
SOLOMON ISLANDS |
|
|
SC:
SEYCHELLES |
|
|
SD:
SUDAN |
|
|
SE:
SWEDEN |
|
|
SG:
SINGAPORE |
|
|
SH:
SAINT HELENA |
|
|
SI:
SLOVENIA |
|
|
SJ:
SVALBARD AND JAN MAYEN ISLANDS |
|
|
SK:
SLOVAKIA |
|
|
SL:
SIERRA LEONE |
|
|
SM:
SAN MARINO |
|
|
SN:
SENEGAL |
|
|
SO:
SOMALIA |
|
|
SR:
SURINAME |
|
|
ST:
SAO TOME AND PRINCIPE |
|
|
SV:
EL SALVADOR |
|
|
SY:
SYRIAN ARAB REPUBLIC |
|
|
SZ:
SWAZILAND |
|
|
TC:
TURKS AND CAICOS ISLANDS |
|
|
TD:
CHAD |
|
|
TF:
FRENCH SOUTHERN TERRITORIES |
|
|
TG:
TOGO |
|
|
TH:
THAILAND |
|
|
TJ:
TAJIKISTAN |
|
|
TK:
TOKELAU |
|
|
TM:
TURKMENISTAN |
|
|
TN:
TUNISIA |
|
|
TO:
TONGA |
|
|
TP:
EAST TIMOR |
|
|
TR:
TURKEY |
|
|
TT:
TRINIDAD AND TOBAGO |
|
|
TV:
TUVALU |
|
|
TW:
TAIWAN, PROVINCE OF CHINA |
|
|
TZ:
TANZANIA, UNITED REPUBLIC OF |
|
|
UA:
UKRAINE |
|
|
UG:
UGANDA |
|
|
UM:
UNITED STATES MINOR OUTLYING ISLANDS |
|
|
US:
UNITED STATES |
|
|
UY:
URUGUAY |
|
|
UZ:
UZBEKISTAN |
|
|
VA:
HOLY SEE (VATICAN CITY STATE) |
|
|
VC:
SAINT VINCENT AND THE GRENADINES |
|
|
VE:
VENEZUELA |
|
|
VG:
VIRGIN ISLANDS (BRITISH) |
|
|
VI:
VIRGIN ISLANDS (U.S.) |
|
|
VN:
VIET NAM |
|
|
VU:
VANUATU |
|
|
WF:
WALLIS AND FUTUNA ISLANDS |
|
|
WS:
SAMOA |
|
|
YE:
YEMEN |
|
|
YT:
MAYOTTE |
|
|
YU:
YUGOSLAVIA |
|
|
ZA:
SOUTH AFRICA |
|
|
ZM:
ZAMBIA |
|
|
ZR:
ZAIRE |
|
|
ZW:
ZIMBABWE |
|
|
lines 59, 70, 105, 127 |
|
|
Constraint: Mandatory when
GlobalRegistrationStatusCode is equal to "Approved". |
|
|
lines 60, 71, 106, 128 |
|
|
Constraint: Mandatory if
GlobalDesignRegistrationNotificationCode is "Update". |
|
|
lines 67, 78, 113, 135 |
|
|
Entity Instances |
|
|
Initial |
The
first-time response or notification regarding design registration status. |
|
Update |
An
updated response or notification regarding design registration status. |
|
lines 64, 75, 79, 91, 110, 114, 132 |
|
|
User Notes: This represents
Geographic Region information, the "choice" being: choose the
Global Geographic Region Code (which is equal to Global) -OR- choose one or
more Global Country Code(s). |
|
|
Lines 66, 77, 81, 93, 112, 116, 134, 138 |
|
|
Entity Instances |
|
|
Global |
All
countries |
|
lines 82, 117 |
|
|
Constraint: At least one
occurrence of 'GlobalProductIdentifier' or 'PartnerProductIdentification' is
mandatory. |
|
|
lines 85, 97, 120, 161, 176 |
|
|
Entity Instances |
|
|
Broker |
Representative
of a third party. |
|
Carrier |
Product
carrier for transporting goods in supply chain. |
|
Contract
Manufacturer |
The
party responsible for the services rendered. |
|
Customs
Broker |
Product
customs broker in supply chain. |
|
Distribution
Center |
Product
distributor in supply chain. |
|
Distributor |
Product
distributor in supply chain. |
|
End
User |
Product
end user in supply chain. |
|
End
User Government |
End
user government. |
|
Financier |
Financial
service provider in supply chain |
|
Freight
Forwarder |
Product
freight forwarder for transporting goods in supply chain. |
|
Manufacturer |
Product
manufacturer in supply chain. |
|
Original
Equipment Manufacturer |
Product
manufacturer of original equipment in the supply chain. |
|
Reseller |
The
party who buys goods from a manufacturer and resells them to customers
unchanged. |
|
Retailer |
Product
retailer in supply chain. |
|
Shopper |
Product
shopper in supply chain. |
|
Warehouser |
Product
warehouser in supply chain. |
|
Forecast
Reply Recipient |
The
party that receives a forecast reply. The Recipient can be the original
forecast owner or other forecast partner (Please refer to the
GlobalPartnerClassificationCode). |
|
lines 89, 101, 124, 142 |
|
|
User Notes:
This status code applies only to the lowest level assembly, core product or
device specified in the information block within which this status code is
embedded. |
|
|
Entity Instances |
|
|
Accepted |
The
submitted supplier part registration has been granted under the terms and
conditions of the supplier. An associated registration number should be
issued concurrently. |
|
Approved |
The
submitted supplier part registration has been approved. |
|
Dead |
The
supplier part is no longer a viable opportunity on the board / assembly. |
|
Pending |
The
submitted supplier part registration is under review for consideration and
has not been moved to an accepted or rejected status. |
|
Pending
/ Competing Registration Present |
The
submitted supplier part registration is under review for consideration and
has not been moved to an accepted or rejected status due to the presence of
competing registration. |
|
Production |
The
supplier part is being utilized in the board / assembly in a manufacturing
environment. |
|
Rejected |
The
supplier/manufacturer representative has denied the distributor request for
an approved registration according to the supplier's rules and regulations. |
|
Revoked |
The
supplier part registration has been removed from prior approved status (e.g.
an update was not submitted in a timely fashion as required) |
|
Valid |
The
submitted supplier part registration is acceptable. |
|
Win |
The
accepted supplier part registration has reached the supplier defined design
win metric. |
|
lines 139 |
|
|
Entity Instances |
|
|
Above
average |
Above
average complexity |
|
Average |
Average
complexity |
|
Maximum |
Maximum
complexity |
|
Minimum |
Minimal
complexity |
|
None |
No
complexity |
|
Some |
Some
complexity |
|
lines 140 |
|
|
Entity Instances |
|
|
Above
average |
80%
dedicated involvement of the Field Application Engineer |
|
Average |
60%
dedicated involvement of the Field Application Engineer |
|
Minimum |
20%
dedicated involvement of the Field Application Engineer |
|
None |
No
involvement of the Field Application Engineer |
|
Some |
40%
dedicated involvement of the Field Application Engineer |
|
Total |
100%
dedicated involvement of the Field Application Engineer |
|
lines 138 |
|
|
Entity Instances |
|
|
Changes
only |
|
|
Total
refresh |
|
|
lines 148 |
|
|
Constraint: Mandatory when GlobalDesignRegistrationNotificationCode is equal to "Update". |
|
|
lines 156,171 |
||
|
Constraint: |
Only
GlobalPartnerRoleClassificationCode equal to Product Provider is allowed. |
156 |
|
Constraint: |
Only
GlobalPartnerRoleClassificationCode equal to DemandCreator is allowed. |
171 |
|
Entity Instances |
|
|
|
Account
Supplier |
Any
trading partner that buys or sells products/services from customers and/or
vendors. |
|
|
Account
User |
Any
trading partner that requires an account to buy or sell products/services. |
|
|
Anonymous
Buyer |
A
requestor of information that chooses to remain anonymous. |
|
|
Appointment
Provider |
The
stakeholder(s) in the shipment delivery activity. |
|
|
Authorized
Service Provider |
The
Service Provider authorized by an OEM to perform service on a unit. |
|
|
Authorizer |
The
partner role that provides product authorization, from a product owner or
manufacturer, for a reselling organization to resell a product. |
|
|
Buyer |
An
employee or organization that buys products for a partner type in the supply
chain. |
|
|
Catalog
Distributor |
The
partner role that distributes catalog information to catalog producers and
buyers. |
|
|
Catalog
Producer |
The
partner role that produces catalog information for a partner type in the
supply chain. |
|
|
Change
Requester |
A
party who has an interest in requesting a review of a possible change to the
component. The requester may be any party including customers and suppliers. |
|
|
Change
Review Forum |
A
party who has responsibility for the review of Engineering Change Requests
and the drafting and review of Engineering Change Orders. The Change Review
Forum is assumed to be at the company that has responsibility for the
engineering aspects of the component affected by the change. |
|
|
Claim
Requester |
The
owner of the shipments who is responsible for the intact delivery. |
|
|
Consignee |
The
receiver of the shipment. |
|
|
Credit
Provider |
This
partner role is responsible for providing credit information about potential
customers. |
|
|
Credit
Reference Requester |
This
partner role is responsible for requesting credit information about potential
customers. |
|
|
Customer |
This
partner role creates a demand for a product or service. |
|
|
Customer
Manager |
This
partner role manages the relationship with the business customers. |
|
|
Decision
Stakeholder |
The
party (such as suppliers, customers and others) who is responsible for the
review and approval of the Engineering Change Approval Request. The
stakeholders may be from multiple organizations. |
|
|
Delivery
Appointment Provider |
A
party that receives a request for a change to a previously scheduled delivery
appointment. |
|
|
Delivery
Appointment Requester |
A
party that requests a change to a previously scheduled delivery appointment. |
|
|
Demand
Creator |
The
partner role that identifies the opportunity, submits design registration,
provides engineering support to advance the opportunity towards design win,
and generates revenue by satisfying customer demand for a product. |
|
|
Failure
Report Administrator |
An
employee or organizational entity that receives and processes PIP Failure
Notifications. |
|
|
Financing
Processor |
The
organization that processes the request for financing. |
|
|
Forecast
Owner |
The
party that creates a sales or order forecast and is ultimately responsible
for it. |
|
|
Forecast
Recipient |
The
party that receives a sales or order forecast. |
|
|
Forecast
Reply Recipient |
The
party that receives a forecast reply. The Recipient can be the original
forecast owner or other forecast partner (Please refer to the
GlobalPartnerClassificationCode). |
|
|
Implementation
Plan Creator |
The
partner role that creates, maintains and manages an implementation plan
associated with an Engineering Change Order. |
|
|
Integrator |
The
organization responsible for the production of the product. Change requests
are communicated back to the Qualification Owner. |
|
|
In-transit
Information User |
The
party who receives shipment status information. |
|
|
Inventory
Information Provider |
An
organization that owns or holds inventory and provides information about this
inventory to partners in the supply chain. This may be a distributor,
contract manufacturer, supplier or OEM reporting inventory that they hold
and/or own. |
|
|
Inventory
Information User |
An
employee or organizatrion that uses information about inventory. |
|
|
Invoice
Provider |
The
organization that generates the invoice. |
|
|
Invoice
Receiver |
The
organization being invoiced. |
|
|
Invoice
Reject Provider |
The
organization that rejects an invoice. |
|
|
Invoice
Reject Receiver |
The
organization being issued an Invoice Reject Notification. |
|
|
Marketing
Activity Information User |
The
party who uses information about Marketing Activities. This party might
include distributors, and retail operations. |
|
|
Marketing
Activity Initiator |
The
partner role that distributes information about marketing activities being
sponsored by the organization. |
|
|
Payee |
The
party receiving a payment. |
|
|
Payer |
The
party issuing a payment. |
|
|
PIP
Failure Notifier |
An
organizational process that automatically notifies the appropriate Failure
Report Administrator of a PIP process failure. |
|
|
Product
Distributor |
The
party authorized by a Product Supplier to purchase goods and services from
the Product Supplier and resell to customers. |
|
|
Product
Information Distributor |
The
partner role that distributes new product information to product information
users and buyers. |
|
|
Product
Information Subscriber |
The
business partner that subscribes to product information from other business
partners. |
|
|
Product
Information User |
The
partner role that uses product information to create or update enterprise
systems and online promotion systems such as electronic catalog systems. |
|
|
Product
Provider |
The
partner role that creates a differentiated product, owns the registration
process and creates a list of eligible products for use in design
registration. |
|
|
Product
Supplier |
This
partner role supplies product to customers in the supply chain. |
|
|
Qualification
Owner |
The
organization responsible for the qualification of manufacturers and suppliers
of parts for the product. The Qualification Owner defines and maintains the
AML for the product. |
|
|
Quality
Data Provider |
The
party responsible for sending the Repair Quality Data. The Provider, through various means,
learns of product or product component defect(s). |
|
|
Quality
Data User |
The
party who receives the repair and/or test data. The User analyzes the data and incorporates findings into its
business model. |
|
|
Receiver |
The
intended recipient of products or business information. The Receiver may
verify receipt if prescribed. |
|
|
Return
Provider |
The
party responsible for authorizing and/or processing the return. |
|
|
Return
Receiver |
A
third-party or warehousing operation responsible for receiving returns,
inspecting the package contents and comparing to the issued RMA to assure the
contents are what was authorized on the RMA. |
|
|
Return
Requester |
Any
party wishing to return a product. This role could be played by a large
end-user such as the Government Services Administration (GSA), a distributor,
or a reseller. |
|
|
Sales
Facilitator |
This
partner role facilitates the sale of product between partners in the supply
chain. |
|
|
Sales
Lead Originator |
The
party assigning a sales lead to another party. |
|
|
Sales
Lead Processor |
The
party who receives the sales lead. This party is responsible for accepting or
rejecting the lead, and if accepted, reports the status of the lead. |
|
|
Sales
Marketing Claim Processor |
The
partner role that processes the claim and/or remits compensation to the Sales
Marketing Claimant. |
|
|
Sales
Marketing Claimant |
The
partner role that requests reimbursement from a Sales Marketing Claim
Processor. |
|
|
Sales
Marketing Program Reimbursement Recipient |
The
partner role that receives status on a previously submitted sales marketing
claim, or who receives reimbursement without submitting a claim. |
|
|
Sales
Marketing Program Reimburser |
The
partner role that is currently processing a sales marketing claim, (or
providing a payment without a claim submitted) and who provides information
on the status of the claim processing. |
|
|
Seller |
An
organization that sells products to partners in the supply chain. |
|
|
Service
Provider |
A
provider that performs a service such as repair, diagnose, maintain, install
or remove on a unit. |
|
|
Shipment
Information User |
The
party who receives shipment status information. |
|
|
Shipment
Requester |
The
party requesting transportation services. |
|
|
ShipmentController |
The
party who is authorized to make decisions regarding a shipment while
in-transit. |
|
|
Shipper |
The
party who relinquishes (assigns) a shipment to a transport service provider. |
|
|
Solution
Provider |
The
party that may architect, configure, engineer, sell, or determine the
fulfillment of the configured solution to partners in the supply chain. |
|
|
Solution
Requester |
This
party that creates a demand for a product or service, or has contracted with
a Solution Provider for the manufacture or fulfillment of a product(s). |
|
|
Specification
Provider |
The
partner role that creates or passes on manufacturing specifications. This may
be a Solution Provider, an OEM who is sub-contracting manufacturing tasks
like fabrication or assembly, or another party. |
|
|
Specification
User |
The
partner role that uses a manufacturing specification. This might be a
sub-contract assembler or fabricator. |
|
|
Stakeholder |
The
party that is required to implement an Engineering Change Order. The
Stakeholder may include all levels of suppliers, customers or other parties.
The Stakeholder may represent multiple organizations. The Stakeholder may
draft and/or be responsible for completing tasks in an implementation plan. |
|
|
Status
Requester |
The
functional partner role, that could be a Product Provider, that creates a
differentiated product, owns the registration process and creates a list of
eligible products, or who is responsible for identifying the opportunity
(that is, it could be a Demand Creator). |
|
|
Status
Responder |
The
organizational partner role, that could be a Product Provider, that creates a
differentiated product, owns the registration process and creates a list of
eligible products, or who is responsible for identifying the opportunity
(that is, it could be a Demand Creator). |
|
|
Supplier |
This
partner role supplies product to customers in the supply chain. |
|
|
Tender
Information User |
The
stakeholder(s) in the tendering activity. |
|
|
Transport
Service Provider |
The
party that provides transportation services for a Shipment Requester. |
|
|
Warranty
Provider |
The
provider who honors the warranty terms and reimburses the Authorized Service
Provider for a service event performed under the terms of the warranty. |
|
|
lines 160,175 |
|
|
Entity Instances |
|
|
Electronic
Components |
The
electronic components supply chain. |
|
Information
Technology |
The
information technology supply chain. |
|
Semiconductor
Manufacturing |
The
semiconductor manufacturing supply chain. |
|
lines 162 |
|
|
Constraint: |
Only
GlobalDocumentFunctionCode equal to Request is allowed. |
|
Entity Instances |
|
|
Request |
The
business document is a request for a business action to be performed by a
partner. |
|
Response |
The
business document is a response to a requesting partner. |
|
Business Properties |
|
|
Name |
Definition |
|
The
first line of a physical address. |
|
|
The
second line of a physical address. |
|
|
The
third line of a physical address. |
|
|
Free
form textual description regarding product assembly information. |
|
|
The
start date of a date period. |
|
|
The
name of a city. |
|
|
Name
of the contact person(s) within the organization. |
|
|
The
proprietary unique identifier that represents a design registration request
for a Demand Creator. |
|
|
The
date a product design is approved and/or expires for a supplier. |
|
|
A
proprietary unique identifier for a design registration. |
|
|
Indicates
a new or updated design registration. |
|
|
The
date registration becomes effective. |
|
|
The
end date of a date period. |
|
|
The
numerical schema designed to achieve contact via facsimile. |
|
|
The
role initiating a business document exchange. |
|
|
The
proprietary identity of a physical address, located at a post office,
designed solely to accept and receive mail. |
|
|
Free
form textual description provided for Product Provider. |
|
|
The
product provider Field Application Engineer. |
|
|
The
product provider sales representative. |
|
|
The
proprietary unique identifier that represents a design registration request
for a Product Provider. |
|
|
Free
form textual description regarding a project. |
|
|
Unique
tracking identification number that identifies a project. |
|
|
The
name of a state or province within a country. |
|
|
The
date stamp when the registration status was generated. |
|
|
The
date a Demand Creator submits the design registration information to a
Product Provider. |
|
|
The
date the Product Provider requires action from the Demand Creator for a
design registration. |
|
|
Free
form text that identifies a revision to a proprietary serial number. |
|
|
The
numerical schema designed to achieve contact via telephone. |
|
|
The
date-time stamp indicating when this document was generated. |
|
|
The
information that identifies the business document being sent. This identifier
is used to represent the specific business document associated with the
defined business process. |
|
|
The
role receiving the document in a business document exchange. |
|
Business Data Entities |
|
|
Name |
Definition |
|
The
collection of business properties that describe a business identity and
location. |
|
|
The
collection of business properties that provide communication and address
information for contacting a person, organization or business. |
|
|
The
collection of business properties that describe the registration of a core
product. |
|
|
The
collection of business properties that specify the number of days by a start
and end date stamp. |
|
|
The
collection of business properties that describe a product design board /
assembly. |
|
|
The
collection of business properties that describe a product part for a product
design registration. |
|
|
The
collection of properties describing a product design project description. |
|
|
The
collection of business properties that compose a product design project. |
|
|
The
collection of business properties that describe design registration
identification. |
|
|
The
collection of business properties that describe a product's registration
requirements for a Design Win process. |
|
|
The
collection of business properties that describe the registration of a core
product. |
|
|
The
collection of business properties that reflects multiple countries of choice
or a specified region. |
|
|
The
collection of business properties that describe a business partners' identity
and their function in a supply chain. |
|
|
The
collection of business properties that allow for the proprietary
identification of a business location. |
|
|
The
collection of business properties that describe proprietary part information. |
|
|
The
collection of business properties that describe a business partners' role in
a partner interface process. |
|
|
The
actual physical location of an entity as prescribed by local postal
authorities, including country identification as it relates to the party or a
product. |
|
|
The
collection of business properties that identify and describe the actual
physical location of an entity as prescribed by local postal authorities,
including country identification. |
|
|
The
collection of business properties that describe proprietary and global
identifier information regarding a product. |
|
|
RegistrationStatus |
The
collection of business properties that describe the registration status of a
product. |
|
Fundamental Business Data Entities |
|
|
|
|
|
|
Name |
Definition |
Data Type |
Min |
Max |
Representation |
|
The
electro-technical communication number, e.g., telephone number, facsimile number,
pager number. |
String |
1 |
30 |
X(30) |
|
|
Specifies
a specific date. Date stamp based on the ISO 8601 specification. The
"Z" following the day identifier (DD) is used to indicate
Coordinated Universal Time. Informal format: YYYYMMDDZ |
Date |
9 |
9 |
9(8)X |
|
|
Specifies
an instance in time. Based on the ISO 8601 specification where
"YYYY" represents the year, "MM" the month and
"DD" the day. The letter "T" is the date/time separator
and "hh", "mm", "ss.sss" represent hour, minute
and second respectively. This representation is immediately followed by a
"Z" to indicate Coordinated Universal Time. Informal format:
YYYYMMDDThhmmss |
DateTime |
13 |
20 |
9(8)X9(6)V9(3)X |
|
|
Electronic
mail address. |
String |
1 |
|
|
|
|
Unformatted
text. |
String |
1 |
|
|
|
|
A
unique business identifier. The DUNS number is specified by RosettaNet. |
Integer |
9 |
9 |
9(9) |
|
|
Code
identifying the two character country code specified in ISO 3166-1993. |
String |
2 |
2 |
X(2) |
|
|
Code
identifying the purpose of a design registration notification, e.g. an
initial notification or an update. |
String |
1 |
|
|
|
|
GlobalDocumentFunctionCode |
Code
identifying the function of a document as either a request or a response. |
String |
1 |
|
|
|
Code
identifying whether a file is being re-sent complete or with changes only. |
String |
1 |
|
|
|
|
Code
identifying a geographic region. |
String |
1 |
|
|
|
|
Location
uniquely identified by the DUNS +4 number. |
Integer |
10 |
13 |
9(9)4(X) |
|
|
Code
identifying a partner's function in the supply chain. |
String |
1 |
|
|
|
|
Code
identifying a party's role in the supply chain. |
String |
1 |
|
|
|
|
Global
unique product identifier. RosettaNet has adopted the Global Trade
Identification Number (GTIN). |
String |
14 |
14 |
9(14) |
|
|
Code
identifying the level of complexity for registering a product. |
String |
1 |
|
|
|
|
Code
identifying the level of involvement for a Field Application Engineer for
registering a product. |
String |
1 |
|
|
|
|
Code
identifying the registration status of a design; namely, the acknowledgment,
collaboration and continuation on the submitted supplier part business
opportunity between a supplier (manufacture representative) and a
distributor. |
String |
1 |
|
|
|
|
GlobalSupplyChainCode |
Code
identifying the supply chain for the partner's function. |
String |
1 |
|
|
|
Code
identifying geographic location as specified by a national postal code. |
String |
1 |
9 |
X(9) |
|
|
Unique
identifier, i.e. a numeric value or alphanumeric value, for a business
document. |
String |
1 |
|
|
|
|
A
descriptor that is used to categorize an organization or business entity that
is in the Proprietary Business Identifier. |
String |
1 |
|
|
|
|
A
unique name that identifies an organization or business entity that is
responsible for managing one or more lists of identifiers. |
String |
1 |
|
|
|
|
A
unique location identifier assigned and administered by a private authority. |
String |
1 |
|
|
|
|
An
internal identifier used to identify a product. |
String |
1 |
|
|
|
|
A
unique reference identifier for goods, services or business documents. |
String |
1 |
255 |
|
|
|
An
incremental number used to identify changes. |
String |
1 |
|
|