PSA Status & deletion

Hi,
I am working on BW 7.3 SP5.
I have a specific datasource which loads a flat file (FULL).
This datasource then loads 2 write-optimized DSOs (DELTA) via DTP.
After loading the PSA, and then both DSOs, I check my datasource -> manage : The demand is still with the status 'request not updated to any target using the delta' even if all targets are updated.
I can not delete this PSA request within a process chain with option "Only successfully booked requests"...
On the other hand, I have the same kind of flow but for a masterdata and only on target, and when I update the masterdata (PSA->MD via DTP) the status is changed to request updated in data target' which is great. This PSA can be delete via a process chain with option "Only successfully booked requests"
Thanks for any help.

Hi, I have similar problems, but already selected delete successfull and not updated requests from PSA, to check if it is then deleting , but no. Therefore the above note won't help (at least not to solve the issue in full).
It's a 7.01SP10 system, the PSA data (data from an R/3 datasource, no datamart) is updated via DTP to a write optim. DSO. The daily amount of datasets is huge (over 20Mio) therefore deletion of whole PSA is desired.
The wrong display of systemstatus showed during Delta update to DSO as well: the entries have been picked up again and again, because of the wrong status! This has been solved by the DTP-setting "Get all data only once".
Does anyone have an idea why this PSA-deletion is not working? Even if both checkboxes are checked?
I read that the position of the process type may have influence in it's proper performance? The PSA-deletion is the final step in chain, after a cube index creation. Any issues with that?
Thanks for any help!

Similar Messages

  • PO with status "Deleted" in SRM and status "Awaiting Approval" in BW

    Hi,
    Report Purchase Order status ( 0BBP_PO_Q007) on ODS 0BBP_PO shows status "Awaiting Approval" for Purchase Orders that have status "Deleted" in the SRM source system.
    Any idea about an appropriate OSS note or other work around solution?
    Thanks in advance for your replies.

    1) The PO data can be extracted from SRM or R/3 . But the advantage of extracting data from R/3 is that you have lot many other data while compared to SRM system . In case u are having SRM and Sap R/3 or ECC as your backend system , it is always better to  extract PO data from R/3 or ECC. In case your backend system is going to be other than SAP system , probably we can think of extracting data from SRM.
    2) GR and invoice data always have to be pulled from R/3 system
    3) Shopping cat details exist only in SRM and the details has to be extracted only from SRM .
    Suggest to extract 1) shopping cart from SRM  2) PO,GR and Invoice from SAP R/3 or ECC.
    Hope above clarifies your questions
    Regards
    Mani
    Message was edited by:
            Manikanda Ilango S.
    Message was edited by:
            Manikanda Ilango S.

  • PSA Data Deletion in SAP BW running on Oracle

    Hi,
      I deleted 2 failed requests (10000000 Records) from PSA Tables because of the disk space issue for our BW System.
    RSA1—PSA –DELETE PSA DATA –
    The requests are deleted from the PSA, In BW in can see that there not requests in that particular PSA.
    But Basis/Database team raised an issue that the data has been added to the Database…
    What is this mean and how can I proceed with this
    Thanks

    This is probably not an Oracle issue.
    refer to your other topic at PSA Data Deletion in SAP BW running on Oracle

  • PSA data deletions

    There are scheduled loads to a data target via a meta chain.
    I want to include deletion of PSA data as part of the scheduled loads.  Just wanted to check the following:
    1. There are Process chain process to delete PSA tables
    2. It is better to collectively delete the PSA tables
    3. Should I include the PSA deletion as the last step for each individual process chain or as a new process in the meta chain
    Thanks

    Hi,
    If you put all PSA tables deletion in one process, then system will delete one by one PSA & process will take more time.
    So group PSA tables like Master data PSA, transaction data PSA, PSA in between source system & BI , PSA tables with in BI etc....
    Then do analysis on data volume on each PSA. If any table will recieve more volume, then better to keep it alone in single process type where as smaller ones can be grouped. Again it depends on your server work processors available, regular PC design & data volume.
    Hope you might get an direction.
    Regards,
    Arun Thangaraj.

  • PSA no deletion SAP BW on HANA Rev 61

    Hi,
    PSAs are not getting deleted for some of the datasources due to error loads and multiple runs. System is SAP BW on HANA Rev 61.
    The previous job failure was not corrected  and the subsequent job was started based on the process chain schedule and that one as well failed. This has happened 2 times. Now the PSA table says it has duplicate entries and it is not dropping when we try to delete manually or through program.
    Whenever we try to delete the PSA, the SAPLSDB2 program runs and is stuck in SM51. St22 error log says
    SQL error "-10807" while accessing table "/BIC/B0000674001".
    65        l_s_data TYPE /BIC/B0000674001.
    66 *---1363526 Increasing the security to check the number of records inserted in PSA table
    67 *---is actually equal to data in l_t_data or p_t_data.
    68  DATA: l_rollback TYPE rs_bool,
    69        l_count TYPE i.
    70  l_rollback = RS_C_FALSE.
    71 *---1363526
    72
    73  APPEND LINES OF p_t_data TO l_t_data.
    74
    75  CLEAR: l_s_data.
    76  l_s_data-partno = p_partno.
    77
    78  MODIFY        l_t_data
    79  FROM          l_s_data
    80  TRANSPORTING  partno
    81  WHERE        request = p_requestid.
    82
    83
    >>>  INSERT      /BIC/B0000674001
    85  FROM TABLE  l_t_data
    86  ACCEPTING DUPLICATE KEYS.
    87 *---1363526
    88  DESCRIBE TABLE l_t_data LINES l_count.
    89  IF l_count NE sy-dbcnt.
    90    l_rollback = RS_C_TRUE.
    91  ENDIF.
    92 *---1363526
    Category              ABAP Server Resource Shortage
    Runtime Errors        DBIF_RSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          10.08.2014 11:28:01
    |Short text                                                                                        |
    |    SQL error "-10807" while accessing table "/BIC/B0000674001".                                  |
    |What happened?                                                                                    |
    |    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
    |What can you do?                                                                                  |
    |    Please make a note of the actions and input which caused the error.                          |
    |    -                                                                                            |
    |                                                                                                  |
    |    To resolve the problem, contact your                                                          |
    |    SAP system administrator.                                                                    |
    |                                                                                                  |
    |    Using transaction ST22 for ABAP dump analysis you can see and                                |
    |    administrate termination messages and retain them for longer periods.                        |
    |    Please make a note of the actions and input which caused the error.                          |
    |    -                                                                                            |
    |                                                                                                  |
    |    To resolve the problem, contact your                                                          |
    |    SAP system administrator.                                                                    |
    |                                                                                                  |
    |    Using transaction ST22 for ABAP dump analysis you can see and                                |
    |    administrate termination messages and retain them for longer periods.                        |
    |Error analysis                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                |
    |    in                                                                                          |
    |    procedure "INSERT_ODS" "(FORM)", 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:                                                              |
    |    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
    |How to correct the error                                                                          |
    |    Internal call code.........: "[RSQL/INSR//BIC/B0000674001 ]"                                  |
    |    Please check the entries in the system log (Transaction SM21).                                |
    |    You may able to find an interim solution to the problem                                      |
    |    in the SAP note system. If you have access to the note system yourself,                      |
    |    please use the following search criteria:                                                    |
    |                                                                                                  |
    |        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
    |        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
    |        "INSERT_ODS"                                                                              |
    |    If you cannot solve the problem yourself, please send the                                    |
    |    following documents to SAP:                                                                  |
    |                                                                                                  |
    |    1. A hard copy print describing the problem (short dump).                                    |
    |      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
    |      on the current screen.                                                                    |
    |                                                                                                  |
    |    2. A suitable hardcopy printout of the system log.                                            |
    |      To obtain this, call the system log with Transaction SM21                                  |
    |      and set the time interval to 10 minutes before and 5 minutes after                        |
    |      the short dump. In the display choose "System->List->Save->                                |
    |      Local File (unconverted)"                                                                  |
    |                                                                                                  |
    |    3. If the programs are your own programs or modified SAP programs,                            |
    |      supply the source code.                                                                    |
    |      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
    |      Editor.                                                                                    |
    |                                                                                                  |
    |    4. Details regarding the conditions under which the error occurred                            |
    |      or which actions and input led to the error.                                              |
    |    You may able to find an interim solution to the problem                                      |
    |    in the SAP note system. If you have access to the note system yourself,                      |
    |    please use the following search criteria:                                                    |
    |                                                                                                  |
    |        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
    |        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
    |        "INSERT_ODS"                                                                              |
    |    If you cannot solve the problem yourself, please send the                                    |
    |    following documents to SAP:                                                                  |
    |                                                                                                  |
    |    1. A hard copy print describing the problem (short dump).                                    |
    |      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
    |      on the current screen.                                                                    |
    |                                                                                                  |
    |    2. A suitable hardcopy printout of the system log.                                            |
    |      To obtain this, call the system log with Transaction SM21                                  |
    |      and set the time interval to 10 minutes before and 5 minutes after                        |
    |      the short dump. In the display choose "System->List->Save->                                |
    |      Local File (unconverted)"                                                                  |
    |                                                                                                  |
    |    3. If the programs are your own programs or modified SAP programs,                            |
    |      supply the source code.                                                                    |
    |      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
    |      Editor.                                                                                    |
    |                                                                                                  |
    |    4. Details regarding the conditions under which the error occurred                            |
    |      or which actions and input led to the error.                                              |
    |    The exception must either be prevented, caught within proedure                                |
    |    "INSERT_ODS" "(FORM)", or its possible occurrence must be declared in the                    |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                |
    |System environment                                                                                |
    |    SAP Release..... 730                                                                          |
    |    SAP Basis Level. 0006                                                                        |
    |                                                                                                  |
    |    Application server... "pkghnp"                                                                |
    |    Network address...... "10.83.240.20"                                                          |
    |    Operating system..... "SunOS"                                                                |
    |    Release.............. "5.10"                                                                  |
    |    Hardware type........ "sun4u"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                |
    |    Work process number.. 4                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "vsyexhann01"                                                              |
    |    Database type..... "HDB"                                                                      |
    |    Database name..... "HNP"                                                                      |
    |    Database user ID.. "SAPHNP"                                                                  |
    |                                                                                                  |
    |    Terminal.......... " "                                                                        |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                        |
    |    created (date)... "Mar 21 2012 09:58:29"                                                      |
    |    create on........ "SunOS 5.10 Generic_141444-09 sun4us"                                      |
    |    Database version. "SQLDBC 1.00.61.0380109 "                                                  |
    |                                                                                                  |
    |    Patch level. 201                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "HDB 1.0"                                                              |
    |    SAP database version. 720                                                                    |
    |    Operating system..... "SunOS 5.10, SunOS 5.11"                                                |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 0                                                                                    |
    |    EM...... 100555392                                                                            |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 75424248                                                                            |
    |    MM Free. 25123904                                                                            |
    |User and Transaction                                                                              |
    |    Client.............. 330                                                                      |
    |    User................ "BIREMOTE"                                                              |
    |    Language key........ "E"                                                                      |
    |    Transaction......... " "                                                                      |
    |    Transaction ID...... "53E66CC9405502F9E10000000A53F03E"                                      |
    |                                                                                                  |
    |    EPP Whole Context ID.... "CEED21FC7C3EC04FA3C0D0912FE05A37"                                  |
    |    EPP Connection ID....... 00000000000000000000000000000000                                    |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "GP4PWAW7JG4VX23SSK75NF4776C"                                            |
    |    Screen.............. "SAPMSSY1 3004"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                  |
    |Server-Side Connection Information                                                                |
    |    Information on caller of Remote Function Call (RFC):                                          |
    |    System.............. "SP1"                                                                    |
    |    Installation number " "                                                                      |
    |    Database release... 620                                                                      |
    |    Kernel release...... 640                                                                      |
    |    Connection type 3 (2=R/2, 3=ABAP system, E=external, R=reg. external)                        |
    |    Call type.......... "synchronous and transactional type T (emode 0, imode 0)"                |
    |    Inbound TID.........." "                                                                      |
    |    Inbound queue name..." "                                                                      |
    |    Outbound TID........."0A53F03E141153E6C6641A65"                                              |
    |    Outbound queue name.." "                                                                      |
    |                                                                                                  |
    |    Client#............. 330                                                                      |
    |    User................."BIWREMOTE"                                                              |
    |    Transaction......... " "                                                                      |
    |    Call program........."SAPLERFC"                                                              |
    |    Function module "ARFC_DEST_SHIP"                                                              |
    |    Call destination.. "HNP330"                                                                  |
    |    Source server....... "pkgapp2_SP1_03"                                                        |
    |    Source IP address "10.83.240.59"                                                              |
    |                                                                                                  |
    |    Additional information on RFC logon:                                                          |
    |    Trusted relationship." "                                                                      |
    |    Logon return code....0                                                                        |
    |    Trusted teturn code..0                                                                        |
    |                                                                                                  |
    |    Note:                                                                                        |
    |    - For Releases < 4.0, information on the RFC caller is not available.                        |
    |    - The installation number is provided from Release > 700                                      |
    |    Transaction......... " "                                                                      |
    |    Call Program........."SAPLERFC"                                                              |
    |    Function Module..... "ARFC_DEST_SHIP"                                                        |
    |    Call Destination.... "HNP330"                                                                |
    |    Source Server....... "pkgapp2_SP1_03"                                                        |
    |    Source IP Address... "10.83.240.59"                                                          |
    |                                                                                                  |
    |    Additional information on RFC logon:                                                          |
    |    Trusted Relationship " "                                                                      |
    |    Logon Return Code... 0                                                                        |
    |    Trusted Return Code. 0                                                                        |
    |                                                                                                  |
    |    Note:                                                                                        |
    |    - For Releases < 4.0, information on the RFC caller not available.                            |
    |    - The installation number is available from caller Release > 700                              |
    |Information on where terminated                                                                  |
    |    Termination occurred in the ABAP program "GP4PWAW7JG4VX23SSK75NF4776C" - in                  |
    |    "INSERT_ODS".                                                                                |
    |    The main program was "SAPMSSY1 ".                                                            |
    |                                                                                                  |
    |    In the source code you have the termination point in line 84                                  |
    |    of the (Include) program "GP4PWAW7JG4VX23SSK75NF4776C".                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                  |
    |    procedure "INSERT_ODS" "(FORM)", but it was neither handled locally nor                      |
    |    declared                                                                                    |
    |    in the RAISING clause of its signature.                                                      |
    |                                                                                                  |
    |    The procedure is in program "GP4PWAW7JG4VX23SSK75NF4776C "; its source code                  |
    |    begins in line                                                                              |
    |    23 of the (Include program "GP4PWAW7JG4VX23SSK75NF4776C ".                                    |
    |Source Code Extract                                                                              |
    |Line |SourceCde                                                                                  |
    |  54|* leave further processing because data is not consistent                                  |
    |  55|                                                                                            |
    |  56|  IF l_inconsistency_found = rs_c_true.                                                    |
    |  57|    p_subrc = 77.                                                                          |
    |  58|    EXIT.                                                                                  |
    |  59|  ENDIF.                                                                                    |
    |  60|                                                                                            |
    |  61|                                                                                            |
    |  62|                                                                                            |
    |  63|                                                                                            |
    |  64|  DATA: l_t_data TYPE ty_t_data,                                                            |
    |  65|        l_s_data TYPE /BIC/B0000674001.                                                    |
    |  66|*---1363526 Increasing the security to check the number of records inserted in PSA table    |
    |  67|*---is actually equal to data in l_t_data or p_t_data.                                      |
    |  68|  DATA: l_rollback TYPE rs_bool,                                                            |
    |  69|        l_count TYPE i.                                                                    |
    |  70|  l_rollback = RS_C_FALSE.                                                                  |
    |  71|*---1363526                                                                                |
    |  72|                                                                                            |
    |  73|  APPEND LINES OF p_t_data TO l_t_data.                                                    |
    |  74|                                                                                            |
    |  75|  CLEAR: l_s_data.                                                                          |
    |  76|  l_s_data-partno = p_partno.                                                              |
    |  77|                                                                                            |
    |  78|  MODIFY        l_t_data                                                                    |
    |  79|  FROM          l_s_data                                                                    |
    |  80|  TRANSPORTING  partno                                                                      |
    |  81|  WHERE        request = p_requestid.                                                      |
    |  82|                                                                                            |
    |  83|                                                                                            |
    |>>>>>|  INSERT      /BIC/B0000674001                                                              |
    |  85|  FROM TABLE  l_t_data                                                                      |
    |  86|  ACCEPTING DUPLICATE KEYS.                                                                |
    |  87|*---1363526                                                                                |
    |  88|  DESCRIBE TABLE l_t_data LINES l_count.                                                    |
    |  89|  IF l_count NE sy-dbcnt.                                                                  |
    |  90|    l_rollback = RS_C_TRUE.                                                                |
    |  91|  ENDIF.                                                                                    |
    |  92|*---1363526                                                                                |
    |  93|                                                                                            |
    |  94|                                                                                            |
    |  95|*---1363526                                                                                |
    |  96|  IF sy-subrc NE 0 OR l_rollback = RS_C_TRUE.                                              |
    |  97|*  Insert not successful - rollback changes                                                |
    |  98|    CALL FUNCTION 'DB_ROLLBACK'.                                                            |
    |  99|*---1363526                                                                                |
    |  100|    p_subrc = 13.                                                                          |
    |  101|  ENDIF.                                                                                    |
    |  102|                                                                                            |
    |  103|ENDFORM.                    "INSERT_ODS                                                    |
    |    isShmLockId  = 0                                                                              |
    |    isUsed      = 1                                                                              |
    |    isCtfyAble  = 1                                                                              |
    |    hasScndKeys  = 0                                                                              |
    |    hasRowId    = 0                                                                              |
    |    scndKeysOutdated = 0                                                                          |
    |    scndUniKeysOutdated = 0                                                                      |
    |    ----- Shareable Table Header Data -----                                                      |
    |    tabi        = 0xFFFFFFF1DD5E8E58                                                            |
    |    pgHook      = 0x0000000000000000                                                            |
    |    idxPtr      = 0x0000000000000000                                                            |
    |    id          = 11    (0x0000000B)                                                            |
    |    shmTabhSet  = 0x0000000000000000                                                            |
    |    refCount    = 0    (0x00000000)                                                            |
    |    tstRefCount  = 0    (0x00000000)                                                            |
    |    lineAdmin    = 4    (0x00000004)                                                            |
    |    lineAlloc    = 4    (0x00000004)                                                            |
    |    shmVersId    = 0    (0x00000000)                                                            |
    |    shmRefCount  = 1    (0x00000001)                                                            |
    |    rowId        = 18446744073709551615                                                          |
    |    scndKeyAdmin = 0x0000000000000000                                                            |
    |    0A53F03E141153E6C6641A65HNP330                          00000001SENDED  RSAR_TRFC_DATA_RECEIVE|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    3433433433333343433334334453332222222222222222222222222233333333544444225545555445445455444454|
    |    0153603514115356366411658E0330000000000000000000000000000000000135E454002312F4263F4141F2535965|
    |    0030004100350033004600300033004500310034003100310035003300450036004300360036003400310041003600|
    |PROG                                                                                              |
    |    SAPLERFC                                                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    5454454422222222222222222222222222222222                                                      |
    |    310C526300000000000000000000000000000000                                                      |
    |    005300410050004C004500520046004300200020002000200020002000200020002000200020002000200020002000|
    |%_DUMMY$$                                                                                        |
    |                                                                                                  |
    |    0000                                                                                          |
    |    0000                                                                                          |
    |    2222                                                                                          |
    |    0000                                                                                          |
    |    0020002000200020                                                                              |
    |NUMBER_OF_FUNCTION_MODULES                                                                        |
    |    1                                                                                            |
    |    0000                                                                                          |
    |    0001                                                                                          |
    |    00000001                                                                                      |
    |SUPPORTABILITY_INFO-DEBUG_CONTEXT_ID                                                              |
    |                                                                                                  |
    |    0000000000000000000000000000000000000000                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    2222222222222222222222222222222222222222                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
    |SPACE                                                                                            |
    |                                                                                                  |
    |    0                                                                                            |
    |    0                                                                                            |
    |    2                                                                                            |
    |    0                                                                                            |
    |    0020                                                                                          |
    |SCREEN                                                                                            |
    |                                                                                                  |
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
    |No.      4 Ty.          FUNCTION                                                                |
    |Name  ARFC_DEST_SHIP                                                                              |
    |SENDER_ID                                                                                        |
    |    pkgapp2_SP1_03                                                                                |
    |    00000000000000000000000000000000                                                              |
    |    00000000000000000000000000000000                                                              |
    |    76667735553533222222222222222222                                                              |
    |    0B71002F301F03000000000000000000                                                              |
    |    0070006B00670061007000700032005F005300500031005F0030003300200020002000200020002000200020002000|
    |SUPPORTABILITY_INFO                                                                              |
    |    ########                                        ##  #                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    000000002222222222222222222222222222222222222222002220                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    0000000000000000000000000000000000200020002000200020002000200020002000200020002000200020002000|
    |UNIT_ID                                                                                          |
    |    ################                                                        

    Hi Siddartha,
    That option is not working.
    Thanks

  • PSA request deletion Error

    Hi All,
    I have a problem for which i am not able to get the proper solution from the threads.
    Can anyone help me to solve this.
    I am getting this error "" RSDU_TABLE_DROP_PARTITION_MSS Error while creating the clone table /BIC/B0000183000"
    while deleting request from the psa.
    This error i am getting because i have deleted the data from the psa table from the tcode se14, but the requests are still there in the request. There is no data in the psa but the request exists.
    Now i want to delete the empty request, because i am scheduling the process chain to delete all request older than 3 days. But because of this empty request, i am getting the error while scheduling the process chain.
    I also tried to delete the psa data from rsa1old but to no sucess.
    Can anyone help me to solve this issue.

    Hi ,
    For your issue you can try these steps : -
    1 - Run the report - SAP_DROP_TMPTABLES.
    2 - Run the report - RSAR_PSA_CLEANUP_DIRECTORY_MS.
    You can Check details for the report execution from the  note : 1063105 - Program "RSAR_PSA_CLEANUP_DIRECTORY /_MS"
    3. You can also check the note - 1299865 - DB Shadow tables with '@k' name (e.g /BIC/B0000201@k0).
    Regards,
    Lokesh

  • PO Status Deleted in SRM

    Hello Everyone,
    I accidentally deleted all of the status of a PO using FM CRM_STATUS_DELETE. To bring back the status of the PO, I inserted the status using CRM_STATUS_UPDATE.
    Now that the status are visible in the PO document, I tried to push it to backend using BBP_PD_PO_TRANSFER_EXEC but an error message came out: "Buffer Table not up to date". There were inconsistencies in the PO status.
    Would you know how to correctly update the status of the PO so that it can now be pushed to back-end?
    SRM Component version: SRM 4.0
    Thanks in advance for your feedback.
    Regards.

    Hi Shravya,
    how could you delete the PO? Once the PO was output, and sent to the vendor, shouldn't be able to deleted.
    !!!   It is not recommended to change documents on the SAP GUI, especially not with direct update  !!!
    Nevertheless if you would like to do this, you can also update the PO directly on the database. Start the transaction BBP_PD. From here you can navigate to the corresponding table. You need to remove the deleted status from the table CRMD_JEST, and remove the deletion indicator from the header and item as well.
    At first test the same in your test system.
    Regards,
    Peter

  • DOCUMENT QUEUE STATUS "DELETING" AFTER LOADING FROM WIRELESS PC

    HAVE HOME NETWORK. DESKTOP VISTA PC CONNECTED TO HP PRINTER BY USB.  DSL ROUTER USED WITH WINDOWS 7 LAPTOP. NETWORK OK, SET UP FILE SHARING AND LAPTOP RECOGNIZES PRINTER. PRINT COMMAND FROM LAPTOP SHOWS IN PRINT QUEUE ON DESKTOP, SHOWS 1 DOCUMENT,
    BUT RATHER THAN PRINTING SHOWS "DELETING" UNDER STATUS. LEFT WITH EMPTY QUEUE. I AM ONLY MODERATELY TECH SAVY SO PLEASE BE GENTLE. THANK YOU. PURSITA2

    Hello,
    The TechNet Sandbox forum is designed for users to try out the new forums functionality. Please be respectful of others, and do not expect replies to questions asked here.
    Since your post is off-topic, I am moving it to the
    off topic forum.
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog: Unlock PowerShell
    My Book:
    Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  • Error in PSA Request deletion

    Hey all,
    how are you!
    I have a little glitch in my Processchain and since I can not seem to find an answer myself I was wondering if any of you might give me some feedback
    In a processchain I created, I wanted to delete the PSA-table contents and I added this process called "Deletion of requests from PSA".
    But whenever I check my daily run, I have to get back (due to its "red" nature) and do manually 'rightclick>repeat' and then all seems well.
    The 'red' condition upon monitoring gives me the message "no sub-request for this request"...
    well...anyone?

    Hey Olivier,
    It is a transactional load from an R/3 ODS.
    In the processchain first we load an ODS and then we start with a request-deletion on the PSA.
    Options:
    - older then...zero days
    the others are not used.
    Nothing fancy
    Just following
    http://help.sap.com/saphelp_nw70/helpdata/EN/b0/078f3b0e8d4762e10000000a11402f/frameset.htm
    Edited by: richard boom on Jan 17, 2008 2:29 PM

  • Deleted site, still appears in SCCM 2012 console status: deleting...

    Hi i recently encountered a problem after deleting a secondary site, but it seems to happen only under my user account on the primary site console, here's the thing
    I deleted the site, and the log shows that the site was succesfully deleted, i connected to the server and the logs are ok, and the registry no longer has any SMS keys left to delete, and in programs files, both the configuration manager files, and the sql
    files were also deleted/uninstalled correctly, but in my console, the site still appears as Deleting...
    Note that I was the one who created it in the first place, and apparently I'm the only one who can still see it..., I open the console in both, the primary site server, and on my computer, and it shows as deleting, under Administration > sites configuration
    > sites, and I can still see the server on the site and site sistem roles, and that's it, and if I switch to the Central Site, is not there, which I guess is good
    I checked on both my colleagues, and they don't see the site anywhere, just me under my user account connected to the primary site
    Now, i did ran the Preinst /DELSITE command and it says that it couldn't find the data base for the site, which is good as well
    Part of the problem is that, I have to re-install the site, and if I run the setup connected to the primary site under my account, it says that the name already exists (i have to re-use the site code as per request) and if I run the same setup but
    connected to CAS or a colleague does it on primary or cas, the setup continues without the warning saying that the site code already exists
    So I would just like to find a way to delete it from my console or find the reason that's causing it, to avoid further conflics for that secundary site

    http://technet.microsoft.com/en-us/library/gg712320.aspx
    Re-Using Site Codes
    <content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Site codes cannot be used more than one time in a Configuration Manager hierarchy for a central administration site or primary sites. If you reuse a site code, you run the risk of having
    object ID conflicts in your Configuration Manager hierarchy. You can reuse the site code for a secondary site if it is no longer in use in your Configuration Manager hierarchy or in the Active Directory forest.</content>
    Have you deleted from AD Container ? did you cheked the hman.log ? is the replication ok?
    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
    Click on "vote as Helpful" if you feel this post helpful to you. This can be beneficial to other community members reading the thread. ------------------------------------------------ PaddyMaddy | http://paddymaddy.blogspot.com/

  • Deleting red delta packet in PSA

    Hello,
    Today morning, I had a red delta packet in PSA, I deleted it, and executed Delta infopackage again.
    It gave me a warning that, this will request again the same delta packet. So I guess, there is no loss data from delta. Can you confirm it?
    My collegue said that, I shall check ROOSPRMSC from R3 and, I should change status of delta packet from red (back to technical status) to red (status NOT OK).
    What is the logic of the operation my collegue said?

    Hi,
      Whenever a delta infopacakge fails then its advisable to make the technical status red manually by going to monitor and making the status RED. But in your case since you said that you got a warning to repeat the delta then there should be no problem. But in future just remember to make the status red manually as always we need to make be sure that no issues are faced.
    alos i would sugest you to be a bit cautious before you repat the infopackage becasue in case if even one delta is missed then you wil need to take lot of efforts in correcting the data. Some checks before repeat delta:
    1) Try to anlyze why the error was faced
    2) Check whether the job was cancelled or over in the source system.
    3) Check the status of job in BW system, even if it is red then make the technical status red manually in montior.
    4) Repeat the delta.
    Check the below thread for more soem good info on repeat delta :
    Repeat of Delta
    In you case you waont face any problem becasue you got a message to request the last data again. The reason for it was that your job was terminated in R/3 as well as BW.
    Thanks

  • How to delete PSAs via process chain

    How to delete PSAs via processchain using program(need to delete automatically).
    For that i have to create the processchain for specially deletiung the PSAa and need to write the code for deleting automatically.

    Hi
    Please follow the below steps for PSA processchain deletion.
    Create the Start varint
    Drag the PSA deletion PSA Request from left menu bar proces types
    Click on maintain varinat of the above dragged psa deletion
    There you select like below
    Object Type:PSA
    Objectname:PSA Table name
    Select the below options on the same screen as Older than 10 days ...
    As per your requirement you can select the options..
    Hope it will helps

  • Unable to delete a set of records from PSA

    Hello All,
    I am trying to delete a PSA request (INIT With data transfer) which had about crores of records. But in my PSA, I can still see about 16000 records from the earlier deleted request.
    Please advice as my next INIT is not brininging in any records. the issue is very critical...
    Regards
    Sneha

    Hi,
    Check out for any other History Init Request available in the PSA and delete it. Or use the program - RSAR_PSA_CLEANUP_DIRECTORY to clean the PSA Completely. Next, check out in the InfoPackage menu, Scheduler - > Initialization for source system, whether there is any successful Initialization request is available or not. If available delete the request by selecting delete from all the systems.
    Now, you can again use the Init Infopackage to initialize the delta.
    Regards,
    Geeta

  • PO status not set to Deletion

    We are using ECS scenario on SRM Server 5.5 with ECC 6.0.
    Deletion of a PO line item changes the value of the PO to $0.00, but does not set the status of the PO to Deletion. It remains as "Ordered". (PO has already been outputted).
    Furthermore, the backend PO line item is also not deleted.
    Any idea how does the status of a PO changes to "Deleted"
    Any help will be appreciated.
    Thanks
    -Bakulesh

    Hi Bakulesh,
    Can you please have a look at the purchase order line which you have deleted , status of that will be set to 'deleted'. There will be one thrash icon which indicates that the purchase order line is deleted.
    As first step , for your purchase order , please check out following things.
    1) as far as i know , there is no status 'deleted' for the purchase order header , only the lines of the purchase order will have status 'deleted'.
    2)do you have this problem with all the purchase orders , or it happens only for specific purchase order?
    3) In the transaction 'BBP_PD' , you can have a look at the status of the purchase order at the header level and item level.
    4)run the function module 'BBP_PD_PO_GETDETAIL' for the purchase order and see what are the values for status in table 'ET_STATUS'.

  • "Delete PSA" variant  not transported

    I have a process chain which involves a 'Delete PSA request' process. When this is transported into our Test environment the variants do not appear so the deletion does not happen. The process still exists but the variant defining which PSA to delete is blank and so no deletion occurs.
    Does anyone know what the problem could be and how we can resolve it?

    Hi, the table names are different in Dev and QA (/BIC/B0000628 in QA and /BIC/B0000302 in Dev). So if we reactivate the datasource in Dev, then re-transport the datasources and then retransport the process chains should this resolve the issue? Would the psa tables be re-created with the correct table names in QA if we do this?
    Nothing in QA has been activated manually after transport so not sure how that would happen.
    We are using NW 2004s, SP 8 at the moment.
    Thanks for you help
    Message was edited by: Katherine Huggins

Maybe you are looking for