There are 2 extractors based on tables BSAK (close invoices) and BSIK (open). So that takes care of your open and closed invoices.and the extractors load into the same inbound invoices DSO As far as the account type, why do you want to pick type 'K'? if thats is the case the your spend will be always be zero as you would nullify the credit amount with debit amounts for all the closed/cleared invoices.
as far as the difference in records, do you have a mismatch between the PSA records and DSO? Usually RSA3 is not a tool to verify the accuracy of the record count but to test the functionality and extraction. Anyway back to the mismatch, do you see a error message in your data management in UI for those 6 records, due to many verifications (date format etc) that the system does while loading to inbound DSO. if any identify them in PSA and correct them in the source system and reload the data. unfortunately system doesnt allow you to load from PSA to DSO in SPM data model, which is kind of dumb but thats what it is.
System tags the po/NON invoice based on indicator it sets during the data - check the transformation for the logic. Not top of my mind. And there are instances when the business say they are PO related, the data record may not have a PO. special authorizations for buyers allow them to create invoices without referencing a PO. Do you see a PO number as a reference document number on the invoice line? That should tell you if it is a data issue or a logic issue. If so is the scenario you can always change the extractor to include additional logic to generate dumy PO number to trick the system - something like 9999999999
Spend Analysis, Non-PO related invoices with multiple vendor lines and a corresponding single GR/IR expense line is not generated in the SPM report - doesnt ring a bell!!!!
create your own detail reports and tag them to the measures in the measures adminstration. But you can as well change the standard reports, not top of my mind.
