SAP ISU Auto Reconnection on payment receipt

Hi Friends,
We need to Automate the process of Auto reconnection on payment received.
i.e When payment received from customer through FPCJ tcode
system will look for the disconnection status and do as follows
            If disconnection Status is 20(Disconnection Started)
               then change Disconnection status to 99( Completed)
1. How can we change this staus from 20 to 99 ?
2. What function fodule to be used for doing this status change.
3. What are the parameters we need to pass to function module for doing this activities.
Thanks
SK

Hi,
It can be done in following steps:
1. Use function module ISU_S_DISCDOC_PROVIDE to populate your AUTO parameter by passing disconnection document.
2. Update following parameters:
AUTO-CONTR-USE-OKCODE    = 'X'.
AUTO-CONTR-OKCODE = 'DARKCOMPL'.
3. Call function module ISU_S_DISCDOC_CHANGE.
This will complete disconnection document.
Hope this helps.
Regards,
Avinash

Similar Messages

  • Standard BAPI to post payment in SAP-ISU

    Hi Experts,
    My client's requirement is the payment via third party should be posted synchronously in SAP-ISU system means payment is accepted by third party and we just need to update that payment in SAP-ISU system. We are trying to achieve this by RFC.
    I came across BAPI_CTRACCTRCTACCNT_PAYBYCARD which post the payment in the system but it need credit card detail. I want to post the payment from third party which can be cash/cheque. I just wanted to know if there is any standard BAPI which can be used to post payment in SAP-ISU system?
    Thanks in Advance,
    Mansoob
    Edited by: Mansoobkhan on Oct 21, 2010 4:08 PM

    Hi you can try with the following BAPI'S
    BAPI_CTRACPAYMINC_CREATE
    BAPI_CTRACPAYMINC_APPEND
    BAPI_CTRACPAYMINC_RELEASE
    BAPI_CTRACPAYMINC_CLOSE
    If you have PI available you should check out the external cash desk functionality.
    Best regards.
    Cristóbal.

  • 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

  • Process to map payment data in soft file format into SAP ISU

    Hi Experts,
    I am preparing TO BE documentation for a power sector client. Currently payment is received in soft file format through below medium -
    ·       Internet Payment Via payment gateway Bill desk.
    ·       Payment using ATM Machines
    ·       Payment Thru Easy Bill Pay option.
    Than currently data is downloaded (CCR for internet, ATM) and entries are posted in cash book.
    Can someone help me what process will be used to upload the data in SAP-ISU system and also post the payment in customer account.
    Thanks in advance,

    Hi,
    You need to develop a customised program to upload the file in a SAP acceptable format and then call SAP standard program RFKKZE00 to process the same, create payment lots and post the amount into customer account.
    You need to perform validation and checks against the file format of the file that you ar uploading.
    Once the file passes the checks, it is reformatted to a file which is accepted by the SAP standard program RFKKZE00.
    A file in the SAP accpted format will have-
    One file header record (BFKKZGR00 structure) per file
    One payment lot header (BFKKZK structure)
    Any number of items (structure BFKKZP)
    You can include data for any number of lots in a file. However, you have to ensure that you always specify the lot header first and then the related line items.
    After you have created reformatted file, then perform a check to ensure that the source file and the reformatted file has the same date and no data has been missed.
    Call the SAP standard program RFKKZE00 (T.code-FPB3) to process the reformatted file.
    You can goto t.code -SLG1 to check for any errors\messages.
    Hope it helps......
    Thanks,
    Amlan

  • Smart-Form name for Printing of Payment-Receipt in Tcode FBCJ

    Dear Sir,
    We use Tcode FBCJ for the making of Cash Payment . To Print the Cash Payment Receipt , we first select the Payment Line Item then Click on Edit --> Print Receipt .
    This call a Smart-Form and Payment Receipt get printed .
    We need to know the name of Smart-Form being used .
    We request SAP experts to kindly guide as whhat is the name of Smart-Form being called in this case .
    We assure to give full points for the suggested solution pl .
    Rgds
    B Mittal

    hi,
    standard smartform for payment receipt is
    FI_CA_PAYMENT_RECEIPT_SAMPL_SF
    reward points if useful,
    siri

  • SAP ISU FICA Posting.

    Hi All,
    I had a requirement which says.
    When a payment is received in third party system, then we have to trigger a RFC to post payment in SAP ISU FICA.
    This RFC will post the payment and return the payment document number.
    what all done in the payment third party system should be posted in SAP synchronously.
    Does any one have an Idea of a  BAPI / RFC which i can use for this purpose.
    Regards,
    Himanshu Sharma

    If you have PI available, you should look into the External cash desk functionality
    http://wiki.sdn.sap.com/wiki/display/ESpackages/ExternalCashDesk
    If you dont have PI available, then you could look into the following BAPIs:
    BAPI_CTRACPAYMINC_CREATE
    BAPI_CTRACPAYMINC_APPEND
    BAPI_CTRACPAYMINC_RELEASE
    BAPI_CTRACPAYMINC_CLOSE
    Best regards,
    Cristobal.

  • Re: Output for Payment Receipt

    Hello Friends,
    I have  a requirement where in I would like to send an output for the customer's payment.
    Basically i would like to send payment receipt output through SAP.
    Can any one help me on this issue .
    Thanks
    Julie

    Hi Julie
    First go for these links:
    invoice as mail
    How to Automate an Invoice Copy to a Customer.
    Define new output type and sent it through mail.
    try and revrt

  • SAP ISU Print Workbench

    Hi,
    Can any one provide me the basics of the SAP ISU Print workbench?
    Regards,
    Chandan
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Sep 23, 2011 11:39 PM

    Hello,
    You need to attach application form for each and every Correspondence Type.
    Few of the Corr types are
    BL44 Outgoing Payment Confirmation
    BL45 Account Statement
    BL46 Capital Transfer Offer
    BL47 Payment Plan
    BL48 Rollover Offer
    BL49 Repayment
    BL50 Borrower Change Without Capital Transfe
    BL51 Deferral of Customer Loan
    BL52 Capitalization of Overdue Items CL
    BL53 Installment Plan Change CL
    BL54 Consumer Loan Confirmation
    BL55 Notice Given by Bank
    BL56 Rescind Credit Life Insurance
    BL57 Confirmation of Change
    BL58 Interest on Arrears Statement
    You can define them in IMG\FICA\Basic Functions\Correspondence\Define Correspondence types.
    <SAP provides lot of correspondence types. You have to copy them from client 000>
    After that you have to define application form for correspondence types in
    IMG\FICA\Basic Functions\Correspondence\Define Application Forms for Correspondence.
    You have to attach SAP defined correspondence forms.
    To trigger correspondence, you have to run FPCOPARA run mentioning relevant correspondence type.
    The data gets updated in table DFKKCOH.
    Do remember that apart from above config, there are various areas of correspondence config you need to do for different categories like Payments, Returns, Refunds , Dunning & Collection agency.
    For ex, for Returns, you attach  application form in Return reason codes, similarly for Dunning, you attach the application form in Dunning activites ...
    To view the list of Application forms, use T-Code EFRM
    Hope this helps
    Rgds
    Rajendra

  • SAP -ISU PrintWorkBench

    Can some one help me with the procedure to use SAP-ISU Print WorkBench

    Hello,
    You need to attach application form for each and every Correspondence Type.
    Few of the Corr types are
    BL44 Outgoing Payment Confirmation
    BL45 Account Statement
    BL46 Capital Transfer Offer
    BL47 Payment Plan
    BL48 Rollover Offer
    BL49 Repayment
    BL50 Borrower Change Without Capital Transfe
    BL51 Deferral of Customer Loan
    BL52 Capitalization of Overdue Items CL
    BL53 Installment Plan Change CL
    BL54 Consumer Loan Confirmation
    BL55 Notice Given by Bank
    BL56 Rescind Credit Life Insurance
    BL57 Confirmation of Change
    BL58 Interest on Arrears Statement
    You can define them in IMG\FICA\Basic Functions\Correspondence\Define Correspondence types.
    <SAP provides lot of correspondence types. You have to copy them from client 000>
    After that you have to define application form for correspondence types in
    IMG\FICA\Basic Functions\Correspondence\Define Application Forms for Correspondence.
    You have to attach SAP defined correspondence forms.
    To trigger correspondence, you have to run FPCOPARA run mentioning relevant correspondence type.
    The data gets updated in table DFKKCOH.
    Do remember that apart from above config, there are various areas of correspondence config you need to do for different categories like Payments, Returns, Refunds , Dunning & Collection agency.
    For ex, for Returns, you attach  application form in Return reason codes, similarly for Dunning, you attach the application form in Dunning activites ...
    To view the list of Application forms, use T-Code EFRM
    Hope this helps
    Rgds
    Rajendra

  • SAP-ISU consultant details

    Hi friends, can any halp me to know SAP-ISU consultant details,
    what are all things i have in that SAP-ISU, whether it's having any programming part like ABAP,

    Hi ARUNKUMAR´,
    gas, water, elelctricity:
    All a mass business: Big numbers of customers, much bigger numbers of document items.
    Main focus is on (sub-module) FI-CA AKA RMCA, means contract acounting. Here you have an interesting kind of userexits: There are hundreds of pre-defined (and well documented) events. You can assign own FUNCTIONS to the events to enrich, change or check data.
    Billing, dunning and payment procedures processed in parralel; quite complex organization of the parrallel processing transactions.
    Alvaro is talking of the PRINT WORKBENCH which integrates the (SAPSCRIPT) forms handling and programming, but you can do a lot more with it.
    Also important/interesting is the customer master data organized using the SAP BUSINESS PARTNER model.
    This is ISU in short.
    Note: The main functions of IS-U are also used in Telecommunications (IS-T) and Media (IS-M).
    Regards,
    Clemens

  • SAP IS-Auto & SAP IS-Utilites in one system

    Hi,
    This is with reference to the thread link give below.
    [Combining different IS solutions on one system;
    Is it possible to activate SAP IS-Auto and SAP IS-Utilities in one System.
    Also if possible please clarify whether SAP IS-Auto and SAP IS-Utilities  are considered an enterprise extension or an enterprise add-on
    With thanks & regards,
    Vinodh

    Thanks Bill !
    As per the thread,  Difference between enterprise extension and enterprise add-on  SAP Auto is an add-on.
    Since SAP ISU is an extension and SAP Auto is an add-on and as they don't share FICA, can we say that both SAP ISU and SAP Auto can be activated in the same system?
    Thanks & regards,
    Vinodh

  • Scrapping Meter(SAP-ISU) post Removal/Replacement

    Kindly refer to the SAP-ISU implementation scenario below:
    A meter(serial number) is issued from stock against a work order(Mov type 261) ,which get physically installed at a site.The issue is done through the transaction MIGO.
    Now after a meter removal/replacement the old meter needs to go back into a "scrap" storage location,as these will be never re-used again.
    Would appreciate,if you can put forth your ideas on how to do this,in terms of movement type to be used,whether it can be done from the same transaction(viz Transaction for removal/replacement).
    Thanks in advance

    Just to understand your suggestion better,you are asking me to do a Goods Receipt of the serialised material, and then transfer post it into a designated scrap storage location,please confirm.
    If I do a GR using MIGO, what do I do the GR against ? Also how do I enter the required serial number/material combination.
    Thanks again.

  • 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

  • Error while sending XML SOAP message to other network

    Hi, I have a java application using SOAP through which I am sending request to a machine in the same network. It is giving the response in xml and i am able to parse it. But when I tried to give the IP in the destination i.e the IP in the other netwo

  • Send SmartForm as Email Body

    Hi All! I need to send a SmarForm by email as an email body. The SmartForm is a simple plain text form. Does someone know how to do it? Regards, Alejandro.

  • Extending af:convertDateTime (and binding property)

    Hello, I have an <af:convertDateTime> in the page: <af:inputDate id="IDATE" value="#{row.bindings.Date.inputValue}">     <af:convertDateTime pattern="#{bindings.TABLE.hints.Date.format}"/> </af:inputDate>I want to customize the converter, but there i

  • [Security:090508]Certificate chain received from 'hostname' was incomplete

    Hey All, I am trying to set up a Managed Server and have it talk to the NodeManager running (Weblogic 8.1 SP2) on the same machine. I can't, however, seem to get a good SSL handshake between the two. I get the following error: ####<Mar 11, 2004 9:55:

  • IOS 7 colors and graphics are hard to read.

    Just downloaded iOS 7. I already enlarged the email text which was tiny.  Can Safari be adjusted? The color scheme of the keyboard is way too pale. The darker  backgrounds were much easier to read. Does anyone know if this be be adjusted. Or did the