Supplier Guide (External Distribution Allowed)

PIP 3B2 VERSION 01.
01: ADVANCED SHIPMENT NOTICE

RELEASE 1.04
Intended for Intel Supplier Trading Partners
Intel Corporation
https://eroom3.intel.com/eRoom/BET/2003DeploymentEnablement/0_a3cd
Revision Date: 22 January 2018
Copyright 2003 Intel Corporation

Intel Confidential
THIS DOCUMENT IS VALID 30 DAYS FROM THE LATEST REVISION.

PIP 3B2 VERSION 01.04: ADVANCED SHIPMENT NOTICE
TABLE OF CONTENTS
INTRODUCTION.......................................................................................................................................................................3
PURPOSE....................................................................................................................................................................................3
AUDIENCE..................................................................................................................................................................................3
BENEFITS....................................................................................................................................................................................3
INTEL KEY CONTACTS................................................................................................................................................................3
TECHNICAL REQUIREMENTS.......................................................................................................................................................3
PROCESSING REQUIREMENTS......................................................................................................................................................4
Error Processing...................................................................................................................................................................4
SERVICE LEVEL AGREEMENT (PERFORMANCE TIME REQUIREMENTS)........................................................................................5
RELATED DOCUMENTS................................................................................................................................................................5
IMPLEMENTATION.................................................................................................................................................................6
WHERE TO FIND PIPS.................................................................................................................................................................6
MESSAGE GUIDELINES................................................................................................................................................................6
SAMPLE....................................................................................................................................................................................11
PO Example........................................................................................................................................................................11
SIMI/TSM Example.............................................................................................................................................................16
RECEIPT ACKNOWLEDGEMENT................................................................................................................................................20
TESTING...................................................................................................................................................................................23
PURPOSE..................................................................................................................................................................................23
TEST SCENARIOS......................................................................................................................................................................23
PRODUCTION..........................................................................................................................................................................24
READINESS...............................................................................................................................................................................24
SUPPORT...................................................................................................................................................................................25
FREQUENTLY ASKED QUESTIONS...................................................................................................................................26
Glossary of Terms.......................................................................................................................................................................28
377232213.doc Page 2 of 31 Revised: 22 January 2018

INTEL CONFIDENTIAL - THIS DOCUMENT IS VALID 30 DAYS THE LATEST REVISION.
INTRODUCTION
PURPOSE
This document is intended to provide to Intel Suppliers (Trading Partners) the information necessary to begin
implementing RosettaNet PIP 3B2 (Advanced Shipment Notification) in support of both a purchase order or TSM
(supplier managed) business model with Intel. The topics covered are:
INTRODUCTION provides the reader with a basic understanding of the PIP implementation
IMPLEMENTATION is a complete outline of the process to be followed to put the document in production
TESTING describes testing procedures and scenarios specific to this PIP
PRODUCTION describes how to migrate from a test to a production environment and the support to follow
FREQUENTLY ASKED QUESTIONS provides answers to some common questions regarding this PIP
GLOSSARY OF TERMS defines terms that are specific to this PIP
AUDIENCE
This document is intended for suppliers and Rosettanet provisioners. It contains many hyperlinks, data mappings
with required fields and is best viewed in soft form. If you are reading a hard copy of this document, then please
print this document on a color printer to better view the message guideline section.
BENEFITS
Some specific benefits of implementing PIP 3B2 for Intel and the Trading Partner include:
 Reduces time spent calling and sending emails to determine shipment status of critical parts
 Improves efficiency, increases data integrity and provides better visibility for tracking purposes
 Provides an in-transit number into existing Intel tools (e.g. SAM, ARM, VRS)
INTEL KEY CONTACTS

For each implementation, Intel assigns the following roles to participate in the engagement:
TRADING PARTNER PROVISIONERS – They assist the technical part of the implementation where they
manage the implementation process between the supplier and Intel.
PIP DEVELOPMENT TEAM – The Intel technical developers responsible for the developing the PIP for Intel.
They provide answers regarding PIP specifics and facilitate testing and migration to production.
BUSINESS ADVOCATE/BUYER/COMMODITY MANAGER – To represent the business processes involved in

this PIP and to provide user acceptance to data sent and received.
It is highly recommended that the trading partner have complimentary representatives available to support this
implementation, as well.
TECHNICAL REQUIREMENTS
The following RosettaNet Infrastructure for transaction processing will be used for this PIP:
RNIF Version 1.1 Version 2.0

Service Header Version 1.1, build #22 Version 2.0
Preamble Version 1.1, build #22 Version 2.0

PIP0A1 Version 1.0 Version 2.0

General Exception Version 1.1, build #22 Version 2.0
PROCESSING REQUIREMENTS
ERROR PROCESSING
When Intel’s backend system generates an error upon receiving this transaction from a trading partner, an email
message is sent to the Intel Trading Partner Provisioner team who will work with the trading partner to resolve
the issue. The message appears as follows:
SIMI/TSM Sample
-----Original Message-----
From: Wiings2
Sent: Friday, April 04, 2003 2:40 PM
To: TP Provisioners
Subject: SIMIRN Error Notification
<ShipmentNotice>
<SiteName>New Mexico</SiteName>
<SupplierNumber>
<BaseCode>999219</BaseCode>
<Location>-99</Location>
</SupplierNumber>
<StockroomName>NM Fab 11 Store</StockroomName>
<DeliveryDockCode>S40</DeliveryDockCode>
<DeliveryNumber>DeliveryNumber0</DeliveryNumber>
<ShipmentNoticeError><ErrorNumber>1070</ErrorNumber><FreeFormText>Invalid
Supplier Base Code.</FreeFormText></ShipmentNoticeError><ShipmentNoticeLine>
<SupplierPartNumber>CT2980-190221-11</SupplierPartNumber>
<IntelItem>233493462</IntelItem>
<ShipQuantity>10</ShipQuantity>
<PriorityCode>REG</PriorityCode>
<EstimatedArrivalDate>
<DateStamp>20030405Z</DateStamp>
</EstimatedArrivalDate>
<SupplierReference></SupplierReference>
</ShipmentNoticeLine>
</ShipmentNotice>
Larger error messages may be sent as an attachment that will be sent to the trading partner to correct and
resend. It is very important that the email address provided in the <fromRole> contains the appropriate email of
someone (or support group) who can take action to correct the error.
PO Example
For non-TSM trading partners the error message will appear as follows:
-----Original Message-----
From: SPS_SQL_Mail
Sent: Tuesday, April 15, 2003 11:10 AM
To: TP Provisioners
Subject: 3B2_IN PP DATA VALIDATION Error - DMEPO04
You are getting this email because there is an error occurred during the private
process of 3B2 message from ProdSupp-SupplierCompany

Track ID = 'B7CD470B4A9EB0111E8DF9D70295',
PIP = '3B2_IN',
FromRoleGlobalBusinsessID = '123456789',
ToRoleGlobalBusinessID = '047897855',
thisDocumentGenerateDate = 'Apr 15 2003 11:03AM ',
thisDocumentID = '0080111404',
BusinessDocID = '0080111404',
Process Name = 'PP DATA VALIDATION',
Process Description = '(PO#/Line#) BAD010431000001/0025 BAD010431000001/0026
BAD010431000001/0033 BAD010431000001/0034 BAD010431000',
Process Datetime = 'Apr 15 2003 11:10AM
SERVICE LEVEL AGREEMENT (PERFORMANCE TIME REQUIREMENTS)

PIP 3B2 follows a single-action activity (asynchronous) process. Ideally, with system-to-system implementations,
the ASN will be sent real time (i.e., at the moment a shipment leaves the dock). However, if ASNs will be
batched, the expected service level for sending the ASN is no earlier than 4 hours before the shipment leaves the
dock, and no later than 4 hours after. The shipper acts as the initiator and the receiver acts as the responder.
After the shipper sends PIP 3B2 to the receiver, the receiver will send a Receipt Acknowledgement or a General
Acception back to the shipper. Assuming the shipper strictly follows framework and PIP 3B2 specifications; the
shipper processes the Receipt Acknowledgement or a General Acception as soon as it is received. If the shipper
does not receive a Receipt Acknowledgement nor a General Acception within two (2) hours (original message +
three retries * (0.5 hour Time to Acknowledgement)), the shipper can initiate PIP 0A1, Notification of Failure, and
sends it to the receiver. Upon receipt, the receiver will [re] send a Receipt Acknowledgment or a General
Acception. Usage of PIP0A1 should be discussed between the suppliers and Trading Partner Provisioner.
The specifics for the Receipt Acknowledgment and PIP 0A1 (Notification of Failure) can be found at
www.rosettanet.org.
RELATED DOCUMENTS
Intel provides documents to assist trading partners in establishing connectivity with Intel. For trading partners
who prefer not to use the connectivity package provided free of charge by Intel, they should reference the
following (most are available on supplier.intel.com or through your Trading Partner Provisioner):
NAME DOCUMENT DESCRIPTION

Core Handbook This guide is meant for first time RosettaNet implementation
partners who need some background on RosettaNet prior to
engaging.
Connectivity Guide Basic Guide To Understanding Available Connectivity Options with
Intel.
HTTPS Trading Partner Guidelines HTTPS Implementation Guide
Revision
HTTPS Trading Partner HTTPS Data Exchange Sheet with specific information the Trading
Information Sheet (it is also Partner needs from Intel and the information Intel needs from its
embedded with the HTTPS Implementation Trading Partners to establish connectivity
Guide)
RAPID Carrier Code to SCAC.xls List of current RosettaNet accepted SCAC codes. The purpose of
this spreadsheet is to identify the carrier and determine who is
carrying the freight.

IMPLEMENTATION
WHERE TO FIND PIPS

For a list of PIPs by cluster and segment and/or to download a copy of PIP 3B2, please access the RosettaNet
web site at www.rosettanet.org. Users are not required to be a member of RosettaNet or have an ID/password to
download the PIPs.
MESSAGE GUIDELINES
Intel is currently implementing 3B2_MG_V01_01_00_AdvanceShipmentNotification (3-Apr-2003 10:59:03 AM).
Data elements required by RosettaNet are indicated in green, those with a conditional requirement appear in
yellow and the rest are optional. If you would prefer an Excel version of this section, please ask your Trading
Partner Provisioner.
Intel Required Data in PIP

Intel Optional
Not required by Intel
Required for SIMI (supplier inventory management) & TSM
(supplier managed) at Intel
Line# Card SIMI Line Item Intel Description Values

1 1 AdvancedShipmentNotification
2 1 |-- BuyingPartner Header - This segment contains information about who is buying
the product. Can be same as ShipTo or different.
3 1 | |-- purchasedBy.PartnerDescription Header
4 1 | | |-- BusinessDescription Header
5 0..1 | | | |-- businessName.FreeFormText "Intel"
6 0..1 | | | |-- GlobalBusinessIdentifier Buying partner's Duns number "047897855" – Intel
DUNS
7 0..n | | | |-- PartnerBusinessIdentification Header
8 1 | | | | |-- ProprietaryBusinessIdentifier
9 1 | | | | |-- ProprietaryDomainIdentifier
10 0..1 | | | | |-- ProprietaryIdentifierAuthority
11 0..1 | | |-- ContactInformation Header
12 1 | | | |-- contactName.FreeFormText Name of the contact at buying company Usually an Intel contact
13 1 | | | |-- EmailAddress Email Address of the contact Intel to provide
14 0..1 | | | |-- facsimileNumber.CommunicationsNumber
15 0..1 | | | |-- telephoneNumber.CommunicationsNumber
16 1 | | |-- GlobalPartnerClassificationCode "End User" Supplier to provide
17 0..1 | | |-- PhysicalLocation Header
18 0..1 | | | |-- GlobalLocationIdentifier
19 0..n | | | |-- PartnerLocationIdentification Header
22 1 | | | | |-- ProprietaryLocationIdentifier
23 0..1 | | | |-- PhysicalAddress Header
24 0..1 | | | | |-- addressLine1.FreeFormText
27 0..1 | | | | |-- cityName.FreeFormText
28 0..1 | | | | |-- GlobalCountryCode
29 0..1 | | | | |-- NationalPostalCode
30 0..1 | | | | |-- postOfficeBoxIdentifier.FreeFormText
32 0..1 | | | | |-- regionName.FreeFormText


32 1 |-- OriginatingPartner Header - This segment contains information about the location
that items are being shipped from. This may be the same as the
SoldBy item or can be different.
33 1 | |-- shipFrom.PartnerDescription Header
35 0..1 | | | |-- businessName.FreeFormText
36 0..1 | | | |-- GlobalBusinessIdentifier Duns Number of the company where the Supplier's DUNS
goods will be shipped from, a 9 digit
number provided by Dun and Bradstreet.
No Other data can be used here.
42 1 | | | |-- contactName.FreeFormText Name of the contact at ship from location Supplier to provide
43 1 | | | |-- EmailAddress Email Address of the contact Supplier to provide
46 1 | | |-- GlobalPartnerClassificationCode Product manufacturer in supply chain "Manufacturer"
48 0..1 | | | |-- GlobalLocationIdentifier Duns + 4 for ship from location
62 1 |-- SellingPartner Header - This segment contains information about the location
that items are being sold from. This may be the same as the
shipFrom or diffrerent
63 1 | |-- soldBy.PartnerDescription Header
66 0..1 | | | |-- GlobalBusinessIdentifier Supplier Duns Number, a 9 digit number Supplier to provide
provided by Dun and Bradstreet. No Other
data can be used here.
67 0..n | | | |-- PartnerBusinessIdentification
68 1 | | | | |-- ProprietaryBusinessIdentifier Vendor ID + Location Code (9 digits) For example:
"206463001"
69 1 | | | | |-- ProprietaryDomainIdentifier "Vendor ID" (9 digits)
70 0..1 | | | | |-- ProprietaryIdentifierAuthority "Intel"
72 1 | | | |-- contactName.FreeFormText Name of the contact at seller Supplier to provide
73 1 | | | |-- EmailAddress Email Address of the contact Supplier to provide
76 1 | | |-- GlobalPartnerClassificationCode Product manufacturer in supply chain "Manufacturer"
78 0..1 | | | |-- GlobalLocationIdentifier Supplier's Duns + 4 for seller location


92 1 |-- Shipment Header
93 0..1 | |-- freightPaymentAccount.AccountNumber
94 1..n | |-- GlobalCarrierCode SCAC Code ex. "FDEX"
95 0..1 | |-- GlobalIncotermsCode
96 0..1 | |-- GlobalShipmentChangeDispositionCode Required If Shipment has Changed
97 0..1 | |-- GlobalShipmentModeCode Method of shipment Example - "Air"
98 1 | |-- GlobalShippingServiceLevelCode SLA for shipment SIMI "REG" =

