cg crm billing internal trng 30.10.09

5/28/2018 Cg Crm Billing Internal Trng 30.10.09

1/68

India SAP CoE, Slide 1

CR71010 -CRM BillingSAP CRM 7.0


2/68


CRM-2007Billing System Landscape


3/68


CRM & R3 Billing for CRM & R3 Transactions

1 PrepareMe

2 TellMe

3 ShowMe

4 LetMe

5 HelpMe


4/68



1 PrepareMe

2 TellMe

3 ShowMe

4 LetMe

5 HelpMe


5/68


Purpose

Billing is an essential part of Sales and Service

processes.

Billing comprises the collection of billable items inthe billing due list and the functionality to invoicethis data, producing billing documents that are

transferred to accounting.

On time, Accurate and Effective Billing process ,ensure good financial health of an Enterprise.


6/68


Use

The Billing function can handle generating invoices (Normal, Corrections

& Cancellation invoices, Debit & Credit Memos) for Order and Deliveryrelated transactions. This results in on time payment collections and alsoin settlement of customersgrievances.

You can use CRM Billing to combine Service order items and Salesorder items in the invoices. This simplifies communication with your

customers.

Billing

due

listBilling

docu-

ments


7/68


Challenges

Receiving timely payment from customers for delivered productsand services as well crediting the customers for their claims, areincreasingly critical to revenue, profitability and customer loyalty.This is especially true in environments where competition is

intense, costs are rising and margins are dwindling.

By deploying technology such as Integrating ERP packages,legacy systems, On line Billing intimation and collection optionsthrough Internet , mobile devices, leading companies around the

world are dramatically improving service capabilities,competitive differentiation and corporate performance.


8/68



1 PrepareMe

2 TellMe

3 ShowMe

4 LetMe

5 HelpMe


9/68


Billing Process Overview

.

The whole billing process comprises three major steps

Input Processing


10/68


Billing Process


11/68


Billing Execution


12/68India SAP CoE, Slide 12

Output Processing



Billing Options: Billing Plans



Billing Process Overview

The process flow for creating and issuing invoices using the CRM Billing can bedivided into four sub-processes:

Input Processing Billing

Cancellation

Output Processing

During Input Processing, CRM Billing takes over billing-relevant items from differentbusiness transactions and saves them as billing due list items.

As of CRM Release 5.0, you can use an external interface to copy data from non-SAP systems to the CRM Billing due list. It supports the formats IDoc; XML SOAP

via HTTP; XML via SAP NetWeaver Exchange Infrastructure. From the billing due list, you can process both single and collective billing from

billing due list items and also trigger these to run in the background.

During billing, related billing due list items are also grouped together as far aspossible from different CRM business transactions and transferred to a joint billingdocument.

You can cancel individual billing documents and also execute collective

cancellations. The system transfers information on cancellations automatically toFinancial Accounting.

Output processing is made up of invoice output, the transfer to SAP FinancialAccounting and retrieval for SAP BW. You can choose from different output media(for example, print, fax or email) for invoice output, although output takes placeusing SAP Smart Forms.The ledger posting of billing data takes place either in SAP FI-A/R or in SAP FI-CA.CRM Billing provides all relevant billing data for the SAP Business Warehouse for

statistical reporting.



CRM Billing Imp Concepts

Billing Unit

The billing unit is the organization in a company that handles thebilling processes for the business partners involved in the sale.

Its tasks include, among others, receiving and handling complaints.

In the invoicing process it is used, among other things, to select billingrequest items and it effectively determines grouping in invoicing.

In Intercompany Billing scenario also it plays important role.

Convergent billing:

Convergent billing is the integration of all service charges onto a single

customer invoice e.g. Many Service confirmations billed together.



CRM Billing Imp Concepts:Billing Relevance

The billing relevance defined at item level in the business

transaction drives the billing process.

It controls:

When billing data is transferred to the billing due list

(for example, after saving or in the case of a specific status)

Whether the transaction or the delivery triggers billing

Where billing takes place: either within CRM or R/3 SD

In transaction-relatedbilling, the business transaction provides

all data necessary for billing

Selection of billing due items via transaction number

Used, for example, for service orders and contracts

In delivery-relatedbilling, a combination of delivery and transaction

data feed the billing process

Selection of billing due items via delivery number

Used, for example, for sales orders



CRM Billing - Master Data & Services

CRM Billing uses existing master data entities for:

Business partners Prices/conditions

Organisational units

Products

Services used by CRM Billing are:

Partner Processing Pricing

Text Processing

Action Processing: Printing and other output actions by using thePost Processing Framework (PPF)

Transfer to accounting (FI-A/R and FI-CA)

BW adapter



CRM BillingPre-Requisites

General :

Number Range, Master Data, Pricing Procedure, Tax configuration,

Middleware, G/L setting, No Billing Block, Billing Type, Billing Relevance

Item Category and Copy Control etc. should have been maintained

For CRM Billing :For Service Items the status should be confirmed,

For Billing Plan the due date must be due

For Delivery related CRM Billing ,PGI should have been done and the

relevant status must be updated in CRM

For Delivery related R3 Billing for CRM Orders:Order should pass correctly from CRM to R3 PGI should have been

done.



Key Billing Functionality available in CRM7.0

Transaction-related and delivery-related billing

Complete integration with preceding processes (business transactions anddeliveries)

Complete integration with SAP Financials

Provision for SAP Business Intelligence

Billing of Complaints (Credit / Debit memos)

Cancellation Direct billing

Milestone billing and Periodic Billing Plan

Intercompany processing

Supplementary invoices

Invoice split

Differential invoicing

Support of foreign trade processes (e.g. GTS, Extrastat, Intrastat Reports)

External interface for billing due list

Individual configuration of billing application



SAP R/3

SAP CRM

Example: Delivery-Related CRM Billing Flow

7

6

Goods Issue5

4

Sales order

2

CRM Billing

Billing

due list

2a

9Sales order

Product Quantity

Book 12 pc.

1

Invoice

8

Delivery3



Example: Service Process CRM Billing Flow Prerequisites: The service process has the status Released. You have

made the settings necessary for copying control and have entered the date

type SRVC_ACTUAL (start of work/end of work) in the date profile.



CRM Billing Confirmation without Service

Process Order :

Example: A customer asks a service employee, who is on site due toanother order, to perform a repair. Because the device failed only an hourago and therefore, the customer has not yet reported the problem, there isno existing service process from which the confirmation can occur. In thiscase, the service employee can perform the repair and subsequently createa confirmation. In this way, the working time and spare parts required for therepair can be invoiced to the customer.



Amount Allocation to CO for Service Order



SAP CRM

Example: Service Plan Billing Flow

CRM Billing

Billing

due list

2

Service order

Service Quantity

Support 100 hr/pm

On Billing Due Date

1

Invoice

8

CRM Billing

Billing

due list

2



Billing PlanExample: Periodic Billing

You can see the billing plan in a business transaction on the billing plan tab

page. The system creates billing due list entries for every billing request item from

the billing plan.

Once the billing date of a billing request item (BRI) is reached, the system

creates a billing document.

Service Contract

Sold-to party:Miller Inc.

Billing plan:Periodic billing

Billing request items (BRI):

31. Jan. 2.000 USD

28. Feb. 2.000 USD

31. Mar. 2.000 USD

Validity period:Jan. - March

Billing date:End of month

Billing Due

List

Entries

Invoice 1

Miller Inc.31. Jan.

2.000 USD

Invoice 2Miller Inc.

28. Feb.

2.000 USD

Invoice 3Miller Inc.

31. Mar.

2.000 USD



A billing plan is a schedule of individual billing dates

for a product or a service.

Periodic billing:

Bills the same amount at regular intervals

Can be used, for example, for maintenance or leasing contracts

Milestone billing:

Bills different amounts on predefined dates

Can be used for items in high-value projects or long-term projects(for example, plant engineering and construction)

Billing Plan- Periodic & Milestone Billing

1st milestone 1. April 20% 2.000 USD

2nd milestone 31. Mai 40% 4.000 USD

Final invoice 30. June 40% 4.000 USD

31. Jan. 2.000 USD28. Feb. 2.000 USD

31. Mar. 2.000 USD



Supplementary Invoice The system creates an additional entry in the billing due list, if a partner with the

partner function bill-to party (supplementary invoice) exists in the original

transaction. This scenario is useful for example when one may be required to send

a copy of invoice to Group companyanother Bill to Party showing only Product

Price without Freight, Tax and other charges-with NO Posting to FI being done.

The system carries out a partner determination for the copied item.

The system carries out pricing for the copied item.

Only the customer invoice is provided to Financial accounting for furtherprocessing

Invoice 1

Miller Inc.

1.200 USD

Invoice 2

SLC Inc.

1.100 USD

Financial

accounting

Financial

accounting

Service order

Bill-to party:

Miller Inc.

Bill-to party

supplementary

invoice:

SLC Inc.



The invoice split is triggered by the condition type and by a flag

in the business partner master data (payer).

The system then creates an additional entry in the billing due list.

The invoices are handled separately in all following processes.

Invoice Split Using Conditions

You can split the net value of an item into two invoices.

Invoice 1

Price 100 USD

Invoice 2

Freight 20 USD

Financial

accounting

Financial

accounting

Order

Price: 100 USD

Freight: 20 USD


29/68


Differential Invoicing

Complaint

Product 1 8 pc 800 USD

Invoice 1 (Original Invc)


Differential Invoice


Product 1 10 pc -1000 USD

-200 USD

Differential invoicing allows invoice corrections to be generated from

complaints. A value or quantity change in a complaint can trigger thecreation of a correction document.

Shortage Complaint

Quantity 8 Received

Original Invoice Quantity Credited back in Full

Received Quantity is Charged


30/68


Direct Billing

Via direct billing, a billing document can be

created directly, without the intermediatestep of initiating billing via the billing due

list:

Direct billing is triggered by a flag in the

business partner master data (payer)

Incomplete or blocked due list items are

excluded from direct billing

If an error during billing occurs, the item can be

found in the billing due list

You can also use a Business Add-In (BAdI) to

trigger direct billing


31/68


Intercompany Billing Flow

Sales org.

Germany

Company

Germany

Delivery plant

New York

Company

US

Customer

Order

Customerinvoice

Intercompany

invoice

Delivery

Intercompany billing: A process for internal invoicing in the case

that the sales organization and the delivering organization of an enterprise

belong to independent accounting units. This happens mostly in delivery relatedbilling, but can happen in service related billing also where actual service is

rendered by sister company for Service Order created by sister company.


32/68


Information on Intercompany Billing

UseYou use intercompany billing if both of the followingapply:

1. A product/ service is delivered by a unit other than the

seller.

2. The seller and supplier of a product are in the same

enterprise group, but in different Company Codes

Intercompany billing enables the supplier to bill the seller in

the above scenario.

The system automatically recognizes a case of intercompany

billing when a supplier is entered in the order that has a

different company code from the seller.


33/68


Intercompany ProcessingCharacteristics

System automatically determines whether vendor belongs to

different billing organization than sales organization

Supports transaction and delivery-related intercompany

processing

Creates two or several billing due list items:

one for customer invoice and one or more for intercompanyinvoice(s)

Within direct delivery billing, integration with controlling

provides determination for the profit center of the delivering

party, and booking of cost of goods issued and revenue tonew accounts.

During the creation of a billing due list entry for an

intercompany invoice, prices and partners are redetermined.


34/68


Multi-Level Intercompany BillingMulti-level intercompany billing: For a given intercompany-relevant

transaction, a chain of intercompany billing documents is derived to allow a

general multi-level intercompany process.

Sales org.

Germany

Company

Germany

Delivery plant

New York

Company

US

Intercompanyinvoice 2

Customer

Order

Customer

invoice

Delivery

Company

holding

Paris

Intercompanyinvoice 1


35/68


Cancellation of Billing Documents

Cancellation

document

Billing due

list entries

Financial

accountingBilling

document

Status:

canceled

In order to reverse the billing process you can cancel billing

documents.The system does the following:

Changes the billing document (status: canceled)

Generates cancellation document (to reverse postings in FI)

Creates new entries in billing due list


36/68


External Due List Interface

The external due list interface is a XIF interface for the billing due list.

The interface can be used to transfer external data to the CRM billing

due list (for example, transfer of items to be billed from an external

order entry or delivery system).


37/68


Integration with SAP Financials

The system transfers billing documents to SAP FI in order

to post them as open items.

Features are:

Status and error handling in billing documents to control transfer

to accounting

Possibility to separate the creation of a billing document from its

transfer to accounting Flexible account determination, either based on single mapping

table

or on condition technique

Can be connected either to SAP R/3 FI-A/R or SAP R/3 FI-CA

Sales transactions transfer the controlling attributes and plannedvalues (incoming sales orders), whereas billing transfers the actual

values (sales volume) to SAP R/3 FI-CO

Middleware controls the connection between billing and accounting


38/68


Differences between Billing in CRM vs. ERP

CRM: Convergent billing based on collected items

CRM: Import of external billing relevant data

CRM: Multi-level inter-company billing (Spare-Parts Scenario)

CRM: Supplementary invoicing (via partner based derivation)

CRM: Condition split

CRM: Flexible Billing application generation to streamline

performance

ERP: Editable header conditions e.g. Freight Conditions

ERP: Display of archived billing documents

ERP: Standard payment card support ERP: Enhanced Revenue recognition support

ERP: Down payment support


39/68



1 PrepareMe

2 TellMe

3 ShowMe

4 LetMe

5 HelpMe


40/68


Configuration of Billing Applications

You can configure your billing application and adapt it

to your needs by activating additional features, suchas:

Advanced item category determination

Enhanced account determination

XIF connection (inbound processing) CRM integration to contract accounting (FI-CA)

Supplementary invoice

Invoice split using conditions

Multilevel intercompany billing

Foreign trade connection (GTS)

Enhanced attributes for pricing

Localization (country-specific functions)


41/68


Customizing Settings for Billing

The following customizing settings are necessary:

Define settings for basic functions/services used by CRM Billing: Settings for pricing (pricing procedure)

Settings for partner processing (partner-determination procedure)

Settings for action processing (action profile)

Settings for text processing (text-determination procedure)

Define number ranges for billing documents and collective runs Define billing units and assign them to sales/service organizations

Define the billing relevance of transaction item categories

Define billing types

Define item categories for billing

Make settings for item category determination in billing Make settings for all additional functions you want to use (for

example, intercompany billing and supplementary invoice)


42/68


CRM Billing: Native Customizing

CRM Billing native customizing

Number Ranges

Item Categories

Billing types

Item Category Determination


43/68



IMG: SAP Implementat ion Guide Customer Relat ionsh ip

Management Master Data Organizat ional ManagementCross-System Ass ignment of Organizat ional Uni ts Ass ign

Bi l l ing Units to Sales Organizat ion

Find out that a Billing Unit Sales US Billing Unit is assigned to your

Sales Organization 50000609 (US Sales & Service).This billing

unit should already have been created as Business Partner inCRM to represent as Company code in R3.


44/68



Assign Company code to Billing Unit / and Business Place. It

means One Billing Unit to One Company Code like One Sales Orgcan be assigned to One company code only but one company

code can have multiple Billing Unit. There will be intercompany

sale when 2 Billing unit (Through their Sales Org Assignment )

assigned to different company code make sale to each other.

Business Place is tantamount to Plant mostly used by FICO for

Payment and Tax collection .


45/68


Configuration for Billing TypeCheck whether the bi l l ing typ e e.g. F2 has the pro per entr ies

IMG: SAP Imp lementat ion Guide Custom er Relat ions hip Management Bi l l ing

Def ine Bi l l ing Types

Highlight F2 / ZFSC Invoice and press Details.


46/68


Customizing for Sales Item Category

Related Customizing in CRMtransactions

Transactions Item Categories

Relevance for Billing


47/68


Configuration for Billing Item Category Ass ign yo ur new Item Category to you r sourc e Process Category ZAXX and

sou rce Item Category TAN from your Transact ion Type.

Save your assignment.

IMG: SAP Imp lementat ion Guide Custom er Relat ions hip Management Bi l l ingDef ine Bi l l ing Category (This helps in determin ing Item category and Pric ing

Procedure at the t ime of Bi l l ing )


48/68


Determination of Billing Item Category Ass ign yo ur new I tem Category to yo ur sou rce Process Category ZAXX

and source Item Category TAN from you r Transact io n Type.

Save your assignm ent. IMG: SAP Implementat ion Guide Customer Relat ionsh ip Management

Bi l l in g Item Catego ry Determinat ion As sign Item Catego r ies

This Source

ProcessMeans Source

transaction e.g.

Order / Contract

Transaction type

and the Source

Item Categoryrefers to Item

Category

assigned to the

Source

Transaction type.


49/68


Billing PlanCustomizing

Customizing of billing plan:

You define billing plan type(s)

You define customer billing plan procedure(s) and assign it to

customer master data

You assign billing plan type to the business transaction or to the

item category (dependent on billing plan procedure)


50/68


Info on Supplementary Invoice

Use You can use this functionality to copy a billing due list entry during creation. It

can, for example, be used to create another invoice for an order or delivery. The

second invoice, which is based on a copy of the original billing due list entry,

contains different partners and different prices.

Activities

1.Check whether the predefined partner access sequence 1004 meets your

requirements. You will find the definition for the access sequence in the IMG, under Customer

Relat ion sh ip Management -> Basic Functio ns -> Partner Proc essing -> Define

Acc ess Sequences. The predefined access sequence has the following settings:


51/68


Info on Supplementary Invoice

Activities

2. If it meets your requirements, use partner determination procedure 100009.

3. In order to use other conditions for the copied billing due list item, you should

create a pricing procedure that only creates the conditions that are relevant to the

copied item. Assign this procedure to the billing item category and the billing type

for the supplementary invoice. This means that you should definitely create your

own billing type to be used for the copied billing due list item. Make sure that youdo not select the "Copy Determination Procedure" indicator in the billing type.


52/68


Controlling Invoice Split Through Conditions

ActivitiesIMG under CRM -> Bil l ing -> Invoice Spl i t via Cond it ions


53/68


CRM Billing: Integration with FICA Related Customizing in CRM for

Account DeterminationMenu

path


54/68


CRM Billing: Integration with FICA

The G/L determination takes

place based on :

1-Condition type

2-Distribution channel

3-Division

4-Product account group

5-Country (of invoice recipient)


55/68


Additional Customization Settings

Configuring the Billing Application


56/68


View Sales Order and its Output on WEBUI


57/68


Input ProcessingBilling Due List

Transactions relevant

for billing: For example,service order, contract,

and delivery

Billing due list:

Billing due list items

Organizational data:

Determines the billing unit

Partner data:

For transferring and filtering businesspartners

Pricing conditions:

For transferring pricing conditions

Text data:

For transferring texts

The billing due list receives the billing-relevant data from preceding

processes, supplements it with customizing data and master data, checks it,

and saves it in the form of a billing due list item.


58/68


CRM Billing - Billing Due List(BEA_DL_01)


59/68


CRM Billing - Billing Document Overview

Initiate Cancellation ViewError LogDocumentStatus

CRM Billing Billing Document


60/68


CRM Billing - Billing Document

Header Details

Document Flow

Access CRM


61/68


Output Processing

The billing capability uses action processing

(post processing framework PPF) for creating the output.

CRM Billing enables invoice output

through various media:

Printer

Fax

E-mail

Optical archiving

External printing channels

You can output customer invoices:

Automatically after the billing documents have been created

Periodically (for example, at the end of a week or month)

Manually


62/68


View CRM Bill and its Output on GUI


63/68


Search Billing Doc on WEBUI of CRM7.0


64/68


Detail View Billing Doc on CRM 7.0-WEBUI

CRM & R3 Billi f CRM & R3 T ti


65/68



1 PrepareMe

2 TellMe

3 ShowMe

4

LetMe

5 HelpMe


66/68


LetMe

Important Transaction Codes

BEA_BTY Maintain Billing Types

CRMD_ORDER Transaction Processing

VA01/2/3 Create / Change/ Display R3 Sales Order

VL01/2/3N Create / Change/ Display R3 Delivery

VF01/2/3 Create / Change/ Display R3 Billing

BEA_BD_01 Maintain Billing Documents

BEA_DL_01 Maintain Billing Due List

CRM & R3 Billi f CRM & R3 T ti


67/68



1 PrepareMe

2 TellMe

3 ShowMe

4

LetMe

5 HelpMe


68/68

Explore Innovate ShareSAP CRMWiKi

https://wiki.wdf.sap.corp/displa

y/SAPCRMHub/Home

SAP CRM - Help Portalhelp.sap.com/CRM

SAP Public Web

http://www.sap.com/crm
http://service.sap.com/rkt-crmhttp://service.sap.com/rkt-crmhttp://service.sap.com/rkt-crmhttp://service.sap.com/rkt-crm

cg crm billing internal trng 30.10.09

Documents

crm r3 billing

billing options

billing documents

billing process overview

effective billing process

billingrelevant items

india sap coe

line billing intimation