updatePartyPendingCDCRequest
- Description
- This transaction is used to update the status of each Critical Data Change currently pending. Each Critical Data Change transaction request may contain multiple Critical Data Changes. Each Critical Data Change has a unique identifier primary key (IdPk) and a Pending status assigned by InfoSphere® MDM. If the change accepted, the party record's update is effected upon changing the status of the Critical Data Change from Pending to Accepted. If the change is rejected, the pending Critical Data Change is inactivated when its status is changed to Rejected.
- Web Services
- Operation name: updatePartyPendingCDCRequest
- Example
- Accept the change of Jane's last name to “Goodman” after
proper verification, and update the party record accordingly.
Reject the change of Jack Bryon's date of birth due to lack of documentary proof.
- Usage information
- This transaction is available only to users with appropriate security rights. Multiple critical pieces of data belonging to the same party can be updated in the same transaction, each with different statuses.
- Preconditions
- Party must exist.
- Associated critical data changes must exist.
- Mandatory input
- PartyId
- CDCId
- CDCStatus
- Reject reason, if the updated Critical Data Change status is rejected
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- Each Critical Data Change represents a change to at least one
element in a business object of a party record that is defined as
critical data, and may contain noncritical data belonging to the same
business object. Each Critical Data Change is treated as one unit
regardless of the number of data elements contained therein.
When a Critical Data Change is created, a Pending status is assigned by InfoSphere MDM. The same status applies to each and every critical and noncritical data element within the Critical Data Change. If the status is changed from Pending to Rejected, a reason must be provided. The Critical Data Change is thus inactivated, and no change to the party record is made.
Important: The PendingCDCIndicator on the party record remains set to Y (yes) if there are other Critical Data Changes remaining pending on the given party record.If the Critical Data Change is accepted, all data contained in the change request is committed to the party record immediately upon the change of status. The updated party record can be retrieved through a getParty transaction.
When all pending Critical Data Changes associated with a party are resolved (no longer bearing a Pending status), the Pending Critical Data Change Indicator on the party record is turned off. This returns the party to the normal stream of operations in the system.
- Request message
- <TCRMTxType> updatePartyPendingCDCRequest
<TCRMTxObject> TCRMMultiplePartyCDCBObj
<TCRMObject> TCRMMultiplePartyCDCBObj
- Response objects
- TCRMMultiplePartyCDCBObj with associated TCRMPartyCDCBObj
- Special note
- Not applicable