Table Conversions

cglass

Member
We are taking the Table Conversions course. In the event rule, we found
that you can map the buffer fields to the fields on the JDE table through
the wizard (row insert) or by manually mapping each buffer field to its
corresponding field on the JDE Table (insert).

Is there a reason why there are two ways of doing this? Why would we
manually map the buffers to the fields on JDE's table?

_______________________________
Colin Glass
Systems Analyst Ph: (204) 474-5597
Manitoba Liquor Control Commission Fax: (204) 284-3500
[email protected]
 
Colin,

Actually there is only one way to do this wich is code !

OneWorld table conversion will always run your code !

So why do you have the automatic mapping tools ? : To help you write the code ! Everytime you do a mapping in the mapping screen it will generate a line of code in the "Event Rule" section.

A addition to this : if you want special logic to happen, then if you are familiar with code it's faster to do it in the Event Rules Screen. What I usualy do Collin is to use the automatic mapping to write my basic conversion program and then I modify the code to fit my requirements.

I hope that this help you.

Christian Audet

*** SHARED KNOWLEDGE = BETTER KNOWLEDGE ***

Implementing B7333 (Xe) SP18.1, SQL
(Support B732, B7331 and B7332)
 
Because sometimes the field names don't match so you can't automatically map them.

Dave.

David D. Helsley, Inc.
[email protected]
Xe, HPUX, Sp17.1, Oracle, TSE, Web
Xe, W2K, Sp17.1, MSSql, TSE
 
One little addition of my (other) 2¢ (Canadian ... eh):
If you decide to use the AutoMagic to modify the T/C mapping, sometime later, AFTER some ER is already in place, you'll discover the NEW line is added in ER, at the bottom; it may affect your logic!

Xe U3 SP17, Oracle 806, Citrix, HTML, FormScape 2.1 Ent RS/6000, AIX 4.2, Dep NT4
 
Back
Top