Бюджетирование в разрезе договоров

Пример возможного сценария

Анатолий Рябуха

Process agreed for materials (50% - down

payment, 50% - final payment)

Process agreed for Service (50% - down

payment, 50% - final payment)

0.A: Top down uploading planning value into

OLTP ERP system

BW/BPS: Planning values across 3PL (Cash flow, P&L, BS)

FI-FM/BCS

FMCYCOPI_BW –

Upload planned data 2

times: one for commitment budget,

one for payment budget

Note:

Need customizing for derivation rules

Funds center – equal to Cost center

Commitment item – equal to line item from financial

reporting

Contract life-cycle management

Внешнее

согласование

Внутреннее

согласование

Переговоры Разработка

проекта

договора

Подписание Исполнение

Закрытие

Пролонгация

Хранение документации

0.B.1: Contract card (SAP RCM)

0.B.2: Contract card (SAP RCM). Specification

Route maps

Notification about required approval contract

Approval Task

Approved electronic version of contract

Contract execution / payments schedule

Contract monitoring: active or passive

1: Purchasing contract (services) creation

from RCM over BAPI

Need creation non stocked materials for different

types of services

Payment term definition

Necessary additional fields (VAT and etc. can be

add with using standard enhancement

MM06E005

Funds reservation after saving contract

(FMRP_RFFMEP1AX):

Closing issues from Objectives of the new design

Issue/Current state SAP functionality % of closing

1. Depository of all contracts and its appendixes Relationships – 1:M (framework -> additional

agreement will be done with using standard

enhancement MM06E005, in current ZPOC will

be add separate section with hierarchy ALV list

100%

2. Workflow to support authorization

process/Vendor creation process

Standard approval process for contracts in

RCM/Initially vendor will be created with blocking

(SAPMF02K), then block will be reset over

FK05/XK05, for confirmation will be used

transaction FK08/FK09

100%

3. Capturing as much information as early as

possible in the process

Using drill down approach for ZPOC adoption

and standard drill down in RCM 100% 4. Use of very few “Free Text” Fields, most input

will be controlled in some form

Using structured fields in RCM/MM contracts

reduce this issue 100% 5. Controls to be introduced for Tender Tracking

& Currency control

Additional steps in Contract release, normal

tracking can be done only in SRM (Please look

outstanding issues) 15%

6. Budgetary controls Commitment plan on contract level integrated

with YTD control approach in FI-FM 100% 7. Renewals and expiration controls Need development special TS

100% 8. Be user friendly Integrated drill down standard objects: necessary

data input one time and use over all chain 100%

Closing issues from Contract design

Issue/Current state SAP functionality % of closing

1. Frame Agreement: This basically is a

preferred vendor appointment. No

payments can ever be made against the

frame agreement. Each purchase with this

vendor will need to be supported by an

individual P.O./Appendix

Customizing: Will create special agreement type

with separate number range. PO will be created

over BAPI for approved frame agreement 100%

2. Standard Contract: These are contracts for

recurring services and/or fixed rate per

transaction POC’s can be booked against

the standard contract No separate

P.O.’s/Appendixes required Examples;

Petrol, transport, rent, insurance, Custom

Brokers etc

Customizing: Will create special agreement type

with separate number range. PO will be created

over BAPI for approved standard agreement

100%

3. ASP Contracts: Payments to ASP

Further process to be thought through in

view of the existing (claim)processes in

place

Customizing: Will create special agreement type

with separate number range. PO will be created

over BAPI for approved ASP agreement

100%

4. Dummy Contracts: These contracts are to

be used and generated by accounting only

Generally for statutory dues

Today , these would be payments without

contract (POC Only)

Customizing: Will create special agreement type

with separate number range. PO will be created

over BAPI for approved Dummy agreement

100%

Closing issues from POC Enchantment

Issue/Current state SAP functionality % of closing

Introduction of rules/dropdown selections/

standardized input (formats)

• All inputted electronic documents will be

standardized (MM contracts, PO, DPR, IR)

• Dropdown selection will be reduced over

automatically created via BAPI: purchasing

contract , PO, DPR (ZPOC)

• Standard WF & objects provide abilities for

using standard authorizations

100%

Addition of fields to facilitate accounting:

VAT Code, Account selection through services

type

• VAT maintenance with using MM06E005

• Automatic account assignment over

derivation from services type 100%

Productivity tools to be built:

Copy facility from Excel , eg Mobile phone bill to

many cost centers

• Use standard documents templates in RCM +

ABAP developments (upon to customer

requirements) 100%

2: PO creation over BAPI for approved contract

Coping commitment plan from contract together with account

assignment

Budget reservation & reducing funds reservation

after saving PO (FMRP_RFFMEP1AX):

3: Down payment request creation (ZPOC – with

reference on PO line items)

Open FI:

copied from

PO Blocked for

payments

Account

assignment

copied from

PO

Approval DPR over WF

Approval DPR over WF

Block reset after approval

Budget reservation & reducing PO reservation

after saving DPR (FMRP_RFFMEP1AX):

4: Payment proposal generation for output DPR +

final payment -> necessary info for bank-client

File for

Bank-client will be

prepared with using

Current application

Grouping

for multi

lines PO

5: EBS upload in system (posting over FEBAN):

DPR will be clear automatically

Actual& reducing DPR reservation after saving DPR

(FMRP_RFFMEP1AX):

7: Invoice-facture posting (ZPOC – with reference

on PO line items)

Approval for

payment will

be the same

as for DPR

After press SAVING – RUN PBU3:

After press «SAVE DOWN PAYMENTS»:

Down

payment

automatically

offset

Actual after IR (FMRP_RFFMEP1AX):

8: Payment proposal generation for FP + final

payment -> necessary info for bank-client

Positions automatically

grouped

Payment date = due

date

9: EBS upload in system (posting over FEBAN):

Invoice-facture will clear automatically

Final payment representing in Budgeting

Open PO on the end of month:

FMTB – posting accruals:

Reversal on 1st day next month – FB08:

Example charging PO based accruals in FI-FM:

Automatical accruals

Need

budgetary

ledger

activation

Closing POC enhancement issues

Issue/Current state SAP functionality % of closing

Input to be Rule based & Dropdowns to

facilitate: Less input & standardized input

selections

Purchasing contract creation over BAPI

PO creation over BAPI

DPR creation over ZPOC

Automatically DP offsetting

IR creation over ZPOC

Automatically FP clearing

RCM contract template update over BAPI

100%

Productivity tools to be built:

Automation of Cash application

Intermediate solution: TR-CM for liquidity

management and forecasting (customer and

vendors groups, special groups for SO and PO)

or Key figures in FI-FM.

100% - cash

balances

approach Feature solution: PSM Cash control activation

with special SL for Cash control. In this case

Payment proposal in F110 will be replace on

FPRL_LIST (automatically creation payment

proposal for approved payments). FPRL_F110 –

will create final payment run in background

mode.

100% - cash

flow based

approach

Example TR-CM report:

Future solution: PSM Cash Control

Creation of payment proposal based upon

rules and ability to manually select or de-select

will be close on 100%

Special case reflected to defferd expenses

(Accrual Engine)

Periodical write off by objects

Necessary RICEW lists

RICEW object Objects Comments

Reports

• ZPOC adoption for creation DPR

• ZPOC adoption for creation IR (invoice-facture)

• ZPOC adoption for display hierarchy relationships

between framework agreement and additional

agreement

• Multi lines PO (comfortable transaction) - CDP

• Multi lines PO (comfortable transaction) - CDP

• Depository of all contracts and its appendixes - CDP

Interfaces

• Run from RCM BAPI_CONTRACT_CREATE for

contract creation

• Run for approved contract BAPI_PO_CREATE1 for PO

creation

• Contract execution – payment schedule

• Contract monitoring

• Run method after change contract status on approved

• CDP

• CDP

Conversions

• LSMW – initial upload fund centers hierarchy

• LSMW – initial upload commitment items hierarchy

• Only for initial MD upload

Enhancement • MM06E005 – additional fields in MM contracts and PO

• SAPMF02K – blocking new vendors

• EXIT_RFEBBU10_001 – add selection for payment

order

• J_3RF_RATE_CALC (form check_partner)

• EXIT_SAPLF040_004

• SAPLFMDT

• BUAVC_LEDGER_CHECK

• ME_COMMITMENT_PLAN

• Upon to customer request

• Need for automatically clearing DPR or final payment

with selection criteria “Payment order”

• Switch off check for clearing in local currency

• Definition approval person from cost center or funds

center

• Keep external contract number in user defined field

(grouping in FI-FM ALV Grid reports)

• Online availability check: inside of contract commitment

plan

• Automatically creation commitment plan in contract

Workflow • WS00400022 – DPR & Final payment approve (based

on AP debts): 3 levels

• Approval TS for contracts

• Expiration notification TS

• Activation standard WF + Payment release customizing

in AP

• CDP

• CDP