Bug 22990
Summary: | Customer Number lookup is incorrect | ||
---|---|---|---|
Product: | Red Hat Web Site | Reporter: | Martin C. Messer <mmesser> |
Component: | Store | Assignee: | Tom Lancaster <tlancast> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Eddie Chen <echen> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | current | CC: | nobody+jcohen, traffic |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://www.redhat.com/apps/internalstore | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-20 14:49:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin C. Messer
2000-12-29 19:39:17 UTC
An explanation of ORACLE_CUSTOMER_NUMBER and ORACLE_CUSTOMER_ID. Oracle will generally have a "public" id and a "private" id for any object within the system. In this case, ORACLE_CUSTOMER_NUMBER corresponds to the public customer number that we can use to talk about a customer. It's the number we give the customer freely, since the search functions in the Oracle Applications use it as a key. ORACLE_CUSTOMER_ID corresponds to the private Oracle id for a customer. We don't give this number to customers since it doesn't really mean anything except to the underlying relational structure. We can't search on it in the Applications. It's for "Oracle-only Use". Does that help? The point of the story is that anytime we're showing customer numbers to the outside, or making any sort of relation between a web customer and a customer in Oracle, we talk about ORACLE_CUSTOMER_NUMBER. In terms of the bug I've reported, something inside the internal store code is matching against ORACLE_CUSTOMER_ID instead of ORACLE_CUSTOMER_NUMBER. Every customer id is unique within the set, and every customer number is unique within the set, but the two sets are _NOT_ unique. There's the problem. One customer's number can be another customer's id, and vice versa. Sorry, you also asked about how these columns get populated in the web tables: ORACLE_CUSTOMER_NUMBER and ORACLE_CUSTOMER_ID (and ORACLE_CONTACT_ID as well) are currently assigned in Oracle ERP/CRM at time of customer import from the web. Then some fancy scripts push these ids back to the web and updates the web_user table with the results. Otherwise the ids are null (we've changed NULL to be -1 for the purposes of these three columns). |