Hugging Face's logo

Datasets:
smurthy5
/
CrossER

Tasks:
Text Classification
Other
Modalities:
Tabular
Text
Formats:
json
Languages:
English
German
Size:
1K - 10K
Tags:
entity-resolution
record-linkage
cross-system-matching
enterprise-data
benchmark
rag
Libraries:
Datasets
pandas
Polars
License:
Dataset card Data Studio Files
xet
 Community
1
CrossER / data /context /raw /documents /migration_runbook.md
smurthy5's picture
smurthy5
Upload data/context/raw/documents/migration_runbook.md with huggingface_hub
a2763b4 verified
preview code
|
raw
history blame contribute delete
3.18 kB

Q4 2025 ERP Migration Runbook

Document ID: RB-MIG-2025-Q4 Version: 3.1 Last Updated: 2025-09-24 Classification: Internal Use Only

1. Executive Summary

This runbook documents the migration of master data from LEGACY_ERP to SAP_TC2 as part of the legacy system decommission initiative. The migration covers products, suppliers, and legal entities currently maintained in the legacy platform.

2. Migration Scope

2.1 Systems Involved

System Role Status
LEGACY_ERP Source (decommission) Active until Q4 2025
SAP_TC2 Primary target Production
SAP_CFIN Financial consolidation Receiving updates
SAP_APAC APAC regional Subset migration

2.2 Entity Scope

  • Products: ~80 active records in LEGACY_ERP
  • Suppliers: ~20 active vendor records
  • Legal entities: ~10 subsidiary records

3. Migration Methodology

3.1 Naming Convention Mapping

LEGACY_ERP uses cryptic internal codes that must be mapped to SAP_TC2 formal names. The mapping follows these patterns:

  • Legacy codes with prefix STR- correspond to starch products in TC2
  • Legacy codes with prefix SUG- correspond to sugar products in TC2
  • Legacy codes with prefix ACD- correspond to acid products in TC2
  • Legacy codes with prefix PRT- correspond to protein products in TC2
  • Legacy codes with prefix OIL- correspond to oil & fat products in TC2

3.2 Completed Migrations

The following entities have been migrated and verified:

  • ZINCOXID (LEGACY_ERP) was migrated to Zinc Oxide Food Grade in SAP_TC2. Verified by data steward.
  • STR-005 (LEGACY_ERP) was migrated to Modified Corn Starch in SAP_TC2. Verified by data steward.
  • sugar product 889 (LEGACY_ERP) was migrated to Sorbitol Powder in SAP_TC2. Verified by data steward.
  • FBR-130 (LEGACY_ERP) was migrated to Chicory Root Fiber in SAP_TC2. Verified by data steward.
  • product 636 (LEGACY_ERP) was migrated to Disodium 5-Ribonucleotides in SAP_TC2. Verified by data steward.

3.3 Pending Migrations

The remaining legacy entities are pending manual review before migration. Contact the migration team for status updates.

4. APAC Regional Considerations

SAP_APAC uses abbreviated naming conventions. When cross-referencing with TC2:

  • APAC product codes use shortened forms (e.g., 'Malto-Dex' instead of full product names)
  • APAC supplier names may use regional abbreviations
  • Not all TC2 products have APAC equivalents — only APAC-relevant products are maintained

5. SAP_CFIN Integration

SAP_CFIN uses internal financial codes that differ from TC2 product names. Common patterns:

  • Product NNNN — numeric product identifiers in CFIN
  • MAT-NNNNN — material codes for raw materials
  • ING-NNNNN — ingredient codes
  • RM-NNNNN — raw material codes

These codes are mapped to TC2 entities via the product crosswalk table.

6. Rollback Procedures

In case of migration failure:

  1. Restore LEGACY_ERP from backup
  2. Revert SAP_TC2 changes using migration journal
  3. Notify downstream systems

This document is maintained by the Migration Team. Contact migration-team@company.com