0 votes
in M3 by (13.3k points)
edited by
I have added a new master data replication in ION and I need to push all the data out in the BODs for that master data. 

MITMAS => Sync.ItemMaster BOD

2 Answers

0 votes
by (13.3k points)

Selection fields for an initial load BOD are defined in 'Initial load.Open' (EVS006). You define one master table, up to three related tables, and the fields to be used as selection fields when executing the initial load. Up to 10 selection fields can be added.

To start a new run and perform your selections, use option 11-Run.

To view the history for a specific run, use option 12-History.

Use 'Initial load job.Open' (EVS007) to carry out the selection and execution for the initial load.

Types of selection are:

- Blank value - Only records containing a blank value in the field are selected

- Specific values - Specific value or a comma separated list of values can be specified, any records containing one of these values are selected

- Range - Only records containing values within the range are selected

- Ignored - The selection field is ignored in the selection.

Press enter on the E-panel to submit the job.

Each run is saved and can be viewed afterwards in (EVS007). That is, number of initial load records, start/end time etc.

Limitation:

Only a maximum of 10 selection fields can be added.

It is not possible to use a key field as a selection field.


0 votes
by (13.3k points)

M3 CE Core: M3BODs Initial Load must use EVS006
The initial load for M3BODs was from the start only available through the M3 program ‘Initial Load.Start’(EVS005). This featured a basic, crude functionality which allowed for publishing only Show BODs and with little possibility to select what records to publish.

A new process for running initial load for M3BODs was introduced in October 2018, see KB 2013262 / NCR 10284, and April 2019, see KB 2046631 / NCR 10797. The new process is run from the M3 program ‘Initial Load. Open’ (EVS006), and features possibility to trigger either Show or Sync BODs, as well as enhanced selection criteria to decide what M3 records to publish.

Since the release, it has been possible to use either (EVS005) or (EVS006) to do an initial load for M3BODs. With this disruptive change, it will only be possible to use (EVS006).
Note The program (EVS005) will not be removed from M3 Business Engine, it will still be available to use for triggering events from an M3 table. It will just no longer be used by M3BODs to trigger an initial load of Show BODs.

Reason for the change:
The initial load using (EVS006) provides functionality to better filter what records to be published, and also functionality to publish either Show or Sync BODs.

Result of the change:
Initial load of M3BODs can only be done using (EVS006). Event Analytics Rules session 'M3BODs_InitialLoad' is removed. (Session 'M3BODs_InitialLoad' included rules for initial load from (EVS005). Rules for initial load from (EVS006) are still located in respective nouns session.)

M3 and Related Technology

A place for me to remember the answers to questions I had to dig around to find. Please feel free to add questions and answers for anything related to Infor, M3, ION, and it's sprawling family.
...