When paired with a business event, these direct GDI to the exact rule that needs to be executed.
Requirement or coding issue identified during testing.
This type of request is submitted when a change is required to GDI code.
DEV, QA, UAT, E2E, STRESS, PROD
These are scheduled to occur in GDI test environments on Tuesdays and Thursdays.
GDI Implementation approach in which the source system sends business events.
_____ date is the actual date a journal hits the ledger. If a journal begins processing on 1/24 and doesn't finish until after midnight, the date populated will be 1/25.
This PeopleSoft field represents a legal entity.
A system-assigned number that identifies the detail record's order in the GDI extract file.
Form submitted to Op Support to either alter current state GDI Code or request testing support.
Required when an Admin system needs to process a test file through the GDI test environment(s).
Differs by business event and contract type (life vs annuity). It is not source specific and should be defined with reusability in mind.
GDI process that populates fields based on values sent in the system file or based on other values determined within GDI such as account or business event. Some fields populated by this process include ATP Code and Open Item Key.
Financial information repository for Corporate Benefit Funding (CBF) Products
Date a journal is processed by PeopleSoft. If a journal begins processing on 1/24 and doesn't finish until after midnight, the date populated will be 1/24.
Location admin files are sent in order to be picked up by GDI for processing.
_____ date is the date the transaction is processed in the source system.
Organization of tables within a database: APTADMIN, IBBADMIN