Lesson 1 of 5
The onboarding lifecycle
10 min
Listen to this lesson
Most EDI problems in production were decided in the first two weeks of onboarding: an identifier copied from an old e-mail, a mapping rule nobody wrote down, a test that proved the connection but not the business result. Onboarding a trading partner is a small project with an outside party, and it deserves a repeatable process with gates, owners and evidence. This course gives you that process and the Academy's sign-off angle on it. It applies equally to classic middleware such as SAP Process Orchestration and to SAP Integration Suite with Trading Partner Management (TPM).
The running example is real for Contoso Motor Co. After the B2B interfaces moved to Integration Suite, sales won a new fleet customer, Northern Plains Coach Lines, which runs a coach fleet across the upper Midwest and wants to order alternators by EDI. Northern Plains will send X12 850 orders over AS2 and expects 997 acknowledgments, 855 order responses, 856 ship notices and 810 invoices, all in version 004010. Theo's integration team owns the build, Priya owns testing, Maria owns order-to-cash acceptance, and Northern Plains has one EDI coordinator.
Seven phases with gates
- Kickoff. Exchange contacts and the partner's implementation guide; complete an onboarding questionnaire; agree the target date and test windows.
- Specification. Turn the partner's guide into a mapping specification for each document; resolve gaps; both sides sign it.
- Build. Create the partner profile and agreement (in TPM from the existing fleet customer template), partner-specific mapping if needed, master data in SAP S/4HANA, and certificates.
- Testing. Connectivity, syntax, business rules and end to end, each with entry and exit criteria agreed with the partner.
- Certification. The partner confirms that Contoso's documents meet its requirements, often against its own checklist or scorecard.
- Pilot or parallel run. Limited production volume under close watch, with daily reconciliation.
- Go-live and handover. Full volume, evidence pack, runbook and a hypercare period before support owns the partner.
Four traps account for most onboarding delays at Contoso and elsewhere. The partner sends test files from its production system with production identifiers, so test and production can't be told apart. Nobody owns the partner's master data in SAP, so conversion tables are filled the day before testing. The test windows are agreed loosely, so a week is lost waiting for a partner response. And acknowledgments are treated as success, so business rejections surface only after go-live. Each phase below has a gate designed to catch one of them.
The onboarding questionnaire
The questionnaire is the cheapest test you will ever run: it finds wrong assumptions before anything is built. Contoso's version asks for the following and stores the answers with the partner profile.
| Topic | What to collect | Northern Plains answer |
|---|---|---|
| Standard and version | X12 or EDIFACT, version, document list | X12 004010: 850 in; 997, 855, 856, 810 out |
| Identifiers | Interchange ID and qualifier, group IDs, test and production IDs | ZZ NPCOACHEDI in both environments |
| Transport | AS2, SFTP or network; endpoints; AS2 IDs; MDN type | AS2, synchronous signed MDN, AS2 ID NPCL-AS2 |
| Security | Certificates, algorithms, renewal contact | SHA-256 signing, AES256 encryption, certificates by e-mail to Nadia's team |
| Acknowledgments | 997 expected, timing, TA1 or not | 997 within 4 hours; no TA1 |
| Volumes and timing | Documents per day, peaks, cut-off times | About 20 orders per week, Monday peak, cut-off 14:00 Central |
| Test windows | When the partner can test, and how long | Tuesdays and Thursdays for four weeks |
| Business rules | Ship-to locations, item numbers, pricing, partial shipments | 11 depots as ship-tos; buyer part numbers; contract price; partials allowed |
Contoso's onboarding questionnaire with Northern Plains Coach Lines' answers.
Classic middleware or Integration Suite
The phases are the same on any platform; the build step differs. On SAP Process Orchestration with the B2B add-on, the build means new communication components, channels with the AS2 adapter and converter modules, and often a copied mapping. On SAP Integration Suite with TPM, it means a trading partner profile and an agreement derived from an existing template, plus a partner-specific mapping guideline only where rules differ. That makes the build faster, but it doesn't shorten testing: the partner's identifiers, locations, part numbers and acknowledgment habits are new either way, and they are where onboarding defects come from.
Who does what
| Activity | Contoso integration (Theo) | Contoso test (Priya) | Business (Maria) | Partner coordinator |
|---|---|---|---|---|
| Questionnaire and guide | Owns | Reviews | Answers business rules | Provides |
| Mapping specification | Writes | Reviews for testability | Approves rules | Approves |
| Build and master data | Builds | Checks readiness | Maintains customer data | Sends certificates |
| Test phases | Supports | Owns plan and evidence | Accepts business results | Sends and checks test files |
| Certification and cutover | Supports | Prepares evidence | Signs off | Certifies, agrees date |
- Week 1KickoffQuestionnaire returned; implementation guide received; target go-live agreed.
- Weeks 2-3Specification and buildMapping spec signed by both sides; TPM profile and agreement built in CMC_DEV, tested in CMC_TEST.
- Weeks 4-7Testing and certificationFour test weeks with the partner on Tuesdays and Thursdays; certification at the end.
- Weeks 8-9PilotTwo depots order by EDI; the others keep ordering by e-mail.
- Week 10Go-liveAll 11 depots; handover to support with a two-week hypercare.
What would you do?
Sales tells the team that Northern Plains wants to "go live on EDI in two weeks", and the partner's implementation guide hasn't arrived yet. What should Theo and Priya do?
- Onboarding is a small project with an outside party: kickoff, specification, build, testing, certification, pilot, go-live.
- Each phase ends at a gate; certification and cutover are agreed in writing with the partner.
- The questionnaire captures standards, IDs, transport, security, acknowledgments, volumes, test windows and business rules.
- Give realistic dates from the guide, test windows and certification, not from the template alone.
Check your understanding · not graded
Lesson check
1. What is the main purpose of the onboarding questionnaire?
2. Which phase ends with the partner confirming that Contoso's documents meet its requirements?
3. Why can't Contoso skip partner testing for Northern Plains because the TPM template works for Great Lakes?
4. Who should own the test plan and the evidence during onboarding?