HZ_CUST_ACCOUNT_ROLE_V2PUB Does Not Validate Whether Valid Party_ID Is Passed
(Doc ID 2122127.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Trading Community - Version 12.1.2 and later
Information in this document applies to any platform.
You can pass any existing party_id to Hz_Cust_Account_Role_V2Pub. There is no validation is done.
Oracle® Trading Community Architecture
Technical Implementation Guide
Part No. B25895-01
Create Customer Account Role API
This routine is used to create an Account Role. The API creates a record in the HZ_CUST_ACCOUNT_ROLES table.
To create a customer account role, you must have already created a customer account and an org contact for the party owning the customer account.
If an orig_system_reference is passed in, the API creates a record in the HZ_ORIG_SYS_REFERENCES table to store the mapping between the source system reference and the TCA primary key.
If orig_system_reference is not passed in, the default is UNKNOWN.
Parameter Description and Validation
The following table lists information about the parameters in the Create Customer
party_id IN NUMBER Yes Validation:
Foreign key to hz_parties
Per TCA manual, there should be a validation on party_id and make sure the pass in party_id is for relationship, not organization or person
STEPS TO REPRODUCE
Customer named JackieCustRole Org
TCA API Hz_Cust_Account_Role_V2Pub validates the input party_id is the relationship party_id in hz_relationships table,
and the subject_id / object_id for that relationship is the party_id for the input cust_account_id
RELEVANT FILE VERSIONS
/*$Header: ARH2CRSS.pls 120.9 2006/08/17 10:17:41 idali ship $ */
/*$Header: ARH2CRSB.pls 120.13.12010000.4 2014/08/06 09:32:17 spokala ship $*/
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Bug Summary|
|2. Fixed Files|
|3. Recommended Patches|
|4. Solution Steps|