15
|
0..1
|
|--AccountDescription
|
Required tag
|
N/A
|
16
|
1
|
| |--accountName.FreeFormText
|
Send Bill-To Company Name.
Example: “Routers Inc.”
|
|
18
|
0..1
|
| |--billTo.PartnerRoleDescription
|
Required tag
|
|
19
|
1
|
| | | - ContactInformation
|
Required tag
|
|
20
|
0..1
|
| | | - contactName
|
contactName.freeFormText – send in Bill To Contact Name Acceptable formats - OR ,. For example – “John Galt” OR “John, Galt”
|
|
21
|
0..1
|
| | | - EmailAddress
|
The billTo contact email address
|
|
22
|
0..1`
|
| | | - facsimilieNumber.CommunicationsNumber
|
facsimilieNumber.
CommunicationsNumber is an optional tag and is not used by system.
Therefore, values sent here will be ignored.
|
Char (30)
|
23
|
0..1
|
| | | |--PhysicalAddress
|
Required tag
|
N/A
|
24
|
0..1
|
| | | | |--addressLine1.FreeFormText
|
Street address of billing company. Not used for order notes.
Example: “170 WEST TASMAN DRIVE”
|
CHAR(240)
|
27
|
0..1
|
| | | | |--cityName.FreeFormText
|
City of street address of billing company.
Example: “San Jose”
|
CHAR(60)
|
28
|
0..1
|
| | | | |--GlobalCountryCode
|
ISO country code of street address of billing company.
Example: “US”
|
CHAR(2)
|
29
|
0..1
|
| | | | |--GlobalLocationIdentifier
|
Partner’s GlobalLocationIdentifier:
Used to send Cisco BID ( Bill-To Identifier).
Cisco assigns a unique BID to each ordering entity and is required in PIP 3A4 PO Request.
If no bid, Cisco performs does order configuration validations with the default active BID corresponding to the submitter cco profile, if one is available, but order is rejected.
If numeric BID value is provided Cisco would perform BID validation and user entitlement checks and if they fail, Cisco would reject the order.
Cisco bid is always numeric and any non-numeric values coming in on bid on the request will result in the order being rejected upfront without any configuration validations being performed.
Partner may use their own BID that is mapped to a BID Cisco assigns this would necessitate a corresponding mapping in system. Please check with Cisco rep for this mapping.
In case of Brazil orders, the derivation is based on Partner BID + OperatingUnit value that is sent on the PO by partners.
Example: 12357135
|
CHAR(20)
|
30
|
0..1
|
| | | | |--NationalPostalCode
|
Required only for US and Canada addresses. If partner plans on using 10 digit code for American addresses, omit hyphen “-“ character. Hyphen “-“ character is not allowed. If valid BID provided, value is ignored.
|
CHAR(9)
|
32
|
0..1
|
| | | | |--regionName.FreeFormText
|
Required only for US and Canada addresses. Enter state or province of billing address.
Example: “NC” for North Carolina
|
CHAR(60)
|
33
|
0..1
|
| | | - telephoneNumber.CommunicationsNumber
|
The billTo Contact communications telephone number. Currently not used by system. Therefore, values sent here will be ignored.
|
Char (30)
|
34
|
1
|
| | |--GlobalPartnerRoleClassificationCode
|
Send the value “Buyer”.
|
N/A
|
35
|
1
|
| | |--PartnerDescription
|
Required tag
|
N/A
|
36
|
1
|
| | | |--BusinessDescription
|
Required tag
|
N/A
|
37
|
0..1
|
| | | | |--BusinessName.FreeFormText
|
Send the Bill-To Company Name.
Example: “Routers Inc.”
|
CHAR(50)
|