Quantcast
Channel: SCN : Document List - SAP for Utilities
Viewing all 277 articles
Browse latest View live

New in Enhancement Pack 7 - Price Uploads

$
0
0

After looking at this Are you making the most of your existing SAP Investment? looking at one of our boxes that is on enhancement package 7 that some of the improvements are already included, without having to activate anything (which is nice).

 

This note "Importing prices to the IS-U system (price upload)"  is extremely helpful and works.

 

Here are the steps:

 

Enter transaction EPRICE_UPLOAD

 

This screen appears:

1fig.png

 

I used the SAP Help to help me format the spreadsheet - see Example: Upload Prices Without Price Template - Contract Billing - SAP Library

 

The most time I spent was formatting the date in the spreadsheet.

2fig.png

Since I am not using a Price Template, I am leaving that field blank.

 

Then I upload the spreadsheet:

3fig.png

Then success!  The price is uploaded:

 

4fig.png

 

I go to transaction EA91 to view the new uploaded price:

5fig.png

 

This is an important feature if you have several prices to upload or change at various times.  We plan on using it.

 

Will we hear more or learn more at this event? Going to Hollywood - in September for SAP for Utilities

 

If you are going, I would welcome talking about this further.


Key Topic: IT/OT Integration

$
0
0

The convergence of Information Technology and Operational Technology is getting more and more important in the Utilities industry.

 

Read about this topic in the following blogs:

 

New: IT/OT Integration is a major topic at the SAP Conference for Utilities 2014 by Gero Bieser, March 12, 2014

The Convergence of Information Technology and Operational Technology is Already Happening – How Can Utilities Best Adapt…, by Henry Bailey, March 4, 2014

 

Thoughts from DistribuTECH 2014 – The Emergence of Software in the Hardware World. by Rory Shaffer, February 6, 2014

 

Situational Intelligence Melds IT, OT and XT to Improve Decision Making by Steve Ehrlich, SpaceTime Insight, February 4, 2014

 

Utilities are moving to the intelligent level of Transmission and Distribution by Henry Bailey, February 3, 2014

 

The Why, How and What of IT-OT integration for Energy Distribution Companies by Miquel Carbo, November 8, 2013

 


Have a look at this Customer Testimonial Video from Alliander. Alliander is the largest energy distribution company in the Netherlands.
Learn how Alliander, the largest energy distribution company in the Netherlands, successfully deployed SAP HANA using SAP Services to drive innovation by analyzing Big Data from sensors and business applications to improve forecasting models.

http://www.sapbigdata.com/stories/alliander-uses-sap-services-to-successfully-analyze-big-data/#sthash.71pdRNeC.n45QKPwA.dpbs

 

Read about a strategic OEM agreement between Rolta, a leading IT provider who offers "Suite and Rolta OT-IT Integration Suite™ and SAP http://www.news-sap.com/rolta-and-sap-announce-a-strategic-oem-agreement/

 

Follow us on twitter @SAP Industrieshttps://twitter.com/sap4utilities

Susanne's News Bites

$
0
0
You might be familiar with our SAP for Utilities Headline News newsletter.
If not, subscribe by email (Susanne Schlenker).

But what happens with information I received shortly after the last issue and that cannot wait until the next issue?
The answer is Susanne's News Bites blog.

Don't miss the in-between news and under Actions, choose Receive email notifications on the right-hand side of this page.

Coming up:
  • SAP's Utility of the Future - A Monthly Virtual Series (last Wednesday of each month) - free of charge

Register today

    • Future of Cloud for Utilities – SAP ‘Utility in a Box
      Wednesday, August 27, 2014
      12 p.m. ET/9 a.m. PT
    • Future of Waste and Recycling for Utilities
Wednesday, September 24th
    • Future of Energy Portfolio Management, Prepayment and IDEX

Wednesday, October 29th

    • Future of Electro-mobility

Wednesday, November 26th

 

 

Past news bites:
  • Webinar: How and Why CenterPoint Energy chose SAP HANA
  • Deep-Dive Workshop: SAP CRM for Utilities New Ehp3 Developments - free of charge
  • Mobile Webinar: Put a Map in Your Mobile App
  • SAP's Utility of the Future - A Monthly Virtual Series (last Wednesday of each month) - free of charge
    • Future of a Multichannel Foundation for Utilities
    • Future of Pricing and Costing for Utilities
  • Multichannel Foundation Workshop - free of charge
  • Classroom Training: SAP Energy Portfolio Management 6.04

Key Topic: SAP CRM for Utilities

$
0
0

Important information: If you would like to get notifications just for this document, please click on "Receive email notifications" in the action box on the right upper corner. You need to be logged in to be able to activate this function.

 


News

Updated: Cookbook for Price Replication from SAP CRM with SAP ISU Master Data Generator by Christiane Voigtmann on Sept 2, 2014
Out Now: SAP CRM for Utilities 7.0 EHP 3 Support Package 5 by Christiane Voigtmann on Aug 5, 2014

 

 

Tips and Tricks

How to change the sort order of premises in the hit list by Michael Sturm on Aug 14, 2014

Required adjustments to copied bol tree profiles by Michael Sturm on Aug 4, 2014

Recommendation: As of SAP CRM 7.0 EHP 3, SAP strongly recommends to use PMU instead of PME (see also KBA 2038592)

 

Further Information

SAP Help Portal for product Information

SAP Service Marketplace (SAP Service Marketplace is just for customers and partners: read what it is and how you can get accessSAP Service Marketplace Overview and FAQ)

How to create a perfect incident

$
0
0

