You do not know what will not migrate until you are halfway through migrating it.
Migration projects do not usually fail on the interfaces that convert, but on the ones that do not, discovered months in and needing decisions nobody budgeted time for. Gap reports front load that discovery: the Figaf Migration Tool shows per interface what converts cleanly, what needs work and what has to be rebuilt, and in Figaf B2B Management every validation run produces a report that ranks issues by severity. Migration leads, architects and B2B teams use them to fix what is actually urgent first.
How it works
In Figaf B2B Management
Validation rules. A rules engine checks your partners, agreement templates and agreements against your naming conventions, identifier schemes, and MIG and MAG version consistency against production.
Severity tiers. Every validation run produces a report that ranks the issues it finds by severity, instead of a flat list to triage.
Before transport. Gaps are caught before the agreement is transported. When you transport B2B scenarios, Figaf also checks that all objects are valid versions: MIG and MAG drafts are stopped, and you are prompted to correct the setup before you continue the transport release.
Drafts. If you choose to keep agreement templates and agreements in draft state, you can exempt these two objects from the draft check. This increases the risk for your B2B landscape.
In the Figaf Migration Tool
Assessment of the SAP PI/PO landscape. Figaf analyzes your ICOs up front and reports what converts cleanly, what needs work and what has to be rebuilt, per interface. It also tracks message processing volumes.
Details that affect effort. The assessment includes adapter type, transport protocol and message protocol, and the parameters and lookups used in mappings, such as SOAP, REST or RFC channels and the RFC functions they call.
Rules and custom queries. You run queries with Regex or XPath across ESR and Directory content, for example to find SFTP channels with archiving enabled, and tag the objects that match. The assessment report then shows which objects have been tagged. Adding rules as you learn lets you reassess without reviewing every object.
Query the landscape and tag the objects that need attention.
Business value
Fix the urgent issues first. A report ranked by severity tells the team where to start, so time goes to the problems that matter instead of to triage.
A plan instead of an estimate. Knowing per interface what will not convert turns a rough interface count into a plan with an effort attached to each one, before you commit to a date.
Fewer surprises late in the project. Problems surface during assessment and validation, not in the middle of the migration or after a failed transport.
Consistency without relying on memory. The rules enforce your conventions on every partner, so the setup no longer depends on which specialist remembers them.
Less manual analysis. Foodstuffs South Island had spent days building their own assessment. The Figaf report gave them more detail and saved days of the project.
Validation of MIG and MAG versions in B2B transports came with release 2512. Custom queries and tagging for the PI/PO assessment came with release 2402.