RosettaNet "Regular"
SIMI "HOT" =
"Expedited Service"
99 1 | |-- numberOfShippingContainers.CountableAmount Total number of shipping containers sent; Supplier to provide
the number of outer boxes
100 1 | |-- ReceivingPartner Header - This segment contains information about where the
shipment is being received. Can be similar to PurchasedBy or
different.
101 1 | | |-- shipTo.PartnerDescription Header
102 1 | | | |-- BusinessDescription Header
103 0..1 | | | | |-- businessName.FreeFormText "Intel"
104 0..1 | | | | |-- GlobalBusinessIdentifier Duns Number, a 9 digit number provided "047897855" – Intel
by Dun and Bradstreet. No Other data can DUNS
be used here.
105 0..n | | | | |-- PartnerBusinessIdentification Header
106 1 | | | | | |-- ProprietaryBusinessIdentifier
107 1 | | | | | |-- ProprietaryDomainIdentifier
108 0..1 | | | | | |-- ProprietaryIdentifierAuthority
109 0..1 | | | |-- ContactInformation Header
110 1 | | | | |-- contactName.FreeFormText Name of contact at company Supplier to provide
111 1 | | | | |-- EmailAddress Email Address of contact Supplier to provide
112 0..1 | | | | |-- facsimileNumber.CommunicationsNumber
113 0..1 | | | | |-- telephoneNumber.CommunicationsNumber Phone Number of contact Supplier to provide
114 1 | | | |-- GlobalPartnerClassificationCode "Contract Manufacturer"/"End User" "End User"
115 0..1 | | | |-- PhysicalLocation Header
116 0..1 | | | | |-- GlobalLocationIdentifier Intel's Duns + 4 number for location of For example:
shipto "0478978550S40"
117 0..n | | | | |-- PartnerLocationIdentification
118 1 | | | | | |-- ProprietaryDomainIdentifier "SiteName"
"Stock Room"(SIMI)
119 0..1 | | | | | |-- ProprietaryIdentifierAuthority "Intel"
120 1 | | | | | |-- ProprietaryLocationIdentifier SiteName/StockRoomName For example:
"New Mexico"
"NM Fab 11 Store"
121 0..1 | | | | |-- PhysicalAddress Header
122 0..1 | | | | | |-- addressLine1.FreeFormText Address line. Address of Shipto Supplier to provide
123 0..1 | | | | | |-- addressLine2.FreeFormText Street Address Supplier to provide
124 0..1 | | | | | |-- addressLine3.FreeFormText Street Adress Continue Supplier to provide
125 0..1 | | | | | |-- cityName.FreeFormText Name of Shipto city Supplier to provide
126 0..1 | | | | | |-- GlobalCountryCode Country Code of Shipto Supplier to provide
127 0..1 | | | | | |-- NationalPostalCode Postal Code for Shipto Supplier to provide
128 0..1 | | | | | |-- postOfficeBoxIdentifier.FreeFormText PO Box for Shipto Supplier to provide
129 0..1 | | | | | |-- regionName.FreeFormText Name of region for Shipto Supplier to provide
130 0..1 | |-- shipmentChangeReason.FreeFormText Required if Line 96 (GlobalShipmentChangeDispositionCode) is
filled
131 1 | |-- shipmentIdentifier.ProprietaryReferenceIdentifier Packaging Slip Number or airway bill Supplier to provide


number or Delivery Number (SIMI)
132 1..n | |-- ShipmentTransportationEvent Header
133 1 | | |-- DateStamp Ship/Estimated Arrival Date at Intel's dock Supplier to provide
134 1 | | |-- GlobalShipDateCode "Shipped on This Date" and "Arrival at Supplier to provide
Destination Yard"
135 1..n | |-- ShippingContainer Header
136 0..1 | | |-- GlobalPackageTypeCode Type Of Package For example: "Box"
137 0..1 | | |-- LinearPhysicalDimension Header
138 1 | | | |-- GlobalPhysicalUnitOfMeasureCode
139 0..1 | | | |-- HeightDimension
140 0..1 | | | |-- LengthDimension
141 0..1 | | | |-- WidthDimension
142 0..1 | | |-- MassPhysicalDimension Header
143 0..1 | | | |-- Volume Header
144 1 | | | | |-- GlobalPhysicalUnitOfMeasureCode
145 1 | | | | |-- Mass
146 1 | | | |-- Weight Header
147 1 | | | | |-- GlobalPhysicalUnitOfMeasureCode Weight UOM Supplier to provide
148 1 | | | | |-- Mass Weight Supplier to provide
149 0..1 | | |-- numberOfShippingContainers.CountableAmount
150 0..1 | | |-- shippingContainerIdentifier.ProprietarySerialIdenti UCC barcode or proprietary container ID Supplier to provide
fier
151 0..n | | |-- ShippingContainerItem Header
152 1..n | | | |-- DocumentSubLineLotShipReference Header
153 1 | | | | |-- GlobalDocumentReferenceTypeCode Document shipment is being sent against, Supplier to provide
"Purchase Order"/"Delivery Note"/
"Invoice"
154 0..1 | | | | |-- LineNumber Line number of the PO, delivery note or Supplier to provide
invoice being referenced for this
shipment, if available
155 0..n | | | | |-- LotShipReference Header - Lot Infomation
156 0..1 | | | | | |-- expiryDate.DateStamp
157 1 | | | | | |-- LotIdentification Header
158 1 | | | | | | |-- primaryLotIdentifier.ProprietaryRef Supplier Lot Number or number Supplier to provide
erenceIdentifier generated using Intel requirements based
on agreement between supplier and Intel
159 0..1 | | | | | | |-- secondaryLotIdentifier.ProprietaryReferenceIdentifier
160 1..n | | | | | |-- LotQuantity Header
161 1 | | | | | | |-- GlobalLotQuantityClassificationCod The lot quantity meets the minimum "Acceptable"
e requirements.
162 1 | | | | | | |-- GlobalProductUnitOfMeasureCode UOM Supplier to provide
163 1 | | | | | | |-- ProductQuantity Quantity in a whole lot, this is the total Supplier to provide
manufactured quantity for the lot.
164 0..1 | | | | | |-- manufacturingDateCode.ProprietaryRef Date when the product was manufactured
erenceIdentifier
165 1 | | | | |-- ProprietaryDocumentIdentifier Number of document referenced in line Supplier to provide
152. Either a PO number or delivery note
number or a Schedule Agreement
Number, Purchase Order Number or
Invoice Number
166 0..1 | | | | |-- requestedQuantity.ProductQuantity Quantity shipped for each document and Supplier to provide
line
167 1 | | | | | |-- shippedLotQuantity.ProductQuantity Quantity shipped from a specific lot; this Supplier to provide
is the total shipped quantity from the lot.
168 0..1 | | | | |-- subLineNumber.LineNumber SubLine number if available
169 0..n | | | |-- ExportLicense Header
170 0..1 | | | | |-- NationalExportControlClassificationCode Export code for product classification
171 1 | | | |-- GlobalProductUnitOfMeasureCode Unit of Measure Code Supplier to provide
172 0..n | | | |-- HazardousMaterialDescription Header
173 1 | | | | |-- NationalHazardousMaterialUnitedNationsCl Required if 173 = "Yes"
assificationCode
174 1 | | | |-- isContainsHazardousMaterial.AffirmationIndica Indicates whether the product contains "Yes"/"No"


