BEMIS - Content

Although most of the EDI setup data is user-definable, LN also provides all the necessary EDI data as default data. This information can be exported from the Enterprise Base Data company 050, or downloaded at http://edi.infor.com. The result is an ASCII file, called defaults.edi, that can be imported into the companies that use EDI.

defaults.edi

The defaults.edi ASCII file contains:

  • The default organization, called BEM (BEMIS message standard).

  • These EDI messages:

    ORD001Order (ORD)
    ORS001Order Acknowledgement/Response (ORS)
    ORC001Order Change (ORC)
    OCA001Order Change Acknowledgement/Response (OCA)
    MRL001Material Release (MRL)
    SHP001Shipping Schedule (SHP)
    SEQ001Sequence Shipping Schedule (SEQ)
    PUS001Pick-Up Sheet (PUS)
    ASN001Advance Shipment Notification (ASN)
    RDN001Receipt Discrepancy Notification (RDN)
    FML001Load Information to Carrier (FML)
    FMS001Carrier status information (FMS)
    INV001Invoice (INV)
    INV100Invoice (Tax on Line) (INV)
    SBI001Self Billed Invoice (SBI)
    RAD001Remittance Advice (RAD)
    ERN001Error Notification (ERN)
    STATUSMessage Status

     

  • Supported EDI messages, which is the same list as above. Almost all EDI messages are supported in both directions ( In and Out).

    The exceptions are:

    • FML001: Only Out supported
    • FMS001: Only In supported
    • SBI001: Only In supported
    • RAD001: Only In supported
    • PUS001: Only In supported
  • Outgoing messages by session. These are the same EDI messages, but now for the outgoing EDI messages a relation with the LN session is made.
  • Conversion setups for the EDI messages.

Related topics