Skip to content

EDIFACT transaction code

EDIFACT SLSRPT Sales Data Report

EDIFACT SLSRPT Sales Data Report: explore its business purpose, mapping identifiers, validation tests and 2 partner references across 2 listed channels.

Standard
EDIFACT
Code
SLSRPT
Partner references
2

Implementation guide

EDIFACT SLSRPT mapping and validation

EDIFACT SLSRPT Sales Data Report is used when sales data for a period is ready. Preserve product, location and reporting period so the sales activity report in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record sales activity report

product, location and reporting period

  • Define which combination of product, location and reporting period identifies one business record, its lines and any later revision.
Update the receiving system Processing the sales activity report

ID assigned by the receiving system and processing result

  • Keep returned units separate from gross sales.
  • Replace a corrected reporting period without doubling reported revenue or units.
Check the processing result Processing status for the sales activity report

Original document reference and matching response

  • Reconcile the sales activity report with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when sales data for a period is ready. Name the operational owner of the sales activity report and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map product, location and reporting period. Confirm qualifiers, code lists, units and date/time meaning against the agreed EDIFACT version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic sales activity report data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful sales activity report processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved SLSRPT sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic sales activity report data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out sales activity report without processing it twice.

Find your trading partner for EDIFACT SLSRPT

2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where EDIFACT SLSRPT Sales Data Report appears in this catalog

The largest groups of classified SLSRPT catalog entries are in retail and e-commerce & marketplaces.

By industry

  • retail 1 channel
  • e-commerce & marketplaces 1 channel
Partner entries with the most listed channels

FAQ

EDIFACT SLSRPT questions

What is EDIFACT SLSRPT Sales Data Report used for?

SLSRPT is used when sales data for a period is ready. It carries information for the sales activity report. Match it to your business system using product, location and reporting period.

Which partners list EDIFACT SLSRPT?

The directory on this page links 2 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for EDIFACT SLSRPT?

Start with product, location and reporting period and the target sales activity report. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test SLSRPT error handling?

Keep returned units separate from gross sales. Replace a corrected reporting period without doubling reported revenue or units. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does SLSRPT relate to other EDI messages?

EDIFACT INVRPT Inventory Report is a related document linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between SLSRPT and INVRPT?

SLSRPT is used when sales data for a period is ready. INVRPT is used when inventory is reported or requested. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.