Enterprise SAP Commerce Impex Library
Professional Impex snippets for SAP Commerce development and administration
Search & Filter Snippets
Basic Catalog Creation
Create a new product catalog with staged and online versions, including default currency and language setup
Creates foundational catalog structure for product management
Advanced Catalog Synchronization
Configure advanced catalog synchronization with custom sync items, exclusions, and delta sync capabilities
Optimizes catalog synchronization performance and reliability
Classification System Setup
Create comprehensive classification system with classes, attributes, and feature assignments for product categorization
Enables structured product attribute management and filtering
Impex Library Guide
What is Impex?
Impex (Import/Export) is SAP Commerce's powerful data import and export mechanism using CSV-like syntax for creating, updating, and managing commerce data efficiently across all system components.
Safety Notice
Always test Impex scripts in development environment before production use. Review prerequisites carefully and backup your data. Use proper parameters and validate syntax before execution.
Parameter Configuration
Configure parameters to customize the Impex snippet for your specific SAP Commerce setup and requirements. Parameters help make snippets reusable and environment-specific.
Enterprise SAP Commerce Impex Library
Professional Impex snippets for SAP Commerce development and administration
Features
- Curated library of ready-to-use ImpEx snippets organised by SAP Commerce subject area (Catalog, Product, User, Order, CMS, Price, System Configuration, Integration, Workflow, Security)
- Each snippet ships with the full ImpEx file body, a plain-English description of what it does, the SAP Commerce versions known to work (6.7 through 2211), and the platform modules it depends on
- Difficulty + risk-level metadata on every snippet — pick "Beginner / Low Risk" examples to learn the syntax, or "Expert / Critical" templates only after reviewing rollback procedures with your team
- Faceted filter panel: search by free text, category, difficulty, risk, or SAP version simultaneously; the visible list narrows live as you tighten constraints
- One-click "Copy to clipboard" for the entire ImpEx body — paste straight into HAC or a deploy pipeline
- Favourites + recently-viewed snippets persist in localStorage so common workflows stay one click away across sessions
- Snippet detail pages render the ImpEx with header alignment, inline notes for every line, and the original "why this exists" context that flat code-dumps omit
- Pure client-side library: the snippet corpus ships in the JS bundle, no server lookups, no telemetry on which snippets you view
How to use
- Pick a category from the sidebar (e.g. Catalog Management) — the visible snippet list narrows to that area.
- Optionally narrow further by difficulty (start with Beginner) or by your target SAP Commerce version.
- Open a snippet card to see the full ImpEx body, version compatibility, module requirements, and the explanation of what each block does.
- Read the risk-level note and the "Required modules" section before copying anything destined for production.
- Click Copy to grab the ImpEx body. Paste into HAC → ImpEx → Import, set the encoding (usually UTF-8), and execute against a dev environment first.
- Star a snippet to add it to Favourites for quick recall on your next task.
Tips & Best Practices
- Bookmark the snippet detail page for any ImpEx you reuse weekly — the URL contains the snippet id and survives library updates.
- Use the Beginner / Low Risk filter combination when teaching ImpEx to new team members; it surfaces snippets where the syntax is the focus rather than dangerous side effects.
- Before running any snippet in production, paste it into the SAP Commerce ImpEx Formatter tool on this site to align headers and spot subtle typos.
- Pair this library with the SAP Commerce ImpEx Converter to round-trip a real export into JSON for diffing.
- Critical-risk snippets are not "broken" — they are powerful operations (cascading deletes, type-system mutations) that need extra review. They live in the library so you can study them; don't treat them as ready-to-run.
FAQ
What is an ImpEx snippet?
In SAP Commerce, ImpEx is the bulk-import language used to load or modify type-system data — products, catalogs, users, CMS items, system config. A snippet is a small, self-contained ImpEx file that performs one specific operation (create a category, link a product to a catalog, etc.) and is meant to be copied, parameterised, and run.
How are the difficulty and risk levels assigned?
Difficulty reflects the SAP Commerce knowledge required to understand the snippet — Beginner needs only base ImpEx syntax, Expert needs deep awareness of type relationships, JaloSession, or integration layer behaviour. Risk reflects what the snippet can do to live data: Low = inserts new rows only; Critical = deletes/updates that can cascade or break referential integrity.
Why do snippets list specific SAP Commerce versions?
Type-system definitions and required attributes change between releases — e.g. some attributes added in 1905 don't exist in 6.7, and 2211 deprecated certain integration patterns. Each snippet declares the versions where its column set matches the platform schema, so you don't spend an afternoon debugging a "missing attribute" error caused by a version skew.
What does "Required modules" mean?
SAP Commerce ships as a set of optional extensions; a snippet targeting CMS items needs the `cms2` extension, a price-rule snippet needs `europe1`, etc. The required-modules list tells you whether the snippet will work on your project's extension list, or whether you need to add an extension to localextensions.xml first.
Is the ImpEx safe to run as-is?
Treat every snippet as a template, not a deploy artifact. Sample data (catalog version names, codes, IDs, prices) will need to be replaced with your real values. Run against a dev or staging environment first. For Risk: High or Critical snippets, plan for rollback (a reverse ImpEx, a DB snapshot, or scheduled maintenance).
Where do these snippets come from?
They are distilled from SAP Commerce documentation, common platform onboarding tasks, and patterns the community has used to load reference data. Each one has been hand-reviewed for syntax accuracy against the named version range; we don't auto-generate snippets.
Can I add my own snippets to the library?
Not from the UI — favourites are local-only. If you have a snippet you think belongs in the public library, open a GitHub issue with the ImpEx body, version range, and a short description; the library is community-maintained.
Does the library send anything to a server?
No. The full snippet corpus, metadata, and your favourites all stay in your browser. The "Copy to clipboard" action uses navigator.clipboard, and the version-compatibility filter runs client-side. DevTools Network shows no requests when you browse or copy snippets.