Publish Idocs issue

Hi,
I'm trying to publish idocs from SAP HR to XI, but I can only see the Idocs in HR with status 3(Data passed to port OK)and not in XI environment.
I already confirmed:
at SAP HR,
- RFC destinations(SM59),
- Transactional port(WE21),
- Partner agreement(WE20),
- Logical System for above Partner agreement(BD54),
- EDIDC header recipient port & LS name is OK(WE19).
at SAP XI,
- RFC destinations(SM59),
- Transactional port(WE21),
- technical and business system for sender SAP system(System Landscape Directory),
Do you guys know what could be missing? or what I should check?
Thanks in advance,
Luí

Hi,
At WE19, when we do a standard outbound processing, it retrieves the following warning:
"IDoc 0000000000200079 was saved but cannot or should not be sent"
I already confirmed that transactional ports and partners are OK. At SM58 in both machines, don't have records.
At Runtime Workbench, I find out, that Result of Self-Test retrieves the following messages:
- Can the SLD be reached?
  "RFC destination LCRSAPRFC does not exist"
- Does the Integration Engine know the business system?
  "Function LCR_GET_OWN_BUSINESS_SYSTEM failed (return code = 1)"
- Are roles in SXMS_CONF_ITEMS and SLD consistent?
  "No role for business system defined in SXMS_CONF_ITEMS"
Do you guys know what means the above warnings/errors? Could be missing some environment configuration?
Thank you
Luí

