c.Product Price
Set the MonetaryAmount field to the total extended price of the ProductLineItem. This is the total price for the product line item, and includes the discount and the quantity.
Discounted Price = List Price * (1-Discount)
Monetary Amount = Discounted Price * Ordered Quantity
Note: The product list price is published in the catalog using the 2A1 Product Information Notification Message Guideline. The following three values are required to look up a price in price catalog:
PriceListIdentifier in [PurchaseOrder.proprietaryInformation.FreeFormText] – Cisco price list identifier
Cisco Part Number in ProductIdentification.PartnerProductIdentification.ProprietaryProductIdentifier – Cisco part number. For example, Cisco2501
Product List Price in listPrice.FinancialAmount.MonetaryAmount
Note: The discount is not published in the price catalog. The partner’s Cisco account manager can provide the partner with the discount information.
A PO having whole sale price list and if the line monetary amount is not matching system calculated Net Price for that line will result in PO rejection.
The table that follows indicates the optional nature of ProductPrice. This fact is evidenced by a cardinality value of 0..1.
Table 71: PIP 3A4 Version 02.00.00 - Product Price
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
339
|
0..1
|
| |--totalLineItemAmount.FinancialAmount
|
Required Tag
|
N/A
|
340
|
1
|
| | |--GlobalCurrencyCode
|
Enter three-character ISO code for global currency. Although this is a required RosettaNet field, Cisco does not need this field to determine currency of the order. Cisco uses Price List in proprietaryInformation.FreeFormText to determine currency.
Example: “USD” for US dollars.
|
N/A
|
341
|
1
|
| | |--MonetaryAmount
|
Enter total price for line.
Do not enter currency symbol (for example, “$”) or thousands separator (“,”).
Example: 12000.25
|
NUMBER 9(13)V9(5)
| d.PO Amount
Partners are not required to send the PO Amount and discount information to Cisco for 3A4 XML orders. Cisco calculates the PO Amount by adding all of the MonetaryAmounts for the product lines for a 3A4-XML order.
If the price format is not valid, the order rejects. For example, if the price field contains non-numeric characters such as abc.xx, the order rejects.
The table that follows indicates the optional nature of PO Amount. This fact is evidenced by a cardinality value of 0..1.
Table 72: PIP 3A4 Version 02.00.00 for PO Amount
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
395
|
0..1
|
|-- totalAmount.FinancialAmount
|
Tag
|
N/A
|
396
|
1
|
| |--GlobalCurrencyCode
|
Three-character ISO code for global currency.
Example: “USD” for US dollars.
|
N/A
|
397
|
1
|
| |--MonetaryAmount
|
Total price for PO.
Do not enter currency symbol (for example, “$”) or thousands separator (“,”).
Example: 12000.25
|
NUMBER 9(13)V9(5)
| 23.Tax Exemption a.Tax Exempt Status
Partners should provide the tax exempt status for Australian, Canadian, and US 3A4 XML orders.
If the order is tax exempt, prior registration of the tax exemption certificate in Cisco’s ERP system is expected. The billing customer and shipping address identifies the order as Australian, Canadian, or from the US.
i.Canadian Orders
If isTaxExempt.AffirmationIndicator = ‘Yes”, then the order is NOT taxable.
If isTaxExempt.AffirmationIndicator = “NO”, then the Order is taxable.
Partner can provide the Canadian Tax code based on the shipping province specified in the shipping address in ProprietaryInformation.
The table that follows indicates the optional nature of tax exemption for Candadian orders. This fact is evidenced by a cardinality value of 0..1.
Table 73: PIP 3A4 Version 02.00.00 for Canadian Orders
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
342
|
0..1
|
|-- proprietaryInformation.FreeFormText
|
Use ‘|’ as a delimiter for multiple values and no whitespace should exist between Name and Value.
Canadian Tax Code
TaxCode=12345
|
|
If a null value is provided, a warning message is generated, and the order is considered as taxable.
If the tax code is not provided or is invalid, it defaults based on the shipping province provided. A warning message is generated.
ii.Australian Orders
Because all Australian orders are taxable, the partner must provide “No” to the isTaxExempt.AffirmationIndicator.
iii.US Orders
If isTaxExempt.AffirmationIndicator = “Yes”, then the order is NOT taxable.
Cisco will attempt to identify the tax exemption certificate number for the partner and apply the tax exemption appropriately. If Cisco is unable to find the tax exemption information for the partner, a warning message issues to the partner as part of the PO Acceptance document.
If isTaxExempt.AffirmationIndicator = “No”, then the Order is taxable. Cisco will automatically apply the appropriate taxes (based on the state specified in the shipping address).
If a null value is provided, a warning message generates as follows: “The order is considered as taxable”.
The table that follows indicates the optional nature of tax exemption for orders shipped within the US. This fact is evidenced by a cardinality value of 0..1.
Table 74: PIP 3A4 Version 02.00.00 for US Orders
No.
|
Cardinality
|
PIP Element
|
Notes
|
Field Length
|
390
|
0..1
|
|-- TaxExemptStatus
|
|
N/A
|
391
|
1
|
| |-- isTaxExempt.AffirmationIndicator
|
Indicates if order is taxable. Partner may provide a value of “yes” or “no” (fully spelled out).
Cisco looks at these field and GlobalTaxExemptionCode to determine if order should be taxed. For example, Cisco does not add tax to “Resale” orders if a valid resale certificate is on file with Cisco.
|
Predefined Values
|
393
|
1
|
| | |-- GlobalTaxExemptionCode
|
Indicates if order type is ‘Resale’. Valid Cisco values are:
“Exempt – for resale”
“Exempt – not for resale”
|
|
394
|
1
|
| | |-- taxExemptionCertificationIdentifier.ProprietaryReferenceIdentifier
|
|
CHAR(255)
|
Share with your friends: |