Internet Sellout

Demand Unearned Rewards

Service Connect for PLM to Epicor

General Process

  1. A scheduled process retrieves Arena csv files, copies them to an archive, and pushes them, reordered by renaming, into Service Connect input folder. The reordering is done so that items in BOMs are done before the BOMs that contain them.
  2. Certain defined criteria may cause any Level 0 Part processing to be aborted. No email sent.
  3. It may be desirable that Level 0 Part with Alt Methods processing be aborted and Email sent. There would be no change made to Epicor data for that part. This depends on the use of Alt Methods -  for the client to determine in advance.
  4. Parts at Level 1 for a Level 0 Kit or Manufactured part are ‘quick created’ inactive with no revision so we can get them onto a BOM. We are assuming that this is only because things are slightly out of sequence and the full info as a Level 0 in a CSV  will be forth coming. Idealy this should never happen.
    1. Quick created parts need to have the Sites and Warehouses done manually even if a level 0 comes soon after.
  5. Part and PartRev are Inserted or Updated
    1. See incoming file section below.
    2. Epicor Erp.Part and Erp.PartRev should be is time stamped to indicate when the last ESC Batch touched this part.
  6. The first time a Level 0 is created
    1. Determine if the part should be inactive - for the client to determine criteria in advance.
    2. All the Part’s Sites and Warehouses will be created.
      1. Warehouses with predetermined criteria, either a flag or by naming convention, will be set as the default warehouse and a bin, either a flag or by naming convention, will be set as the Primary Bin for that warehouse
  7. If the Source Type changes the Buyer or Planner in the Sites will be reset.
  8. Approved Manufacturer
    1. Non Existing Manufacturers are added and descriptions are updated. The ID from Arena is used as the key.
    2. Existing Manufacturer’s part numbers are all removed and then added.
  9. Engineering Workbench
    1. Level 0 part - All material is removed, every time.
    2. Engineering Workbench for Level 0 parts with BOMs and are not Purchased (If no source type is specified, Purchased is the default)
      1. Level 1 part material is added to the BOM of the Level 0 part
        1. View As Assembly is Checked if Part Type is M
        2. Pull As Assembly is Checked if Part Type is M and Non Stock
    3. Ops are not added (if this is not desired there is a lot more discovery and work to determine how this should be done).
  10. Email is sent

Incoming file

  1. Level
    1. Level 0 is expected to have all data
    2. Level 1 is not complete data and is used only for ‘Quick Create’ and Engineering Workbench
  2. item_number
    1. Add if not exists.
  3. revision
    1. Add if not exists.
  4. item_name
    1. Update in the Part: PartDescription and the PartRev: RevDescription
  5. MaterialSequence
    1. if not supplied then automatically generated for Engineering Workbench
  6. unit_of_measure
    1. Part: IUM, PUM, SalesUM, UOMClassID
  7. serialized_mask
  8. prodcode
  9. classid
  10. TaxCatID
  11. RevShortDesc
  12. MtlBurnRate
  13. DaysOfSupply
  14. ECOGroup
  15. HTS
  16. ScheduleB
  17. ECCN
  18. change_number
    1. PartRev: ECO
  19. material_effectivity_date
    1. PartRev: Effective Date (only on new revision because the Arena value is the date of any ECO change)
  20. source_type
    1. P, M or K
  21. NonStock
  22. QuantityBearing
  23. gross_weight
  24. dimensions
  25. SystemABC
  26. ManualABC
  27. manufacturer_x
    1. Manufacturer: Name
  28. manufacturer_code_x
    1. Manufacturer: MfgID
  29. manufacturer_item_x
    1. PartXRefMfg: MfgPartNum
  30. line_number
  31. quantity
    1. Material Quantity on BOM (if 0, part not added)
  32. reference_designator
  33. bom_notes

These fields are defined by Arena and an XSL Template arena_xml_to_csv.xslt that is part of the ERP-EXCHANGE process

https://www.arenasolutions.com/pdfs/products/plm/Arena_ERP_Integration.pdf