EBF Overview En

SAP AG - IBU Utilities

SAP Consulting Germany

EBF

SAP AG 2005, Easy Bill-correction Framework, / 2

ContentWhy Easy Bill-Correction Framework ?

Overview and Definition

EBF legacy billing data pool

EBF line item correction

Available downgrades until ERP 2005


Total co

st of im

plemen

tations

Starting point - Frequency of corrections in history

full installation structure isto decide on customerproject

IS-U (Full) Reversal

Corrections

100 %

80 %

60 %

40 %

20 %

productive

start

History

Easy Bill-correction Framework

Reduces migration effort to a minimumLow risk of data inconsistencyRecalculation of price and quantity

Future


Customer options until now

Historical migration of billing documents required also a historicalMigration of installation structures, devices, historical changes

cost intensive, increases migration effort to a factor of tenhigh risk, increases risk of data inconsistency

Full IS-U Functionality available for migrated data(including wash-up and bill reversals)

Full history available in IS-U

Full historical Migration

No migration of historical data

cheap approach, reduces migration effort to a minimumlow risk, decreases risk of data inconsistency to a minimum

No history and no historical data in IS-U available

No bill reversal and wash-up possible in IS-U

No historical M

igration


Customer Benefit of EBF

Historical migration of billing documents WITHOUT a historicalMigration of installation structures, devices, historical changes

cheap approach, reduced migration effortlower risk, decreases risk of data inconsistency

Reduced functionality available for migrated billing documents inEBF Data Pool (EBF correction methods, EA22)

Full billing documents history available in IS-U

NOW: partial historical Migration with EBF


SAP / IS-UProcesses

Definition of EBF

Easy Bill-correction Framework

LegacyBilling Data Pool

Line-itemCorrection

Physical storage place incustomer namespaceReduced billing line itemsfrom the legacy systemInserted by new migrationobjects

Central correction interface forbilling line itemsOpen framework to definecustomer specific correctionmethods based on single stepsPredefined correction stepsfrom standard

LegacySystem

Operationalbilling data

without EBF

EBF


Definition Easy Bill-correction Framework

The Easy Bill-correction Framework (EBF) is a tool box for simple corrections /re-calculations of billing document lines comes from an non-operationaldatabase, without any installation structure.

EBF is able to:migrated billing documents from the legacy system in an non-operationalcustomer databaseuse customer-specific correction methods on line item levelcreate a manual billing document for single corrections on easy way

EBF is not able to:create a manual billing document from the operational IS-U databasehandle any installation-structures or facts

In the end EBF is a more automatic way to create a manual billing documentwith reduced information.








EBF – General Idea

OperationalIS-U Data

ERCHZERCH

daily storage procedure

Loaded onrunning time forbill correction

unique storageafter migration(„read only“ database)

ReducedERCHZ-Structure

Non operationalEBF Data PoolLegacy

System

migrationprocess


Z

historical bill migration using EBF data pool

XYZ are legacy bill docs; AB are new bill docs create in IS-U

X Y

Start of Installation Structureand / or DPC -> last real meter reading result

Move-in

B

X Y

EBF period

IS-U Database

A …...

EBF Data Pool(smaler customer table)

Installation in IS-U

Migration to IS-U

Installation-structure in IS-U

Z

allERCH

sub tables

Contract in IS-U

ZExxx

standard migrationbilling documents

new migrationof EBFdata pool

ERCH


Distinct reduced Migration Objects in EBF-Period

IS-U/CCSLegacy-System

Billing-Documents

Time-Schedule

Meter-Readings

Devices/Registers

Installation

Device

Register

Billing-Documents

Installation-Facts

Migration

MeterReading

Time-Schedule

Reasons

contractEBF-Documents


active Contract in IS-Uclosed Contract in IS-U

Installation in IS-U I-structure IS-UscenarioD

01.May 04

active Contract in IS-Uclosed Contract in IS-U

Installation in IS-U Installation-structure in IS-UscenarioC

01.May 0301.May 02

closed Contract in IS-U

Installation in IS-U Installation-structure in IS-UscenarioB

EBF periodView from Migration Key Date

01.May 00

Installation-structure in IS-U

active Contract in IS-Uscenario

A

Possible EBF Migration scenarios (samples)

Migration history since

time2000

Move-In Move-Out last Move-In

2001 2003

legacy contract (active)

n

legacy contract (closed)

legacy billingdocuments


EBF migration time line

standard migration process (partially)

additional EBF migration process

Installation (INSTLN)

active contract (MOVE_IN)

Install. structure (INST_MGMT)

BillDoc A

EBF-Doc Z

BillDoc B

EBFDoc X EBFDoc Y

time line

Never aEBF-objectbefore this

reference

hist. closed contract

reference

New migration objectto create „Historicalclosed contracts“

New migration objectto create reduced EFB

billing documents


New MIG-Object – MOVE_IN_H

MOVE_IN_H - Historical Insert of Contracts (Move-In /-Out)Historical insertion of finished contracts in pastCreation of Move-In and Move-Out documentsGeneration of Move-Out Billing-Trigger (for trigger bill)Basically copy of the migration object MOVE_IN (now with move-out date)


New MIG-Object – BILLDOCEBF

BILLDOCEBF – Load reduced BillDoc’s into EBF Data PoolUse formally and dependent checks for the document consistenceStorage of document headers into the operational database ERCHStorage of reduced billing line items into the EBF data poolPartially a copy of migration object BILLDOC (now with EBF line items)


Results of EBF migration

consistent data environment for installation (without a full installationstructure for contract 30000234

Installation 40000153contract 01.01.04 - **.**.** 30000233 active / with MOVE_INcontract 01.01.00 - 31.12.00 30000234 finished / with new MOVE_IN_H

consistent billing view of installationCorrect historical billing periods

Removed End-Billing Trigger from contract 30000234Displayable and correctable EBF Documents (with specific origin 10)








EBF Correction Process

CIC / IC integrationsimulationdisplaycreate

expandableown database fieldscustomer specific corrections stepsBusiness Add In

used as manual documentable to invoicereversiblechargeableprintable…

GETDocument Data

Call correctionmethod / steps

BAdI for add/delline items

save

Process central EBFcorrection SCREEN

Generate correctionproposal

(from customizing)

Display

SAVE ? yes

CorrectionProcess

(started from CIC)

Change Price(amount)and/or consumption

new bill doc

simulation

back

no


EBF Customer interface “Correction Screen”

CORRECTIONCORRECTION

SELECTIONSELECTION

HEADERHEADER


EBF Display single correction result

As result it exist an manual billing document, special marked as EBF-Document. Those manual billing document is able to invoice, reverse,display.


EBF Configuration

Customer correction methodAssigned correction steps per methodAssigned line item types for correction proposal








EBF available downgrades until ERP 2005

Downgrade for the ERP 2005 standard solutionof Easy Bill-Correction Framework (EBF) is available for:

IS-U 4.72- project based downgrade with options for enhancements- can be implemented remote

IS-U 4.64- project solution (less functionality compare to ERP 2005)


Contact

Do you have any questions?

Carsten Hoppe [email protected]. : +49 160 90 821 434

Uwe Haupt [email protected]. : +49 160 90 822 058

mailto:[email protected]

mailto:[email protected]


Recalculation for a part of the original period


EBF Workspace


Recalculation with a changed billing period


Recalculation with additional line items


Original period with new price and / or consumption


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 othersoftware vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®,Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

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

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and otherCitrix product names referenced herein are trademarks of Citrix Systems, Inc.

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

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other product and service names mentioned are trademarks of their respective companies.

Copyright 2002 SAP AG. All Rights Reserved