Error while doing a mass change in info record

Dera Experts ,
We are getting the following error while settin g the complete deletion indicator for a purchase info record through t code MEMASSIN.
Communication block for info record incompletely transferred
Message no. 06327
Diagnosis
Internal error.
Procedure
Please inform your programming department or system administrator.
We are able to mark the deletion indicator maually through ME12 T code .
Please suggest what coiuld be wrong ?
Regards
Anis

Hi,
I have searched and could not find any information related this error in the transaction you use. I suggest that you open a ticket at SAP, so that an expert can have a look into your system.
Best Regards,
Arminda Jack

Similar Messages

  • Error in mass change for info records -MEMASSIN

    Hello Friends,
    We want to mass change the info records. We want to set the "Unlimited del" indicator to all the Info records which is not there currently.
    When we tried to do the same, we came across an error saying  -
    "5300177458 : Enter Purch. Group (5300177458)" ....message type ME083.
    but purch grp is maintained in all the Info records.
    Can anybody help us to fix this issue ?
    Thanks in Advance,
    Vidyadhar.

    Hi all,
    Thanks for your inputs.
    1st thing - pur grp is maintained in customizing also. ..not deleted in customizing.
    2nd thing - in MASS trans selection, I selected pur org, plant, and unlimited del options....still its giving me the same error.
    any other solution pls ?

  • Receiver JDBC: Error while doing the Deleting and Inserting new records

    Hi All,
              I am doing Idoc to JDBC scenario. In this I am collecting & bundling different type of Idocs and then sending to the JDBC receiver. My requirement is to delete the existing records in the database and insert the new records. I have configures as mentioned in the link
    Re: Combining DELETE and INSERT statements in JDBC receiver
    In the above link its shows for single mapping. In my scenario I am using multi mapping for collecting idocs in BPM. If I configured for normal mapping then it is working fine(Deleting existing records and Inserting new record). Whenever I am using multi mapping then I am getting following error in the receiver JDBC communication channel u201CError while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)u201D . Can you please tell me what might be the problem.
    Thanks & Regards,
    T.Purushotham

    Hi !
    check this out:
    JDBC - No 'action' attribute found in XML document - error
    JDBC receiver adapter: No 'action' attribute found in XML document
    It appears that the inbound payload (the one that is going from XI to the JDBC adapter) does not have the requiered tag to specify which SQL action to execute in the receiver system. Maybe the multimapping is not creating the desired output message format.
    Regards,
    Matias.

  • Error While Doing GR "Check table YMSEG:"

    I am getting following error while doing GR for sales set  article 303387.
    Check table YMSEG: entry 303384 0001  does not exist
    Sales set header 303387
    sales set Component 303384 & 303386.
    can't find any issue with the article (material) setup

    YMSEG is a standard internal table used in import and export of function modules.
    if you search SAP notes on YMSEG then you get about 230 hits.
    Unfortunately the info given is by far not enough to tell you the reason for this error.
    The number from the error explains just that it is one of the sales set Components
    But you need to describe the process and what changes you eventually did compared to standard process. Only then we might be able to help you further.

  • Error while doing ABGL Asset Credit Memo

    Hi Friends,
    I am getting the below error while doing Asset Credit Memo in ABGL. Please help me in fix this issue.
    Balance for transaction type group 10 negative for the area 01
    Note:In Asset Explorer Fiscal year start Asset value is 98,425.45 and Change is 4768.19. So total Asset value as of now is 1,03,193.64.
    Now we are trying to do ABGL with 12,790.23 value (Transaction type is 105). System is giving the above highlighted error.
    If we give the amount 4768.19 in ABGL transaction, system is not giving any error. If we give more that that system is giving error.
    Why system is giving error even the asset has balance of 1,03,193.64? Please help me on this..
    Thanks
    Sunil

    Hi,
    If the asset has been capitalized during earlier years, use ABGF to post credit memo.  ABGL is meant for assets capitalized during the year.
    Best Regards,
    Madhu

  • Dump error while creating or double click the info package

    Hello experts,
    I have actived infocube 0FIAR_C03 in BI content. Ago, The creation infopackage have been deleted in the past , today, I  created a infopackage, while I update mode selected u2018initialize delta processu2019, then click save button , the system prompt u2018Deltas already loaded for request  REQU_D64R47LDUSZHY9CBIB86WMLFJ init.selection; no 2. initu2019, I canoti save it for my setting. Why is this?
    Then I have search cause in SDN,  and I have reference OSS Note 852443 to do .
    Note 852443 have mention some table: RSSELDONE、RSSDLINIT、RSSDLINITSEL、ROOSPRMSC、ROOSPRMSF.
    I have to delete that request of record using se16 in these tables: RSSELDONE、RSSDLINIT、RSSDLINITSEL.
    in my BI 7.0 system,   ROOSPRMSC、ROOSPRMSF is no any data.
    I was no found delta queue in RSA7.
    Now . Dump error while creating or double click the info package,  how can I change this?
    Please let me know the solution.
    Thanks for your help.
    Best Regards
    Steve

    Here are some links  which deals with same issue.
    Re: Dump In Infopackage
    Re: Getting into Short dump at the time of selecting InfoPackage to execute for
    Short dump while performing init in infopackage
    Re: Infopackage going into short dump
    Thanks.

  • Error while doing F-90 Asset Acquisation

    Hi,
    I am getting the below error while doing F-90 Asset Acquisation scenario. Please help me to fix this issue.
    Tax code V1 country IN does not exist in procedure TAXINN
    Message no. FF713
    Diagnosis
    You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
    System Response
    Procedure
    Check and, if necessary, correct the entry.
    Procedure for System Administration
    If it is not an input error, check and possibly change the system settings.
    To do this, choose Maintain entries (F5).
    Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
    Create a new tax code if necessary.
    Caution:
    Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
    Thanks
    KB

    Hi,
    you need to maintain Tax Code A0 & V0 in t.code OBCL t.code.
    and also ensure to check whether you have created tax code V1 or not in FTXP t.code. If not, create V1 tax code and assign GL on that in the right Transaction event keys in OB40.
    Try.... if not working let me know....
    Regards,
    MOhan.

  • Error while doing AIAB Settlement

    Hi I am facing the below error while doing AIAB during AUC settlement. Please do the needful.
    Data for determination of capitalization not managed in area 01
    Message no. AW507
    Diagnosis
    You have chosen a depreciation area, which does not carry the depreciation data from table COEPBR.
    Procedure
    Choose a different depreciation area.
    Thanks
    KC

    Hi,
    This message could be helpful:
    Error AW507
    Please check the field T082AVIEWB-AUTHORITY. If it is not on 2 this is the reason.
    In this case, you can change the value in T093-VIEW1 using the coding as per SAP note 29706 which you have already discovered. There will be no risk involved in changing this value.
    regards Bernhard

  • Error while doing Challan updation

    Dear all,
       Iam getting error while doing Challan updation, system shows an error saying "No line Item exist for Challan updation" whereas iam having all the data but the system is not picking.
    pls help on this
    will get a good points for solving this

    I understood ur problem, u r running the J1INCHLN when u r running this program . Program chks both the Table BSEG & WITH_ITEM they 2 field from BSEG-BUZEI & WITH_ITEM -J_1IBUZEI . if this 2 line item is not matching then system will show the same error which u have mentioned.
    Whether this has occured first time or rarely it occurs, if first then just update the table WITH_ITEM for the field J_1IBUZEI with respect to BSEG-BUZEI for the TDS line item only. Make the changes with help of ur Internal consultant. write an update program.

  • Error while doing outbound delivery against Purchase Order

    hello
    i m getting error while doing Outbound delivery for purchase order as follows
    EKPO-SOBKZ=E; EKPO-UMSOK=_; EKPO-KZBWS<>_ EKPO-KZVBR<>E (Note 305582) not supported (check your entry)
    Message no. M7146, i m not getting wht will be the reason,
    Regards
    NISHJ

    Please go through the note - 305582. It is clearly given the direction.
    Symptom
    You try to post a goods movement for a stock transport order from the unrestricted-use stock into the sales order stock or project stock.
    During the goods issue, the system displays error message M7146 with a text along the lines of "EKPO-SOBKZ=E; EKPO-KZVBR<>E; ... not supported".
    Cause and prerequisites
    In the goods issue for the stock transport order, the system may have to create a stock in transit which is deconstructed during the goods receipt. If the withdrawal takes place from the special stock, it is clear which is the receiving stock.
    However, if the withdrawal is carried out from the unrestricted-use stock ("Collective requirements", controlled by the dependent requirements indicator MARC-SBDKZ in the material master of the issuing plant), this results in the design problem that the control tables of the goods movement do not have any key field for the receiving stock. Therefore, the control for the receiving stock is controlled via the consumption indicator in the account assignment category of the purchase order. The consumption indicator therefore requires a specific default setting (you may have assumed you could change the design of these control tables, however this is not possible).
    Using an inappropriate consumption indicator then causes for the goods issue an incorrect or no stock in transit to be created so that the goods receipt fails.
    Solution
    Implement the program change in accordance with the correction instructions.
    Afterwards implement Note 413908 immediately if this is relevant for your release.

  • Error while doing the repository export

    hi,
    I am getting error while doing the export repository,Message: GEN-13, Additional Message: Dictionary is not available on this database, can anyone help me how to resolve this issue.
    thanks,
    Sundar M

    Hi Sundar,
    Please provide the export repository command, what you used and the log file to review.
    The error "Dictionary is not available on this database" will pop up when Siebel Repository is not present in DB.
    For export process you have to give repository name as "Siebel Repository" and it will export schema in to *.dat file.
    NOTE: Do not change Siebel Repository name for export process.
    Thanks,
    Shilpi

  • Mass upload for info records when price gets changes

    Dear All,
    How to do Mass upload for info records when price gets change.
    Regards,
    Bhargav

    Hi Bhargav,
    Please upload the present price (Map) by  LSMW . When you are doing the transactions  then automatically by selecting option info update price will be updated the  info record in Order Price history
    Regards
    M B Raju

  • Termination error while doing me31k

    HI Experts,
    This is the sincere apology for the previous thread which was in capital letter subject" termination error while doing me31k 
    Posted: Mar 6, 2012 2:56 AM          
    HI while performing transaction ME31K I'm getting follow error
    Runtime error: DYNPRO_NOT_FOUND
    What Happened?
    Error in the ABAP application Program
    The current ABAp program "SAPLXM06" had to be terminated because it has come across a statement that unfortunately canont be executed.
    Error Analysis
    The system attempted to use dynpro 0201 in program "SAPLXM06".
    This dynpro does not exist.
    Trigger Location of Run TIme Error
    Program: SAPLXM06
    Include: MM06E00C_CUSTSCR1_HEAD_SET_DAT
    ROW: 10
    There is a Edit button, that allows you to change the subject
    Edited by: Jürgen L. on Mar 6, 2012 8:41 AM

    Dear MM user,
    Follow the documentation of this enhancement (see transaction SMOD):
    Within the documentation of enhancement MM06E005, via TA SMOD, it specifically states that if you use the enhancement you must generate six listed dynpros (screens), even if you are not using them.
    So you may goto transaction CMOD and enhance the same.
    For example, the dynpro area should be like the following:
    Calling screen No. Area Called screen No. ShortTxt
    SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101 Subscreen: PO header
    SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
    SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201 Subscreen: agreement
    Regards,
    ian Wong Loke Foong

  • Update termination error while doing PGR

    Hi,
    I got this error while doing PGR, please do suggest the dolution.
    Update was terminated
    System ID....   DPT
    Client.......   900
    User.....   SDUSER
    Transaction..   VL02N
    Update key...   4BEAA8A2A6DA0609E1000000AC1107A7
    Generated....   12.05.2010, 18:38:55
    Completed....   12.05.2010, 18:38:56
    Error Info...   Update program: I/O error Error; function Update, RC= 4, key
    Thanks,
    Swapnil

    Hi Lakshmipathi,
    I have checked the analysis in SM13, got the folllowing,
    Function Module        SERIALNUMBER_POST
    Status                        Update was terminated
    Report                        LIEP1U01
    Row                            159
    Error details   Class:     IS         Number:    229
    Update program: I/O error Error; function Update, RC= 4, key

  • Error while doing "Visulaize Plan"

    Hi,
    Before i did Visualize plan many times without any problem.Now I am getting error while doing so.
    I was able to run "Explain Plan" successfully.
    I am on HANA revision 60.
    I saved above error log and the log information is given below:
    I can identify invalid XML tag <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved> but how to fix this issue?
    I gone through various blogs related to Visulaization Plan but not found related to this issue.
    <Plan xmlns="http://www.sap.com/ndb/planviz" ID="ID_0" Type="Estimated">
    <SQL><![CDATA[SELECT KOKRS, BELNR, PERIO, SUM(MEGBTR)
    FROM "_SYS_BIC"."raj/AN_VIZ"
    GROUP BY KOKRS, BELNR, PERIO]]></SQL>
    <CompileTime>
      <Start Unit="us">1401281467643661</Start>
      <End Unit="us">1401281467658329</End>
    </CompileTime>
    <RootRelation ID="ID_0" TypeName="PROJECT" Status="Finished">
      <Name>Project</Name>
      <ExecutionType>Row Search</ExecutionType>
      <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">2.12902e+06</Exclusive>
       <Inclusive Unit="us">2.64021e+06</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <Details><![CDATA[{"Projected Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)","Project column0":"NString(4, 0)  __trex_field_NVarchar3__() ....... [3]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [0]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [1]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 0 ....... [2]:LOAD:<4/5 (4B)>:","Project column1":"NString(10, 0)  __trex_field_NVarchar3__() ....... [8]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [5]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [6]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 1 ....... [7]:LOAD:<4/5 (4B)>:","Project column2":"NString(3, 0)  __trex_field_NVarchar3__() ....... [13]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [10]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [11]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 2 ....... [12]:LOAD:<4/5 (4B)>:","Project column3":"Decimal(18, 3)  __typecast__() ....... [23]:076:<10/12 (16B)>:
      /1/ Fixed16(18, 3)  __trex_field_Fixed16__() ....... [19]:043:<6/8 (16B)>: 
         /1/ void*  \"__rids__\" ....... [15]:NOP:<0/1 (8B)>:
         /2/ int32_t(10, 0) const := 0 ....... [16]:LOAD:<3/4 (4B)>:
         /3/ int32_t(10, 0) const := 3 ....... [17]:LOAD:<4/5 (4B)>:
         /4/ int32_t(10, 0) const := 3 ....... [18]:LOAD:<5/6 (4B)>: 
      /2/ int32_t(10, 0) const := 18 ....... [21]:LOAD:<8/9 (4B)>:
      /3/ int32_t(10, 0) const := 3 ....... [22]:LOAD:<9/10 (4B)>:"}]]></Details>
      <Child ID="ID_8" >
      </Child>
    </RootRelation>
    <Relation ID="ID_8" TypeName="TREX_SEARCH" Status="Finished">
      <Name>Column Search</Name>
      <ExecutionType>Column Search</ExecutionType>
      <Summary><![CDATA[Aggregation on a single table]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">511194</Exclusive>
       <Inclusive Unit="us">511194</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved>
      <LogicalPlan ID="ID_11" Type="Estimated">
       <RootRelation ID="ID_11" TypeName="PROJECT" Status="Finished">
        <Name>Project</Name>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Child ID="ID_12" >
        </Child>
       </RootRelation>
       <Relation ID="ID_12" TypeName="GROUP_BY" Status="Finished">
        <Name>Aggregation</Name>
        <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO\nSUM(raj/AN_VIZ.MEGBTR)]]></Summary>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Details><![CDATA[{"Grouping Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO","Aggregation Cols":"SUM(raj/AN_VIZ.MEGBTR)"}]]></Details>
        <Child ID="ID_13" >
        </Child>
       </Relation>
       <Relation ID="ID_13" TypeName="TABLE" Status="Finished">
        <Name>Column View</Name>
        <Schema><![CDATA[_SYS_BIC]]></Schema>
        <ObjectName><![CDATA[raj/AN_VIZ]]></ObjectName>
        <Location>hanasp7:30003</Location>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>682404</EstimatedOutputCardinality>
       </Relation>
      </LogicalPlan>
    </Relation>
    </Plan>
    Regards
    Raj

    Hi,
    To solve this you must update your studio. In lower studio versions (PlanViz) does not allow "unknown" XML tags sent by higher version servers. A fix for this issue was made so that PlanViz parser can simply skip unknown tags.
    Please go to version 74, if possible.
    Regards,
    Michael

Maybe you are looking for