SAP-ISU on CRM 5.0

HI experts
We are currently running CRM 5.0 Now we plan to implement SAP-ISU.Can we implement the same on existing CRM system or we have to go for separate system.
please suggest links to down load the Installation guides  and medai for ISU and documents related to ISU
Points are rewarded
Regards
Kumar

grosso.d79 wrote:
Dear all, i write becasue I need some explanation about WEBUI and SAPGUI on CRM 7.0, because i've no experience on that.
> Is it true that doesn't exist SAPGUI on CRM 7 ?
> I've the following doubts.
> I'm going to update my CRM 5.0 to 7.0 and I've a lot of custom development that needs SAP GUI: custom report, module pool, function module. What happen to them on CRM 7.0 ? I have to use WEBUI or can I continue with the old SAP GUI ?
> And another thing: the following transaction can be used on CRM 7.0 ?
>
> CRM_MKTPL - Market planner
> CRMD_PROF_CHAR - Segment Builder
> SE37, SE38, SE80 to change program/data dictionary.
>
> At the end...I'm intersted to know if there is the possibility to continue with SAP GUI and to ignore the new WEB UI.
> Thank you in advance
>
> Davide
Davide,
             Gui would continue to be there for back end stuff. Tables (SE11) you would still continue to display, maintain. Creation of function module (SE37), report programs (SE38), lots of basis adminstration stuff, batch job scheduling and such stuff would still be done though SAP GUI.
Though SAP is trying to move many things to UI - such instead of EEWB, most of the functionality can be achieved through new AET.
CRM_MKTPL --- not suported, it will give you error message 'SAP GUI transaction CRM_MKTPL is no longer supported; use CRM WebClient UI'
CRMD_PROF_CHAR - you can still open this in CRM 7.0
CRMD_ORDER - you can still open this in CRM 7.0
  Mostly marketing related developments (including TPM) will be taken care of by Web UI as this is newly developed area with lots of enhancements coming up - and GUI use would be reduced day by day even for configurations going forward.
Important is - for almost everything that is done in older versions - there is something in CRM 7.0 that you can use to do that in a better way, so not to worry.
Best Luck!
Thanks,
Rohit

