Skip to content

SAP reference for sell-in

This reference translates the current public Community/Enterprise contracts. The legacy planning-* codebase is not a mapping authority; confirm final availability in the deployed edition and OpenAPI.

This page complements the sell-in contract. In SAP, sell-in is an interpretation of a point in the commercial flow, not the name of one table. Before mapping it, choose whether occurrence is recognized at billing or at the physical goods issue and use the same rule throughout the history.

Nearby SAP sources

Chosen event Common SAP tables Possible reference date Possible quantity
customer billing VBRK and VBRP billing date FKDAT billed quantity FKIMG
delivery or physical goods issue LIKP and LIPS actual goods movement date WADAT_IST delivered quantity LFIMG

Do not combine a billing date with a delivery quantity in the same series without explicit reconciliation. Cancellations, returns, and credit memos must also follow the source policy.

Field mapping

OpsFactor Nearby SAP field Note
documentId VBELN + POSNR from the chosen document Identifies a billing or delivery item for transactional loads
referenceDate FKDAT or WADAT_IST Choose one date meaning
originLocationId plant WERKS and, when needed, storage location LGORT The composition must resolve to an existing OpsFactor location
destinationLocationId customer or recipient, such as KUNNR or a ship-to partner Define which partner represents the planned destination
materialId MATNR Preserve leading zeroes when they belong to the integrated code
quantity FKIMG or LFIMG Use the quantity that matches the chosen event
uomId corresponding sales or delivery unit Map to a registered, convertible unit
totalValue NETWR or a reconciled document value Document gross/net meaning, currency, and tax treatment

What to place in documentId

If each SAP item is loaded separately, use a stable composition such as 0090012345-000010, preserving the leading zeroes in VBELN and POSNR.

If the extract already consolidates values by day, load one row for each date, origin, destination, material, and unit. For example:

2026-05-31|DC-01|CUSTOMER-07|MAT-001

Include unit, channel, or another dimension in the ID when it separates rows. The complete rule is in Identifiers and periodicity.

Nearby SAP transactions

  • VF03: display billing document;
  • VL03N: display delivery;
  • billing or delivery analytical reports and apps may be better sources than direct table reads in SAP S/4HANA.

These transactions help reconcile examples, but they do not define the extraction contract by themselves.

Return to sell-in or the SAP index.