F-28 - Alternate payer

[marcchambers]

When processing a manual cash adjustment using Tcode F-28, I have noticed recently that when bringing in a customer, it would also bring all "alternate" payers as well. (Did not do that previously)

This new way has really created a very slow operating time within SAP.

Before: Using Tcode F-28, only the actual customer requested would generate - Would take secs for open AR to load
Now: Using Tcode F-28, customer and all aternate payers are pulled

and the request can take 10+ mins to be generated.

[Former Member]

Welcome to the SAP Community. Thank you for visiting us to get answers to your questions.

Since you're asking a question here for the first time, I'd like to offer some friendly advice on how to get the most out of your community membership and experience.
First, please see https://community.sap.com/resources/questions-and-answers, as this resource page provides tips for preparing questions that draw responses from our members. Second, feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html, as that will help you when submitting questions to the community.
I also recommend that you include a profile picture. By personalizing your profile, you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html.
Now for some specific suggestions on how you might improve your question:
* Outline what steps you took to find answers (and why they weren't helpful) -- so members don't make suggestions that you've already tried.
* Make sure you've applied the appropriate tags -- because if you don't apply the correct tags, the right experts won't see your question to answer it.
* Use the "insert code" feature when sharing your code, so members have an easier time reading.
Should you wish, you can revise your question by selecting Actions, then Edit.
The more details you provide (in questions tagged correctly), the more likely it is that members will be able to respond. As it stands, I don't know if there is enough information here for members to understand your issue. So please consider revising your question because I'd really like to see you get a solution to your problem!
I hope you find this advice useful, and we're happy to have you as part of SAP Community!