Scheduling Automatic Payment Program Error.

[Former Member]

Hi Experts,

I have created a varient in F110S for APP as on Payment date as 09.04.2013 with Identification as "FITVY" with all other required field entered. Now i have created a Job and schedule the Program every date.

On 09.04.2013 all the Open item for the Vedor have been cleared and the Job ran Succesfully. But the Next day i.e., on 10.04.2013 the Job status was in Canceled status  when I looked into the Job Log it says Identification Already Exist.

I would like to know how to schedule APP through Job or is there any steps i am missing.

Regards,

Raziq Fareed.

[former_member198032]

Hi,

1. How can avoid to have jobs started which will conflict?

2. If we get question 1 solved, then we can also skip our waiting steps,

as next steps will start when previous step really is finalized.

You can call report RFF110S for following cases:

1. To create parameter for SAPF110S and to start a proposal run!

2. To create parameter and to start a payment run immediately!

3. To start the payment run if a proposal exist already!

There are not any other functions!

Although you have to pay attention, that a proposal run or a payment run

will be started as batch jobs in any batch task, if such a free batch

task exist. The job with the reports RFF110S etc. is blocking such a

batch task furthermore if there are any WAIT steps.

You are right too, that proposal run or payment run can run a short time

only, but can run a very long time too.

At last step in the proposal run the payment program updates the table

entry REGUV by REGUV-XVORE = 'X'. This will be checked in RFF110S too.

If parameter already exist and a payment should be started, but

REGUV-XVORE <> 'X', than F0379 with 'Run Identification Already Exists'

will be displayed.

At last step in the payment run the payment program updates the table

entry REGUV by REGUV-XECHT = 'X'.

But this does not mean, that all functions of payment program will be

ready. You know, normally the payment documents will be posted

asynchronous. These postings could be take more time than the run time

of the payment program. That's why "payment document validation" is

important for creation of payment medium (see topic 4 of note 545340).

As described there, the update is complete if the number of posting

orders created (REGUV-ANZER) corresponds with the number of completed

posting orders (REGUV-ANZGB) in transaction F110. But a simple check

does not exist, if any posting terminates and will be visible by SM13.

Best regards,

Cristiano