Xform / XSLT in B1if

E-invoicing in Germany: How to implement the obligation with SAP Business One

in the integration Framework for SAP Business One (B1ifare Xform and XSLT the central tools for data transformations. XSLTExtensible Stylesheet Language Transformations) is the standard by which XML messages are converted into other XML-, JSON- or transferred to text structures. Xform is the B1if's own graphical editor, which constructs XSLT transformations via drag-and-drop between source and target schemas and stores the generated XSLT code.

Context

A typical B1if flow takes an inbound message (e.g. a ZUGFeRD XML order or a Shopware JSON order), transforms it via XSLT into a B1i internal format and further into a SAP Business One DI Import XML or a Service Layer JSONXform allows you to link source and target fields, define conditions (e.g., only provide if a mandatory field is filled), build loops over rows (DocumentLines), and insert constants. The transformation runs as an atom in the scenario and benefits from variables, context data, and the BizStore. Direct XSLT writers often use the Xform editor only for the framework and finalise in the Source editor, because complex XPath expressions, templates, and parameters are difficult to map in the graphical view.

Demarcation

XSLT in B1if is not a substitute for database scripts or SQL queries; it operates on XML structures, not directly on tables. Compared to more modern format converters (e.g., JSONata, Camel Data Format), XSLT is expressive but less readable and more difficult to debug. Xform provides a pragmatic entry point but cannot map the complexity of every conceivable transformation – at a certain point, manual XSLT becomes necessary. For new developments on the BTP side, many partners switch to SAP Integration Suite with Groovy/JavaScript scripts, but retain B1if for scenarios close to the client.