Skip to main content
Home
  • AI Mode
  • Supply Chain Orchestration
    fast
    Supply Chain Orchestration
    • Life Sciences Company
    • Direct Material Supplier
    • Contract Manufacturer
    • Third Party Logistics
    • Wholesale Distributor
    • Healthcare Provider
    • Retail Pharmacy
  • Network
  • Products
    fast
    Products
    • Multienterprise Information Network Tower (MINT)
    • Process Orchestration for Empowered Teams (POET)
    • Track-and-Trace
  • Resources
    fast
    Resources
    • Resource Center
    • TraceLink University
    • Partners
    • Community
    • Events
  • About
    fast
    About
    • Our Story
    • Newsroom
    • Culture and Careers
    • Leadership
    • Our Values
    • Corporate Social Responsibility
    • Contact Sales
  • Log In
    • Tracelink Classic
      TraceLink Classic app.tracelink.com
      Redirect
    • Opus Platform
      Opus Platform opus.tracelink.com
      Redirect
Log In
  • Tracelink Classic
    TraceLink Classic app.tracelink.com
    Redirect
  • Opus Platform
    Opus Platform opus.tracelink.com
    Redirect
Tracelink University

Breadcrumb

  1. Home
  2. Resources
  3. TraceLink University

Order status report (IDoc)

  • Download PDF
  • Share
    • LinkedIn
    • Facebook
    • Mail
    • Twitter

Table of contents

Order Status Report, is a key communication tool used to improve visibility and coordination across the supply chain. It allows suppliers or CMOs to provide timely and structured updates to their customers or MAHs regarding the current status of open purchase orders. These updates may include confirmations that the order has been received, processed, shipped, delayed, or partially fulfilled.

By sharing order status report electronically, businesses gain significant advantages, including real-time visibility into order progress and production stages, which improves supply chain transparency. It also supports more accurate planning and forecasting, helping to prevent stockouts or excess inventory. Early identification of issues allows teams to resolve delays proactively, while consistent communication fosters stronger collaboration between CMOs and MAHs. Additionally, it enables efficient resource management across warehousing, transport, and distribution, ensures ongoing quality control and regulatory compliance, and reduces the need for manual updates, resulting in streamlined communication and fewer errors.

Order status report (IDoc)

The order status report IDoc message sends updates on the progress of an order, helping businesses track and manage their purchase orders more effectively via an IDoc basic type message.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_ORDER_STATUS_REPORT
  • IDoc Format: ORDRSP.ORDERS05
  • Transform Names:
    • SAP_IDoc_ORDRSP_ORDERS05_OrderStatusReport_IB_V1

