Value assignment instance editable in released status in specification management

[former_member355940]

Hi all ,

Need some guidance .

We are working on one requirement where we want certain instances in the property tree to be editable even after the spec is released . How to proceed ?

Note - You have assigned the Change Not Permitted indicator to the appropriate status in Customizing for Basic Data and Tools under Specify Statuses .

https://help.sap.com/saphelp_erp60_sp/helpdata/en/b1/e7c2537d3ab74ce10000000a174cb4/frameset.htm

[christoph_bergemann]

Hello

further small "add on".

The "Status" handling on Specification header depends on (e.g.)

- property/value assignment type

- usage of data record (property/value assignment type)

The use of "Status" is quite rare (i would assume); e,g. you increase "maintenance complexity" if you would like to use "rule sets". To use rulesets (in your scenario) you must revoke thr "released status" befroe you can go on

But for "status management" handling some "extension" options are possible. But this option is used very customer specific and therefore no general help is possible

C.B.

[christoph_bergemann]

Hello

your topic is not "easy" to handle. Normally you can different "values" in VAT by "usages". And the "Status" on spec header "corresponds" to the usage on datalevel on the VAT. Now if "STANDARD/REG_WORLD" values should not be changed: the idea of the status is normally as:

You maintain something; Then your "release" the change (by using the "Status"), but in >99% of cases there must be an option to change the value afterwards (and therefore change the "status".

PLease check therefore the "Status" net. There are option to "enhance" the process. We are not using the Status (much to complex fo rnormal endusers).

C.B.

PS: the SAP online help provides a good idea of the use of "Status"; in the example shown the "key date" was discussed. Top use "key dates" (or change numbers) increase the complexity of your EHS system and should be avoided (or used only if there is realy a good business case for use),