SAP ABAP IMG Activity EHS_SR_210_10_15 (Check Document Status)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ CBIMG1 (Package) EH&S: IMG Migration
IMG Activity
ID EHS_SR_210_10_15 Check Document Status  
Transaction Code S_ALR_87008697   IMG Activity: EHS_SR_210_10_15 
Created on 19990122    
Customizing Attributes EHS_SR_210_10_15   Check document status 
Customizing Activity EHS_SR_210_10_15   Check Document Status 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_SR_210_10_15    

In this step, you check the status network definitions:

Standard settings EH&S

The following status definitions are included in the standard SAP system:

W1: AA Work request 
W2: IA In work 
W3: SE System error 
W4: UN Unknown 
W5: ER Errors 
W6: CO Completed 
W7: RE Released 
W8: RR Report body start 
W9: NN Not necessary 
WA: GP Generation possible 
WB: GF Generation failed 
WC: GS Generation successful 
WD: HI Histoic 
WE: GW Gen. warning 
WF: IP In process on WS (workstation) 
WX: R1 Release 1

Activities

Check whether a status network has been defined for all document types.

Recommendation

Do not change the standard settings.

Recommendation

Do not change the standard settings. See the IMG under Cross-Application Components -> Document Management System.

General instructions

In this step, you define your status network.

You can define a number of statuses for each document type, and link them to each other by defining which statuses precede and follow each other. If you define a status network for a document type, the system determines the possible entries for the status in any processing situation for documents of this type. The statuses are displayed in the logon language.

Requirements

First, complete the following steps:

If you want to enter a specific workflow task, first create the task in the Workflow Workbench (menu path: Tools -> Business Workflow -> Definition tools -> Workflow tasks).

Activities

You can change the settings for a status on the overview screen or create new statuses on the detail screen.

  1. First enter the data that identifies the status:
    • Document type for which the status is to be used
    • Document status (internal key)
      • This key is only used internally. The end user only works with the language-dependent values (in the logon language).
      When you enter a status that already has a status text and confirm your entry, the system determines the language dependent status abbreviation and the description.
      If you want to enter a status that does not yet have a status text, enter the status and choose Create new status. After you have finished entering the status, you should describe the new document status language dependently.
  2. Enter the properties of the status, for example:
    • Must the objects used in object links exist?
      (see: Indicator: object check
    • Is the document 'released' once it has this status?
      (see: Indicator: release)
    • Is the document with this status distributed in ALE systems?
      (see: Indicator: distribution lock)
    • Is the log field to be processed?
    • Is a document with this status 'complete' for engineering change management?
      (see: Indicator: complete for engineering change mgmtt)
    • Is the audit function to be executed?
      (see: Indicator: audit for originals)
    • Is a specific workflow task to be carried out?
      • First, you must define this workflow task in the Workflow Workbench.
    • Is the status to have particular properties?
      • You only need to enter a value here if you want additional checks to be made. For example, you could want to allow a certain status to be set only when a document is first created (see the data element documentation for 'Status type' for more information).
  3. Define a status network. To do this, enter one or more previous statuses. When you set a status in a document, the system checks whether the current status is one of the previous statuses for your status.

    Example:

    Three statuses are defined for document type DRW:

    • 01 - Work request
    • 02 - Change request
    • 03 - Rejected

      Now, you want to define status 04 (Inspection request). A document is only to have this status if the document has already had statuses 01, 02, and 03. This means you have to enter these statuses as previous statuses in the Prev. 1,2,3 fields.

  4. Workflow task
  5. If you want to start a Workflow task when you save the status, enter the object type (for example, WF for customer Workflow task) and the identifying key.

    Note: In the Type linkage table, you must activate event linkage. Choose the following path: Tools -> Business Workflow -> Development -> Utilities -> Events-> Event inst. linkage.
    Select the following entries:

    • Object type: DRAW
    • Event: CHANGE
    • Receiver ID: DOKST

      Set the enabled indicator on the appropriate detail screen.

  6. Program exit and FORM routine

    You can enter a program from which the FORM routine you enter is to be executed.

    You can define when the program is to be started by setting the Indicator: execute program immediately.

  7. Signature strategy You can control approval procedures by using a signature strategy. A digital signature must be made when you set this document status.
    If you create a signature strategy, you must execute the following activities:

Recommendation

Please note the business process used for documents of different document types.
Once documents of a specific document type exist, you should no longer change the status network for the document type. Otherwise, inconsistencies could occur.

Further hints

You can only use the audit function for original application data that is stored either in an archive or in a vault. See the step Define data carrier types for information on how to define a vault. Archives are defined in the "Optical archive" section of the IMG.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TDWS V - View SM30 EHS_01 Document Status 
History
Last changed by/on SAP  19990122 
SAP Release Created in