Error when scheduling the infopackage for loading Master data attributes

Hi,
Iam getting the following error message when scheduling this Master data Attributes ZIP_0PLANT_ATTR_FULL..( Flexible update of Master data info objects)..
In Data load monitor error i got this following error message.
Error message when processing in the Business Warehouse
Diagnosis
An error occurred in the SAP BW when processing the data. The error is documented in an error message.
System response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Update rules
Thanks

HI,
A caller 01, 02 or equal to or greater than 20 contains an error meesage This is an Idoc error. Please check the Idocs :
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
Also see if there is any 'sysfail' for any datapacket in SM37.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
5) Check in SM58 and BD87 for pending tRFCs and IDOCS.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the data tables.
SM21 - System log can also be helpful.
Thanks,....
Shambhu

Similar Messages

  • DTP error: Lock NOT set for: Loading master data attributes

    Hi,
    I have a custom datasource from ECC which loads into 0CUST_SALES.  I'm using DTP & transformation which has worked for loading data in the past for this infoobject.  The infopackage loads with a green status but when i try to load data, the DTP fails with an error message at "Updating attributes for InfoObject 0CUST_SALES Processing Terminated" & the job log says: "Lock NOT set for: Loading master data attributes".  I've tried reactivating everything but it didn't help. Does anyone know what this error means? We're on SP7.   Thanks in advance!

    Hello Catherine
    I have had this problem in the past (3.0B) --> the reason is that our system was too slow and could not crunch the data fast enough, therefore packets where loacking each other.
    The fix: load the data into the PSA only, and then send it in background from the PSA to the info object. By doing this, only a background process will run, therefore locks cannot happen.
    Fix#2: by a faster server (by faster, I mean more CPU power)
    Now, maybe you have another issue with NW2004s, this was only my 2 cents quick thought
    Good luck!
    Ioan

  • What are the steps for loading master data

    Hello
    what are the steps for loading master data? i want to learn about loading all master data and the steps to choose the best way to load the data.
    if anyone has documents please send me the documents i will be really greatful
    [email protected] thanks everyone
    Evion

    Hi Heng,
    Download the data into a CSV file.
    Write a program using GUI_UPLOAD to upload the CSV file and insert records.Chk the below link for example
    http://www.sap-img.com/abap/vendor-master-upload-program.htm
    Reward Points for the useful solutions.
    Regards,
    Harini.S

  • Lock NOT set for: Loading master data attributes error

    Hi experts,
    We were encountering this error before when trying to load master data.  When we checked the system we could not find any locks at the time, and activation or kicking off the attribute change run failed again.  We finally solved the problem running FM RSDDS_AGGR_MOD_CLOSE which sets the close flag to 'X' in table RSDDAGGRMODSTATE.  I have read that it is possible this lock error happens when two change runs happen at the same time.
    My question are:
    1. is it possible to find out what process exactly "caused" the lock? the table RSDDAGGRMODSTATE does not have a reference to any object or job. I am curious as we are trying to find ways to avoid this in the future...
    2. in our case, when we could not find any locks, is running this fm the only work around? is this a best practice?
    mark
    Message was edited by:
            Mark Siongco
    Message was edited by:
            Mark Siongco

    Hello Catherine
    I have had this problem in the past (3.0B) --> the reason is that our system was too slow and could not crunch the data fast enough, therefore packets where loacking each other.
    The fix: load the data into the PSA only, and then send it in background from the PSA to the info object. By doing this, only a background process will run, therefore locks cannot happen.
    Fix#2: by a faster server (by faster, I mean more CPU power)
    Now, maybe you have another issue with NW2004s, this was only my 2 cents quick thought
    Good luck!
    Ioan

  • Process chain for loading master data attributes

    Dear Experts,
    Can any one explain the steps needed to load master data into info object through process chain.
    Thanks in advance
    Santhosh
    Please search the forum
    Edited by: Pravender on Jun 8, 2010 3:06 PM

    in bi7 this would be:
    start
    infopackage
    dtp
    attribute change run
    M.

  • Lock NOT set for: Loading master data attributes

    Error when running Process chain on a load pls can you advise?
    Thanks

    Hi,
    Probably some other job is running for the same tables,or activation change run is happening.
    Check your monitor to see what other jobs are running or check in SM37. Wait till those jobs finish and then try again.
    You can also use tcode SM12 to delete any lock entries as well.
    Cheers,
    Kedar

  • Where to set lock while loading master data attributes

    Hello Experts,
    I have two different datasources from ECC which loads into 0CUST_SALES attributes. I'm using two different DTP & transformation which are loading data in the this infoobject attributes.
    When i try to load data, the DTP fails with an error message at "Updating attributes for InfoObject 0CUST_SALES Processing Terminated" & the job log says: "Lock NOT set for: Loading master data attributes".
    Here what exactly  LOCK means?
    Thanks in advance.
    Zakir Khan.

    Hi,
    The lock means that some program is updating the master data (a table) and at the same time other program can not update that same master data. When the first program completes the updation it will release the lock so that the other program can update this.
    In your case you and schedule the DTP one after another.
    Thanks

  • Wht is the relevant for BW Flag option in the infopackage for loading Hier

    Hello Gurus,
    Whta is the relevant for BW Flag option in the infopackage for loading Hierarchies? What happens when you turn this on?
    Thanks
    Simmi

    As the hierarchies are stored in combination with the OLTP system, when you tend to load from a flat file, the system doesnt allow you to maintain this feature, as this hierarchy would be relevant to BI.
    Diagnosis
    The relevant hierarchies in BI are stored according to the combination DataSource/source system.
    If you want to change the selection of BI-relevant hierarchies, this change is effective for all InfoPackages that have been created for the same DataSource/source system combination.
    Procedure
    Check all other InfoPackages for DataSource 0COSTCENTER_0101_HIER and source system PRDCLT100 to see whether the change executed is also appropriate for these InfoPackages.
    Procedure for System Administration
    If you want to load a hierarchy in a different InfoPackage (which will be marked as non BI-relevant as a result of your changes) the selections made for this InfoPackage will be lost and The InfoPackage can no longer load.
    Errors will occur when you start the InfoPackages. The monitor produces an error message to say that a valid hierarchy selection has to be made.

  • Error message "Error when scheduling the query(JOB_CLOSE)".

    Hi all,
    While using query extractor (rscrm_bapi) I am getting error message "Error when scheduling the query(JOB_CLOSE)".
    Could you please find what this error is?
    Thanks,
    Uday.

    Hi Uday,
    This problem can occur if you changed the query definition.
    In this case the query definition would be inconsistent with the existing extract structure.
    Certain Meta information is maintained with each extract defined using the RSCRM_BAPI. If the definition of the query is changed and you need to use the same extract table then you need to delete the extract using the report RSCRMBW_DEL_ALL_EXTRACTS selecting the extract you want
    to delete.
    After this you could use the same table name for any further extract that you need to create.
    One caution is that the extract table should not be deleted through any other transaction before you run the report.
    Rgds,
    Colum

  • Error while loading master data attribute

    Hi Guru's
    I am getting below mention error while loading master  data attribute.
    0MANU_MATNR : Data record 1035 ('000000000000229058 '): Version 'BDM755s ' is not valid
    Please sugggest how to resolve ?
    Regards
    Karan

    Hi,
    I think there is problem with "0MANU_MATNR" Data, check the records 1033 to 1036 and find the differnce between 1035 record and other records, some values is giving problem so by looking at other reocrds i.e 1033,1034,1036. Check in PSA in Monitor. 
    Note: If any problem with Upper/Lowe case then use TOUPPER in Transfer Rules
    If need use Conversion exits in transfer rules.
    ALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT         = 0MANU_MATNR
    IMPORTING
       OUTPUT        =   Result .
    or
    ALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
      EXPORTING
        INPUT         = 0MANU_MATNR
    IMPORTING
       OUTPUT        =   Result .
    Thanks
    Reddy
    Edited by: Surendra Reddy on Mar 3, 2009 11:46 AM

  • Turning off the text for a master data object

    What happens if we turn off the texts for a master data object?  (In RSA1, under info objects - double click on info object and go to Master data/texts tab and untick the 'with texts' box).  Are there any risks in doing this?  Has anyone performed this and run into any issues?  Thanks

    Hi,
    There are no issues in turning off the texts, but if its an object that requires description in the report, say material, plant etc, then you won't have that available as the texts are disabled and not loaded.
    Cheers,
    Kedar

  • Loading master data attributes

    Hi.
    When I am loading master data attributes, DTP process takes long time (approximately 30 minute) .
    Although records count is just 193.
    What may be a reason of this?
    Information about system:
    Software component   Release    Level
    SAP_ABA                      700          0023  
    SAP_BASIS                   700          0023  
    SAP_BW                        700          0025

    Hi...
    Check the Package size in the DTP......try to increase or decrease it.....if it makes any differerence......
    Secondly....in the DTP in the tab "Update" select the option " Valid records update, No reporting"....then the "Semantic Groups" in the tab " Extraction" will work.....it will improve the performance....
    Regards,
    Debjani........

  • Error when creating a bdc for asset master upload

    I am getting a warning message (AA186), when changing the depreciation start date to capitalization date. It says,
    "Different Order Dep. start date in depreciation area 01. Check"
    This error is a problem in creating the BDC for asset master upload. We have only one depreciaton area 01 (book dep).
    Please help.

    This is normal message you get when you try to change depn start date. I think this should not be a problem for BDC posting. This message can always be bypassed.

  • Error Caller 70" is missing while loading master data

    Hi All,
    I am facing a Problem while loading master data getting error like "Error Caller 70" is missing" ,there are 4 data packages and in that except one all other with status green .1  data pakage is showing with red color, its update till only PSA .
    Please help me out to solving this issue .
    Thanks in Advance
    Sandhya

    Hi,
    check the below links
    caller 70
    Re: Caller 70 error
    caller 70
    Hope this helps

  • Best Practices for Loading Master Data via a Process Chain

    Currently, we load attributes, text, and hierarchies before loading the transactional data.  We have one meta chain.  To load the master data it is taking more than 2 hours.  Most of the master data is full loads.  We've noticed that a lot of the master data, especially text, has not changed or changed very little since we implemented 18 months ago.  Is there a precedence or best practice to follow such as do we remove these processes from the chain?  If so, how often should it be run?  We would really like to reduce the amount of the master data loading time.  Is there any documentation that I can refer to?  What are other organizations doing to reduce the amount of time to load master data?
    Thanks!
    Debby

    Hi Debby,
    I assume you're loading Master Data from a BI system? The forum here are related to SAP NetWeaver MDM, so maybe you should ask this question in a BI forum?
    Nevertheless, if your data isn't changed this much, maybe you could use a delta mechanism for extraction? This would send only the changed records and not all the unchanged all the time. But this depends on your master data and of course on your extractors.
    Cheers
    Michael

Maybe you are looking for