ClosedGuidelines
Input Element Occurs Length Description Example
IDOC 1…1 - Required. IDoc root -
  @BEGIN 1…1 0/* Required. Begin of message attribute. 1
  EDI_DC40 1…1 - Required. IDoc Control record. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    TABNAM 1…1 0/* IDoc table name. EDI_DC40
    MANDT 0…1 0/3 Required. Client. 300
    DOCNUM 0…1 0/16 Required. IDoc control number mapping to fileControlNumber. 0000000134206118
    DOCREL 0…1 0/4 IDoc version release number. 720
    STATUS 0…1 0/2 Current IDoc processing status. 30
    DIRECT 0…1 0/* Direction. 1
    OUTMOD 0…1 0/1 Output mode. 2
    EXPRSS 0…1 0/1 Overriding in inbound processing. -
    TEST 0…1 0/1 Test flag. -
    CIMTYP 0…1 0/30 Required. Name of extension type. -
    IDOCTYP 1…1 0/* IDoc basic type. ORDERS05
    MESTYP 1…1 0/* Required. Logical message type. ORDRSP
    MESCOD 0…1 0/3 Logical message code. -
    MESFCT 0…1 0/3 Logical message function. -
    STD 0…1 0/1 EDI standard. X
    STDVRS 0…1 0/6 Version of EDI standard. 005010
    STDMES 0…1 0/6 EDI message type. 855
    SNDPOR 1…1 1/10 Required. Sender port. SAPERP
    SNDPRT 1…1 1/2 Required. Partner type of sender. LS
    SNDPFC 0…1 0/2 Partner function of sender. -
    SNDPRN 1…1 1/10 Required. Partner number of sender. ERPCLNT300
    SNDSAD 0…1 0/21 Sender address (SADR). -
    SNDLAD 1…1 1/70

Required. Logical address of sender. Required for TraceLink.

Identifies the IDoc sender for the TraceLink system. Must match the primary identifier value that the sender has configured for themselves in TraceLink master data.

If no party type is sent, TraceLink assumes that the value is the internal party identifier in the sender's SAP system.

Sender can also use a GLN, DUNS or any other party type standard listed in code list CL_CompanyIdentifierType.

(missing or bad snippet)

If sender identifier is a GLN or any other identifier type in code list CL_CompanyIdentifierType, the party type must be included in the SNDLAD value separated from the identifier with a colon (:) character, for example:

GLN:00123456789106

TraceLink uses SNDLAD to look up the identifier value and type in master data. If a match is not found, an error will be thrown in TraceLink.

0010136941923
    RCVPOR 1…1 1/10 Required. SAP receiver port. TRACELINK
    RCVPRT 1…1 1/2 Required. Partner type of receiver. LS
    RCVPFC 0…1 0/2 Partner function of receiver. LS
    RCVPRN 1…1 1/10 Required. Partner number of receiver. TRACELINK
    RCVSAD 0…1 0/21 Receiver address (SADR). -
    RCVLAD 1…1 1/70

Required. Logical address of receiver. Required for TraceLink.

Identifies the IDoc receiver for the TraceLink system. Must match the primary identifier value that the sender has configured for their receiver in TraceLink master data.

If no party type is sent, TraceLink assumes that the value is a party identifier for the receiver in the sender's SAP system.

Sender can also use a GLN, DUNS or any other party type standard listed in code list CL_CompanyIdentifierType.

(missing or bad snippet)

 

If the receiver identifier is a GLN or any other identifier type in code list CL_CompanyIdentifierType, the type must be included in the RCVLAD value separated from the identifier with a colon (:) character, for example:

GLN:00123456789106

TraceLink uses RCVLAD to look up the identifier value and type in master data. If a match is not found, an error will be thrown in TraceLink.

0030135941894
    CREDAT 0…1 0/8 Required. Date IDoc was created. 20110118
    CRETIM 0…1 0/6 Required. Time IDoc was created. 161010
    REFINT 0…1 0/14 Reference to interchange file. -
    REFGRP 0…1 0/14 Reference to message group. -
    REFMES 0…1 0/14 Reference to message. -
    ARCKEY 0…1 0/70 EDI archive key. -
    SERIAL 0…1 0/20 EDI/ALE: Serialization field. -
  E1EDK01 1…1 - Required. Header Record. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    ACTION 0…1 1/3

Action code for the whole EDI message. Optional.

Valid values

  • 000 - No particular action is required

  • 001 - Reverse entire document

  • 002 - Changes to order

  • 003 - Changes to one or more items

  • 004 - Changes to header and items

This field is optional and does not need to be present

000
    KZABS 0…1 0/1 Flag: order acknowledgment required. -
    CURCY 0…1 0/3 Currency. USD
    WKURS 0…1 0/12 Exchange rate. -
    BSART 0…1 0/4 Document type. ZNB
    BELNR 0…1 1/35 Required. Supplier's identifier for the sales order that generates the PO Acknowledgment. 8196733288
  E1EDK14 0…12 - Organization or Sales Document Data. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    QUALF 0…1 1/3

Required. Organization type as defined in CL_ORGID.

Valid canonical values:

  • 003 - Delivery company code

  • 004 - Plant

  • 006 - Sales division

  • 007 - Distribution channel

  • 008 - Sales organization

014
    ORGID 0…1 1/35 Required. IDOC organization. CH40
  E1EDK03 0…10 - Document or Milestone Dates and Times. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    IDDAT 1…1 1/3

Required. Qualifier for IDoc date segment as defined in CL_DateQualifierCodeEnum.

Valid values:

  • 001 = Delivery date

  • 002 = Delivery requested by date

  • 010 = Date shipped

  • 011 = Transactional date

  • 012 = Document date

012
    DATUM 1…1 1/8 Required. Date defined by IDDAT qualifier. 20251117
    UZEIT 0…1 0/6 Time associated with the date recorded. -
  E1EDKA1 1…99 -

Order status report partner identifier and address information.

The following SAP party types are currently supported by TraceLink:

  • Sold-to customer where PARTNER_Q - AG

  • Supplier/vendor where PARTNER_Q - LF

  • Ship to party where PARTNER_Q - WE

  • Bill to party where PARTNER_Q - RG

  • Carrier party where PARTNER_Q - SP

-
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    PARVW 1…1 1/3 Required. Partner type identifier. Sold-to customer partner qualifier. AG
    PARTN 0…1 1/17 Required. Sold-to customer number. 0001013694
    LIFNR 0…1 1/17 Alternate partner number. -
    NAME1 0…1 0/35 Name 1. Pharma1 Supplier
    NAME2 0…1 0/35 Name 2. -
    STRAS 0…1 0/35 Street and house number 1. 230 Houston St.
    STRS2 0…1 0/35 Street and house number 2. -
    ORT01 0…1 0/35 City. Anytown
    PSTLZ 0…1 0/9 Postal code. 97003
    LAND1 0…1 0/* Country key. US
    TELF1 0…1 0/25 Contact telephone number. -
    TELFX 0…1 0/25 Contact fax number. -
    SPRAS 0…1 0/1 Language key. E
    ANRED 0…1 0/1 Form of address. -
    HAUSN 0…1 0/15 House number. -
    REGIO 0…1 0/3 Region code. CA
    BNAME 0…1 0/35 IDoc user name. -
    PAORG 0…1 0/35 IDOC organization code. -
    ORGTX 0…1 0/30 IDoc organization code text. -
    PAGRU 0…1 0/35 IDoc group code. -
    ILNNR 0…1 0/70 International Location Number. Use to store GLN. 888888202867
    SPRAS_ISO 0…1 0/2 ISO language code. EN
    TITLE 0…1 0/15 Title. -
  E1EDK02 0…10 - Document data. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    QUALF 1…1 1/3

Required. Transaction identifier type.

Valid values:

  • 001 - Customer Purchase Order

  • 002 - Supplier sales order

  • 003- Customer inquiry

  • 004 - Supplier quotation number

  • 005 - Customer contract number

  • 006 - Supplier contract number

  • 010 - Message or document number

001
    BELNR 1…1 1/35 Required. Business document number. 8196733288
    DATUM 0…1 0/8 Document date. 20251117
    UZEIT 0…1 0/6 Document time. -
  E1EDK17 0…4 - Delivery conditions. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    QUALF 0…1 0/3

Required. IDoc qualifier for delivery conditions.

Valid values:

  • 001 - INCOTERMS part 1

  • 002 - INCOTERMS part 2

001
    LKOND 0…1 0/3 Purchase Order delivery condition code. FCA
    LKTEXT 0…1 0/70 IDOC delivery condition text. WHITBY
  E1EDK18 0…3 - Terms of payment. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    QUALF 0…1 0/3

Required. IDoc qualifier for terms of payment type.

Valid values:

  • 001 - Payment terms 1

  • 002 - Payment terms 2

  • 003 - Payment terms 3

001
    TAGE 0…1 0/8 IDOC Number of days. 14
    PRZNT 0…1 0/8 Percentage for terms of payment. 3.00
    ZTERM_TXT 0…1 0/70 Payment terms text. -
  E1EDKT1 0…99 - Free-form Text Header. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    TDID 1…1 1/4 Required. Text ID. All codes *
    TSSPRAS 0…1 0/3 Language key. E
    TSSPRAS_ISO 0…1 0/2 Language according to ISO 639. EN
    TDOBJECT 0…1 0/10 Texts: application object. VBBK
    TDOBNAME 0…1 0/70 Name. -
    E1EDKT2 0…* - Required. Free-form Text Records. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      TDLINE 1…1 1/70 Required. Text line. 49000 BETACH RIKVA
      TDFORMAT 0…1 0/2 Tag column. *
  E1EDP01 1…* - Required. E1EDP01 total order quantities. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    POSEX 1…1 1/6 Item number. 000010
    ACTION 0…1 1/3

Action to be taken at the item level of the order status report message, as defined in CL_ProcessingFunctionCode column IDoc P01-ACTION.

Valid values:

  • 001- Item added

  • 002 - Item changed

  • 003 - Item canceled

  • 004 - Item has not been changed

  • 005 - Item locked

  • 093 - Item returned

This field is optional and does not need to be present.

001
    PSTYP 0…1 1/1 Item Category. 3
    KZABS 0…1 0/1 Flag: order acknowledgment required at line item level. -
    MENGE 1…1 1/15 Required. Quantity 25.000
    MENEE 1…1 1/3 Required. Unit of measure. PCE
    BMNG2 0…1 0/15 Quantity in price unit. 25.000
    PMENE 0…1 1/3 Unit of measure for quantity in price unit. PCE
    VPREI 0…1 0/15 Unit price for product. 3560
    PEINH 0…1 0/9 Quantity basis for the unit price. 1
    NETWR 0…1 0/18 Item value (net). 89000
    NTGEW 0…1 0/18 Net weight of product at line item level. 1000
    GEWEI 0…1 1/3 Unit of measure for net weight. UN
    PREIS 0…1 0/18 Gross price for ordered product. 89000
    CURCY 0…1 0/3 Currency. USD
    MATKL 0…1 0/9 IDOC material class. ZNV
    UEPOS 0…1 0/6 Higher-level item in BOM structures. -
    BPUMN 0…1 0/6 Denominator for Conv. of Order Price Unit into Order Unit. 1
    BPUMZ 0…1 0/6 Numerator for Conversion of Order Price Unit into Order Unit. 1
    ANTLF 0…1 0/1 Single-character flag. -
    BRGEW 0…1 0/18 Gross weight for ordered product. 1100
    WERKS 0…1 0/4 Plant. CH01
    LGORT 0…1 0/4 Storage location. S001
    E1EDP02 0…10 - Required. Document data at item level. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      QUALF 1…1 1/3

Required. Transaction identifier type.

Valid values:

  • 001 - Customer Purchase Order

  • 002 - Supplier sales order

  • 003- Customer inquiry

  • 004 - Supplier quotation number

  • 005 - Customer contract number

  • 006 - Supplier contract number

  • 010 - Message or document number

001
      BELNR 1…1 1/35 Required. Business document number. 89000238
      ZEILE 0…1 0/6 Line item number. 000001
      DATUM 0…1 0/8 Document date. 20251117
      UZEIT 0…1 0/6 Document time. -
    E1EDP03 0…10 - Document or Milestone Dates and times at item level. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      IDDAT 0…1 1/3 Required. Qualifier for IDoc date segment for the order status report at line item level as defined in CL_DateQualifierCodeEnum.

Valid values:

  • 001 = Delivery date

  • 002 = Delivery requested by date

  • 010 = Date shipped

  • 011 = Transactional date

  • 012 = Document date

002
      DATUM 0…1 0/8 Required. Date defined by IDDAT qualifier. 20251117
      UZEIT 0…1 0/6 Time associated with the date recorded. -
    E1EDP20 1…* - Scheduled delivery dates and quantities. -
      @SEGMENT 1…1 1/1 Required. Begin of segment attribute. 1
      WMENG 1…1 1/15 Required. Scheduled quantity of the current item reported for delivery in order status report. 25000.000
      AMENG 0…1 0/15 Previously scheduled quantity if the quantity is changing. 0.000
      EDATU 1…1 1/8 Required. Date of delivery for the quantity schedule for delivery of the current item. 20110119
      EZEIT 0…1 0/6 Time of delivery for the quantity schedule for delivery of the current item. -
    E1EDPA1 0…8 - Ship-to partner ID and address data at line item level, generally if not present at header level. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      PARVW 0…1 0/3 Required. Ship-to partner qualifier. WE
      PARTN 0…1 0/17 Required. Partner number. -
      LIFNR 0…1 0/17 Alternate ship-to partner number. 0001013699
      NAME1 0…1 0/35 Name 1. Pharma1 Pharma
      NAME2 0…1 0/35 Name 2. Warehouse
      STRAS 0…1 0/35 Street and house number 1. 123 Victory Blvd
      STRS2 0…1 0/35 Street and house number 2. -
      ORT01 0…1 0/35 City. Newark
      PSTLZ 0…1 0/9 Postal code. 07103
      LAND1 0…1 0/* Country key. US
      TELF1 0…1 0/25 Contact telephone number. -
      TELFX 0…1 0/25 Contact fax number. -
      SPRAS 0…1 0/1 Language key. E
      ANRED 0…1 0/15 FormOfAddr. .0003
      HAUSN 0…1 0/6 House number. 123
      REGIO 0…1 0/3 Region. NJ
      BNAME 0…1 0/35 IDoc user name. -
      PAORG 0…1 0/35 IDOC organization code. -
      ORGTX 0…1 0/30 IDoc organization code text. -
      PAGRU 0…1 0/35 IDoc group code. -
      ILNNR 0…1 0/70 International Location Number. Use to store GLN. 888888202867
      SPRAS_ISO 0…1 0/2 ISO language code. EN
      TITLE 0…1 0/15 Title. -
    E1EDP19 1…5 - Required. Identifier or identifiers for ordered product in current line item. At least one material identifier must be present in E1EDP19. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      QUALF 1…1 1/5

Required. Material type qualifier as defined in CL_MaterialType.

Valid values:

  • 001 - Customer material number

  • 002- Vendor material Number

  • 003 - EAN/UPC Universal Item Number/GTIN

  • 004 - Manufacturer's product number

001
      IDTNR 1…1 1/35 Required. Customer material number. 000000000000991182
      KTEXT 0…1 0/70 Material description. SORITOL SR FCT 20MG 3X10 IL
      MFRPN 0…1 0/42 Manufacturer part number. -
      MFRNR 0…1 0/10 Manufacturer number. -
    E1EDPT1 0…* - Free-form Text Header at item level. -
      @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
      TDID 1…1 1/4 Required. Text ID. All codes *
      TSSPRAS 0…1 0/3 Language key. E
      TSSPRAS_ISO 0…1 0/2 Language according to ISO 639. EN
      TDOBJECT 0…1 0/10 Texts: application object. VBBK
      TDOBNAME 0…1 0/70 Name. -
      E1EDPT2 0…* - Required. Free-form Text Records at item level. -
        @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
        TDLINE 1…1 1/70 Required. Text line. AT LEAST 80% REMAINING SHELF LIFE
        TDFORMAT 0…1 0/2 Tag column. *
  E1EDS01 0…5 - IDoc Summary Total Quantities and Amounts. -
    @SEGMENT 1…1 0/* Required. Begin of segment attribute. 1
    SUMID 0…1 1/3

Required. Qualifier for totals segment for order status report, as defined in CL_SUMID.

Valid values:

  • 001 - Number of Items

  • 002 - Net Document Value

  • 003 - Gross Document Value

  • 004 - Total of All Quantities

001
    SUMME 0…1 0/18 Required. Total value of sum segment. 89000
    SUNIT 0…1 0/3 Total value unit for totals. USD
    WAERQ 0…1 0/3 Currency. -
ClosedExample
<ORDERS05>
    <IDOC BEGIN="1">
        <EDI_DC40 SEGMENT="1">
            <TABNAM>EDI_DC40</TABNAM>
            <MANDT>300</MANDT>
            <DOCNUM>0000000120231218</DOCNUM>
            <DOCREL>740</DOCREL>
            <STATUS>03</STATUS>
            <DIRECT>1</DIRECT>
            <OUTMOD>2</OUTMOD>
            <EXPRSS>A</EXPRSS>
            <TEST>X</TEST>
            <CIMTYP>cimtyp</CIMTYP>
            <IDOCTYP>ORDERS05</IDOCTYP>
            <MESTYP>ORDRSP</MESTYP>
            <MESCOD>COD</MESCOD>
            <MESFCT>FCT</MESFCT>
            <STD>X</STD>
            <STDVRS>005010</STDVRS>
            <STDMES>855</STDMES>
            <SNDPOR>SAPERP</SNDPOR>
            <SNDPRT>LS</SNDPRT>
            <SNDPFC>PF</SNDPFC>
            <SNDPRN>SAPERP</SNDPRN>
            <SNDSAD>A</SNDSAD>
            <SNDLAD>3520075644994</SNDLAD>
            <RCVPOR>MUNRO LTD</RCVPOR>
            <RCVPRT>LS</RCVPRT>
            <RCVPFC>LS</RCVPFC>
            <RCVPRN>MUNRO LTD</RCVPRN>
            <RCVSAD>A</RCVSAD>
            <RCVLAD>6278032738213</RCVLAD>
            <CREDAT>20231217</CREDAT>
            <CRETIM>044504</CRETIM>
            <REFINT>ICI</REFINT>
            <REFGRP>GCI</REFGRP>
            <REFMES>TCI</REFMES>
            <ARCKEY>ARI</ARCKEY>
            <SERIAL>20231218044504</SERIAL>
        </EDI_DC40>
        <E1EDK01 SEGMENT="1">
            <ACTION>003</ACTION>
            <KZABS>A</KZABS>
            <CURCY>USD</CURCY>
            <WKURS>1.00000</WKURS>
            <BSART>NB</BSART>
            <BELNR>8196733288</BELNR>            
        </E1EDK01>
        <E1EDK14 SEGMENT="1">
            <QUALF>014</QUALF>
            <ORGID>CH40</ORGID>
        </E1EDK14>
        <E1EDK03 SEGMENT="1">
            <IDDAT>002</IDDAT>
            <DATUM>20231218</DATUM>
            <UZEIT>112233</UZEIT>
        </E1EDK03>
        <E1EDKA1 SEGMENT="1">
            <PARVW>AG</PARVW>
            <PARTN>0497030300017</PARTN>
            <LIFNR>APN</LIFNR>
            <NAME1>Alpenstock Ltd</NAME1>
            <NAME2>A</NAME2>
            <STRAS>1 Bayern Strasse</STRAS>
            <STRS2>E</STRS2>
            <ORT01>Munich</ORT01>
            <PSTLZ>342525</PSTLZ>
            <LAND1>DE</LAND1>
            <TELF1>CTN42</TELF1>
            <TELFX>CFN</TELFX>
            <SPRAS>A</SPRAS>
            <ANRED>A</ANRED>
            <HAUSN>A</HAUSN>            
            <REGIO>DE</REGIO>    
            <BNAME>A</BNAME>
            <PAORG>A</PAORG>
            <ORGTX>A</ORGTX>
            <PAGRU>A</PAGRU>
            <ILNNR>A</ILNNR>
            <SPRAS_ISO>A</SPRAS_ISO>
            <TITLE>A</TITLE>
        </E1EDKA1>
        <E1EDKA1 SEGMENT="1">
            <PARVW>LF</PARVW>
            <PARTN>0495010100015</PARTN>
            <LIFNR>APN</LIFNR>
            <NAME1>MUNRO LTD</NAME1>
            <NAME2>A</NAME2>
            <STRAS>100 Queensway</STRAS>
            <STRS2>E</STRS2>
            <ORT01>London</ORT01>
            <PSTLZ>w9 1NH</PSTLZ>
            <LAND1>GB</LAND1>
            <TELF1>CTN42</TELF1>
            <TELFX>CFN</TELFX>
            <SPRAS>A</SPRAS>
            <ANRED>A</ANRED>
            <HAUSN>A</HAUSN>            
            <REGIO>GB</REGIO>    
            <BNAME>A</BNAME>
            <PAORG>A</PAORG>
            <ORGTX>A</ORGTX>
            <PAGRU>A</PAGRU>
            <ILNNR>A</ILNNR>
            <SPRAS_ISO>A</SPRAS_ISO>
            <TITLE>A</TITLE>
        </E1EDKA1>
        <E1EDKA1 SEGMENT="1">
            <PARVW>WE</PARVW>
            <PARTN>0497030300017</PARTN>
            <LIFNR>APN</LIFNR>
            <NAME1>Alpenstock Ltd</NAME1>
            <NAME2>A</NAME2>
            <STRAS>1 Bayern Strasse</STRAS>
            <STRS2>E</STRS2>
            <ORT01>Munich</ORT01>
            <PSTLZ>342525</PSTLZ>
            <LAND1>DE</LAND1>
            <TELF1>CTN42</TELF1>
            <TELFX>CFN</TELFX>
            <SPRAS>A</SPRAS>
            <ANRED>A</ANRED>
            <HAUSN>A</HAUSN>            
            <REGIO>DE</REGIO>    
            <BNAME>A</BNAME>
            <PAORG>A</PAORG>
            <ORGTX>A</ORGTX>
            <PAGRU>A</PAGRU>
            <ILNNR>A</ILNNR>
            <SPRAS_ISO>A</SPRAS_ISO>
            <TITLE>A</TITLE>
        </E1EDKA1>
        <E1EDKA1 SEGMENT="1">
            <PARVW>RG</PARVW>
            <PARTN>0497030300017</PARTN>
            <LIFNR>APN</LIFNR>
            <NAME1>Alpenstock Ltd</NAME1>
            <NAME2>A</NAME2>
            <STRAS>1 Bayern Strasse</STRAS>
            <STRS2>E</STRS2>
            <ORT01>Munich</ORT01>
            <PSTLZ>342525</PSTLZ>
            <LAND1>DE</LAND1>
            <TELF1>CTN42</TELF1>
            <TELFX>CFN</TELFX>
            <SPRAS>A</SPRAS>
            <ANRED>A</ANRED>
            <HAUSN>A</HAUSN>            
            <REGIO>DE</REGIO>    
            <BNAME>A</BNAME>
            <PAORG>A</PAORG>
            <ORGTX>A</ORGTX>
            <PAGRU>A</PAGRU>
            <ILNNR>A</ILNNR>
            <SPRAS_ISO>A</SPRAS_ISO>
            <TITLE>A</TITLE>
        </E1EDKA1>
        <E1EDKA1 SEGMENT="1">
            <PARVW>SP</PARVW>
            <PARTN>0497030300017</PARTN>
            <LIFNR>APN</LIFNR>
            <NAME1>Alpenstock Ltd</NAME1>
            <NAME2>A</NAME2>
            <STRAS>1 Bayern Strasse</STRAS>
            <STRS2>E</STRS2>
            <ORT01>Munich</ORT01>
            <PSTLZ>342525</PSTLZ>
            <LAND1>DE</LAND1>
            <TELF1>CTN42</TELF1>
            <TELFX>CFN</TELFX>
            <SPRAS>A</SPRAS>
            <ANRED>A</ANRED>
            <HAUSN>A</HAUSN>            
            <REGIO>DE</REGIO>    
            <BNAME>A</BNAME>
            <PAORG>A</PAORG>
            <ORGTX>A</ORGTX>
            <PAGRU>A</PAGRU>
            <ILNNR>A</ILNNR>
            <SPRAS_ISO>A</SPRAS_ISO>
            <TITLE>A</TITLE>
        </E1EDKA1>
        <E1EDK02 SEGMENT="1">
            <QUALF>001</QUALF>
            <BELNR>1777656478</BELNR>
            <DATUM>20231218</DATUM>
            <UZEIT>1122</UZEIT>
        </E1EDK02>
        <E1EDK17 SEGMENT="1">
            <QUALF>001</QUALF>
            <LKOND>COD</LKOND>
            <LKTEXT>COD1</LKTEXT>
        </E1EDK17>
        <E1EDK18 SEGMENT="1">
            <QUALF>001</QUALF>
            <TAGE>24</TAGE>
            <PRZNT>4</PRZNT>
            <ZTERM_TXT>desc</ZTERM_TXT>
        </E1EDK18>
        <E1EDKT1 SEGMENT="1">
            <TDID>A101</TDID>
            <TSSPRAS>E</TSSPRAS>
            <TSSPRAS_ISO>EN</TSSPRAS_ISO>
            <TDOBJECT>VBBK</TDOBJECT>
            <TDFORMAT>*</TDFORMAT>
            <E1EDKT2 SEGMENT="1">
                <TDLINE>49000 BETACH RIKVA</TDLINE>
                <TDFORMAT>*</TDFORMAT>
            </E1EDKT2>
        </E1EDKT1>
        <E1EDP01 SEGMENT="1">
            <POSEX>000010</POSEX>
            <ACTION>001</ACTION>
            <PSTYP>0</PSTYP>
            <KZABS>Y</KZABS>
            <MENGE>1000</MENGE>
            <MENEE>EA</MENEE>
            <BMNG2>1000</BMNG2>
            <PMENE>EA</PMENE>
            <VPREI>3560</VPREI>
            <PEINH>1</PEINH>
            <NETWR>89000</NETWR>
            <NTGEW>1000</NTGEW>
            <GEWEI>UN</GEWEI>
            <PREIS>89000</PREIS>
            <CURCY>USD</CURCY>
            <MATKL>ZNV</MATKL>
            <UEPOS>A</UEPOS>
            <BPUMN>A</BPUMN>
            <BPUMZ>A</BPUMZ>
            <ANTLF>A</ANTLF>
            <BRGEW>1100</BRGEW>
            <WERKS>CH01</WERKS>
            <LGORT>A</LGORT>
            <E1EDP02 SEGMENT="1">
                <QUALF>001</QUALF>
                <BELNR>1777656478</BELNR>
                <ZEILE>00010</ZEILE>
                <DATUM>20231218</DATUM>
                <UZEIT>045227</UZEIT>
            </E1EDP02>
            <E1EDP03 SEGMENT="1">
                <IDDAT>002</IDDAT>
                <DATUM>20231218</DATUM>
                <UZEIT>0452</UZEIT>
            </E1EDP03>
            <E1EDP20 SEGMENT="1">
                <WMENG>25000</WMENG>
                <AMENG>0</AMENG>
                <EDATU>20231218</EDATU>
                <EZEIT>045227</EZEIT>
            </E1EDP20>
            <E1EDPA1 SEGMENT="1">
                <PARVW>WE</PARVW>
                <PARTN>0497030300017</PARTN>
                <LIFNR>APN</LIFNR>
                <NAME1>Alpenstock Ltd</NAME1>
                <NAME2>A</NAME2>
                <STRAS>1 Bayern Strasse</STRAS>
                <STRS2>E</STRS2>
                <ORT01>Munich</ORT01>
                <PSTLZ>342525</PSTLZ>
                <LAND1>DE</LAND1>
                <TELF1>CTN42</TELF1>
                <TELFX>CFN</TELFX>                        
                <SPRAS>A</SPRAS>
                <ANRED>A</ANRED>
                <HAUSN>A</HAUSN>            
                <REGIO>DE</REGIO>    
                <BNAME>A</BNAME>
                <PAORG>A</PAORG>
                <ORGTX>A</ORGTX>
                <PAGRU>A</PAGRU>
                <ILNNR>A</ILNNR>
                <SPRAS_ISO>A</SPRAS_ISO>
                <TITLE>A</TITLE>            
            </E1EDPA1>            
            <E1EDP19 SEGMENT="1">
                <QUALF>001</QUALF>
                <IDTNR>000000000000991182</IDTNR>
                <KTEXT>SORITOL SR FCT 20MG 3X10 IL</KTEXT>
                <MFRPN>Manufacturer part number</MFRPN>
                <MFRNR>number</MFRNR>
            </E1EDP19>
            <E1EDPT1 SEGMENT="1">
                <TDID>ZOC6</TDID>
                <TSSPRAS>E</TSSPRAS>
                <TSSPRAS_ISO>EN</TSSPRAS_ISO>
                <E1EDPT2 SEGMENT="1">
                    <TDLINE>AT LEAST 80% REMAINING SHELF LIFE</TDLINE>
                    <TDFORMAT>*</TDFORMAT>
                </E1EDPT2>
            </E1EDPT1>
        </E1EDP01>
        <E1EDS01 SEGMENT="1">
            <SUMID>004</SUMID>
            <SUMME>5000</SUMME>
            <SUNIT>USD</SUNIT>
            <WAERQ>A</WAERQ>
        </E1EDS01>
    </IDOC>
</ORDERS05>
Review TraceLink's API: Terms of Use

Table of contents

Related Content
Related content
Forecast plan (IDoc)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record.
View More
Related content
Forecast plan (X12)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record.
View More
Related content
Forecast plan response (IDoc)
Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with downstream supply chain Partners without giving these Partners access to their serialization system of record.
View More

Cookie Settings

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies or similar tracking technologies. Please see below for an overview of the categories of cookies and similar technologies used on this site. You can allow or deny some of all of them, except Strictly Necessary Cookies which are required to provide the site to you. However, blocking some types of cookies may impact your experience of the site and services we are able to offer.

Please see our Cookie Policy for more details, including a list of the cookies we use. You can change your consent options at any time by following the “Cookie Settings” link in the Cookie Policy.
'Strictly Necessary' cookies let you move around the Site and use essential features like secure areas, shopping baskets and online billing. Without these cookies you would not be able to navigate between pages or use certain vital features of our Site, so we do not require your consent for their use. These cookies don't gather any information about you that could be used for marketing or remembering where you've been on the internet. For example, we use these Strictly Necessary cookies to identify you as being logged in to the Site. You can set your browser to block or alert you about these cookies, but if you do so, some parts of the Site will not work.
'Performance' cookies collect information about how you use the Site, such as which pages you visit, the time spent on the Site and if you experience any errors. We use performance cookies to provide aggregated statistics on how the Site is used and help us improve the Site including by measuring any errors that occur.
'Functional' cookies are used to provide services or to remember settings to improve your visit. We use 'Functionality' cookies to remember your settings and choices and show you when you're logged in to the Site.
‘Targeting' cookies are linked to services provided by third parties, such as 'Like' buttons and 'Share' buttons. The third party provides these services in return for recognizing that you have visited the Site. We also use 'Targeting' cookies to gather information that could be used to display content that we think may interest you.

Footer

  • Quick Links
    Get a Demo
    TraceLink Network Directory
    The Network
    OPUS Platform
    Technical Support
    Open Jobs
    API: Terms of Use
  • Products
    Multienterprise Information Network Tower
    U.S. DSCSA Compliance
    Targeted Recalls
    Process Orchestration for Empowered Teams
    Serialization
    Global Compliance
  • Resources
    Resource Center
    Events
    TraceLink University
    Partners
    Community
  • About TraceLink
    Our Story
    Newsroom
    Culture & Careers
    Leadership
    Our Values
    Corporate Social Responsibility
  • Hot Topics
    Transaction Integration
    Supply Chain Visibility
    DSCSA Compliance
    Process Orchestration
    Kazakhstan Compliance for Pharmaceuticals
    Kyrgyzstan Compliance for Pharmaceuticals
Follow Us on Social
Facebook
Linkedin
X
Legal & Trust.
© TraceLink Inc. 2009-2026 All Rights Reserved
Contact Us Today
Contact us today to begin your journey toward agentic supply chain orchestration — digitalize your end-to-end supply chain with intelligence, flexibility, and collaborative orchestration.
Contact Us
Stay Up-to-Date
Subscribe to receive industry insights and stay at the forefront of evolving trends.
Subscribe