ATS-ACC-BKS-005 Maintain a business unit’s chart: Capability Test Specification
Markdown Design / Accounting / Books, Business Units and Chart of Accounts / Accounts and Reporting Destinations / Capability Test Specification Maintain a business unit’s chart: Capability Test Specification Coverage Normalize codes within each unit. Keep account identity stable. Present default and invalid account types. Retain referenced accounts. Protect default destinations. The structured coverage map distinguishes specified examples from remaining findings. Proposed examples require executable proof before qualification.
Released default frees its chart destination. A receiving account prevents chart removal. A tax destination prevents chart removal. Related-capability and workflow references identify the seams each scenario exercises. The lifecycle coverage record retains transitions that still need individual proof.
Binding Review The pinned service and browser assertions support the registered bindings. Original test references remain beside each scenario so partial evidence and unresolved conformance remain reviewable.
Coverage Rule covered Transition gap: FND-ACC-BKS-066 Validation covered Permission covered Edge gap: FND-ACC-BKS-066 Failure covered Boundary covered Concurrency covered Invariant gap: FND-ACC-BKS-081 Interaction covered Test Scenarios 11 scenarios proving CAP-ACC-BKS-005
01 Normalize codes within each unit validation api test
Proves BR-CAP-ACC-BKS-005-01INV-DOM-ACC-BKS-002-01 Preconditions Two separate units exist. Steps Create a lower-case code, repeat its upper-case form locally, then use it in the other unit. Expected The code is stored upper-case with a derived identity, the local repeat is refused and the other-unit code succeeds. Data The setup needs no extra fixture records. Bound to Source services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js #stores the code trimmed and upper-cased, under the id from the lower-cased code 02 Keep account identity stable invariant api negative proposed
Proves BR-CAP-ACC-BKS-005-02Preconditions A saved USD account has a unit and code. Steps Change code, unit and currency in separate replacements. Expected Each receives a field-specific conflict. Data The setup needs no extra fixture records. Source FND-ACC-BKS-081 03 Present default and invalid account types rule api test
Proves BR-CAP-ACC-BKS-005-03Preconditions A unit is ready for account setup. Steps Create a nameless account with no type and another with an unknown type. Expected The first defaults to income and displays its code; the other is refused. Data The setup needs no extra fixture records. Bound to Source services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js #defaults the account type to income 06 Exercise the grants for maintain a business unit’s chart permission api negative proposed
Proves BR-CAP-ACC-BKS-016-01Preconditions An application-authorized reader and administrator share the run-owned setup. A third principal lacks the relevant resource grant. Steps Read the relevant configuration as the reader, attempt each supported mutation, then repeat with the matching administrator grants. Repeat the reads without their resource grants. Expected The permission outcomes match the cited authorization rule, and refused mutations leave every configured value unchanged. Data Run-owned records for the stated setup; retain the initial values for comparison. Source services-accounting:modules/books/tests/e2e/configuration-security.e2e.spec.js #is refused the create 403 permission_missing 07 Chart page-size endpoints boundary api negative proposed
Proves BR-CAP-ACC-BKS-005-06Preconditions An isolated workspace has records needed for both eligible and ineligible examples. Steps Read a populated chart with page sizes one and five hundred, then request five hundred and one. Expected Eligible page sizes return bounded pages; the excessive request is refused. Data Run-owned records for the stated setup; retain the initial values for comparison. Source services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js #answers every account by business unit, then code 08 Refuse the second replacement of a shared read version concurrency api negative proposed
Proves BR-CAP-ACC-BKS-016-05Preconditions Two administrators read the same version of the relevant mutable record. Each prepares a different otherwise valid replacement. Steps Release both replacement requests from a barrier. Read the record again and retry the losing payload at its original version. Expected One replacement commits, the other is stale, and repeating the stale request preserves the winning values. Data Run-owned records for the stated setup; retain the initial values for comparison. Source services-accounting:modules/books/tests/e2e/payment-terms.e2e.spec.js #answers 400 naming is_active to a replacement that leaves it out 09 Released default frees its chart destination interaction browser test
Proves BR-CAP-ACC-BKS-005-05BR-CAP-ACC-BKS-006-04Preconditions Run-owned records satisfy the preconditions of the referenced capability proofs. Steps Assign an account as a default, try deactivation, clear the assignment twice and deactivate the account. Expected Only the released destination can become inactive. Data Run-owned records for the stated setup; retain the initial values for comparison. Bound to Source services-accounting:modules/books/tests/integration/services/persistence/gl-accounts.integration.spec.js #refuses deactivating the unit’s Accounts Receivable default, naming the purpose,services-accounting:modules/books/tests/integration/services/persistence/default-gl-accounts.integration.spec.js#answers the purpose with no account when clearing a purpose the unit has no default for 10 A receiving account prevents chart removal interaction browser test
Proves BR-CAP-ACC-BKS-005-04BR-CAP-ACC-BKS-007-01Preconditions Run-owned records satisfy the preconditions of the referenced capability proofs. Steps Create a receiving destination on a local chart account, try removing the chart account, remove the destination and retry. Expected The dependency blocks the first removal and its release permits the later removal. Data Run-owned records for the stated setup; retain the initial values for comparison. Bound to Source services-accounting:modules/books/tests/integration/services/persistence/gl-accounts.integration.spec.js #translates the refusal of each restrict foreign key to a GL account into a 409 naming it,services-accounting:modules/books/tests/e2e/bank-accounts.e2e.spec.js#answers 400 to another unit’s GL account, naming both units 11 A tax destination prevents chart removal interaction browser test
Proves BR-CAP-ACC-BKS-005-04BR-CAP-ACC-BKS-013-02Preconditions Run-owned records satisfy the preconditions of the referenced capability proofs. Steps Map a tax rate to the unit account, try deleting that account, remove the mapping and retry. Expected The mapped destination remains protected until the tax reference is released. Data Run-owned records for the stated setup; retain the initial values for comparison. Bound to Source services-accounting:modules/books/tests/integration/services/persistence/gl-accounts.integration.spec.js #translates the refusal of each restrict foreign key to a GL account into a 409 naming it,react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0022.spec.ts#ACT-ACC-0022 ← Previous Capability Test Specification ATS-ACC-BKS-004 · Maintain dated exchange rates for a unit: Capability Test Specification Next Capability Test Specification → ATS-ACC-BKS-006 · Assign accounts to standard posting purposes: Capability Test Specification