Here are the new data objects to use instead of the existing data objects in the managed package.
- Map your financial data to the Accounting Subledger data model
- Use the new AccountingModelConfig object instead of the abacus__Accounting_Mapping_Set__mdt object.
- Configure settings for the Accounting Subledger job
- Use the new AccountingSettings object instead of the abacus__Ledger_Entry_Settings__c object.
- View the generated financial transactions records
- Use these new and existing fields on the TransactionJournal object instead of the abacus__Ledger_Entry__c object.
New fields:
- AccountingModelConfigName
- Comment
- CreditAmount
- DebitAmount
- DueDate
- FundAccountRecordIdValue
- FundAccountValue
- GeneralLedgerCode
- IsAccrualJournalEntry
- IsAdjustmentJournalEntry
- IsHistoricalJournalEntry
- IsRelatedJournalEntry
- IsWriteOffJournalEntry
- PaymentDate
- PrimaryRecordIdValue
- SecondaryRecordIdValue
Existing fields:
- BookingDate
- JournalReason
- JournalType
- PaymentMethod
- Monitor Accounting Subledger jobs
- Use the BatchJob and BatchJobPart objects instead of the AsyncApexJob object.
- Review failed Accounting Subledger jobs
- Use the BatchJobPartFailedRecord object instead of the abacus__Subledger_Error__c object.