Hi Rodrigo,
in a nutshell:
- you can define status network based on objects (w.g. material)
- Define Attributes: you can define attributes like DELETION_ALLOWED or LOCKED_FOR_CHANGE and you can implement preconditions in custom classes when should it happen
- Define Status Field: you can define some fields which are related to the status. e.g. in recipe management RCP_USAGE
- Status: you can define the different statuses (e.g. in process, completed..) with attributes
- Scheme Definition: you can define the logic between statuses. E.g. you would like to swith from status In Process to Completed and from New to In Process. Then switching from New to Completed is not possible for the user.
- Subobject Type Scheme only applied if you have subobjects
here you can find the customizing documentation, there are some examples as well:
Define Status Scheme
Use
In this Customizing activity, you define statuses and status schemes for object types and corresponding attributes.
For each status, you can define which attributes are allowed to be set for an object with this status assigned.
The status scheme defines the initial status and the possible transitions from one status to another.
Activities
You define status schemes as follows:
1. Select the required object type and enter the following:
a) An identifier
b) An object type class (Note: this class should implement the interface class)
c) A subobject type search help
The search help provides a list of all possible subobject types. This feature enhances the usability while maintaining status schemes at subobject-type level.
d) If the
Status
tab page shall be visible on the PLM Web UI, select the
Status Tab
checkbox
.
Status and action management is a reusable object. It has been modeled as a dependent object. The prerequisites to enable status and action management for any new objects are:
- Add the Status and Action Management tab page on the UI.
- Enable the Status Tab checkbox in this Customizing activity.
2. Select the required object type and define the following attributes for it:
a) An object type
b) An attribute identifier
c) An attribute description
d) An attribute type
e) Select a precondition class (Note: This class should implement the '/PLMB/IF_SAM_PRECONDITION' interface)
3. Define the technical status field name.
When you change the object status, the system updates the technical status field names to the new values made in these settings.
4. Select object type and define corresponding statuses.
a) Select the status and define the corresponding object type, an identifier, description, and status icon.
Note:
You cannot define new statuses for materials and material BOMs. For these objects, all values should be transferred from the back-end system.
You can import the status values from the back-end system as follows:
b) Select the object type that represents a material or a MatBOM.
c) Select
Status
in the dialog structure.
d) Choose the
New Entries
pushbutton.
e) Choose the
Import Status
pushbutton.
Note
The system imports the following status values into SAM:
X-plant matl status
(cross-plant material status)
For MatBOM: the header status
Although you cannot change the imported value for a material or a MatBOM, you can change its name and description to conform to SAM terminology.
You can differentiate between the following cases for objects whose status values are imported from the back-end system:
The object was not created on the PLM Web UI, but in the back-end system; no SAM status scheme or status was assigned, but a status value was set in the back-end system.
If you assign a SAM status scheme to this object later on that contains the equivalent imported status values, the SAM status value is set accordingly, even if any precondition check results of the SAM status scheme may exist.
The object was created in the back-end system or on the Web UI and a SAM status scheme is assigned to the object on the PLM Web UI.
If the corresponding status value is changed in the back-end system, then existing SAM preconditions for this status transition and allowed status transitions are checked. If the preconditions are not fulfilled, a message is raised and the new status cannot be saved.
5. Specify which attributes are allowed for each object type when the chosen status is set.
a) Select a status and open the
Attributes
screen.
b) Choose an object type.
c) Choose an attribute.
6. Define whether values from other technical fields are affected by setting this status.
a) Select a status and open the
Field Values
screen.
b) Select an object type.
c) Select a technical field name.
7. Specify the status scheme. The status scheme defines the initial status and status transition for the object type. For example, below is a list of standard status schemes defined for iPPE object types.
- Assembly Header - PLM_PPEAH
- Assembly Item - PLM_PPEAI
- Product Item Variant - PLM_PPEPIV
- Product Variant - PLM_PPEPV
You can also create schemes for the object type as follows:
a) Specify an identifier and description for the status scheme and set one of the statuses defined above as the initial status.
b) Select the status scheme and open the
Transitions
screen. Enter all possible status transitions by specifying the source (
Status From
) and target status (
Status To
).
c) Select the
Long Text
checkbox if you want the system to open the long text editor on the
Status
tab in the PLM Web UI. You can use the long text editor to create notes for this transition.
8. Define the scheme at subobject-type level by entering following parameters:
a) Object type
b) Subobject type (You can choose from the list of subobject types you have specified when defining the search help in step 1)
Alternatively, you can define a default status scheme that is automatically displayed on the
Status
The following statuses are included in the standard delivery:
- REPLACE_PH_ASSEMBLY (only in the PLM_PPEAI assembly item and the PLM_PPEPIV product item variant)
- 30 - Released For Planning
The following status transitions are possible:
| FROM | TO | Long Text checkbox (dialog box for notes) |
|---|
| 10 | 20 |
| 20 | 30 |
| 30 | 40 |
| 20 | 40 |
| 20 | 10 | X |
| 30 | 10 | X |
| 40 | 10 | X |
More on SAP help:
Status and Action Management on the Web UI - SAP Library
Best regards
Tamas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.