Too much data for a complete response, but here is a quick summary:
ECM Menu - Datadocks:
These are logical places or "docks" where data flows inbound or outbound like the different doors of a warehouse. BPCS and ECM are predefined. Typically an additional one is setup to represent your translator, e.g. "HARBINGER". In the database, transaction data moves from one dock to another as various processing steps occur.
Trading Partners:
These are the entities you will be sending/receiving data to/from. Just make up an id and key in the description. For example "WALMART".
Trading Partner Entities:
This is a mapping of external identifiers to internal identifiers. For example, if WALMART has stores numbered 1234500001 and 1234500002, you would create a record for each of these and key in the associated BPCS customer number and ship to number. In addition you need a base record for the customer number itself, key in the external entity as a 6 digit customer number, ex: 003215 and associate it with the BPCS customer 3215.
ECA's:
These associate a partner with a specific function (e.g. Inbound Orders or Outbound Invoices). You must associate each partner with each function that is applicable. In addition, you must associate the appropriate datadocks to the partner within that ECA. Call helpline for additional information, too much to go into regarding all of the settings and parameters here.
Inbound Order Example:
Translator should convert the inbound PO and write header information to TOHB, line information to TOLB, and a processing request for this order in TPEC. Each of these files has some key fields that need to be setup properly, but that is beyond the scope of this message.
At this point, begin running the ECM/EDM programs (option 54 on ECM menu), they will detect the new order processing request, validate the data in the files, if good post the order to BPCS, if bad errors will be logged which can be viewed in option 52.
Hope this summary helps to get you started.
