Job Description :
Sr. SAP ABAP Consultant with BPC Knowledge.

Location: West Palm Beach Florida
Duration: 12 months to 24 months
Start: Within 7-10 days

Analysis of Contractor Need

Background / History with Project:
Technical limitations were encountered in 2015 with the native programming language ,ScriptLogic, of the SAP BPC 10.0 (Classic) environment implemented for capital, and headcount planning solution.
The BPC consultants / contractors were unable to use the language to perform complex planning calculations reading and writing data from / to several BPC models / InfoCubes in real-time when required by the business.
Initial development indicated that using ScriptLogic required:
o An unacceptable run-time for the calculations to run to read / save data
o Used an unacceptable amount of server / system / processing resources that impacting usability for end-users
o Generated unacceptable amounts of “interim calculation” data records / volumes
A need for a senior / experienced ABAP / BADI developer was required in order for the project to proceed with development. He has built several pieces of complex planning logic used today by the FPL SAP BPC System production system and coached / guided several other more junior ABAP / BADI programmers that were brought into FPL SAP BPC System project team to help with the workload.

Past Key FPL SAP BPC System Planning Logic Developed / Supported:
Core Headcount, Timesheet, Payroll, O&M, Capital Dollar Planning
o Headcount Planning
Batch logic - ABAP / BADI programs to reference employee master data changes and post / repost / clear headcount forecast data based on master data changes.
On-save - ABAP / BADI programs to automatically generate headcount forecast data for future periods when users clicks “Save Data” button
o Timesheet Planning
Batch logic - ABAP / BADI programs to reference employee master data changes and post / repost / clear timesheet forecast data based on master data changes.
On-save - ABAP / BADI programs to automatically generate timesheet forecast data when user updates headcount forecast data.
o Payroll Planning
On-Save / Batch logic - ABAP / BADI programs to reference employee headcount, timesheet, and salary amounts when users clicks “Save Data” button in EPM workbooks to generate payroll dollar forecast values allocated to correct cost centers, accounts, and internal orders.
o IO Planning
On-Save / Batch logic - ABAP / BADI programs to allocate all forecast dollars posted to an internal order to appropriate Level 3 and Level 4 WBS element master data in downstream models and apply overhead dollar amounts.
o WBS Planning
On-Save / Batch logic - ABAP / BADI programs to allocate all forecast dollars posted to a Level 3 WBS element to appropriate Level 4 WBS element master data in downstream models and apply overhead dollar amounts.
Additional Planning
o Checkbook Planning
On-Save logic - ABAP / BADI programs to apply overhead dollar amount to forecast dollars posted to a Level 3 WBS element
On-Save logic - ABAP / BADI programs to generate automatically generated email workflow
o Driver-Based Planning
Batch logic - ABAP / BADI programs to reference actual driver data and actual O&M / capital dollar data and automatically generate $ / driver rate data on a nightly basis as part of the overnight batch
On-Save logic - ABAP / BADI programs to reference driver forecast data, $ / driver rate forecast data, account allocation forecast data, and project type allocation forecast data to generate O&M / capital forecast data when users clicks “Save Data” button in EPM workbooks and post results to downstream models




Looking forward for your response.