Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
We ran a payment run and the payment document even got posted - but the session was continuing and had to be manually stopped.
There are coupl of question though - It was not use behave like this earlier as I can see in the job log an session being executed correctly for payment run.
I'm assuming 2 things:
1. For the user running the PAyment run program the - default parameter in SU3 was defined as 'locl'.
2. The user ran the payment run for a company code and in the Variant for program Z_RFFOAVIS_FPAYM_ADVICE_TCSBCT has a different company code.
Execute the same program Z_RFFOAVIS_FPAYM_ADVICE_TCSBC by mapping the parameters from the payment run after proposal is generated. Check in debug, may help you get to the cause of it.
Execute the same program Z_RFFOAVIS_FPAYM_ADVICE_TCSBC by mapping the parameters from the payment run after proposal is generated. Check in debug, may help you get to the cause of it.
Bluesky
