1 person found this helpful
The behavior witnessed in the Service Request form (CSXSRISR.fmb) seems to be the current functionality.
An Enhancement Request has been raised in R12:
Bug 9964954 - ABLE TO CREATE AN SR IN FIELD SERVICE EVEN THOUGH THE CUSTOMER DOESNT BELONG TO
Creating service request form, should provide a list of customers belonging to that Organization.
Currently, a person logged in US ORG can create a service request for a Canadian Customer, for instance.
If the Organization is 'US', the Customer drop down must list only US customers, but it lists all.
That ER is linked to and will be reviewed along with another ER:
Bug 5470324 - NEED THE ABILITY TO RESTRICT THE VIEWABLE ADDRESSES BASED ON THE OU OF THE SR
In reference to the latter, there are other considerations and options for the Addresses.
For instance, Account Site is associated with an OU. However, Incident Address is populated from Party site.
The Party Site is not associated with an OU. For this we need an enhancement in Trading Community Architecture (TCA).
Additionally, there is an option in R12 to filter the Ship To and Bill To Address LOVs by Party Sites or Account Sites.
And for the behavior in the Contact Center, we may need more details and more time to review your current settings and exact functionality.
If you have further questions, feel free to raise a Service Request and we will review.
Thanks for the detailed response on the Query, is there any workaround in the Service Request Form to achieve the functionality like form personalization?
I would say it is possible, but I don't have the details or clear instructions for that.
I'm checking internally, and I'll let you know. But if this is very critical, you may raise a SR so we can validate the options with Development and Product Management.
HZ_PARTIES table is a generic table and does not contain any org specific data, I am not sure how you want the customer data to be striped based on the org in the SR Header, However in the SR Header Level, Customer LOV can be modified using Form Personalization so that restriction can be enabled:
In this case I joined with HZ_CUST_ACCT_SITES_ALL table, since it contains the Org Id, please review the following sample code:
p.address1 || decode(p.address2,null,null,';'||p.address2) || decode(p.address3,null,null,';'||p.address3) || decode(p.address4,null,null,';'||p.address4) address,p.address1,p.address2,p.address3,p.address4,
from hz_parties p,
where p.party_type = 'ORGANIZATION' and
p.status = 'A' and
p.party_id = a.party_id and
a.status = 'A'
FROM hz_cust_acct_sites_all hcasa
WHERE hcasa.cust_account_id = a.cust_account_id
AND hcasa.org_id = fnd_profile.value('ORG_ID')
order by 1
Thanks & Regards,
Thanks for the query.