Академический Документы
Профессиональный Документы
Культура Документы
Intel Corporation
https://eroom3.intel.com/eRoom/BET/2003DeploymentEnablement/0_a3cd
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
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)
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.
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:
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
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):
IMPLEMENTATION
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.
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
<?xml version="1.0" encoding="UTF8"?>
<!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>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Receiver Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</toService>
</ServiceRoute>
<TransactionControl>
<AttemptCount>1</AttemptCount>
<PartnerRoleRoute>
<fromRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</fromRole>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</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>
<VersionIdentifier>V01.01</VersionIdentifier>
</ActionIdentity>
<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
<PartnerRoute>
<fromPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>111222333</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Distributor</GlobalPartnerClassificationCode>
</PartnerDescription>
</fromPartner>
<toPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</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
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE Pip3B2AdvanceShipmentNotification SYSTEM "3B2_MS_V01_01_AdvanceShipmentNotification.dtd">
<Pip3B2AdvanceShipmentNotification>
<AdvancedShipmentNotification>
<BuyingPartner>
<purchasedBy>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>Scott Hubley</FreeFormText>
</contactName>
<EmailAddress>Scott.Hubley@Intel.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>4809999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
<CommunicationsNumber>4801111111</CommunicationsNumber>
</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>
</PartnerDescription>
</purchasedBy>
</BuyingPartner>
<OriginatingPartner>
<shipFrom>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>999999999</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>Supplier Company</FreeFormText>
</contactName>
<EmailAddress>Joe.Supplier@supplier.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>9999999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
<CommunicationsNumber>1111111111</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
<PhysicalLocation>
<PhysicalAddress>
<addressLine1>
<FreeFormText>First Street</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Phoenix</FreeFormText>
</cityName>
<NationalPostalCode>85023</NationalPostalCode>
<regionName>
<FreeFormText>AZ</FreeFormText>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</PartnerDescription>
</shipFrom>
</OriginatingPartner>
<SellingPartner>
<soldBy>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>999999999</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>Supplier Company</FreeFormText>
</contactName>
<EmailAddress>Joe.Supplier@supplier.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>9999999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
<CommunicationsNumber>1111111111</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
<PhysicalLocation>
<PhysicalAddress>
<addressLine1>
<FreeFormText>First Street</FreeFormText>
</addressLine1>
<cityName>
<FreeFormText>Phoenix</FreeFormText>
</cityName>
<NationalPostalCode>85023</NationalPostalCode>
<regionName>
<FreeFormText>AZ</FreeFormText>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</PartnerDescription>
</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>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>Intel</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>Scott Hubley</FreeFormText>
</contactName>
<EmailAddress>Scott.Hubley@Intel.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>9999999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
<CommunicationsNumber>1111111111</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</shipTo>
</ReceivingPartner>
<shipmentIdentifier>
<ProprietaryReferenceIdentifier>987654321</ProprietaryReferenceIdentifier>
</shipmentIdentifier>
<ShipmentTransportationEvent>
<DateStamp>20030415Z</DateStamp>
<GlobalShipDateCode>Shipped on This Date</GlobalShipDateCode>
</ShipmentTransportationEvent>
<ShipmentTransportationEvent>
<DateStamp>20030430Z</DateStamp>
<GlobalShipDateCode>Arrival at Destination Yard</GlobalShipDateCode>
</ShipmentTransportationEvent>
<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>
<GlobalProductUnitOfMeasureCode>Piece</GlobalProductUnitOfMeasureCode>
<ProductQuantity>5653</ProductQuantity>
</LotQuantity>
</LotShipReference>
<ProprietaryDocumentIdentifier>5501011161</ProprietaryDocumentIdentifier>
<requestedQuantity>
<ProductQuantity>8661</ProductQuantity>
</requestedQuantity>
<shippedLotQuantity>
<ProductQuantity>8661</ProductQuantity>
</shippedLotQuantity>
</DocumentSubLineLotShipReference>
<GlobalProductUnitOfMeasureCode>Piece</GlobalProductUnitOfMeasureCode>
<isContainsHazardousMaterial>
<AffirmationIndicator>No</AffirmationIndicator>
</isContainsHazardousMaterial>
<ProductIdentification>
<PartnerProductIdentification>
<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>
<ProprietaryProductIdentifier>A7040600102</ProprietaryProductIdentifier>
</PartnerProductIdentification>
<PartnerProductIdentification>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
<ProprietaryProductIdentifier>M7040600102</ProprietaryProductIdentifier>
</PartnerProductIdentification>
</ProductIdentification>
<shippedQuantity>
<ProductQuantity>8661</ProductQuantity>
</shippedQuantity>
<shippingContainerItemIdentifier>
<ProprietarySerialIdentifier>111</ProprietarySerialIdentifier>
</shippingContainerItemIdentifier>
</ShippingContainerItem>
</ShippingContainer>
<TrackingReference>
<GlobalTrackingReferenceTypeCode>Bill of Lading Number</GlobalTrackingReferenceTypeCode>
<ProprietaryShipmentTrackingIdentifier>BLADNUM</ProprietaryShipmentTrackingIdentifier>
</TrackingReference>
<transportedBy>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>999999999</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>DummyName</FreeFormText>
</contactName>
<EmailAddress>Dummy@dummy.com</EmailAddress>
<facsimileNumber>
<CommunicationsNumber>9999999999</CommunicationsNumber>
</facsimileNumber>
<telephoneNumber>
<CommunicationsNumber>1111111111</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</transportedBy>
</Shipment>
</AdvancedShipmentNotification>
<fromRole>
<PartnerRoleDescription>
<ContactInformation>
<contactName>
<FreeFormText>Jon Kakeno</FreeFormText>
</contactName>
<EmailAddress>Jkakeno@supplier.com</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>8152875913</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>999999999</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</fromRole>
<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
<thisDocumentGenerationDateTime>
<DateTimeStamp>20030415T110750.000Z</DateTimeStamp>
</thisDocumentGenerationDateTime>
<thisDocumentIdentifier>
<ProprietaryDocumentIdentifier>987654321</ProprietaryDocumentIdentifier>
</thisDocumentIdentifier>
<toRole>
<PartnerRoleDescription>
<ContactInformation>
<contactName>
<FreeFormText>Toshiyuki Sakamoto</FreeFormText>
</contactName>
<EmailAddress>toshiyuki.sakamoto@intel.com</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>8129846934</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</toRole>
</Pip3B2AdvanceShipmentNotification>
SIMI/TSM EXAMPLE
ContentType: application/xml; charset=UTF8; rnsubtype=preambleheader
ContentTransferEncoding: binary
ContentDescription: Preamble Header
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">
<Preamble>
<DateTimeStamp>20030512T142558.977Z</DateTimeStamp>
<GlobalAdministeringAuthorityCode>RosettaNet</GlobalAdministeringAuthorityCode>
<GlobalUsageCode>Production</GlobalUsageCode>
<VersionIdentifier>1.1</VersionIdentifier>
</Preamble>
RNPartBoundary1052749559180
ContentType: application/xml; charset=UTF8; rnsubtype=serviceheader
ContentTransferEncoding: binary
ContentDescription: Service Header
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE ServiceHeader SYSTEM "ServiceHeaderPartMessageGuideline.dtd">
<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>
<GlobalProcessCode>Notify of Advance Shipment</GlobalProcessCode>
<GlobalProcessIndicatorCode>3B2</GlobalProcessIndicatorCode>
<initiatingPartner>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</initiatingPartner>
<InstanceIdentifier>5qx.k0njeeh2.153964.a.k0vlikk6.153964</InstanceIdentifier>
<VersionIdentifier>V01.01</VersionIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Shipper Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</fromService>
<toService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Receiver Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</toService>
</ServiceRoute>
<TransactionControl>
<AttemptCount>1</AttemptCount>
<PartnerRoleRoute>
<fromRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</fromRole>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</toRole>
</PartnerRoleRoute>
<TransactionIdentity>
<description>
<FreeFormText>A Shipper issues an Advance Shipment Notification to a Receiver.</FreeFormText>
</description>
<GlobalTransactionCode>Notify of Advance Shipment</GlobalTransactionCode>
<InstanceIdentifier>5qx.k0njeeh2.153964..101.47897855.0</InstanceIdentifier>
</TransactionIdentity>
<ActionControl>
<ActionIdentity>
<GlobalBusinessActionCode>Advance Shipment Notification Action</GlobalBusinessActionCode>
<InstanceIdentifier>5tc.k0njeeh2.153964.</InstanceIdentifier>
<VersionIdentifier>V01.01</VersionIdentifier>
</ActionIdentity>
<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
<PartnerRoute>
<fromPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</fromPartner>
<toPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</toPartner>
</PartnerRoute>
</ActionControl>
</TransactionControl>
</ProcessControl>
</ServiceHeader>
RNPartBoundary1052749559180
ContentType: application/xml; charset=UTF8; rnsubtype=servicecontent
ContentTransferEncoding: binary
ContentDescription: Service Content
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE Pip3B2AdvanceShipmentNotification SYSTEM "3B2_MS_V01_01_AdvanceShipmentNotification.dtd">
<Pip3B2AdvanceShipmentNotification>
<AdvancedShipmentNotification>
<BuyingPartner>
<purchasedBy>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>
</PartnerDescription>
</purchasedBy>
</BuyingPartner>
<OriginatingPartner>
<shipFrom>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</shipFrom>
</OriginatingPartner>
<SellingPartner>
<soldBy>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
<PartnerBusinessIdentification>
<ProprietaryBusinessIdentifier>206463001</ProprietaryBusinessIdentifier>
<ProprietaryDomainIdentifier>Vendor ID</ProprietaryDomainIdentifier>
<ProprietaryIdentifierAuthority>Intel</ProprietaryIdentifierAuthority>
</PartnerBusinessIdentification>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</soldBy>
</SellingPartner>
<Shipment>
<GlobalCarrierCode>FDEX</GlobalCarrierCode>
<GlobalShippingServiceLevelCode>Regular</GlobalShippingServiceLevelCode>
<numberOfShippingContainers>
<CountableAmount>1</CountableAmount>
</numberOfShippingContainers>
<ReceivingPartner>
<shipTo>
<PartnerDescription>
<BusinessDescription>
<businessName>
<FreeFormText>Intel</FreeFormText>
</businessName>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<ContactInformation>
<contactName>
<FreeFormText>Scott Hubley</FreeFormText>
</contactName>
<EmailAddress>Scott.Hubley@Intel.com</EmailAddress>
</ContactInformation>
<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>
<PhysicalLocation>
<GlobalLocationIdentifier>0478978550S03</GlobalLocationIdentifier>
<PartnerLocationIdentification>
<ProprietaryDomainIdentifier>SiteName</ProprietaryDomainIdentifier>
<ProprietaryIdentifierAuthority>Intel</ProprietaryIdentifierAuthority>
<ProprietaryLocationIdentifier>Arizona</ProprietaryLocationIdentifier>
</PartnerLocationIdentification>
<PartnerLocationIdentification>
<ProprietaryDomainIdentifier>Stock Room</ProprietaryDomainIdentifier>
<ProprietaryIdentifierAuthority>Intel</ProprietaryIdentifierAuthority>
<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>
<NationalPostalCode>85248</NationalPostalCode>
<regionName>
<FreeFormText>AZ</FreeFormText>
</regionName>
</PhysicalAddress>
</PhysicalLocation>
</PartnerDescription>
</shipTo>
</ReceivingPartner>
<shipmentIdentifier>
<ProprietaryReferenceIdentifier>11922569</ProprietaryReferenceIdentifier>
</shipmentIdentifier>
<ShipmentTransportationEvent>
<DateStamp>20030509Z</DateStamp>
<GlobalShipDateCode>Shipped on This Date</GlobalShipDateCode>
</ShipmentTransportationEvent>
<ShipmentTransportationEvent>
<DateStamp>20030511Z</DateStamp>
<GlobalShipDateCode>Arrival at Destination Yard</GlobalShipDateCode>
</ShipmentTransportationEvent>
<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>
<ProprietaryDocumentIdentifier>11922569</ProprietaryDocumentIdentifier>
<shippedLotQuantity>
<ProductQuantity>1</ProductQuantity>
</shippedLotQuantity>
</DocumentSubLineLotShipReference>
<GlobalProductUnitOfMeasureCode>Box</GlobalProductUnitOfMeasureCode>
<isContainsHazardousMaterial>
<AffirmationIndicator>No</AffirmationIndicator>
</isContainsHazardousMaterial>
<ProductIdentification>
<PartnerProductIdentification>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
<ProprietaryProductIdentifier>PART1030528011</ProprietaryProductIdentifier>
</PartnerProductIdentification>
</ProductIdentification>
<shippedQuantity>
<ProductQuantity>1</ProductQuantity>
</shippedQuantity>
<shippingContainerItemIdentifier>
<ProprietarySerialIdentifier>1</ProprietarySerialIdentifier>
</shippingContainerItemIdentifier>
</ShippingContainerItem>
</ShippingContainer>
<TrackingReference>
<GlobalTrackingReferenceTypeCode>Carrier Reference Number</GlobalTrackingReferenceTypeCode>
<ProprietaryShipmentTrackingIdentifier>627475567727/</ProprietaryShipmentTrackingIdentifier>
</TrackingReference>
<transportedBy>
<PartnerDescription>
<BusinessDescription>
<businessName>
<FreeFormText>Supplier Company</FreeFormText>
</businessName>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</transportedBy>
</Shipment>
</AdvancedShipmentNotification>
<fromRole>
<PartnerRoleDescription>
<ContactInformation>
<contactName>
<FreeFormText>CSC</FreeFormText>
</contactName>
<EmailAddress>csc@aupplier.com</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>5554241605</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</fromRole>
<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>
<thisDocumentGenerationDateTime>
<DateTimeStamp>20030512T092548.000Z</DateTimeStamp>
</thisDocumentGenerationDateTime>
<thisDocumentIdentifier>
<ProprietaryDocumentIdentifier>11922569</ProprietaryDocumentIdentifier>
</thisDocumentIdentifier>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</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
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">
<Preamble>
<DateTimeStamp>20030512T142625.012Z</DateTimeStamp>
<GlobalAdministeringAuthorityCode>RosettaNet</GlobalAdministeringAuthorityCode>
<GlobalUsageCode>Production</GlobalUsageCode>
<VersionIdentifier>1.1</VersionIdentifier>
</Preamble>
RNpartboundary
ContentType: Application/XML; RNSubType="serviceheader"; charset="UTF8"
ContentDescription: This is the Service Header part of the business message
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE ServiceHeader SYSTEM "ServiceHeaderPartMessageGuideline.dtd">
<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>
<GlobalProcessCode>Notify of Advance Shipment</GlobalProcessCode>
<GlobalProcessIndicatorCode>3B2</GlobalProcessIndicatorCode>
<initiatingPartner>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</initiatingPartner>
<InstanceIdentifier>5qx.k0njeeh2.153964.a.k0vlikk6.153964</InstanceIdentifier>
<VersionIdentifier>V01.01</VersionIdentifier>
</ProcessIdentity>
<ServiceRoute>
<fromService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Receiver Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</fromService>
<toService>
<BusinessServiceDescription>
<GlobalBusinessServiceCode>Shipper Service</GlobalBusinessServiceCode>
</BusinessServiceDescription>
</toService>
</ServiceRoute>
<TransactionControl>
<AttemptCount>1</AttemptCount>
<PartnerRoleRoute>
<fromRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</fromRole>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
</PartnerRoleDescription>
</toRole>
</PartnerRoleRoute>
<TransactionIdentity>
<description>
<FreeFormText>A Shipper issues an Advance Shipment Notification to a Receiver</FreeFormText>
</description>
<GlobalTransactionCode>Notify of Advance Shipment</GlobalTransactionCode>
<InstanceIdentifier>5qx.k0njeeh2.153964..101.47897855.0</InstanceIdentifier>
</TransactionIdentity>
<SignalControl>
<inResponseTo>
<ActionIdentity>
<GlobalBusinessActionCode>Advance Shipment Notification Action</GlobalBusinessActionCode>
<InstanceIdentifier>5tc.k0njeeh2.153964</InstanceIdentifier>
</ActionIdentity>
</inResponseTo>
<InstanceIdentifier>signalID1052749585012</InstanceIdentifier>
<PartnerRoute>
<fromPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</fromPartner>
<toPartner>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</toPartner>
</PartnerRoute>
<SignalIdentity>
<GlobalBusinessSignalCode>Receipt Acknowledge</GlobalBusinessSignalCode>
<VersionIdentifier>1.1</VersionIdentifier>
</SignalIdentity>
</SignalControl>
</TransactionControl>
</ProcessControl>
</ServiceHeader>
RNpartboundary
ContentType: Application/XML; RNSubType="servicecontent"; charset="UTF8"
ContentDescription: This is the Service Content part of the business message
ContentTransferEncoding: binary
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE ReceiptAcknowledgement SYSTEM "ReceiptAcknowledgementMessageGuideline.dtd">
<ReceiptAcknowledgement>
<fromRole>
<PartnerRoleDescription>
<ContactInformation>
<contactName>
<FreeFormText>AMR RNET</FreeFormText>
</contactName>
<EmailAddress>AMR.RNET@intel.com</EmailAddress>
<telephoneNumber>
<CommunicationsNumber>877.811.2574 option 4,2</CommunicationsNumber>
</telephoneNumber>
</ContactInformation>
<GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</fromRole>
<NonRepudiationInformation>
<GlobalDigestAlgorithmCode>MD5</GlobalDigestAlgorithmCode>
<OriginalMessageDigest>0zmPvx6TNnnhzWWncPY0SQ==</OriginalMessageDigest>
</NonRepudiationInformation>
<receivedDocumentDateTime>
<DateTimeStamp>20030512T142558.977Z</DateTimeStamp>
</receivedDocumentDateTime>
<receivedDocumentIdentifier>
<ProprietaryDocumentIdentifier>11922569</ProprietaryDocumentIdentifier>
</receivedDocumentIdentifier>
<thisMessageDateTime>
<DateTimeStamp>20030512T142625.012Z</DateTimeStamp>
</thisMessageDateTime>
<thisMessageIdentifier>
<ProprietaryMessageIdentifier>document0478978553661052749585012</ProprietaryMessageIdentifier>
</thisMessageIdentifier>
<toRole>
<PartnerRoleDescription>
<GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
<PartnerDescription>
<BusinessDescription>
<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>
<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>
</BusinessDescription>
<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>
</PartnerDescription>
</PartnerRoleDescription>
</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:
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.
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:
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.
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
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.
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