cancel
Showing results for 
Search instead for 
Did you mean: 

status text could not be determined

MTerence
Active Contributor
0 Kudos

Hi experts

I am using ECC 6.0, upgrade to ECC 6 from 4.7 around a year go. We didn't face any problem like this.

I want to delete a project which is created in 2002. I deleted the WBS elements and i saved it. Then i went to CJ02 and and deleted the project and saved it.

I tried to open the project, it is there, but the error message in status text could not be determined...

I have already used the OSS notes given here...519976 & 701946. But i am not sure, why this problem is occured.

Do let me know, how i can revert the status back, is there any solutions for this

- Pithan

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Pithan,

I am working on ECC 6.0 and facing the same error as you faced sometime back.

Can you please let me know the details of the correction instructions provided by SAP so that it would be helpful to us in resolving the issue.

Thanks in advance.

Nagarajan

MTerence
Active Contributor
0 Kudos

Hi

SAP has provided a correction program, so it was resolved.

0 Kudos

Hello Maria,

Can you please help with the OSS Note number regarding this correction program

Former Member
0 Kudos

Hi,

I also have same problem in ECC 6.0 and I am not able to delete a project. I saw SAP Note 701946 but is it applicable for ECC 6.0?

Will anybody help me?

Former Member
0 Kudos

Hello Rashid,

This Problem occurs since the person who tried to delete the project was not having complete authorization to delete the project. Hence the project was deleted inconsistently. Currently your project is having inconsistent status and you are facing this issue.

The user trying to delete the project must have a role which has authorization object C_PROJ_PRC with act 06. This will grant authorization to delete project. This change will prevent such possibility in the furture.

To correct the current project you will need to create a program which will bring the project in CRTD state. Once the project comes in CRTD state the user with above mentioned role can easily delete the project without getting any inconsistencies.

Use following Code to bring the project in consistent state:

&----


*Author : Priyank Joshi

*Creation date : 15-12-2009

*Short Description : PS Create Project Status for inconsistent Projects

*Component Function :

*Developement Class : ZPS1

*Request Number :

*Correction Number : ---

&----


*Logical database : None

*Smart Form : None

*Short description :

*Style :

*Short Description :

*Structure :

*Short Description :

*Sort Requirement : Yes

*Unix Shell Script : None

*File Locations : None

*Logical File names : None

*Text Elements : selection-text

*&----


&----


*& Report ZPS_CRT_STS

*&

&----


*&

*&

&----


REPORT zps_crt_sts.

PARAMETERS: p_pspid TYPE proj-pspid.

DATA: e_objnr TYPE jsto-objnr,

i_objnr TYPE jsto-objnr,

i_stonr TYPE tj30-stonr.

AT SELECTION-SCREEN.

SELECT objnr FROM proj INTO e_objnr UP TO 1 ROWS WHERE pspid EQ p_pspid.

ENDSELECT.

IF sy-subrc IS NOT INITIAL.

MESSAGE 'Invalid Project' TYPE 'E'.

ENDIF.

START-OF-SELECTION.

SELECT objnr FROM proj INTO e_objnr UP TO 1 ROWS WHERE pspid EQ p_pspid.

ENDSELECT.

IF sy-subrc IS INITIAL.

CALL FUNCTION 'STATUS_OBJECT_CREATE'

EXPORTING

  • CHGKZ = ' '

client = sy-mandt

objnr = e_objnr "'PD00000944'

obtyp = 'PDN'

stsma = 'Z000001'

  • IONRA_IMP =

  • I_OBJECTKEY =

  • ONLY_E_STATUS = ' '

IMPORTING

objnr = i_objnr

stonr = i_stonr

EXCEPTIONS

  • obtyp_invalid = 1

status_object_already_exists = 2

  • stsma_invalid = 3

  • stsma_obtyp_invalid = 4

OTHERS = 5

.

IF sy-subrc <> 0.

CASE sy-subrc.

WHEN 2.

WRITE: 'STATUS Object Already exists for Project: ', p_pspid.

WHEN OTHERS.

WRITE: 'Unknown Error occured during creation of STATUS object for Project: ', p_pspid.

ENDCASE.

ELSE.

COMMIT WORK.

IF sy-subrc IS INITIAL.

