SAP S/4HANA implementation skill covering module selection (CO, SD, PS, FI, HCM), SAP Activate methodology, fit-to-standard workshops, multi-country localization, intercompany configuration, and professional services industry patterns. Use whenever the user mentions SAP, S/4HANA, SAP implementation, fit-to-standard, SAP modules, SAP localization, SAP migration, ERP implementation, or needs guidance on SAP configuration for IT services companies. Also trigger for SAP-specific gap analysis, SAP scope definition, SAP best practices, CATS integration, Strangler Fig migration, Activity Type configuration, or revenue recognition patterns for T&M, fixed price, retainer, or managed services contracts. Trigger: SAP implementation, S/4HANA configuration, fit-to-standard, SAP modules, SAP localization, CATS integration, Strangler Fig, Activity Types, revenue recognition.
From maonpx claudepluginhub javimontano/mao-discovery-frameworkThis skill is limited to using the following tools:
evals/eval-result-1.mdevals/evals.jsonreferences/henka-adrs-and-pocs.mdreferences/sap-activate-and-localization.mdEnables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
"Fit-to-Standard is not about bending the business to SAP — it's about finding where SAP already solved the problem."
Guide SAP S/4HANA Public Cloud implementations for IT services companies. Covers module configuration, SAP Activate methodology, fit-to-standard workshops, multi-country localization, intercompany billing, incremental data migration (Strangler Fig), timesheet integration (external frontend + CATS API), and revenue recognition across multiple service variants.
For project-specific ADRs, PoCs, and sandbox validation:
references/henka-adrs-and-pocs.mdFor SAP Activate phases and localization checklists:references/sap-activate-and-localization.md
Key Objects for IT Services:
Decision Tree — Which CO Object?
What are you tracking?
|-- Recurring departmental costs -> Cost Center
|-- Revenue AND cost for a business unit -> Profit Center
|-- A specific time-bound initiative -> Internal Order
|-- Hours worked at a certain skill level -> Activity Type
|-- An external client deliverable -> WBS Element (PS)
Activity Type Configuration: Activity Types map skill levels to Cost Rates and Sales Prices. Each AT has:
See sofka-regional-finance skill for CTC formulas and AT rate tables.
Decision Tree — Which Document Type?
What kind of engagement?
|-- Client pays per hour worked -> Sales Order (T&M)
|-- Client pays on milestones -> Sales Order + Milestone Billing Plan
|-- Client pays fixed monthly -> Sales Order + Periodic Billing
|-- Client pays per ticket/SLA -> Service Contract
| Model | SAP Config | Revenue Recognition |
|---|---|---|
| Time & Materials | Sales order + timesheet confirmation | Hours x Rate per period |
| Fixed Price | Sales order + milestone billing plan | PoC or milestone-based |
| Retainer | Sales order + periodic billing | Monthly straight-line |
| Managed Services | Service contract + SLA monitoring | Per-period or per-ticket |
IT services companies typically have multiple billing models. Each requires distinct SAP config:
| Variant | SAP Config | Recognition Pattern | Notes |
|---|---|---|---|
| T&M Fixed Hours | Timesheet x Sales Price per AT. Scope 1IL. | Over time: monthly on hours confirmed | Most common for staffing |
| T&M Variable | Same + FX conversion, volume tiers | Over time: monthly, variable | Cross-border scenarios |
| Fixed Price | Milestone Billing Plan in SD. PoC. | Over time: % completion | Requires proper milestone design |
| Cost-Only (Bench) | Internal Orders in CO. No SD. | N/A — cost tracking only | No revenue recognition needed |
Decision Tree:
Revenue-generating contract?
|-- NO -> Internal Order (CO only). Bench/training.
|-- YES: Pricing per hour?
|-- YES: Fixed hours/month? -> T&M fixed. Variable? -> T&M variable.
|-- NO: Per milestone? -> Fixed Price. Monthly fee? -> Retainer.
| Dimension | 1 (Low) | 3 (Medium) | 5 (High) |
|---|---|---|---|
| Effort | < 3 days | 1-2 weeks | > 2 weeks |
| Risk | No dependencies | Some | Critical path |
| Upgrade Impact | None | Key user ext. | Custom ABAP |
| Business Value | Nice to have | Important | Must have |
Score = Effort + Risk + Upgrade Impact - Business Value. Lower = higher priority.
| Gap Type | Score | Recommendation |
|---|---|---|
| Fit | 0 | Use standard |
| Configure | 2-4 | Preferred |
| Extend | 5-8 | Acceptable with justification |
| Custom | 9-12 | Avoid — redesign process |
| Workaround | 3-6 | Assess change management effort |
1. Sending entity: Employee works, confirms hours
2. Sending entity: Cost posted (Dr Labor Cost, Cr Payroll Accrual)
3. Sending entity: IC billing (Dr IC Receivable, Cr IC Revenue)
- IC Price = CTC Cost Rate x (1 + markup %)
4. Receiving entity: IC posting (Dr IC Cost, Cr IC Payable)
- FX conversion at transaction date rate (IAS 21)
5. Receiving entity: Bills end client (Dr AR, Cr Revenue)
6. Month-end: IC clearing + FX revaluation
7. TP documentation attached to postings
| Account | Sending Entity | Receiving Entity | Purpose |
|---|---|---|---|
| IC Receivable | Balance sheet | — | Claim on receiving entity |
| IC Payable | — | Balance sheet | Obligation to sending |
| IC Revenue | P&L | — | Markup income |
| IC Cost | — | P&L | Intercompany cost |
| FX Gain/Loss | P&L | P&L | IAS 21 revaluation |
Instead of big-bang migration, eliminate legacy Excel/tools incrementally. SAP takes over one data domain at a time.
| Priority | Source | Data Domain | SAP Target | Risk |
|---|---|---|---|---|
| 1 (MVP) | Revenue tracking | Hours, rates, recognition | SD + CO + FI-RA | High |
| 2 (MVP) | Cost rate source | Cost per resource | CO (Manage Cost Rates) | High (key person) |
| 3 (MVP) | Staffing allocation | Resource-project mapping | PS (WBS assignments) | Medium |
| 4 | Validation/BI | Reporting | Analytics Cloud | Low |
| 5+ | Remaining tools | Various | Phase 2+ | TBD |
When employees already use an established timesheet tool, forcing migration to SAP's native Manage My Timesheet risks adoption resistance. Instead, preserve the familiar frontend and integrate with SAP backend via CATS BAPI.
[External Timesheet Frontend] --REST/JSON--> [SAP CPI/BTP]
--CATS BAPI--> [SAP S/4HANA]
--> PS (hours) + CO (cost allocation) + SD (billing trigger)
| Error | Response | Resolution |
|---|---|---|
| Invalid WBS/Project | Rejection | User corrects in frontend |
| Inactive Activity Type | Rejection | Admin activates for period |
| Hours exceed threshold | Warning/rejection | PM override or correction |
| API timeout | No response | Retry queue with alerting |
| Employee not assigned | Rejection | PM assigns in PS first |
| Risk | Impact | Mitigation |
|---|---|---|
| Master data quality | High | Data cleansing sprint per source |
| Blended rate (no cost/price split) | High | CTC formula automation; Activity Types |
| Intercompany model undefined | High | Cost-Plus proposal; tax advisor validation |
| External timesheet delayed | High | Fallback to native Manage My Timesheet |
| Multi-currency rounding | Medium | Rounding rules upfront; test with real data |
| Key person dependency on cost calc | High | Document formula; automate in SAP |
| Parallel ERP/system implementation | Medium | Coordinate touchpoints and release calendars |
| User adoption resistance | High | Change management + keep familiar frontend |
XX_Gap_Analysis_SAP_Deep.htmlXX_Roadmap_SAP_Deep.html