3816269 - Why would the fares be stored as PI instead of TR when our configured pricing option is TR?

I booked a split ticket on AA and DL and their fares were stored as PI (Pricing Instruction) instead of TR (Ticket Record).   
FQPI- 1. 4PFSR#/@@XXXXXX#FNP#S1

Why would the fares store as PI instead of TR when other sites store them as TR for splits?

In the past Concur was using PI (Pricing Instruction) but I read earlier this year that the PI was being sun-setted and Concur was going to start using TR (Ticket Record). , KBA , CON-EXP-TRS , Trip Segments / Reservations , CON-CA , Cross Applications , CON-SRV-TRV-ADM-LAN , View Airlines , Problem