Skip to content

Commit 715de8e

Browse files
committed
Update setup.md
1 parent 818ee0f commit 715de8e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,15 @@ objects, Open Registry schema objects (with its local reference data), OR Loader
2626

2727
* Execute the batch job for each configured SOR by running the following script and passing an SOR name parameter. For example: `$OR_LOADER_DIST_HOME/bin/sor-data-loader.sh HR` or `$OR_LOADER_DIST_HOME/bin/sor-data-loader.sh SIS`
2828

29-
* Verify the correctness of the entire inbound data from HR processing by examining Open Registry `PRS_*` and `PRC_*` tables.
29+
* Verify the correctness of the entire inbound data from SORs processing by examining Open Registry `PRS_*` and `PRC_*` tables.
3030

3131
## Adding additional SORs
3232

3333
Once the initial set up is completed, adding the additional SORs to the batch job configuration will require the following steps:
3434

3535
* Add `configuration` mapping block for each new SOR with an unique string `id` of that SOR to `$OR_LOADER_CONFIG_HOME/config/config.groovy`
3636

37-
* Insert a row of data for each new SOR into `prd_system_of_record` tables with `sor_id` value matching the value of the `id` in the `$OR_LOADER_CONFIG_HOME/config/config.groovy`'s `configuration` block. For example:
37+
* Insert a row of data for each new SOR into `prd_system_of_record` table with `sor_id` value matching the value of the `id` in the `$OR_LOADER_CONFIG_HOME/config/config.groovy`'s `configuration` block. For example:
3838

3939
`INSERT INTO prd_system_of_record (id, sor_id) VALUES (prd_system_of_record_seq.nextval, 'NEW_SOR');`
4040

0 commit comments

Comments
 (0)