Understanding NFC Processing
The NFC processes payroll for the majority of U.S. civilian federal government employees. This population consists of approximately 600,000 individuals. Consequently, the NFC and its federal customers generate a high volume of human resources transactions each day. The NFC SINQ Import process enables you to upload the daily SINQ transaction file from NFC. Positions, job codes and personnel actions are identified and marked as SINQed (for example, failed). The last operator (OPRID) who updated the SINQ row is notified to correct transactions in the PeopleSoft Human Resources system.
Note: Oracle PeopleSoft delivers Notification Composer Framework to manage the setup and administration of all notifications in one central location.
Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications.
Notifications delivered with HCM Image 48 or later must use Notification Composer.
For more information about Notification Composer Framework, see Understanding Notification Composer.
Additionally, the NFC SINQ Import process:
Automates the assignment of errors to human resources personnel in your agency.
Enables human resource personnel to view and change transaction status.
Field or Control |
Description |
|---|---|
National Finance Center (NFC) |
Part of the U.S. Department of Agriculture that provides payroll services to more than 600,000 federal employees. |
Personnel Action Processing System (PACT) |
NFC's online system for entering personnel actions into the payroll and personnel databases. |
Personnel Management System (PMSO) |
NFC's online system used for creating, editing, inactivating, reactivating or deleting individual (position) and primary (jobcode) data. Position data must be entered into PMSO before personnel data can be entered into PACT. |
Personnel Edit Subsytem (PINE) |
NFC's system that combines PACT and PMSO data and processes edits against the submitted personnel and position transactions. PACT and PMSO transactions must pass PINE edits before they are processed through NFC's Personnel Processing System (PEPL) to update the Payroll/Personnel System database (PPS). PINE processes Monday through Friday of each week, and the first Saturday of the pay period. |
Suspense Inquiry and Correction System (SINQ). |
Position (PMSO) and personnel (PACT) transactions that do not pass PINE edits are placed in the this system. |
This diagram shows the process flow for the SINQ Import process. The process is similar for PACT and PMSO except that different tables are used. For both PACT and PMSO, the batch process loads data into a temporary table, validates the data, prepares to move the data into an application table, updates the NFC update indicator field, and notifies the last update user:
This table describes the NFC PACT import file layout supported by the SINQ import process. A sample import file, fgnfcpinesinq.dat, is delivered under your product data directory.
|
Field Name |
Start Position |
Length |
Field Type |
Description |
|---|---|---|---|---|
|
ERR_SSN_NO |
1 |
9 |
Char |
Employee SSN (no dashes) |
|
ERR_SUBAGENCY |
10 |
2 |
Char |
NFC agency (sub) code (that is, 70, 71) |
|
ERR_POI |
12 |
4 |
Char |
Agency Personnel Office Identifier |
|
ERR_COMPANY |
16 |
2 |
Char |
Company Cd |
|
ERR_DOC_TYPE |
18 |
3 |
Char |
NFC doc type (action) |
|
ERR_PAY_PERIOD |
21 |
2 |
Char |
Pay period that action was processed in. |
|
ERR_AUTH_DATE |
23 |
6 |
Num |
Date action was authorized |
|
GVT_STATUS_TYPE |
29 |
3 |
Char |
NFC nature of action code (denotes correction or cancellation of action) CAN = 001, COR = 002 |
|
GVT_NOA_CODE |
32 |
3 |
Char |
NFC nature of action code (type of action) |
|
ERR_EFFDT |
35 |
6 |
Num |
Date action was effective (month) |
|
ERR_BATCH_NO |
41 |
4 |
Char |
NFC batch processing identifier |
|
ERR_OPER_CODE |
45 |
7 |
Char |
HR specialist (id) submitting the action |
|
ERR_CODE |
52 |
3 |
Char |
NFC error code |
|
ERR_MSG |
55 |
50 |
Char |
NFC error message |
This table describes the NFC PMSO import file layout supported by the SINQ import process. A sample import file, fgnfcpmsosinq.dat, is delivered under your product data directory.
|
Field Name |
Start Posn |
Length |
Field Type |
Description |
|---|---|---|---|---|
|
SUSP_OPER_CD |
1 |
7 |
Char |
HR specialist (id) submitting the action |
|
SUSP_MAST_INDV |
8 |
4 |
Char |
"MSTR" if job code action / "INDV" if position action |
|
SUSP_FUNCTION_CD |
12 |
10 |
Char |
Type of action performed (for example, CHANGE, ADD, and so forth) |
|
SUSP_COMPANY |
22 |
2 |
Char |
Company Cd |
|
SUSP_SUBAGCY |
24 |
2 |
Char |
NFC agency (sub) code (for example, 70, 71, and so forth) |
|
SUSP_POI |
26 |
4 |
Char |
Agency Personnel Office Identifier Example: POI 1536 for Smithsonian |
|
SUSP_JOBCODE |
30 |
6 |
Num |
Jobcode |
|
SUSP_GRADE |
36 |
2 |
Num |
Pay grade level of position/job code |
|
SUSP_POSITION_NBR |
38 |
8 |
Num |
Position Number |
|
SUSP_INCUM-SSN |
46 |
9 |
Char |
SSN of current or last employee holding position |
|
SUSP_OBLIG-SSN |
55 |
9 |
Char |
SSN of new hire employee filling position |
|
SUSP_PAY_PERIOD |
64 |
2 |
Num |
Pay period that action was processed in |
|
SUSP_PASS_NUM |
66 |
2 |
Num |
NFC processing sequence within pay period (1, 2, 3, and so forth) |
|
SUSP_ERR_CD |
68 |
3 |
Num |
NFC error code |
|
SUSP_ERR_MSG |
71 |
50 |
Char |
NFC error message |
|
SUSP_ELEM_NAME_NUM |
121 |
3 |
Char |
NFC element number (record field location) where error detected |
|
SUSP_ELEM_NAME |
124 |
30 |
Char |
NFC element name (record field location) where error detected |
|
SUSP_DATA_FIELD |
154 |
8 |
Char |
NFC element content (field value) where error detected |
Supported Document Types
PeopleSoft delivers and supports four document types that correspond to the types of data imported during the SINQ Import process. The delivered document types are listed in this table:
|
NFC Document Type |
Description |
|---|---|
|
063 |
Personnel Action |
|
110 |
Award |
|
112 |
Cash Award |
|
123 |
Education |
System administrators can filter any of these NFC document types when they run the SINQ Import process.
The SINQ Import process generates a worklist entry and an email message. The recipient uses the worklist entry to access a list of all PACT or PMSO assigned work entries. Clicking a work entry routes the user to the component where the work is to be performed.
The following diagram illustrates the process of using the worklist notification to access first the list of work entries and subsequently the components where the work is to be performed:
When a user selects an assigned work entry for a PACT SINQ row, the page that is displayed depends on the NFC document type and the status type values. If the NFC document type is 063 (Personnel action), 110 (Award action) or 112 (Education), the pages that are displayed are:
If the Status type value equals 001, the Cancel Personnel Action USF (EE_CANCELLATION) component is displayed.
If the Status type value equals 002, the Correct Personnel Action USF (EE_CORRECTION) component is displayed.
If the Status type value equals blank or any other value, HR Processing USF (EE_HR_PROC) component is displayed.
See Understanding the Administering PAR System.
If the NFC document type is 123, the Person Profile component is displayed.
See Person Profile Page.
When a user select an assigned work entry for a PMSO SINQ row:
If Action type field value is INDV, the Position Data component is displayed.
If Action type field value is MSTR, the Job Code component is displayed.