Automotive EDI- ERP Integration

iCARaS can function as a stand-alone system, or it can easily be integrated to your ERP's

• Demand Processing — EDI demand is received, translated and maintained within iCARaS. An export function provides this demand to ERP/MRP for all trading partners in a common file format. A change in EDI specifications by one of your trading partners no longer means a change in your ERP system. iCARaS handles the differences in EDI formats, so you can focus on running your business. The 830, 862, 866, and 850 transaction sets are exported from iCARaS , and demand data can be updated to a sales order, manufacturing demand, or a forecasting application, based on your company’s internal business practices.

• Shared Data — iCARaS and your ERP system require separate database environments. To reduce redundant entry of key information, such as: part and address information, iCARaS supports transparent import of data from a variety of ERP systems.

• Automotive Shipping — Shipping can be performed within iCARaS or your ERP system. Shipment transactions within iCARaS can be created from requirements, from a scanning application, imported from the ERP system, or entered manually. Shipment data is captured for shipping documents and is also used to produce the 856.

• Invoicing — The Invoice can be created from shipments, manually entered, or imported from the ERP system. iCARaS is then used to transmit the Invoice. If your trading partner pays directly from the ASN, iCARaS will receive your Remittance Advice (820), which can be applied within the ERP system’s Accounts Receivable module.