Similar Messages

  • Hardware Spec for SAP ISU 6 + CRM IDES 7

    Hi,
    What would be a recommended hardware spec required to run SAP ISU 6 + CRM IDES 7 with atmost 4-5 concurrent users?
    I plan to implement it using CentOS & SAP MAXDB.
    Thanks & Regards,
    Sumith

    Hi,
    As the concurrent users seem to be less, you only need to ensure disk space (for an ERP and CRM IDES you would need atleast 600-700GB) along with appropriate page file size of approx 120-140GB.
    As for CPU/RAM: a 2 CPU/8Cores (Intel/AMD 2.08GHz) with 32GB RAM should do well enough.
    However, if you plan to do the setup for productive environment please use the SAP Quick Sizer tool.
    Regards,
    Srikishan

  • Sap ISU and CRM

    We are implementing SAP ISU with Billing and Invoicing, next step would be the implementation of CRM for Utilities.  In a part we are using the installation guide of Best Practices for Water Utilities, which presuppose the implementation of CRM. My question is the following: is it possible to do the implementation of billing and invoicing in ERP and afterwards move the billing and invoicing to CRM, without any big efforts?
    Thanks in advance
    Maja

    Maja,
    The IS-U billing engine sits in the SAP for Utilities system. Today, there is not such a thing in the CRM system you can use to do the same. Same it is for invoicing, bill print etc. not to speak of FI-CA. You can't even replicate these objects to CRM.
    The Water Template is not referring to such a thing. It is only levelling he way to a replication the standard objects, such as, business partner, from the ERP system to the CRM system.
    I hope this answers your question.
    Kind regards,
    Fritz

  • SAP ISU UCES - Utility Customer E-services

    Hi Folks,
    We are using CRM IC Webclient and UCES for a SAP ISU and CRM implementation for a utility company. I have following queries to start with.
    1. I understand that UCES works on Java/JSP and can work standalone as well as via EP. Please share documentation as to how to get UCES up and running in both scenarios.
    2. There are certain things which can be done via CRM IC Webclient as well e.g Move-in and Move-out. How would this be different from UCES apart from the fact that it is being created by the customer service agent in the former and by the customer in the later.
    3. Is there a cookbook for development/configuration for UCES ? If so please share.
    Thanks ahead,
    Regards,
    Yuvaraj

    Hi,
    Good day experts,
    iam working on variant programming which is EA88 T.CODE. I've created YAVGCONS variant for avg.consumption which is ISU_YAVGCONS But it goes to short dump. thats why i've created another ISU_YAVGCONS1 For ea00 t.code. when iam execute the ea00 t.code which is under Debug mode. New function module is not triggering? Why? and can i delete old one or else anything i hve to do?
    Plz give me solution
    regards,
    kk

  • Replication of CRM payment in SAP ISU

    Hi Gurus,
    I have a requirement where we need to accept the payment through CRM 7.0 and the same payment should update in SAP FICA through BAPI.
    ISU has already implemented at client side now CRM is going to be implemented.
    Currently client is updating payment through BDC with the transaction FP25(Cheque Lot)
    What setting we require for the same?
    Valuable thoughts will be appreciated..
    Regards
    Kumar

    Hi Bill,
    Thanks for the instant reply.I am totally agree with you that for posting a payment through CRM 7.0 is a standard functionality for card and other payment except cash and we are not substituting it with cash desk.
    Here the requirement is like that the persons who are collecting the payment in the form of cash and cheque at receiving centers are not the employees of the client, they are outsource employees so we can't give them cash desk screen because of some reasons.
    So what we think to create one own CRM payment screen and accept the payment from the same and through BAPI upload the same payment in SAP ISU by calling the program of FP25(Cheque Lot)
    Please correct me if I am wrong.
    Reagards
    Kumar

  • Trigger alert modeler CRM IC based on SAP ISU information

    Hi experts,
    My current client will start a trial with smart meters shortly. These meters will be registered in SAP ISU as devices with a specially reserved device type.
    Device type is not replicated to CRM, but the call center wishes to receive an alert in IC alert modeler if a customer has a smart meter placed.
    My questions:
    - Is it possible to trigger an alert based on information in another system?
    - If so, what would be the best approach (with rough indication of effort involved)?
    - How can this custom made check be used within the alert modeler?
    Alternatively, we could create a special marketing attribute for these customers, but standard SAP cannot use marketing attributes assigned to a Business Partner either. So the question how to integrate custom check within alert modeler remains relevant for this scenario as well.
    Thank you in advance for your help.
    Regards,
    Jeroen
    PS Feel free to contact me if more information is needed!

    solved

  • SAP ISU BP Contact - CRM Activity - CRM IC Interaction record

    Hi   All -
    I have a cookbook which talks about migrating SAP ISU BP Contacts into CRM Activity.
    Now, my question is if I do this, will this show up as a interaction record against the customer in the IC WebClient in CRM?
    We are considering a design where billing supervisors will enter a BP Contact in ISU when customers directly call them about a bill.  Later, if this customer calls the Cust Service Rep, we want this interaction to be visible to the CSR who will only use the CRM Webclient.
    So, I guess indirectly my question is,
    "Is a CRM Activity the same as an CRM WebClient Interaction record"?
    or
    "Is a CRM WebClient Interaction record a type of CRM Activity"?
    Thanks in advance for taking your time to answer this.
    Regards,
    Pradhip.S

    Hello Pradhip,
    the CRM IC Interaction Record is technically a CRM Activity with a certain transaction type. You can configure the replication of IS-U Contacts that the created activity is shown in the Interaction Center as Interaction Record. So you will be able to see the IS-U Contacts created in ERP - for example within a Front Office Process - in CRM as replicated Interaction Records.
    Kind regards,
    Christian

  • CRM Middleware -XI-SAP-ISU

    Hi all,
    1) In connecting between SAP-ISU and SAP-CRM we have CRM Middleware. People are having second thought that it can be done by XI bcz of volume of data from SAP-ISU to SAP-CRM
    Can anybody suggest me which one we can suggest?
    2) In connecting with telephone system to CRM they have already some in built mechanism to connect with CRM , now they are having second thought that we can use XI between
    Can anybody suggest me which one we can suggest?

    Hi venu,
    I hope the following documents ll be useful to u.
    <u>For XI</u>
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    <u>BW WITH SD, FI, CRM:</u>
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    <u>CRM to BW extraction:</u>
    http://help.sap.com/bp_biv135/html/bw.htm
    http://help.sap.com/bp_biv135/html/BW/SalesAnalysis.htm
    http://help.sap.com/bp_biv235/BI_EN/index.htm
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/af/ed833b2ab3ae0ee10000000a11402f/frameset.htm
    check threads for possible 'error' happened
    CRM Data source issue with Delta Load( For BW Gurus only)
    Re: Activities : 0CRM_SALES_ACT_1
    Re: CRM Service Contracts : no records with 0CRM_SRV_CONTRACT_H
    Hope it helps...let me know
    Regards,
    R.Ravi

  • Billing view in SAP ISU CRM - Meter reading not visible

    Hi All,
    We are working on SAP ISU CRM implementation
    In the billing view factsheet ,bill details are visible but meter reading and device is not visible.As one bill document number may have multiple line items  with meter readings in more than one line item
    Can someone guide me how to pick specific line item and viewed it in Billing details.
    Regards
    Ankit

    Hi,
      Your requirement is not clear.
    As per my understanding,u mentioned as multiple meter reading and multiple line items.
    This is due to Price may be block price, check the price key.
    Check the rate steps  line item type and also schema steps
    regards,
    Nags

  • Billing details in SAP ISU CRM : Meter reading not visible

    Hi All,
    We are working on SAP ISU CRM implementation
    In the billing view factsheet ,bill details are visible but meter reading and device is not visible.As one bill document number may have multiple line items  with meter readings in more than one line item
    Can someone guide me how to pick specific line item and viewed it in Billing details.
    Regards
    Ankit

    Hi,
      Your requirement is not clear.
    As per my understanding,u mentioned as multiple meter reading and multiple line items.
    This is due to Price may be block price, check the price key.
    Check the rate steps  line item type and also schema steps
    regards,
    Nags

  • Migration from ISU to CRM

    Hi,
    We are populating SAP ISU via Emigall and proposing to replicate all customer data including BP, CA and Contract and all technical master data including CO, Premise and Device.  This is a lot of objects and data to replicate from ISU to CRM which will mean our migration takes a long time. 
    Are there any other options to populating data into CRM? Would you advice LSMW load into CRM and Emigall load into ISU?
    KR,
    Michelle

    Hi we are proposing to use Emigall (Data migration workbench) to load the following into ISU:-
    BP
    CA
    Contract
    CO
    Premise
    Device
    Reg Structure
    Documents
    Dunning etc
    We are proposing to use CRM middleware to replicate the following objects from ISU to CRM:-
    BP
    CA
    Contract
    CO
    Premise
    Device
    My concern is that the replication from ISU to CRM is very slow and will be our bottleneck during migration weekend. I am looking for ways to speed up this replication including alternative ways of populating CRM.
    KR,
    Michelle

  • Classification View in BP is not replicating to from ISU to CRM

    Hi All,
    I am very new to SAP CRM Middleware. We are upgrading to CRM 7 in out project.
    When we run a request load to replicate BP (Busines Partner) from IS-U to CRM, It successfully replicates all the data from ISU to CRM.
    But only the Classification Data is not getting replicated to CRM. Please see screen shot sbelow:
    ISU Screen shot: XD03--> Additional Data
    In CRM after Replication:
    Attribute 4 is not copied. Can anybody suggest me any solution to this problem?
    Thanks in advance,
    Suman

    Hi Ramana,
    You need to set up CRM middleware for Initial and delta load of Business Partners from R3 to CRM.
    This link may help you ->
    http://help.sap.com/saphelp_crm40/helpdata/en/1c/924555855849ba896b0af806cd343c/frameset.htm
    Cheers,
    Ashish

  • Logical database in SAP-ISU system

    Hello,
    Does any1 knows the LDB available in SAP ISU system. I am searching for LDB (or table join) which containes tables like FKKVKP, EVER, EANL , EVBS & ADRC.
    Regards,
    Abhijeet

    Hello,
    Does any1 knows the LDB available in SAP ISU system. I am searching for LDB (or table join) which containes tables like FKKVKP, EVER, EANL , EVBS & ADRC.
    Regards,
    Abhijeet

  • SAP ISU EMIGALL DISC_DOC IMPORT ERROR

    Hi,
    I am trying to import a converted file with 234 records of DISC_DOC objects with SAP ISU EMIGALL app. I am getting this error:
         Short text                                                                      
                   The current application triggered a termination with a short dump.                                                            
         What happened?                                                                      
                   The current application program detected a situation which really                                                            
                   should not occur. Therefore, a termination with a short dump was                                                            
                   triggered on purpose by the key word MESSAGE (type X).                                                            
         What can you do?          
                   Note down which actions and inputs caused the error.
                   To process the problem further, contact you SAP system
                   administrator.
                   Using Transaction ST22 for ABAP Dump Analysis, you can look
                   at and manage termination messages, and you can also
                   keep them for a long time.
         Error analysis          
                   Short text of error message:
                   Processing canceled
                   Long text of error message:
                   Technical information about the message:
                   Message class....... "EH"
                   Number.............. 000
                   Variable 1.......... " "
                   Variable 2.......... " "
                   Variable 3.......... " "
                   Variable 4.......... " "
         How to correct the error          
                   Probably the only way to eliminate the error is to correct the program.
                   If the error occures in a non-modified SAP program, you may be able to
                   find an interim solution in an SAP Note.
                   If you have access to SAP Notes, carry out a search with the following
                   keywords:
                   MESSAGE_TYPE_X " "
                   SAPLES34ALLG or "LES34ALLGU04"
                   ISU_DISCDOC_OBJECT_GET
                   If you cannot solve the problem yourself and want to send an error
                   notification to SAP, include the following information:
                   1. The description of the current problem (short dump)
                      To save the description, choose "System->List->Save->Local File
                   (Unconverted)".
                   2. Corresponding system log
                      Display the system log by calling transaction SM21.
                      Restrict the time interval to 10 minutes before and five minutes
                   after the short dump. Then choose "System->List->Save->Local File
                   (Unconverted)".
                   3. If the problem occurs in a problem of your own or a modified SAP
                   program: The source code of the program
                      In the editor, choose "Utilities->More
                   Utilities->Upload/Download->Download".
                   4. Details about the conditions under which the error occurred or which
                   actions and input led to the error.
         System environment          
                   SAP-Release 700
                   Application server... "sapec1"
                   Network address...... "10.170.7.71"
                   Operating system..... "HP-UX"
                   Release.............. "B.11.31"
                   Hardware type........ "ia64"
                   Character length.... 16 Bits
                   Pointer length....... 64 Bits
                   Work process number.. 8
                   Shortdump setting.... "full"
                   Database server... "cnvhpx01"
                   Database type..... "ORACLE"
                   Database name..... "EC1"
                   Database user ID.. "SAPSR3"
                   Char.set.... "C"
                   SAP kernel....... 700
                   created (date)... "Oct 22 2007 23:34:45"
                   create on........ "HP-UX B.11.23 U ia64"
                   Database version. "OCI_102 (10.2.0.1.0) "
                   Patch level. 133
                   Patch text.. " "
                   Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
                   SAP database version. 700
                   Operating system..... "HP-UX B.11"
                   Memory consumption
                   Roll.... 16192
                   EM...... 8379680
                   Heap.... 0
                   Page.... 57344
                   MM Used. 3152352
                   MM Free. 1034864
         User and Transaction          
                   Client.............. 230
                   User................ "ANGHELC"
                   Language Key........ "E"
                   Transaction......... " "
                   Transactions ID..... "48B591833C495D0CE10000000AAA0747"
                   Program............. "SAPLES34ALLG"
                   Screen.............. "SAPMSSY0 1000"
                   Screen Line......... 6
                   Information on caller of Remote Function Call (RFC):
                   System.............. "EC1"
                   Database Release.... 700
                   Kernel Release...... 700
                   Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
                   Call Type........... "synchron and non-transactional (emode 0, imode 1)"
                   Inbound TID.........." "
                   Inbound Queue Name..." "
                   Outbound TID........." "
                   Outbound Queue Name.." "
                   Client.............. 230
                   User................ "ANGHELC"
                   Transaction......... "EMIGIMP"
                   Call Program........."SAPMEMIG_IMPORT"
                   Function Module..... "ISU_M_REPORT_SUBMIT"
                   Call Destination.... "sapec1_EC1_23"
                   Source Server....... "sapec1_EC1_23"
                   Source IP Address... "10.170.7.71"
                   Additional information on RFC logon:
                   Trusted Relationship " "
                   Logon Return Code... 0
                   Trusted Return Code. 0
                   Note: For releases < 4.0, information on the RFC caller are often
                   only partially available.
         Information on where terminated          
                   Termination occurred in the ABAP program "SAPLES34ALLG" - in
                    "ISU_DISCDOC_OBJECT_GET".
                   The main program was "RE3TR_EGD01_DCD ".
                   In the source code you have the termination point in line 17
                   of the (Include) program "LES34ALLGU04".
         Source Code Extract               
         Line               SourceCde
         1               FUNCTION ISU_DISCDOC_OBJECT_GET.
         2               *"----
         3               ""Lokale Schnittstelle:
         4               *"  IMPORTING
         5               *"     REFERENCE(X_HANDLE) LIKE  EBAGEN-HANDLE
         6               *"  EXPORTING
         7               *"     REFERENCE(Y_OBJ) TYPE  ISU05_DISCDOC_INTERNAL
         8               *"----
         9               
         10               * read line of objectss's table
         11                 read table iobj into y_obj          
         12                                 with key handle = x_handle          
         13                                 binary search.          
         14                 if sy-subrc <> 0.          
         15               *   invalid handle          
         16               *    message...          
         >>>>>                   message x000(eh).          
         18                 endif.          
         19               ENDFUNCTION.          
         Contents of system fields                         
         Name                         Val.
         SY-SUBRC                         4
         SY-INDEX                         20
         SY-TABIX                         1
         SY-DBCNT                         8
         SY-FDPOS                         2
         SY-LSIND                         0
         SY-PAGNO                         0
         SY-LINNO                         1
         SY-COLNO                         1
         SY-PFKEY                         
         SY-UCOMM                         
         SY-TITLE                         Generated program for migration object DISC_DOC
         SY-MSGTY                         X
         SY-MSGID                         EH
         SY-MSGNO                         0
         SY-MSGV1                         
         SY-MSGV2                                                                                                                                            
         SY-MSGV3                                                                                                                                            
         SY-MSGV4                                                                                                                                            
         SY-MODNO                         0                                                                                                                   
         SY-DATUM                         20080827                                                                                                                   
         SY-UZEIT                         115457                                                                                                                   
         SY-XPROG                         SAPLSYST                                                                                                                   
         SY-XFORM                         SYSTEM_HOOK_OPEN_DATASET                                                                                                                   
         Active Calls/Events                                                                                                                                            
         No.               Ty.                              Program                                                            Include                                   Line
                        Name                                                                                                                             
         5               FUNCTION                              SAPLES34ALLG                                                            LES34ALLGU04                                   17
                        ISU_DISCDOC_OBJECT_GET                                                                                                                             
         4               FUNCTION                              SAPLES34                                                            LES34U10                                   21
                        ISU_O_DISCDOC_ACTION                                                                                                                             
         3               FUNCTION                              SAPLEC85                                                            LEC85U02                                   103
                        ISU_S_DISCDOC_CREATE                                                                                                                             
         2               FUNCTION                              SAPLISU_M_DISCONNECTION                                                            LISU_M_DISCONNECTIONU01                                   221
                        ISU_M_DISCON_DOCUMENT_CREATE                                                                                                                             
         1               EVENT                              RE3TR_EGD01_DCD                                                            RE3TR_EGD01_DCD                                   199
                        START-OF-SELECTION                                                                                                                             
         Chosen variables                                                                                                                                            
         Name                                                                                                                                            
                   Val.                                                  
         No.               5                    Ty.                         FUNCTION
         Name               ISU_DISCDOC_OBJECT_GET                                             
         X_HANDLE                                                            
                   0                                                  
              0                                                       
              0                                                       
         Y_OBJ                                                                               
              0                                                       
              0                                                       
              2,22222E+93                                                       
              0                                                       
         WEDISCACT                                                            
                                  0000  0000000000000000                                     0000
              0     
              0     
              2,22222E+93     
              0     
         WEDISCPOS          
                                  0000000000000000000000  00
              0     
              0     
              2,22222E+44     
              0     
         CO_CORIV          
                   4
              0     
              0     
              33     
              4     
         IOBJ          
                   Table IT_673[1x7240]
                 \FUNCTION-POOL=ES34ALLG\DATA=IOBJ     
                 Table reference: 39     
                 TABH+  0(20) = C000000416A30E60000000000000000000000000     
                 TABH+ 20(20) = 00000027000002A10000000100001C48FFFFFFFF     
                 TABH+ 40(16) = 0400008900000A10000124C001800000     
                 store        = 0xC000000416A30E60     
                 ext1         = 0x0000000000000000     
                 shmId        = 0     (0x00000000)     
                 id           = 39    (0x00000027)     
                 label        = 673   (0x000002A1)     
                 fill         = 1     (0x00000001)     
                 leng         = 7240  (0x00001C48)     
                 loop         = -1    (0xFFFFFFFF)     
                 xtyp         = TYPE#000039
                 occu         = 1     (0x00000001)
                 access       = 1     (ItAccessStandard)
                 idxKind      = 0     (ItIndexNone)
                 uniKind      = 2     (ItUniqueNon)
                 keyKind      = 1     (default)
                 cmpMode      = 8     (cmpManyEq)
                 occu0        = 0
                 groupCntl    = 0
                 rfc          = 0
                 unShareable  = 0
                 mightBeShared = 0
                 sharedWithShmTab = 0
                 isShmLockId  = 0
                 gcKind       = 0
                 isUsed       = 1
                 isCtfyAble   = 1
                 >>>>> Shareable Table Header Data <<<<<
                 tabi         = 0xC000000416A69840
                 pgHook       = 0x0000000000000000
                 idxPtr       = 0x0000000000000000
                 shmTabhSet   = 0x0000000000000000
                 id           = 162   (0x000000A2)
                 refCount     = 0     (0x00000000)
                 tstRefCount  = 0     (0x00000000)
                 lineAdmin    = 1     (0x00000001)
                 lineAlloc    = 1     (0x00000001)
                 shmVersId    = 0     (0x00000000)
                 shmRefCount  = 1     (0x00000001)
                 >>>>> 1st level extension part <<<<<
                 regHook      = Not allocated
                 collHook     = Not allocated
                 ext2         = Not allocated     
                 >>>>> 2nd level extension part <<<<<     
                 tabhBack     = Not allocated     
                 delta_head   = Not allocated     
                 pb_func      = Not allocated     
                 pb_handle    = Not allocated

    hi,
    thanks.i have another doubt.
    In Initialization- Define -> sender system is Empty, but in receiver system it has the company name.where to set the sender machine.
    regards,
    vinodh

  • While creating SAP ISU Device category i got one error message like The material 5 does not exist or is not activated Message no. M3305

    while creating SAP ISU Device category EG01 .i got one error message like The material 5 does not exist or is not activated Message no. M3305

    I don't know EG01 transaction, but if SAP says "material 5 does not exist " then SAP is usually right.
    Can you give an evidence that material 5 exists? e.g. screenshot from  SE16 at table MARA, MARC and MAST

Maybe you are looking for