WRITE: 'STATUS Object Created Successfully for Project: ', p_pspid.

ENDIF.

ENDIF.

ENDIF.

With Best Regards,

Priyank.

Former Member
0 Kudos

Hello Rashid,

This Problem occurs since the person who tried to delete the project was not having complete authorization to delete the project. Hence the project was deleted inconsistently. Currently your project is having inconsistent status and you are facing this issue.

The user trying to delete the project must have a role which has authorization object C_PROJ_PRC with act 06. This will grant authorization to delete project. This change will prevent such possibility in the furture.

To correct the current project you will need to create a program which will bring the project in CRTD state. Once the project comes in CRTD state the user with above mentioned role can easily delete the project without getting any inconsistencies.

Use following Code to bring the project in consistent state:

*&---------------------------------------------------------------------*
*Author               : Priyank Joshi
*Creation date        : 15-12-2009
*Short Description    : PS Create Project Status for inconsistent Projects
*Component Function   :
*Developement Class   : ZPS1
*Request Number       :
*Correction Number    : ---

*&---------------------------------------------------------------------*
*Logical database     : None
*Smart Form           : None
*Short description    :
*Style                :
*Short Description    :
*Structure            :
*Short Description    :
*Sort Requirement     : Yes
*Unix Shell Script    : None
*File Locations       : None
*Logical File names   : None
*Text Elements        : selection-text
*&----------------------------------------------------------------------

*&---------------------------------------------------------------------*
*& Report  ZPS_CRT_STS
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT  zps_crt_sts.

PARAMETERS: p_pspid TYPE proj-pspid.

DATA: e_objnr TYPE jsto-objnr,
      i_objnr TYPE jsto-objnr,
      i_stonr TYPE tj30-stonr.

AT SELECTION-SCREEN.
  SELECT objnr FROM proj INTO e_objnr UP TO 1 ROWS WHERE pspid EQ p_pspid.
  ENDSELECT.
  IF sy-subrc IS NOT INITIAL.
    MESSAGE 'Invalid Project' TYPE 'E'.
  ENDIF.

START-OF-SELECTION.
  SELECT objnr FROM proj INTO e_objnr UP TO 1 ROWS WHERE pspid EQ p_pspid.
  ENDSELECT.
  IF sy-subrc IS INITIAL.
    CALL FUNCTION 'STATUS_OBJECT_CREATE'
      EXPORTING
*       CHGKZ                              = ' '
       client                             = sy-mandt
       objnr                              = e_objnr   "'PD00000944'
       obtyp                              = 'PDN'
       stsma                              = 'Z000001'
*       IONRA_IMP                          =
*       I_OBJECTKEY                        =
*       ONLY_E_STATUS                      = ' '
     IMPORTING
       objnr                              = i_objnr
       stonr                              = i_stonr
     EXCEPTIONS
*       obtyp_invalid                      = 1
       status_object_already_exists       = 2
*       stsma_invalid                      = 3
*       stsma_obtyp_invalid                = 4
       OTHERS                             = 5
              .
    IF sy-subrc <> 0.
      CASE sy-subrc.
        WHEN 2.
          WRITE: 'STATUS Object Already exists for Project: ', p_pspid.
        WHEN OTHERS.
          WRITE: 'Unknown Error occured during creation of STATUS object for Project: ', p_pspid.
      ENDCASE.
    ELSE.
      COMMIT WORK.
      IF sy-subrc IS INITIAL.
        WRITE: 'STATUS Object Created Successfully for Project: ', p_pspid.
      ENDIF.
    ENDIF.
  ENDIF.

With Best Regards,

Priyank.

Edited by: Priyank Joshi on Jan 8, 2010 6:13 AM

Former Member
0 Kudos

hi

have you completed deleted the project from the database by archive. .

MTerence
Active Contributor
0 Kudos

Hi

I have not done to remove the project...

Rather than using deleiton flag, i have used delete option since i dont need this project

Now, when i login, i am getting an error as no status object not avaliable...

- Pithan

Former Member
0 Kudos

Hi Pithan,

Can you and your abaper take a look at the note 170948. It includes a custom report code which can correct this inconsistency. I think this should resolve your issue. Please let us know

Ritesh