Any standard functionality Exists to update the Specification status to " Released" using OCC?

[Ramu-Mannava]

Once we load the Specifications by OCC Tool, Any standard functionality Exists to update the Specification status to " Released" ?

[satya11719]

Hello Ramu ,

Obselete you can find mainly for recipes,

Based on business requirement we can modify the functionality addition and modification.

Based on your requirement you amend the status, FR means almost all the data entry was completed. So at this stage if your business want a block ,then you cannot modify , but in standard you can add or delete.

If my answer clarifies , please accept the answer.

Thanks

Satya

[Ramu-Mannava]

Hi Satya,

I found the Standard SAP ABAP Report /PLMI/SPC_SAM_MASS_STS_CHANGE can do the Mass Change for Header Status of Specifications. and /PLMI/SPC_SAM_MASS_C is the Transaction code which is relevant to this above SAP report.

Does this Program suffice my requirement ? I tried running this program by giving a single specification and executed. But i am not able to make the status change happen.

I got the message "Substance has reached its final status 100 in Scheme Z_SPECSTAT"

is it because of i am not having authorization to the role "SAP_PLMWUI_STATUS_CHANGER" ?? (This will do enable users to make the status changes in the Header Status Tab)

Can you please suggest in this? is this right way ?

FYI , please see Some Reference links i got Link 1, Link 2 : Spec Header Status and Role for Header Status

I performed the above activities by referring to the above links.

kindly suggest.

Best regards

Ramu M

[satya11719]

Hello Chowdary R

As of i know there is now such functionality , Cause status is all together different business functionality you cannot directly set it to released , Need to follow once step after another IP (In Process) - FR (For Release) - NC (Noncritical Change) - RE (Released).

Mostly it will be used for workflow set up to know the status of the specification based the property filling.

Still you can try the below in OCC , making an update based on the particular usage,

Depending on the sequence in the status network (see below), you can assign the statuses in the header data of a Specification to the usages required.

For example, to forbid changes to data of value assignments and identifiers that have the usage PUBLIC/DE, create the following status entry in the header data of the relevant specification:

Rating ValACat ValArea StatusPUBLIC REGION DE Released

For more information check the SPRO - Specify Statuses.

I hope it helps.

Cheers

Satya

[Ramu-Mannava]

Hi Satya,

Thank you so much for the reply,

As i can see there are 2 Status Tabs. 1 will work with Workflow process.

And 2nd one will have (100-In Process,400-Obsolete).Usually we can find this Tab as the Last one.

In this, If the status is 100 means , we can still alter the specification.

If the status 400 means, we may not able to do anything w.r.to that Specification.

So, As u said, FR-For Release in the 1st Status TAB. FR means , will it allow us to alter the specification/assign materials.. e.t.c?

Kindly clarify

Best regards

Ramu

[christoph_bergemann]

Hello

1.) the "Status" on specification header is not often used; you will find not more than 20 threads here duscussing the status

2.) first you need to prepare the whole "customizing" and you need to implement an "access concept"

3:) then you can use the many "exits" in CG02 to do the job (Secondary data determination); based on hit list you can use an own developped ABAP based on hit list to get a number of spec id in the status "Released"

The use of a "Status net" is an important business decision ! The reality is showing: in most cases the process is "to complex" for te end user and overall has some pitfalls to lookat

Conclusion: SAP has provided only a framework (by standard). It is on your side to do the whole coding...

C.B.

PS: here as an example one of the not so many threads discussion the "status": https://answers.sap.com/questions/6636493/specification-status-in-header-specification-workb.html

Please execute an own research

PSS: there is a "pdf" file existing describing the options how to use "OCC" and how to prepare the "EXCEL" file (with the data); i did not check the pdf file for an example regarding the "Status net"... PLease check for OCC related content here; in one of the many threads you will find links to this important pdf file; there is some chance that the "status" is listed in the pdf file

Check e.g. https://answers.sap.com/questions/11711624/data-import-with-the-ehs-open-content-connector.html