Hi,
To use event 940 to populate additional fields in the FI document during the transferring to GL, I am adding a field that is available by standard in
structure ACCIT to structure FKK_ACCIT_CUS with the same name as in structure ACCIT, then I am populating the field in event 940, however when I see the field in FB03 the field is still empty. Am I missing some step? or is event 940 only meant to populate custom fields? what should I use if i need to populate a standard field?
Best regards,
M
When I try to execute billing (EASIBI), I am getting the following error. Not sure how to resolve this issue. No schedule records exist for meter reading unit Message no. TU103 Diagnosis No schedule record was found for the meter reading unit you have entered. The schedule records have either not yet been created or have been deleted.
Hi All,
Hope you all fine and doing great.
I have a requirement where in i have to add few fields at Point Of Delivery ID screen of transaction EEDM10. Is there any BADI or EXIT to add this. I have searched for the related enhancement but i didn't find any specific to the requirement. Kindly help me find the solution for this. Attached is the screen shot which shows where exactly i need to add the fields.
Thanks and Regards,
Mohammed Farooq
Locked by moderator. This site does not exist to do your work for you, nor as a replacement for basic training. Further you clearly haven't read (or understood) the Research Resources and Rules of Engagement. If you wish to participate in this site you MUST adhere to the rules.
Any further posts you make will simply be locked if they break the rules.
While executing EASIBI, the following error occurs I need some help in resolving the issue.
Thanks.
Message was edited by: William Eastman
Hello Experts,
I created a custom variant ZVAR1(say) that takes FLAG as input operand and INTEGER type as Output operand.
This output operand holds integer values(for month difference) that is used by next std variant (INFACT08) in the schema.
My custom variant ZVAR1 should NOT write to the install facts. The next variant writesto the installation facts(using MAC_FACTS_WRITE).
What macro should i use here? I tried mac_output_ioper x_op-o1 but its not working.
In the rate config(EA32), i am seeing that my variant gets called first followed by std variant INFACT08. In debug mode inside the std variant INFACT08 code, i am seeing some values filled up in XY_OBJ & X_OP-O1 structures. i am NOT able to see the value of my output operand coming from the previous variant(ZVAR1).
Can someone tell me what is wrong? Thanks Ricky
Hi experts,
Any solution to reverse proration date? As user key in a wrong proration date.
Cheers,
Lawrence
Dear Experts,
We would like to know the advantages of implementing SAP MFU over SAP UCES.
Can someone draw the comparisons based on the offerings by the two services.
Surely, we want something that should be device independent (can run on desktop/tablet/mobile) , an emerging solution and on which SAP will continue to invest as new developments/enhancements/refinements etc.
I've gone through a lot of blogs that explain / outline SAP MFU as SAP's new strategy to help utilities implement modern customer engagement applications.
But before coming to any conclusion, we would like to hear from the experts 
BR,
Anurag
Hello,
I have one question.
What is main purpose MR documet status 3 - blocked by agent.
it is only one way how to achive through EL27,28,29 using RESET button. this button set status 3.
Is there any function for processing this status.
thanks for explanation
Boris Orlický
Hi,
I have a requirement to write a report program to display the counter values in EL09 (EL09 >>LOGS>>Job Logs>>Counter). Could anyone help me to find the table where these Counter values are fetching.
Regards,
Dipin
Dear Experts,
Contract Overview tab is not appearing in UCES application though it has been configured to "Yes" in XCM.
Please note that we are accessing the application with a test user id which has been created in UME and has assigned Reference User and Business Partner to it.
We are able to access the other screens but Contract Overview tab is not appearing after logging on to UCES application.
Any pointers on the above issue will be highly appreciated!!!
BR,
Anurag
Hi All,
I'm trying to compile a list of SAP IS-U Best Practices.
If you have others we currently use please post them in this post or on [http://www.sap-isu.net/|http://www.sap-isu.net/profiles/blogs/sap-isu-best-practices].
Billing - Billing Class
Best practice is to have billing class as residential, commercial, industrial.
Billing - Portions
Best practice is to have one portion for each billing cycle. For example if the company has only monthly billing and bills each day we would have 21 portions, 1 portion for each billing day.
Meter Reading - Meter Reading Unit
Best practice is to have one meter reading unit containing all the meters in a route that a meter readier can read in a day usually no more than 100 meters.
Portion - End of Billing Period
The month in the End of Billng Period date in the Portion should be January. For example if you need to define 21 portions for your project those portion should have the dates as (if we take 2009 as an example): 2.01.2009, 5.01.2009, 6.01.2009, 7.01.2009, 8.01.2009, 9.01.2009, 12.01.2009, 13.01.2009, 14.01.2009, 15.01.2009, 16.01.2009, 19.01.2009, 20.01.2009, 21.01.2009, 22.01.2009, 23.01.2009, 26.01.2009, 27.01.2009, 28.01.2009, 29.01.2009, 30.01.2009.
If there are customers who are read on the last day of the month you should create one more portion with end billing period date as 31.01.2009.
Billing - Manual Billing
Best practice is to give permission to Manual Billing Transaction only to a few (2-3) users which have been very well trained. Manual Billing transaction is a very flexible transaction and not very good trained users can make big mistakes.
Parallel Processing
When using a parallel processing transaction (Billing, Invoicing, Dunning, etc) the interval lenght should be 1000 for best performance. The number of jobs should be less or equal with the number of number ranges defined for that process.
Billing - Billing Master Data Naming Convention
Best practice is that Billing Master Data Naming Convention to contain a letter to designate the division. Then the remaining letters should be use to best abbreviate the meaning of the respective billing master data.
Example:
01 u2013 Electricity Division
Rate:
Naming Convention
E-XXXXXXXX
where
E = Electricity
XXXXXXXX = best abbreviation for the rate name
Regional Structure
Best practice is to use Regional Structure when default values need to be proposed from the regional structure (meter reading unit, temperature area, grid, etc).
Master Data Number Ranges.
Best Practice is to have different number ranges for different master data objects.
Example:
Business partner starts with 1
contract account starts with 2
contract starts with 3
installation starts with 4
premise starts with 5
connection object starts with 6
device location starts with 7
Error Processing
Best practice to handle errors in SAP IS-U is to use BPEM - Business Process Exception Management component. BPEM is a cross application functionality used to create exception cases from error log and to assign a correction procedure (manul or automatic) to each case.
Billing - Schema
Best practice is to have as many schema as products you sell. Lets say you have 2 residential products with different components: one has a daily charge and electricity consumption charge and the other has only the consumption charge. Is best to have them separate into different schemas as it is much easy to read and handle each product in it's schema then having all the products in one schema.
Customer Service - IC Web
Best practice is to implement IC Web client as the client interaction center. Web IC is want SAP is focusing right now. Old CIC0 will not be supported in the future.
Billing Serial Switching
Best practice in billing serial switching is to use the new Installation Groups concept rather than the old register relationship. Installation Groups is much more flexible and user friendly than the old register relationship.
Customer Service - Master Data Template
Best practice for creating master data (technical or business) is to use master data templates to create all the necessary data insted of creating the master data objects manually. Transaction EPRODCUST is used to create new master data templates based on existing master data template categories. Master data template can be used to quickly create test data in test client.
Business Partner Creation
Best practice is to set up the system to create an customer master in Accounts Receivable module even though there is no integration with SD module. Further down after go live it might be the case to integrate the SD functionalities with IS-U therefore having business partner already set up as customer master in AR would leas to a seamless integration.
Billing - Period End Billing
Best practice for period end billing is not to use it if you are planning to change MRU in the instalation in the middle of the period, or if you want to use alternative portion in the contract.
Who's next?
Thanks,
Daniel Toba
sap isu social network
With the new year arriving, it is a good opportunity to check on your previous discussions. Identify those which are still open and which have been solved, either through your own ingenuity or via the help of a forum member. Identify the solution and mark the response with the correct answer, or add a posting with the information you found which solved your issue. This will go a long way toward making the forum more beneficial to everyone - and will also help yourselves, since soon there likely will be a return to the limits on the number of open threads per user. Get ahead of this and make the Utilities space even better for 2015!
Hello,
In my variant program, i need to export an integer variable(holds months) to an output operand which of INTEGER type. This Output operand should update the Installation facts history.
I tried writing using macro’s : mac_output_ioper x_op-o1,
MAC_FACTS_WRITE X_OP-O1-OPERAND X_OP-O1-OPTYP
but they are NOT working.
Also tried updating izone strcuture but in vain.
I have XY_OBJ & SY_SOBJ as changing parameters. Do i need to update in one of them?
Can anyone suggest me how do I do that?
Thanks
When I try to run a invoice using ESIBI, error occurs as "Sub-transactions in schema XXXX step 0001 inconsistent". the error message details are below. I configured the main and sub transactions correctly in EK 01 and EKA01. I am not able to understand whether the issue is in FICA area or Billing. Appreciate the help. You are billing a contract with the following data: o Company code: MS00. o Division: 20. o Account determination ID: 01. o Main transaction: 0100. These fields and the sub-transactions from the schema steps are used to define the tax determination code in billing. In each schema step, the debit sub-transaction and the credit sub-transaction must produce the same tax determination code. In addition, the tax determination code cannot be blank. In schema ZCASCHEMA1, step 0001, this is not the case: Debit/credit Sub-transaction Tax determination code Debit 0021 Credit 0011
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.
Hi,
While creating print document via EA60 system is indicating that Print document 60000XXXXX printed successfully but showing error as "error in reading table ECHANGE_SERVICE". Kindly suggest possible reasons. Our system is recently updated with EHP7 for SAP ERP 6.0.
Regards
Girish Bahuguna
Hi Amian,
Happy new year!
I found you had discussed payment card process here , I wonder can we process encrypted Credit card number into SAP directly when get confirmation from Card issue company?
thanks !
Mary
Hi All,
In our EHP6 env we are using '03 - Quantity Determination during Meter Reading' functionality for gas division.
We have configured thermal gas billing and for this following have been created:
a) Volume Correction Factor - This is created with 02 thermal gas billing factor (inclusive of temperature and pressure).
VCF is to be calculated based on daily weighted averages of temperature and pressure.
For this:
1) Temperature area is defined and values are defined in TE448 table.
2) Weighting Key (Degree Day) is defined and values are maintained in TE107 table.
3) Gas Pressure Determination checkbox is ticked so that gas pressure is determined via Gas Pressure Area defined.
4) Air Pressure Ares is defined and daily air pressure area values are maintained.
5) Temperature and Pressure extra fields are selected.
6) No Special VCF procedure checkbox is selected so that standard controls defined in VCF procedure are followed.
b) Calorific Value Procedure - Calorific value district is defined and daily values are maintained in TE450 table.
CVP is defined to calculate arithmetic mean of daily values stored in TE450 table.
When actual meter read is entered via EL28 tcode, error - "Gas Factor ITHG cannot be defined uniquely" is returned and no expected MR is calculated.
I believe this error is caused due to the new quantity determination procedure - 03 (introduced in EHP6) defined in customising where gas consumption (in MJ) has to be calculated on save of meter read.
On debugging this issue further we found that there is issue in calculating the gas factor and internal table yt_ithg (SAP program - SAPLEA50, Include - LEA50F02) contains more than one entry. SAP only expects one entry with gas factor calculated.
Can you please let me know if anyone else has encountered this error or is there an issue in our VCF procedure defined?
Thanks,
Mayur
Hi,
I am working with Device Info Records (EG44 Transaction) and I have got the below issue. Can someone please provide some help on this?
Scenario:
1.I have installed the Device Info Record to Installation say from 01.01.2014.
2. Now I have received a request where I have to modify the Register Group for DIR from 15.12.2014 and configuration needs to be changed from Real Time Pricing Device to Non Real Time Pricing Device.
3. So, when I try to perform DIR modification by EG41, it gives me the error "Rate data is no longer consistent".
4 If I try to change the Rate Data first EG70, it doesn't allow me to change the Rate Type as the device still belongs to Real Time Pricing; So Non Real time pricing Rate Type is not allowed.
So till the time the Device Info Record is installed, I cannot change either of the values (Rate Type & Interval Length on Register).
Then I thought of Process as
1. Remove DIR
2. Amend DIR with new value of Register Group
3. Re-Install DIR with New Rate Type
But the problem is once I remove the DIR, it does not open in EG41 as editable. There is an error message "Device is not valid from 15.12.2014 to 15.12.2014 (Message EG065)".
In Short, both the approaches are not working for me right now. Can you please help me with your thoughts, how to handle such situation?
Thanks
Rishi
When running invoice (EASIBI) the following message appears:
No print document type found for creation reason 01 and company code MS00