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:

    ORD001 Order (ORD)
    ORS001 Order Acknowledgement/Response (ORS)
    ORC001 Order Change (ORC)
    OCA001 Order Change Acknowledgement/Response (OCA)
    MRL001 Material Release (MRL)
    SHP001 Shipping Schedule (SHP)
    SEQ001 Sequence Shipping Schedule (SEQ)
    PUS001 Pick-Up Sheet (PUS)
    ASN001 Advance Shipment Notification (ASN)
    RDN001 Receipt Discrepancy Notification (RDN)
    FML001 Load Information to Carrier (FML)
    FMS001 Carrier status information (FMS)
    INV001 Invoice (INV)
    INV100 Invoice (Tax on Line) (INV)
    SBI001 Self Billed Invoice (SBI)
    RAD001 Remittance Advice (RAD)
    ERN001 Error Notification (ERN)
    STATUS Message 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