j.Co-Terming
The presence of an end date on the order indicates that the partner wishes to co-terminate all services and subscriptions on the order on the specified end date.
Co-terming is available for Maintenance only, M-lines, that is, for service or subscription lines where the product has been previously ordered and shipped.
Co-terming is for service only ordering, for all services ordered as standalone along with products, and for services ordered as standalone whose products have already procured.
The following is the logic for calculation of the List Price:
-
Calculate Service Duration in years.
k.ServiceDuration = (EndDate – StartDate + 1 – LeapDay)/365
l.LeapDay = Number of times Feb 29 falls between StartDate and EndDate
14.Find out SPA Duration Quantity for the line service level
a.DurationQty = 1 if Price in Price list is for 1 year
b.DurationQty = 2 if Price in pricelist is for 2 years and so on
15.Calculate Duration Factor
a.DurationFactor = ServiceDuration/DurationQty
16.Divide Price List List Price by Duration Factor to find prorated List Price
a.ListPrice = PriceListListPrice x DurationFactor
17.Round List Price using transaction currency rounding rules
a.If Transaction currency is JPY or KRW, round to 0 decimals
b.For all other currencies (USD/EUR/GBP, etc., round to two decimal places)
c.Donation Orders
Donation orders are orders submitted as part of Cisco Corporate Donation Program. This functionality allows members of the Cisco Corporate Donation Program to submit orders in CCW-B2B with the correct discount and also removes the manual processing that CPE had to do on all of these orders. To derive an order that is intended for Donation purposes, the system looks for a name value pair of Donations in the tag as described in the table that follows.
Note: Any other value sent as part of the name value pair is ignored and the order is processed as normal.
The table that follows indicates the optional nature of participation in donation orders. This fact is evidenced by a cardinality value of 0..1.
Table 1: PIP 3A4 Version 02.00.00 for Donation Orders
No.
|
Card
|
PIP Element
|
Notes
|
Field Length
|
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: Donations
Example: Donations=Y
|
CHAR(8)
|
CE – Country Enablement program’s charter is to enable Cisco’s local presence in the respective countries. BRICM – Brazil, Russia, India China, Mexico are the 5 countries where CE is driving to setup Cisco business entities in which is necessary to adhere to the compliance / legal rules of thosecountries.
As part of the Country Enablement initiative, the CCW B2B orders for Brazil would be placed within the Brazil business entity.
Also, in order to abide by any local legal and compliance requirements, certain business validations have been enabled. Refer to Appendix J for the complete list of CE Brazil rules. Any validation failures for these rules will result in PO rejection.
In case of Brazil orders, if partners are providing their local billing address ID (BID) and expecting Cisco to derive the corresponding Cisco BID, they need to send Cisco’s business operating unit for that transaction. Partners can find Cisco’s business operating unit for their billing address selected on a quote or estimate in the B2B output mechanism (Punchout shopping cart transfer, file export formats – CSV, TSV & XML, Acquire Quote web service and Get Estimate web service
Refer to Appendix I for list of current Cisco’s business operating units
Cisco BID is derived from the partner BID and operating unit value sent in on the PO. If no OperatingUnit is sent on such orders, then system will map Cisco Inc. BID associated with Partner BID.
Below is the placeholder for the new Name-Value pair on the PO for the Operating Unit.
Table 42: PIP 3A4 Version 02.00.00 – Operating Unit
No.
|
Card
|
PIP Element
|
Notes
|
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: OperatingUnit
Example: OperatingUnit= CISCO BRAZIL CA OPERATING UNIT
|
In case of Brazil transactions, Cisco will derive taxability on the PO as per the below logic
Table43: PIP 3A4 Version 02.00.00 – Taxability for Brazil transactions
TaxExemptAffirmationIndicator on PO
|
GlobalTaxExemptionCode on PO
|
Derived Taxability
|
N or Blank
|
NA
|
Internal Use
|
Y
|
Exempt For Resale
|
Resale
|
Y
|
Exempt Not For Resale
|
PO Rejection
|
Y
|
Blank
|
Internal Use
|
Y
|
Non Exempt Not For Resale
|
PO Rejected
|
Y
|
Non Exempt For Resale
|
PO Rejected
|
For Brazil orders, partners should send additional address related inscription information in the following name values pairs at header and line level respectively. If the inscription details are not present or incomplete for Brazil orders, there will be a delay in order booking.
Table44: PIP 3A4 Version 02.00.00 -Header level inscription address information for Brazil orders
No.
|
Card
|
PIP Element
|
Notes
|
Field Length / Data Constraints
|
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 –
ShipToLine4 (to indicate the neighborhood)
ShipToInscriptionNumber (* This should be the CNPJ number)
ShipToContributorClass
|
ShipToInscriptionNumber
Field Length : 150
Data Constraints : The format supported is “00.000.000/0000-00”
ShipToContributorClass
Field Length : 150
Data Constraints : accepted values are "CONTRIBUTOR" or "NON-CONTRIBUTOR"
|
Table 45: PIP 3A4 Version 02.00.00 for line level inscription address information for Brazil orders
No.
|
Card
|
PIP Element
|
Notes
|
Field Length / Data Constraints
|
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 –
ShipToLine4 =
ShipToInscriptionNumber (* This should be the CNPJ number)
ShipToContributorClass
EndUserLine4 =
EndUserInscriptionNumber
EndUserContributorClass
|
InscriptionNumber
Field Length : 150
Data Constraints : The format supported is “00.000.000/0000-00”
ContributorClass
Field Length : 150
Data Constraints : accepted values are "CONTRIBUTOR" or "NON-CONTRIBUTOR"
|
Share with your friends: |