tor hazardous material
175 0..n | | | |-- ManufacturerProfile
176 0..1 | | | | |-- countryOfOrigin.GlobalCountryCode Country code where manufactured
177 0..1 | | | | |-- manufactureDate.DateStamp Date when the product was manufactured
178 0..1 | | | | |-- productSerialIdentifier.ProprietarySerialIde Manufacturing serial number
ntifier
179 0..1 | | | |-- NationalHarmonizedTariffScheduleCode Product classification code for International shipping
180 0..1 | | | |-- numberOfItemPackages.CountableAmount Number of Items packages in container; Supplier to provide
number of inner most boxes if present.
181 1 | | | |-- ProductIdentification Header
182 0..1 | | | | |-- GlobalProductIdentifier GTIN
183 0..n | | | | |-- PartnerProductIdentification Header - Intel and supplier Product Info This segment, lines 182
will be repeated for supplier/Intel product information
184 1 | | | | | |-- GlobalPartnerClassificationCode "End
User"/"Manufacturer"
185 1 | | | | | |-- ProprietaryProductIdentifier Part Number Supplier to provide
186 0..1 | | | | | |-- revisionIdentifier.FreeFormText Part Revision Number Supplier to provide
187 1 | | | |-- shippedQuantity.ProductQuantity Total Quantity. Intel does not use this Supplier to provide
field; at the container level which could
include several PO/lines; We need to
know the shippedQuantity at the PO/line
level. Required by PIP
188 0..1 | | | |-- shippingContainerItemIdentifier.ProprietarySer ContainerItem ID
ialIdentifier
189 0..n | | | |-- traceIdentifier.ProprietaryLotIdentifier Some of Intel's business units pre-deinfe the lot number for
suppliers to reference. It it doesn't apply to the supplier, they may
use their own lot number here
190 0..n | | |-- SubContainer Header - This would be used if sub containers exist. In the case
where a palette has 10 boxes and each box has smaller boxes
inside, then the palette would the container, the 10 boxes would be
subcontainers and the inner boxes would be considered items.
191 1 | | | |-- (ShippingContainer) Inner box to the out most box
192 0..1 | | |-- TrackingReference Header
193 1 | | | |-- GlobalTrackingReferenceTypeCode HAWB or tracking reference used by the carrier
194 1 | | | |-- ProprietaryShipmentTrackingIdentifier Tracking Number
195 0..n | |-- TrackingReference Header
196 1 | | |-- GlobalTrackingReferenceTypeCode "House Airwaybill Number"and/or "Master Supplier to provide
Airwaybill Number" and/or "Bill of Lading
Number"
197 1 | | |-- ProprietaryShipmentTrackingIdentifier Tracking ID Supplier to provide
198 1 | |-- transportedBy.PartnerDescription Header - The party responsible for either carrying or forwarding
the product. This could be either the supplier or Intel.
201 0..1 | | | |-- GlobalBusinessIdentifier Duns number of the company paying for Supplier to provide
shipment
207 1 | | | |-- contactName.FreeFormText
208 1 | | | |-- EmailAddress
211 1 | | |-- GlobalPartnerClassificationCode Carrier
213 0..1 | | | |-- GlobalLocationIdentifier


227 1 fromRole.PartnerRoleDescription Header - FromRole Information
228 1 |-- ContactInformation Header
229 1 | |-- contactName.FreeFormText FromRole Contact Name Supplier to provide
230 1 | |-- EmailAddress FromRole Email Email to be used to
receive errors from Intel
regarding this
transaction.
231 0..1 | |-- facsimileNumber.CommunicationsNumber Fax Number
232 1 | |-- telephoneNumber.CommunicationsNumber FromRole Phone Supplier to provide
233 1 |-- GlobalPartnerRoleClassificationCode "Shipper"
234 1 |-- PartnerDescription Header
235 1 | |-- BusinessDescription Header
236 1 | | |-- GlobalBusinessIdentifier From Duns Number Supplier to provide
237 0..1 | | |-- GlobalSupplyChainCode "Electronic
Components"
238 1 | |-- GlobalPartnerClassificationCode "Manufacturer"
239 1 GlobalDocumentFunctionCode "Request"
240 1 thisDocumentGenerationDateTime.DateTimeStamp DateTime PIP was generated Supplier to provide
241 1 thisDocumentIdentifier.ProprietaryDocumentIdentifier Packaging Slip Number Supplier to provide
242 1 toRole.PartnerRoleDescription Header - To Role Information
243 0..1 |-- ContactInformation Head
244 1 | |-- contactName.FreeFormText Contact Name
245 1 | |-- EmailAddress Email
246 0..1 | |-- facsimileNumber.CommunicationsNumber Fax Number
247 1 | |-- telephoneNumber.CommunicationsNumber Phone Number
248 1 |-- GlobalPartnerRoleClassificationCode "Receiver"
249 1 |-- PartnerDescription Header
250 1 | |-- BusinessDescription Header
251 1 | | |-- GlobalBusinessIdentifier Intel Duns "047897855"
252 0..1 | | |-- GlobalSupplyChainCode "Semiconductor
Manufacturing"
253 1 | |-- GlobalPartnerClassificationCode "Manufacturer"
The following elements are required for SIMI (supplier inventory management)/TSM (supplier managed) business
model:
 68 <ProprietaryBusinessIdentifier>, 69 <ProprietaryDomainIdenfiier>, 70 <ProprietaryIdentifierAuthority> to
provide the Intel vendor id (supplier number)
 98 <GlobalShippingServiceLevelCode>, where the previously used SIMI code of “REG” becomes “Regular” in
RosattaNet and SIMI code of “HOT” becomes “Expedited Service”
 118 <ProprietaryDomainIdentifier>, 119 <ProprietaryIdentifierAuthority>, 120
<ProprietaryLocationIdentifer> are looped to define the Intel Site Name and Stock Room
 131 <shipmentIdentifier.ProprietaryReferenceIdentifier>
 230 <EmailAddress> must be provided as the contact to receive error messages regarding the transaction
who is able to correct and resend the transaction
SAMPLE
The following is an example of the type of XML Advanced Shipment Notice that Intel would expect to receive
from its trading partners. If you would prefer an Excel version of this section, please ask your Trading Partner
Provisioner.

PO EXAMPLE
ContentType: Application/XML; RNSubType="preambleheader"
ContentDescription: This is the Preamble Header part of the business message
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">
<Preamble>
<DateTimeStamp>20030423T203037.842Z</DateTimeStamp>
<GlobalAdministeringAuthorityCode>RosettaNet</GlobalAdministeringAuthorityCode>
<GlobalUsageCode>Test</GlobalUsageCode>
<VersionIdentifier>1.1</VersionIdentifier>
</Preamble>
RNpartboundary
ContentType: Application/XML; RNSubType="serviceheader"
ContentDescription: This is the Service Header part of the business message
<!DOCTYPE ServiceHeader SYSTEM "ServiceHeaderPartMessageGuideline.dtd">
<ServiceHeader>
<ProcessControl>
<ProcessIdentity>
<GlobalProcessCode>Notify of Advance Shipment</GlobalProcessCode>
<GlobalProcessIndicatorCode>3B2</GlobalProcessIndicatorCode>
<initiatingPartner>
<GlobalBusinessIdentifier>111222333</GlobalBusinessIdentifier>
</initiatingPartner>
<InstanceIdentifier>PIDBCBCRNSIMTP10511298378420000024</InstanceIdentifier>
<VersionIdentifier>V01.01</VersionIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Shipper Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</fromService>
<toService>
<GlobalBusinessServiceCode>Receiver Service</GlobalBusinessServiceCode>
</toService>
</ServiceRoute>
<TransactionControl>
<AttemptCount>1</AttemptCount>
<PartnerRoleRoute>
<fromRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</fromRole>
<toRole>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
</toRole>
</PartnerRoleRoute>
<TransactionIdentity>
<description>
<FreeFormText>The Advance Shipment Notification contains detailed information on when product
shipped, expected date of arrival, how product shipped, and detail of the shipment
contents.</FreeFormText>

</description>
<GlobalTransactionCode>Notify of Advance Shipment</GlobalTransactionCode>
<InstanceIdentifier>TransID10511298378420000024</InstanceIdentifier>
</TransactionIdentity>
<ActionControl>
<ActionIdentity>
<description>
<FreeFormText>The Advance Shipment Notification contains detailed information on when product
shipped, expected date of arrival, how product shipped, and detail of the shipment
contents.</FreeFormText>
</description>
<GlobalBusinessActionCode>Advance Shipment Notification Action</GlobalBusinessActionCode>
<InstanceIdentifier>actionID1051129837842</InstanceIdentifier>
</ActionIdentity>
<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
<PartnerRoute>
<fromPartner>
<PartnerDescription>
<BusinessDescription>
</BusinessDescription>
<GlobalPartnerClassificationCode>Distributor</GlobalPartnerClassificationCode>
</PartnerDescription>
</fromPartner>
<toPartner>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</toPartner>
</PartnerRoute>
</ActionControl>
</TransactionControl>
</ProcessControl>
</ServiceHeader>
RNpartboundary
ContentType: Application/XML; RNSubType="servicecontent"
ContentDescription: This is the Service Content part of the business message
ContentTransferEncoding: binary
<!DOCTYPE Pip3B2AdvanceShipmentNotification SYSTEM "3B2_MS_V01_01_AdvanceShipmentNotification.dtd">
<Pip3B2AdvanceShipmentNotification>
<AdvancedShipmentNotification>
<BuyingPartner>
<purchasedBy>
<ContactInformation>
<contactName>
<FreeFormText>Scott Hubley</FreeFormText>
</contactName>
<EmailAddress>Scott.Hubley@Intel.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>4809999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
</telephoneNumber>

