After implementation of package
SAP_BASIS
70217
73013
73115
74010
transaction SP01 (or SP02) display too many blank lines for ABAP lists.
SAP list output in spool with more than one page has blank spaces.
For example, if there are 2 pages, the first page has some data and then there are a lot of blank lines followed again by data.
Root cause is note 1885860.
Apply note 2169148 (BC-CCM-PRN - Too many blank lines in SP01 display).
>Help >Settings...
"F4 Help"
'X' Control (amodal)
F4 help (multiple selection) is used in several transactions and message DH802 "No values for this selection" is issued.
example:
FP05 - F4-selection for payment lot with selection posting date (BUDAT) 01.05.2016-27.05.2016
Read KBA 2226949 and apply note 1238036.
We had a requirement in our project to interpolate the move in read based on the move out reading. The move-in was performed a day after the move-out and it was required to copy the move-out reading into the move-in reading. We achieved this through the below config.
Picture 1 : SAP Utilities->Device Management->Meter Reading->Basic Settings->Define Control Parameters for Meter Reading Data Processing
Picture 2 : Click the execute button highlighted in picture 1 to get the below screen
Picture 3 : Then under SAP Utilities->Device Management->Meter Reading->Meter Reading Order->Order Creation->Define Automatic Interpolation of Meter Reading Reasons
Picture 4: On clicking the execute button highlighted in picture 3 we will get the below screen. Note that we have marked the 'Auto Interpolation' field for the move in read reason.
Picture 5: Under the Meter Reading Unit (MRU) assigned to the installation, we need to set the number of days under 'Entry Interval' as shown below. Since we had the move in and move out orders created at a difference of 1 day we have set it as 1.
With the above config we were able to successfully interpolate the move in meter reads. This was a new learning for me so I have share it over here, hope this helps!
Background:
This is the second part of the series Interpolating the move-in meter reading in SAP IS-U Device Management . Here I would like to describe the technical fix required to achieve the interpolation of the move-in meter reading through the function module BAPI_MTRREADDOC_UPLOAD.
The config described in the article Interpolating the move-in meter reading in SAP IS-U Device Management correctly interpolates the move-in read while we enter a read through EL28 transaction in any read order which is at an interval defined in the field "Entry Interval" of the MRU assigned to the installation. However if we try to upload the meter reading through the function module BAPI_MTRREADDOC_UPLOAD for the same scenario the interpolation doesn't work!
Analysis:
The reason for the issue described in the Background section is that the function module BAPI_MTRREADDOC_UPLOAD retrieves the data records from EABL and EABLG tables at the beginning of its processing based on the meter read document ID ( EABL-ABLBELNR ) supplied through the tables interface parameter METERREADINGRESULTS. This is because of the fact that we can upload the meter reading for 600 read orders at once through this FM and the initial data retrieval is to minimize the performance issue. In the interpolation routine it refers to these data records and tries to identify a meter read order based on the search criteria created out of the interpolation config described in the article Interpolating the move-in meter reading in SAP IS-U Device Management and fails to find any. Hence only the read orders supplied to the FM are fulfilled.
The interpolation concept works through EL28 transaction because it hits the EABL & EABLG tables directly during the interpolation routine based on the search criteria created out of the interpolation config and pulls the read order correctly which requires interpolation.
Solution:
The solution is to bypass the initial retrieval of the data records in the FM BAPI_MTRREADDOC_UPLOAD so that the interpolation routine may look to the EABL & EABLG tables during its processing. And the FM BAPI_MTRREADDOC_UPLOAD has the provision to achieve this. Below is the code to be written before calling the FM.
Hope this helps!
Introduction:
The transaction code ES31 is used to update the rate category at the installation level. In this article we shall work out updating the rate category at the installation level through programming.
Steps through SAP transaction ES31:
ES31 Initial Screen
Under Installation Time-dependent data section, provide new rate category and click ‘SAVE’.
Steps through a program: Sample Code
DATA : wa_obj TYPE isu01_instln,
wa_auto TYPE isu01_instln_auto,
l_installation TYPE anlage,
l_new_rate_category TYPE tariftyp.
*-----Open the Installation in change mode-----*
CALL FUNCTION 'ISU_S_INSTLN_PROVIDE'
EXPORTING
x_anlage = l_installation "Pass Installation Number Here!
x_keydate = '20160105' "This is the Key Date
x_wmode = '2' "Open up the installation in change mode
IMPORTING
y_obj = wa_obj
y_auto = wa_auto
EXCEPTIONS
not_found = 1
invalid_keydate = 2
foreign_lock = 3
not_authorized = 4
invalid_wmode = 5
general_fault = 6
OTHERS = 7.
IF sy-subrc NE 0.
*--------------Handle failures
RETURN.
ELSE.
SORT wa_obj-eanlh BY bis DESCENDING.
READ TABLE wa_obj-eanlh INDEX 1
ASSIGNING FIELD-SYMBOL(<lfs_eanlh>).
<lfs_eanlh>-tariftyp = l_new_rate_category. "Pass the new rate category here!
ENDIF.
*-----Instructions to save the changes-----*
wa_auto-contr-okcode = 'SAVE'.
wa_auto-contr-use-okcode = 'X'.
wa_obj-auto-contr-use-okcode = 'X'.
wa_obj-auto-contr-okcode = 'SAVE'.
*-----Provide the updated values and instructions for update-----*
CALL FUNCTION 'ISU_S_INSTLN_CHANGE'
EXPORTING
x_anlage = l_installation
x_keydate = '20160105'
x_prorate = 'X'
x_upd_online = 'X'
x_no_dialog = 'X'
x_auto = wa_auto
x_obj = wa_obj
EXCEPTIONS
not_found = 1
foreign_lock = 2
not_authorized = 3
cancelled = 4
input_error = 5
general_fault = 6
OTHERS = 7.
IF sy-subrc NE 0.
*---------------Handle failures
ENDIF.
Scope: This document provides a solution to the requirement "ending the existing installation facts time slice to a specific date via ABAP program".
Background: We implemented the solution for the above requirement in my current assignment. Before sharing it as a document here, I searched in SCN to see if the solution is already available however could not find any. Below are few unanswered threads on this topic.
http://scn.sap.com/thread/1165065
http://scn.sap.com/thread/10754
http://scn.sap.com/thread/3305647
So I hope this piece of information will be useful to the SAP IS-U developers out there!
Solution: The BAPI BAPI_UTILINSTALLATION_CHANFACTcan be used to achieve this task. Say suppose, there exists a time slice starting 1st January 2016 till 31st December 9999 for an operand XYZ ( assume the operand category as USERDEF ) with a value 123. Now we need to end the time slice to a date 31st March 2016, then the code for this would be as below.
************************************************************************************************************
*----Data Declaration
************************************************************************************************************
DATA :
lit_instln_facts_upd TYPE STANDARD TABLE OF bapi_instln_userdef,
lwa_instln_facts_upd TYPE bapi_instln_userdef,
lwa_bapi_return_value TYPE bapireturn1,
l_installation TYPE anlage.
************************************************************************************************************
*----Populate the internal table
************************************************************************************************************
lwa_instln_facts_upd-operand = 'XYZ'.
lwa_instln_facts_upd-fromdate = '20160401'. "time slice starting 1st April 2016
lwa_instln_facts_upd-duedate = '99991231'. "time slice ending 31st December 9999
lwa_instln_facts_upd-udefval1 = '123'.
APPEND lwa_instln_facts_upd TO lit_instln_facts_upd.
************************************************************************************************************
*----Call the BAPI for the update.
************************************************************************************************************
CALL FUNCTION 'BAPI_UTILINSTALLATION_CHANFACT'
EXPORTING
number = l_installation "Pass the installation number to this variable
updforce = 'X'
auto_delete = 'X' "This is the important parameter performing the deletion operation
IMPORTING
return = lwa_bapi_return_value
TABLES
userdeftable = lit_instln_facts_upd.
IF lwa_bapi_return_value-type NE 'E'.
COMMIT WORK.
ENDIF.
The trick here is to delete the time slice starting from 1st April 2016 till 31st December 9999, so that what gets left is the time slice starting 1st January 2016 till 31st March 2016.
Summary: We have learnt the idea / solution to end the installation facts time slice to a specific date using the BAPI BAPI_UTILINSTALLATION_CHANFACT.
Background:
We have been using the BOR object ISUNBSERVC tocreate and endthe non billable service in our present project. We were able to accomplish most of the requirements such as enrolling the customer into a service provider portfolio ( through BOR methodCreate), terminating theservice of a service provider (BOR method End) and the change of supplier scenario ( working out through End and Create BOR methods ).
It was while working on one of the interface which required changing the start date of an existing service contract we got stuck with no standard method / function in hand to do the job. So we had to write a custom method following the logic of the BOR object methodISUNBSERVC.End.
This document details the development done to achieve the task of changing the start date of a non billable service through ABAP program.
Solution:
A custom method with the existing service contract ( ESERVICE-VERTRAG ) and the to be service start date as input parameters. The sample code is as below,
DATA : lwa_eservice TYPE eservice,
lwa_eservice_auto TYPE isuedi_nbservice_auto.
*--Get the contract details
CALL FUNCTION 'ISU_DB_ESERVICE_SINGLE'
EXPORTING
x_vertrag = i_service_contract
IMPORTING
y_eservice = lwa_eservice
EXCEPTIONS
OTHERS = 1.
IF sy-subrc NE 0.
*-- Handle Exception
*-- Exit Out
ENDIF.
*--Get the entire information in the deep structure
CALL FUNCTION 'ISU_S_NBSERVICE_PROVIDE'
EXPORTING
x_vertrag = i_service_contract
x_wmode = '2'
IMPORTING
y_auto = lwa_eservice_auto
EXCEPTIONS
not_found = 1
foreign_lock = 2
general_fault = 3
not_authorized = 4
invalid_wmode = 5
OTHERS = 6.
IF sy-subrc <> 0.
* Handle Exception
* Exit Out
ENDIF.
*--Change the start date
lwa_eservice_auto-eserviced_use = abap_true.
IF i_service_start_date IS SUPPLIED.
lwa_eservice_auto-eserviced-service_start = i_service_start_date.
ENDIF.
CALL FUNCTION 'ISU_S_NBSERVICE_CHANGE'
EXPORTING
x_vertrag = i_service_contract
x_upd_online = abap_true
x_no_dialog = abap_true
x_auto = lwa_eservice_auto
EXCEPTIONS
not_found = 1
foreign_lock = 2
general_fault = 3
input_error = 4
not_authorized = 5
OTHERS = 6.
IF sy-subrc <> 0.
* Handle Exception
* Exit Out
ENDIF.
Background:
EL31 is the transaction for monitoring the meter reading data. These reads are pulled from the table EABL and EABLG. Most of the times because of client requirements the table EABL is enhanced with custom fields. However, the custom fields so added will not be reflected in the transaction EL31 unless we do a small enhancement for that. This document talks about the steps for enhancing the EL31 view with the custom fields.
Steps:
I) Enhance the structure EABLD_EL31.
Note: The above field is pulled from the EABL enhancement structure CI_EABL as shown below.
Also Note: In the same as above, the structures EANL_EL31, ERCH_EL31 and EVER_EL31 can be enhanced for the respective enhancements done in tables EANL, ERCH and EVER.
II) : Change the layout in EL31 to reflect the custom field in the ALV
You might ask yourself how you, as an SAP customer, can continuously influence and improve SAP products especially for the utilities industry?
Our answer is the current Customer Connection program for SAP for Utilities.
SAP customers have great ideas and tons of experience to add value to SAP Products and Solutions. With Customer Connection you can influence the SAP products you are using productively. This is the channel for small enhancements & improvements. The improvement delivery takes place via SAP Notes and Support Packages.
These developments are based on a close collaboration between SAP customers and SAP employees. For this - proven and well established collaboration models via SAP User Groups/Customer Communities are defined.
What do I have to do to participate?
Here is an overview of the whole process and below is a detailed timeline of the project.
Submit your improvement requests now!
The collection of the ideas has started on May 4th, 2016. If you want to learn more about the project please feel free to watch the Kick-off webinar recordings:
May 3rd, 2016 (German language)Access the recording of the session
May 4th, 2016 (English language)Access the recording of the session
For downloading the presentation slide deck, please choose tab Documents & Events on page SAP for Utilities.
Some customers already did submit improvement requests - kindly check! 
Please have a look at our project timeline:
Thank you very much for the valuable and great ideas up to now!!!
We are looking forward to your contribution and we'll keep you posted!
Yours sincerely
Holger Schütt and Max Streibl
After implementation of package
SAP_BASIS
70217
73013
73115
74010
transaction SP01 (or SP02) display too many blank lines for ABAP lists.
SAP list output in spool with more than one page has blank spaces.
For example, if there are 2 pages, the first page has some data and then there are a lot of blank lines followed again by data.
Root cause is note 1885860.
Apply note 2169148 (BC-CCM-PRN - Too many blank lines in SP01 display).
|
|
|  FAQ |
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.
At a Glance(Back to top)
| For Utilities | For Public Sector |
|---|---|
New:SAP Multichannel Foundation for Utilities and Public Sector(MCF) Explained!(Jan. 2016)
New:SAP Multichannel Foundation for Utilities (MCF) - Customers around the world (Feb. 2016)
Do we Need a Mobile App for Customer Self Service? (July 2015)
Multichannel self-service for Utilities from SAP is about more than just adding apps (Sept. 2013)
Release Info (Back to top)
Updated:SAP Multichannel Foundation for Utilities and Public Sector (MCF) - Support package and release information (April 2016)
Technical Info (Back to top)
User Self-Service in standard SAP Gateway (please check very nice video tutorial)
User Provisioning with SAP IDM
Responsive UI Application Configuration
Responsive UI Application Setup for IS-U only Scenario
Desktop UI Application Configuration
New: Cookbook for Responsive UI Application Configuration for Public Sector
New: Responsive UI Custom Theme Creation
Web Analytics Integration and Visualization in SAP Lumira
General Channel Analytics and Reporting
New: iOs Packaged Application Setup for Development
New: Android Packaged Application Setup for Development
Best Practices (Back to top)
SAP Multichannel Foundation for Utilities: First reference customers / Erste Referenzkunden Aug 2015
Learning Material (Back to top)
FAQ (Back to top)
FAQ for SAP Multichannel Foundation for Utilties and Public Sector (MCF)
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.
THE WHY, THE WHAT AND THE HOW OF MAKING DIGITAL ENABLEMENT HAPPEN IN YOUR UTILITY
Quick guide to the Digital Utility
WHY DO WE NEED TO MOVE "BEYOND CRM" TOWARDS CUSTOMER ENGAGEMENT AND COMMERCE
GET AN OVERVIEW OF SAP HYBRIS
"Utilities" is on hybris.com>>LINK
The business perspective:What SAP Hybris can do - a valuable story >>LINK
MORE DETAILS
Coming soon: What SAP Hybris can do for Utilities - An overview
Webinar for partners - requires Partneredge Login: >>LINK
HEAR FROM THE EXPERTS - IN PLAIN WORDS
“I’m a Utility…Get me Outta Here!” Finding your way through the Customer Engagement Jungle
“Digital Customer Innovation” at the International Utilities Conference
THE SOLUTION SET OF SAP HYBRIS FOR UTILITIES - BUILDING ON WHAT YOU HAVE, STEP BY STEP
Contact:
Juergen Kuhmann, Customer Engagement & Commerce Industry Group, Principal for Utilities - located in the United States
Florian Froemberg, Customer Engagement & Commerce Industry Group, Principal for Utilities - located in Germany
Hi Folks,
Today let’s discuss about reconciliation key concept of ISU FICA. Here we will learn and see how the concept works and I will show you with screenshots about how to check if the FICA postings are actually posted in FI.
As a general definition we know that Reconciliation key stores the posting made in the GL accounts and when the recon keys are closed and transferred to FI the totals are posted in the GL. Let us see the entire thing happen and the related TCODES.
Wish you a very happy read. 
The GL account postings can be seen by the tcode: FBL3N.
Let us view of the cash desk clearing GL account initially. We will see all items which are posted today's date.
Now I am taking a Payment from cash desk with the following attributes as seen in the following screen:
Payment is posted in the Reconciliation key ‘my_recon99’.
Let’s see the FPL9 view of the contract account after payment.
We see that the payment is posted in the SAP system under document 30000000608 and a part of the open item is cleared.
Now let’s check if the same amount is posted in the GL account after the payment is posted or not.
Sorry still no items are posted in the GL Account. In order to post the amount in the GL account we need to transfer the Reconciliation key into FI. In order to transfer we need to close the recon key so that no further postings can be done into the same reconciliation key.
In order to do this execute the tcode FPF2.
The status of the recon key ‘my_recon99’ is as the following screen shot shows:
The status of the reconciliation key after making the payment. The recon key is open and further postings can be made in the recon key.
We close the recon key.
After the recon key is closed key the status of the recon key becomes as below:
Now in order to transfer the FICA total records to the FI GL execute the Tcode FPG1.
The recon key attributes changes to the following status: check with tcode FPF2
Now let’s see what does the GL status is in TCode: FBL3N
So now you can see the postings are made to the GL account.
Once GL posting is done you will find the amount have been posted in the table BKPF.
So guys that's all for today.
Please let me know if this document did some value addition to your knowledge-base.
See you in my next document, till then take care of the Love of your Life.
While fulfilling different payment scenarios requests for a customer, I ran into an interesting business situation: since Croatia is not yet adopting SEPA-DD (Single Euro Payment Area - Direct Debit) format, the functionality itself if supported by all banks that operate in this area, but every single one has a different implementation of the functionality.
After acquiring all needed documentation, I had to decide which way to go: try to implement and modify the built-in direct debit functionality or develop sets of programs. Either way, I had to do a blocks of three programs, which are also a three sections I will describe in this document:
I decided to make a set of three programs, one for each phase, for each bank.
Theory around this is quite easy: client comes to the bank and opens the direct debit contract. At defined date, bank send the file to the billing company. Usualy, the file consists of several data than can be easily connected with either client or one of its bills: last bills note to payee, client bank account, or even contract account it (for the banks that support that kind of identification).
Technical implementation in SAP is also quite easy. Ill explain it on one single client / line in the file.
First find out the contract account. You can do that by some of the sent data, as stated above. Most of the banks will give note to payee, from where you have several ways: if you used classification ID implementation, then you can easily read all data from the DFKKOP table, comparing the field OPORD with the given data. If you didnt do that implementation and still note to payee consists of either business partner or contract account, get that data. There isnt any universal solution, as it depends on the data you get and the configuration of your system. What matters is that the "Bank details" area on the business partner needs to be filled (transaction: BP).
Its wise to use a nomenclature for the bank data you will be writting into business partner (field BKVID of the BUT0BKtable). For example, start all direct debits with letter D and use two more letters for bank (DSB, DRF), or any other rule that fits your needs. That way the operater will easily visualy understand what this data is all about.
Next step is entering the Incomming payment method and Bank details for incomming payments, on Payments tab of Contract account master data (transaction: CAA1).
For ABAPers:
Now that we have the business partner and contract account prepared, we can move on. We should process billing (or, which is very unlikely, enter invoices manualy) and run the payment run (transaction: FPY1) with the corresponding parameters (at least: enter Payment Methods, date ranges, contract account ranges (if any) and choose Open items). If everything goes well, you have a successful run with paid invoices, which we now need to process. We will create a file that bank needs to charge clients.
Theory is again quite easy: everything we need is already prepared in the payment run. Again, depending on the bank, and the file format they request, the important data is: client identification (either through bank account number, contract account, note to payee or the external ID that the bank gave us in first step), invoice identification (through document number, unique note to payee / classification key), invoice date and amount.
Technicaly its also quite nice: check DPAYH table, where most of the needed data are. You will not find classification ID there - in case you need it, make a link to the original document via clearing document (combine tables DPAYH and DFKKOP). Also, if the bank asks you for any additional info (like client bank account), in DPAYH you have the contract account from which you can work your way up to any other information you need (remember: you have dedicated nomenclature for bank ID, which helps you with this), even though this exact number is a part of the stated table.
For ABAPers:
Here goes the tricky part. Theory is again simple (as it should always be): bank gives us the information about the successful or rejected payments. Not all banks give both information, but, the only thing we need are the rejected ones, and we get those from all banks. When we get the information from the bank that the bill wasnt successfuly payed (that it was rejected) we put it in a return lot, to reverse the clearing and reopen the original document.
Technicaly its a bit tricky. The bank wont always give you the document number, so we need to find it ourselves. If youre going through classification ID (field OPORD), then you have two documents, like in previous step: you will find the original (invoice) document by classification key, but for return lot you need to reference to the payment document (it means you need to find the payment document via payment document clearing).
Also, some banks will give you the amount (which is an additional check), while the others wont. That means you need to get that information aswell, in order to fill the list in the return lot.
Not all of the following BAPIs allow test run, which is important for checking the file and the data itself, before the actual run. This means you (or your development team) will have to make their own way of checking (either by checking all data separately, or simulating what the BAPIs do - this is up to you, and your business requirements; hint: banks usualy give very precise files).
For ABAPers:
Due to large volume of different banks (and thus formats) I can not give you a cookbook for this. But, I hope I cleared the steps for the software architects and consultants and gave BAPIs for ABAPers to start your way in solving this issue, in case you run to it.
|
|
|  Additional Info |
Overview (Back to top)
Solution Info (Back to top)
Best Practices (Back to top)
Learning Material (Back to top)
Additional Info (Back to top)
Follow us on twitter @SAP Industries
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!
The Digital Utility and The Internet of Things: Converging at the Right Time! (August 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
You might ask yourself how you, as an SAP customer, can continuously influence and improve SAP products especially for the utilities industry?
Our answer is the current Customer Connection program for SAP for Utilities.
SAP customers have great ideas and tons of experience to add value to SAP Products and Solutions. With Customer Connection you can influence the SAP products you are using productively. This is the channel for small enhancements & improvements. The improvement delivery takes place via SAP Notes and Support Packages.
These developments are based on a close collaboration between SAP customers and SAP employees. For this - proven and well established collaboration models via SAP User Groups/Customer Communities are defined.
Where are we today?
The influence space was open to submit improvement requests and to subscribe for other customer's improvement requests until July 15th 2016. Now we have reached the selection phase, where SAP is analyzing the qualified improvement requests. An improvement request (idea) is qualified for the selection phase if 5 or more customer subscribe for the idea. Here a brief summary:
We have got 128 improvement request in total - 78 achieved the minimum of 5 customer subscriptions (qualified for selection phase) - 50 improvement requests are not qualified. Please have a look at the qualified improvement requests in which area they belong to:
Next milestone - Selection Call End of September!
The result of the selection phase will be announced within our selection call end of September. You will receive an invitation for this webinar in time!
For downloading the presentations and recordings of our already held sessions, please choose tab Documents & Events on page SAP for Utilities.
Please have a look at our project timeline:
Thank you very much for the valuable and great ideas we have got!
We are looking forward to your contribution and we'll keep you posted!
Yours sincerely
Holger Schütt and Max Streibl
