MDG Budget Transfer Rules

8/18/2019 MDG Budget Transfer Rules

1/18

Budget Transfer Ruleswith SAP NetWeaver Decision Service Management

PublicSeptember, 2013


2/18

© 2013 SAP AG. All rights reserved. 2Public

Agenda

1• Overview

2• Requirements

3 • Implementation overview

4• SAP NW DSM(1) implementation

1 - SAP NetWeaver Decision Service Management is an add-on to BRFplus


3/18


Overview

Business Context:

Budget transfers need to be limited (controlled) according

to rules defined by law and loaded into system by the

customer.

Development scope:

- Localization for MENA region countries

- Funds Management functional area (FI-FM)- Software component EAPSGLO


4/18


OverviewDetail

Governmental Institutions in Saudi Arabia, UAE and manyother MENA countries are strictly following some rules and

instructions stipulated by Ministry of Finance (MOF)

regarding any financial aspect or activity carried out by these

governmental institutions.

The core controller of all Governmental Institutions’ financial

aspects is the BUDGET.

The approved budget is provided by Ministry of Finance

(MOF) to the governmental institutions to spend on

designated activities i.e. every expenditure (financial wise)

done by these governmental institutions should be linked to

budget item in the BUDGET and cannot exceed (otherwise

unbudgeted expense request should be created for

approval) the designated budget amount.

In some cases whenever it’s justifiable, government

organizations need to transfer some pre-approved

budgets from one budget items (Commitment items) to

another whenever possible and as per the instructions

received from Ministry of Finance (MOF).


5/18


Agenda

1• Overview

2• Requirements


4• SAP NW DSM implementation


6/18


Main requirementsOverview

This development has a total of 19 main requirements;

Due to the extensive list of requirements we list here some of the main ones:

Type Requirement

Rule setup Defining more than one rule per Commitment Item (CI)

Rule setup Use of lists or ranges of CIs in a single rule

Budget Cap Budget cap: using fixed value

Budget Cap

Budget cap: using a % of the total sender budget

Budget Cap Budget cap: using the rule budget key to define how to calculate the CI budget cap

Additional restrictions Rule time validity

Rule conflict management

Prevent the creation of overlapping rules

Globalization Solution available in Arabic

Compatibility Future compatibility with a Workflow implementation


7/18© 2013 SAP AG. All rights reserved. 7Public

Main requirementsOptions

The following options were analyzed regarding the

possible requirements’ coverage:

• Consistency Check (*)

• Cover Eligibility (*)• Full ABAP Custom Development

(*) Standard solutions from Funds Management



Main requirementsCoverage

We concluded that SAP NW DSM was the best option regarding the relation Requirements coverage /Development complexity:



Agenda

1• Overview

2• Requirements





ImplementationOverview

DSM Service Support Objects

Service Class

R BRFplus Functiondetails

FMBB Extension

Transaction FMBB

BADI

Implementation

BRFplus(1)

Logic

Rules Table

R Rules

Transfer

permissionR

CustomizationCustomization

settings

R

Customization

Caption

Component

Storage

Channel

R Request flow

Badi Call

Budget

InformationR

This development is comprised of 4major building blocks:

• the BADI implementation that

extends the functionality of

transaction FMBB;

• The DSM development thatcontains most of the logic (using

BRFplus);

• the Service objects that provide

most of the information needed

during the check process;

• the customization that allows theuser to configure the behavior of

the solution.

1 - SAP NetWeaver Decision Service Management is an

add-on to BRFplus



ImplementationDetails

FMBB Extension: enables the transfer check when a document is being checked or posted. In order to

do this, a standard BADI was implemented and the transaction will run this BADI implementation every

time a document check is performed.

DSM Implementation: includes most of the logic behind the definition and processing of the budget rules.

The customer defines the rules in a BRF+ object called Decision Table. BRF+ will receive as input the

information about the document that the user is trying to check/post and outputs if the transfer is allowed

or not. If the transfer is not allowed BRF+ will output the calculation details so that the user knows why thetransfer was not allowed.

Service Support Objects: is responsible for providing the information necessary for several of the

calculations made in DSM.

Customization: allows the user to enable the rule checking and allows the configuration of some aspects

of the program behavior.



Agenda

1• Overview

2• Requirements





SAP NW DSM implementation

Overview

Total of 139 objects• 2 Applications

• 1 Ruleset

• 1 Function

• 24 Rules

• 1 Decision Table

• 10 Formulas

• 4 Procedure Calls

Delivered with two different DSM storage

types: (System and Customization). This

allows the client to customize the rules in the

decision table.



SAP NW DSM implementationDecision table

Allows the user to define the rules that will impose the limits to the transfers.



SAP NW DSM implementationProcedure Call

Static Method Call, will retrieve some of the information needed for the calculations made in DSM.



SAP NW DSM implementationRuleset

Includes most of the logic of the development:


17/18

Thank you


18/18

© 201 SAP AG All rights reserved

© 201 SAP AG. All r ights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power

Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,

Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered

trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin

are trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®,World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry

Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App

World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,

Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,

Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, SAP HANA, and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal

Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase

products and services mentioned herein as well as their respective logos are trademarks or

registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarksof Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational purposes only. National

product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be

reproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.

MDG Budget Transfer Rules

Documents

Transcript of MDG Budget Transfer Rules