Total Pageviews

Thursday, November 8, 2012

Revision Number

Use:-

You can use revisions to collect larger service or maintenance tasks under one number.
You enter a revision number in a notification or in an order and use it to summarize several notifications or orders.

Integration:-

The revision is connected to the status management and change documents.

You can enter the following data in a revision:

    Start and end of a revision
    Functional location
    WBS element or network

You can only assign a revision to a notification or an order if it has the status opened or released. You can then only close it if the assigned notifications or
orders are closed. If a revision has the status opened you can only directly close or delete it if no notifications or orders are assigned to it.

Notification and Order Processing

If you enter a revision when creating or editing an order, the dates in the revision are copied to the order. The same applies if:
(a) you create a notification from an order or
(b) you are creating a notification and you enter a revision at the same time as you create an order.

If you are editing a notification and enter a revision retrospectively, a dialog box appears. You must then decide if you want to copy the dates from the revision
to the notification.
Some notifications contain a revision and have been assigned to an order via an object list. You can delete these notifications from the order object list at anytime.

Checks

The system carries out various checks in the notification and in order processing.
You can make settings in Customizing to control how the system should react:

        If you assign notifications to an order, the system checks whether the revisions from the notification and order are the same.
    If not, the system will check whether they are allowed to differ.
        You create a revision for a specific functional location and enter the revision in a notification or order.
    A functional location is also entered as the base object in the notification or order. The system checks whether the base object
    (from the notification/order) is installed in the functional location structure (from the revision) or if it is identical.

    If you are processing a revision, the system will also check whether the revision is already assigned to a notification or order.
    The system then checks to see if a functional location has been entered in the notification/order.

        If the revision is assigned and no functional location has been entered in the notification/order, you can enter a functional location as a reference object in the revision.
        If the revision is assigned and a functional location has been entered in the notification/order, you cannot enter data in this field of the revision.

    You create a revision for a network and enter the revision in an order. A network is also entered in the order. The system checks whether the network (from the order) is contained in the network structure (from the revision).

The system carries out a similar check if a WBS element has been entered in the revision and in the order. However, in this case you cannot use Customizing to set the message, and you must decide whether you want to copy the WBS element from the revision to the order.

1 comment:

  1. Hello Nikhil ,
    Its a nice post , Really Helpful , We are trying to create a scenario where we create a notification from order where the order is in CRTD MANC NTUP status, While coming back to notification from order and assigingna revision level to the order , system is giving a dump , while its not in case if we doc not assign a revision to notification .
    Please help
    9004116438

    ReplyDelete