A partner may request the way to group the product lines into a ship set. This shipSetNumber name value pair is not read by the system. System assigns the ship set numbers internally, and In order to ship all ATOs on different shipset - PO request would need to have "GlobalSpecialFulfillmentRequestCode" as blank so its taken from User profile (if the user profile value is set up as Ship All items Separately = 'Y') or the PO can also have GlobalSpecialFulfillmentRequestCode ='SHIP PARTIAL - BALANCE BACK ORDER'
n.End User / Install Site
Partners should provide end user information if the Product Line Item is a hardware part, for example, Cisco2501. End user information is required for all resale orders.
Partners should specify the install site information, that is, the location where the hardware part will be serviced if the Product Line Item is a service part, for example, CON-SNT-2501. When partners are ordering a new service on a 3A4-XML order, Cisco returns warnings and recommends the other available service(s) in case the requested service is not available at the given install site.
Please contact your Cisco B2B project manager or technical lead for further information on address validation and mapping.
If there are only service products in the PO (that is, a Service Only PO), Cisco rejects the PO when the requested service level is not available at the given install site.
Cisco validates the provided ship to and end user addresses against country postal guidelines for completeness and validity. Addresses that do not conform to the below guidelines may cause the submitted order to require manual review by Cisco’s order processing Customer Service team. This can delay subsequent order cycles.
Note – In the case of a resale order with deal ID but no end customer information sent in on the order request, the end customer is picked from the deal and the Cisco Order Reason code is derived as Resale.
i. Guidelines
Please ensure you take the following guidelines into account when developing your ship to and end user address mapping:
Insert street address in line 1, unless additional department name or building information is required for delivery.
If additional company department or building information needs inclusion, please use address line 1 (and 2, if necessary). Place the street address in the next address line.
Insert contact names and contact details in the relevant contact elements, not in the address line fields.
Insert any additional delivery instructions in the packing slip or carton notes fields. For more information, see Section 4.12, Shipping and Packaging Notes.
Do not use PO Box references in end user addresses.
RegionName (state/province) is mandatory for Japan, US, or Canada addresses.
The following Address-Requirement Grid summarizes the minimum address data requirement for indicated country for a 3A4 XML order.
Table : Address Requirement Grid
2Country
|
ISO Code
|
End user Company Name
|
Address Line 1
|
Address Line 2
|
Address Line 3
|
City
|
State/
Province/ Region
|
Country
|
Postal Code
|
Australia
|
AU
|
|
Street address is mandatory. See above guidelines for placement.
|
|
O
|
|
|
Brazil
|
BR
|
|
|
O
|
|
|
Canada
|
CA
|
|
|
|
|
|
China
|
CN
|
|
|
O
|
|
|
France
|
FR
|
|
|
O
|
|
|
Germany
|
DE
|
|
|
O
|
|
|
Italy
|
IT
|
|
|
O
|
|
|
Japan
|
JP
|
|
|
|
|
|
UK
|
GB
|
|
|
O
|
|
|
USA
|
US
|
|
|
|
|
|
Other Countries
|
-
|
|
|
O
|
|
|
2 () is a required data for a valid address, it is commonly used in that country and will pass internal Cisco order validations
(O) is a optional data for a valid address, it is not part of common address format for that country.
(N/A) data is not required for a valid address; it is not used in that country.
Refer to appendix C for complete list of such rules.
Note: customer name, address line 1, and country are mandatory for performing address validation. System would reject the orders in case these mandatory elements are not provided on the PO and there is no address ID is provided on the PO. This is applicable to shipping, billing, reseller and end user/install site addresses.
Note – system has been enhanced to handle diacritics. Refer to Appendix H for more details on acceptable diacritics
Table : PIP 3A4 V02.00.00
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
127
|
1..n
|
|--ProductLineItem
|
Required tag
|
N/A
|
140
|
0..n
|
| |--CustomerInformation
|
Required tag
|
N/A
|
142
|
1
|
| | |--GlobalCustomerTypeCode
|
Send the value “End Customer”.
|
N/A
|
143
|
1
|
| | |--PartnerDescription
|
Required tag
|
N/A
|
144
|
1
|
| | | |--BusinessDescription
|
Required tag
|
N/A
|
145
|
0..1
|
| | | | |--businessName.FreeFormText
|
Send End Customer Company Name.
Example: “BigCompany Inc.”
|
CHAR(50)
|
150
|
1
|
| | | |--GlobalPartnerClassificationCode
|
Send the value “End User”.
|
N/A
|
151
|
0..1
|
| | | |--PhysicalAddress
|
Required tag
|
N/A
|
152
|
0..1
|
| | | | |--addressLine1.FreeFormText
|
Street address of End Customer company.
Example: “170 WEST TASMAN DRIVE”
Note: Field not used for order notes.In order to prevent CPE tasks, systems expects the Name, addressLine1 and Country for address creation or validation
|
CHAR(240)
|
153
|
0..1
|
| | | | |--addressLine2.FreeFormText
|
Street address of End Customer Company.
Example: “170 WEST TASMAN DRIVE”
Note: Field not used for order notes.
|
CHAR(240)
|
154
|
0..1
|
| | | | |--addressLine3.FreeFormText
|
The street address of End Customer company.
Example: “170 WEST TASMAN DRIVE”
Note: Field not used for order notes.
|
CHAR(240)
|
155
|
0..1
|
| | | | |--cityName.FreeFormText
|
The city of street address of End Customer company.
Example: “San Jose”
|
CHAR(60)
|
156
|
0..1
|
| | | | |--GlobalCountryCode
|
ISO country code of street address of End Customer Company. UPPERCASE only.
Example: “US”
Depending on country, system may expect other mandatory address elements like City and/or State
|
CHAR(2)
|
157
|
0..1
|
| | | | |--GlobalLocationIdentifier
|
If partners provide a valid location identifier, system uses this instead of the address on the PO. However a known system limitation is that an invalid ID on this tag results in an order rejection. Only numeric values accepted
|
CHAR (13)
|
158
|
0..1
|
| | | | |--NationalPostalCode
|
If partners plan to use 10 digit code for American addresses, omit hyphen “-“. Hyphen “-“ character is not allowed.
|
CHAR(9)
|
160
|
0..1
|
| | | | |--regionName.FreeFormText
|
Mandatory for Japan, US and Canada addresses. Enter state or province of End Customer address.
Example: “NC” for North Carolina
|
CHAR(60)
| ii.End Customer Notes
Partners can send any notes for their customers (for example – Customer PO Number) at header and/or line level in name value pair “EndCustomerNotes”. Cisco will not take any action on these notes, but these will be echoed back on POA and order submit email notification at line level. These customer notes will be printed on the shipping label and invoice in a future release.
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
304
|
0..1
|
| |-- proprietaryInformation.FreeFormText
|
Used to send multiple Cisco proprietary information in = format. Use ‘|’ as a delimiter for multiple values, and no whitespace should exist around equal sign.
Name: EndCustomerNotes
Example: EndCustomerNotes= customer notes
|
String of 35 Char
|
342
|
0..1
|
| |-- proprietaryInformation.FreeFormText
|
Used to send multiple Cisco proprietary information in = format. Use ‘|’ as a delimiter for multiple values, and no whitespace should exist around equal sign.
Name: EndCustomerNotes
Example: EndCustomerNotes=customer notes
|
String of 35 Char
|
Note – In case, there is a header level end Customer note and there are no line level end Customer notes, then system would default the header level end Customer note to the lines.
Note – System would associate EndCustomerNotes with the EndCustomerAddress for the line. For lines with same EndCustomerAddress, the EndCustomerNotes should be the same. System would always pick the EndCustomerNote from the first line within this address group and replicate it to the other lines of the group.
Share with your friends: |