Scribd
Upload
260 views2 pages

How To Update Service Request

This document provides details on how to update service request contact points using the CS_SERVICEREQUEST_PUB.UPDATE_SERVICEREQUEST API. The API accepts a record type parameter called p_contacts which includes fields like SR_CONTACT_POINT_ID and PARTY_ID to identify the contact point to update. There are validations to ensure contact points are valid employees, persons, or relationships depending on the customer type.

Uploaded by

ameetdey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
260 views2 pages

How To Update Service Request

This document provides details on how to update service request contact points using the CS_SERVICEREQUEST_PUB.UPDATE_SERVICEREQUEST API. The API accepts a record type parameter called p_contacts which includes fields like SR_CONTACT_POINT_ID and PARTY_ID to identify the contact point to update. There are validations to ensure contact points are valid employees, persons, or relationships depending on the customer type.

Uploaded by

ameetdey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

Service: Example of How to Use the CS_SERVICEREQUEST_PUB.UPDATE_SERVICEREQUEST API


To Update a Service Request Contact Point (Doc ID 215093.1)

In this Document

Abstract
History
Details
Summary

APPLIES TO:

Oracle Teleservice - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]


Information in this document applies to any platform.

ABSTRACT

To offer details of the CS_SERVICEREQUEST_PUB.UPDATE_SERVICEREQUEST Application Program Interface (API).

This article details how to add/change contacts to a Service Request (SR) via the API method.

HISTORY

16-Oct-2002: Created

to new format
15-May-2009: Migrated

DETAILS

To update the contact points associated with an SR, the SR API accepts the following parameter:

p_contacts -> which is a Record Type with the following structure:

TYPE contacts_rec IS RECORD ( 

   SR_CONTACT_POINT_ID   NUMBER        := FND_API.G_MISS_NUM, 


   PARTY_ID              NUMBER        := FND_API.G_MISS_NUM, 

   CONTACT_POINT_ID      NUMBER        := FND_API.G_MISS_NUM, 

   CONTACT_POINT_TYPE    VARCHAR2(30)  := FND_API.G_MISS_CHAR, 

   PRIMARY_FLAG          VARCHAR2(1)   := FND_API.G_MISS_CHAR, 

   CONTACT_TYPE          VARCHAR2(30)  := FND_API.G_MISS_CHAR 

);

To "update" a contact point, you **must** specify a value for 'sr_contact_point_id'; i.e. the primary key from
cs_hz_sr_contact_points along with the modified values.  There are validations that kick in for validating these updates.  The
procedure that does the validation is shown in parenthesis below.

If the customer is of type 'ORGANIZATION' (object type), the contact **should** be:

1. Valid EMPLOYEE in PER_EMPLOYEES_X (cs_servicerequest_util.validate_employee)


2. Valid PARTY_RELATIONSHIP in hz_relationships (cs_servicerequest_util.validate_org_relationship)

If the customer is of type 'PERSON' (object type), the contact **should** be:

1. Valid PERSON in hz_relationship (cs_servicerequest_util.validate_customer_contact (up to patchset G))


2. Valid PARTY_RELATIONSHIP in hz_relationship (cs_servicerequest_util.validate_person_relationship)
3. Valid EMPLOYEE in per_employees_x (cs_servicerequest_util.validate_employee)

Also, there can be only one primary contact for an SR.

SUMMARY

Didn't find what you are looking for?

You might also like