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

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

How to create A/R Down payment Invoice

Hi;
I am trying to create A/R Down Payment Invoice through DI API by using the below mentioned object but the system is giving me the following error "Invalid Value. {DPI1.ExLineNo} {Line No. 1}".
SAPbobsCOM.Documents oDoc SAPbobsCOM.Documents)x.CompanyObject.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDownPayments);
            oDoc.Lines.SetCurrentLine(0);
            oDoc.CardCode = "C0001";
            oDoc.Lines.ItemCode = "Test";
            oDoc.Lines.Quantity = 2;
            oDoc.Lines.UnitPrice = 10;
            oDoc.Lines.ActualDeliveryDate = DateTime.Now.Date;
            oDoc.Lines.BaseType = 17;
            oDoc.Lines.BaseLine = 1;
            oDoc.Lines.BaseEntry = 1;
            oDoc.Lines.ExLineNo
            int oRetVal = oDoc.Add();
            if (oRetVal != 0)
                MessageBox.Show(x.CompanyObject.GetLastErrorDescription());
Please suggest me how I can create AR Down Payment Invoice along with Incoming Payment and then wanted to link AR down payment invoice with AR invoice.
Regards;
Deepak

Hi
Try this code
Try
'Create DownPayment Invoice Object
        oDPM = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDownPayments)
        'Set Down Payment Header Values
        oDPM.CardCode = "Some Card code"
        oDPM.DocDueDate = "Suitable Date"
        oDPM.DownPaymentPercentage =" Numeric value (Double)"
        oDPM.DownPaymentType = SAPbobsCOM.DownPaymentTypeEnum.dptInvoice
        'Set Down Payment Line Values
        oDPM.Lines.ItemCode =" Some Item Code"
        oDPM.Lines.Quantity =" Quantity"
        oDPM.Lines.Price =" Item Price"
        lRetCode = oDPM.Add ' Try to add the invoice to the database
        If lRetCode <> 0 Then
             oCompany.GetLastError(lErrCode, sErrMsg)
             MsgBox(lErrCode & " " & sErrMsg) ' Display error message
        Else
             MsgBox("Down Paymeny Invoice Added to DataBase", MsgBoxStyle.Information, "Invoice Added")
        End If
    Catch ex As Exception
        MsgBox(ex.Message)
    End Try
Regards
Arun

Error in joining Total A/R Down Payment Invoice with A/R Invoice.

Hi Everybody,
After creating a sales order for a customer, with the help of that sales order I had created the A/R Down Payment Invoice.
But while making A/R Invoice, when I browse for A/R Invoice down Payment It shows me the error,
No down payments found [Message 439-96]
I am using SBO 2007B PL-08
Please help me and reply ASAP

Hi Niraj,
You should create an incoming payment on the A/R Down payment first. then you can add it on the invoice.
Regards,
David

Cancel down payment Invoice and accounting document without lines item

Dear masters,
I have a problem with down payment invoice cancel. As you know when doing invoice down payment request, after release to accounting, the accounting doc will have special G/L indicator is F (noted item). And when I cancel this billing down payment and after release to accounting, the accounting doc of cancel invoice will not have any lines item. Now I want to have lines item for cancel down payment, how can I do that? I really appreciate your support!
Regards,
Nguyen Pham.

Dear Nguyen,
As i understand your process you created Downpayment Request from SD.
Then created Downpayment with reference to that request.
Then you generated Billing invoice and released to accounts.
After that you cleared the downpayment with the Billing document.
Now you want to cancel all this.
First cancel the downpayment by FBRA reset and reverse.
Then cancel the billing document.

Create AP Down Payment Invoice

Dear All,
I have a problem when I creating AP Down payment Invoice using SDK SAP2007. Error message like this
"Chosen BP is not customer ODP1.Cardcode line: 1, 'v181'"
When i check in SAP B1 2007, V181 is already set to VENDOR.
Here is the code :
Set oCompany = New SAPbobsCOM.Company
    With oCompany
        .Server = "T9\sql2005"
        .CompanyDB = "blive"
        .UserName = "n2301"
        .Password = "n7hfd8sd22"
        .DbServerType = dst_MSSQL2005
        .language = ln_English
        .UseTrusted = False
        .DbUserName = "sa"
        .DbPassword = "23dsasdh8d"
    ierr = oCompany.Connect()
        If ierr <> 0 Then
            Call oCompany.GetLastError(lErr, sErr)
            MsgBox sErr
        Else
            MsgBox "OK"
        End If
    End With
    Set oDP = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDownPayments)
    With oDP
        .CardCode = "V181"
        .NumAtCard = "Ticket 001"
        .DownPaymentPercentage = CDbl(100)
        .DocDate = Now
        .DocDueDate = Now
        .DownPaymentType = SAPbobsCOM.DownPaymentTypeEnum.dptInvoice
        .Lines.ItemCode = "C1"
        .Lines.Quantity = CDbl("10")
        .Lines.Price = CDbl("200")
        .Lines.VatGroup = "ZI"
    End With
        lErr = oDP.Add()
        If lErr <> 0 Then
            Call oCompany.GetLastError(lErr, sErr)
            MsgBox sErr
        Else
            MsgBox "OK"
        End If
