ERP settings

The ERP settings page (/en/account/erp-settings). Every value here is a decision taken in your own system and cannot be derived from any invoice — which is why it has to be configured and cannot be guessed.

Five areas, one tab each

Tab	What is configured there
SAP INVOIC IDoc	partner roles for seller and buyer, qualifiers for the invoice, delivery and due dates, invoice and order number, line-item net amount, material number; the EDI_DC40 control record
UN/EDIFACT INVOIC	the qualifiers of the respective subset — EDIFACT fixes the syntax and segment identifiers, not a trading partner’s qualifiers
cXML (Ariba, SAP Business Network)	which pair of domain and identity designates a party (agreed per trading relationship)
openTRANS	the identifiers by which receiving procurement systems reconcile parties against their supplier records
DATEV document package	posting fields from the tenant’s chart of accounts (SKR03/SKR04)

“Reset” returns exactly one area to its factory settings; the other four and the segment definition stay untouched.

The error message leads here

If a SAP IDoc fails with “Invoice date (BT-2) missing”…

…the message names not only the expected qualifier but also those actually present in your file — for instance: expected IDDAT=012, present 026. It then points explicitly to this page.

There is deliberately no fallback to a second qualifier

Which IDDAT type carries the invoice date is fixed by your customising — 027, for example, is a service date. A guessed fallback would produce an invoice with the wrong date, and without any error message at all. So the qualifier is to be configured, not guessed.

Segment definition for flat-file IDocs

In a flat file a whole segment sits as one unbroken string — only the segment definition says where one field ends and the next begins. Without it, an IDoc with customer-specific Z segments cannot be read.

1. Produce it in SAP via SE37 → function module IDOCTYPE_READ_COMPLETE → save the table SEGMENT_STRUCT as a local file. The field list from WE60 works just as well.
2. Upload: a tab- or semicolon-separated file with column headings in the first row is expected; German and English headings are both recognised.
3. Validation: the file is checked before saving. If no definition can be read from it, the existing one stays untouched — a working definition is not replaced by an unusable one.
4. Verification: after the upload, the page names the segment names it can actually read.

If no definition is stored, the supplied INVOIC02 standard applies.

This surface is an Enterprise capability

The ERP formats count as ERP integrations. In the public portal they remain fully functional for everyone — trial access is the way to evaluate them. Only the volumes in bulk import are limited.