</ContactInformation>
<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>
<PhysicalLocation>
<PhysicalAddress>
<addressLine1>
<FreeFormText>45005 S. Dobson Rd. Attn:Rcvg</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Chandler</FreeFormText>
</cityName>
<NationalPostalCode>85248</NationalPostalCode>
<regionName>
<FreeFormText>AZ</FreeFormText>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</purchasedBy>
</BuyingPartner>
<OriginatingPartner>
<shipFrom>
<contactName>
<FreeFormText>Supplier Company</FreeFormText>
</contactName>
<EmailAddress>Joe.Supplier@supplier.com</EmailAddress>
<facsimileNumber>
</facsimileNumber>
<telephoneNumber>
</telephoneNumber>
<PhysicalLocation>
<PhysicalAddress>
<addressLine1>
<FreeFormText>First Street</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Phoenix</FreeFormText>
</cityName>
<regionName>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</shipFrom>
</OriginatingPartner>
<SellingPartner>
<soldBy>
<contactName>
</contactName>

<EmailAddress>Joe.Supplier@supplier.com</EmailAddress>
<facsimileNumber>
</facsimileNumber>
<telephoneNumber>
</telephoneNumber>
<PhysicalLocation>
<PhysicalAddress>
<addressLine1>
<FreeFormText>First Street</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Phoenix</FreeFormText>
</cityName>
<regionName>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</soldBy>
</SellingPartner>
<Shipment>
<freightPaymentAccount>
<AccountNumber>1111</AccountNumber>
</freightPaymentAccount>
<GlobalCarrierCode>DZAN</GlobalCarrierCode>
<GlobalShipmentModeCode>Air</GlobalShipmentModeCode>
<GlobalShippingServiceLevelCode>Air Cargo</GlobalShippingServiceLevelCode>
<numberOfShippingContainers>
<CountableAmount>1</CountableAmount>
</numberOfShippingContainers>
<ReceivingPartner>
<shipTo>
<GlobalBusinessIdentifier>Intel</GlobalBusinessIdentifier>
<contactName>
</contactName>
<facsimileNumber>
</facsimileNumber>
<telephoneNumber>
</telephoneNumber>
</shipTo>
</ReceivingPartner>
<shipmentIdentifier>
<ProprietaryReferenceIdentifier>987654321</ProprietaryReferenceIdentifier>
</shipmentIdentifier>
<ShipmentTransportationEvent>
<GlobalShipDateCode>Shipped on This Date</GlobalShipDateCode>
</ShipmentTransportationEvent>

<GlobalShipDateCode>Arrival at Destination Yard</GlobalShipDateCode>
<ShippingContainer>
<GlobalPackageTypeCode>Pallet</GlobalPackageTypeCode>
<MassPhysicalDimension>
<Weight>
<GlobalPhysicalUnitOfMeasureCode>Kilogram</GlobalPhysicalUnitOfMeasureCode>
<Mass>73.10</Mass>
</Weight>
</MassPhysicalDimension>
<shippingContainerIdentifier>
<ProprietarySerialIdentifier>Container1</ProprietarySerialIdentifier>
</shippingContainerIdentifier>
<ShippingContainerItem>
<DocumentSubLineLotShipReference>
<GlobalDocumentReferenceTypeCode>Purchase Order</GlobalDocumentReferenceTypeCode>
<LineNumber>0010</LineNumber>
<LotShipReference>
<LotIdentification>
<primaryLotIdentifier>
<ProprietaryReferenceIdentifier>LOT01</ProprietaryReferenceIdentifier>
</primaryLotIdentifier>
</LotIdentification>
<LotQuantity>
<GlobalLotQuantityClassificationCode>Acceptable</GlobalLotQuantityClassificationCode>
<GlobalProductUnitOfMeasureCode>Piece</GlobalProductUnitOfMeasureCode>
<ProductQuantity>3008</ProductQuantity>
</LotQuantity>
</LotShipReference>
<LotShipReference>
<LotIdentification>
<primaryLotIdentifier>
<ProprietaryReferenceIdentifier>LOT02</ProprietaryReferenceIdentifier>
</primaryLotIdentifier>
</LotIdentification>
<LotQuantity>
<GlobalLotQuantityClassificationCode>Acceptable</GlobalLotQuantityClassificationCode>
</LotQuantity>
</LotShipReference>
<ProprietaryDocumentIdentifier>5501011161</ProprietaryDocumentIdentifier>
<requestedQuantity>
</requestedQuantity>
<shippedLotQuantity>
</shippedLotQuantity>
</DocumentSubLineLotShipReference>
<isContainsHazardousMaterial>
<AffirmationIndicator>No</AffirmationIndicator>
</isContainsHazardousMaterial>
<ProductIdentification>
<PartnerProductIdentification>
<ProprietaryProductIdentifier>A7040600102</ProprietaryProductIdentifier>
</PartnerProductIdentification>
<ProprietaryProductIdentifier>M7040600102</ProprietaryProductIdentifier>
</ProductIdentification>

<shippedQuantity>
</shippedQuantity>
<shippingContainerItemIdentifier>
<ProprietarySerialIdentifier>111</ProprietarySerialIdentifier>
</shippingContainerItemIdentifier>
</ShippingContainerItem>
</ShippingContainer>
<TrackingReference>
<GlobalTrackingReferenceTypeCode>Bill of Lading Number</GlobalTrackingReferenceTypeCode>
<ProprietaryShipmentTrackingIdentifier>BLADNUM</ProprietaryShipmentTrackingIdentifier>
</TrackingReference>
<transportedBy>
<contactName>
<FreeFormText>DummyName</FreeFormText>
</contactName>
<EmailAddress>Dummy@dummy.com</EmailAddress>
<facsimileNumber>
</facsimileNumber>
<telephoneNumber>
</telephoneNumber>
</transportedBy>
</Shipment>
</AdvancedShipmentNotification>
<fromRole>
<contactName>
<FreeFormText>Jon Kakeno</FreeFormText>
</contactName>
<EmailAddress>Jkakeno@supplier.com</EmailAddress>
<telephoneNumber>
</telephoneNumber>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</fromRole>
<thisDocumentGenerationDateTime>
</thisDocumentGenerationDateTime>
<thisDocumentIdentifier>
</thisDocumentIdentifier>
<toRole>

<contactName>
<FreeFormText>Toshiyuki Sakamoto</FreeFormText>
</contactName>
<EmailAddress>toshiyuki.sakamoto@intel.com</EmailAddress>
<telephoneNumber>
</telephoneNumber>
</toRole>
</Pip3B2AdvanceShipmentNotification>
SIMI/TSM EXAMPLE
ContentType: application/xml; charset=UTF8; rnsubtype=preambleheader
ContentDescription: Preamble Header
<Preamble>
<GlobalUsageCode>Production</GlobalUsageCode>
</Preamble>
RNPartBoundary1052749559180
ContentType: application/xml; charset=UTF8; rnsubtype=serviceheader
ContentDescription: Service Header
<ServiceHeader>
<ProcessControl>
<ProcessIdentity>
<description>
<FreeFormText>The primary purpose of this PIP is to facilitate receiving product
shipments, provide information unique for a shipment and provide information needed for further
transportation and distribution.</FreeFormText>
</description>
<initiatingPartner>
<InstanceIdentifier>5qx.k0njeeh2.153964.a.k0vlikk6.153964</InstanceIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>

</fromService>
<toService>
</toService>
</ServiceRoute>
<PartnerRoleRoute>
<fromRole>
</fromRole>
<toRole>
</toRole>
</PartnerRoleRoute>
<description>
<FreeFormText>A Shipper issues an Advance Shipment Notification to a Receiver.</FreeFormText>
</description>
<InstanceIdentifier>5qx.k0njeeh2.153964..101.47897855.0</InstanceIdentifier>
<ActionControl>
<ActionIdentity>
<InstanceIdentifier>5tc.k0njeeh2.153964.</InstanceIdentifier>
</ActionIdentity>
<PartnerRoute>
<fromPartner>
</fromPartner>
<toPartner>
</toPartner>
</PartnerRoute>
</ActionControl>
</ProcessControl>
</ServiceHeader>
RNPartBoundary1052749559180
ContentType: application/xml; charset=UTF8; rnsubtype=servicecontent
ContentDescription: Service Content

<!DOCTYPE Pip3B2AdvanceShipmentNotification SYSTEM "3B2_MS_V01_01_AdvanceShipmentNotification.dtd">
<Pip3B2AdvanceShipmentNotification>
<AdvancedShipmentNotification>
<BuyingPartner>
<purchasedBy>
</purchasedBy>
</BuyingPartner>
<OriginatingPartner>
<shipFrom>
</shipFrom>
</OriginatingPartner>
<SellingPartner>
<soldBy>
<PartnerBusinessIdentification>
<ProprietaryBusinessIdentifier>206463001</ProprietaryBusinessIdentifier>
<ProprietaryDomainIdentifier>Vendor ID</ProprietaryDomainIdentifier>
<ProprietaryIdentifierAuthority>Intel</ProprietaryIdentifierAuthority>
</PartnerBusinessIdentification>
</soldBy>
</SellingPartner>
<Shipment>
<GlobalCarrierCode>FDEX</GlobalCarrierCode>
<GlobalShippingServiceLevelCode>Regular</GlobalShippingServiceLevelCode>
<numberOfShippingContainers>
<CountableAmount>1</CountableAmount>
</numberOfShippingContainers>
<ReceivingPartner>
<shipTo>
<businessName>
<FreeFormText>Intel</FreeFormText>
</businessName>
<contactName>
</contactName>
<PhysicalLocation>
<GlobalLocationIdentifier>0478978550S03</GlobalLocationIdentifier>
<PartnerLocationIdentification>
<ProprietaryDomainIdentifier>SiteName</ProprietaryDomainIdentifier>

<ProprietaryLocationIdentifier>Arizona</ProprietaryLocationIdentifier>
</PartnerLocationIdentification>
<PartnerLocationIdentification>
<ProprietaryDomainIdentifier>Stock Room</ProprietaryDomainIdentifier>
<ProprietaryLocationIdentifier>Fab 12 Store</ProprietaryLocationIdentifier>
</PartnerLocationIdentification>
<PhysicalAddress>
<addressLine1>
<FreeFormText>45005 S. Dobson Rd. Attn:Rcvg</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Chandler</FreeFormText>
</cityName>
<GlobalCountryCode>US</GlobalCountryCode>
<regionName>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</shipTo>
</ReceivingPartner>
<shipmentIdentifier>
<ProprietaryReferenceIdentifier>11922569</ProprietaryReferenceIdentifier>
</shipmentIdentifier>
<GlobalShipDateCode>Shipped on This Date</GlobalShipDateCode>
<GlobalShipDateCode>Arrival at Destination Yard</GlobalShipDateCode>
<ShippingContainer>
<GlobalPackageTypeCode>Box</GlobalPackageTypeCode>
<MassPhysicalDimension>
<Weight>
<GlobalPhysicalUnitOfMeasureCode>Kilogram</GlobalPhysicalUnitOfMeasureCode>
<Mass>0</Mass>
</Weight>
</MassPhysicalDimension>
<shippingContainerIdentifier>
<ProprietarySerialIdentifier>serial12345</ProprietarySerialIdentifier>
</shippingContainerIdentifier>
<ShippingContainerItem>
<DocumentSubLineLotShipReference>
<GlobalDocumentReferenceTypeCode>Shipping Reference
Identifier</GlobalDocumentReferenceTypeCode>
<LineNumber>1</LineNumber>
<shippedLotQuantity>
</shippedLotQuantity>
</DocumentSubLineLotShipReference>
<GlobalProductUnitOfMeasureCode>Box</GlobalProductUnitOfMeasureCode>
<isContainsHazardousMaterial>
<AffirmationIndicator>No</AffirmationIndicator>
</isContainsHazardousMaterial>
<ProductIdentification>
<ProprietaryProductIdentifier>PART1030528011</ProprietaryProductIdentifier>

</ProductIdentification>
<shippedQuantity>
</shippedQuantity>
<shippingContainerItemIdentifier>
<ProprietarySerialIdentifier>1</ProprietarySerialIdentifier>
</shippingContainerItemIdentifier>
</ShippingContainerItem>
</ShippingContainer>
<TrackingReference>
<GlobalTrackingReferenceTypeCode>Carrier Reference Number</GlobalTrackingReferenceTypeCode>
<ProprietaryShipmentTrackingIdentifier>627475567727/</ProprietaryShipmentTrackingIdentifier>
</TrackingReference>
<transportedBy>
<businessName>
</businessName>
</transportedBy>
</Shipment>
</AdvancedShipmentNotification>
<fromRole>
<contactName>
<FreeFormText>CSC</FreeFormText>
</contactName>
<EmailAddress>csc@aupplier.com</EmailAddress>
<telephoneNumber>
</telephoneNumber>
</fromRole>
<thisDocumentGenerationDateTime>
</thisDocumentGenerationDateTime>
<thisDocumentIdentifier>
</thisDocumentIdentifier>
<toRole>

</toRole>
</Pip3B2AdvanceShipmentNotification>
RECEIPT ACKNOWLEDGEMENT
Intel will send Trading Partners a receipt acknowledging that an ASN was successfully received and processed.
Below is a sample acknowledgement. If you would prefer a separate text file version of this section, please ask
your Trading Partner Provisioner.
ContentType: Multipart/Related; boundary="RNpartboundary"; type="Application/xRosettaNet"
ContentDescription: This is the RosettaNet business message
RNpartboundary
ContentType: Application/XML; RNSubType="preambleheader"; charset="UTF8"
ContentDescription: This is the Preamble Header part of the business message
<Preamble>
<GlobalUsageCode>Production</GlobalUsageCode>
</Preamble>
RNpartboundary
ContentType: Application/XML; RNSubType="serviceheader"; charset="UTF8"
ContentDescription: This is the Service Header part of the business message
<ServiceHeader>
<ProcessControl>
<ProcessIdentity>
<description>
<FreeFormText>The primary purpose of this PIP is to facilitate receiving product
shipments, provide information unique for a shipment and provide information needed for further
transportation and distribution.</FreeFormText>
</description>
<initiatingPartner>
<InstanceIdentifier>5qx.k0njeeh2.153964.a.k0vlikk6.153964</InstanceIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>
</fromService>
<toService>
</toService>
</ServiceRoute>

