Manage Invoice Options Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Invoice Options under Payables.
Supported Operations
This task supports creating a new Invoice Options setup row and updating an exact existing setup row. It does not support delete or end-date operations. Only the operation-specific fields documented in Input Validation and Design Enforcement are permitted; all other fields remain blocked.
Task Behavior
Use the exact AP_SYSTEM_PARAMETER package and CSV header contract. The
supported create and update fields are defined by the local resources and
adapter.
Keep the exact AP_SYSTEM_PARAMETER package root
(/SystemOptionVO/SystemOptionVORow) and the current template's header order
and field count. Do not create a replacement schema. For a create, find the
business unit in finBusinessUnitsLOV, use its PrimaryLedgerId to find the
ledger in ledgersLOV, and write that ledger name to SOBName.
For EnterpriseId, use (in order): the value explicitly requested for that
row, the current-run default, or the fresh FSM export when it has exactly one
nonblank value. Record this choice as enterpriseIdResolution. An update
keeps the value from its uniquely matched export row. Fusion then resolves
BuName and EnterpriseId to OrgId.
The three payment-term fields are separate defaults. In the CSV, the Payment
Request Payment Terms control is EmployeeTermName. Check each supplied name
with the read-only payablesPaymentTerms service and keep the result as
evidence only; do not choose an ID from multiple results. On import, Fusion
resolves TermName, PrepaymentTermName, and EmployeeTermName to their
corresponding IDs. A missing value is reported as an import dependency.
Before normalization, run scripts/resolve_lookup_prerequisites.py for any
populated page lookup fields. The adapter checks fixed system values locally.
It preserves customer-controlled values and lets Fusion validate them during
the separately approved import.
Route every import through core.data-loader in FSM mode. A static artifact
never authorizes an import: Data Loader still requires an immutable preview
and approval for that candidate.
Setup Task Skill Contract
- task_code:
AP_MANAGE_INVOICE_OPTIONS
- task_name:
Manage Invoice Options
- parent_skill_id:
erp.financials.payables
- pillar:
ERP
- offering:
Financials
- functional_area:
Payables
- functional_area_code:
FIN_PAYABLES_DEPLOYED
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- dataloader_import_mode:
FSM
- businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Invoice Options under Payables.
Setup Task Metadata
- Task name:
Manage Invoice Options
- Task code:
AP_MANAGE_INVOICE_OPTIONS
- Available:
Y
- Export/import supported:
Y
- CSV export/import supported:
Y
- CSV export/import routing:
supported
- Data Loader import mode:
FSM
- Business Object: ``
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is Y for this task, so route task setup data work through the relevant skills:
- Export setup task data with
shared.setup-export.task-level-export.
- Validate setup task data with
shared.validation.setup-data-validator.
- Validate reference data with
shared.validation.reference-data-validator.
- Import setup task data with
core.data-loader.
Use this task metadata when invoking those skills:
- Offering:
Financials
- Functional area / Setup Object:
Payables
- Setup task name:
Manage Invoice Options
- Setup task code:
AP_MANAGE_INVOICE_OPTIONS
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
skill_run_record
token_usage_record
Implementation Notes
AP_SYSTEM_PARAMETER is a shared row with separate Invoice and Payment
ownership rules. For an Invoice Options setup update, merge the requested change
with the baseline, then validate all resulting Payment-owned values with the
Manage Payment Options field contract. For a new Invoice Options setup row,
validate only supplied Payment-owned values and never invent optional ones.
Invoke only the sibling validator, not the full Payment Options skill, to avoid
a recursive workflow.
For one business unit, a single NLP request that includes both Invoice Options
and Payment Options changes is one shared-row transaction. Merge all requested
fields into one canonical AP_SYSTEM_PARAMETER row before candidate generation,
validate both field contracts against that row, and submit only this Invoice
Options package when any Invoice Options field is present. Do not create or
submit a second full-row package with a different baseline or values. A
Payment-only request remains a Manage Payment Options package.
Use the parent functional-area skill erp.financials.payables for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Account segment serialization and blank-position rules: see ora-resource/ora_input_validation.md, “Account segment package format”.
For account changes, ledger changes affecting an existing account, or enabling
interest invoices, run scripts/resolve_lookup_prerequisites.py --baseline <fresh-export.zip> before normalization. It uses the task-owned
scripts/interest_account_validation.py and the unchanged core OAuth/HTTP client. Require a positive existing
CCID with DynamicInsertion=No; invalid or unavailable validation blocks the
candidate. Preserve receipt bindings to operation, BU, ledger, ordered segments
and baseline. Never create a GL combination. Keep the builder's JSON report
with a generated ZIP. For offline validate-upload, pass that report through
--validation-context <build-report.json>. It ties the original requests and
lookup results to the exact ZIP and baseline, including interest-account
checks. For a separately prepared upload, --prerequisites still accepts
upload-specific preflight receipts. Missing evidence blocks account changes.
Account serialization remains the native 30-slot LF vector.
Narrow Post-Import Interest Verification
This check applies only when a nonblank Interest Expense Distribution was
requested and Create Interest Invoices (AutoCalculateInterestFlag) is Y in
the effective submitted row. Reject a nonblank requested account before building
a package when this flag is not Y; preserve the exported flag for an update
unless the requester changes it. Disabling interest invoices clears the account
and tolerance; do not expect account retention in that case.
After the approved import completes, inspect its status/errors through Data
Loader, obtain a fresh same-task setup-data export through Task Level Export,
then run the task-owned command:
python3 scripts/fsm_task_adapter.py verify-interest --baseline <before.zip> --candidate <approved.zip> --blueprint <blueprint.json> --export <fresh-after.zip> --report <verification.json> --verification-evidence <observations.json> --environment <selected-environment> --base-url <selected-https-origin> --import-request-id <completed-import-request>
Use the environment, HTTPS origin and import request selected by the governed
workflow. The observation file must come from that workflow's actual Data Loader
status/error checks and completed Task Level Export, with file hashes and times.
Do not create success observations from matching CSV values or copied ZIP
metadata. See Error Handling
for the observation fields and checks. Missing or mismatched proof leaves
verification PENDING; do not describe the account as saved.
The task workflow must complete this follow-up before claiming the requested
interest account was configured. PASS means the requested ordered account
segments persisted on the exact BU with interest enabled; a blank or different
account is FAIL. Missing/unreadable readback is PENDING: report "Import
completed; interest account verification pending." With no requested account,
this check is NOT_APPLICABLE. Compare leading zeros and blank segment positions
using the existing canonical multiline format. Do not compare unrelated fields
or BUs, audit values, defaults or derived fields. Full reconcile remains an
optional diagnostic. Do not retry imports or restore values automatically.
Data Loader's import result remains separate. SUCCESS.DONE in the pre-import
Task Hook registry means pre-import readiness, not persisted configuration.
Verifying Changes After Import
reconcile can report PASS only after the workflow has observed a successful
import and a later completed export from the same task and environment. Supply
--verification-evidence <observations.json> --environment <selected-environment> --base-url <selected-https-origin> --import-request-id <completed-import-request>
along with the baseline, approved candidate, blueprint, requirements and export.
Missing, stale or mismatched evidence leaves verification PENDING; say that
saved changes have not yet been verified.
For an offline file comparison, use reconcile --compare-only. Its result is
MATCH or DIFFERENT, with persistenceVerification=NOT_PERFORMED. A file match
does not prove that an import occurred. Package building and import approval
are unchanged. See Error Handling
for the required observations.
Reference Lookup Evidence
When a design or uploaded ZIP uses lookup receipts, follow
Reference evidence provenance.
Keep the selected target separate from evidence, require matching environment
and HTTPS origin, and rerun preflight for missing, malformed, future, or
more-than-24-hour-old observations. The same provenance checks apply to
unavailable lookup warnings. An offline receipt does not authorize a live call
or prove that Fusion imported the ZIP.
Uploaded Package Compatibility
Before reporting an uploaded ZIP as valid, supply validate-upload with
--target-context <selected-target.json> from the independently selected
workflow target. Both baseline and uploaded metadata must match its environment
and release. Read Uploaded package compatibility
for the contract and migration boundary. Matching schemas alone do not establish
source/target compatibility.
Source Manifest Labels and Origins
When producing a source manifest or verifying post-import observations, follow
Manifest labels and HTTPS origins.
A source manifest's environment must match its ZIP metadata; keep migration
destination information separate. Use a credential-free HTTPS origin without
an API path, query or fragment. A template-only label requires an empty package.
Sibling Runtime Dependency
Invoice Options imports the Payment Options descriptor and runtime to validate
Payment-owned fields in the shared AP_SYSTEM_PARAMETER row. It calls the Payment
field-contract entry point, never the full Payment Options workflow or blueprint
validator.
The sibling ID in depends_on is a required code/component dependency. Package
both skill folders, including their SKILL.md, e2e-adapter.json and script files,
under the same Payables parent directory. Preserve the sibling directory names
used by the loaders. The reciprocal declarations describe mutual runtime
requirements, not an execution order or a request to run both workflows.
Dependency collection should include each skill once. A missing sibling runtime
or descriptor blocks validation with an actionable error; do not replace it with
weaker local checks. Keep both components together when distributing this pair.
1---2skill_id: "erp.financials.payables.manage-invoice-options"3name: manage-invoice-options-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Invoice Options under the Payables functional area."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Payables"9functional_area_code: "FIN_PAYABLES_DEPLOYED"10task_code: "AP_MANAGE_INVOICE_OPTIONS"11task_name: "Manage Invoice Options"12parent_skill_id: "erp.financials.payables"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "planning"20execution_mode: "assisted"21owner_team: "ERP financials pillar team"22version: "0.1.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "skill_run_record"33 - "token_usage_record"34depends_on:35 - "shared.setup-export.task-level-export"36 - "shared.validation.setup-data-validator"37 - "shared.validation.reference-data-validator"38 - "core.data-loader"39 - "erp.financials.payables.manage-payment-options"40uses_core:41 - "core.auth.fusion-oauth-authentication"42 - "core.fusion-api.ucm-rest-client"43 - "core.project-mgmt.artifact-version-manager"44 - "core.project-mgmt.artifact-registry-manager"45 - "core.project-mgmt.project-state-manager"46persists_project_state: true47token_usage_tracking:48 enabled: true49 granularity: "per_skill_run"50 artifact_type: "token_usage_record"51 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"52 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"53 required_fields:54 - "activity_start_time"55 - "skill_id"56 - "task"57 - "trigger"58 - "artifacts_written"59 - "files_read"60 - "estimated_input_tokens"61 - "estimated_output_tokens"62 - "estimated_total_tokens"63 - "estimation_method"64 - "notes"65state_updates:66 - "setup_task_sequence"67 - "configuration_blueprints"68 - "validation_results"69 - "token_usage_records"70workspace_outputs:71 - artifact_type: "configuration_blueprint"72 default_location: "project/{project_id}/artifacts/pillars/erp/financials/payables/manage-invoice-options/current/"73 versioning_policy: "major-new-version-minor-confirm-update"74 - artifact_type: "validation_result"75 default_location: "project/{project_id}/artifacts/pillars/erp/financials/payables/manage-invoice-options/current/"76 versioning_policy: "major-new-version-minor-confirm-update"77 - artifact_type: "skill_run"78 default_location: "project/{project_id}/state/runs/"79 versioning_policy: "append-only"80 - artifact_type: "token_usage_record"81 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"82 versioning_policy: "append-only"83applicability:84 industries:85 - "All"86 countries:87 - "All"88 fusion_releases:89 - "Current Oracle Fusion Cloud release"90side_effects: []91required_privileges: []92metadata:93 source: https://skillmd.com/skills/oracle/manage-invoice-options-setup-task-guidance94---9596# Manage Invoice Options Setup Task Guidance9798<!-- fscr-supported-operations: create, update -->99<!-- fscr-create-fields: AP_SYSTEM_PARAMETER::BuName, AP_SYSTEM_PARAMETER::InterestSegments, AP_SYSTEM_PARAMETER::BaseCurrencyCode, AP_SYSTEM_PARAMETER::InvoiceCurrencyCode, AP_SYSTEM_PARAMETER::PaymentCurrencyCode, AP_SYSTEM_PARAMETER::AlwaysTakeDiscFlag, AP_SYSTEM_PARAMETER::PayDateBasisLookupCode, AP_SYSTEM_PARAMETER::AddDaysSettlementDate, AP_SYSTEM_PARAMETER::DaysBetweenCheckCycles, AP_SYSTEM_PARAMETER::FederalIdentificationNum, AP_SYSTEM_PARAMETER::UpdatePaySiteFlag, AP_SYSTEM_PARAMETER::GlDateFromReceiptFlag, AP_SYSTEM_PARAMETER::DiscIsInvLessTaxFlag, AP_SYSTEM_PARAMETER::AccountingMethodOption, AP_SYSTEM_PARAMETER::OnlinePrintFlag, AP_SYSTEM_PARAMETER::EftUserNumber, AP_SYSTEM_PARAMETER::MaxOutlay, AP_SYSTEM_PARAMETER::VendorPayGroupLookupCode, AP_SYSTEM_PARAMETER::RequireTaxEntryFlag, AP_SYSTEM_PARAMETER::PostDatedPaymentsFlag, AP_SYSTEM_PARAMETER::SecondaryAccountingMethod, AP_SYSTEM_PARAMETER::InterestToleranceAmount, AP_SYSTEM_PARAMETER::TermsDateBasis, AP_SYSTEM_PARAMETER::LiabilityPostLookupCode, AP_SYSTEM_PARAMETER::DiscountDistributionMethod, AP_SYSTEM_PARAMETER::CombinedFilingFlag, AP_SYSTEM_PARAMETER::IncomeTaxRegion, AP_SYSTEM_PARAMETER::IncomeTaxRegionFlag, AP_SYSTEM_PARAMETER::AllowFinalMatchFlag, AP_SYSTEM_PARAMETER::AllowFlexOverrideFlag, AP_SYSTEM_PARAMETER::AllowPaidInvoiceAdjust, AP_SYSTEM_PARAMETER::UssglTransactionCode, AP_SYSTEM_PARAMETER::UssglTrxCodeContext, AP_SYSTEM_PARAMETER::InvDocCategoryOverride, AP_SYSTEM_PARAMETER::PayDocCategoryOverride, AP_SYSTEM_PARAMETER::VendorAutoIntDefault, AP_SYSTEM_PARAMETER::TransferDescFlexFlag, AP_SYSTEM_PARAMETER::AllowAwtFlag, AP_SYSTEM_PARAMETER::AllowAwtOverride, AP_SYSTEM_PARAMETER::CreateAwtDistsType, AP_SYSTEM_PARAMETER::CreateAwtInvoicesType, AP_SYSTEM_PARAMETER::AwtIncludeDiscountAmt, AP_SYSTEM_PARAMETER::AwtIncludeTaxAmt, AP_SYSTEM_PARAMETER::AutoCreateFreightFlag, AP_SYSTEM_PARAMETER::GlobalAttributeCategory, AP_SYSTEM_PARAMETER::GlobalAttribute1, AP_SYSTEM_PARAMETER::GlobalAttribute2, AP_SYSTEM_PARAMETER::GlobalAttribute3, AP_SYSTEM_PARAMETER::GlobalAttribute4, AP_SYSTEM_PARAMETER::GlobalAttribute5, AP_SYSTEM_PARAMETER::GlobalAttribute6, AP_SYSTEM_PARAMETER::GlobalAttribute7, AP_SYSTEM_PARAMETER::GlobalAttribute8, AP_SYSTEM_PARAMETER::GlobalAttribute9, AP_SYSTEM_PARAMETER::GlobalAttribute10, AP_SYSTEM_PARAMETER::GlobalAttribute11, AP_SYSTEM_PARAMETER::GlobalAttribute12, AP_SYSTEM_PARAMETER::GlobalAttribute13, AP_SYSTEM_PARAMETER::GlobalAttribute14, AP_SYSTEM_PARAMETER::GlobalAttribute15, AP_SYSTEM_PARAMETER::GlobalAttribute16, AP_SYSTEM_PARAMETER::GlobalAttribute17, AP_SYSTEM_PARAMETER::GlobalAttribute18, AP_SYSTEM_PARAMETER::GlobalAttribute19, AP_SYSTEM_PARAMETER::GlobalAttribute20, AP_SYSTEM_PARAMETER::AllowSupplierBankOverride, AP_SYSTEM_PARAMETER::UseBankChargeFlag, AP_SYSTEM_PARAMETER::BankChargeBearer, AP_SYSTEM_PARAMETER::MrcBaseCurrencyCode, AP_SYSTEM_PARAMETER::GainLossCalcLevel, AP_SYSTEM_PARAMETER::WhenToAccountPmt, AP_SYSTEM_PARAMETER::FutureDatedPmtLiabRelief, AP_SYSTEM_PARAMETER::GlTransferAllowOverride, AP_SYSTEM_PARAMETER::GlTransferMode, AP_SYSTEM_PARAMETER::GlTransferSubmitJournalImp, AP_SYSTEM_PARAMETER::IncludeReportingSob, AP_SYSTEM_PARAMETER::ApprovalWorkflowFlag, AP_SYSTEM_PARAMETER::AllowForceApprovalFlag, AP_SYSTEM_PARAMETER::ValidateBeforeApprovalFlag, AP_SYSTEM_PARAMETER::XmlPaymentsAutoConfirmFlag, AP_SYSTEM_PARAMETER::BuildPrepaymentAccountsFlag, AP_SYSTEM_PARAMETER::Enable1099OnAwtFlag, AP_SYSTEM_PARAMETER::ApprovalTiming, AP_SYSTEM_PARAMETER::ReceiptAcceptanceDays, AP_SYSTEM_PARAMETER::PaymentPriority, AP_SYSTEM_PARAMETER::ExcludeFreightFromDiscount, AP_SYSTEM_PARAMETER::AutoCalculateInterestFlag, AP_SYSTEM_PARAMETER::ProrateIntInvAcrossDists, AP_SYSTEM_PARAMETER::RequireInvoiceGroupFlag, AP_SYSTEM_PARAMETER::EmployeePaymentPriority, AP_SYSTEM_PARAMETER::EmployeePayGroupLookupCode, AP_SYSTEM_PARAMETER::SsInvoiceBackdatingFlag, AP_SYSTEM_PARAMETER::SsLimitToSinglePoFlag, AP_SYSTEM_PARAMETER::SsUpriceChangeForQtymatch, AP_SYSTEM_PARAMETER::SOBName, AP_SYSTEM_PARAMETER::TermName, AP_SYSTEM_PARAMETER::EmployeeTermName, AP_SYSTEM_PARAMETER::PrepaymentTermName, AP_SYSTEM_PARAMETER::ToleranceName, AP_SYSTEM_PARAMETER::ServicesToleranceName, AP_SYSTEM_PARAMETER::AwtName, AP_SYSTEM_PARAMETER::EnterpriseId, AP_SYSTEM_PARAMETER::PrepaymentAvailableMesgFlag, AP_SYSTEM_PARAMETER::RecalcPayScheduleFlag, AP_SYSTEM_PARAMETER::BudgetDateBasis, AP_SYSTEM_PARAMETER::OverrideMatchRejectionFlag, AP_SYSTEM_PARAMETER::RouteInterfaceRejectionFlag, AP_SYSTEM_PARAMETER::AllowInvThirdPartyOvrd, AP_SYSTEM_PARAMETER::AllowPymtThirdPartyOvrd, AP_SYSTEM_PARAMETER::RoutingFlag, AP_SYSTEM_PARAMETER::AttachmentMandatorySsFlag, AP_SYSTEM_PARAMETER::DisallowAttachmentDelFlag, AP_SYSTEM_PARAMETER::BankChargeDeductionTypeDes, AP_SYSTEM_PARAMETER::ReleaseDupInvoiceHoldFlag, AP_SYSTEM_PARAMETER::SsQtyMatchOverbillFlag, AP_SYSTEM_PARAMETER::SsAmtMatchOverbillFlag, AP_SYSTEM_PARAMETER::EscheatmentEligibilityPeriod, AP_SYSTEM_PARAMETER::AccountDefaultBasisCodeDes -->100<!-- fscr-update-fields: AP_SYSTEM_PARAMETER::InterestSegments, AP_SYSTEM_PARAMETER::BaseCurrencyCode, AP_SYSTEM_PARAMETER::InvoiceCurrencyCode, AP_SYSTEM_PARAMETER::PaymentCurrencyCode, AP_SYSTEM_PARAMETER::AlwaysTakeDiscFlag, AP_SYSTEM_PARAMETER::PayDateBasisLookupCode, AP_SYSTEM_PARAMETER::AddDaysSettlementDate, AP_SYSTEM_PARAMETER::DaysBetweenCheckCycles, AP_SYSTEM_PARAMETER::FederalIdentificationNum, AP_SYSTEM_PARAMETER::UpdatePaySiteFlag, AP_SYSTEM_PARAMETER::GlDateFromReceiptFlag, AP_SYSTEM_PARAMETER::DiscIsInvLessTaxFlag, AP_SYSTEM_PARAMETER::AccountingMethodOption, AP_SYSTEM_PARAMETER::OnlinePrintFlag, AP_SYSTEM_PARAMETER::EftUserNumber, AP_SYSTEM_PARAMETER::MaxOutlay, AP_SYSTEM_PARAMETER::VendorPayGroupLookupCode, AP_SYSTEM_PARAMETER::RequireTaxEntryFlag, AP_SYSTEM_PARAMETER::PostDatedPaymentsFlag, AP_SYSTEM_PARAMETER::SecondaryAccountingMethod, AP_SYSTEM_PARAMETER::InterestToleranceAmount, AP_SYSTEM_PARAMETER::TermsDateBasis, AP_SYSTEM_PARAMETER::LiabilityPostLookupCode, AP_SYSTEM_PARAMETER::DiscountDistributionMethod, AP_SYSTEM_PARAMETER::CombinedFilingFlag, AP_SYSTEM_PARAMETER::IncomeTaxRegion, AP_SYSTEM_PARAMETER::IncomeTaxRegionFlag, AP_SYSTEM_PARAMETER::AllowFinalMatchFlag, AP_SYSTEM_PARAMETER::AllowFlexOverrideFlag, AP_SYSTEM_PARAMETER::AllowPaidInvoiceAdjust, AP_SYSTEM_PARAMETER::UssglTransactionCode, AP_SYSTEM_PARAMETER::UssglTrxCodeContext, AP_SYSTEM_PARAMETER::InvDocCategoryOverride, AP_SYSTEM_PARAMETER::PayDocCategoryOverride, AP_SYSTEM_PARAMETER::VendorAutoIntDefault, AP_SYSTEM_PARAMETER::TransferDescFlexFlag, AP_SYSTEM_PARAMETER::AllowAwtFlag, AP_SYSTEM_PARAMETER::AllowAwtOverride, AP_SYSTEM_PARAMETER::CreateAwtDistsType, AP_SYSTEM_PARAMETER::CreateAwtInvoicesType, AP_SYSTEM_PARAMETER::AwtIncludeDiscountAmt, AP_SYSTEM_PARAMETER::AwtIncludeTaxAmt, AP_SYSTEM_PARAMETER::AutoCreateFreightFlag, AP_SYSTEM_PARAMETER::GlobalAttributeCategory, AP_SYSTEM_PARAMETER::GlobalAttribute1, AP_SYSTEM_PARAMETER::GlobalAttribute2, AP_SYSTEM_PARAMETER::GlobalAttribute3, AP_SYSTEM_PARAMETER::GlobalAttribute4, AP_SYSTEM_PARAMETER::GlobalAttribute5, AP_SYSTEM_PARAMETER::GlobalAttribute6, AP_SYSTEM_PARAMETER::GlobalAttribute7, AP_SYSTEM_PARAMETER::GlobalAttribute8, AP_SYSTEM_PARAMETER::GlobalAttribute9, AP_SYSTEM_PARAMETER::GlobalAttribute10, AP_SYSTEM_PARAMETER::GlobalAttribute11, AP_SYSTEM_PARAMETER::GlobalAttribute12, AP_SYSTEM_PARAMETER::GlobalAttribute13, AP_SYSTEM_PARAMETER::GlobalAttribute14, AP_SYSTEM_PARAMETER::GlobalAttribute15, AP_SYSTEM_PARAMETER::GlobalAttribute16, AP_SYSTEM_PARAMETER::GlobalAttribute17, AP_SYSTEM_PARAMETER::GlobalAttribute18, AP_SYSTEM_PARAMETER::GlobalAttribute19, AP_SYSTEM_PARAMETER::GlobalAttribute20, AP_SYSTEM_PARAMETER::AllowSupplierBankOverride, AP_SYSTEM_PARAMETER::UseBankChargeFlag, AP_SYSTEM_PARAMETER::BankChargeBearer, AP_SYSTEM_PARAMETER::MrcBaseCurrencyCode, AP_SYSTEM_PARAMETER::GainLossCalcLevel, AP_SYSTEM_PARAMETER::WhenToAccountPmt, AP_SYSTEM_PARAMETER::FutureDatedPmtLiabRelief, AP_SYSTEM_PARAMETER::GlTransferAllowOverride, AP_SYSTEM_PARAMETER::GlTransferMode, AP_SYSTEM_PARAMETER::GlTransferSubmitJournalImp, AP_SYSTEM_PARAMETER::IncludeReportingSob, AP_SYSTEM_PARAMETER::ApprovalWorkflowFlag, AP_SYSTEM_PARAMETER::AllowForceApprovalFlag, AP_SYSTEM_PARAMETER::ValidateBeforeApprovalFlag, AP_SYSTEM_PARAMETER::XmlPaymentsAutoConfirmFlag, AP_SYSTEM_PARAMETER::BuildPrepaymentAccountsFlag, AP_SYSTEM_PARAMETER::Enable1099OnAwtFlag, AP_SYSTEM_PARAMETER::ApprovalTiming, AP_SYSTEM_PARAMETER::ReceiptAcceptanceDays, AP_SYSTEM_PARAMETER::PaymentPriority, AP_SYSTEM_PARAMETER::ExcludeFreightFromDiscount, AP_SYSTEM_PARAMETER::AutoCalculateInterestFlag, AP_SYSTEM_PARAMETER::ProrateIntInvAcrossDists, AP_SYSTEM_PARAMETER::RequireInvoiceGroupFlag, AP_SYSTEM_PARAMETER::EmployeePaymentPriority, AP_SYSTEM_PARAMETER::EmployeePayGroupLookupCode, AP_SYSTEM_PARAMETER::SsInvoiceBackdatingFlag, AP_SYSTEM_PARAMETER::SsLimitToSinglePoFlag, AP_SYSTEM_PARAMETER::SsUpriceChangeForQtymatch, AP_SYSTEM_PARAMETER::SOBName, AP_SYSTEM_PARAMETER::TermName, AP_SYSTEM_PARAMETER::EmployeeTermName, AP_SYSTEM_PARAMETER::PrepaymentTermName, AP_SYSTEM_PARAMETER::ToleranceName, AP_SYSTEM_PARAMETER::ServicesToleranceName, AP_SYSTEM_PARAMETER::AwtName, AP_SYSTEM_PARAMETER::EnterpriseId, AP_SYSTEM_PARAMETER::PrepaymentAvailableMesgFlag, AP_SYSTEM_PARAMETER::RecalcPayScheduleFlag, AP_SYSTEM_PARAMETER::BudgetDateBasis, AP_SYSTEM_PARAMETER::OverrideMatchRejectionFlag, AP_SYSTEM_PARAMETER::RouteInterfaceRejectionFlag, AP_SYSTEM_PARAMETER::AllowInvThirdPartyOvrd, AP_SYSTEM_PARAMETER::AllowPymtThirdPartyOvrd, AP_SYSTEM_PARAMETER::RoutingFlag, AP_SYSTEM_PARAMETER::AttachmentMandatorySsFlag, AP_SYSTEM_PARAMETER::DisallowAttachmentDelFlag, AP_SYSTEM_PARAMETER::BankChargeDeductionTypeDes, AP_SYSTEM_PARAMETER::ReleaseDupInvoiceHoldFlag, AP_SYSTEM_PARAMETER::SsQtyMatchOverbillFlag, AP_SYSTEM_PARAMETER::SsAmtMatchOverbillFlag, AP_SYSTEM_PARAMETER::EscheatmentEligibilityPeriod, AP_SYSTEM_PARAMETER::AccountDefaultBasisCodeDes -->101102## Purpose103104Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Invoice Options` under `Payables`.105106## Supported Operations107108This task supports creating a new Invoice Options setup row and updating an exact existing setup row. It does not support delete or end-date operations. Only the operation-specific fields documented in [Input Validation](ora-resource/ora_input_validation.md) and [Design Enforcement](ora-resource/ora_design_enforcement.md) are permitted; all other fields remain blocked.109110## Task Behavior111112- Use the exact `AP_SYSTEM_PARAMETER` package and CSV header contract. The113 supported create and update fields are defined by the local resources and114 adapter.115116- Keep the exact `AP_SYSTEM_PARAMETER` package root117 (`/SystemOptionVO/SystemOptionVORow`) and the current template's header order118 and field count. Do not create a replacement schema. For a create, find the119 business unit in `finBusinessUnitsLOV`, use its `PrimaryLedgerId` to find the120 ledger in `ledgersLOV`, and write that ledger name to `SOBName`.121 For `EnterpriseId`, use (in order): the value explicitly requested for that122 row, the current-run default, or the fresh FSM export when it has exactly one123 nonblank value. Record this choice as `enterpriseIdResolution`. An update124 keeps the value from its uniquely matched export row. Fusion then resolves125 `BuName` and `EnterpriseId` to `OrgId`.126- The three payment-term fields are separate defaults. In the CSV, the Payment127 Request Payment Terms control is `EmployeeTermName`. Check each supplied name128 with the read-only `payablesPaymentTerms` service and keep the result as129 evidence only; do not choose an ID from multiple results. On import, Fusion130 resolves `TermName`, `PrepaymentTermName`, and `EmployeeTermName` to their131 corresponding IDs. A missing value is reported as an import dependency.132- Before normalization, run `scripts/resolve_lookup_prerequisites.py` for any133 populated page lookup fields. The adapter checks fixed system values locally.134 It preserves customer-controlled values and lets Fusion validate them during135 the separately approved import.136- Route every import through `core.data-loader` in FSM mode. A static artifact137 never authorizes an import: Data Loader still requires an immutable preview138 and approval for that candidate.139140## Setup Task Skill Contract141142- task_code: `AP_MANAGE_INVOICE_OPTIONS`143- task_name: `Manage Invoice Options`144- parent_skill_id: `erp.financials.payables`145- pillar: `ERP`146- offering: `Financials`147- functional_area: `Payables`148- functional_area_code: `FIN_PAYABLES_DEPLOYED`149- available_flag: `Y`150- export_import_supported_flag: `Y`151- csv_export_import_supported_flag: `Y`152- dataloader_import_mode: `FSM`153- businessObject: ``154- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`155156## Usage157158Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Invoice Options` under `Payables`.159160## Setup Task Metadata161162- Task name: `Manage Invoice Options`163- Task code: `AP_MANAGE_INVOICE_OPTIONS`164- Available: `Y`165- Export/import supported: `Y`166- CSV export/import supported: `Y`167- CSV export/import routing: `supported`168- Data Loader import mode: `FSM`169- Business Object: ``170171## CSV Export, Import, and Validation Workflow172173`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:1741751. Export setup task data with `shared.setup-export.task-level-export`.1762. Validate setup task data with `shared.validation.setup-data-validator`.1773. Validate reference data with `shared.validation.reference-data-validator`.1784. Import setup task data with `core.data-loader`.179180Use this task metadata when invoking those skills:181182- Offering: `Financials`183- Functional area / Setup Object: `Payables`184- Setup task name: `Manage Invoice Options`185- Setup task code: `AP_MANAGE_INVOICE_OPTIONS`186187## Inputs188189- `implementation_objective`190- `project_context`191- `setup_task_scope`192- `setup_data_artifacts`193194## Outputs195196- `setup_task_plan`197- `setup_data_routing`198- `validation_checkpoints`199- `skill_run_record`200- `token_usage_record`201202## Implementation Notes203204`AP_SYSTEM_PARAMETER` is a shared row with separate Invoice and Payment205ownership rules. For an Invoice Options setup update, merge the requested change206with the baseline, then validate all resulting Payment-owned values with the207Manage Payment Options field contract. For a new Invoice Options setup row,208validate only supplied Payment-owned values and never invent optional ones.209Invoke only the sibling validator, not the full Payment Options skill, to avoid210a recursive workflow.211212For one business unit, a single NLP request that includes both Invoice Options213and Payment Options changes is one shared-row transaction. Merge all requested214fields into one canonical `AP_SYSTEM_PARAMETER` row before candidate generation,215validate both field contracts against that row, and submit only this Invoice216Options package when any Invoice Options field is present. Do not create or217submit a second full-row package with a different baseline or values. A218Payment-only request remains a Manage Payment Options package.219220Use the parent functional-area skill `erp.financials.payables` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.221222Account segment serialization and blank-position rules: see `ora-resource/ora_input_validation.md`, “Account segment package format”.223224For account changes, ledger changes affecting an existing account, or enabling225interest invoices, run `scripts/resolve_lookup_prerequisites.py --baseline226<fresh-export.zip>` before normalization. It uses the task-owned227`scripts/interest_account_validation.py` and the unchanged core OAuth/HTTP client. Require a positive existing228CCID with `DynamicInsertion=No`; invalid or unavailable validation blocks the229candidate. Preserve receipt bindings to operation, BU, ledger, ordered segments230and baseline. Never create a GL combination. Keep the builder's JSON report231with a generated ZIP. For offline `validate-upload`, pass that report through232`--validation-context <build-report.json>`. It ties the original requests and233lookup results to the exact ZIP and baseline, including interest-account234checks. For a separately prepared upload, `--prerequisites` still accepts235upload-specific preflight receipts. Missing evidence blocks account changes.236Account serialization remains the native 30-slot LF vector.237238## Narrow Post-Import Interest Verification239240This check applies only when a nonblank Interest Expense Distribution was241requested and Create Interest Invoices (`AutoCalculateInterestFlag`) is `Y` in242the effective submitted row. Reject a nonblank requested account before building243a package when this flag is not `Y`; preserve the exported flag for an update244unless the requester changes it. Disabling interest invoices clears the account245and tolerance; do not expect account retention in that case.246247After the approved import completes, inspect its status/errors through Data248Loader, obtain a fresh same-task setup-data export through Task Level Export,249then run the task-owned command:250251```text252python3 scripts/fsm_task_adapter.py verify-interest --baseline <before.zip> --candidate <approved.zip> --blueprint <blueprint.json> --export <fresh-after.zip> --report <verification.json> --verification-evidence <observations.json> --environment <selected-environment> --base-url <selected-https-origin> --import-request-id <completed-import-request>253```254255Use the environment, HTTPS origin and import request selected by the governed256workflow. The observation file must come from that workflow's actual Data Loader257status/error checks and completed Task Level Export, with file hashes and times.258Do not create success observations from matching CSV values or copied ZIP259metadata. See [Error Handling](ora-resource/ora_error_handling.md#post-import-readback-evidence)260for the observation fields and checks. Missing or mismatched proof leaves261verification `PENDING`; do not describe the account as saved.262263The task workflow must complete this follow-up before claiming the requested264interest account was configured. `PASS` means the requested ordered account265segments persisted on the exact BU with interest enabled; a blank or different266account is `FAIL`. Missing/unreadable readback is `PENDING`: report "Import267completed; interest account verification pending." With no requested account,268this check is `NOT_APPLICABLE`. Compare leading zeros and blank segment positions269using the existing canonical multiline format. Do not compare unrelated fields270or BUs, audit values, defaults or derived fields. Full `reconcile` remains an271optional diagnostic. Do not retry imports or restore values automatically.272273Data Loader's import result remains separate. `SUCCESS.DONE` in the pre-import274Task Hook registry means pre-import readiness, not persisted configuration.275276## Verifying Changes After Import277278`reconcile` can report `PASS` only after the workflow has observed a successful279import and a later completed export from the same task and environment. Supply280`--verification-evidence <observations.json> --environment <selected-environment>281--base-url <selected-https-origin> --import-request-id <completed-import-request>`282along with the baseline, approved candidate, blueprint, requirements and export.283Missing, stale or mismatched evidence leaves verification `PENDING`; say that284saved changes have not yet been verified.285286For an offline file comparison, use `reconcile --compare-only`. Its result is287`MATCH` or `DIFFERENT`, with `persistenceVerification=NOT_PERFORMED`. A file match288does not prove that an import occurred. Package building and import approval289are unchanged. See [Error Handling](ora-resource/ora_error_handling.md#reconciliation-evidence)290for the required observations.291292293## Reference Lookup Evidence294295When a design or uploaded ZIP uses lookup receipts, follow296[Reference evidence provenance](references/reference-evidence-provenance.md).297Keep the selected target separate from evidence, require matching environment298and HTTPS origin, and rerun preflight for missing, malformed, future, or299more-than-24-hour-old observations. The same provenance checks apply to300unavailable lookup warnings. An offline receipt does not authorize a live call301or prove that Fusion imported the ZIP.302303304## Uploaded Package Compatibility305306Before reporting an uploaded ZIP as valid, supply `validate-upload` with307`--target-context <selected-target.json>` from the independently selected308workflow target. Both baseline and uploaded metadata must match its environment309and release. Read [Uploaded package compatibility](references/uploaded-package-compatibility.md)310for the contract and migration boundary. Matching schemas alone do not establish311source/target compatibility.312313314## Source Manifest Labels and Origins315316When producing a source manifest or verifying post-import observations, follow317[Manifest labels and HTTPS origins](references/manifest-labels-and-origins.md).318A source manifest's environment must match its ZIP metadata; keep migration319destination information separate. Use a credential-free HTTPS origin without320an API path, query or fragment. A template-only label requires an empty package.321322323## Sibling Runtime Dependency324325Invoice Options imports the Payment Options descriptor and runtime to validate326Payment-owned fields in the shared AP_SYSTEM_PARAMETER row. It calls the Payment327field-contract entry point, never the full Payment Options workflow or blueprint328validator.329330The sibling ID in `depends_on` is a required code/component dependency. Package331both skill folders, including their SKILL.md, e2e-adapter.json and script files,332under the same Payables parent directory. Preserve the sibling directory names333used by the loaders. The reciprocal declarations describe mutual runtime334requirements, not an execution order or a request to run both workflows.335Dependency collection should include each skill once. A missing sibling runtime336or descriptor blocks validation with an actionable error; do not replace it with337weaker local checks. Keep both components together when distributing this pair.