Similar Messages

  • Publish idocs to external system

    Hi,
    We have a business requirement to publish Idocs to an external system, however we don't have any kind of middleware to perform that action.
    Since it is HR master data, we can use change pointers internal table, to create a flat file with that data, and the external system could read it from a shared folder.
    Do you know other options to send idocs to that external system? There is any function to publish idoc via webservices for example?
    How can I solve it technically?
    Thanks in advance!
    Luis Teixeira

    HI,
    Check if this code for automatic processing of idoc helps you.
    REPORT ZFI_BD87 NO STANDARD PAGE HEADING
                    MESSAGE-ID ZZ
                    LINE-SIZE 132.
    *& Program Name          :  ZFI_BD87                                  *
    *& Module Name           :  FINANCE                                   *
    *& Author                :  DEEPTHI REDDY KAUKUNTLA
    *& Creation Date         :  09/22/2006                                *
    *& Program Type          :  Report                                    *
    *& SAP Release           :  4.6C                                      *
    *& Description           :  To  automate the manual IDoc              *
                              processing.                               *
    *-- TABLES
    TABLES: EDIDC,         " Control record(IDoc) Table
            EDIDS.         " Status Record (IDoc) Table
    RANGES : R_DOCNUM FOR EDIDC-DOCNUM.
    *-- INTERNAL TABLES
    *-- Table for holding Control Record details.
    DATA: BEGIN OF IT_EDIDC OCCURS 100,
          DOCNUM LIKE EDIDC-DOCNUM,
          UPDDAT LIKE EDIDC-UPDDAT,
          UPDTIM LIKE EDIDC-UPDTIM,
          END OF IT_EDIDC.
    *-- Table for holding Control Record details.
    DATA: BEGIN OF IT_EDIDS OCCURS 100,
          DOCNUM LIKE EDIDS-DOCNUM,
          STAMID LIKE EDIDS-STAMID,
          STAMNO LIKE EDIDS-STAMNO,
          END OF IT_EDIDS.
    *--                 Selection Screen
    SELECTION-SCREEN BEGIN OF BLOCK S WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS : S_STATUS FOR EDIDC-STATUS,
                     S_MESTYP FOR EDIDC-MESTYP,
                     S_UPDDAT FOR EDIDC-UPDDAT,
                     S_STAMNO FOR EDIDS-STAMNO,
                     S_STAMID FOR EDIDS-STAMID.
    SELECTION-SCREEN END OF BLOCK S.
    *-- START OF SELECTION
    START-OF-SELECTION.
      PERFORM GET_IDOCNUM.
    *&      Form  GET_IDOCNUM
          text
    -->  p1        text
    <--  p2        text
    FORM GET_IDOCNUM.
      REFRESH R_DOCNUM.
      CLEAR   R_DOCNUM.
      SELECT DOCNUM
             UPDDAT
             UPDTIM
             FROM EDIDC INTO TABLE IT_EDIDC
                       WHERE STATUS IN S_STATUS
                       AND MESTYP   IN S_MESTYP
                       AND UPDDAT   IN S_UPDDAT.
      IF NOT IT_EDIDC[] IS INITIAL.
        SELECT DOCNUM
               STAMID
               STAMNO
                   FROM EDIDS INTO TABLE IT_EDIDS
                   FOR ALL ENTRIES IN
                   IT_EDIDC WHERE DOCNUM = IT_EDIDC-DOCNUM
                   AND LOGDAT = IT_EDIDC-UPDDAT AND
                   LOGTIM = IT_EDIDC-UPDTIM
                   AND STAMNO IN S_STAMNO
                   AND STAMID IN S_STAMID.
        LOOP AT IT_EDIDS.
          R_DOCNUM-LOW = IT_EDIDS-DOCNUM.
          R_DOCNUM-SIGN = 'I'.
          R_DOCNUM-OPTION = 'EQ'.
          APPEND R_DOCNUM.
          CLEAR R_DOCNUM.
        ENDLOOP.
      ENDIF.
      IF SY-SUBRC = 0.
        SUBMIT RBDMANI2
          VIA SELECTION-SCREEN
          USING SELECTION-SET 'VARIANT'
          USING SELECTION-SETS OF PROGRAM 'ZFI_BDC87'
             WITH SO_DOCNU IN R_DOCNUM
             WITH SO_MESTY IN S_MESTYP
             AND RETURN.
      ENDIF.
    ENDFORM.                    " GET_IDOCNUM
    regards,
    deepthi

  • XML Publisher Report Issues

    Hi,
    We have customized a report (XML Publisher) in which our template is in XSL format.When using this stylesheet (.XSL) to print out PO's, there are some problems with the page layout, more specifically regarding the page breaks:
    1) Extra empty page is printed - can this be avoided?
    2) If the entire line block does not fit on the page, the line should be completely shifted to the next page (called "widow and orfan control" in MS Word) ?
    How to avoid these issues? Replies will be appreciated.
    Thanks,
    Sumir

    Hi,
    We have customized a report (XML Publisher) in which our template is in XSL format.When using this stylesheet (.XSL) to print out PO's, there are some problems with the page layout, more specifically regarding the page breaks:
    1) Extra empty page is printed - can this be avoided?
    2) If the entire line block does not fit on the page, the line should be completely shifted to the next page (called "widow and orfan control" in MS Word) ?
    How to avoid these issues? Replies will be appreciated.
    Thanks,
    Sumir

  • IDOC ISSUE full point assigned

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Seems like the error is because the user passed through the JCO call does not have the necessary authorizations...in SAP. Trace the authorizations for that user and grant what is needed... in particular the functions about the IDOC setup and structure used by the repository...
    Enjoy

  • IDOC ISSUE-10/10 POINTS ASSIGNED

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Hello,
    If the IDoc is creaetd in systen with error or with anty status,you can view it via we02 transaction.
    But if it's autorisation issue,i guess IDoc will not get created.
    Thanks.

  • Regarding Idoc issue

    Hi Folks,
    I have triggered the Idoc from R/3 to XI.
    For the statue 30: I can see the text as:
    Receiver exists , No filters , No conversion , No version change
    Please let me know the meaning of this.
    can we use any code page conversion parameter in ALE to convert the data.
    Issue is like:
    In the Idoc I am getting the data correctly. But when the Idoc sent to XI with the help of batch run it went with some invalid character set. (I have checked inbound message payload in XI)
    I have re-triggered the same Idoc manually using the logon language as chenese and now it went to XI with the correct Chinese character set.
    Please guide me why it is transferred to Xi with Invalid data for the first time ?
    Thanks,
    SPMD.

    Hi ,
    I will explain you oit clearly.We are sending idoc to XI.
    we have 2 cases here:
    1st case:
    Idoc triggered for the first time and in data segements we can see the data as:
    name : ³£ÖÝÊа²½°Ù»õÓÐÏÞ¹«Ë¾ --this is in data segment.
    In XI (Inbound payload) we see the same data:   (Inbounb payload )
    My doubt is when the same idoc triggered for the first time the data conversion is not done and when the same Idoc is triggered manually the data conversion happend and we se the correct data in chinese format.
    Appreciate your help.
    Thanks,
    SPMD

  • IDOCs issue in XI

    In our IDOC -> XI -> IDOC scenario, we are facing an issue when a large number (~4000) of IDOCs are sent to XI system at the same time.
    The source SAP system sends the IDOCs to the XI system using a system user. When a large volume of IDOCs are sent at the same time, this user takes up all the dialog processes in the XI system.
    The system eventually becomes slow and needs to be restarted.
    One message gets created per IDOC in XI. The mapping between source and target IDOCS is simple. There is no issue with small number of IDOCs.
    Request your suggetions/inputs in this case. Could we make the IDOC process to run in background in XI to avoid this situation?

    Have a look into this thread to know how to improve performance when large IDOCs are transferred:
    Processing of huge IDocs ...
    You can also opt for IDOC packaging : /people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
    Regards,
    Abhishek.

  • Purchase Order Idoc Issue - PORDCR103

    Hello Experts,
    I have one PO and 5 PO Items in my source. I sent Idoc(PORDCR103) to SAP from SAP BODS4 successfully and I was expecting to see 1 PO with 5 items But I saw 5 PO's were created with 5 items each instead of 1 PO with 5 items. Please find attached my Job screenshots.
    Any Idea on this.. Please can anybody share your experience.
    Thanks...Mohan

    This was because of different purchase group's in source data for all other 5 po items. I have resolved this issue by make same purchase group for all 5 po items.

  • Purchase order idoc issue

    Hi,
        I am facing a issue with an inbound purchase order change IDOC (message type: PORDCH).
    I am getting the following error: FM VENDOR_MASTER_DATA_SELECT_15 ; no partner functions found for vendor VENDOR_MASTER_DATA_SELECT_15 1.
    The vendors are configured such that they dont need a partner function. The suprising part is that the same message type idoc from the same vendor got succesfully posted a few days back and a few days after the issue was found, which means the error doesnt occur every time.
    Any input is highly appreciated.
    Thanks,
    Aparna.

    Hi Aparna,
    I want to make changes in an existing PO through an inbound idoc. I am using idoc type PORDCH01 and message type PORDCH, process code BAPI. But I am getting an error "Characteristic does not exist in operating concern".
    Can you please explain how u are using idoc type PORDCH01??
    Thanx in advance,
    Shaleen

  • Purchase Order Outbound Idoc issue. Message Type ORDER

    Hi Experts,
    I am having issue with outbound IDoc generated from Purchase Order.(Message Type ORDER and Basic Type ORDERS05)
    Issue is when i create PO idoc Segment  E1EDP01 and field ACTION populates as 001 this works fine.
    Now when made any changes to the purchase order.* PO trigers one more EDI - Idoc. but the ACTION field is stil as 002.*
    Could any tell me how to fix this.
    Cheers...Gopinath.

    Hi,
    Thank you.
    I have found the issue and fixed.
    Below three setting was missing same has been done in Partner Profile now ok.
    Message type u2013 ORDCHG, Processing Code u2013 ME11 and Change flag On.
    Cheers..Gopinath
    Edited by: Gopinath A.R on Oct 8, 2009 3:14 PM

  • Payext Idocs Issue

    Hi,
    I am generating payext idocs off the back of a payment run (F110). The issue that I have is where I am paying a supplier with multiple invoices, that the individual invoices are all included in the IDOC. When the bank statement is returned to us, for this type of example, the bank statement is delivering all of the invoice references in the Payment Notes section. I am being informed that this is due to my system sending out segments E1EDP02 009 / 010. I am also informed that I need to make changes in FBZP - "Payment methods in Company Code". So far my settings (under payment advice control) here are:-
    1. Note to payee lines on form - None
    2. Payment Advice output according to number of lines - always payment advice
    Also in the DME I am using program RFFOEDI1 and have amended the variant in the output control section to only generate 2 "number of " invoice details.
    Is anyone able to advise please.

    Hi,
    This thread has been created some time ago and recieved no response. Can you please close if you feel this issue/query has been resolved in the meantime. If it has not then please provide additional information in relation to your query. By providing updates to your thread it moves you thread to the first page of thread and increases visibility and possiblity for the multiptude of experts in SDN Forums to offer their support.
    Therefore please update with more information or close thread.
    Thank you for your assistance.
    Regards,
    Brendan.
    (ERP FI/CO SDN/WIKI Moderator)
    http://wiki.sdn.sap.com/wiki/display/ERPFI/ERP+Financials

  • Idoc issue - canbe fixed with enhancement?

    Hi idoc Gurus,
    I have issue related to idoc.
    We have extended the DEBMAS with one custom segment(Z1KNA13).
    Custom segment(Z1KNA13) has three fields. one of the field is to store customer's second address line(cust_address2).
    When someone changes the customer's second address line in Mainframe. It updates the same in SAP.
    And in WE05 under segment Z1KNA13
    Field                                         Value
    cust_address2                       B. P. road
    But if someone deletes the customer's second address line in Mainframe, it does not deletes the same in SAP.
    And in WE05 under segment Z1KNA13
    Field                                         Value
    Even field "Field" is empty.
    Could anyone help me to figure out, where the problem could be.
    Thank you so much in advance.

    Hi,
    Could you please clarify if my understanding is correct..
    You are receiving the IDoc from the Mainframe...When you change the Customer Master in Mainframe then the MAinframe sends an IDoc to SAP with the change vales....the issue when deleting the record might be from mainframe side wherein they do  trigger the IDoc exchange interface only for change and not for delete...if that is the case then you may have to extend your Idoc with another update indicator which states whether to change or delete the address record...
    and based on the update indicator you can update or delete the record in the IDoc processing in SAP end...
    Why I guess this is because you have sadi that the value in the IDoc field is empty..so if mainframe doesnot send the value in IDoc you will not get the value in SAP also...
    Hope you find this helpfull...
    Sitakant...

  • IDoc issue

    Hi,
    i'm trying to test a scenario from idoc  to idoc.Partner profile is defined properly.
    But when i post through runtime work bench i'm facing a issue.PFB error
    error category  - IDOC_ADAPTER
    error id - ATTRIBUTE_IDOC_METADATA
    When i try to load metadata(PI box) i'm unable to load the IDoc its showing as Segment versions could not be read.
    Kinldy suggest on the same.
    Regards,
    Anitha M

    Anitha,
    It seems some issues with the idoc itself. Check in SAP whether it is released properly and dont have any errors. You can also see some info on this error here:
    Error importing Idoc - Unable to read segments
    Regards,
    ---Satish

  • APEX Database Configuration re XML / BI Publisher report issue

    Greetings,
    I have a problem that would be considered database related.
    I am attempting to implement the APEX REPORTS functionality.
    The process currently breaks for me when I have over 45 columns in an XML output in the APEX Reports framework. When I say BREAK, this is a very soft break. It just does not return any XML. The system eventually returns “no response” and then continues normally.
    Looking closer at the DB, I will see the session hanging on, and not completing with very little information. These sessions will stay active for a very long time… possibly indefinitely. They are running as “APEX_PUBLIC_USER”.
    The “current statement” shows as follows…
    BEGIN
       DECLARE
          l_bind_values   wwv_flow_global.vc_arr2;
          i               NUMBER                  := 0;
       BEGIN
          FOR c1 IN (SELECT c001, c002
                       FROM wwv_flow_collections
                      WHERE collection_name = 'SET_BIND_VALUES')
          LOOP
             i := i + 1;
             l_bind_values (i) := c1.c002;
          END LOOP;
          FOR c2 IN (SELECT owner
                       FROM wwv_flows
                      WHERE ID = :fb_flow_id)
          LOOP
             wwv_flow_render_query.print_shared_query
                                         (p_flow_id            => :fb_flow_id,
                                          p_format             => 'XML',
                                          p_xml_structure      => :p1112_xml_structure,
                                          p_query_text         => :p1110_query,
                                          p_query_name         => :p1110_name,
                                          p_query_owner        => c2.owner,
                                          p_items              => :p1111_items,
                                          p_values             => l_bind_values
          END LOOP;
       END;
    END;I have tested this on APEX.ORACLE.COM and I am un-able to reproduce the same issue. It runs fine. This leads me to believe that I have a database setup issue. The problem is that I don’t know where or how to discover.
    Steps (for me) to reproduce:
    1- Create a REPORT QUERY which has a fair number of columns (say 50 – 60)
    2- Go through the wizard steps and finish
    3- Review the Query – Option n the right (under tasks) – click on “Export Report as XML”
    Result = session hangs creating a DB session which does not complete.
    Footprint:
    Application Express: 3.0.1.00.08
    Database: 10.2.0.1.0
    Connecting via a DAD connector from Oracle Application Server
    BI Publisher connection
    Suggestions are welcome.
    Many Thanks.
    --Tim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Just for the off chance that someone else runs into this, I am going to try to brief my findings on the subject related to this issue...
    Previously, in the 3.0.1 version of APEX, our system would generate an OS process which would not terminate. Now in 3.1, it seems as though there is an error that is generated when this issue comes into play. I can, when attempting to get the sample XML from the REPORTS definition screen, generate this output when using the DOWNLOAD button:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    SUMMARY
    TO RECREATE:
    1- CREATE a report with a lot of "columns wide" (about 50).
    2- Create a report using the GENERIC LAYOUT setting for REPORT LAYOUT
    3- RUN or get XML by using the DOWNLOAD or TEST REPORT buttons from the designer page Report Queries>Edit Report Query
    ISSUE: The generic layout has an issue in the code with size....
    PROBLEM: When creating a new report - XML is not available in order to create the required layout. Without a layout, XML will not generate. Standard chicken and egg syndrome.
    WORKAROUND: Create a DUMMY layout and assign it to the QUERY so that the proper XML output can be created.
    --Tim St. Hilaire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Publisher editor issue

    Hi,
    If a try to add a link like this:
    http://portal.myorg.edu/portal/server.pt?open=512...
    using the publisher editor, and save it, the link is Ok. If I reopen the editor, the link is changed to
    "/server.pt?open=512..."
    which is pointing to the content server name, instead of the portal name.
    Any clue how I can disable this editor behavior, or how I can do a work around?
    Thanks!
    Val, GSB University of Chicago

    Val,
    This is an issue with the rich text editor. There are a few ways to work around this. One is to not use the rich text editor at all. Basically making the field a text box. Another is to make another property and call it link1 or something like that. Lastly you can create a content item that does a javascript redirect. This would require you to make a new data entry template with a field for the community id and page number. Then a presentation template that does a redirect to a pt opener location. See the docs for help on those. Then you make a new content item. This could be "comm page bob" for instance. Then in the original content item you highlight your text, then choose link from the menu. Then you choose the content item you created earlier, "comm page bob". This will make a working link that does not get destroyed by the rich text editor. I know this is not ideal, but this is the only way I know of. I have complained to BEA about this behavior many times, but I do not think it will be fixed any time soon. Let me know if you need any more help.
    Andrew Morris | bdg | http://www.thebdgway.com
    [email protected]

Maybe you are looking for

  • [TUTORIAL] GE70 2OE Installing Windows 7 (OS CHANGE)

    Hello Forum, Here is my very first post on this forum... but I wanted to share my experience with switching OS on the new GE70 2OE-015NL (as the product name says, I'm from The Netherlands  ) I bought my GE70 and immidiately wanted to switch my OS to

  • Registration of several reference images in a test image using vision builder

    I have downloaded the trial version of vision builder, and I am attempting a test to determine if it's worth buying: I would like to determine the position and orientation of two reference parts within a set of test images.  I am able to load the ref

  • Install windows xp in bootcamp

    Hi, I need to increase the partition size in my bootcamp running under snow leopard, I did that, but before reinstalling windows xp, the lyon release was available. I installed it with no problems, but now Windows XP will not load. Must I buy a new c

  • Re: WRT350N ----- Very poor Wireless signal strength from my router

    I have a WRT350N router.  I had it for a year now.   In the begining the Wireless Signal strenth was good.  I used to get 4-5 bars in my bed room which is about 10 meters from the router.  Now I have my laptop sitting 1 feet away from the router and

  • How to adjust logical system after coping PRD to QAS in tabels

    Hello I wonder how to adjust logical system after coping PRD to QAS in tabels. I know (the logical system changes) but there is a transaction which adjustes entries in tabeles...