Thanks before
rgrds,
Edited by: Lunatic on Jun 25, 2009 6:24 AM

HI
Use the BoObjectTypes.oPurchaseDownPayments for A/P Down payments (purchase).
oDownPayments object is a A/R Down payment for (sales)
Regards,
J.
Edited by: Janos Nagy on Jun 25, 2009 9:32 AM

A/P Down Payment Invoice error....

Hi all....
Please Help me...
I done all setup relevant to Vendor/Supplier for Business Partner Data...........
But whan I am creating A/PDown payment Invoice I got error...
In Vendor AP Down Payment Invoice I got error i.e "No Matching Records Found"
so what is the solutions.....
I am not getting error for my customer... when I am creating A/R Down Payment Invoice...
Please help me...
Regards
Umang

Hi... Nagesh ......
Dear Please... see here What I done....
First I done...
Admin--> set up --> Finance -> G/L Acct .. determination
Set control Account for Sales & Purchase.
2)
Then I assigned Control Account in Accounting Tab of Business Partner Records...
3) I created AP Down Payment Invoice for Vendor Based on Goods Receipt PO ....... After adding that ... Then I go for AP Invoice .....
Whn I click on DPM Tab It gives me error....."No Matching Records Found"
Ok .... If you have solution plz tell me....
Please ! do in your system .... and chk where I do mistake ?
Note : For Customer I am not getting error
Regards
Umang

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.

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 in Creating Time series objects in APO 5.0

Hi, We are implementing APO 5.0. I am trying to Create Time series objects for Planning Area 9ASNP05, but getting the following Run Time Error
We have used Support Package 10
Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
not caught in procedure "RSS_TEMPLATE_INSTANTIATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is: A PERFORM was used to call the routine "INSTANTIATE" of the program
"GP_MET_RSSG_HEADER_COMMENT".
This routine contains 15 formal parameters, but the current call
contains 16 actual parameters.
Any

Hi
I am getting exactly the same error, on SCM 5.0 SR2, running on Windows 2003 64 BIT & SQL 2000.
Conditions for error:
Using transaction:
/SAPAPO/MSDP_ADMIN
Select: Planning Object Structures
Short Dump occurs if you either:
1. Attempt to deactivate an active Planning Object Structure
2. Attempt to create a Characteristic Combination
Gives a runtime error shortdump PERFORM_TOO_MANY_PARAMETERS
Error analysis:
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
     not caught in
    procedure "RSS_TEMPLATE_INSTANTIATE" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    A PERFORM was used to call the routine "INSTANTIATE" of the program
     "GP_MET_RSSG_HEADER_COMMENT".
    This routine contains 15 formal parameters, but the current call
    contains 16 actual parameters.
Has anyone seen this before?
Did you find a solution Bhavesh ?
Thanks.

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

Error in profit center determination for settled vendor down payments

Hello All,
When we try to settle vendor down payments an error is detected for the profit center determination .
The settled down payment is found on the dummy profit center instead of the profit center of the original invoice. This means that the reporting of oustanding payables per profit center is wrong
When you only see the invoice and not the settled down payment which should reduce you outstanding debt (down payment already paid).
Can any one help in this matter
Regards
Arun

Hi,
Check the document splitting configuration. Advances to vendors recon.. account should be assigned as category 'Vendor 'special gl transaction''.
Check the document type 'KA' transaction as '0300'... or unspecified posting.
Thanks,
padmaja N

Posting down payment document through F-48 without down payment request

Dear All:
I am facing a serious control issue in vendor down payment. SAP transcation code F-48 (vendor down payment) can post a payment document without even any Down Payment Request.
Is there some configuration / notes missing in my SAP system?? If this is standard then how come one can post payment wihout having any invoice?
Regards,
Shabbir

Thank you all for your replies.
I got the process flow, however, how can I put restriction on F-48 so that the user CANNOT execute the transaction without payment request? Is it possible? Just like F-58, F-53, where open items are mandatory.
My user has executed F-48 and after completed the processing send the check to the vendor but the down payment request created by Accounts Payable guy, remained there. Thats why I am asking this question.
Regards,
Shabbir

How to create Down Payment Invoice without Small Business One

Greetings,
I have a requirement to create an AR Invoice to solicit a Down Payment (previous to any Goods Issue). I see from other postings that this can be done using Small Business One, but we only have the SAP ERP 5.0 implemented. The customer has agreed to Down Payments, but will only submit payment after receiving an invoice.
Is this functionality available in SAP 5.0?
Thanks,
Tony-

Closed due to non-response.

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

Similar Messages

Maybe you are looking for