ACBRDNTRAN – The Burden Transactions file is updated by the Activity Posting (AC190) program.
- System
- Activity Management (AC)
- Prefix
BTR- Primary key
ATN-OBJ-ID- Fields
- 11
- Updated by
- 7 programs
- Referenced by
- 35 programs
ACBRDNTRAN is the The Burden Transactions file is updated by the Activity Posting (AC190) program. table in Lawson Activity Management (prefix BTR). It is indexed by ATN-OBJ-ID (BTRSET1); alternate indexes: BTRSET2 and BTRSET3. It is updated by AC145, AC190, AC197, AC300, AC310, AC311 and AC45.1 and referenced by AC198, AC42.1, AP125, AP126, AP178, AP20.1, AP20.2, AP20.3 and 27 more. The table has 11 fields, 3 indexes and 0 documented relations.
About ACBRDNTRAN
The Burden Transactions file is updated by the Activity Posting (AC190) program. A burden transaction record is created for each burden record created in ACTRANS. The source code for the burden transactions is "BD". The ACBRDNTRAN.ATN-OBJ-ID field is the Object ID of the burden ACTRANS record. The ACBRDNTRAN.ATN-ORG-OBJID field is the Object ID of the ACTRANS record that spawned the burden transaction.
Fields (11)
Column = COBOL field name without the BTR- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored. PK = primary key (present in every index); SETn = leading/alternate key of that index.
| Field / column | Type | Description & values | Updated by |
|---|---|---|---|
#BTR-ATN-OBJ-ID PKATN_OBJ_ID | Numeric 12 | This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems. | AC190, AC197 |
#BTR-BURDEN-CD SET2BURDEN_CD | Alpha 5 | — | AC190, AC197 |
#BTR-STEP SET3STEP | Numeric 3 | This field determines when an allocation detail line will get processed. All lower steps are processed before processing higher steps. | AC190, AC197 |
#BTR-VARIATIONVARIATION | Alpha 1 | — | AC190, AC197 |
#BTR-BOB-BURDEN-CDBOB_BURDEN_CD | Alpha 5 | — | AC190, AC197 |
#BTR-BOB-STEPBOB_STEP | Numeric 3 | — | AC190, AC197 |
#BTR-POOL-NBRPOOL_NBR | Numeric 3 | — | AC190, AC197 |
#BTR-ATN-ORG-OBJID SET2 SET3ATN_ORG_OBJID | Numeric 12 | — | AC190, AC197 |
#BTR-PT-ACCT-CATPT_ACCT_CAT | Alpha 5 | Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thru | AC190, AC197 |
#BTR-ACTIVITY SET3ACTIVITY | Alpha 15 | Activities are the processes or procedures that produce work. Cost objects (products, services, customers, and so on) are the reasons for performing the activity. | AC190, AC197 |
#BTR-EXEMPT-FLEXEMPT_FL | Alpha 1 | Exempt Flag.
| AC190, AC197 |
Indexes (3)
Keys are listed in index order; ↓ marks a descending key. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.
| Index | Keys | Flags | Condition | Used in |
|---|---|---|---|---|
BTRSET1 |
| Primary | AC197, AC310, AC311 | |
BTRSET2 |
| KeyChange | AC145, AC197, AC300, AC42.1, AC45.1, AP125, AP126, AP178 +22 more (list truncated in source) | |
BTRSET3 |
| KeyChange | AC198 |
Programs
Updated by (7)
- AC145 Mass Transaction Backout
- AC190 Activity Posting
- AC197 Burden Recalculation Based on Total Cost
- AC300 Activity Group Purge
- AC310 Transaction Consolidation
- AC311 Purge and Archive
- AC45.1 Transaction Edit
Referenced by (35)
- AC198 Burden Rate Recalculation
- AC42.1 Subcontractor Time and Material Entry
- AP125 Batch Release
- AP126 Mass Invoice Release
- AP178 Paid Invoice Activity Update
- AP20.1 Basic Invoice
- AP20.2 Taxed Invoice
- AP20.3 Detail Invoice
- AP20.4 Invoice Line Detail
- AP20.5 Multiple Invoice
- AP20.7 Distributions
- AP21.1 View Distributions
- AP23.1 Transit Invoice Entry
- AP25.1 Batch Control
- AP25.2 Batch Review
- AP26.1 Invoice Release
- AP27.1 Single Invoice Release
- AP30.2 Distribution Adjustments
- AP30.4 Invoice Cancel
- AP520 Invoice Interface
- API1.1 Add Invoice
- API2.1 Add Invoice
- EX542 Expense Creation
- MA41.1 Add-On Cost Detail - Purchase Order
- MA41.2 Add On Cost Lookup
- MA41.4 Miscellaneous Add-On Cost
- MA41.7 AOC Approval Entry
- MA42.2 Memo Line AOC Detail
- MA43.2 Purchase Order Lookup
- MA44.1 Invoice Line Detail - Purchase Order
- MA44.2 Invoice Line Detail- Service
- MA61.1 Match Invoice Approval
- MA70.1 Invoice Unmatch
- MA75.1 PO Invoice Cancel
- MAI1.1 Invoke for MAMATCH Object