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:

• Anglian Water
• HydroOne
• More Utilities customer stories

Further information: OpenText homepage

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

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.

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

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.

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

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 .

In the past, there were some issues regarding the dunning statistics display in the dunning proposal (transaction FPVA)  or dunning activity run (transaction FPVB). Either the dunning statistics were completely missing or the dunning statistics were incomplete.

There are correction notes for the missing dunning statistics. You will find more information in Knowledge Base Article 2037520.

If you use parallel processing, you may only see incomplete dunning statistics. Please note that the dunning statistics are written per job and the total dunning statistics is not created by default. There is a work-around which you’ll find in Knowledge Base Article 2077157.

Attention: Regarding the dunning statistics in the dunning activity run: in a productive system, a dunning notice should only be created in a correspondence container (Function module ISU_DUNNING_PR_CORR_CONT_0350). Printing a dunning notice directly from the dunning activity run may only be used for test purposes. 

Therefore, in the SAP standard system the dunning statistics are displayed in the dunning proposal run only and the standard will not display the dunning statistics in dunning activity run.

African SME’s have a unique set of needs and challenges and SAP has tailored their solutions to ensure this market’s future success. Over 185,000 SMEs are already using SAP and this is why:

1. Complete

We deliver a complete set of solutions designed for SME’s in Africa. Our business intelligence and performance management solutions allow you to make better decisions and streamline your processes.

2. Leadership

We are recognised as a leader by industry experts and trusted by SME customers. We currently have over 185,000 SME customers and this number
continues to grow, especially in emerging regions such as Africa. Did you know, 80% of customers using SAP Business One have less than 50 users, showing that SME’s are one of our core target markets.

3. Choice

We offer choices to fit the way you do business. Whether you need packaged or custom designed solution, deployment on demand or on your premise, we can give you the complete, integrated functionality you need – delivered the way you want.

4. Industry

We put our industry expertise to work for you. SME’s in Africa need best-practice support and industry-specific innovation. At SAP, we deliver 1,300+ solutions that have been designed for 25 major industries.

5. Time and value

We help you to start fast and see results in weeks. As an SME in Africa, you want to start seeing value in as little time as possible. Our ERP solutions for SME’s can be deployed within 2 to 12 weeks and our BI solutions within 1 day to 8 weeks, making SAP the logical choice.

6. Insight

Our analytics solutions help you turn information into actionable insight. As a business owner in Africa, you want to free your time from sorting through ad hoc reports, spreadsheets and databases. Our real-time insights give you the ability to drive better decision making with confidence.

7. Innovation

Doing business in Africa means you need to partner with a company which focuses on the technologies that matter, such as Cloud computing, Mobile, In-memory computing and Big Data. We deliver innovations that help your business succeed through R&D investment, acquiring companies that deliver innovation (as opposed to legacy technology) and co-innovating new solutions with customers and partners.

8. Growth

Our solutions are designed to adapt as your business grows. Proven scalability to support from 10 users to more than 1,000 users, coupled with flexible configuration options, means African SMEs can invest in what they need now and can add more later as their business model or organisation changes.

9. Local

SAP solutions for SME’s, meet global and local business requirements in 80+ countries. Whether you’re operating from South Africa, Nigeria or Uganda, we can support you wherever you are.

10. Ecosystem

Access the industry-specific business expertise and technical know-how you need to meet your business and IT challenges. Our extensive ecosystem of partners and customers gives you more choices and more resources.

Are you ready to take your business in Africa to the next level? Contact me directly or call +27 11 235 6045 / 0800 981 334.

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 KBA's:

KBA's from November:

KBA's from October:

KBA's from September:

KBA's from August:

KBAs from July:

Overview

Solution Info

Best Practices

Learning       Material

Additional Info

Overview (Back to top)

• New: Maher Chebbo (VP EMEA, Head of Energy & Natural Resources, SAP) discusses IT/OT Convergence, creating a an end-to-end energy chain and new possibilities for utilities at the European Utility Week 2014, Nov. 2014, view video Interview.
• “Metering & Smart Energy International” focuses on the European Utilities Week in Amsterdam, where SAP was present as a gold sponsor. IT/OT integration was of course one of the main topics at the conference. Too learn more about SAP’s current view on IT/OT jump to page 104 in the "Metering & Smart Energy International" edition.
• 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

Solution Info (Back to top)

• The SAP Data Management solutions are the basis for IT/OT integration.
• SAP Predictive Analytics solutions enable deep insight into combinde data from IT and OT systems.
• The SAP Solution Explorer describes SAP solutions for the Intelligent Grid.
  

Best Practices (Back to top)

• At Teched 2014 Alliander demoed how they use HANA spatial to support predictive maintenance of gas lines; November 2014

• With the SAP HANA platform, Alliander it is gathering and analyzing massive amounts of data to better maintain assets, optimize its grid, and help customers save big on energy bills.
• With the SAP Business Warehouse application as well as SAP Data Services and SAP Information Steward software, data owners at Alliander can take advantage of the latest innovations in reporting and data analysis.

Learning Material  (Back to top)

• coming soon

Additional Info  (Back to top)

• Read about a strategic OEM agreement between Rolta, a leading IT provider who offers "Suite and Rolta OT-IT Integration Suite™ and SAP .

Follow us on twitter @SAP Industries

Overview

Technical Info

Best Practices

Learning        Material

Additional Info

You will find learning material for different features and functions in SAP Service Marketplace under SAP for Utilities - Product Information -> SAP CRM for Utilities -> Learning Material

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

• 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)

Overview

Technical Info

Best Practices

Learning       Material

Additional Info

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.

Overview (Back to top)

• SAP Multichannel Foundation for Utilities SP03 offering a brand new responsive UI out-of-the-box, is now available by Asif Dogar on September 26, 2014
• Release Strategy for the SAP Multichannel Foundation for Utilities by Nicole Huth on July 22, 2014
• SAP Multichannel Foundation for Utilities just got better with Sp02by Mohammed Wasim Arafat on July 2, 2014
• SAP Delivers Multichannel Foundation, Example Apps and Free Workshop!byHenry Baileyon Apr 9, 2014
• SAP Multichannel Foundation for Utilities 1.0: What’s under the hood? by Mohammed Wasim Arafat, Jan. 23, 2014
• Multichannel self-service for Utilities from SAP is about more than just adding apps by Juergen Kuhmann, Sept. 24, 2013

Technical Info (Back to top)

• SAP Multichannel Foundation for Utilities: Analytics by Olga Esipova  on October 2, 2014
• SAP Multichannel Foundation for Utilities: Implement Custom Logic for an Existing Entity by Ming Hao Xie on August 1,2014
• Extending the Interface of an OData Entity Using Custom Fields by Simon Xu on July 30, 2014
• How to customize sample UI application in the standard Multichannel Foundation for Utilities packageby  Satish Srirambhatlaon June 5, 2014
• Multichannel Foundation for Utilities OData services consumption with AngularJS application by Aleh Autushka on May 16, 2014
• Consuming SAP Multichannel Foundation for Utilities OData services through C# and a .NET Client by Ahmad Sebak on May 13, 2014

Best Practices (Back to top)

• coming soon

Learning Material  (Back to top)

• New: Feb 9-10, 2015 - New Training "SAP Multichannel Foundation for Utilities" Now Also in North America
  
• Updated: Further WDEUMC training sessions with the same content are offered in Europe, too. They will take place in 2015 e.g. in Walldorf on March 19-20, June 22-23, Oct. 5-6. see  https://training.sap.com/shop/course/wdeumc-sap-multichannel-foundation-for-utilities-classroom-010-de-en/
• Ramp-up Knowledge Transfer Release 1.0 >>LINK to webpage

Additional Info  (Back to top)

• For Online Help please visit our >>SAP Help Portal
• To access the Administrator´s guide (updated mid-July 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

Overview

Technical Info

Best Practices

Learning        Material

Additional Info

Overview (Back to top)

• Coming Soon: Q1/2015

• SAP HANA Live for Utilities Q4/2014: New Insights for Device-Related Activities and Utilities Quotation
  

• SAP HANA Live for Utilities Q3/2014by Tanja Bader on August 4, 2014

• Now on YouTube: SAP HANA Live for Utilities (edition for SAP ERP) by Stefanie Becker on May 13th, 2014

Video on YouTube:

Technical Info (Back to top)

• Virtual Data Model for Utilities

Best Practices (Back to top)

Getting Started with SAP HANA Live for Utilities by Silvia Wille on July 14, 2014

Learning Material  (Back to top)

Coming Soon

Additional Info  (Back to top)

• Further Information for SAP for Utilities:

  • SAP Help Portalfor product information
  • SAP Service Marketplace (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)

• General information about SAP HANA:

  • SAP HANA webpage
  • SAP HANA Live for SAP Business Suite - SAP Help Portal: Release Notes, Installation, security, configuration and operations information
  • SAP HANA Live Webpage

• Follow us on Twitter @SAP Industries

In the past some customers were not satisfied with the result of the interest calculation (transaction FPI1 and FPINTM1) for cleared documents. They believe that the interest “To-Date” is not correctly determined for certain FI-CA documents.

For already cleared receivables the interest functionality uses the clearing value date (field DFKKOP-AUGVD) as the interest “To-Date”. But the clearing value date is not filled during the clearing with the account maintenance functionality (transaction FP06 or FPMA) because with the account maintenance it is possible
to clear more than one receivable with more than one credit. Therefore, the interest functionality has to find the best interest “To-Date”.  From technical point of view the FI-CA event 2065 calls the function module FKK_GET_VALUEDATE_FOR_INT_CALC if the clearing value date is empty. This function module uses the due date of the item with the highest amount in the clearing process as interest “To-Date”.

With a customer function module for FI-CA event 2065 it is possible to implement your own requirements. More information about this topic is available in KBA 1511725.

This document provides newest Information from Product Support, helping you to keep your system well running.

• New: FI-CA: Interest „To-Date“ determination during the interest calculation by Ronny Friedericks on December 17, 2014
• New: CRM: B2C Process Overviewby Katrin Frenzel on December 09, 2014
  
• FI-CA: Dunning statistics missing or incomplete by Ronny Friedericks on October 22, 2014
• Updated: What does "Knowledge Base Article" (KBA) mean? Explore the Latest KBAs.by Joerg Gotthardt on December 08, 2014
• Updated :Your Vote counts. Are KBAs Helpful? by Joerg Gotthardt on December 08, 2014
• How to create a perfect incident by Katrin Frenzel on July 25, 2014
• Recommendation: For utilities products (like electricity, gas, …) SAP strongly recommends to use PMU instead of PME! by Joerg Gotthardt on July 15, 2014

Further information

• for further information see also the Key Topic CRM for Utilities

A new KBA was created to provide solutions for various problems concerning selections, error messages and dumps in billing and invoicing processes after implementing EHP7 and integrating Convergent Invoicing. It is recommended to apply the corrections provided inside of this KBA. Please follow this link to KBA 2071296

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 6 (click to enlarge):

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

• CRM for Utilties Customer Connection, How You can Improve CRM for Utilities

Read more and register

• SAP Multichannel Foundation for Utilities: Two-Day Classroom Training in Walldorf (in German)

Montreal: Feb. 9-10, 2015

Walldorf, Germany 2015: March 19-20, June 22-23, Oct. 5-6

Target Audience: Solution Consultants, Developers

Read more and register

Past news bites:

• Webcast: ISO 55000: Using SAP Solutions to Support ISO 55000 Standards for Asset Management
• Webcast: Best Practices: How to Bridge the Gap between SAP Structured Data and Unstructured Content for Asset Management Processes
• Webcast: SAP Predictive Maintenance and Service
• Virtual Info Session: Big Data Analytics in Utilities - Lessons from the Trenches
• One-Day Seminar: Transforming Assets to a Plan: Learn How to Solve the ISO 55000 Challenge
• 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
• Multichannel Foundation Workshop - free of charge
• Classroom Training: SAP Energy Portfolio Management 6.04

Most of the time we struggle to find the right transaction code .

Although there are alternate ways to find the tcodes.

1)Using SE93 (Maintain Transaction).

2)Navigating through SAP easy access .

3)Through Google.

There is a tool / t- code which can be used to search and call up SAP ISU transaction quickly using search term.

The Transaction code is “EASY”.

How to find transaction code(s).

Just provide the search term and select the respective ISU Module checkbox.Suppose you want to find the t-code related to device. Provide Device* in the search term am click on execute.

All SAP ISU transactions related to devices will be displayed.

Double clicking on the transaction code will navigate you to that transaction.

I hope this document  will help you in finding the right transaction code easily and quickly.

Henry Bailey, Global Vice President of the IBU Utilities shares his insights from customer and event visits.

Here is the summary of his latest updates. Enjoy reading!

New: Adapt And Run Simple: How The Utilities Industry Is Using Technology To Face The Future (January 2015)

Top Utility Industry Trends Driving The Need For Ongoing Innovation (November 2014)

The Digital Utility and The Internet of Things: Converging at the Right Time! (August 2014)

At CS Week, an estimated 1500 Utility Customer Service professionals came together in San Antonio (May 2014)

SAP Delivers Multichannel Foundation, Example Apps and Free Workshop! (April 2014)

Utilities are moving to the intelligent level of Transmission and Distribution  (March 2014)

The Convergence of Information Technology and Operational Technology is Already Happening – How Can Utilities Best Adapt? (March 2014)

Insights with Henry - The Digital Utilities on YouTube, published on July 2014:

SAP Innovation Video for Utilities on YouTube, published on June 2014:

"Insights with Henry" video on YouTube, published on May 2014:

Follow us on Twitter @SAP Industries

The intent of this document is to provide a brief overview of the installment plan creation and processes (including fields that are changed during the installment plan processes) for newbies.

An installment plan can be created for one or more open items for an account. With an Installment plan you divide source items into several Installment receivable that have a due date in the past or future.

• FPR1: Installment Plan Creation

You must have an open item before you are able to create an Installment plan. Use transaction FPE1 to post a document.

• FPR2: Installment Plan Deactivation/Change

• FPR3: Installment Plan Display

Legends:

OPBEL:   Number of the document in contract accounts receivable and payable

OPUPK: Item number in the FI-CA document

WHGRP: Repetition group

BETRW:  Amount in transaction currency with +/- sign

OPUPW: Repetition item in the FI-CA document

FAEDN:   Net due date

Which fields are changed in the source receivable (table dfkkop) after Installment plan is created?

ABWBL - Number of substitute FI-CA document

ABWTP - Category of substitute FI-CA document

Which fields are changed  in table DFKKOP after an Installment is paid?

AUGST - Clearing Status
AUGDT - Clearing Date
AUGBL -  Clearing document or Printed document
AUGBD - Clearing document posting date
AUGRD -  Clearing Reason
AUGWA - Clearing Currency
AUGBT - Clearing amount in clearing currency
AUGVD - Value date for clearing

Which fields are changed in table DFKKOP after an Installment is deactivated?

ABWBL - Number of substitute FI-CA document (In source receivable)
ABWTP - Category of substitute FI-CA document (In source receivable)

And in FKK_INSTPLAN_HEAD following fields are changed:

        DEADT - Deactivation Date
        DEMAN - Manually deactivated
        DEAGD - Deactivation Reason
        DPUDT - Entry Day Of Installment Plan Deactivation
        DPUTM - Entry Time Of Installment Plan Deactivation

The status is changed as shown below: