updatePartyMacroRole
- Description
- This transaction updates the
recorded details for PartyMacroRole. Optionally, it can be used as
a coarse-grained transaction, and allows the user to add or update
a PartyMacroRoleAssociation. These are the entities that can be associated
with the PartyMacroRole:
- PartyAddress
- PartyContactMethod
- PartyIdentification
- OrganizationName
- PersonName
- PartyAdminSysKey
- PartyAlert
- PartyBankAccount
- PartyChargeCard
- PartyIncomeSource
- PartyPayrollDeduction
- PartyPrivacyPreference
- PartyRelationship
- PartyValue
- PartyLOBRelationship
- ContractPartyRole
- Web Services
- Operation name: updatePartyMacroRole
- Example
- Update PartyMacroRole to end the role of Client for John Smith. With the same transaction, end all existing PartyMacroRoleAssociations.
- Usage information
- To make a Party Macro Role inactive, use this transaction to set
an EndDate that is less then or equal to the current date. The EndDate
must be greater than the StartDate. The same considerations apply
to PartyMacroRoleAssociation start dates and end dates.
When using this transaction as a coarse-grained transaction, the following simple transactions may also apply:
- Preconditions
- PartyMacroRole must exist.
- Mandatory input
- PartyMacroRoleId
- LastUpdateDate
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- When the EndDate exists, this transaction can be used to supply
the EndReasonTypeCode and EndReasonTypeValue.
The EndReasonTypeCode and EndReasonTypeValue are user-defined attributes.
The RoleCategoryTypeCode and RoleCategoryTypeValue are included in the response of this transaction.
- Request message
- <TCRMTxType> updatePartyMacroRole
<TCRMTxObject> TCRMPartyMacroRoleBObj
<TCRMObject> TCRMPartyMacroRoleBObj
with optional business objects:
- one or more TCRMPartyMacroRoleAssociationBObj
- Response objects
- TCRMPartyMacroRoleBObj
with optional business objects:
- Special note
- Not applicable