Error in creating Document versions

Hi All,
I am working in SAP ERP 6.0 EHP 4.0 system.
I have problem in creating new document versions.
I create a document with functional location and specify the mpd cycle. Then when i try to create a new version by copying the contents created from already created document.I change the MPD cycles in the new version and save it.
once when i display the first document created the mpdcycle specified in version 001 is copied to the 000 version.
The document is inconsistent where versioning of document doesnot work properly.
The problem which i found was the document identification guid remains the same for all the document versions getting created.The last documet version value is stored in the all the previous document versions.
The same is working fine in SAP ERP6.0 EHP3.0 sytem.
Please someone help me in resolving the above issue.
Regards,
Prasad.B

Hi,
Sorry instead of specifying as 2 characters by mistake i typed as 3 character field in the forum. I have maintained only two characters.
I have posted the same question in   
SAP Community Network Forums » ABAP Development » ABAP, General
The forum link for your reference is
I have resolved the issue myself. I have replied with answer for the above question.
Below is the solution for my issue
There is a change in the standard code.The reason for the above problem was because of a missing Enhancemnet point in a standard function module 'CV110_DOC_CREATE_WITH_TEMPLATE'.
** IS-ADEC-MPD - Enhancement to copy MPD data
ENHANCEMENT-POINT CV110_DOC_CREATE_WTEMPL_01 SPOTS ES_SAPLCV110.
+*$*$-Start: CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
+**ENHANCEMENT 1  ZSF_AD_MPD_SAPLCV110.    "active version**+
+*** copy MPD relevant data from templ. doc to current doc**+
  +**CALL FUNCTION 'MPD02_COPY_MPD_DATA'**+
    +**EXPORTING**+
      +**is_draw = ls_draw**+
    +**TABLES**+
      +**ct_drad = lt_drad.**+
+*ENDENHANCEMENT.**$*$-End:   CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
Created a custom enhancement point similar to SAP ECC6.0 EHP 3.0 system.
The reason was the buffer was not getting cleared previously.After inserting the above code the DIR's are getting created withot any issues.
Regards,
Prasad.B

