972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Communications

EDI 159 Motion Picture Booking Confirmation

The X12 document used to confirm motion picture business terms, conditions and licensing information from distributor to exhibitor.

Sent by
Film distributor
Received by
Exhibitor (cinema operator)
Standard
ANSI ASC X12

What is an EDI 159?

The EDI 159 Motion Picture Booking Confirmation is the ANSI X12 transaction set used to confirm motion picture business terms, conditions and licensing agreement information from the distributor to the exhibitor.

When a cinema books a film, the distributor and exhibitor agree which screens will show it, for how long and on what financial terms, such as revenue share percentages. A confirmation as data lets the exhibitor's booking and settlement systems apply the agreed terms when calculating film rental. Terms may change during the run.

How the EDI 159 worksDiagram of the EDI 159 Motion Picture Booking Confirmation. Film distributor sends it to exhibitor (cinema operator). It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), N1 (Party Identification) and the required LX loop with LX (Transaction Set Line Number), REF (Reference Information) and the required THE loop with THE (Screen Theater Identification) and the required DTP loop with DTP (Date or Time or Period). 2 optional loops are listed by their first segment.How the EDI 159 worksMotion Picture Booking Confirmation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 159SENDERFilm distributorRECEIVERExhibitor (cinemaoperator)997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MPGS … GETransaction set 159ST … SEHEADINGBGNBeginning SegmentN1Party IdentificationRequired loop LX · repeats many timesLXTransaction Set Line NumberREFReference InformationRequired loop THE · repeats many timesTHEScreen Theater IdentificationRequired loop DTP · repeats many timesDTPDate or Time or Period+ 2 optional loops, starting with:N9G63Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 159. Your trading partner's implementation guide adds its own requirements.
How the EDI 159 worksDiagram of the EDI 159 Motion Picture Booking Confirmation. Film distributor sends it to exhibitor (cinema operator). It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), N1 (Party Identification) and the required LX loop with LX (Transaction Set Line Number), REF (Reference Information) and the required THE loop with THE (Screen Theater Identification) and the required DTP loop with DTP (Date or Time or Period). 2 optional loops are listed by their first segment.How the EDI 159 worksMotion Picture Booking Confirmation: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 159SENDERFilm distributorRECEIVERExhibitor(cinemaoperator)997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MP (GS … GE)Transaction set 159 (ST … SE)HEADINGBGNBeginning SegmentN1Party Identification+ required LX (LX) and 2 optional loops,starting with:N9G63Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 159. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 159, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 159 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Confirming film bookings with cinemas
  • Confirming licensing terms and revenue shares
  • Updating bookings when runs are extended

Where it fits in the document flow

This document 159 Motion Picture Booking Confirmation
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 159 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • N1
  • LX
  • REF
  • THE
  • DTP
  • N9
  • G63
  • SE

Practical example

The 159 in practice

A cinema chain books a new release in 40 locations. The distributor sends a 159 confirming the release date, the locations, the minimum run and the revenue share terms by week. The chain's systems load the terms and use them for weekly film rental settlements.

Implementation

Implementation considerations for the 159

  • Confirm terms for every location and screen booked.
  • Update confirmations when runs are extended or ended.
  • Reconcile terms with settlement calculations.
  • Protect commercially sensitive booking terms.

How ECOM helps

Automate the 159 with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related communications documents

All 16 communications documents

Need help with the EDI 159?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us