<PartnerRoleRoute>
<fromRole>
</fromRole>
<toRole>
</toRole>
</PartnerRoleRoute>
<description>
<FreeFormText>A Shipper issues an Advance Shipment Notification to a Receiver</FreeFormText>
</description>
<InstanceIdentifier>5qx.k0njeeh2.153964..101.47897855.0</InstanceIdentifier>
<SignalControl>
<inResponseTo>
<ActionIdentity>
<InstanceIdentifier>5tc.k0njeeh2.153964</InstanceIdentifier>
</ActionIdentity>
</inResponseTo>
<InstanceIdentifier>signalID1052749585012</InstanceIdentifier>
<PartnerRoute>
<fromPartner>
</fromPartner>
<toPartner>
</toPartner>
</PartnerRoute>
<SignalIdentity>
<GlobalBusinessSignalCode>Receipt Acknowledge</GlobalBusinessSignalCode>
</SignalIdentity>
</SignalControl>
</ProcessControl>
</ServiceHeader>
RNpartboundary
ContentType: Application/XML; RNSubType="servicecontent"; charset="UTF8"
ContentDescription: This is the Service Content part of the business message
<!DOCTYPE ReceiptAcknowledgement SYSTEM "ReceiptAcknowledgementMessageGuideline.dtd">
<ReceiptAcknowledgement>
<fromRole>

<contactName>
<FreeFormText>AMR RNET</FreeFormText>
</contactName>
<EmailAddress>AMR.RNET@intel.com</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>877.811.2574 option 4,2</CommunicationsNumber>
</telephoneNumber>
</fromRole>
<NonRepudiationInformation>
<GlobalDigestAlgorithmCode>MD5</GlobalDigestAlgorithmCode>
<OriginalMessageDigest>0zmPvx6TNnnhzWWncPY0SQ==</OriginalMessageDigest>
</NonRepudiationInformation>
<receivedDocumentDateTime>
</receivedDocumentDateTime>
<receivedDocumentIdentifier>
</receivedDocumentIdentifier>
<thisMessageDateTime>
</thisMessageDateTime>
<thisMessageIdentifier>
<ProprietaryMessageIdentifier>document0478978553661052749585012</ProprietaryMessageIdentifier>
</thisMessageIdentifier>
<toRole>
</toRole>
</ReceiptAcknowledgement>
TESTING
PURPOSE
Testing for Intel PIP follows the stages listed below:
Level 1 Establish transport and connectivity with Trading Partners using HTTPS. This is a test of each
Trading Partner’s public processes. These tests are defined in the connectivity guides for each
associated method.
Level 2 This stage tests the RosettaNet PIP structure and syntax. Within each Trading Partner’s public
process, testing is done to ensure the document is well formed and valid against the DTD. These

tests are defined in the connectivity guides for each associated method.
Level 3 This is a real-time, end-to-end integration test against Intel’s ERP system. This will be a test of the
private process for both Trading Partners.
TEST SCENARIOS
Once connectivity is successfully completed, the following transaction specific tests would be executed:
Step Description Expected Results For Intel As Receiver
3B2 - 1 Supplier sends a PIP 3B2, Advanced Shipment Structure and Domain Values correct for ASN.
Notification to Intel’s Test URL “Incoming Request Document” seen in BCRN (Intel’s
gateway) audit log.
3B2 - 2 Acknowledgement of receipt exists; Signal "Sending Receipt Acknowledgement" and "Delivering
ReceiptAcknowledgment Request Document to Private Process" in BCRN
(Intel’s gateway) audit log.
3B2 - 3 Enable digital signatures. Check the checkbox titled “Use Digital Signatures Where
Required”. Load the supplier’s P7B used for digital
signatures for Role “Buyer”, “Failure Report Administrator”,
and “PIP Failure Notifier”. BCRN (Intel’s gateway) enabled
for digital signatures.
3B2 - 4 Send of RosettaNet message (Advanced Shipment Notification) Structure and Domain Values correct for Advanced Shipment
with a digital signature. Supplier sends an Advanced Shipment Notification. “Incoming Request Document” seen in BCRN
Notification to Intel’s Test URL with a digital signature. (Intel’s gateway) audit log.
3B2 - 5 Send of Receipt Acknowledgement with digital signature. BCRN (Intel’s gateway) sends Receipt Acknowledgement
with a digital signature to the supplier in response to the
Purchase Order Request. “Sending Receipt
Acknowledgement” and “Delivering Request Document to
Private Process” in BCRN (Intel’s gateway) audit log.
3B2 - 6 NOF#1 from Supplier. Supplier changes the primary URL to send to Intel on to
something invalid (set Acknowledgement to valid URL after
milestone 30). Supplier tries to send Purchase Order
Request, after https failure Supplier will send PIP 0A1
Notification of Failure (NOF) on backup/secondary URL to
Intel. “Incoming Request Document” is seen in the audit log.
3B2 - 7 Send of Receipt Acknowledgement to NOF#1 from Supplier. “Sending Receipt Acknowledgement” is seen in the audit log.
Intel sends a Receipt Acknowledgement to the TP in response
to the NOF.
Once these basic tests are completed, it is recommended that the following test scenarios, specific to this PIP be
tested as they apply. Not all of these scenarios will apply to every supplier. Each Trading Partner should
determine with Intel which would be best to test and/or what additional tests should be added.
1. A discrete Purchase Order (PO)

2. A blanket PO
3. A single PO line item
4. Multiple PO line items on a single PO
5. A PO using Intel-managed freight
6. A PO using non-Intel managed freight
7. A PO with one shipping container
8. A PO with multiple shipping containers
9. A PO without "optional" tracking numbers

10. A secondary 3B2 transaction in response to a previously sent transaction that had been sent without
optional tracking numbers
11. Delete an ASN that has been sent
12. Against a known closed PO
13. An invalid PO number, where a Notification Of Failure [NOF] is generated and sent
14. With a quantity higher than the PO is approved for
15. With a quantity lower than the PO is approved for
16. With an estimated arrival date earlier than the one on the PO
17. With an estimated arrival date later than the one on the PO
18. With an invalid service header (should generate NOF)
19. With one or more required fields missing/blank (should generate NOF)
Once these tests are successfully entered into Intel’s private process with no technical errors, the Intel Business
Advocate/Buyer/Commodity Manager can review the data as follows:
1. From an Internet browser, the Intel Business Advocate will enter

http://ebgapps.intel.com/mseb/indicators/scdash-asnusg.asp in the address field or simply click on the
link in this document.
2. Select "ASN Report Summary Usage"
3. Enter a date range of: mm/dd/yy to mm/dd/yy
4. Click “Submit”.
Once the Business Advocate has reviewed and approved this information, and then preparation needs to be done
for production.
PRODUCTION
READINESS
Once the user acceptance testing is completed, we would ask that you please follow the procedure below for a
successful migration to production:
1. If you are using HTTPS, please ensure your B2B gateway is utilizing Intel’s production URL and verify
it with the Trading Partner Provisioner
2. If you are using HTTPS, send the Trading Partner Provisioner the supplier Trading Partner’s
production URL, Digital Certificate and Digital Signature if these are different from what was provided
in the HTTPs information sheet for testing
3. Establish a "go live" date when processing can begin in Intel’s production environment
4. When notification is received from Intel, please send an ASN transaction to validate connectivity in
the production environment
5. Intel will verify connectivity was established in production and when to begin sending transactions
SUPPORT
Any issues related to this implementation should be directed to your assigned Trading Partner Provisioner.

FREQUENTLY ASKED QUESTIONS

The following are questions from previous implementations of this PIP.
Q1 What are the most common errors seen in testing this transaction?
Below is a list of common errors that are encountered during testing:
1. <thisDocumentIdentifer> is not the same as the <shipmentIdentifier>. They both
should be the Packing Slip Number
2. <LineNumber> is sent as empty or NULL, which is not allowed
3. <requestedQuantity> is sent as empty, which is not allowed; it should be the total ship
quantity for the PO line
4. Missing Shipped on This Date in <ShipmentTransportationEvent.confirmedEvent>
5. Missed Arrival at Destination Yard in <ShipmentTransportationEvent>
6. <requestedQuantity> is sent as non-numeric, which is not allowed
7. <shippedLotQuantity> is sent as non-numeric or empty, which is not allowed
Q2 What is being tracked?

