Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: Integration data flow

Integration data flow

Who sends which information to whom, in which direction, and through what mechanism?

This view traces supported information movement around customer integration: customer forms, executable customer operations, the stores7 customer records, and the supplied unload records. The source shows form fields mapped to customer columns and executable functions that read or write the customer table through Informix SQL E0007. The supplied material does not establish a single runtime deployment or prove that generated Java artifacts are loaded at runtime E0008.

The order and item unload records are retained as a separate store because their relationship to the customer flow is not established. The item field meanings are only inferred from cross-file use, not declared in the unload file itself E0008.

Diagram

flowchart LR
  n8e0d6cf8b1ec53af7c67["Customer forms"]
  n2ad93273b9dc7ed2d992["Customer application"]
  n1517c439620528079c2f["Stores7 customer records"]
  n7fa9b738616fc725ffde["Customer source records"]
  ncb084cd61a42c933125d["Order and item unload records"]
  n2a906cadac554ac6dd30["Main navigation"]
  n7531659ac43b7eb29ac8["Help and executable source"]
  n8e0d6cf8b1ec53af7c67 -->|"Customer entry to customer processing"| n2ad93273b9dc7ed2d992
  n2ad93273b9dc7ed2d992 -->|"Customer processing to database records"| n1517c439620528079c2f
  n1517c439620528079c2f -->|"Database records to customer processing"| n2ad93273b9dc7ed2d992
  n2ad93273b9dc7ed2d992 -->|"Customer processing to customer forms"| n8e0d6cf8b1ec53af7c67
  n2a906cadac554ac6dd30 -->|"Main navigation to customer processing"| n2ad93273b9dc7ed2d992
  n7fa9b738616fc725ffde -.->|"Customer source records to customer processing (inferred)"| n2ad93273b9dc7ed2d992

Elements

Customer forms

Kind: component
Basis: reported
Description: Customer form sources define screens for customer number, name, company, address, city, state, ZIP code, and telephone; their fields map to corresponding customer columns E0007.
Evidence: E0007

Customer application

Kind: component
Basis: reported
Description: The executable customer functions add, find, update, delete, and display customer records. Customer input uses INPUT BY NAME; queries use constructed selection criteria; updates and deletes operate on selected customer rows E0007.
Evidence: E0007

Stores7 customer records

Kind: store
Basis: reported
Description: The stores7 database declares a customer table. The customer source records contain customer number, name, business, address, city, state, ZIP code, and telephone values E0007.
Evidence: E0007

Customer source records

Kind: store
Basis: reported
Description: The customer unload excerpt contains 18 pipe-delimited records with identifiers 101 through 118 and customer contact and address fields. This is an unload excerpt, not proof of the complete database contents E0007E0008.
Evidence: E0007, E0008

Order and item unload records

Kind: store
Basis: reported
Description: The item unload excerpt contains six pipe-delimited values per visible row. Its field meanings are not declared in the file; mapping them to order and item concepts is only a cross-file inference E0007E0008.
Evidence: E0007, E0008

Main navigation

Kind: component
Basis: reported
Description: The main menu provides Customer, Orders, Stock, Reports, and Exit commands; selecting Customer calls the customer routine and later returns to the menu E0007.
Evidence: E0007

Help and executable source

Kind: component
Basis: reported
Description: Help text documents customer, order, stock, and report operations, but it diverges from executable source in form names, window coordinates, and some identifiers. It should therefore be treated as supporting documentation rather than an exact runtime definition E0008.
Evidence: E0008

Relationships

Customer entry to customer processing

From: Customer forms
To: Customer application
Relation: sends
Basis: reported
Description: Customer form fields are accepted by the customer application through INPUT BY NAME; normal completion proceeds to customer insertion, while interruption exits input without inserting E0007.
Evidence: E0007
Information: Customer number, name, company, address, city, state, ZIP code, and telephone input E0007.
Mechanism: Form input using INPUT BY NAME, with field help and interruption controls E0007.

Customer processing to database records

From: Customer application
To: Stores7 customer records
Relation: sends
Basis: reported
Description: Customer creation inserts p_customer.* into the customer table. Updates modify the matching customer row, and confirmed deletions remove the selected customer row E0007.
Evidence: E0007
Information: Customer record fields and selected customer identity E0007.
Mechanism: Informix SQL INSERT, UPDATE, and DELETE operations in the executable source E0007.

Database records to customer processing

From: Stores7 customer records
To: Customer application
Relation: sends
Basis: reported
Description: Customer searches construct selection criteria over customer fields, prepare an ordered query, and browse returned results. The application also retrieves customer records for reporting E0007.
Evidence: E0007
Information: Customer rows matching query-by-example criteria, ordered by last name for customer browsing E0007.
Mechanism: Constructed SQL selection, prepared query, and browse actions E0007.

Customer processing to customer forms

From: Customer application
To: Customer forms
Relation: sends
Basis: reported
Description: The customer routine opens and displays the customer form, initializes customer state, displays generated customer numbers after insertion, and redisplays selected state values E0007.
Evidence: E0007
Information: Customer field values, generated customer number, and selected state code E0007.
Mechanism: Form opening, field display, and executable form interaction E0007.

Main navigation to customer processing

From: Main navigation
To: Customer application
Relation: sends
Basis: reported
Description: Selecting the Customer command from the main menu calls the customer routine; after customer operations, control returns to the menu flow E0007.
Evidence: E0007
Information: Customer-operation command selection E0007.
Mechanism: Menu command dispatch to the customer routine E0007.

Customer source records to customer processing

From: Customer source records
To: Customer application
Relation: sends
Basis: inferred
Description: The unload records are structurally consistent with the customer fields used by the customer forms and application, but the evidence does not show an import or runtime load operation from this unload file. This is a semantic correspondence, not a confirmed runtime transfer E0007E0008.
Evidence: E0007, E0008
Information: Unload customer rows containing identifiers and contact/address values E0007.
Mechanism: Unknown; no source-supported import or load mechanism is established E0008.

Gaps

The evidence does not establish that customer.unl is loaded into the application or database, so the apparent relationship between the unload records and runtime customer processing remains inferred E0008.

No supported sender or receiver is established for the order and item unload records. Their contents are therefore not modeled as an integration flow; the item-field interpretation remains cross-file inference E0008.

The customer insertion path has no explicit post-INSERT status check in the supplied source, and transaction handling for customer creation is not shown. Whether a failed insert can be reported as successful requires runtime or broader source verification E0008.

The supplied form declarations do not prove that the corresponding binary forms match them. Additional runtime dependencies named orderform, state_list, and stock_sel are not verified by the supplied evidence E0008.

The two database configuration files specify materially different endpoints and credentials, and precedence or deployment context is unresolved. This prevents a reliable assertion about which physical database receives the customer flow E0008.

Recovery limitations

• Ownership, mechanism or boundary controls remain explicitly unverified.
• Some identified concepts have no supported connection.
• The view includes explicitly marked inference.

Sources

• E0007 — SHA256 ce6dd2b00b79f008ecb98935db9ed709c044218bcdd4143008d56d06a04cff97
• E0008 — SHA256 1713f4e3d42ac5e2af28387ac6ff649f06bbe1683b11869af71326929d6a5f32