SFS will send PayServ the initial Cost Center file to be loaded into the PayServ Account Code table for use upon conversion to SFS during the second Full Dress Rehearsal FDR2. Only Cost Centers that are active and properly mapped in SFS, have valid chart field values and have personal service segregations established (including zero segregations) will be included on that file. This file will contain data as of February 17, 2012. Any Cost Centers updated in SFS after February 15, 2012 will not be transmitted to PayServ in time for the first pay period in April 2012.
OSC will begin converting the PayServ Account Code table using the Cost Center file from FRD2 concatenated with the new SFS Account Codes on March 23, 2012. OSC will then match the values in the table with the PayServ Account Code values in the Position Pools (Cost Center portion only).
All Position Pools with a valid match will then be updated with the new SFS Account Code (formally object code).
Any Position Pools that do not have a valid match to a PayServ Account Code table cannot be successfully transmitted to SFS. As a result, OSC must change any Position Pool assignments to PayServ Account Code value that was valid in SFS as of February 17, 2012. All changes to Position Pools in PayServ must be completed by March 22, 2012 so that conversion of the PayServ system to the SFS format can begin.
OSC will assign a default PayServ Account Code value to every Position Pool without a match. The updated value will remain in place until action is taken by the agency. This value cannot be changed prior to the first pay cycle in April. Accordingly, completing all Position Pool updates by March 23, 2012 is critical.
One default value has been established for each Business Unit using a Cost Center that is valid for that Business Unit. Each default value has the same short description of OSCCHG. A list of these default PayServ Account Code Values is in Attachment A.
After these actions are taken, all Position Pools will function properly in SFS and the Payroll Earnings Charges file can be successfully transmitted to SFS. But, while the PayServ Account Code will be valid in SFS, it may not charge the COA string desired by the agency. Agencies that do not complete updating of the Position Pools may need to process Journal Vouchers in SFS.