Menu
  • Electronic Data Interchange (EDI) Option test
    • Electronic Data Interchange (EDI) is typically implemented by medium to large suppliers. Through EDI, electronic documents and business data is transferred from Mead Johnson to your company without human intervention (our SAP system talks directly to your SAP system).

      The primary application of Mead Johnson's EDI will be the distribution of purchase orders, purchase order acceptance, purchase order changes, invoicing and invoice rejections. By utilizing EDI, suppliers:

      • Improve data accuracy
      • Reduce technical complexity by using standardized data formats
      • Reduce the need for paper transactions
      • Accelerate information exchange within order processing

      For suppliers with existing EDI capability, Mead Johnson will use EDI ANSI X12 version 4030.

      Related Technical Information

      Standards Supported

      UCS and X12 - All versions up to 5010

      Communications Qualifier: 01

      Communications ID (ISA & GS): 006370092

      Duns Number: 006370092

      Test ID: 006370092T

      Contacts

      mjnsourcing@mjn.com

      Transport

      Protocol: HTTP

      Assigned Port Number: 8080

      Production AS2 Name (routing ID): meadjohnson

      Production Address (URL): http://b2b.mjn.com:8080/bcgreceiver/receive

      Proxy IP: TDB

      Test AS2 Name (routing ID): meadjohnsontest

      Test Address (URL): http://b2btest.mjn.com:8080/bcgreceiver/receive

      Proxy IP: 74.119.122.129

      Security

      Sign documents: YES

      Request acknowledgement of documents: YES

      Request signed acknowledgement: YES

      Synchronous acknowledgement: YES

      Message Digest: SHA1

      Encrypt documents: YES

      Document encryptions: Triple DES

      Encryption key length: 256

      AS2 Client Software

      Web Sphere Partner Gateway 6.2

      Business Transaction ANSI X12 Message Direction Special Notes
      New Purchase Order 850 (Version 4030) Outbound from MJN Does not support Service PO's. Use Supplier Portal for Service PO.
      Change Purchase Order 860 (Version 4030) Outbound from MJN Does not support Service PO's. Use Supplier Portal for Service PO.
      Purchase Order Agreement 855 (Version 4030) Inbound to MJN Does not support Service PO's. Use Supplier Portal for Service PO.
      Advance Shipment Notification 856 (Version 4030) Inbound to MJN Only in scope for suppliers supporting Direct Procurement. Not in scope for Indirect Procurement Suppliers.
      Delivery Forecast and Schedule 830/862 (Version 4030) Outbound from MJN Only in scope for suppliers supporting Direct Procurement. Not in scope for Indirect Procurement Suppliers.
      Invoice/Credit Memo 810 (Version 4030) Inbound to MJN
      Invoice Rejection Notification 824 (Version 4030) Outbound from MJN Text type of message sent back to supplier for Invoices that have been rejected with the reason.
  • Supplier Portal Option
  • Email Option
    • Companies that either have a lower volume of transactions or are not using EDI or the Suppliers Portal can take advantage of the new Email Option. Using the Email Option, suppliers can receive new and modified purchase orders via email. The Email Option will allow suppliers to:

      • Receive purchase order document in PDF format via email
      • Email paper invoice to Mead Johnson
      • Use email as a temporary solution when other systems such as EDI or the Supplier Portal they typically use are not available
  • eSourcing
    • Mead Johnson procurement will use eSourcing to facilitate electronic Bidding and electronic Contract Negotiations. Open to all suppliers, eSourcing requires access to email and the Internet. Through eSourcing, suppliers can:

      • Receive and respond to electronic RFI, RFP, RFQ
      • Participate in online auctions
      • Access and collaborate on MJN contracts (including version control through a checkout/check-in process)