Service - CommerceAccounting Customer Payment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
= Object Schemas = | = Object Schemas = | ||
; Additional Information: [[Per Service Schemas]] | ; Additional Information: [[Per Service Schemas]] | ||
== comAccCustomerPayment == | == comAccCustomerPayment == | ||
Latest revision as of 09:58, 8 August 2026
Overview
Handle payments by customers.
Repository
...
Object Schemas
- Additional Information
- Per Service Schemas
comAccCustomerPayment
{
objectType: "comAccCustomerPayment",
generatedBy: "systemGenerated",
canDelete: false,
addOnDataStructure: [],
storageResources: {
"dynamo": {
"storageType": "dynamoDB",
"tableName": "comAccCustomerPayment",
}
},
fieldNames: {
// businessId,
// organizationId,
// customerPaymentId,
// record lock eg: prefix: "updateCustomerPayment"
// updateCustomerPayment_status: {requiredOnCreate: true}, // open|lock,
// updateCustomerPayment_uniqueRequestId: {requiredOnCreate: true},
// updateCustomerPayment_timestamp: {requiredOnCreate: true},
journalId: {
type: "string",
optionalOnCreate: true,
canUpdate: true,
storageResourceTags: ["dynamo"],
},
},
identifiers: [
{
type: "partitionKey",
fieldNames: ["businessId", "organizationId"],
name: "comAccLinkId",
},
{
type: "sortKey",
fieldName: "customerPaymentId"
},
]
}
- maintains a link between customerPaymentId and journalIds, so can adjust if changes made to payment
Relationships
...
flowSchemas
customerPaymentCreated
- when creating a customer payment add journal entries
customerPaymentChange
- make adjustment to journal entries
- need to check for locked records