Are you also sometimes annoyed when product support engineers seems to play ping pong with your incident asking about system access, reproducible example data or providing notes which are already applied in your system?
This can be avoided if you keep a few things in mind when creating an incident:

 

  • Assign the incident to the right installation and system ID
  • Enter a meaningful short text in the Subject area. The short text helps to identify the message. It is also a search term for searching in the SAP Support Portal and knowledge base articles.
  • Enter a detailed description of the problem as a long text.
  • Provide test data and a detailed step-by-step description of how to reproduce the problem. Screen shots are often helpful to point out what you did.
  • In case the CRM web client is involved, always provide the business role to be used to log on.
  • Explicitly mention the system and client which should be used for testing. If it is only possible in the productive system, make sure authorization is taken care of so that the support engineer is allowed to analyze here.
  • Inform about the release and patch levels of the system, but only mention the ones which are related to the problem (like IS-U or FI-CA or CRM).
  • Ensure that the system connection will be open and valid logon data are available.
  • Perform a note search and let the support engineer know what you searched for and the result of the search:
    • Choose the right component
    • Ensure that the right patch level is used
    • Use meaningful key words
    • Technical search terms are often very helpful like technical names of transactions, programs, function modules or methods or BSP components (in the CRM environment) xantippe

Key Topic: Product Support

$
0
0

Your Vote Counts. Are KBAs Helpful?

$
0
0

Since July we have been publishing important Knowledge Base Articles (KBA) which are intended to help you have a stable running system or solve existing problems.

 

Now we are very interested in your feedback regarding our KBAs.This way we can improve and give you exactly what you are looking for.

 

Your vote counts. This is how it works:

 

  1. Out of the KBA list below, click on the number of the KBA or KBAs that you find most interesting and helpful.
  2. In the top right-hand corner in the Overall Rating field, cast your vote by choosing stars.

 

Thank you so much for your feedback. We really appreciate it.

 

Most recent KBAs:

 

1895682IC Web Client: Not all invoices are displayed in BuAg View
2027247Reverse Charge for invoices for certified reseller - How to build up the scenario in the application form
2042834CRM-IU-MD-PRO: Creating BRF+ Rules using Attributes across Product
1970759

EL35/RELEABL1: Short Dump CONNE_IMPORT_WRONG_COMP_LENG in EPRINTPA

2047744
IC Web Client: Enhanced Bill Correction: dump "Business server page (BSP) Error" concerning relation BuAgPrintDocRel

KBA's from August:

2034292FI-CA transaction FPO2: differences between FI-CA and General Ledger
2035406FI-CA transactions FPO1/FPO1P/FPO4/FPO4P: result is different to the general ledger
1585870ICWC: Technical objects not visible in Web UI
2037246FPY1: Zahlsperren und  SEPA Ausführungsdatum
2047888

CRM-IU: Reuse of Procedures within PMU


KBAs from July:

1977298FI-CA: FPY1 problems with SEPA mandates
2033159FI-CA: FPY1 SEPA Item indicator 031
1771145CRM-IU: Integration of UTIL_SALES components into UTIL_IC role
1976190IS-U Invoicing EA19 terminates with error EA19 >0-115
1805595

BW-IS-U: How to reload Data with Data Source 0UC_SALES_STATS_02

One-Day Seminar: Transforming Assets to a Plan: Learn How to Solve the ISO 55000 Challenge

$
0
0

Hello,

 

Take advantage of this opportunity to learn more about how to solve the ISO 55000 challenge.

 

Register here


Agenda below

 

Invitation: Click to enlarge

Capture.JPG

Capture.JPG


How Alliander is Frontrunning the Energy Transition by Using HANA Smart Grid Analytics?

$
0
0

Alliander is a Dutch utility company which provides gas and electricity, and supports more than 3.5 million customers in the Netherlands.


In this video Jeroen Scheer and Rob Jansen talk about Alliander's implementation highlights. See how Alliander is front-running the energy transition by using smart grid analytics based on HANA. Learn about the challenges they encountered and how they overcame them.

View this video:

 

 

One of the largest expenses for Alliander is the upgrading of substations in electricity grid.

Together with the consultants from SAP Data Science, they build (and brought live in the beginning of 2013) a SAP HANA powered solution for the first part of the process: analyzing last year grid sensor data.

 

Read the following blog for having more information on how Alliander improves their load forecasting and their asset management systems with SAP HANA.

Watch demo of  Alliander SAP HANA powered load forecasting applications.

Multi Channel Self Service for Utilities – ASUG Webcast Question & Answer

$
0
0

This was an SAP webcast provided to the ASUG Utilities Special Interest Group covering Key Topic: SAP Multichannel Foundation for Utilities

 

MCF is Multi Channel Foundation

 

Question & Answer:

Q: How long has the product been GA?

A: Exit ramp-up from June this year

 

This release was available from November last year

Q: How many SAP customers use this?

A: 15

 

Some customers are implementing it or planning to implement

 

Cannot share customer names without their consent

 

Q: Any discussion of this at SAP TechEd?

A: No plans to participate at TechEd

 

Q: Use case for social networks

A: Facebook posting, save $ per year and sign up

Outages are a good use case; when get outage panic, and put information/complaints in social media

Track sentiment and resolve the issues

Sign in with Facebook account to utility

 

Q: Is there a migration path from UCS?

A: UCS (UCES?) is not easy to extend, MCF is using open standards and can be used across different channels – position MCF is a successor to UCS

Not aware of a migration path or a demand for it

 

Q: Are these API’s using standard SAP functionality or can they be extended to use SAP custom modules?

A: Design of OData services use standard SAP API’s but have in place a framework where OData can be enhanced

Can use custom API’s if you want to

 

Q: Where MCF fit if we are implementing SMP 3.0?

A: SMP is alongside MCF

MCF does not require SMP

If you want to have an app which receives notifications – depending on the need – SMP could work as a complementary solution to MCF

SMP is not a must for MCF but can work together if there is a need

 

Q: Is it correct to assume that PI is needed for these API’s

A: PI is not necessarily needed; OData connects directly to backend systems

PI can be part of your landscape

SAP Gateway is the necessary platform which provisions OData Services to outside world

 

Q: Does SP3 cover user management on top of UME?

A: User management was there from beginning

SP3 – nothing new in terms of user management

SP3 has new sample mobile app and new OData services

 

Q: Does MCF require any additional licensing or support costs?

A: If you have SAP ISU or CRM there is an additional cost, based on number of active online users

Based on customers who sign-on self-service determines pricing and licensing

Based on active online users

 

Q: Is prepay a functionality that is provided?

A: Not in current implementation but it is on the backlog and working on upcoming releases and SAP wants to hear about it.

 

Q: How do you integrate with a payment processor?

A: Use standard interfaces – API’s for payment, dispatch to standard core of SAP for payments and from there to FI-CA and covered there

 

Q: Is payment posted in SAP in real time?

A: Yes – as a payment document or payment specification based on configuration

Payment run could be run immediately from credit card

From end user point of view it is done right away and reflected on self-service portal right away

 

Q: For proper license costs, how would know the users who logs on day one – need cost model

A: typically licensing and auditing happens retroactively

X number of customers

Anticipate X number to do online

Do rough estimate, implement solution

Auditing takes place retroactively in system

Exact pricing tough to determine

On day 1 hard to come up with number – has to be approximation

 

Q: How is the IVR is integrated?

A: If IVR supports OData protocol it can be integrated

 

Q: What is the time duration to fully implement out of the box?

A: German partner installed and built custom app – it took less than a week to install and start building UI on OData services

Did an initial prototype

It varies from customer to customer

 

Q: Can this be done in-house or do you recommend having a partner?

A: Having a partner is always good; worked with SAP Services who knows the solution

Helpful to have a partner on-board if they know solution and experience

It depends – if you are a large company who have technical knowledge

Some customers are implementing without a partner

Main skillsets needed in house – ABAP, OData Protocol, UI – HTML5, SAPUI5

 

Q: If the user interface and tiles – can they be used out of the box?

A: Yes, the foundation comes with 2 UI’s

Web only UI and a responsive UI that runs on different platforms

Should work out of the box – once you install MCF they should work out of the box

Do branding – on the OData side or UI side enhancements

 

Q: Can you talk about security protocols?

A: Depend on the Gateway Server and underlying technology

Gateway supports https protocol and encryption and different types of authentication with SAML

Special framework where check for OData requests where user asks – assign BP to user

End users are communications types in Gateway and SAP and assigned to BP – can read this data

See admin guide and application help

How Does OpenText Bring Value to SAP Customers?

$
0
0

Learn about why OpenText partnered with SAP, what the impact of their partnership has been and the key lessons they learned.

 

Richard Matti, Director SAP Program Management EMEA at OpenText, talks about how OpenText brings value to SAP customers.

They have more than 20 years of experience as an SAP partner and over 100 000 customers globally.

They are experts in information management  and structure information in the context of business processes.


“Long term commitment, close alignment & success are the basis of our relationship with SAP.”

 

 

 

Some Utilities customer stories:

 

 

Further information: OpenText homepage

SAP Info Session: Big Data Analytics in Utilities – Lessons from the TrencheS

$
0
0

Wed, Oct 29, 2014 4:00 PM CET / 11:00 AM ET / 8:00 AM PT

This session is aimed at providing the audience a practitioner’s view on analyzing Big Data leveraging SAP HANA in the Utilities Industry with experiences from real-life examples and relevant use cases. Hear first-hand from one of our premier customer how SAP partnered with CenterPoint Energy in driving an advanced analytics driven Big Data Strategy through co-innovation in delivering a Forecasting Model Engine vision within their organization. The session aims to cover the following:

  • Big Data Trends and Challenges within the Utilities Industry
  • Differentiating between traditional BI and Advanced Analytics
  • Customer examples of approach to an advanced analytics initiative and driving exponential business value through predictive analytics
  • Representative business use cases relevant to the Utilities Industry that can be driven on SAP HANA
  • CenterPoint Energy’s experience on their approach and advanced analytics journey leveraging the SAP HANA platform

 
Speakers:

  • Rajkumar Erode, IT Solution Architect, CenterPoint Energy
  • Shailesh Tekurkar, Industry Analytics Principal Consultant, SAP

Register at: https://goto.webcasts.com/starthere.jsp?ei=1044097

Configuring Payment Medium Formats

$
0
0

Using outgoing payments in FI-CA, where managing large amount of data is one of the main goals, creating payment medium is very useful and time-saving activity which except for the speed helps with reducing errors.

 

In order to correctly configure Payment Medium Format, several transactions are to be used:

- FQP3 - Payment Medium Formats

- FQP1 - Define Payment Methods

- FQP4 - Company Code Details for Payment

 

This document will explain how to configure and use the Payment Medium Format /Z/HR-HUB3 which uses parameters and outputs file used in Croatia.

 

Prerequisits

 

Since the structure of the croatian payment medium format comes with an addon HR-CEE, it has to be installed on the system. If this is not the case, there is a set of notes which can be imported instead, but this will not be the topic of this document.

 

Step 1: Create Payment Medium Format (FQP3)

 

Enter the transaction FQP3 and create new Payment Medium Format with the following parameters:

- Format: /Z/HR-HUB3

- Country: HR

- Description: Croatia HR-HUB3

 

In the Payment Medium Format details enter data as follows:

- [X] Payment Medium with Documents: Output Media

- [X] Payment Medium (DME) without Documents; Type: File

- Country: HR

- Ext. Format name: HUB3

 

Payment Medium Output Separated By (Degree):

- [X] Company code

- [X] House bank

 

Step 2: Define Event Modules for Payment Medium Formats

 

Staying in the same transaction, while creating Payment Medium Format, select the subnode "Event Modules for Payment Medium Formats" and enter the following combination of Event, Function Module and Structure for format parameters:

 

20 - FKK_PAYMEDIUM_DMEE_20 - /CCEE/HRFI_HUB3_PARA

25 - FKK_PAYMEDIUM_DMEE_25 - /CCEE/HRFI_HUB3_PARA

30 - FKK_PAYMEDIUM_DMEE_30 - /CCEE/HRFI_HUB3_PARA

40 - FKK_PAYMEDIUM_DMEE_40 - /CCEE/HRFI_HUB3_PARA

 

Events are being called in the payment program and payment medium program. Events call the function modules which then deal with parameters to create the needed output format.

 

Step 3: Define Supplements for Payment Medium Formats

 

Supplemtns for Payment Medium Formats are printed in the payment medium (file) and are often used to distinguish between the types of payment. If the format itself needs this data, like it is needed in Croatia, you need to define at least one.

 

In the subnote "Supplements for Payment Medium Formats" enter the following combination of supplement and format supplement name:

OT - Others

 

Step 4: Define Payment Method

 

Enter the transaction FQP1, choose your country (in this case HR) and select subnode "Payment methods". Create new payment method with the following data:

- Payment Method: H

- Description: Bank transfer - HUB3

- Processing type: Bank account

 

Required master record specifications:

- [X] Bank details

- [X] IBAN required

 

Payment medium format

- Format: /Z/HR-HUB3

 

Data for application area Utility company:

- Document Type: CL (choose the document type you defined for clearing purposes)

- Clearing reason: 02 (Outgoing payment)

- Note to Payee: SAP_PS2

 

Save the changes and select "Permitted currencies" subnode. Having in mind simple scenario, where you use only local currency, create a new entry with the currency type "HRK".

 

Instruction keys inform the bank how the payments will be carried out. If the instruction keys are used in your country, you need to define them. We will create one. Enter the "Instruction keys" subnode and enter the following Instruction key:

- Country: HR

- Payment method: H

- Instruction key: 99

- Instruction key 1: 99

- Format: /Z/HR-HUB3

 

This step define the link between the Payment Medium Format created in steps 1 and 2 and the payment method you just created.

 

Step 5: Define Company Code Details for Payments

 

Enter transaction FQP4 and create a new paying company code. If you have only one company code, define that one here by just entering company code.

 

Save the changes and select "Payment Methods in Company Code" subnode. Create a new entry where you will connect the payment method created in step 4 (H) with the paying company code:

- Paying company code: 1000

- Payment method: H

- Country: HR

 

Save the changes and select "Payment Medium Formats in Company code" subnode. Here you will connect the payment medium format created in steps 1 and 2 (/Z/HR-HUBR3) with the paying company code:

- Company code: 1000

- Format: /Z/HR-HUB3

- Form formatting type: SAPscript

- Form for Accompanying Sheet: J_3K_AVIS

- Issuer details: <enter the details that will be used in the form for accompanying sheet and in the payment medium>

 

Step 6: Creating variant for payment medium program

 

Enter transaction SE38 and enter program name SAPFKPY3. Then enter the following data:

- Payment medium format: /Z/HR-HUB3

- [X] Output media

- [X] Data Medium Exchange

- [X] Error log

 

Save the variant.

 

Testing the Payment Medium

 

The specified steps will do everything needed for the payment medium to be created and outputed. To test it, we can concider an often scenario in which a customer overpays its bill and wants the refund for the difference. To follow this repayment scenario, the following can be done in the test system:

- create an invoice for the customer (for example in FPE1)

- create a payment where the amount exceedes the invoice (for example in FP05)

- check residual item, edit it and enter "H" as a payment method in the payment data tab (for example, in FPL9)

- run payment program (FPY1)

- run payment medium creation program (SE38 / SAPFKPY3) using the variant you created in step 6.

Natural Gas (CNG) distribution in India and SAP Solution

$
0
0

1. Natural Gas Overview in India and challenges

Natural gas is a combustible, gaseous mixture of simple hydrocarbon compounds, usually found in deep underground reservoirs formed by porous rock. Natural gas is a fossil fuel composed almost entirely of methane, but does contain small amounts of other gases, including ethane, propane, butane and pentane. Methane is composed of a molecule of one carbon atom and four hydrogen atoms.

Natural gas is used extensively in residential, commercial and industrial applications. India had 159.1 trillion cubic feet of proven natural gas reserves as on May 2014. Almost 70% of India’s natural gas reserves are found in the Bombay High basin and in Gujarat. Offshore gas reserves are also located in Andhra Pradesh coast (Krishna Godavari Basin) and Tamil Nadu coast (Cauvery Basin). Onshore reserves are located in Gujarat and the North Eastern states (Assam and Tripura).


2. How Does the Natural Gas Delivery System Work?

Gas flowing from higher to lower pressure is the fundamental principle of the natural gas delivery system.  The amount of pressure in a pipeline is measured in pounds per square inch.

The Natural Gas Delivery Network

n1.gif

From the well, the natural gas goes into "gathering" lines, which are like branches on a tree, getting larger as they get closer to the central collection point.

Gathering Systems

A gathering system may need one or more field compressors to move the gas to the pipeline or the processing plant.  A compressor is a machine driven by an internal combustion engine or turbine that creates pressure to "push" the gas through the lines.  Most compressors in the natural gas delivery system use a small amount of natural gas from their own lines as fuel.

The Transmission System

From the gathering system, the natural gas moves into the transmission system, which is composed of about 272,000 miles of high-strength steel pipe ranging from 20 inches to 42 inches in diameter.They move large amounts of natural gas thousands of miles from the producing regions to local distribution companies (LDCs).  The pressure of gas in each section of line typically ranges from 200 pounds to 1,500 pounds per square inch, depending on the type of area in which the pipeline is operating.  As a safety measure, pipelines are designed and constructed to handle much more pressure than is ever actually reached in the system.  For example, pipelines in more populated areas operate at less than one-half of their design pressure level.

Compressor Stations

Compressor stations are located approximately every 50 to 60 miles along each pipeline to boost the pressure that is lost through the friction of the natural gas moving through the steel pipe.  Many compressor stations are completely automated, so the equipment can be started or stopped from a pipeline's central control room.  The control center also can remotely operate shut-off valves along the transmission system.  The operators of the system keep detailed operating data on each compressor station, and continuously adjust the mix of engines that are running to maximize efficiency and safety.

Gate Stations

When the natural gas in a transmission pipeline reaches a local gas utility, it normally passes through a "gate station."  Utilities frequently have gate stations receiving gas at many different locations and from several different pipelines.  Gate stations serve three purposes.  First, they reduce the pressure in the line from transmission levels (200 to 1,500 pounds) to distribution levels, which range from ¼ pound to 200 pounds.  Then an odorant, the distinctive sour scent associated with natural gas, is added, so that consumers can smell even small quantities of gas.  Finally, the gate station measures the flow rate of the gas to determine the amount being received by the utility.

The Distribution System

From the gate station, natural gas moves into distribution lines or "mains" that range from 2 inches to more than 24 inches in diameter.  Within each distribution system, there are sections that operate at different pressures, with regulators controlling the pressure.  Some regulators are remotely controlled by the utility to change pressures in parts of the system to optimize efficiency.  Generally speaking, the closer natural gas gets to a customer, the smaller the pipe diameter is and the lower the pressure is.


3. Problems with Natural Gas


Not a renewable source of energy. India has only limited reserves of natural gas, though further discoveries are being made from recent explorations.

Owing to the high percentage of methane in natural gas, it is highly combustible.

The process of extraction of natural gas involves making large cavities in the ground.

Natural gas requires highly complex treatment plants and pipelines for its delivery.

Natural gas occupies four times the space of a gasoline-equivalent energy.

 

4. CNG network In India


Compressed Natural Gas (CNG): is natural gas compressed to a pressure of 200-250 Kg/cm² (g) (due to its low density) to enhance the vehicle onboard storage capacity. Thus, the compressed form of natural gas is used as a fuel for transportation purposes.

 

Network In India

 

At present CNG Retail Outlets of GAIL and Its JVCs are available in Delhi, Maharastra, Uttar Pradesh, Gujarat, Andhra Pradesh, Tripura, and Madhya Pradesh States with more than 400 CNG Retail outlets catering to approximately 6,80,000  vehicles. 


Indraprastha Gas Ltd, a JV of GAIL (India) Ltd, has 209 CNG Retail outlets and Mahanagar Gas Ltd another JV of GAIL (India) Ltd has set up 148 CNG stations.
Similarly, other JVCs like MNGL has 13 Outlets, BGL has 14 outlets , GGL with 10 outlets each,  and AGL &  CGUL with 9 retail outlets each and TNGCL with one outlet.

GAIL Gas Limited, a wholly owned subsidiary of GAIL (India) Limited has currently 17 CNG outlets at Dewas, Sonepat, Kota, Meerut, Vijaipur, Dibiyapur, Firozabad, Vadodara and Panvel. It will be commissioning its other outlets very soon.


5.  SAP Solution for Natural Gas CNG


Indraprastha gas limited, GAIL, Petronet LNG all are on SAP which supplies CNG. Either R/3 can be implemented or SAP IS Utilities, or SAP IS OIL depending upon the nature of business.


SAP Industry Business processes can have implementation challenges across all SAP Modules like SD, FI and CO, HR, MM, PM and EHS.

The following business scenarios are mapped to SAP Solution:


Natural Gas can be created as Pipeline Material with negative stock. There are meters installed for consumption of gas, but in SD there is no concept of Meter Reading. Either an enhancement has to be worked out or simply can integrate it with PM where Meter Reading is available along with Location, Equipment as a standard concept. As CNG is used as a Transportation fuel and is supplied through gas stations, we can treat Gas Stations as Sold to Customers and One time Customers as Ship to. Plant is the compressor Station from where we get the gas to main station. After taking the meter reading for consumption, a sales Order can be created with the meter reading Quantity and Material and it would be Standard Order Flow. The Outbound Delivery is created and accordingly the Invoice is generated.

There is no Inventory as the Gas is continuously supplied through Pipelines, so no WHM and there is no PP as we are purchasing Gas through Vendors.

SAP has also provided with SAP IS OIL where we can use downstream process which is an integration of SD, MM, and PM.

We can also use SAP IS UTILITIES where we have to generate billing for many customers where natural gas like PNG (Kitchen gas) is used by millions of households.


Module

Functions/Concerns

Sales & Distribution

• Standard sales process

 

• One time customer concept

 

• Pricing, Country India Version for Taxes

 

• Billing

Material Management

•      Pipe Line Material

Plant Maintenance

•      Location, Equipment, Meter Reading

 

• Preventive and breakdown maintenance for all Equipment’s

Master Data

•      Material Master

 

•      Customer Master

 

•      Pricing Condition Records

 

• Output Condition Records

FICO

•     General Ledger

 

•     Accounts Payable and Receivables



6. References

www.eai.in/ref/fe/nag/nag.html

http://www.gail.nic.in/final_site/cng_overview.html

http://www.gailonline.com/gailnewsite/businesses/citygasdistribution.html

http://www.pngrb.gov.in/

http://www.cepa.com/about-pipelines/types-of-pipelines/natural-gas-pipelines

Update Contract Move-Out Reversed Flag using report by using Splitter in ALV Display

$
0
0

My requirement was to update the Move-Out Reversed Flag of Contracts with a Report having a test mode flag in it which will show the details of the rows of the tables getting updated.

 

1. The report's test mode should show the details of rows getting updated for the contracts provided in a single screen.

This can be achieved using splitter control

 

The tables getting updated are EAUS,EAUSV & EVER.

 

The reason behind me writing this document is to help technical people achieve this requirement with basic details of what is required.

 

Step 1. Write a report for updation of the flag.

Step 2 . To have splitter, you first have to create a screen for your program. For this go to SE51 and create a screen for the same program

For Ex : If your program name is : ZTEST, create a screen, 9000 (or any other number ) for the same program.

Step 3. In this screen, create a Custom Container.

This custom container actually will be called in the report and then we will split it into the desired format.

Give a name to this custom control . Ex : give name : CCONTAINER

 

Now the source code :

 

TABLES :

ever,

eaus,

eausv.

** Selection ScreenSELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.SELECT-OPTIONS : s_vert FOR ever-vertrag.SELECTION-SCREEN SKIP.PARAMETERS : p_mout RADIOBUTTON GROUP r1,
             p_min
RADIOBUTTON GROUP r1,
             p_tmode
AS CHECKBOX DEFAULT 'X'.SELECTION-SCREEN END OF BLOCK b1.SELECTION-SCREEN SKIP.
***-- for splitterDATA splitter_1 TYPE REF TO cl_gui_splitter_container.DATA splitter_2 TYPE REF TO cl_gui_splitter_container.DATA container TYPE REF TO cl_gui_custom_container.DATA container_1 TYPE REF TO cl_gui_container.DATA container_2 TYPE REF TO cl_gui_container.DATA container_3 TYPE REF TO cl_gui_container.DATA : gt_sflight_1 TYPE TABLE OF sflight,
      gt_sflight_2
TYPE TABLE OF sflight,
      gt_sflight_3
TYPE TABLE OF sflight,
      g_container
TYPE scrfname VALUE 'CCONTAINER',
       grid1
TYPE REF TO cl_gui_alv_grid,
       grid2
TYPE REF TO cl_gui_alv_grid,
        grid3
TYPE REF TO cl_gui_alv_grid.
DATA : ok_code TYPE sy-ucomm.

** Type DeclarationsTYPES : BEGIN OF st,
        vkonto
TYPE ever-vkonto,
      
END OF st.
TYPES : BEGIN OF ty_evr,
        vertrag
TYPE vertrag,
  loevm
TYPE vertrag,
  anlage
TYPE anlage,
  einzdat
TYPE einzdat,
  auszdat
TYPE auszdat,
 
END OF ty_evr.
** Data DeclarationsDATA : lt_eausv TYPE TABLE OF eausv,
       ls_eausv
LIKE LINE OF lt_eausv,
       lt_vkonto
TYPE TABLE OF st,"ever-vkonto,
       lt_eaus
TYPE TABLE OF eaus,
       ls_eaus
LIKE LINE OF lt_eaus,
       lt_ever_min
TYPE TABLE OF ever,"ty_evr,
       ls_ever_min
LIKE LINE OF lt_ever_min.
DATA: lcl_alv TYPE REF TO cl_gui_alv_grid,
      t_eaus
TYPE STANDARD TABLE OF eausv,
      t_eaus1
TYPE STANDARD TABLE OF eaus,
      t_ever
TYPE STANDARD TABLE OF ever,
      ls_fli 
TYPE eausv,
      lr_data
TYPE REF TO data,
      lr_alv
TYPE REF TO cl_salv_table,
      lr_alv1
TYPE REF TO cl_salv_table,
      lr_desc
TYPE REF TO cl_abap_datadescr,
      lr_str 
TYPE REF TO cl_abap_structdescr,
      lr_fun 
TYPE REF TO cl_salv_functions_list.
DATA lin TYPE i.
** For splitter Container
DATA:
      g_alv_grid1
TYPE REF TO cl_gui_alv_grid,
      g_alv_grid2
TYPE REF TO cl_gui_alv_grid,
      g_alv_grid3
TYPE REF TO cl_gui_alv_grid,
            g_title 
TYPE lvc_title,
   gr_display  
TYPE REF TO cl_salv_display_settings,
   gr_function       
TYPE REF TO cl_salv_functions,
gr_columns        
TYPE REF TO cl_salv_columns_table,
g_custom_container
TYPE REF TO cl_gui_custom_container,
      g_splitter_container
TYPE REF TO cl_gui_splitter_container,
      g_top_container
TYPE REF TO cl_gui_container,
      g_middle_container
TYPE REF TO cl_gui_container,
      g_bottom_container
TYPE REF TO cl_gui_container.** End
FIELD-SYMBOLS: <l_tab> TYPE ANY TABLE,
               <ls_eausv>
TYPE eausv,
               <ls_eaus>
TYPE eaus,
               <fs_ever_min>
TYPE ever." ty_evr.
** Local Variables*Data lv_vkonto type VKONT_KK.
** ConstantsCONSTANTS : c_col_x  TYPE sap_bool VALUE 'X'.


**-- Start of Logic
IF p_mout = 'X'.
 
PERFORM update_mout_dtab.ELSEIF p_min = 'X'.
 
PERFORM update_min_dtab.ENDIF.

*&---------------------------------------------------------------------**&      Form  UPDATE_MOUT_DTAB*&---------------------------------------------------------------------**       text*----------------------------------------------------------------------**  -->  p1        text*  <--  p2        text*----------------------------------------------------------------------*FORM update_mout_dtab RAISING cx_salv_msg .** To check move-out reversal indicator for EAUSV

 
SELECT * FROM eausv INTO TABLE lt_eausv WHERE vertrag IN s_vert.

 
IF sy-subrc = 0.
   
SORT lt_eausv BY vertrag.
   
LOOP AT lt_eausv INTO ls_eausv.
     
IF ls_eausv-storausz = 'X'.
       
DELETE TABLE lt_eausv FROM ls_eausv.
     
ENDIF.
   
ENDLOOP.
   
IF p_tmode = 'X'.
*INSERT ls_fli INTO TABLE t_eaus.
      t_eaus[]
= lt_eausv[].
     
ASSIGN t_eaus TO <l_tab>.
**----test splitter for tables

   
ELSE.
     
LOOP AT lt_eausv ASSIGNING <ls_eausv>.
        <ls_eausv>
-storausz = 'X'.
     
ENDLOOP.

     
DESCRIBE TABLE lt_eausv LINES lin.
     
MODIFY eausv FROM TABLE lt_eausv.
     
IF sy-subrc = 0.
       
WRITE : lin, 'records updated in EAUSV table'.
     
ENDIF.
   
ENDIF.
 
ENDIF.
** To check move-out reversal indicator for EAUS.

 
SELECT vkonto FROM ever INTO TABLE lt_vkonto WHERE vertrag IN s_vert.

 
IF sy-subrc = 0.

   
SELECT * FROM eaus INTO TABLE lt_eaus FOR ALL ENTRIES IN lt_vkonto WHERE vkont EQ lt_vkonto-vkonto.

   
IF sy-subrc = 0.
     
SORT lt_eaus BY vkont.
     
LOOP AT lt_eaus INTO ls_eaus.
       
IF ls_eaus-storausz = 'X'.
         
DELETE TABLE lt_eaus FROM ls_eaus.
       
ENDIF.
     
ENDLOOP.
     
IF p_tmode = 'X'.*        CLEAR : t_eaus,lt_eausv.

       
CALL SCREEN 9010.

     
ELSE.
       
LOOP AT lt_eaus ASSIGNING <ls_eaus>.
          <ls_eaus>
-storausz = 'X'.
       
ENDLOOP.
       
CLEAR lin.
       
DESCRIBE TABLE lt_eaus LINES lin.
       
MODIFY eaus FROM TABLE lt_eaus.
       
IF sy-subrc = 0.
         
WRITE : /  lin, 'records updated in EAUS table'.
       
ENDIF.
     
ENDIF.
   
ENDIF.

 
ENDIF.ENDFORM.                    " UPDATE_MOUT_DTAB*&---------------------------------------------------------------------**&      Form  UPDATE_MIN_DTAB*&---------------------------------------------------------------------**       text*----------------------------------------------------------------------**  -->  p1        text*  <--  p2        text*----------------------------------------------------------------------*FORM update_min_dtab RAISING cx_salv_msg.** get all the Contracts

 
SELECT * FROM ever INTO CORRESPONDING FIELDS OF TABLE lt_ever_min WHERE vertrag IN s_vert.   "vertrag loevm anlage einzdat auszdat
** check if deletion indicator is already set.
 
SORT lt_ever_min BY vertrag.
 
LOOP AT lt_ever_min INTO ls_ever_min.
   
IF ls_ever_min-loevm = 'X'.
     
DELETE TABLE lt_ever_min FROM ls_ever_min.
   
ENDIF.
 
ENDLOOP.** test mode
 
IF p_tmode = 'X'.
   
CLEAR : t_ever.
   
CLEAR lr_alv1.
    t_ever[]
= lt_ever_min[].
   
ASSIGN t_ever TO <l_tab>.
   
CALL METHOD cl_salv_table=>factory*        EXPORTING*          r_container  = g_middle_container
     
IMPORTING
        r_salv_table
= lr_alv1
     
CHANGING
        t_table     
= <l_tab>.

    gr_function
= lr_alv1->get_functions( ).

    gr_function
->set_all( abap_true ).

    gr_columns
= lr_alv1->get_columns( ).

    gr_columns
->set_optimize( c_col_x ).

   
CLEAR g_title.
   
MOVE 'Following enteries will get modified in EVER Table' TO g_title.

    gr_display
= lr_alv1->get_display_settings( ).

    gr_display
->set_striped_pattern( if_salv_c_bool_sap=>true ).

    gr_display
->set_list_header( g_title ).

   
CALL METHOD lr_alv1->display.

 
ENDIF.

 
IF lt_ever_min IS NOT INITIAL AND p_tmode NE 'X'.
   
CLEAR ls_ever_min.
   
LOOP AT lt_ever_min ASSIGNING <fs_ever_min>.
      <fs_ever_min>
-loevm = 'X'.
      <fs_ever_min>
-anlage = ' '.
      <fs_ever_min>
-einzdat = ' '.
      <fs_ever_min>
-auszdat = ' '.
   
ENDLOOP.
   
MODIFY ever FROM TABLE lt_ever_min.
   
IF sy-subrc = 0.
     
CLEAR lin.
     
DESCRIBE TABLE lt_ever_min LINES lin.
     
WRITE : / lin, 'records have been updated in EVER table for Move-In Mismatch Issue'.
   
ENDIF.
 
ENDIF.ENDFORM.                    " UPDATE_MIN_DTAB*&---------------------------------------------------------------------**&      Module  STATUS_9010  OUTPUT*&---------------------------------------------------------------------**       text*----------------------------------------------------------------------*MODULE status_9010 OUTPUT.*  SET PF-STATUS 'xxxxxxxx'.*  SET TITLEBAR 'xxx'.*  SET PF-STATUS 'TEST'.* creating object reference for container
 
CREATE OBJECT container
   
EXPORTING
      container_name
= 'CCONTAINER'.
 
" pass name of the container created in Screen no 9010
*Spliting the main container in to 1 row & 2 coloum
 
CREATE OBJECT splitter_1
   
EXPORTING
      parent 
= container
     
rows    = 2
      columns
= 1.
*getting the reference for the splited container( row 1 & col 1 container )

 
CALL METHOD splitter_1->get_container
   
EXPORTING
      row      
= 1
      column   
= 1
    RECEIVING
      container
= container_1.
*getting the reference for the splited container (row 1 & col 2 container)

 
CALL METHOD splitter_1->get_container
   
EXPORTING
      row      
= 2
      column   
= 1
    RECEIVING
      container
= container_2.
* Populating first internal table to the container
 
CREATE OBJECT container
   
EXPORTING
      container_name
= g_container.

 
CREATE OBJECT grid1
   
EXPORTING
      i_parent
= container_1.

 
CALL METHOD grid1->set_table_for_first_display
   
EXPORTING
      i_structure_name
= 'EAUSV'
   
CHANGING
      it_outtab       
= lt_eausv.
* Populating second internal table

 
CREATE OBJECT container
   
EXPORTING
      container_name
= g_container.

 
CREATE OBJECT grid2
   
EXPORTING
      i_parent
= container_2.
 
CALL METHOD grid2->set_table_for_first_display
   
EXPORTING
      i_structure_name
= 'EAUS'
   
CHANGING
      it_outtab       
= lt_eaus.
** Populating third internal table
ENDMODULE.                 " STATUS_9010  OUTPUT
*----------------------------------------------------------------------**  MODULE exit INPUT*----------------------------------------------------------------------***----------------------------------------------------------------------*MODULE exit INPUT.* free the container memory when exit
 
CALL METHOD container->free.
 
LEAVE PROGRAM.ENDMODULE. " EXIT INPUT*&---------------------------------------------------------------------**&      Module  USER_COMMAND_9010  INPUT*&---------------------------------------------------------------------**       text*----------------------------------------------------------------------*MODULE user_command_9010 INPUT.
 
CALL METHOD cl_gui_cfw=>dispatch.
 
CASE ok_code.
   
WHEN 'BACK'.
     
LEAVE SCREEN.
   
WHEN 'CANCEL'.
     
LEAVE PROGRAM.
   
WHEN 'EXIT'.
     
LEAVE SCREEN .
 
ENDCASE .ENDMODULE.                 " USER_COMMAND_9010  INPUT

 

 

Result Screen added as attachment. This structure will get poplualted based on the contract.

 


Note : Create an attribute OK_CODE type OK in the screen to use user_command module.

These modules get called whenever screen is getting called, or there is any user input.

 

Feel free to ask me in comments,if you have doubt displaying the ALV Splitter Control .


Issue Five now Available: SAP for Utilities Headline News

$
0
0

Wouldn't it be nice to:

  • receive the latest information and be directly informed on which innovations SAP has to offer
  • learn best practices from other customers
  • hear about how you can enhance your portfolio with partner solutions
  • know what is going on in the Utilities community


Issue 5 of SAP for Utilities Headline News is now available, full of news, stories and hot topics in the Utilities industry.

 

You are more than welcome to subscribe. Just send me, Susanne Schlenker, an e-mail simply stating Subscribe to SAP for Utilities - Headline News.

Please note your e-mail address will only be used to receive this newsletter, it will not be forwarded to anyone or used for other purposes.


FYI: Information which cannot wait until the next issue, will be published in Susanne's News Bites blog.

 

Enjoy reading.

 

Best regards,

Susanne Schlenker

 

Preview Issue 5 (click to enlarge):

Capture.JPG

 

See the faces behind SAP for Utilities Headline News in our video:

  Video intro play.jpg

Key Topic: Product Support

$
0
0

What does "Knowledge Base Article" (KBA) mean? Explore the Latest KBAs.

$
0
0

What is a KBA?

SAP Knowledge Base Articles (KBAs) are support documents that help you find answers to questions arising from your daily work with SAP software. In a KBA you will find an incident-specific solution and How to FAQ documents. No coding corrections and modifications are provided.

 

What is the difference between KBAs and SAP Notes?

An SAP Note is a technical document that describes a software issue and its solution. SAP Notes include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs. Depending on the type of error, an SAP Note may also include workarounds, descriptions of how to correct repository objects in the ABAP workbench (known as correction instructions), and/or links to Support Packages that solve the problem. 80% of SAP Notes contain coding corrections.

 

Most recent KBAs:

2042788Various Fi-CA Transactions: Performance Issue after implementing EhP 7
2014202IS-U: Billing terminates with error AH 437
1999288IS-U printing: EA64 child documents of collective bills are not
2032637How to debug a mass activity
1991826IsuMdContractQuery fetching incorrect EINZDAT and AUSZDAT


KBA's from September:

1895682IC Web Client: Not all invoices are displayed in BuAg View
2027247Reverse Charge for invoices for certified reseller - How to build up the scenario in the application form
2042834CRM-IU-MD-PRO: Creating BRF+ Rulesusing Attributes across Product
1970759EL35/RELEABL1: Short Dump CONNE_IMPORT_WRONG_COMP_LENG in EPRINTPA
2047744IC Web Client: Enhanced Bill Correction: dump "Business server page (BSP) Error" concerning relation BuAgPrintDocRel


KBA's from August:

2034292FI-CA transaction FPO2: differences between FI-CA and General Ledger
2035406FI-CA transactions FPO1/FPO1P/FPO4/FPO4P: result is different to the general ledger
1585870ICWC: Technical objects not visible in Web UI
2037246FPY1: Zahlsperren und  SEPA Ausführungsdatum
2047888

CRM-IU: Reuse of Procedures within PMU


KBAs from July:

1977298FI-CA: FPY1 problems with SEPA mandates
2033159FI-CA: FPY1 SEPA Item indicator 031
1771145CRM-IU: Integration of UTIL_SALES components into UTIL_IC role
1976190IS-U Invoicing EA19 terminates with error EA19 >0-115
1805595

BW-IS-U: How to reload Data with Data Source 0UC_SALES_STATS_02

 

Look forward to more KBAs coming up soon.

Key Topic: SAP Multichannel Foundation for Utilities

$
0
0
Important information: If you would like to get notifications just for this document, please click on "Receive email notifications" in the action box on the right upper corner. You need to be logged in to be able to activate this function.
What´s new?
  • Updated: Two-Day Classroom Training in Walldorf on Oct. 6-7, 2014 (German) and Dec. 15-16, 2014 (English). More planned for 2015. Target Audience: Solution Consultants, Developers >>Read more and register
What is it and where are we going?

 


How it works and how can you implement it?
Want to know more....
  • For Online Help please visit our >>SAP Help Portal
  • To access the Administrator´s guide (updated Sept 26, 2014) including configuration details, visit >>SAP Marketplace (choose Industry Solutions > Industry Solution Guides > SAP for Utilities)
  • Sizing guide onSAP Service Marketplace: See the Guide under Products > Performance and Scalability > Sizing > Sizing Guidelines > Industries

 

The SAP Service Marketplace is just for customers and partners. Read what it is and how you can get access SAP Service Marketplace Overview and FAQ


One-Day Seminar: Transforming Assets to a Plan: Learn How to Solve the ISO 55000 Challenge

$
0
0

Hello,

 

Take advantage of this opportunity to learn more about how to solve the ISO 55000 challenge.

 

Register here


Agenda below

 

Invitation: Click to enlarge

Capture.JPG

Capture.JPG

Viewing all 277 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>