The goal of sending an ASN is to put an automated process in place that gives the receiver critical
information about shipment/s before they arrive. ASNs should help automate existing processes fro
both senders and receivers.
In-transit information:
 Specific events initiated by the carrier
 Concluded at Proof of Delivery (POD)
Tracked events:
 Part level detail on supplier shipment
 Airline information (for air shipments)
 Proof of Delivery (POD)
Direct connection with supplier’s systems to create touchless transactions is the key value for
implementing e-Business solutions.
Q3 How long will it take to prepare?

The implementation process requires multiple weeks of preparation and testing. Refer to the
implementation checklist in the Intel RosettaNet General Implementation Guide for estimated
durations for each activity
Q4 Which element should the “Packing slip number” be input ?

Intel requires to input the “Packing slip number” into
<shipmentIdentifier.ProprietaryReferenceIdentifier>. Intel recommends the suppliers to input the
“Packing slip number” into <TrackingReference> again to make your ASN message general. If the
supplier’s partner wanted to receive the “Packing slip number” from <TrackingReference>, this
solution could meet the requirement.
Q5 What Unit of Measurement code should be input to element for Dimension?

If Unit of Measurement code you are going to input to the elements is not available in the
<GlobalProductUnitOfMeasurementCode> list (message guide line file), please clarify if it could be
used or not with your Trading Partner Provisioner.
Q6 Can “Tender Information User” be input to

<GlobalPartnerRoleClassificationCode>?
Intel can receive “Tender Information User”, however, Trading Partners should use
“Receiver” to compliance to RosettaNet.
Q7 There appears to be no purchase order number referenced in this PIP. Is

purchase order an element of the 3B2 PIP?
The purchase order number is within the PIP as follows in the DTD section of this document:
<!ELEMENT DocumentSubLineReference (
GlobalDocumentReferenceTypeCode,
LineNumber?,
ProprietaryDocumentIdentifier,
subLineNumber?)>
And also seen as such in the XML sample section of this document:
<DocumentSubLineReference>
<GlobalDocumentReferenceTypeCode>Purchase
Order</GlobalDocumentReferenceTypeCode>
<ProprietaryDocumentIdentifier>MX1234567</ProprietaryDocumentIdentifier>
</DocumentSubLineReference>
The <GlobalDocumentReferenceTypeCode> indicates the type that can be a purchase order and
the <ProprietaryDocumentIdentifier> is contains the purchase order number.

GLOSSARY OF TERMS
-B-
BCRN Business Connect / RosettaNet (Tibco software used by Intel) Intel’s gateway
-D-
DTD Document Type Definition
-P-
PIP Partner Interface Process (PIP) is the RosettaNet model that depicts the activities,
decisions and Partner Role interactions that fulfill an eBusiness transaction
between two partners in a supply chain.
POD Proof of Delivery
-R-
RNIF RosettaNet Implementation Framework. The RNIF provides implementation
guidelines for those who wish to create interoperable software application
components that execute PIPs.
-S-
SIMI Supplier Inventory Management - Indirect
-T-
TSM Total Supplier Managed
Trading Partner The technical implementation specialist Intel assigns to assist trading partners
Provisioner with a RosettaNet implementation

DOCUMENT MANAGEMENT
Version Revision Date Modifier Description

1.00 05/12/2003 Patricia Ramirez First working draft for this version.
1.01 07/14/2003 Patricia Ramirez Specifically called out SIMI required elements.
1.02 07/17/2003 Patricia Ramirez Stronger note that trading partners need to
provide an email address in the <fromRole> to
be used to send errors with the transactions.
1.03 09/10/2003 John Alexander Updated revision number, date and new
hyperlink for Eroom. Inserted the audience
section and specifically called out the purpose of
SCAC codes. Inserted Intel DUNS references.
1.04 09/15/2003 John Alexander Removed references to BDE and updated data
mappings.


Supplier Guide (External Distribution Allowed)

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Supplier Guide (External Distribution Allowed)

Cargado por

Copyright:

Formatos disponibles

PIP 3B2 VERSION 01.

01: ADVANCED SHIPMENT NOTICE

Intended for Intel Supplier Trading Partners

Revision Date: 22 January 2018

Copyright 2003 Intel Corporation

THIS DOCUMENT IS VALID 30 DAYS FROM THE LATEST REVISION.

377232213.doc Page 2 of 31 Revised: 22 January 2018

INTEL KEY CONTACTS

BUSINESS ADVOCATE/BUYER/COMMODITY MANAGER – To represent the business processes involved in

RNIF Version 1.1 Version 2.0

377232213.doc Page 3 of 31 Revised: 22 January 2018

PIP0A1 Version 1.0 Version 2.0

377232213.doc Page 4 of 31 Revised: 22 January 2018

SERVICE LEVEL AGREEMENT (PERFORMANCE TIME REQUIREMENTS)

NAME DOCUMENT DESCRIPTION

377232213.doc Page 5 of 31 Revised: 22 January 2018

WHERE TO FIND PIPS

Intel Required Data in PIP

Line# Card SIMI Line Item Intel Description Values

377232213.doc Page 6 of 31 Revised: 22 January 2018

Line# Card SIMI Line Item Intel Description Values

377232213.doc Page 7 of 31 Revised: 22 January 2018

Line# Card SIMI Line Item Intel Description Values

98 1 | |-- GlobalShippingServiceLevelCode SLA for shipment SIMI "REG" =

377232213.doc Page 8 of 31 Revised: 22 January 2018

Line# Card SIMI Line Item Intel Description Values

377232213.doc Page 9 of 31 Revised: 22 January 2018

Line# Card SIMI Line Item Intel Description Values

377232213.doc Page 10 of 31 Revised: 22 January 2018

Line# Card SIMI Line Item Intel Description Values

377232213.doc Page 11 of 31 Revised: 22 January 2018

377232213.doc Page 12 of 31 Revised: 22 January 2018

377232213.doc Page 13 of 31 Revised: 22 January 2018

377232213.doc Page 14 of 31 Revised: 22 January 2018

377232213.doc Page 15 of 31 Revised: 22 January 2018

377232213.doc Page 16 of 31 Revised: 22 January 2018

377232213.doc Page 17 of 31 Revised: 22 January 2018

377232213.doc Page 18 of 31 Revised: 22 January 2018

377232213.doc Page 19 of 31 Revised: 22 January 2018

377232213.doc Page 20 of 31 Revised: 22 January 2018

377232213.doc Page 21 of 31 Revised: 22 January 2018

377232213.doc Page 22 of 31 Revised: 22 January 2018

377232213.doc Page 23 of 31 Revised: 22 January 2018

377232213.doc Page 24 of 31 Revised: 22 January 2018

377232213.doc Page 25 of 31 Revised: 22 January 2018

Step Description Expected Results For Intel As Receiver

1. A discrete Purchase Order (PO)

377232213.doc Page 26 of 31 Revised: 22 January 2018

1. From an Internet browser, the Intel Business Advocate will enter

377232213.doc Page 27 of 31 Revised: 22 January 2018

FREQUENTLY ASKED QUESTIONS

Q2 What is being tracked?

Q3 How long will it take to prepare?

Q4 Which element should the “Packing slip number” be input ?

Q5 What Unit of Measurement code should be input to element for Dimension?

377232213.doc Page 28 of 31 Revised: 22 January 2018

Q6 Can “Tender Information User” be input to

Q7 There appears to be no purchase order number referenced in this PIP. Is

377232213.doc Page 29 of 31 Revised: 22 January 2018

377232213.doc Page 30 of 31 Revised: 22 January 2018

Version Revision Date Modifier Description

377232213.doc Page 31 of 31 Revised: 22 January 2018

También podría gustarte