SAP Technical BA

Tech BA, Output Management

Project language: German

On-site: Munich, Frankfurt or Essen, up to 3 days every 3 weeks

Start: ASAP

About the Output Management squad

The squad owns the end-to-end output process. That covers mass correspondence built on SAP application forms, document rendering, and print processes out of SAP S/4HANA. SAP CE and CPQ connect to the Quadient Inspire platform through interfaces, and harmonised data streams feed the generation of individual correspondence, tariff sheets, orders and similar documents.

The squad also owns archiving in nScale, so documents are stored efficiently and, in an audit,-proof way, then made available to customers and agents.

Scope note

This role does not work on Inspire or nScale user stories. It works on the SAP user stories that sit upstream or downstream of them.

Core requirements

• Prioritising user stories by refinement status
• Experience with interfaces between SAP, web services and Inspire, including firewall considerations
• Understanding of bounce email management: rule sets, data structures, audit
• Ideally, experience working with teams in India

Priority 1 skills

1. SAP correspondence and trigger mechanisms

How SAP triggers correspondence: event-driven (ad hoc, single) versus mass batch runs such as billing, invoicing and dunning via FPCOPARA

Working knowledge of the SAP Correspondence Tool, Correspondence Container and Print Workbench (application forms, form classes)

2. Source-to-target data mapping (SAP CCM payload)

Identifying which SAP tables and fields hold the required data: Business Partner, Contract Account, Contract, Meter Reading, document line items

Writing clear data contracts for what SAP passes to the rendering engine (e.g. Quadient Inspire): XML/JSON payload definitions, field types, cardinalities, fallbacks and transformation logic

3. Functional requirements engineering

Implementation-ready specs covering trigger events, data extraction rules, conditional logic (e.g. “if customer type = B2B and country = DE, render text block X”) and fallback rules for missing data

Multi-channel dispatch routing: print shop via spool/OMS, transactional email, customer portal

4. Hands-on SAP navigation and data checks

Navigating SAP GUI independently: SE16N/SE11 for tables, FPL9 for account balance and correspondence history, SP01/SM37 for spool and job monitoring

Confirming whether a trigger fired and inspecting the raw payload in SAP without calling in a developer for basic checks

5. E2E test design and test data

Defining and running Product Increment Tests (PIT) and Business Process Tests (BPT): happy path, edge cases (special characters, long names, negative balances) and error scenarios

Finding or staging valid test accounts and contracts in lower SAP tiers (DV1, FV1, QV1) that reflect real customer constellations

6. Interface and dependency management

Acting as functional translator between upstream business squads (Billing, Sales, Service), SAP ABAP/integration engineers and downstream document designers (CCM/Inspire team)

Nice to have

• ABAP basics: reading simple ABAP and stepping through the debugger to find where an extraction or rule fails
• Quadient Inspire: familiarity with Designer/Interactive concepts (variables, layout blocks, rules) to understand template constraints and effort estimates
• Archiving and post-processing: SAP ArchiveLink, document indexing, enterprise archiving (nScale, OpenText); downstream print management (OMS, spool formatting, postal optimisation and sorting tools such as Columbus or Paragon)
• Compliance and accessibility: PDF/UA, BITV, and GDPR (DSGVO) retention and redaction requirements
• Payload analysis: XPath, JSONPath or SQL for inspecting large correspondence batches or test datasets