RMS Supplier Web Service Creates Wrong Entry for Addresses in ADDR Table (Doc ID 2214685.1)

Last updated on JULY 31, 2017

Applies to:

Oracle Retail Merchandising System - Version 15.0.1 and later
Information in this document applies to any platform.

Symptoms

The RMS Supplier web service creates an incorrect entry for Addresses in ADDR table.


Steps to Reproduce:

Scenario 1:
  1. Prepare the XML message with_address_type_01, 02, 03, 04, 05, 06
  2. Send the message to RMS web-service :/SupplierBean/SupplierService?WSDL through SOAPUI

  Expected result: Supplier parent and Supplier Site should both have all 6 types of addresses.
  Actual result: Supplier Parent has address type 01 only, and Supplier Site has all 6 Address types.

Scenario 2:
  1. Prepare the XML message without_address_type_01, has only types 02, 03, 04, 05, 06
  2. Send the message to RMS web-service :/SupplierBean/SupplierService?WSDL through SOAPUI

  Expected result: Supplier parent and Supplier Site should both have all 5 types of addresses, 02 through 06
  Actual result:  Supplier parent and Supplier Site both have all 6 types of addresses, 01 through 06
    Address type 01 is generated by RMS using the input address type 04 for both Supplier and Supplier Site
    Supplier (Parent) has all remaining address types (02 to 06) defaulted based on the input

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms