biller direct 6. from sap

5/20/2018 Biller Direct 6. From SAP

1/62

SAP AG 1

SAP AG 2005

mySAP ERP

Financial Supply ChainManagement

SAP Biller Direct 6.0

Application Solution Management

mySAP ERP Financials


2/62

SAP AG 2

SAP AG 2005

SAP Biller Direct Business Requirements

Agenda

User Management

Supported Business Processes

Various User Modes

Summary and Roadmap

Buy-side e-Invoicing (Payer Direct)

System Architecture and Deployment Options


3/62

SAP AG 3

SAP AG 2005

What is EIPP ?

Electronic: Electronic delivery and receipt using the Internet

and customer or supplier portals

Invoice: Display of invoices, payments and credits

Presentment: Presentation of account information via the

Internet&

Payment: Initiate payments, receive invoice and paymentstatus information

EIPP represents a way of presenting and delivering invoice andaccount information electronically from the biller to thecustomer.


4/62

SAP AG 4

SAP AG 2005

What are the Goals of EIPP ?

Cost savings

Through non-paper invoice processing, archiving, and streamliningof business processes

Improved customer contact

Through rapid communication between biller and recipient andprovision of self-service functions

Quality assurance

By avoiding manual errors in bill entry

Marketing instrument

Improved use of bills for sales and marketing purposes


5/62

SAP AG 5

SAP AG 2005

SAP Biller Direct - Commercial Factors

Bill creation

0.35-0.75 US$

Creation ofbill filePrintput in envelope

Cost savingpotential:7-15* Bill. US$

Dispatch

0.25-0.60 US$

Postage


Receipt ofpayment

0.20-0.60 US$

InformationprocessingPostingCustomer service


* Figures based on round 20 billion bills created in the US each year.

Source: PSW3/DMR

Payment ofCustomer

PaymentClearing


0.05-0.12 US$

These are four examples of steps in the billing process that are simplified by SAP Biller Direct, thereby

enabling cost savings.

They show the commercial potential of implementing SAP Biller Direct.


6/62

SAP AG 6

SAP AG 2005

SAP Biller Direct is part of SAP Financial Supply ChainManagement and provides functions for Electronic Invoice

Presentment and Payment (EIPP)

Using SAP Biller Direct, invoice recipients can see their accountbalance with the biller and look at their bills, credits or payments

Invoice recipients can initiate payments or download bills into theiraccounts payable system

Invoice recipients can dispute bills from the Internet andcollaborate with the biller

SAP Biller Direct enables real-time integration between the SAPbackend system and the Internet without any data redundancies

SAP Biller Direct What is it?


7/62

SAP AG 7

SAP AG 2005

Advantages for the Biller

Billing Lower cost of billing with no printing and postal charges

Use of open communication and data standards (HTTPS, XML)

Customer participation in electronic business without EDI

Payment Processing Efficient processing of payments and exceptions

More precise cash management and improved liquidity planning

Faster invoice approval and payments by customers

Better explanation of payment deductions

Integration Data integration with accounts receivable and cash management

Integration with other business processes, e.g. dispute and collectionsmanagement

Marketing Better customer retention (retaining a customer is five times cheaper than

acquiring a new one)

Competitive advantages through attractive service offerings

Opportunities for one-to-one marketing


8/62

SAP AG 8

SAP AG 2005

Advantages for the Bill Recipient

Payments

Simplified and secure processing of electronic payments using 365/24 accessto the Internet

Control over the time of payment and management of the outgoing cash flow

Favorable payment conditions can be better exploited

Payment details can be easily analyzed

Invoices

Fewer accounting and settlement errors

Comprehensive data analysis is possible

Immediate access to invoice copies (no archiving necessary)

Integration Upload of invoices into accounts payable, no reformatting of data necessary

No changes of existing business processes

Easy change of master data

Only Web Browser needed


9/62

SAP AG 9

SAP AG 2005



User Management


Various User Modes

Summary and Roadmap


Agenda


10/62

SAP AG 10

SAP AG 2005

Overview: Architecture of SAP Biller Direct

SAPApplication

Server

Open ItemsManagement

SAP FI-CA /SAP FI-ARDispute Mgmt.

SAP BillerDirectFront End(Java)

JCO

Firewall

BrowserWebServer

Firewall

SAP WebApplication Server

RFC

Transfer of

Bill Data

Billing Appl.(e.g. CRMBilling, SD)

Enterprise System Architecture

S

S

L

+

H

T

T

P

S

S

S

L

+

H

T

T

P

S

C u s t o m e r

B i l l e r

OpticalInvoiceArchive


11/62

SAP AG 11

SAP AG 2005

SAP Biller Direct Availability

mySAP ERP 2005 SAP NetWeaver 2004swith usage type AS-Java

R/3

SAP Biller Direct 6.0SAP Biller Direct 6.0

mySAP ERP 2004

SAP R/3 Enterpriseor

SAP R/3 4.6C

RFC

PIug-In2004.1

SAP Biller Direct 3.0 can be implemented both with mySAP ERP or older R/3 releases. To implement it

with lower releases a separate Plug-In is needed.

SAP Biller Direct 3.0 can be implemented in a one- or two-system scenario.


12/62

SAP AG 12

SAP AG 2005


Back End

The following components are available as back-end components

FI-AR (Accounts Receivable)

FI-CA

In addition, SAP Biller Direct has been integrated with the followingFSCM components:

SAP Cash Management (the cash management position and the liquidityforecast for released or paid bills is automatically updated)

SAP Dispute Management (customers can create dispute cases, view thestatus of the dispute case and can communicate with the disputemanagement department via notes)

SAP Biller Direct 3.0 customers can create dispute cases directly via SAP Biller Direct for both partial

payments or the entire invoice. The minimum system requirement for this scenario is R/3 Enterprise or

FI-CA 4.72.

The internal dispute processing can start immediately after the dispute case has been created in the SAP

backend system. If you want to activate Dispute Management you are unable to use the contact

management concept any longer.


13/62

SAP AG 13

SAP AG 2005


SAP Web Application Server

Comprises 4 components

Internet Communication Manager (ICM)

J2EE conform runtime environment

Conventional ABAP development and runtime environment

Integration and exchange infrastructure

Combines the advantages of the stable and widely available SAPBasis system with the advantages of the J2EE standard

Enhancement of SAP basis technology with open Internet protocollsand standards such as http, https, smtp, XML, SOAP

Enables the creation of interactive Web applications and XML basedmessage applications

Advantages Straightforward integration of external applications

Object oriented component development

Combined use of the SAP database for ABAP and Java applications

Reliability of SAP Basis system and security of existing applicationinvestments

Java 2 Enterprise Edition (J2EE) is a specification of Sun Microsystems, and is an enhancement of the Java 2

Standard Edition (J2SE) to develop and operate company-specific applications. This does not involve a compiler of

program language but rather a software framework comprising various components. In addition to the Java

Development Kit, a development environment of the programming language Java with compiler, debugger, and

applet viewer, J2EE includes a runtime infrastructure for the flow of applications and an enhancement of the

standard Java API for implementing distributed applications.

The Internet Communication Manager (ICM) is responsible for the connection between the Web application server

and external communication partners via intranets or the Internet. It can be used as Web server (external access via a

Web browser) as well as client (calls initiated from the Web application server). The ICM supports standard

protocols such as HTTP, HTTPS, SMTP or SOAP, and can therefore be used for processing Web services.

The J2EE runtime environment receives the requests from the ICM, processes them, and creates the answers

dynamically. The ABAP development and runtime environment is based on the tried and tested SAP Basis system.

All components that exist there, such as SAP business objects from the BOR (Business Object Repository) or their

methods (BAPIs), can be used for implementing the business logic.

The combination of ABAP and Java runtime environments opens up new possibilities for developers of interactive

Web applications. The presentation layer can be developed using JSP and Web screens. The Web screen will replace

the previous screen concept of the SAP system and clearly separate the presentation layer from the business logic. A

mix of JSP and Web screen is also possible. There are also several options for realizing the business logic: existing

SAP business objects and BAPIs or Enterprise Java Beans (EJB). Using EJB makes the components created on the

SAP Web application server compatible with other J2EE-based applications (continued on next slide).

The integration and exchange infrastructure supports numerous standards - for example, the XML-based SOAP

protocol for exchanging business information. In this way, Web services can be provided for other applications in a

heterogeneous system landscape or be seamlessly integrated. The SAP Internet Transaction Server (SAP ITS) is alsointegrated in the SAP Web application server and changes from a dedicated server to a function that is configured

within the SAP Web application server. This ensures the investment is protected.


14/62

SAP AG 14

SAP AG 2005


Presentation Layer

Structured according to the MVC2 (Model View Controller) approach,which separates the user interface from the business process logicand the data

JAVA ServerPages for the dynamic creation of HTML pages

HTML pages can be individually adapted according to customerbranding

Link between Front and Backend

SAP-specific communication protocol RFC and SAP Java Connector(JCO)

JCO: Toolkit for bi-directional communication between JAVA andABAP components

The JCO provides the Java developer with a class library to integrate ABAP components using this protocol. The

JCO is therefore a tool kit that enables communication between Java and ABAP components. In the course of this

the business logic remains in the SAP BAPI interfaces (Business Application Programming Interface). These are

methods for calling up business objects in the SAP System (for example, bills).

The JCO supports bi-directional connections between the Java and ABAP world, meaning that a Java client can call

up a BAPI interface in the SAP back end system and also an ABAP program on the Java server. It provides a high

performance JNI-based (Java Native Interface) RFC middleware and supports synchronous, transactional, and

queued RFC connections. In the future, it will also support the SOAP protocol (SOAP = Simple Object Access

Protocol). The JCO corresponds to the J2EE standard specification for the integration of ERP systems (J2EE

Connector API).

The Java part of SAP Biller Direct is used for the presentation layer. It is created in accordance with the MVC2

approach (Model View Controller), a generic design model that separates the user interface from the business

process logic and the data. JavaServer Pages (JSP) are used to create HTML pages dynamically. Just like Java

Servlets, JSPs are a method for creating the presentation layer of a Web application. They are therefore generally

used for the simple creation of the HTML and XML output of the Web server.

However, whereas servlets are application programs written in Java and are implemented in normal Java classes and

compiled in Java, JSPs are Java commands that are integrated in HTML documents. At runtime, a servlet is

generated from the JSP files and executed on the Web sever like any other servlet.

The MVC2 approach has the advantage that the JSP is completely decoupled from both the logic on which it is

based and the data storage, and the user can change the JSPs without affecting the logic and the data storage. This

approach also ensures that the JSP contains virtually no Java coding and can therefore be changed by Web designers

with no help from Java developers. Alternatively, customers can use the JSP standard design delivered by SAP and

change the Cascading Style Sheets that are delivered with this standard design to adapt the SAP Biller Directapplication to the company's own Internet page.


15/62

SAP AG 15

SAP AG 2005

Individual Look-and-Feel of SAP Biller Direct


16/62

SAP AG 16

SAP AG 2005

SAP NetWeaver Adoption of SAP Biller Direct

Do NEW things

Present bills electronically Enable business partners to

process bills online

Simplify reconciliation

Enable business partners to

edit master data online

Increase visibility for all parties

involved

Do things in NEW ways

Access on bills from anywhere,any time via an Internet browser

(J2EE)

Full integration always ensures

reference to correct business

objects

Internal Service Requests help to

execute master data changes in a

controlled way

Integration with EP and CRM

The Unique Value Of Innovation By SAP

+The business functionalityin SAP Biller Direct... Delivered In One Business Solution

The power of SAP NetWeaver

in SAP Biller Direct


17/62

SAP AG 17

SAP AG 2005

SAP Biller Direct

SAP NetWeaver

Features

Platform

SAP Biller Direct Powered By SAP NetWeaver

Manufacturing

Manufacturing

Execu

tion

Qualitiy

Management

Enterp

rise

AssetMan

agement

Environ

ment

Health&

Safety

Integration

NotificationConcept

MasterDataMana

gement

ProcessingModes

PayerDirect

mySAP ERP

Invoice Shorten ways of

bills and paymentsfrom and to

business partners

Direct processing

on original data (no

redundancies)

Simplify customer

communication by

operating in the same

view Portal implementation

of SAP Biller Direct

Notify Pay Dispute Reconcile Confirm

LDAP

LDAP Billing

Billing

FinancialAccounting

CRM

CRM

Process Integration

People Integration

SAP Biller Direct always uses the SAP NetWeaver components

J2EE

User Management Engine

SAP Biller Direct always uses as a back end

FI-AR or

FI-CA

Complete integration with the back end

SAP Biller Direct release independent from back end release

Flexible adaption of the interface to the invoice recipient

Flexible user management

SAP Biller Direct can be implemented in a Portal

SAP NetWeaver is an application and integration technology platform that helps unify and align people,

information and business processes across technologies and organizations; It is a comprehensive, best-in-

class, integrated technology based on an intimate and longstanding experience in developing mission-

critical business solutions in more then 20 industries. SAP NetWeaver helps leverage your existing IT

investment, today - and is the foundation for future, innovative cross-enterprise processes.


18/62

SAP AG 18

Open

A standards and Web-services based architecture that supports a heterogeneous IT landscape

Fully interoperable with .NET and J2EE environments

Built for business

Reliable, secure, scalable and geared to run mission critical applications

SAP NetWeaver, enables the Enterprise Services Architecture with the following capabilities:

People In tegration

Portal Infrastructure

Collaboration

Multi-channel access (mobile, voice, RFID)

I nformation I ntegration

Knowledge Management

Business Intelligence

Master Data Management

Process I ntegration

Integration Broker

Business Process Management

Application Platform

J2EE & ABAP engine

DB and OS abstraction

Composite Appli cation Fr amework

Solution L if e Cycle Management

Portal (I nf rastructure)

Combines industry leading portal technology with an unequalled depth and breadth of business content.

Drives efficiencies into business processes that span customers, suppliers, partners and employees. An

open, standards-based portal, mySAP Enterprise Portal brings collaboration, knowledge management and

role-based access to existing IT systems and Web Services. Through its support of Web-based, mobile

and wireless interfaces, the SAP Enterprise Portal provides an immediate enhanced return on existing IT

investments.

Collaboration

Collaboration room and real time collaboration capabilities that promote dynamic communication within

permanent and ad hoc teams or communities. Shared email, calendars, threaded discussion and document

stores are managed by local administrators who can independently update memberships and access rights.

Mul ti-channel access

Provides access to your enterprise systems via mobile devices, voice or RFID.

This key capability of SAP NetWeaver allows enterprises to extend their business processes to where

business occurs, thus leveraging their existing investment and enabling new user communities. Through

SAP NetWeavers Mobile Infrastructure companies can extend mission critical mobile business

applications to their users in either a connected or disconnected environment either utilizing SAPs ready-

made applications or developing their own via a standardized development framework.


19/62

SAP AG 19

Knowledge management

Open KM platform with user-centric services that provide a single access point to 3rd party repositories

and SAPs own content management systems that delivers integrated search, taxonomy, classification,

content management and publishing and the respective workflow processes.

Business I ntelli gence Platform

SAPs Business Intelligence platform is an end to end, solution for all of your BI needs. The scalable

architecture and open-standards-based technology enables organizations to integrate, analyze, and

disseminate relevant and timely information. It integrates data from various sources providing consistent

information for analysis quickly, in the right context, and at the appropriate level of detail. It also provides

a robust suite of BI tools to easily create and deploy customized, interactive reports and applications,

supporting decisions at every level throughout and beyond the enterprise walls.

Master Data Management

SAP Master Data Management enables information integrity across the business networks by the ability to

harmonize master data for business partners, products, assets, etc. across systems.

I ntegration Broker

In addition to enabling XML/SOAP based communication between application components from various

sources and vendors, the SAP Exchange Infrastructure includes the capabilities to define software

components, interfaces, mappings and content-based routing rules. This so called shared collaboration

knowledge represents meta knowledge or business semantics describing integration relevant facts based on

open standards

Business Process Management (BPM )

Business Process Management addresses the needs of modeling and driving processes in a dynamic

landscape. It allows combining underlying applications into adaptive end-to-end processes spanning the

entire value chain. It also enables ad-hoc creation and execution of workflows by end users.

Application Platform (J2EE and ABAP)Provides full support for platform-independent Web services, business Web applications, and open

standards-based development built on key technologies such as Java 2 Enterprise Edition (J2EE) and

ABAP. As a result, customers can leverage existing technology assets while building and deploying the

dynamic e-business applications and Web-service oriented solutions that drive today's collaborative

business.

Solution L if ecycle Management

Centralized technology for all stages of the solution life cycle, from design, development, deployment,

implementation, versioning and testing through ongoing operations like administration and change

management. Provides tools for developing, testing, and deploying Web applications through the entire

software life cycle.

Composite Appli cation Framework

Composite Application Framework is the factory in which xApps are built, many times, quickly and

easily. It contains the tools, methodology, rules and patterns that allow SAP and its partners to efficiently

develop xApps.


20/62

SAP AG 20

Unique Attributes

Most reli able, scalable and proven architecture

30 years of experience building business applications with 18,000 leading-edge customers and 50,000

installations. Combine this with native Web technologies such as Java/J2EE, XML, and Web services and

you get the industrys most scalable, and reliable infrastructure for running mission critical business

solutions

Only integrated platf orm to provide complete in formation integration

SAP NetWeaver integrates both structured data, with best-in-class business intelligence capabilities, and

unstructured data, with knowledge management capabilities. BI capabilities include a robust BI Platform,

a complete suite of BI Tools including reporting, analysis and information delivery, data warehouse

management and administration, and Extract, Transformation and loading (ETL). Knowledge

Management offers user-centric services that provide a single access point to 3rd repositories and SAPs

own content management systems. It delivers integrated search, taxonomy, classification, content

management and publishing and supports customized workflow processes.

Old Notes:

If you have SAP in your IT landscape, SAP NetWeaver is the most reasonable, cost effective, flexible,speedy solution to innovate while reducing costs. However, what most do not realize is that SAP NW is

also the preferred choice to integrate both SAP and non-SAP applications.

The justification for this is simple, a third party integrator needs to integrate both the 3rd party application

to the platform, plus the SAP application. However, the integration costs for SAP NW are cut in half,

because SAP NW needs to only integrate the third party application, SAP NW and applications come pre-

integrated

SAP has managed to accomplish this lower cost structure because we are committed to maintaining our

present standards participation, and we are built on open standards

The more SAP NetWeaver is used in an IT landscape, the more it increases customer cost savings.


21/62

SAP AG 21

SAP AG 2005



User Management


Various User Modes

Summary and Roadmap


Agenda


22/62

SAP AG 22

SAP AG 2005

Different Types of Users within Biller Direct

Web User

Pool User

ReferenceUser

Customer

BusinessPartner

Web user: the user who logs on via the Web browser and processes the data from there (for example, the

user of the business partner's accounting clerk who processes bills using the Web browser). No separate

roles/profiles are assigned to the Web user.

Reference user: a user in SAP R/3 who is assigned to the Web user, and to whom authorizations and roles

are assigned in SAP R/3 that the Web user has to have (transaction SU01). In SU01 you assign this user as

reference user. This way you can create a separate references user for reading accesses only, for example.

Pool user: is used for reading accesses (and in certain scenarios also for writing accesses) to SAP R/3

(improved control of system load and performance).

To manage Web users who display and pay their bills using SAP Biller Direct, you have to make certain

settings in the master data. You create three types of master records for this:

One user master record for each Web user: you need to create a user master record in FI-AR for each

Web user who is to access FI-AR.

Several reference users: for performance reasons, you should not assign the authorization profile to the

user master record of individual Web users directly, but assign them indirectly using reference users.

A pool user master record: this master record is used for read accesses to FI-AR. By bundling the Web

users who only execute display functions, you can improve performance with no risk of compromising

data security.

You can either assign one or multiple customers (FI-AR), one or multiple business partners, contract

accounts or contracts (FI-CA) to the web user.


23/62

SAP AG 23

SAP AG 2005

Pooled Versus Named Connections

Web User 1 Web User 2 Web User 3

SAP Application Server

ConnectionPool

SAP Web Application Server

All "read" accesses that do not lead to data changes in SAP R/3 are processed on the R/3 back end using

connection pooling. The Web application server manages the existing RFC connections to R/3. In

connection pooling, an RFC connection to the application server is not immediately disconnected when it

is no longer needed (for example, when a user has logged off); instead, it is stored in a pool of existing

RFC connections to R/3 and used for the next inquiry. This procedure has the following advantages:

Maximum performance, since the constant, time-consuming opening and closing of connections (logon

and creation of a role area in R/3) is no longer necessary

The burden on the R/3 back end is minimal.

The customer can set up the maximum number of connections on the Web server and therefore has

complete control over the maximum load on the back end as a result of Internet inquiries.

Pooled connections are therefore used by all Internet users that are logged on; they do not work under the

user logged on, instead they work under a service user (user name and password of the service user). This

service user is created once as a normal anonymous user in the SAP R/3 system and has its own

authorization profile. Note that all authorization checks are carried out on the authorization data of the

service user. This means that the service user must have all authorizations that permit the back end

processes for all users logged on (for example, all required company codes). It also means that the

authorization checks (for example, in events from customer enhancements) are made based on the

authorizations of the user logged on. System parameters (such as user name or language) do not have the

values of the user logged on, but rather those of the service user.

In order to map date and currency formats within texts, which are transferred from the backend to thelanguage of the web-user you can create per log-on language an own pool user.


24/62

SAP AG 24

In contrast, all "write" accesses that lead to database changes in the SAP R/3 System are executed via an

RFC connection under the user logged on for reasons of audit security. These include transactions such as

payment of bills, complaints, or stopping payment. This named connection creates a separate RFC

connection for each user of the SAP Biller Direct application. This connection only exists for the time of

the individual user action (for example, partial payment of a bill), and is then disconnected. This variant

ensures that all authorization checks are carried out under the user logged on and all change documents are

stored under the actual user. All user-specific system parameters are assigned the values of the user that is

logged on.

Compared to pooled connections, named connections use more resources such as network connections and

memory, since several users cannot share a named connection. The constant recreation of back end

connections and logging on to the SAP R/3 system makes the named connection slower than pooled

connections, and increases the load on the R/3 system. Using both access methods in the SAP Biller Direct

application represents a reasonable compromise between performance on the one hand, and security

requirements on the other. Most accesses are read accesses (for example, account display), and therefore

only require pooled connections. Named connections are only required for the rarer write accesses.


25/62

SAP AG 25

SAP AG 2005

User Log On SAP Biller Direct with mySAP CRM

Reference UserBusiness Partner / Customer

Biller Direct

Web User

Web User

Reference User

Business Partner / Customer

CRM

ERP

12

3

4

All Web users must be authenticated with CRM. The customers/business partners related to the Web user

are read from CRM. In addition to the customers/business partners, the assigned reference user (contains

only an authorization profile and is created as a reference user) is read from CRM (steps 1 and 2).

Using the reference user now recognized by the system, the authorizations from the mySAP ERP (or SAP

R/3 (Enterprise)) System are read (step 3) and processed in the Java front end (step 4).

All processing is now carried out using the pool user, as the Web user has only been created in the CRM

System in this scenario.

For performance reasons, access to the mySAP ERP System can be made using a pool user. So it is

possible to follow who made which changes in the mySAP ERP System and when, the name of the Web

user is transferred to the function modules in mySAP ERP. Information about users, function modules andso on is then saved.


26/62

SAP AG 26

SAP AG 2005

User Log On SAP Biller Direct without mySAP CRM

Web User

Reference User

Business Partner/Customer

ERP

Biller Direct

Web User

12

In this scenario the Web users have been created direct in the mySAP ERP (SAP R/3 (Enterprise)) System.

This means a reference user in mySAPERP is assigned to each Web user, and all Web users are

authenticated with the mySAP ERP system.

The user authorizations are saved in mySAP ERP and read and processed when logging on to the Java

front end.


27/62

SAP AG 27

SAP AG 2005

User Log On SAP Biller Direct with LDAP

ERP

Biller Direct

Web User

User-ID/Password

Reference UserBusiness Partner / Customer

LDAPData-

base

UME 4.0 (part of WAS 6.40)

2

1

4

3

Business PartnerCompany Code

Reference User

All web users must be authenticated with an external LDAP Server. The customers/business partners plus

company code and reference users belonging to the LDAP user are read from a separate database (steps 1

and 2).

Using the reference user now recognized by the system, the authorizations from the mySAP ERP (SAP

R/3 (Enterprise)) System are read (step 3) and processed in the Java front end. (step 4).

All these transactions are carried out with the pool connection, and the user name for "write" accesses is

always passed on and logged in the SAP system.

LDAP ist SAP's recommended solution for mapping a large number of users. LDAP (Lightweight

Directory Access Protocol) was developed as an open standard for global or local directory services in a

network and/or in the Internet. A directory is treated like a telephone book. The directories are designed tosupport a high volume of queries, but the data in a directory should not change frequently. LDAP can be

executed on a PC and via TCP/IP with no additional action required. Its specification is based on the

nomenclature of X.500, which is why LDAP is sometimes also called "X.500 Lite".


28/62

SAP AG 28

SAP AG 2005

Company Administrator

Company AdministratorXYZ AG

Company AdministratorUVW Inc.

User XYZ AG User UVW Inc.

Delegated user administration within the User Management Engine allows you to distribute user administration

between several administrators so that each administrator is responsible for a particular set of users.

SAP Biller Direct makes use pf this concept so that you can designate one user administrator for each company

which receives invoices from your enterprise.

By assigning users to companies, you divide them up into administrative sets. One or more administrators are

responsible for managing the users and their individual user authorizations in each company.

Each company administrator can only create, modify, and delete users that he or she is responsible for.

You must distinguish between overall user administrators and delegated user administrators:

Overall User Administrators can add, modify and delete users of all companies. They can create and administer

delegated user administrators and assign them appropriate roles and permissions. In addition the following taskscan only be performed by an overall user administrator:

- Group management

- Role management with permissions to assign all roles to all users and groups

- User mapping (SAP Enterprise Portal only)

- Import and export of user data

- Replication of user data

In the portal, overall user administrators are all administrators who are assigned to the Super Administration or User

Administration role. In all other cases, overall user administrators must belong to a role to which the

UME.Manage_All action is assigned. Delegated User Administrators can add, modify and delete users that belong to the same company as the

delegated user administrator. When they search for users, only users in their company are displayed. They cannot

perform any actions involving groups.


29/62

SAP AG 29

SAP AG 2005

Assignment Of Accounts In UME

Company administrators (delegated user administrators) can create, display and modify users in the User

Management Engine.

Company administrators are able to assign accounts to their users provided that these accounts have been

previously assigned to the company by the overall user administrator. To assign accounts, the company

administrator can click on the Maintain additional databutton of the user management screen. From an

account selection he can pick those accounts he wants to assign to the user.

In addition the company administrator can select from a list of authorizations and assign them to the users.

He can only pick from those authorizations that fit his authorization profile (which are equal or below his

profile).


30/62

SAP AG 30

SAP AG 2005

Additional Functions in User Management (1)

Active and Passive Enrollment

Customers can themselves log on to the Biller Direct Service

A biller can notify several customers of the service using a report in FI-AR or

FI-CA Change passwords

Various User Roles

SAP delivers a range of standard roles to which customers can assign therequired authorizations (using transaction PFCG)

Support for User Management Engine (UME)

Administration GUI is completely based on iViews

SAP Biller Direct makes use of several UME functions (Create, copy, modify,search users)

Support of Sub-Objects

Head-Office And Branch-Office

Bill-to/Sold-to


31/62

SAP AG 31

SAP AG 2005

Additional Functions in User Management (2)

Logging

Activities in the SAP R/3 back end that need to be logged have to bespecified

The retention period of logged entries can be specified

Reporting

All log entries for each user

All log entries for each document

Supported ISR Scenarios for SAP Biller Direct

Create or change bank details or payment cards

Request a new user Change address data

It is not possible to deactivate logging for individual users.

The expected data volumes relate to the number of log entries (size of a log entry: ca. 120 bytes). A

reorganisation job deletes log entries once retention period has expired.


32/62

SAP AG 32

SAP AG 2005


Agenda


User Management


Various User Modes

Summary and Roadmap



33/62

SAP AG 33

SAP AG 2005

List of Open Bills

Customers cansee all of theirbills and creditnotes

They can displaythe documentsas PDF, HTML orXML

They candownload billdata as PDF,XML or CSV

SAP Biller Direct

is tightlyintegrated withFI-AR or FI-CA(no separatedatabase)


34/62

SAP AG 34

SAP AG 2005

Invoice and Payment History

Customers cansee a history oftheir paymentsand invoices

Invoices andpayments canhave a differentstatus dependingon the backendprocesses

Scheduledpayments can becancelledprovided that nopayment run tookplace


35/62

SAP AG 35

SAP AG 2005

Payments

Customers can paytheir invoicesusing credit cardsor bank collection

(FI-AR)

Online credit cardauthori-zation andsettlement aresupported

Partial payments,offset with creditsand cash discountsare supported

When a customerhas paid aninvoice, a paymentmethod, bankdetails, or creditcard details areentered in the openitems that belongto the selectedinvoice

Customers can also schedule offline payments (check/bank transfers) in conjunction with FI-CA.

Partial payments lead to a real document split in FI-CA with two items one cleared and one open item.

In FI-AR a new open item is created with reference to the original item.


36/62

SAP AG 36

SAP AG 2005

Integration with SAP Cash & Liquidity Management

Customers candownloadinvoices in XML,PDF and CSV

format

Customers candirectly uploadinvoices in XMLand/or PDF intheir SAPAccountsPayables system

Documents areautomaticallyarchived andattached to theposted document

Customers donthave to scaninvoices anylonger


37/62

SAP AG 37

SAP AG 2005

Integration With SAP Dispute Management (1)

Customers cancreate disputecases for bothpartial payments orthe entire invoice

They can selecta reason code anddownload or uploaddocuments

An initial note forthe disputemanagementdepartment can beentered

They can select acontact person outof the customercontact list

The disputemanagementdepartment canreply to thecustomer


38/62

SAP AG 38

SAP AG 2005

Two-System Versus One-System Scenario

SAP R/3

Enterprise4.7

SAP Dispute

Management3.0

SAP WebAS 6.20

SAP Web AS6.40

ALE

SAP ECC 5.0(FI-AR)

SAP DisputeManagement

3.0

SAP Web AS 6.40

Synchronous Attachment

Asynchronous Attachment

It depends on the system landscape (whether SAP Dispute Management is implemented in a one- or two-

system scenario) whether the attachments are uploaded synchronously or asnychronously. In the second

case it might take some time until the attachments are visible in the dispute case.


39/62

SAP AG 39

SAP AG 2005

Invoice Upload in Accounts Payable

Customers canprovide theirbusiness partnerswith a download

of invoices (XML,PDF and/or CSV)

Its possible todirectly uploadinvoices (XMLand/or PDF) in theSAP AccountsPayables system

Documents areautomatically

archived andattached to theposted document

Accounting errorsare reduced

Scanning ofinvoices is nolonger necessary


40/62

SAP AG 40

SAP AG 2005

Display Balances and Line Items

Customers canview balance andline item infor-mation from FI-

AR (transactionFD11)

Download ispossible in CSVor Excel format

Access is to amonthly sum-marization and isseparated accor-ding to receivab-les and payments

The display of special general ledger transactions can be filtered using a Business Add-In.


41/62

SAP AG 41

SAP AG 2005

Open Item Display

Customers canview line itemdetail information

Customers candisplay accoun-ting documentsin HTML, PDF orXML

Customers candownloadaccountingdocuments inXML, PDF format


42/62

SAP AG 42

SAP AG 2005

Creation of Payment Advices

Customers canassign paymentsto invoices in andsend payment

advice notes tothe biller

The assigneditems can bechanged up untilthe point whenthe billersaccounting clerkhas processedthem

The responsibleaccounting clerkcan access thepayment advicenotes from hisSAP inbox

A frequent occurrence in business processes is ambiguity about the note to payee for incoming payments.


43/62

SAP AG 43

SAP AG 2005

Balance Confirmation

Customers can(not) confirmtotal balances

They can give noreply or specifyreasons why theycannot processthe balanceconfirmation

They can eitherprint the list ordownload it inExcel or CSVformat.

The returnedbalance compa-rison appears inthe inbox of theaccounting clerkassigned in theSAP system.

The balance confirmation function - a part of balance sheet preparation for the year-end - corresponds to

the activity of an accounts receivable accountant after receiving the request in paper form. This process is

mapped in SAP Biller Direct in electronic form and allows the customer to compare the current open items

with his accounting records in SAP Biller Direct.

This gives them the opportunity of analyzing the individual items, confirming or rejecting them and

commenting why, in order to explain any variances. The customer can also specify whether the balance

confirmation should be sent simultaneously to the external auditor.

The balance confirmation function is only available in FI-AR.


44/62

SAP AG 44

SAP AG 2005

Master Data

Customers candisplay andchange their

address, bank orcredit card data

They can grant orwithdrawautomatic debitauthorizations

They can modifytheir notificationpreferences

Users can be informed automatically about changes in their account:

FI-AR: Information using SD message determination

FI-CA: Information using print workbench events and correspondence

Transmission methods are e-mail including hyperlink to billers portal page or SMS. The required

components for notification from SAP systems are the certified system interface RDI, SAPConnect or the

SAP spool system


45/62

SAP AG 45

SAP AG 2005

Extended Configuration Management

Customers canconfigure theweb application

to their needs

Settings can bemade for the userinterface, theuser manage-ment and certainapplicationfunctions

Technical set-tings can bemade for poolconnections, theBusinessConnector andthe JCo-Server

To check which languages are currently supported by SAP Biller Direct have a look at the information

published in PPMS (alias PPMS).

Biller Direct is delivered with a variety of business-to-business and business-to-consumer functions. By

using the XCM administration tool (EXtended Configuration Management) you can easily set technical

and application specific settings on a web interface). A customer can create his own application and can

adjust the delivered configurations (SAP configuration) to his needs. Depending on the configuration used,

the application behaves differently during runtime.

A customer configuration consists of the following:

Configuration name

Base confiugration (the SAP configuration on which the customer bases his configuration)

A number of configuration parameters with associated values


46/62

SAP AG 46

SAP AG 2005


Agenda


User Management


Various User Modes

Summary and Roadmap



47/62

SAP AG 47

SAP AG 2005

Biller Direct Processing Mode

SAP Biller Direct can be operated in various modes

Biller DirectStandard Mode

Biller DirectAgent Mode*

Biller DirectCall Center Mode

Biller DirectBalance Mode

* only available with FI-CA


48/62

SAP AG 48

SAP AG 2005

Biller Direct Standard Mode

The standardmode covers allfunctions the

customer canuse via theInternet