Similar Messages

  • Bapi-salesorder creation error in  creating document

    hai friends..
      iam doing creation of sales order using bapi .-structures..
      but error in creating doucment ....
    can u send me some example .. abt sales order .creation ..
    once u check my code ...
    DATA: BEGIN OF HEADER OCCURS 0,
           VBELN LIKE BAPIVBELN-VBELN,
           AUART LIKE VBAK-AUART,
           VKORG LIKE VBAK-VKORG,
           VTWEG LIKE VBAK-VTWEG ,
           SPART LIKE VBAK-SPART,
           VKBUR LIKE VBAK-VKBUR,
           KUNNR LIKE BAPIPARNR-PARTN_NUMB ,"vbak-kunnr,
        END OF HEADER.
    DATA: BEGIN OF ITEM OCCURS 0,
           VBELN LIKE BAPIVBELN-VBELN,
           POSNR LIKE BAPISDITM-ITM_NUMBER ,"vbap-posnr,
           MATNR LIKE VBAP-MATNR,
          NETWR LIKE VBAP-NETWR,
           KWMENGE LIKE VBAP-KWMENG,
          WERKS LIKE VBAP-WERKS,
          NETPR LIKE VBAP-NETPR,
       END OF ITEM.
    DATA:  ORDER_HEADER_IN LIKE BAPISDHD1,
           ORDER_HEADER_INX LIKE BAPISDHD1X.
    DATA: ITAB_HEAD likE order_header_in,
          ITAB_HEADX likE ORDER_HEADER_INX.
    DATA: ITAB_ITEM  TYPE STANDARD TABLE OF  BAPISDITM WITH HEADER LINE,
          ITAB_ITEMX TYPE STANDARD TABLE OF  BAPISDITMX WITH HEADER LINE.
    DATA: KUST TYPE STANDARD TABLE OF  BAPIPARNR WITH HEADER LINE,
           RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA: VNO  LIKE BAPIVBELN-VBELN,
          VCNT LIKE VBAP-POSNR.
    LOOP AT HEADER.
        VCNT = 10.
        CLEAR ITAB_HEAD.
       ORDER_HEADER_IN-REFOBJTYPE = 'OR'.
       ORDER_HEADER_IN-REFOBJKEY = 'OR'.
       ORDER_HEADER_IN-REFDOCTYPE = 'OR'.
       ORDER_HEADER_IN-DOC_TYPE = HEADER-AUART.
        ITAB_HEAD-DOC_TYPE = HEADER-AUART.
        ITAB_HEAD-SALES_ORG = HEADER-VKORG.
        ITAB_HEAD-DISTR_CHAN = HEADER-VTWEG.
        ITAB_HEAD-DIVISION = HEADER-SPART.
        ITAB_HEAD-SALES_OFF = HEADER-VKBUR.
        KUST-PARTN_NUMB = HEADER-KUNNR.
         ITAB_HEADX-DOC_TYPE = 'X'.
         ITAB_HEADX-SALES_ORG = 'X'.
        ITAB_HEADX-DISTR_CHAN = 'X'.
        ITAB_HEADX-DIVISION = 'X'.
        ITAB_HEADX-SALES_OFF = 'X'.
        LOOP AT ITEM WHERE VBELN = HEADER-VBELN.
          REFRESH RETURN.
          ITAB_ITEM-ITM_NUMBER = VCNT.
          ITAB_ITEM-MATERIAL = ITEM-MATNR.
          ITAB_ITEM-NET_WEIGHT = ITEM-KWMENGE.
          APPEND ITAB_ITEM.
          ITAB_ITEMX-ITM_NUMBER = VCNT.
          ITAB_ITEMX-MATERIAL = 'X'.
          ITAB_ITEMX-NET_WEIGHT = 'X'.
          APPEND ITAB_ITEMX.
          VCNT  = VCNT + 10 .
        ENDLOOP.
        CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
          EXPORTING
        SALESDOCUMENTIN               = SALESORDER
            ORDER_HEADER_IN              = ITAB_HEAD
         ORDER_HEADER_INX              = ITAB_HEADX
        SENDER                        =
        BINARY_RELATIONSHIPTYPE       =
        INT_NUMBER_ASSIGNMENT         =
        BEHAVE_WHEN_ERROR             =
        LOGIC_SWITCH                  =
        TESTRUN                       =
        CONVERT                       = ' '
         IMPORTING
           SALESDOCUMENT                 = VNO
          TABLES
           RETURN                        = RETURN
           ORDER_ITEMS_IN                = ITAB_ITEM
           ORDER_ITEMS_INX               = ITAB_ITEMX
            ORDER_PARTNERS                = KUST.
       CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              WAIT          = 'X'.
             IMPORTING
               RETURN        = RETURN.
    LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
    ENDLOOP.
    IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
    ELSE.
    COMMIT WORK AND WAIT.
    ENDIF.
        WRITE: / '   Sales Order NO  IS: ', VNO.
        WRITE: / SPACE.
        CLEAR VNO.
        WRITE SY-ULINE.
      ENDLOOP.
    my HEader  is    123    OR  1000 30 10 SATYA.
    ITem  2  IS     123   10  HAI   15
    once u check it ......

    Hi Satya,
    just check this
    REPORT  Z_STANDARD_SALES_ORDER no standard page heading.
    DATA DECLARATION
    CONSTANTS : C_X VALUE 'X'.
    Structures to hold Sales order header data
    DATA : HEADER LIKE BAPISDHD1," OCCURS 0 WITH HEADER LINE,
           HEADERX LIKE BAPISDHD1X." OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Sales order ITEM DATA
    DATA : ITEM LIKE BAPISDITM OCCURS 0 WITH HEADER LINE,
           ITEMX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Partners ITEM DATA
    DATA : PART LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE.
    Internal Tables to hold Partners SCHEDULE DATA
    DATA: SCHEDULE LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE,
          SCHEDULEX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE.
    Internal table to hold messages from BAPI call
    DATA: RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA  W_MSG(150).
    *DATA: begin of wa_MESSAGE,
         message(150),
         end of wa_message.
    *DATA: itab_msg like table of wa_message with header line.
    Data: Begin of Record occurs 0,
          Control type i,
          DOC_TYPE like HEADER-DOC_TYPE,
          SALES_ORG like HEADER-SALES_ORG,
          DISTR_CHAN like HEADER-SALES_ORG,
          DIVISION like HEADER-DIVISION,
          PURCH_NO_C like HEADER-PURCH_NO_C,
          PARTN_NUMB like PART-PARTN_NUMB ,
          PARTN_ROLE like PART-PARTN_ROLE ,
          ITM_NUMBER like ITEM-ITM_NUMBER,
          MATERIAL like ITEM-MATERIAL,
         TARGET_QTY like item-TARGET_QTY,
          REQ_QTY LIKE BAPISCHDL-REQ_QTY,
          TARGET_QU like item-TARGET_QU,
          PLANT like ITEM-PLANT,
          PMNTTRMS like header-PMNTTRMS,
          End of record.
    data: itab like ALSMEX_TABLINE occurs 0,
          wa like ALSMEX_TABLINE.
    data: SO like BAPIVBELN-VBELN.
    Selection Screen
    selection-screen begin of block b1 with frame title text-001.
    PARAMETERS: P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
    selection-screen end of block b1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
      PERFORM GET_FILE USING P_FILE.
    Start of Selection
    start-of-selection.
      DATA: xl type string.
      xl = '*.xls'.
      IF not P_FILE CP xl.
        Message 'Wrong input file format' type 'E'.
      ENDIF.
      CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                      = P_FILE
          I_BEGIN_COL                   = 1
          I_BEGIN_ROW                   = 1
          I_END_COL                     = 13
          I_END_ROW                     = 3000
        TABLES
          INTERN                        = itab
    EXCEPTIONS
      INCONSISTENT_PARAMETERS       = 1
      UPLOAD_OLE                    = 2
      OTHERS                        = 3
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    DATA POPULATION
      loop at itab into wa.
        if wa-col = '0001'.
          record-Control = wa-value.
        elseif wa-col = '0002'.
          record-DOC_TYPE = wa-value.
        elseif wa-col = '0003'.
          record-SALES_ORG = wa-value.
        elseif wa-col = '0004'.
          record-DISTR_CHAN = wa-value.
        elseif wa-col = '0005'.
          record-DIVISION = wa-value.
        elseif wa-col = '0006'.
          record-PURCH_NO_C = wa-value.
        elseif wa-col = '0007'.
          record-PARTN_NUMB = wa-value.
        elseif wa-col = '0008'.
          record-PARTN_ROLE = wa-value.
        elseif wa-col = '0009'.
          record-PMNTTRMS = wa-value.
        elseif wa-col = '0010'.
          record-ITM_NUMBER = wa-value.
        elseif wa-col = '0011'.
          record-MATERIAL = wa-value.
        elseif wa-col = '0012'.
          record-REQ_QTY = wa-value.
        elseif wa-col = '0013'.
          record-TARGET_QU = wa-value.
        elseif wa-col = '0014'.
          record-PLANT = wa-value.
        endif.
        AT END OF row.
          APPEND record.
          CLEAR: wa, record.
        ENDAT.
      endloop.
      DATA: tot_lines type i,
            tot_po type i,
            index type i.
      describe table record lines tot_lines.
      read table record index tot_lines.
      tot_po = record-control.
      DO tot_po times.
        index = index + 1.
        clear: HEADER,HEADERX,ITEM[],ITEMX[],RETURN,RETURN[],SCHEDULE[],SCHEDULEX[], PART[],PART.
        refresh: ITEM[],ITEMX[],RETURN[],SCHEDULE[],SCHEDULEX[],PART[] .
    POPULATE HEADER FLAG.
        HEADERX-UPDATEFLAG = c_x.
        HEADERX-doc_type = c_x.
        HEADERX-SALES_ORG = c_x.
        HEADERX-DISTR_CHAN = c_x.
        HEADERX-DIVISION = c_x.
        HEADERX-PURCH_NO_C = c_X.
        HEADERX-PMNTTRMS = c_X.
        loop at record where control = index.
    POPULATE HEADER DATA FOR PO
          HEADER-DOC_TYPE = record-DOC_TYPE.
          HEADER-SALES_ORG = record-SALES_ORG.
          HEADER-DISTR_CHAN = record-DISTR_CHAN.
          HEADER-DIVISION = record-DIVISION.
          HEADER-PURCH_NO_C = record-PURCH_NO_C.
          HEADER-PMNTTRMS = record-PMNTTRMS.
    *POPULATE ITEM DATA.
          ITEM-ITM_NUMBER = record-ITM_NUMBER.
          ITEM-MATERIAL = record-material.
         ITEM-TARGET_QTY = record-TARGET_QTY.
          ITEM-TARGET_QU = record-TARGET_QU.
          ITEM-PLANT  = record-PLANT .
          APPEND ITEM.
    *POPULATE ITEM FLAG TABLE
          ITEMX-ITM_NUMBER = record-ITM_NUMBER.
          ITEMX-UPDATEFLAG = C_X.
         ITEMX-TARGET_QTY = C_X.
          ITEMX-PLANT = C_X .
          ITEMX-MATERIAL = C_X .
          ITEMX-TARGET_QU = C_X .
          APPEND ITEMX.
    *POPULATE SCHEDULE  TABLE
          SCHEDULE-ITM_NUMBER = RECORD-ITM_NUMBER.
          SCHEDULE-REQ_QTY = RECORD-REQ_QTY.
          APPEND SCHEDULE.
    *POPULATE SCHEDULE  TABLE
          SCHEDULEX-ITM_NUMBER = RECORD-ITM_NUMBER.
          SCHEDULEX-REQ_QTY = C_X.
          APPEND SCHEDULEX.
        endloop.
    *POPULATE PARTNER  TABLE
        PART-PARTN_NUMB = record-PARTN_NUMB.
        PART-PARTN_ROLE = record-PARTN_ROLE.
        APPEND PART.
    *BAPI CALL
        CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
              EXPORTING
               ORDER_HEADER_IN               = HEADER
               ORDER_HEADER_INX              = HEADERX
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
              IMPORTING
               SALESDOCUMENT                 = SO
              TABLES
               RETURN                        = RETURN
               ORDER_ITEMS_IN                = ITEM
               ORDER_ITEMS_INX               = ITEMX
               ORDER_PARTNERS                = PART
               ORDER_SCHEDULES_IN            = SCHEDULE
               ORDER_SCHEDULES_INX           = SCHEDULEX
      ORDER_CONDITIONS_IN           =
      ORDER_CONDITIONS_INX          =
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
        loop at return where type = 'E' and ID NE 'MEPO' and ID NE 'BAPI'.
          WRITE:/ Return-message.
        endloop.
    *Confirm the document creation by calling database COMMIT
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT = 'X'.
    *Messages
        loop at return where type = 'S' and number ne '233'.
         WRITE:/ Return-message.
          CALL FUNCTION 'FORMAT_MESSAGE'
            EXPORTING
              ID        = return-ID
              LANG      = SY-LANGU
              NO        = return-NUMBER
            IMPORTING
              MSG       = W_MSG
            EXCEPTIONS
              NOT_FOUND = 1
              OTHERS    = 2.
          WRITE W_MSG.
         itab_msg-message = w_msg.
         append itab_msg.
          clear: W_MSG.
        ENDLOOP.
      enddo.
         -->P_W_FILE  text
    FORM GET_FILE  USING    P_W_FILE.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        CHANGING
          FILE_NAME     = P_W_FILE
        EXCEPTIONS
          MASK_TOO_LONG = 1
          OTHERS        = 2.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.     "GET_FILE
    Regards,
    Sachin

  • Error when creating document flow for delivery

    Hi,
    I would like to post the GR for Inbound delivery. I receive an error the TO is not confirmed. I have tried to confirm the tranfer order and I receive the "error when creating document flow for delivery . In order to avoid inconsistencies the goods movement posting was cancelled." It seems like the document already exist.
    How can I do to confirm the TO and post the GR.
    Thanks
    Dede

    In Inbound delivery after GR only a TO is created and confirmed.
    So please check the PO history and see a GR is there or not .
    Once a GR is found create a TO and do the confirmation

  • Getting Error while creating Document object  after  parsing XML String

    Hi All,
    I have been trying to parse an XML string using the StringReader and InputSource interface but when I am trying to create Document Object using Parse() method getting error like
    [Fatal Error] :2:6: The processing instruction target matching "[xX][mM][lL]" is not allowed.
    seorg.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
    Please find the code below which i have been experimenting with:
    import java.io.BufferedReader;
    import java.io.FileNotFoundException;
    import java.io.FileReader;
    import java.io.IOException;
    import java.io.StringReader;
    import java.util.List;
    import java.util.*;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.ParserConfigurationException;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    import org.xml.sax.InputSource;
    import org.xml.sax.SAXException;
    import java.io.*;
    public class TestMain {
         public static void main(String[] args) {
              String file = "";
              file = loadFileContent("C:\\Test.xml");
              System.out.println("contents >> "+file);
              parseQuickLinksFileContent(file);
    public static void parseQuickLinksFileContent(String fileContents) {
    PWMQuickLinksModelVO objPWMQuickLinksModelVO = new PWMQuickLinksModelVO();
         try {
    DocumentBuilderFactory factory =           DocumentBuilderFactory.newInstance();
         DocumentBuilder builder = factory.newDocumentBuilder();
         StringReader objRd = new StringReader(fileContents);
         InputSource objIs = new InputSource(objRd);
         Document document = builder.parse(objIs); // HERE I am getting Error.
         System.out.println(document.toString());
    What is happening while I am using builder.parse() method ???
    Thanks,
    Rajendra.

    Getting following error
    [Fatal Error] :2:6: The processing instruction target matching "[xX][mM][lL]" is not allowed.
    seorg.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

  • Error while creating document numbering series via SDK add on

    Dear Experts,
    We receive the following error while creating the document numbering series through the SDK add on
    [Microsoft][SQL Server Native Client 10.0][SQL Server]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
    From the above error message I can suspect the following possibilities
    1. The limit for the document numbering must be less or equal to 2100.
    2. There is a problem in the coding in SDK where it does not allow more than 2100 lines in the database.
    We tried to create manually for the same fiscal year and period indicator disconnecting the add on, the same error occured.
    Then we created a seried for a single document with the period indicator for the next fiscal year, it allowed.
    After creating the document numbering for the next fiscal year, we were able to create the numbering for the previous year also.
    Kindly help us on how to solve the same.
    With regards,
    Yeshwanth Prakash

    Hi
    You have, as far as i can determine without seeing the template,defined no Part Appraiser Column (PAPP) in your template. But you have defined a function on the template to automaticly default the part appraisers.
    On the Appraisal document persons (appraiser / appraisee) are getting defaulted as part-appraisers although no part appraisal column excist,and therefor 00 Part Appraisers are allowed. This gives the error. Remove the Part Appraisers default functionality from the template and this problem will be solved.
    FYI: The reason why this doesn't give a business check error is that the functions to default participants are BAdI's and we have no means of determining wether or not a BAdI implentation will create an inconsistency on the appraisal document.
    Also, the reason that it occurs as a S message and not as E or W is because of programming restrictions in combination with messages. All errors on the Appraisal Document will come as 'S' messages.

  • Error while creating document in cv01n

    In cv01n while attaching excel,word etc.file,at the time of saving error massege given is document can not change.Please provide me solution

    I have checked the img setting ,img setting is ok,still it gives program error  as below,can you suggest me whether reccomndations can implemented or not.
    Note 964021 -Update Task Fails When New Version Created
    Note Language: English Version: 2 Validity: Valid from 07.11.2006
    Summary
    Symptom
    Update task fails when a new version of an old document info record is
    created using CV02n transaction.The system throws an update terminate
    error.
    More Terms
    UPDATE TERMINATE, MESSAGE 26 178, CV200_DB_DOC_UPDATE, CV02N
    Cause and Prerequisites
    Program Error
    Solution
    Implement the note
    Header Data
    Release Status: Released for Customer
    Released on: 07.11.2006 12:13:26
    Priority: Correction with medium priority
    Category: Program error
    Main Component CA-DMS Document management
    Valid Releases
    Software Component Release From
    Release
    To Release and Following
    SAP_APPL 500 500 500
    SAP_APPL 600 600 600
    Support Packages
    Support Packages Release Package Name
    SAP_APPL 500 SAPKH50016
    SAP_APPL 600 SAPKH60008
    Attributes
    Attribute Value
    SAP objects CV200_DB_DOC_UPDATE
    Transaction codes CV02N,CV03N
    Transaktionscodes - manuell CV02N,CV03N
    SAP-Objekte - manuell CV200_DB_DOC_UPDATE
    DownPort/UpPort-WF UpPort check done, symptom
    repaired
    Correction Instructions
    19.06.2008 Page 1 of 2
    Note 964021 -Update Task Fails When New Version Created
    Correction
    Instructio
    ns
    Valid
    from
    Valid
    to
    Software
    Component
    Typ
    e
    Reference
    Correction
    Last
    Changed
    518092 500 500 SAP_APPL C P6DK093226 07.11.2006 17:30:29
    807328 600 600 SAP_APPL C P7DK042952 13.07.2006 14:50:41
    *) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined
    19.06.2008 Page 2 of 2

  • Error while creating Document Templates

    Hi Experts,
    Am getting an ActiveX error while trying to create a document template designer using a webservice I created in the WST. I have consulted note 1018674 and ensured that the following browser settings are activated but still I keep getting the error.
    - Active Scripting
    - Run Active X Controls and plug-ins
    - Initialize and script ActiveX controls not marked as safe
    Also, since I had been trying to create a microsoft word type of template the system does open an instance of the word doc. Can anyone pls advice?
    How can we ensure that the webservice we have created is working. When I try to test the service in the WST tool, I keep getting the message - URL cannot be retrieved. Does it mean that the service has not been created correctly?

    Check if you done all the following settings...
    .NET Framework-reliant components:
    ○     Run components not signed with Authenticode ® Enable
    ○     Run components signed with Authenticode ® Enable
    ActiveX controls and plug-ins:
    ○     Download signed ActiveX controls ® Enable
    ○     Initialize and script ActiveX controls not marked as safe ® Enable
    ○     Run ActiveX controls and plug-ins ® Enable
    ○     Script ActiveX controls marked safe for scripting ® Enable
    Downloads:
    ○     File download ® Enable
    Miscellaneous:
    ○     Installation of desktop items ® Disable
    Scripting:
    ○     Active scripting ® Enable
    ○     Allow paste operations via script ® Enable
    ○     Scripting of Java applets ® Disable
    ●     To enable groupware integration, adjust the browser settings under Tools ® Internet Optionsu2026 ® Security ® Custom Levelu2026 as follows:
    ActiveX controls and plug-ins:
    ○     Download unsigned ActiveX controls ® Prompt.
    ○     Initialize and script ActiveX controls not marked as safe ® Enable
    ○     Run ActiveX controls and plug-ins ® Enable

  • Error while creating document with attachment.

    Hi,
    I am getting an error "An error occured while creating the original attribute for PDF"
    I tried with out file attachment, it works as you know it is simple....
    I tried with various types of attachments like .TXT and .WRD (changed both wsapplication and docfile parameters), however i get the same error. I tried both from presentation and application server (by providing   pf_ftp_dest                = 'SAPFTPA'    pf_http_dest               = 'SAPHTTPA' )
    Any idea on how to solve this?
    All i need is create a DMS document with a PDF attachment from application server. Are there any other ways to solve this issue?
    ws_docdata-documenttype = 'ARE'.
    ws_docdata-description = 'BAPI DMS'.
    ws_docdata-statusextern = 'CR'.
    ws_file-storagecategory = 'DMS_C1_ST'.
    ws_file-wsapplication   = 'PDF'.
    ws_file-description = 'Job output'.
    ws_file-docfile = 'C:\CAD Integ BAPIS_46.pdf'.
    append ws_file to it_files.
    CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
      EXPORTING
         documentdata               = ws_docdata
    IMPORTING
         return                     = v_ret
    TABLES
         documentfiles              = it_files   .
    BREAK-POINT.
    IF v_ret-type CA 'EA'.
      ROLLBACK WORK.
      WRITE : v_Ret-message.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = '5'.
    ENDIF.
    Thanks
    Pavan

    Hi,
    I found that it is due to document type = 'ARE'. I changed hte document type to one of hte standard type 'TST'. It works for presentation server, but does not work for application server. Any ideas? Any help is appreciated with points.
    ws_docdata-documenttype = 'TST'.
    ws_docdata-description = 'BAPI DMS'.
    ws_docdata-statusextern = 'CT'.
    ws_docdata-documentnumber = 'ZNG-10000000017'.
    ws_file-storagecategory = 'DMS_C1_ST'.
    ws_file-wsapplication   = 'PDF'.
    ws_file-description = 'Job output'.
    ws_file-docfile = p_file.
    append ws_file to it_files.
    CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
      EXPORTING
        documentdata               = ws_docdata
       pf_ftp_dest                = 'SAPFTPA'
       pf_http_dest               = 'SAPHTTPA'
    IMPORTING
       documentnumber             = v_docnum
       documentpart               = v_docpart
       documentversion            = v_docver
       return                     = v_ret
    TABLES
       documentfiles              = it_files   .
    IF v_ret-type CA 'EA'.
      ROLLBACK WORK.
      WRITE : v_Ret-message.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = '5'.
    ENDIF.
    Thanks
    Pavan

  • Error while creating Documents in WPC

    Hi All,
    I am trying to create a form using an article template in Web page composer (NW 7.3). When i save the form keying in the required details I get an error saying "Error while saving the document" . This is what i found in Log files and have not been able to find out what is going wrong.
    I have all the required roles but still the form saving doesn't happen.
    Please help.
    #2.0 #2011 12 30 19:44:04:495#+0530#Error#com.sap.nw.pcc.editor.EditorTool$EditorToolDynPage#
    #EP-PIN-WPC-WCM#sap.com/com.sap.nw.pcc.xmleditor#C000AC10D25D11BE0000000100001CE4#1581950000000004#sap.com/com.sap.nw.pcc.xmleditor#com.sap.nw.pcc.editor.EditorTool$EditorToolDynPage#hussain.s#771##2EBA27FD32F011E1A35300000018237E#84d32d4332f011e18d6700000018237e#84d32d4332f011e18d6700000018237e#0#Thread[HTTP Worker [@1002771266],5,Dedicated_Application_Thread]#Plain##
    PCC exception while saving a document: Unable to authenticate request!XSRF token is not valid.
    [EXCEPTION]
    com.sap.nw.pcc.km.service.editor.EditorException: Unable to authenticate request!XSRF token is not valid.
         at com.sap.nw.pcc.editor.EditorBean.saveDocument(EditorBean.java:468)
         at com.sap.nw.pcc.editor.EditorTool$EditorToolDynPage.onSave(EditorTool.java:523)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:173)
         at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:106)
         at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
         at com.sap.nw.pcc.editor.EditorTool.doContent(EditorTool.java:131)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:205)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:121)
         at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$5.service(RequestDispatcherFactory.java:308)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
         at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)
         at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:229)
    Thanks
    Hussain

    Hi Andrea,
    Please try below fix and check if this works for you. This solution has worked for us.
    Logon to NWA, and navigate to Configuration->Infrastructure->Java System Properties.
    Open Java System Properties and select the Instance and choose Show advanced properties.
    In the Details Section, switch to services tab and search for web container.
    Select the Web Container and in the properties serach for the string "XSRF".
    choose the property "xsrf.protection.enabled" . This property is set to true by defualt. Change it to false, save and restart portal.
    Then try saving WPC Forms
    Hope this helps.
    Thanks
    Hussain

  • Error in creating document series at A/R Down payment Invoice

    Dear All,
    One of my client has 4 Regional Offices,one in Delhi,one in Mumbai,one in Chennai and one in Gurgaon.
    For all the other RO's I have created seperate document number series for A/R Down payment Invoice but when I am trying to create a new series for Gurgaon RO, I am receiving an error message as"Another User is Modified(NMC1) ".
    Please put your valuable thought on this issue and help me to resolve this issue.
    Thanks & Regards,
    Ashish

    Close the Document Numbering Screen and Open again and Update the Series.
    Ensure that the Series Nos don't overlap

  • Check InDesign data merge template for errors without creating document?

    I've got a big InDesign template with hundreds of rows. Producing a full batch takes over an hour, and sometimes crashes. The deadline is fast approaching, and I'm waiting for the final minor amendments to the content spreadsheet, which could virtually land any minute.
    I want to check for overset text errors on the current sheet without creating a merged document or PDF, so I can get on with fixing any likely major problems before the final sheet arrives - but I don't want to create a full merged doc, because that will take a very long time and will that doc's content will be obsolete, whereas the overall length of the text will change very little.
    When you create a merged document, you have the option to turn "Generate overset text report" off. What I want to do, is ONLY generate the overset text report, without actually storing the merged document in memory.
    Is this possible?
    The closest I can see is click through the "Next" button in the Data Merge palette with Preview turned on, while watching the "No errors" preflight panel notification at the bottom of the screen. This is probably faster than creating a full merge, but still very slow.

    That is what Indesign does when it does a data merge, it creates copies of the document and there's no way to change this.  Have you tried exporting to PDF (In CS4 you can do this in one step from the original) and printing?  I've never had anyone confirm it definitively but I'm pretty sure that the PDF created will be an 'optimized' one, meaning that when it sends it off to a compatible printer the images will be sent once and cached, with only the text that changes being sent separately.
    Definitely worth comparing it to Publisher for speed anyway, Office programs can merge straight to the printer, but in effect they're doing the same thing.  There are programs out there for doing far fancier stuff than data merge, probably the best is XM Pie, but unless you've got a printer that recognises their language they're a waste of time in this circumstance anyway.

  • Urgent. [Items - Valuation Method] error when creating documents

    I have recently upgraded one of my customers databases to the newest 2005 sp: 01 pl: 45 version
    Before that, they were running 2005, but with no service pack.
    However, after the upgrade they cannot any longer create salesorders, invoices etc!
    They allways get 'Items - Valuation Method' when pressing the add-method.
    Every item is checked as Stock Item, but not purchased Item. I cannot change any of this, it seems.
    But they do NOT use any logistics, they only use SBO as an invoicing system. And they will not use it for logistics in the future either. 'Response to Release of Stock below the Minimum level' is set to 'Without warning'.
    How can I quickly make salesorders/invoices work again? Does anyone know what might have happened during the upgrade?
    Help is highly appreciated!
    Regards, Runar

    Hi Runar,
    I realize that this is a very late response, if you have not already logged a message with SAP support you should do that.
    When releasing 2005 SP01 a lot of the logic of the Inventory transactions where corrected to avoid inconsistencies. Among these changes were certain settings on Items that could no longer be changed.
    Hope it helps.
    Jesper

  • Inbound delivery - Error when creating document flow for delivery #########

    Hello all:
    When attempting to PGI an inbound delivery (via VL06I - For Goods receipt - select inbound delivery - click Post Goods Receipt) I received error messgae VL 659:
    Diagnosis
    As the system was recording the document flow for the goods movement, it determined that the subsequent document number is either blank or identical to the number of the preceding document.
    System response
    In order to avoid inconsistencies, the goods movement posting was cancelled.
    All WMS transfer orders tied to this inbound delivery are complete.  This hasn't happened with any other delivery.    Any suggestions as to what I can do?
    Thanks,
    Bill

    Hi,
    I would suggest you to go trough OSS notes using the error message number as search key (e.g. 352243, 645119, 197864).
    If you fail to find any maybe it would be worth of contacting SAP AG.
    Regards,
    Csaba

  • Error while creating Salesorder using BAPI

    hello frnds,
    I m new to abap and tryin to make use of BAPI_SALESORDER_CREATEFROMDAT1 to create Sales Order
    I have used the progrtam below.
    *& Report  ZSALESBAPITRIAL
    REPORT  zsalesbapitrial.
    TABLES : vbak , vbap.
    Parameter Screen.
    Sales Document Type.
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    Sales document type.
    PARAMETERS: p_auart TYPE vbak-auart OBLIGATORY.
    Sales Organisation.
    PARAMETERS: p_vkorg TYPE vbak-vkorg OBLIGATORY.
    Distribution channel.
    PARAMETERS: p_vtweg TYPE vbak-vtweg OBLIGATORY.
    Division.
    PARAMETERS: p_spart TYPE vbak-spart OBLIGATORY.
    SKIP 1.
    Sold to.
    PARAMETERS: p_sold TYPE vbak-kunnr OBLIGATORY.
    Ship to.
    PARAMETERS: p_ship TYPE vbak-kunnr OBLIGATORY.
    SKIP 1.
    Material(Article No).
    PARAMETERS: p_matnr TYPE vbap-matnr   OBLIGATORY.
    Quantity (Cummulative quantity of sales Order)
    PARAMETERS: p_menge type vbap-kwmeng obligatory.
    Plant(Site )
    parameters: p_plant type vbap-werks obligatory.
    SELECTION-SCREEN END OF BLOCK b1.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
    sales_header_in = header
    sales_header_inx = headerx
    IMPORTING
    salesdocument_ex = v_vbeln
    TABLES
    return = return
    sales_items_in = item
    sales_items_inx = itemx
    sales_schedules_in = lt_schedules_in
    sales_schedules_inx = lt_schedules_inx
    sales_partners = partner.
    Check the return table.
    LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
    ENDLOOP.
    IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
    ELSE.
    WRITE: / 'Document ', v_vbeln, ' created'.
    ENDIF.
    but its giving 'Error in creating document' I m unable to figure wat i m missing . Is it tht i m gving wrong parameters.
    Please help !!!

    Does tht mean i need to add the following code
    Line item number.
    item-itm_number = '000010'.
    itemx-itm_number = 'X'.
    Material
    item-material = p_matnr.
    itemx-material = 'X'.
    Plant
    item-plant    = p_plant.
    itemx-plant   = 'X'.
    Quantity
    item-target_qty = p_menge.
    itemx-target_qty = 'X'.
    APPEND item.
    APPEND itemx.
    For second item.
    Line item number.
    item-itm_number = '000020'.
    itemx-itm_number = 'X'.
    Material
    item-material = '600020001'.
    itemx-material = 'X'.
    Plant
    item-plant    = p_plant.
    itemx-plant   = 'X'.
    Quantity
    item-target_qty = p_menge.
    itemx-target_qty = 'X'.
    APPEND item.
    APPEND itemx.
      Fill schedule lines
    lt_schedules_in-itm_number = '000010'.
    lt_schedules_in-sched_line = '0001'.
    lt_schedules_in-req_qty    = p_menge.
    APPEND lt_schedules_in.
      Fill schedule lines
    lt_schedules_in-itm_number = '000020'.
    lt_schedules_in-sched_line = '0002'.
    lt_schedules_in-req_qty    = p_menge.
    APPEND lt_schedules_in.
      Fill schedule line flags
    lt_schedules_inx-itm_number  = '000010'.
    lt_schedules_inx-sched_line  = '0001'.
    lt_schedules_inx-updateflag  = 'X'.
    lt_schedules_inx-req_qty     = 'X'.
    APPEND lt_schedules_inx.
      Fill schedule line flags
    lt_schedules_inx-itm_number  = '000020'.
    lt_schedules_inx-sched_line  = '0002'.
    lt_schedules_inx-updateflag  = 'X'.
    lt_schedules_inx-req_qty     = 'X'.
    APPEND lt_schedules_inx.
    But i guess it is overwritting my frst material..
    Also i m gettin a error 
    For object rv_beleg, number  range interval doesnot exist
    Pls suggest

  • Create document number range 03 using internal number assignment in AFAB

    Hi Experts,
    Where i have to create number range to Depreciation Posting ? Please mentain Transaction code .
    I had check T Code:AS08 (No Tick is assign)  & FBN1 (Intrenal Tick is assign)
    I am doing T Code AFAB
    Folowing error coming
    Create document number range 03 using internal number assignment
    Message no. AA776
    Diagnosis
    Processing terminated because the document number range 03 for year 2011 was set up with external number assignment.
    System Response
    For periodic posting of depreciation, you have to create a document number range with internal number assignment, since the document numbers are assigned from Financial Accounting.
    Procedure
    Change the number assignment for the number range 03 from external to internal in Customizing for Asset Accounting. See SAP Note 890976 for more information.
    Waiting for reply
    Regards,
    Girish

    locked.  please read the error message and search the IMG (very easy).

Maybe you are looking for