3 Replies Latest reply: Dec 26, 2012 10:02 AM by Dhanaji Mhetre RSS

CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1

Frank Pedro
Currently Being Moderated

hi ia m getting this error during the upgrade .i did checked in sm12 for any failed updates but there arent any .so i think there should be a table that i need to alter.should this be done in se16 ? and i think the table name is TRAN.LBWG any ideas.

 

CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex

 

  Long text:

 

    Cause

      Changing the extract structure &V#& for application &V#& is not

      permitted, because the restructure table &V#& for the extractor still

      contains data in &V#&.

      You cannot change the structure in this status, because when you load

      an InfoPackage from BW, this leads to errors.

 

    What to do

      <DS:TRAN.LBWG>Delete</> the entries for all restructure tables for

      application &V#&.

 

 

 

1 ETH010XRSVBCHCK: Check of open update requests

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex

t" ""MC02M_0HDRSETUP""100"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex

t" ""MC02M_0ITMSETUP""100"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long tex

t" ""MC02M_0SCLSETUP""100"

A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex

t" ""MC03BF0SETUP""100"

A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex

t" ""MC03BX0SETUP""100"

A2EEMCEX 141 Struct. appl. "03" cannot be changed due to setup table -> Long tex

t" ""MC03UM0SETUP""100"

A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex

t" ""MC11VA0HDRSETUP""100"

A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex

t" ""MC11VA0ITMSETUP""100"

A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex

t" ""MC11VA0STHSETUP""100"

A2EEMCEX 141 Struct. appl. "11" cannot be changed due to setup table -> Long tex

t" ""MC11V_0SSLSETUP""100"

A2EEMCEX 141 Struct. appl. "13" cannot be changed due to setup table -> Long tex

t" ""MC13VD0ITMSETUP""100"

4 EPU202XEND OF SECTION BEING ANALYZED

  • Re: CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1
    Markus Doehr
    Currently Being Moderated

    Do as advised in the text:

     

    <quote>

    What to do

    <DS:TRAN.LBWG>Delete<> the entries for all restructure tables for

    application &V#&.

    </quote>

     

    Start transaction LBWG and empty the BW delta queues. Check with your BW developer, that the data isn't needed any more.

     

     

    --

    Markus

  • Re: CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.MX1
    kalyan konedala
    Currently Being Moderated

    1. Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.

     

    2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014.

     

    3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.

     

    Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.

Actions