JR55719: Sterling Organization Code does not use store identifier by default

APAR status

• Closed as program error.

Error description

• When integrating WebSphere Commerce with Sterling Configurator
  on WebSphere Commerce Feature Pack 7 or higher, leaving the
  Sterling Organization Code blank in the Sterling transport
  settings causes the Configure iFrame at the storefront to fail
  since the organizationCode POST parameter sent to Configurator
  is null.
  
  The following error might be seen in the Sterling SystemOut.log:
  
  [4/1/16 9:24:01:904 CDT] 000000ab SystemOut     O 2016-04-01
  09:24:01,901:ERROR  :WebContainer : 0: <?xml version="1.0"
  encoding="UTF-8"?>
  <Errors>
  ...
  ...
          <Attribute Name="ErrorCode" Value="YFS10001"/>
          <Attribute Name="ErrorDescription" Value="YFS:No Record
  Found"/>
          <Attribute Name="OrganizationKey" Value=""/>
          <Attribute Name="OrganizationCode" Value="null"/>
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce Version 7 users on Feature Pack 7 or higher
  integrating with Sterling Configurator.
  
  PROBLEM ABSTRACT:
  Sterling Organization Code does not use store identifier by
  default
  
  BUSINESS IMPACT:
  Administrators must set a Sterling Organization Code for every
  store they want integrated with Sterling Configurator.
  
  RECOMMENDATION:
  

Problem conclusion

• The underlying code has been updated to use the Store identifier
   as the organizationCode sent to Sterling if the Sterling
  Organization Code is left blank in the Sterling transport
  settings.
  

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