JR45220: CMVC 225839 - ENSURE XML GENERATED BY ORDER SERVICES IS MAPPED CORRECTLY

7.0.0-WS-WCServer-FP009
WebSphere Commerce Version 7.0.0.7 Fix Pack
WebSphere Commerce Version 7.0.0.8 Fix Pack
WebSphere Commerce Version 7.0.0.9 Fix Pack

APAR status

• Closed as program error.

Error description

• PHONE1TYPE or PHONE2TYPE from ADDRESS table are not mapped to
  the restricted values(Home1, Home2, etc.) defined in
  CommonTypes.xsd.
  When XML is generated by Order services e.g. ProcessOrder, the
  corresponding data type in the XSD expects the phone type value
  to be from a pre-defined set of values which are Home1, Home2,
  Work1, Work2, etc.
  
  The XML is generated like the following:
  <_wcf:Telephone1 publish="true" type="H2">
            <_wcf:Value>(651) 239-1874</_wcf:Value>
  </_wcf:Telephone1>
  
  This fails if we try to validate the XML as no mapping exists
  between H1, H2, etc. and Home1, Home2, etc.
  

Local fix

• Updating the CommonTypes.xsd to expect the values H1 instead of
  Home1 etc. will alleviate the problem.
  Find the following section in CommonTypes.xsd and update the
  values:
  
                 <attribute name="type"
  type="_wcf:TelephoneLocationType" use="optional">
     <annotation>
      <documentation>The type of phone number:
       Home1:  Primary home phone number.
       Home2:   Secondary home phone number.
       Work1:     Primary work phone number.
       Work2:    Secondary work phone number.
       Mobile1: Primary mobile phone number.
       Mobile2: Secondary mobile phone number.
      </documentation>
     </annotation>
    </attribute>
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce v7 users who validate are validating the
  order generated XML
  
  PROBLEM ABSTRACT:
  XML generated by order services is being mapped incorrectly
  
  BUSINESS IMPACT:
  Prevents orders being processed if the XML needs to be validated
  in order to proceed with order flow
  
  RECOMMENDATION:
  

Problem conclusion

• Mapped the phone type value in ADDRESS database table to the
  corresponding defined restricted value in XSD file When
  composing the generated XML for processing order service. For
  example, map 'H1' to 'Home1'.
  
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP