SAP, SAP ISU, SAP Technical, Uncategorized

SAP IS-U Price Transport Control

Most of you working on SAP IS-U project as billing consultant knows the fact that managing and transporting Billing Master Data is a bit tricky.
There are standard tools provided by SAP to move these efficiently across Development -> Quality -> Production, few of them are below:
EA_TRANSPORT – Complete Transport
EA_DOWNLOAD – Download Selective Master Data
EA_UPLOAD – Upload Selective Master Data
Where from the source system you execute Complete Transport which will ask for a new Request and this will be used to move to target system.
Again under EA_TRANSPORT (or EQ82) there is an option to include the Price and Discount changes as well. There are Price-only transports like EPRICE_UPLOAD, REA_PRICE_DOWNLOAD, REA_PRICE_UPLOAD available which can also be referred.
Advertisements
Custom idoc, idoc creation, SAP

Steps for Creation of Custom IDoc:

There are basically two types of IDOCs: (a) Basic IDOCs (b) Extended IDOCs

Basic IDoc Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extension IDoc Extending the functionality by adding more segments to existing Basic IDOCs.

Steps for Creation of Custom IDoc:

To Create IDoc we need to follow these steps:

1. Create Segment ( WE31)

2. Create IDoc Type ( WE30)

3. Create Message Type ( WE81)

4. Assign IDoc Type to Message Type ( WE82)

 

1. Creating a Segment

a) Go to transaction code WE31

b) Enter the name for your segment type and click on the Create icon

c) Type the short text

d) Enter the variable names and data elements

e) Save it and go back

f) Go to Edit -> Set Release

g) Follow steps to create more number of segments

2) Create IDOC Type

a) Go to transaction code WE30

b) Enter the Object Name, select Basic type and click Create icon

c) Select the create new option and enter a description for your basic IDOC type and press enter

d) Select the IDOC Name and click Create icon

e) The system prompts us to enter a segment type and its attributes

f) Choose the appropriate values and press Enter

g) The system transfers the name of the segment type to the IDOC editor.

3) Create IDOC Type

a) Follow these steps to add more number of segments to Parent or as Parent-child relation

b) Save it and go back

c) Go to Edit -> Set release

4) Create Message Type

a) Go to transaction code WE81

b) Change the details from Display mode to Change mode

c) After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

d) Click New Entries to create new Message Type

e) Fill details

f) Save it and go back

5) Assign Message Type to IDoc Type

a) Go to transaction code WE82

b) Change the details from Display mode to Change mode

c) After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

d) Click New Entries to create new Message Type.

e) Fill details

f) Save it and go back

 
deregulation, POD, SAP, SAP ISU, Utility

SAP IS Utility : Deregulation Terminology

 Abbreviations:
NB service Non-billable service
CRN Cross-reference number
 Definitions:
Advance payment          Procedure whereby the billing agent pays the service provider for the
Outstanding receivables, even if the customer has not yet paid the billing agent. The billing agent owns the receivables from the customer once they have been invoiced in IS-U.
Bill ready                          Bill creation process performed by the service provider, in which they are the owner of the receivable. The bill covers services performed by the service provider as well as services from any third parties involved. The bill is transferred to the billing consolidator, who is responsible for bill payment. This means the customer receives one bill for all service types.
Billing agent                     Service provider who creates bills and monitors incoming payments both for services they provide themselves and for services provided by third parties.
Receivables for which the customer is billed on behalf of third parties are forwarded directly to the third party and do not appear (as revenue) in the billing agent’s general ledger.
Billing consolidator          Service provider who bills the customer for several services. This is an
Umbrella term for billing agent and sole provider.
Customer payment     Procedure whereby the billing agent only pays outstanding receivables to the service provider once the customer has paid the outstanding receivables to the billing agent.
Deregulation scenario Description of a valid relationship between service providers in the
 Deregulated market. To simplify matters, the scenarios are not always described in full in this documentation. For example, when a sole provider scenario is mentioned, it is not clear whether the sole provider is the distributor or the supplier, or when a billing agent scenario is mentioned, the scenario may involve a bill ready or rate ready procedure with advance payment or customer payment. If the exact scenario is irrelevant in a particular context, general references like these are used.
Grid                                   Object in the IS-U System that corresponds to a distribution grid or part of one.
Rate ready                       Bill creation process and bill payment by the billing consolidator on behalf of the service provider who is the service owner.
The billing consolidator must have access to all the necessary data (for example, rate data) in order to create the bill.
This means the customer receives one bill for all service types.
Service provider              Company that provides, for example, one of the following services
(Service types):
·        Energy generation
·        Energy purchasing
·        Energy switching
·        Energy distribution
·        Meter installation and maintenance
·        Meter reading
A service provider is assigned one service type.
Sole provider                   Service provider solely responsible for all services, from the customer’s point of view. The sole provider is also the owner of third-party Receivables from the customer. All receivables for which the customer is billed are listed as revenue in the sole provider’s general ledger.
Templates                        SAP provides predefined programs and workflows for some process
Flows. These are supplied as templates.
SAP delivers the following templates:
·        IDocs
·        Programs for entering data in IDocs for outbound messages
·        Programs for reading IDocs for inbound messages and subsequent
Processing
·         Workflows for more complex process management
Point of delivery               Point at which a utility service is performed or determined for a customer. A point of delivery has one (or in some cases no) external number (point of delivery ID) at one time.
A point of delivery is used for:
·        Communication in automatic data exchange (deregulation
·        point of delivery)
·        Exchange of meter reading results (technical point of
·        delivery)
·        When exchanging meter reading results, the technical point of delivery
·        has the following categories:
·        Standard point of delivery

·        Virtual point of delivery
2015, Billing, ERP, FICA, Industry solution form SAP, ISU, POD, SAP, SAP FI, SAP ISU, SAP ISU Transactions, SAP Technical, t code, Utility

Important Tables in SAP ISU:

Master Data:

EKUN  ISU business partner data
BUT050  Business partner relationships
BUT100  Business partner roles
BUT020  Business partner address
ADRC  Addresses
BUT000  Business partner
DFKKLOCKS  Business locks
FKKVKP  Contract account for partner
FKKVK  Contract account

 

Billing and Invoicing:

ERDK  Print doc header
ERDO  Outsorting for invoices
ERDB  CA document for print document
ERCHO  Outsorting for billing document
ERCHC  Invoicing reversal history
ERCH  Billing doc header
DBERCHZ (1-8)  Billing doc lines
DBERDL  Print doc lines
DBERDLB  Billing doc-print doc line reference

Billing master data:

ETTA  Rate category
ETTAF  Rate category facts
TE221  Operands
ETRF  Rates
EKDI  Rate facts
ESCHS  Billing schema steps
ESCHS  Billing schema header
EPREIH  Price history
EPREI  Prices header
TE069  Rate types
ETTIF/ETTIFN/ETTIFB  Installation facts
ERTFND  Rate determination

 

Technical master data

EANL  Installation
EVBS  Premise
EHAUISU  Connection object
EANLH  Installation time slice
EGPLTX  Device locations
EUI HEAD  PoDs
EUITRANS  PoD internal to external Ids

Device Management

ETDZ  Registers
EPROFASS  Registers-profiles
EASTI  Register relationships
EUILZW  Register- Pod
EASTS  Installation-register
EADZ  Multiple installation billing data registers
EZWD  Register Groups
EZUZ  Device allocation for registers
EGERH  Historical device data
EGERS  master device data
EGERR  Device info for Pod
EUILNR  Device Pod
ETYP  Device category- material data
EZUG Device allocation for device

 

Scheduling


TE422  Meter reading units
TE418  Schedule records- meter reading units
TE420  Portions
TE419  Parameter records
TE417  Schedule records for portion
ETRG  Billing orders
EABL  Meter reading document
EABLG  Meter reading reasons

Budget billing, cook book, FICA, Industry solution form SAP, ISU, payment, SAP, SAP FI, SAP ISU, Scheme, Utility

SAP ISU Payment Plan vs Payment Scheme

The major difference between payment plan and a payment scheme is that a payment plan is related to a finite number of open items to be payed on a e.g. monthly basis until the debt is payed finally. On the other hand, the validity period of a payment scheme is unrestricted.
Payment plan:
An agreement between the customer and the utility company, which determines the amount to be paid for each bill on agreed dates. The payment plan amount is not necessarily the bill amount. The difference amount between the bill amount and the payment plan amount is fixed and posted. The payment plan is not to be compared with the budget billing plan that is charged between two periodic bills.
Payment Scheme:
The payment scheme is a statistical budget billing procedure. Consumption billing amounts from previous and current billing periods are copied to the payment scheme and distributed evenly over the next billing period. The budget billing amount is determined partially from an extrapolation portion that reflects the expected consumption for the current billing period and partially from the copied consumption billings. It is not necessary to copy consumption billings to the payment scheme in order to use this procedure. If you do copy them, the bills are not paid directly by the customer but during the next billing period when the
payment scheme requests are paid. The payment scheme allows payments to be made in weekly, fortnightly, monthly, quarterly, and yearly cycles. The validity period of a payment scheme is unrestricted. This means that a payment scheme is not ended and another created when you create a periodic bill. Instead, the existing payment scheme is adjusted.
There is a cookbook payment scheme available in [http://service.sap.com/utilities] -> SAP for Utilities (product information) -> IS-U/CCS -> Billing&Invoicing -> Cookbooks&Guidelines.
Billing, course, SAP, SAP ISU, Utility

SAP ISU Billing And Invoicing

The SAP Utilities (IS-U) component is a sales and information system that supports all business processes and utility services of a utility company. You can use IS-U for managing and billing residential, commercial and industrial, and prospective customers. This component also allows you to manage and bill customers who receive services, purchase goods, or pay fees and taxes.
        Billing and Invoicing module explain the process that starts with Billing and Invoicing and finishes with Bill print out. Here you will also get knowledge of all  ISU/CCS  master data and functions relevant to Billing. Detail analysis of  rates and prices modelling  is presented in most simplistic way.

       Following are some of the business processes which can be handled by this module:- 

Billing Process Scheduled Billing, 
Billing  Process Produce Invoice Statements, 
Joint Invoicing, 
Process Invoice Printing, 
Billing Process Bill Inserts And Messages, 
Billing  Process Send Sms For The Month, 
Process Send Ebill  For The Month, 
Billing Process To Send More Than One Bill Copy For A Month, 
Billing Process Display  Latest Bill  For The Month On The Web, 
Billing Process Category Change, 
Billing Create Maintain Installation Facts, 
Billing Process Individual Reversal Or Adjustment., 
Billing Process Mass Reversal Adjustment, 
Billing  Process Produce Invoice Statements, 
Billing Process Display  Latest Bill  For The Month On The Web, 
Billing Process Mass Reversal Adjustment, 
Billing  Process Duplicate Invoice Statement., 
Billing  Process Bill Batching, 
Billing  Create Maintain Rate Tariff Structure, 
Billing  Create Maintain Price, 
Billing  Create Maintain Discounts Surcharges Prices, 
Billing  Process Bill Simulation, 
Billing Process Bill Exceptions And Errors, 
Billing  Process Unscheduled Bill

       The Scope & overview of this module is as follows:
         Billing Master  Data
        Billing Class
        Rate type
        Price
        Operand
        Variant Program
        Rate
        Fact Group
        Schema
        Rate Category
       
         Invoicing  
        Invoicing Functions
        Account  Maintenance
        Due Dates
        Credit Processing.
         Joint Invoicing / Integration
        Outsorting  in Invoicing
        Invoice Reversal
         Billing  
       Billing overview
       Billing reversal  and Adjustment
       Manual Billing
       Billing Exception
       Billing Outsort
       Billing Exception

Business Suite, Interview, Management, SAP, SAP Technical

What are the components of the ‘SAP Business Suite’?

What are the components of the ‘SAP Business Suite’?

  SAP Customer Relationship Management (CRM 5.0)
  SAP Supply Chain Management (SCM 5.0)
  SAP Supplier Relationship Management (SRM)
  SAP SRM 2007
  SAP Catalog Content Management (SRM-MDM 1.0)
  SAP Product Life Cycle Management
  SAP Product Life Cycle Management 4.00
  SAP Environment, Health, and Safety 2.7B
  SAP PLM Recipe Management 2.1
  Audit Management
  SAP Compliance Management for SOA
  Management of Internal controls 1.0
  SAP Learning Solution 2.00
  SAP Strategic Enterprise Management (SEM)

Interview, SAP, SAP Technical

What is ‘SAP Business One’?

What is ‘SAP Business One’?

 ‘SAP Business One’ is the low-cost, easy-to-implement business management  solution from SAP for Small and Medium Enterprises (SME). Unlike regular ERP software from SAP, this solution gives managers on-demand access to critical  real-time information through ‘one single system’ containing financial, customer relationship management, manufacturing, and management control capabilities.  As a result, the solution enables rapid employee productivity, while empowering managers to make better business decisions to stay ahead of the competition.  Equipped with a user-friendly interface, SAP Business One serves as your central ERP hub with standard interfaces to internal and external data sources, handheld computers, CRM applications, and other leading analysis tools.

SAP Business One is based on the Microsoft Windows platform making it easier to comprehend and use. The application comes with a ‘demo company,’ which can be used by the implementing company to become familiar with functionality.  The modules of SAP Business One include:

  Administration
  Financials

Sales Opportunities
  Sales – A/R
  Purchasing – A/P
  Business Partners
  Banking
  Inventory
  Production
  MRP
  Service
  Human Resources
  Reporting

Interview, SAP, SAP Technical

About SAP xApps

What is ‘SAP xApps’?

 The ‘SAP xApps’ family of composite applications enables continuous business  innovation – and provides the flexibility necessary to respond quickly and profitably to business changes. They extend the value of core business investments and maximize the return on strategic assets: employees, knowledge, products, business relationships, and IT.  SAP and SAP certified partners deliver these composite applications that drive specialized business processes, provide comprehensive business insights, and focus on the needs of a variety of industries.  All these applications combine Web services and data from multiple systems in an application design made possible by the SAP Composite Application Framework within the SAP NetWeaver technology platform. 

This framework includes the methodology, tools, and run-time environment to develop composite applications. It provides a consistent object model and a rich user experience, and gives developers a productive way to create composite applications on top of a set of heterogeneous applications.

What are all the components of ‘SAP xApps’?

  Duet
  SAP Document Builder
   SAP Global Trade Services
  SAP xApp Manufacturing Integration and Intelligence
  SAP xApp Resource and Portfolio Management
  SAP xApp Product Definition
  SAP xApp Cost and Quotation Management
  SAP xApp Integrated Exploration and Production
  SAP xApp Sales and Operations Planning