Multicompany Field Translations

Hi guys - My head is spinning trying to understand how to set up the Multi-company Translations in External Company Maintenance. (lives in the Ice.IntTransIn table, I think).

  1. Do I make my receiving company (Company B) the current company, and select the parent Company A in External Company Maintenance for the translation? The help file states the translation must be on the receiving company in External Company Maintenance (child company B current). However, KB0040422 shows it as the exporting company (parent company A current).

  2. Is Inbound what is coming in from the external parent company A and database what is getting replaced in child-receiving Company B (per help), or is it the other way (per KB article)?

Help - Translations Topic:

Translations are used to remap from an incoming transaction from the external company (Inbound Value) into the current company (Database Value). The Default Value is used to specify if none is provided from the inbound document or no mapping exists.

KB0040422 :

The “Database value” field there you have to put the value you will receive.
The “Inbound Value” field there you have to put the value that will replace the one going in.

Snip…

On the Parent External Company Maintenance, when setting the translation for the Child Company (EPIC02), for Table = Part and Field = Class ID, you have to use as follow

  • Database Value = HDW (Class ID value on Child Company database)
  • Inbound Value = AKB (Class ID value on Parent Company to be used)
    ““So when the part goes in, if AKB comes up it will be replaced by HDW””

Did you ever figure this out @askulte?

My head exploded when I read the KB articles and compared them to the help.

EDIT: Nevermind, figured it out by playing around.

  1. The receiving company is where you define it.
  2. The Inbound value is what comes from the transmitting company. The database value is what you want to translate it to for the receiving company.
  3. If you want all data to come through with a certain value, then you leave the inbound value blank and only define the database value. Then you check the DefaultValue checkbox.
3 Likes

@Doug.C - Yes, exactly! Just got back from vacation (woohoo, Canada let me in!) :slight_smile:

Nice. Wanting to plan a vacation up there soon. May have to wait until the thaw next spring…

Epicor usually told us to define it in the receiving company, but also in the sending company if the data were to ever trickle back up from that child company.

So we usually always did it in pairs.

Yes, since we are doing the process both ways I set it up in both companies. I just wish there was a checkbox so it would hide the fields where translations were not defined. It would make it easier to revisit/edit the current configuration. I just use a BAQ that give s me that info so I can make sure I don’t miss anything.