My Oracle Support Banner

EGL9.2: Rows Process By 1st Mass Change Rule Not Picked Up By 2nd Rule. (Doc ID 2016739.1)

Last updated on AUGUST 24, 2021

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


There are mass change rules and  group applied to the edit and post before processing the FAH journals in PSFT.
The mass change does not seem to trigger for all the chart fields but only one.

Expect Behaviour
Process apply Mass Change rules ( by chartfield) one by one and update all applicable rows.

Replication Step
1. Set up 2 Mass Change Rules on page General Ledger > External System Integration > Mass Change Rules Definition
  -1st rule on Chartfield ACCOUNT
  - 2nd rule on chartfield DEPTID
2. Set up Mass Change Group
3. Run 3rd party Integration process GL_FAIJEDIT
4. Verify data and trace and note below
  - Any row that is processed for the 1st rule (ACCOUNT) will not be picked up by 2nd rule, although the data satisfy the 2nd rule on DEPTID.
  - This is because at (GL_FAIJCFCHG.RuleRun.RuleSeq) (SQL), process set CF_MCHG_GROUP, CF_MCHG_RULE to values at its first encounter.
  - At next encounters, process is checking CF_MCHG_GROUP, CF_MCHG_RULE field as blank in where clause which gives not rows for any other chartfield.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.