On this page
Prepare source inputs
Collect source artifacts and shared dependencies, record their revision, and check the package before supplying it to a project.
Prepare a package that describes the scope you want to assess. The result should let another team member identify what was supplied, where it came from, and which questions the material is intended to answer.
Before you begin
You need an agreed source platform and assessment scope, access to the relevant exports or scripts, and a source owner who can resolve missing dependencies. Use the source platform’s approved extraction or export process.
Resolve the platform choice before creating the project: Source Platform cannot be changed after project creation in the reference workflow. This guide covers preparation and handover of artifacts; it does not install the modernAIze service.
Select the source material
Choose the platform that produced the source. For data estates, collect SAS or Qlik scripts, Informatica or DataStage exports, Teradata SQL/BTEQ, or an SAP BW extraction. For application estates, collect COBOL programs and copybooks or webMethods service and namespace artifacts.
Use the platform guide to identify the main input format and shared dependencies. Files, Folder, and ZIP are ways to supply material in the reference Setup workflow; packaging does not change which source artifacts are appropriate for the selected platform.
Start from the required output
- Identify the report or data output for a data estate, or the entry program, service, or operation for an application estate.
- List the programs or definitions that produce it.
- Add the structures, routines, and shared inputs required to interpret them.
- Mark dependencies that remain outside the package and identify their owners.
For monthly revenue, include the reporting script and the definitions needed to understand orders, exchange rates, conversion, and aggregation. If another team owns the conversion routine, record that handover explicitly rather than assuming its behavior from the call name.
Collect a consistent source revision
Use artifacts from a known revision or extraction period. Mixing a current job definition with an old structure can produce a confusing picture of the flow. Record the extraction date or source revision and any unavoidable exceptions.
Preserve the filenames and directory context that help a reviewer identify the material. For an extraction package, retain the components needed to interpret its catalog and object detail. Follow the SAP BW guide for that platform’s package structure.
Review the package contents
Inspect the package before transfer. Remove files unrelated to the agreed scope and handle connection details or other sensitive contents according to the engagement’s approved process. Source logic and metadata need review even when no business records are included.
Keep a short manifest with the handover. The following example is an engagement record, not an import format required by modernAIze:
| Material | Revision context | Review note |
|---|---|---|
| Monthly reporting script | Agreed source revision | Includes conversion call and monthly aggregation |
| Orders and rate definitions | Same source revision | Required to interpret the script’s inputs |
| Shared conversion routine | Awaiting source owner | Rate-selection behavior remains open |
Avoid placing source passwords or tokens in the manifest.
Hand over and verify
Give the project editor the package, manifest, source platform, and expected outputs or objects. When the analysis is available:
- Confirm that the intended files appear in the project inputs.
- Read the Briefing for the expected system purpose and composition.
- Check that the relevant processing and dependencies are represented.
- Compare any missing or partial information with the manifest.
A missing file returns to package preparation. An included file with incomplete analysis needs investigation of the result and its reported limitations. Keep those two cases separate when asking for help.