Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from dfeyres on May 10 at 10:02 PM Hello Sunny,
This requires an answer on a couple of levels.
First: Why do you want separate batch proposal and batch payment runs? Best practice is to reduce the human interaction with the automated process. If an item has been approved by all relevant authority to be created as a payable, why do you need to have a proposal to have someone approve it again?
- If it is to make sure that "all is in order", your best practice is to make sure that the vendor or customer data is correct at set-up.
Second: I know. a lot of businesses still want a proposal followed by a payment run.
- I don't believe that standard SAP allows you to have a batch job pick up an already-existing proposal and complete it as a payment run, but I am not certain on this. My logic is that the batch F110 runs I have seen always create a new object (ie proposal or run with date/ID combo) and because that date/ID combo already exists as a proposal, SAP logic considers the new object an illegal duplicate and it crashes. In other words, you have a proposal called SUNNY dated 05102014 and the system will try to create a payment run called SUNNY dated 05102014; since that combo already exists, it crashes.
There are some workarounds.
a. Have the batch job create the proposal. A person can review it and update it as needed, then manually launch the payment run and output. You can have a security profile that allows view-only access of a proposal, or payment run only use of F110 etc if there is worry about separation of duties.
b. Run the proposal via batch the day before, review, then delete it. That allows time for corrections and updates. Then have another batch job run the payment run on the following day, without a proposal. You need to use different names so that today's proposal and payment run don't interfere with each other. Example: Call the proposal SUNN1 and call the payment run SUNN2 each day; payment run SUNN2 for day N+1 always has the data reviewed in proposal SUNN1 on day N. You should run the proposal after the payment run as customers on a proposal are blocked for other posting, including the payment run- and the proposal will be open for a little while.
- This is what I've done successfully at a client.
V/R
DFE
| | | ---------------Original Message---------------
From: Sunny
Sent: Tuesday, April 15, 2014 4:35 PM
Subject: Automatic ACH run through Batch Job
Hello Gurus,
I have configured ACH Incoming and Outgoing payments for F110 successfully. Is there a way we can run ACH, everyday through a scheduled batch job?
The job would do a payment run and save the file into given folder from where we will upload the file to our bank.
The basic idea is to decrease the human intervention in the ACH process.
Thank You
Sunny |
| Reply to this email to post your response. __.____._ |   _.____.__ |