Invoices andpayments aredisplayed in aline itemoverview form


49/62

SAP AG 49

SAP AG 2005

Biller Direct Balance Mode

The balancemode allowsusers to view

balances andtransactions

The account ispresented to thecustomer like abank account

Transactions arepresented on thescreen chrono-logically in total,including bills inprocess, paidbills, credits andpayments


50/62

SAP AG 50

SAP AG 2005

Other Biller Direct Processing Modes

Call Center Mode

Makes all the standard mode functions available

The option exists of integrating SAP Biller Direct as a Java-basedsubcomponent in a call center

The call center application can be expected to transfer the numberof the business partner to the Web application

Agent Mode

For integration with collection companies

All standard mode functions are available to an agent who collectsreceivables on behalf of your company

This mode is only available in conjunction with FI-CA


51/62

SAP AG 51

SAP AG 2005



User Management


Various User Modes

Summary and Roadmap


Agenda


52/62

SAP AG 52

SAP AG 2005


Architecture and User Management

Payer Direct uses the same architecture and user managementas SAP Biller Direct

It is integrated with FI-AP (Accounts Payable) and providessuppliers with an entire internet view on their account

There are currently no separate enrollment functions available

Presentation Layer Payer Direct can be deployed in two ways:

as business package, i.e. as iViews within a SAP Portal (e.g. in theSupplier Portal)

as stand-alone application on J2EE basis (like SAP Biller Direct) Payer Direct povides a web based HTMLB user interface.

HTMLB is a Java Tag Library developed by SAP and allows you to create browser-independent GUI

elements.

Customers who want to implement SAP Payer Direct and SAP Biller Direct on the same server need to

change the deployment description in the Software Development Manager.


53/62

SAP AG 53

SAP AG 2005

Buy-side e-Invoicing: Bills View

Suppliers cansee all of theirinvoices in-

cluding theirstatus (e.g. ifthey are paid ornot)

They can alsoview additionalpayment in-formation (e.g.check number)


54/62

SAP AG 54

SAP AG 2005

Buy-side e-Invoicing: Bills View

Suppliers cansee all of the pay-ments scheduled

by the payer(buyer)

They can alsoview a paymenthistory in orderto explain whichinvoices wereprocessed by thepayment


55/62

SAP AG 55

SAP AG 2005

Buy-side e-Invoicing: Credits View

Suppliers cansee all of hiscredits posted in

the payerssystem


56/62

SAP AG 56

SAP AG 2005


Agenda


User Management


Various User Modes

Summary and Roadmap



57/62

SAP AG 57

SAP AG 2005

Business Benefits

Lower cost of billing with no printing and postal charges

Efficient processing of payments and exceptions

More precise cash management and improved liquidity planning

Better explanation of payment deductions

Data integration with accounts receivable, accounts payable, cashmanagement and dispute management

Better customer retention

Opportunities for one-to-one marketing

Fewer accounting and settlement errors

Immediate access to invoice copies

No changes of existing business processes Productivity gain for A/R and A/P departments


58/62

SAP AG 58

SAP AG 2005

Availability

SAP Biller Direct 3.0 is part of the Ramp-Up for mySAP ERP 2004 /SAP FSCM 3.0

Ramp-Up has started in June 2004


59/62

SAP AG 59

SAP AG 2005

SAPFSCM 2.0

Roadmap SAP Financial Supply Chain Management

mySAP ERP 2004(SAP FSCM 3.0)

Ramp-Up

Q2/2004Release to Customer

Q3/2003

mySAP ERP 2005

(SAP FSCM 4.0)

Ramp-Up

Q3/2005(planned)


60/62

SAP AG 60

SAP AG 2005

SAP Biller Direct at SONY UK

SONY UK runs SAP Biller Direct

Enables self-service for dealer network

Rapid implementation: 30 days Reduces call center volume for account

status by 30%

Enables greater focus on cash collections

and dispute resolution

SAP Biller Direct augments our dealer portal withinvoicing and account management capabilities. Now, our

dealers have better visibility of account status and abilityto make payments electronically. This has enabled ourcustomer accounts team to focus their time on collectionsand dispute resolution, which will ultimately have apositive impact on cash flow.

Matthew Jepp, General Manager, Finance

Applications, Sony Information Systems & Solutions

Europe


61/62

SAP AG 61

SAP AG 2005

SAPNet

Service Marketplace

Public Web:

Use ALIAS: FSCM or erp-financials

Direct Contact:

mySAP ERP Application Solution Management

Further Information


62/62

SAP AG 62

SAP AG 2005

Copyright 2005 SAP AG. All Rights 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, Outlook, and PowerPoint are registered trademarks of Microsoft 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, 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.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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.

This document is a preliminary vers ion and not subject to your license agreement or any other agreement with SAP. This document contains only intended

strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, productstrategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,

links, or other items contained within this material. This document is provided without a warranty o f any kind, either express or implied, including but not limited

to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use

of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the useof hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party

Web pages.

biller direct 6. from sap

Documents

sap ag

billersap biller

data redundanciessap

electronic business

initiate payments

invoice andaccount information

nonpaper invoice processing

electronic invoicepresentment