149 lines
4.0 KiB
Plaintext
149 lines
4.0 KiB
Plaintext
IRA Story IA-2866 - RAG Knowledge Base
|
|
Chunk 1: Story Overview
|
|
|
|
Metadata: module=JIRA, storyId=IA-2866, type=overview, domain=dataPreloading, system=AWS
|
|
|
|
Purpose:
|
|
Preloads iSeries-derived data into AWS data store to support downstream nightly processing for pending cancellations, cancellations, and billing statements.
|
|
|
|
Business Goal:
|
|
Ensure required historical and transactional data is available so nightly processes can successfully validate and retrieve prior information.
|
|
|
|
Key Concepts:
|
|
data preloading, AWS data store, iSeries integration, billing statements, cancellation processing, nightly validation workflows.
|
|
|
|
Chunk 2: Preconditions
|
|
|
|
Metadata: storyId=IA-2866, type=preconditions, dependencies=externalSystems
|
|
|
|
Requirements:
|
|
|
|
Data must be extracted from iSeries and/or EDW
|
|
Oracle identifier may exist on payment schedule file (requires confirmation)
|
|
|
|
Purpose:
|
|
Defines required upstream data availability before AWS preloading can occur.
|
|
|
|
Chunk 3: Pending Cancel Document Requirements
|
|
|
|
Metadata: storyId=IA-2866, type=requirements, documentType=pendingCancel
|
|
|
|
Required Fields:
|
|
|
|
AccountIdentifier
|
|
PrimaryCancellationReason
|
|
CancellationNoticeDate
|
|
CancellationEffectiveDate
|
|
PolicyNumber
|
|
TransactionId
|
|
InstallmentNumber
|
|
|
|
Purpose:
|
|
Defines data required to construct pending cancellation records in AWS.
|
|
|
|
Chunk 4: Billing Statement Document Requirements
|
|
|
|
Metadata: storyId=IA-2866, type=requirements, documentType=billingStatement
|
|
|
|
Required Fields:
|
|
|
|
AccountIdentifier
|
|
PaymentDueDate
|
|
StatementType
|
|
PolicyNumber
|
|
TransactionId
|
|
InstallmentNumber
|
|
|
|
Purpose:
|
|
Defines data required for billing statement records used in downstream processing.
|
|
|
|
Chunk 5: Cancellation Requirements
|
|
|
|
Metadata: storyId=IA-2866, type=requirements, documentType=cancellation
|
|
|
|
Required Fields:
|
|
|
|
AccountIdentifier
|
|
CancellationDate
|
|
PolicyNumber
|
|
|
|
Purpose:
|
|
Defines minimal dataset required to represent completed cancellations.
|
|
|
|
Chunk 6: External System Responsibilities
|
|
|
|
Metadata: storyId=IA-2866, type=integration, systems=iSeries,AWS,Oracle
|
|
|
|
iSeries Responsibilities:
|
|
|
|
Provides PolicyNumber
|
|
Provides InstallmentNumber
|
|
Provides document type information
|
|
|
|
AWS Responsibilities:
|
|
|
|
Fetch missing attributes from iSeries APIs
|
|
Fetch additional data from Oracle systems
|
|
|
|
Oracle Role:
|
|
|
|
Supplies supplemental identifiers and attributes not available in iSeries
|
|
Chunk 7: Installment Handling Rules
|
|
|
|
Metadata: storyId=IA-2866, type=businessRules, domain=installments
|
|
|
|
Rules:
|
|
|
|
iSeries sends only the latest InstallmentNumber
|
|
If InstallmentNumber > 1:
|
|
System must pre-populate Installment 1 data
|
|
Ensures billing statement completeness
|
|
|
|
Purpose:
|
|
Ensures correct historical representation of billing data when only partial installment data is provided.
|
|
|
|
Chunk 8: Data Preloading Workflow
|
|
|
|
Metadata: storyId=IA-2866, type=workflow, stage=preprocessing
|
|
|
|
Flow:
|
|
|
|
Extract data from iSeries and/or EDW
|
|
Validate availability of required identifiers
|
|
Enrich missing data via AWS calls to iSeries APIs and Oracle
|
|
Apply installment handling rules
|
|
Store processed data in AWS data store
|
|
Make data available for nightly processing
|
|
|
|
Purpose:
|
|
Describes end-to-end data preparation process.
|
|
|
|
Chunk 9: Data Quality and Assumptions
|
|
|
|
Metadata: storyId=IA-2866, type=dataQuality, validation=assumed
|
|
|
|
Assumptions:
|
|
|
|
Required fields are available from upstream systems
|
|
Oracle identifiers may require validation
|
|
Installment data may be incomplete and requires augmentation
|
|
|
|
Risks:
|
|
|
|
Missing Oracle identifiers could impact downstream linking
|
|
Incomplete installment data without rule handling could break billing logic
|
|
Chunk 10: Search Queries Supported
|
|
|
|
Metadata: storyId=IA-2866, type=queryPatterns, purpose=RAGRetrieval
|
|
|
|
Examples:
|
|
|
|
What data is required for pending cancel documents?
|
|
What fields are needed for billing statement generation?
|
|
What systems provide installment data?
|
|
How are missing attributes retrieved in AWS?
|
|
What are the rules for installment handling?
|
|
What data is required for cancellation records?
|
|
What are the preconditions for AWS data preloading?
|
|
How does AWS enrich iSeries data?
|
|
What happens when installment number is greater than 1? |