Skip to Content
Technical Articles
Author's profile photo Nimish Agarwal

Automating Payment Proposal Process (F110) Through Batch Jobs For Program ‘RFF110S’

Hello and welcome to my blog post on automating payment proposal process through batch jobs using program RFF110S.

 

Introduction: –

Client had a requirement to automate ONLY their proposal jobs whereas payment runs be executed manually by the AP team.

Daily, business executes 20 pay-cycles for multiple company codes with varied dataset based on the day of the week. For example, Checks are run on Tues & Thurs, ACHs & Wires daily, Outsourced Checks on Wed & Fri, and so on. Dates such as Posting date, Next post. date, etc. play a key role in defining your dataset for that specific day.

This looked quite monotonous even from a user perspective, entering same set of data every single day to get the process going.

PS: Requirement is ‘proposal job should ONLY trigger on business days.’

 

Prerequisites: –

Three-step settings required to achieve the aforesaid requirement –

Step 1 – Configuration Change – Create Factory Calendar, i.e., AP Team Working Days Calendar. (T.Code SCAL)

Step 2 – Create variants for program RFF110S for each working day (Program RFF110S)

Step 3 – Schedule batch jobs for program RFF110S with variants created in Step 2 (T.Code SM36)

 

Step 1 – Configuration Change – Create Factory Calendar, i.e., ZZ – AP Team Working Days Calendar.

T.Code  SCAL –

Usually, Factory calendar is quite a risky thing to configure, and it’s advisable to have inputs from PP (Production Planning) team before proceeding to setup the same. In case you don’t have PP team in the project, check who is responsible or owns the factory calendar part and align with them.

While creating a factory calendar be careful that SAP landscape is completely in sync with all the calendars available in production. The new transport request will include existing calendars as well as the one you will create for AP team working days schedule. Kindly take a note of that.

In my case, while creating factory calendar I had to tweak few days to reflect them as working day and few days as holiday. This can be achieved using Special rules in factory calendar and it’s the sole criteria for your batch jobs to ONLY trigger on business days.

One important thing to remember, you must update the factory calendar every year based on the business days provided by your client.

 

Step 2 – Create variants for program RFF110S for each working day (Program RFF110S)

This is the most critical step in the entire setup.

All my variants are DYNAMICALLY date updated and any change in the static field led to creation of new variant for the pay run.

For example,

ACHs (A) & Wires (W) ran daily

Checks (C) ran Tues & Thurs

Outsourced checks (O) ran Wed & Fri

To begin with parameters for program RFF110S, we need to create variants

 

Variant 1 – CC_MON     (CC = Company Code & Mon = Monday)

Run date = Current date, Run id = Company code, Posting date = Current date +1, Docs Entered up to = current date, Company code, Payment Methods = AW, Next Post. Date = current date +2

Vendor range = to be provided by business. Rest of the fields can be selected on need basis.

 

Variant 2 – CC_TU_TH

Run date = Current date, Run id = Company code, Posting date = Current date +1, Docs Entered up to = current date, Company code, Payment Methods = ACW, Next Post. Date = current date +2

 

Variant 3 – CC_WED

Run date = Current date, Run id = Company code, Posting date = Current date +1, Docs Entered up to = current date, Company code, Payment Methods = AWO, Next Post. Date = current date +2

 

Variant 4 – CC_FRI

Run date = Current date, Run id = Company code, Posting date = Current date +1, Document entered up to = current date, Company code, Payment Methods = AWO, Next Post. Date = current date +4

Friday’s run required a new variant, solely because the next post. date is current date +4 days (since Sat & Sun are weekly off)

4 variants per company code were setup, reaching 80 variants in total for 20 company codes.

 

Step 3 – Schedule batch jobs for program RFF110S (T.Code SM36)

The pay-cycles required to be run at 09:00 am daily. Jobs were scheduled as –

Job Name – RFF110S_MON_CC (MON = Monday & CC = Company Code)

Program – RFF110S

Variant – CC_MON

Date and time – Enter upcoming Monday date and time as 09:00:00

Periodic Job – Checked, Period Values – Weekly

Restrictions – Factory calendar, Calendar ID:  ZZ and Select Execute on Working Days radio button.

Similarly schedule jobs for Tuesday, Wednesday, Thursday, and Friday with their respective variants.

When the scheduled batch job is executed, system will create an additional job for your proposal run with regular nomenclature ‘F110-20230112-2000   -X’. Please refer below screenshots for better understanding.

 

Conclusion: –

This helped business users save substantial time in their busy work hours and had proposal data readily available in the system for review in early hours of work.

One vital step to remember, those pay-cycles where proposal doesn’t yield any successful payments (none of the supplier is in green) needs to be deleted. If you don’t take this step – vendors will be locked in the said pay-cycle and won’t be considered successful in the next payment-run.

 

I hope, my blog provides solution and guidance in the subjected matter and wish my colleague consultants find it useful in their support and development activities.

 

Best Regards,

Nimish Agarwal

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.