IG Version: 29.0
|
118
|
Added additional LOVs (Dock, Pick-up) for TransportEventCode
|
Section 4.9.2
|
Q2FY16
|
117
|
Added:
Contract ‘New’ or Use Existing’ to be defaulted from profiles and preferences of the user if not sent in the PO request
|
Section 5.7.1
|
Q2FY16
|
116
|
Updated:
-
Changed the attribute “RoHS_Terms” for Refurbished / Pre-owned SKUs
-
Meraki Ordering validation changes for Enterprise and Advanced Security licenses
Added: Changes in Purchase Order Request for below Q4Fy15 ordering enhancement
-
Co-term of Initial Purchase SWSS Technical Service (End date Alignment for Technical Services)
|
Section 7.12
Section 5.3.4
Section 7.15
|
|
115
|
Updated: Changed the content for SWIFT / eDelivery email address
Added: Changes in Purchase Order request for below Q2FY15 ordering enhancements
-
Refurbished / Pre-owned SKU ordering
-
Cisco Smart Software Licensing
-
Ultimate Consignee Address and Type
|
Section 7.10
Section 7.12
Section 7.13, Appendix K
Section 7.14
|
Q2FY14
|
114
|
Added: Support for Technical Services (TSS) with duration up to 60 months
|
Notes under section 5.7.1
|
Q4Fy14
|
113
|
Added: Additional scenario for FSSD Order Rejection validation
|
Table under section 7.11
|
Q4FY14
|
112
|
Added: PO rejection for Global RNSD
|
Table 32 under section 5.11
|
Q3FY14 PR2
|
111
|
Added: Fulfillment Restriction details for 3A4 Order
|
5.3.3
|
Q4FY14
|
110
|
Updated: Contract Start Date for Initial purchase of services
|
5.7.1
|
Not Applicable
|
109
|
Updated: CE Brazil – Product and Service ordering business rules
|
Appendix J
|
Q4 FY14
|
108
|
Removed sample error message table as the validation details are called out in the respective sections
|
Appendix A
|
Not Applicable
|
107
|
Added: CE Brazil - As part of the Country Enablement initiative, Cisco will enable Brazil place orders on the to-be CE Brazil Business Operating Unit via B2B.
|
6.12
|
Q4FY14
|
106
|
Updated: Content on Order Ack Emails – Order ack emails will include the Partner Name or CCO ID and any order notes, end customer notes that is sent in on the PO.
|
12.1
|
Q4Fy14
|
105
|
Updated: Ordering services/subscriptions attached to system included items- In case of ordering services/subscriptions attached to system included items, partners are expected to send the system included items along with the associated services/subscriptions on the PO
|
5.5
|
Q4FY14
|
104
|
Added: FlexibleServiceStartDelay - FSSD allows partners to order Product + Service in CCW and automatically delay service start up to 60 days after ship date.
|
7.11
|
Q4FY14
|
103
|
Updated: Deal ID validations – Deal ID validation enhancements to reduce order booking cycle.
|
5.11
|
Q3Fy14
|
102
|
Updated:Rejection Email Addressee list – In case of rejections system will send out the rejection status email to the email address(es) in OrderAck name-value pair and/or email addresses of the DUNS setup in Cisco’s B2B ordering system.
|
12.2
|
Q3FY14
|
101
|
Added: Reseller Information on PO – Partners are expected to send reseller information on the PO in the SecondaryBuyer tags at header level. System will no longer read reseller information from the freeform Text name value pairs at header or line level.
|
5.7.3
|
Feb MR
|
99
|
Updated: LOV values for GlobalPurchaseOrderTypeCode – Updated the valid values that system accepts in the GlobalPurchaseOrderTypeCode to reflect RN Compliance. Specifically, change to accept “Consigned order”
|
4.6
|
Q3Fy14
|
98
|
Updated: Order Contact defaulting – In case the order contact information is not explicitly provided in the PO (no order contact name-value pairs), system will default the order contact information from the fromRole/PartnerRoleDescription/ContactInformation tags
|
7.6
|
Q3FY14
|
97
|
Updated: End User information on POA – Partners will receive the end user information on the POA in the scenario when the end user is not specified on the PO and has been picked from the deal.
|
11
|
Q3Fy14
|
96
|
Updated: Mandatory elements in addresses- PO’s not having mandatory elements in the addresses (End-user, billTo, ShipTo, Reseller, Install site at header or line as applicable) – will be rejected
|
4.14.1
|
Q3Fy14
|
95
|
Updated: Duration Defaulting for Services and Subscriptions – In case of partners not specifying the Contract Duration or Contract Start date and Contract End Date on the PO, system defaults the duration based on the standard duration that has been setup for the service/subscription.
|
5.7.1
|
Q3Fy14
|
94
|
Added: 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”.
|
4.14.2
|
Q3FY14
|
93
|
Added: Ordering Primary and Secondary Technical Services - Secondary coverage is sold as a compliment to a primary coverage when additional service is needed that is not included in the primary service program. Ordering of these Secondary services and the validations associated with them.
|
5.7.2
|
Q3FY14
|
92
|
Updated: Price list mismatch error- 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.
|
8.3
|
Q3FY14
|
91
|
Added: Order Notes - Partners can enter order notes on the Purchase Order for their own references. Cisco would not take any action on these but these can be viewed on the Order View status screens.
|
7.9
|
Q3FY14
|
90
|
Updated: Deal Validation Error Messages/Warnings updated based on the current implementation
|
Appendix A
|
Q2FY14
|
89
|
Updated: Deal ID format update
|
5.11
|
Q2FY14
|
88
|
Updated: End User information when picked up from Deal will be sent back on the Purchase Order Confirmation
|
11
|
To be updated
|
87
|
Updated: End User Address ID when on the PO, needs to be numeric only
|
4.14
|
Q2FY14
|
86
|
Updated: Support enabled for multiple Serial Numbers on PO for a service line
|
5.6
|
Q2FY14
|
85
|
Updated: Rules for mandatory address elements per country for all address sections have been updated
|
Appendix C
|
Q2FY14
|
84
|
Updated: Support for service contract durations greater than 36 months is enabled on orders with Non stzndard deals or for OSM/OEM users
|
5.7.1
|
Q1FY14
|
83
|
Updated: DotX recognized pattern is “x” instead of “X” or “LATEST”
|
7.2
|
Q1FY14
|
82
|
Updated: The subject line of the email message regarding acceptance contains web order ID and the po number
|
11
|
Q1FY14
|
81
|
Updated: PO’s which have TAA+ SKU’s but if partners have not indicated that the order be TAA compliant, then order is rejected
|
6.3.2
|
Q1FY14
|
80
|
Updated: Ship set number assignment is done internally during order processing. In order for partners to request shipping all items separately, they can either have "GlobalSpecialFulfillmentRequestCode" as blank so it’s taken from User profile ( it can get setup as Ship All items Separately = 'Y') or the user can also send GlobalSpecialFulfillmentRequestCode ='SHIP PARTIAL - BALANCE BACK ORDER'
|
4.13
|
Q1Fy14
|
79
|
Updated: Contract start date is not defaulted with the requested ship date for services. If no values are provided on the PO, contract duration is defaulted.
|
|
Q1FY14
|
78
|
Updated: Purchase order confirmation emails going out – the format of the accept email message contains a lot more detail
|
Section 11
|
July 2013
|
77
|
Updated: Known limitations for kitRef and ConfigRef – ZPL is not supported on kitRef and ConfigRef orders
|
Section 7.3 and section 7.4
|
July 2013
|
76
|
Updated: Shipping Information defaulting. When carrier information and carrier account number is not provided on the PO request, but the routing preference is Customer Routed, then system defaults this information from the SRC tool for the user profile. This derivation happens before the order is imported into ERP but is not reflected on the POA. In case these are not setup in the SRC tool, then system raises tasks to reflect the same.
|
Section 4.11
|
June 2013
|
75
|
Updated: End User/install Site contact information. System expects Contact Name, Address Line 1 and Country as required attributes to create new contact. Depending upon the country there may be other fields that the system expects like City and/or state in order to create or validate contacts. If contacts are not created/validated, system reports a warning to the same effect
|
Section 4.14.1
|
June 2013
|
74
|
Added: Reseller BID information can be sent by partners at line level or header level
|
Section 5.7.1
|
June 2013
|
73
|
Added: Meraki SKU ordering needs contact and address information for processing without delays
|
Section 5.3.4
|
May 2013
|
72
|
Added: Partial Service Ordering enables distributors place resale service orders even for products that have not yet been shipped
|
Section 5.6
|
May 2013
|
71
|
Added: Delivery Options enables partners to send in requested delivery option details on a purchase order
|
Section 4.10
|
May 2013
|
70
|
Added: Changes in relation to kitRef
|
Section 7.3
|
May 2013
|
69
|
Added: Changes in relation to ConfigRef
|
Section 7.4
|
May 2013
|
68
|
Added: Purchase order confirmation header and line level values sent back from system is detailed
|
Section 11
|
April 2013
|
67
|
Added: Product References format updated. Partners can now send Redundancy and/or default flags as part of the configuration Information at line level. System ignores values send as selection sequence. System is also able to derive the Redundancy and default flags, along with config path and selection flags at line level based on the Cisco Product Reference Code aka hash code.
|
Section 10.2.1
|
April 2013
|
66
|
Added: Order Reference is echoed back on a POA.
|
Section 7.6
|
April 2013
|
65
|
Added: On a POA, the po line ref at line level, in case of zero priced system added SKU lines, is truncated to 6 characters to be in line with RN standards
|
Section 7.1
|
April 2013
|
64
|
Added: Note – In case Contract duration is not provided on an order for subscription SKU’s, systems defaults this attribute internally. If a Contract start date is not provided for subscription SKU’s then system defaults this from the requested ship date at the corresponding line level or current date (if requested ship date is unavailable).
|
Section 6.9
|
April 2013
|
63
|
Added: In case an invalid TAB deal is provided on a TAB order, the system performs configuration validations, but rejects the order
|
Section 6.4
|
April 2013
|
61
|
Added: Known system limitation around processing of multiple serial numbers at line level.
|
Section 5.6
|
April 2013
|
60
|
Added: Accepted values in the ProductIdentification/PartnerProductIdentification/GlobalPartnerClassification at a line level. On a POA, this value would be “Manufacturer” for all lines
|
Section 5.3.2
|
April 2013
|
57
|
Added: Acceptable formats for billTo/contactName are or , .
|
Sectio 4.7
|
April 2013
|
56
|
Added: Acceptable values on BID (billTo/GlobalLocationIdentifier) and details around invalid/missing values on BID
|
Section 4.7
|
April 2013
|
55
|
Added: Note: Any other values sent other than Contract (as specified in the table that follows) will be ignored.
|
Section 5.11
|
March 2013
|
54
|
Added: Invalid value: 00000000Z. If provided, the system will default to Submit Date +1
|
Tables 14 (Element 306) and 15 (Element 344) in Section 4.9.2, Shipping Address
|
March 2013
|
53
|
Added:
Known Limitation
The system cannot currently proceed with processing orders with only service lines, but no serial number information/PAK number information at line level.
|
Section 5.6
|
March 2013
|
52
|
Added:
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 removes the manual processing that CPE had to do on all of these orders. To derive an order intended for Donation purposes, the system looks for a name value pair of Donations in the tag as described in the table that follows. (See Section 6.11 to view the table.) Note: Any other value sent as part of the name value pair is ignored and the order is processed as normal.
|
Section 6.11
|
March 2013
|
51
|
Added: Donations (Element #304) column to Table 9: Values Set for Cisco Order Reason – 3A4 XML.
Condensed view of the table follows:
Global PO Type Code (Element #92)
|
Donations (Element #304)
|
Evaluation
|
Not Considered
|
Sample
|
Not Considered
|
Service
|
Not Considered
|
Replenishment
|
Not Considered
|
Site
|
Not Considered
|
Consigned order
|
Not Considered
|
Standard
|
Not Provided
|
Standard
|
Not Provided
|
Standard
|
Y
|
|
Section 4.6, Table 9
|
March 2013
|
50
|
Added: The use of ServiceFor (Element #304) tag has been discontinued. Partners will have to send Line ID and Parent Line ID to indicate the service linkage.
|
Section 4.17
|
March 2013
|
49
|
Changed: Changed “Consiged Order” to “Consigned order” in all instances of use in the Implementation Guidelines
|
Section 4.6, Table 9 and Table 10
Section 6.2
Section 9.2, Table 545
|
March 2013
|
IG Version: 17.0 and Earlier
|
48
|
Changed: Character length to 120 characters in the contactName.FreeFormText element of the Participant Information section for PIP 3A4 V02.00.00.
|
Section 4.1 (Table 4, Element 3)
|
|
47
|
Added: The GlobalPurchaseOrderTypeCode for MSCP orders should be set to “Consigned order”. This is a change from sending “Services” in this field as in Legacy.
|
Section 6.2
|
|
46
|
Added:
Validations:
For partners submitting government orders without the intention that the order be TAA compliant, but have their line items on the request specified as TAA compliant, line item values will be ignored while fulfilling the order.
For partners submitting government orders with the intention that the order be TAA compliant:
If at line level none of the lines are specified as TAA compliant then the order is rejected
If at line level there is a mixture of TAA compliant lines and some lines that are non TAA compliant - a warning will be raised to that effect
If SKU at line level is specified as non-TAA compliant, however the SKU can only be fulfilled as TAA compliant and there is no Exception process to fulfill this SKU, then the partner can expect such SKUs as TAA compliant in response.
If SKU at line level is specified as non-TAA compliant, however the SKU can be TAA compliant and there is a Exception process to fulfill this SKU, then the partner can expect such SKUs as non-TAA compliant in the response.
Government TAB orders with preferential indicators(TAA-DX, TAA-DO, Dx, DO) will result in warnings and these values will be ignored.
Government TAB orders can be requested as TAA compliant.
|
Section 6.3.2
|
|
45
|
Added: If Cisco is unable to identify the covered product in relation to the service lines, orders are rejected.
|
Section 5.4
|
|
44
|
Added: In this case, if partners have not provided line level addresses, Cisco will make every effort to cascade this header level ShipTo address to the line level shipTo address.
Added:
Known Limitation
The actual order ship-to date information is not known at the time of PO Ack response. In light of not delaying the PO Ack response to wait until full processing is done, Cisco will send the PO Ack with no shipTo information at header level.
|
Section 4.9.2
|
|
43
|
Added: Before placing an order with the Kit Ref function, partners should create a ConfigSet using the Cisco Configuration Web Service and name it with a Partner product number, then:
-
Provide a kitReference Indicator flag on the product line item with valid value to indicate that a Kit Ref ID/Name is being used.
-
Provide the valid ConfigSet ID/Name as the Cisco part number (in the Proprietary Product Identifier field) to be ordered.
System does the following with these orders:
Retrieves the ConfigSet associated with the kitReference (s) along with the line item price and line item quantity
Adjusts the retrieved quantity at line level in reference to the specified kit Quantity
|
Section 7.3
|
|
42
|
To process orders with Promotion Codes - a Name value pair of PromotionCode = <> and is used; value is sent in tag 342 on the XML order.
|
Section 6.7
|
January 2013
|
41
|
Partners will send in ShipTo address free form text rather than the ShipTo address ID.
|
Section 4.9.2
|
January 2013
|
40
|
When B2B XML orders have any of the BLOCK SKUs, the order is rejected. For B2B EDI orders with the “BLOCK”, SKUs is a new task (“Prevent Booking” task where the order imported to ERP in “Entered” status) is raised explicitly for the Fulfillment Restriction for the CPE team. CPE team will work with the Distis to inform them of the Fulfillment restriction put in place for the particular SKU: The SKU would need to be removed from the Order before booking or the Disti can request that the CPE team cancel the order. Please see Appendix F for the list of BLOCK SKUs.
|
Section 5.3.3
|
January 2013
|
39
|
SWIFT and eDelivery should have the order contact email ID.
|
Section 7.9 (As of Version 18, the Section is 7.8)
|
January 2013
|
38
|
Partners can send orders with multiple KitRefs, one in each line item on the XML order. Each KitReference can be a KitRefName or a KitRefID. Also, net KitAmounts associated with the KitReferences will need to be sent for each of the KitReferences.
|
Section 7.3
|
January 2013
|
37
|
Product ID for DotX starts with "S".
|
Section 7.2
|
January 2013
|
36
|
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.
|
Section 6.10
|
January 2013
|
35
|
A US government Disti Stocking order is rejected if DPAS value is sent in as DX, DO, TAA-DX, or TAA-DO.
|
Section 6.3
|
January 2013
|
34
|
Removed:
Tag 342 - proprietaryInformation.FreeFormText - IG states: "ReferralReasonCode name value pair with reasons being - "Service Sale pending in 30 Days"
"Service Sale pending in 90 days"
"Service Sold by other Partner or Cisco"
"Service Referral"
"Spares or Stocking Order"" (However, no such logic has been implemented.)
|
Was Section 7.2 in Version 15 of the Implementation Guide
|
January 2013
|
33
|
Added: If you are a Distributor and are ordering the service for Resale, provide the Reseller Bill to Id and/or Address and/or Reseller Contact Email Address
|
Section 5.7.1
|
January 2013
|
32
|
Removed: In Response, zero price line items are included with Z prefixed with the major line number
|
Was Section 6.3.1 in Version 15 of the Implementation Guidelines
|
January 2013
|
31
|
Added to 4. 16: Line ID and Parent Line ID will be used in the configuration information tag as specified in section 5.5.
Removed from 4.16: "N.M format is the Cisco UI standard of representing PO list of hardware or software item(s) in a point decimal format. The relative configuration item appears as a sub digit. For example: Hardware ‘X’ is bold count 1.0 and its relative configuration items required will appear as sub counts 1.1, 1.2, 1.3 and so on in a set. However a new hardware or software item in the PO will not follow the same string. It will continue as 2.0, 2.1, 2.2 and so on. Only configuration items will appear as a sub count under each bold count.
As a general convention, Line number for major lines is N.0, where N is any integer. Line number for minor lines is N.M, where N and M are integers. Product lines with the same N value are grouped as one configuration.
There are line numbers in the format N.M.O for bundles that have 2 tiers of options:
• 1.0 - Bundle Chassis X
• 1.1 - Option Card Y
• 1.1.1 - Memory for Option Card Z
The Line number displayed in the CCW UI may not match the line numbers on the order.
|
Section 4.16
|
January 2013
|
30
|
Added: If partners do not provide shipping address at either the Product Line level or the Purchase Order level, Cisco will run defaulting rules as specified in the attached document to make every effort to process the order. In case we are unable to work throught any of the defaulting rules, Cisco will reject the order.
Added: Product Line file to Appendix C and referenced in the text.
|
Section 4.9.2 and Appendix C
|
January 2013
|
29
|
Added: Partner's GlobalLocationIdentifier (tag 29) /Cisco BID/ BillTo ID not on an order but partner has a default BID in its Cisco Profile. In this case default BID is fetched from partner's profile and order is processed however the order is rejected.
|
Section 4.7
|
January 2013
|
28
|
Added to 4.1 (tag 12): GlobalPartnerClassificationCode - Send a value of "Buyer" for this field. All other values will be ignored.
Removed: Send a value that describes what the customer’s business relationship is to Cisco. Potential values include “Distributor”, “Reseller” and “End User”. Please use the value from the “Identification” section in the “Trading Partner Profile” (set up in partner’s B2B Gateway server).
|
Section 4.1 (5.1.12 in prior version)
|
January 2013
|
27
|
Removed: Penny to zero dollar reverse calculation logic is already implemented
|
Preface (2.3.4 in prior version)
|
January 2013
|
26
|
Added: TAB orders having CTMP quote number/Promo Code but no Deal ID will result in an order rejection. Value for CTMP Quote number is to be derived from the Quote UI and is specified under TradeIn Quote Number.
|
Section 6.5 (7.6 in prior version)
|
January 2013
|
|
Prior Versions of Implementation Guide
|
|
|
25
|
Penny to Zero Dollar conversion is in place. Because SAP cannot handle zero priced items, in OCI the unit price for any items whose price is zero is set to a penny. The old ordering system then reverse calculates the price for any penny-valued items to zero.
|
|
September 2012
|
24
|
Enabling the ability to place orders with or without CiscoProductReference, along with passing a combination of Config Path, Selection Sequence, and Selection Flag on the order. If CiscoProductReference is passed on the order, it takes precedence over and ignores Config Path, selection sequence, and selection flag values.
|
|
September 2012
|
23
|
Enabling the ordering of Standalone Service, Freight Charges, and Landing Cost SKUs
|
|
September 2012
|
22
|
PAK delivery preference (PDP) values sent by partners are validated against transaction level values and warnings are raised when there is a mismatch. These validations will be applicable to perpetual licenses for ATO Configurations and Term and Content license subscription SKU (M:1 Option selection for standalone lines)
|
|
September 2012
|
21
|
Line level proprietaryInformation.FreeFormText field “PartnerTAAFlag with possible values “Y/N” should be used to indicate if the line item being ordered is TAA compliant.
Example:
[ProductLineItem.proprietaryInformation.FreeFormText]PartnerTAAFlag=Y
|
|
May 2012
|
20
|
A Bill-To Contact email address must be specified for TAA orders.
Example:
[PurchaseOrder. billTo.PartnerRoleDescription.ContactInformation.EmailAddress](Element #21)
|
|
May 2012
|
19
|
Service Only orders will no longer be identifiable by an order type of ‘Maint_Only’. Service Only orders will have an order type of ‘Standard’.
|
|
|
18
|
Partners can specify if they would like to receive subscriptions as Single or Multiple PAK via the LicenseKeyRequested attribute.
Example:
[ProductLineItem.proprietaryInformation.FreeFormText]LicenseKeysRequested=Single
|
|
|
17
|
As of March, 2012 release: Service Only orders must provide Serial Numbers as a reference to the covered product. The provision to provide Sales Order No. and Line No. as a covered product reference will be enabled in a later release.
|
|
|
16
|
Orders for AS-Fixed SKUs should include install site address, contact, and contact email information. See Section 6.10 AS-Fixed Ordering for details.
|
|
|
15
|
The “PathHashCode” will now be referred to as the “CiscoProductReference” code.
|
|
|
14
|
Removed references to SIS98 services.
|
|
|
13
|
References to the MOVE program have been replaced with Shipping Routing and Configuration Tool.
|
|
|
12
|
References to “Integrated Configuration Tool”(ICT), “Multi Line Configurator” (MLC), and “Dynamic Configuration Tool” have been replaced with references to the new systems and services used for like purposes: “Acquire Quote”, “Transfer Quote”, “Config Web Services”, and “CCW Config UI”.
|
|
|
11
|
Details surrounding specification of the delivery preference for SKUs are documented in Section 7.9 Swift and eDelivery products.
|
|
|
10
|
UCS products come with OEM software. If the OEM software was not ordered with the original UCS purchase, partners may order it separately as a spare. When this spare is ordered, partners are required to add a $0 minor line indicating ‘Acceptance of the Terms and Conditions’ under the OEM Major line, to indicate that they are aware of the proper use of the OEM software. If an OEM product is ordered as part of a configuration, this $0 minor line would have been added by the system when creating the configuration and therefore does not need to be added separately.
|
|
|
9
|
Try and Buy (TAB) orders with a CTMP number or a Promo Code but no Deal ID result in a rejection of the order.
|
|
|
8
|
The default trial period for Try and Buy orders without a Deal ID will be 90 days. Telepresence products will have a trial period of 120 days. The trial period for orders with a Deal ID are obtained from the deal.
|
|
|
7
|
Contract Duration values must be provided in months.
System defaults the duration to 12 months if not provided on the order.
Standard Duration values are 12, 24, and 36.
proprietaryInformation.FreeFormText (Element #304)
Example:
[ProductLineItem.proprietaryInformation.FreeFormText]ContractDuration=12
|
|
|
6
|
When ordering configurations with both products and services, partners should either include orders for all applicable services for the product configuration on the same order OR not order any of the applicable services. See Section 5.9 All or Nothing Rule for additional details.
|
|
|
5
|
A two digit country code should be provided for zero pricing. Partners may no longer provide a zero price region name.
The two digit code will be provided, as before, via the [PurchaseOrder.proprietaryInformation.FreeFormText] (Element #342)
Example:
[ proprietaryInformation.FreeFormText]ZeroPriceCountry=JP
|
|
|
4
|
Taxability and Intended Use (Order Reason) related changes.
A GlobalPurchaseOrderTypeCode of “Standard” used to convey both “Internal Use” & “Resale,” but going forward Standard will only be for “Resale” and “Site” will be used for “Internal Use”.
Additional details are in Section 4.6, Purchase Order type.
|
|
|
3
|
Discontinue use of the ServiceFor (Element #304) tag. Partners should send the Line Id and Parent Line Id via the ConfigurationInformation tag mentioned in No. 2 above.
Previous use was:
[ProductLineItem.proprietaryInformation.FreeFormText]ServiceFor=1.0
|
|
|
2
|
Line Id and Parent Line Id must be provided via the ConfigurationInformation pair within proprietaryInformation.FreeFormText (Element #304)
Example:
[ProductLineItem.proprietaryInformation.FreeFormText]ConfigurationInformation=3716361399,0;2324567]
|
|
|
1
|
To send an order to the CCW platform, partners need to send “OrderPlatform=CCW” in “Tag 342 proprietaryInformation.FreeFormText at the PurchaseOrder level”. If “OrderPlatform=CCW” is not specified in Tag 342, then the order will be processed in the old environment.
[PurchaseOrder.proprietaryInformation.FreeFormText]OrderPlatform=CCW
|
|
|
