KNOWN ISSUE in mLINQS

There is currently a known issue in mLINQS FSC is working on.  The error is being caused when an amendment is done in mLINQ that removes the expense lines that had a payment processed against it for an advance and another amendment is processed to add the expenses back in. This action creates duplicate lines in FSMS and produces a “fetch error” as FSMS does not know how to process against the multiple lines due to a payment being tied to one. There is currently a SNOW ticket open at FSC Tier 3/FSMS.

ATTENTION - E2 USERS

Single sign on (CAC) for E2 is currently causing profiles issues. Please refrain from using and/or creating CAC E2 profiles until further notice. Using the user name and password (historical E2 log on process) should be used at this time, at E2 User ID and password

ETS ERROR

ETS is currently producing an error when creating new accounts or updating user IDs/EMPLIDs to current accounts, please submit a PPC ticket for these members so that the issues can be fixed individually. A system wide fix is still trying to be worked. If a member who does not have an ETS account is needing to book upcoming travel with a departure date within the next 3-5 days, they will need to call the TMC/SATO to make any reservations and insist that the booking be made without a profile.

With the ongoing issue in E2 that prevents new user accounts from being created, if any of the impacted members have had to call the TMC to make reservations without a TMC profile, please submit a PPC Customer Care Ticket including the following information below. PPC is working with E2 programmers/contractors to track this issue as well as reduce the TMC fees for those impacted due to the systematic issue.

Member Name, Rank, and EMPLID:

Reservation Confirmation Code:

Travel Dates:

Duplicate Relocations Found in mLINQS from Unauthorized Manual Entries

There have been several duplicate PCS relocations found in mLINQS causing a plethora of issues.

AO’s and/or proxies should NOT be entering relocations manually in mLINQS without contacting PPC first (customer care ticket) as relocations should be processed from DA to mLINQS. Below are the steps to take if a relocation has not processed from DA to mLINQS.

If the PCS relocation has been put in a “ready” status in DA and is not found in mLINQS :

1. Contact PPC customer care via trouble ticket subject “re-submit to mLINQS” and PPC will manually re-submit this relocation over to mLINQS.
2. If PPC cannot process this relocation over to mLINQS due to a systems error, we will work with the AO on manual entry.
3. Relocations input using the legacy process should still submit a ticket to finish those claims using the legacy process calculator method. Only if they have already started using the legacy process.
4. Any manual input relocations into mLINQS outside of this process will require an AO/proxy re-training and possible revocation of elevated permissions.

RETIRED PAY 

PPC is addressing a processing delay due to systematic issues and a shortage of personnel. This is causing a delay in response efforts for VA offsets, AEWs, CRDP, and CRSC disability. You remain our primary concern. We want to assure you that we are fully committed to resolving these issues promptly and handling your cases with utmost care and accuracy.